Think I found it, m558 command H parameter.

@number40fan:

Command the print head down in small steps until the nozzle just touches the bed or just grips a sheet of paper. You may need to send M564 S0 to allow movement lower than where the firmware thinks Z=0 is. You may also wish to create a macro to lower the head by e.g. 0.02mm to get greater accuracy (G91 followed by G1 Z-0.02).

Found this in the calibration wiki.

I don't think the current (1.19 firmware) manual calibration routine will allow me to access a macro but I will give it a try.

The current routine pops up a dialog with a couple of buttons to move up/down by 0.01mm until it just touches the bed.

That dialog may prevent access to the macros.

Thanks.

Frederick

It's the E parameter(s) in the M92 command in config.g that you need to change (there may be two separate M92 commands, one for XYZ and one for E. Multiply the existing value by 100/148.

They all need to be the same. Fairly tight, but don't go crazy, some people use guitar tuning apps.

A feature that automatically applies toolhead offsets. It sounds like G1 R2 will work if I update to t 1.19 beta. I will try that. Thanks

I had a result like that because I didn't run G32 first.

Hi John, Thanks for the tips.

I have not tried 1.19 Beta 11 firmware and manual leveling. How do you do that? It will be of great help if you can elaborate the steps for manual leveling in the 1.19 firmware.

Probing offsets, I am aware of and I will try them in G30.

Hope your solution works for me. Thanks in advance.

How are the FSR sensors working for you? Have you compared it to the DC42 IR sensor?

Thanks for checking that. Let me know if you manage to get the extruder misbehaving with 1.19beta11.

The system goes back to absolute extrusion after a pause because each gcode source has its own absolute/relative flag. Also, after executing a macro, the absolute/relative state of the gcode source that invoked the macro is restored to what it was before the macro was run.

The sole exception to this is that when config.g is run at startup, after config.g ends the relative/absolute extrusion flag is copied to all gcode sources from the current value. This is so that a M82 or M83 command in config.g has the desired effect.

The same considerations apply to the G90/G91 absolute/relative movement mode and to the feed rate.

I'll look at making a change so that a pause command during execution of a macro file (whether caused by M226 in the gcode or externally using M25) is deferred until execution of the macro file ends.

I see you had issues at 150mm/s. I am good at 90, so I think I'll stick with 12 volts. Appreciate the link.

Thank you David, but I can't make it work.
Sorry for these silly questions, I'm a total newbie here.

When sending G92 Z0, under "machine status", Z heads position changes to 0. But once I send G28 it goes back to the previous Z height. Config.g Z height value remains the same.

So, I did it as you previously suggested and modified the H parameter. Made my first print and….
IT WORKS!!!! 🙂

I can't believe how silent everything is now, the only noticeable noise comes from the Titan Aero fan. Might change that one for a noctua or similar. Thank you so much for this incredible board.

30x30 test cube:

A little bit overextruding, but looks great.

The best part is that segmentation or vertical banding dissapeared now. This was the main reason to do the upgrade.
Still having some corner overshoot. Any help here would be much appreciated.

E3D should tell you what current setting is appropriate for their motor. But if it's the new one with 42BYGHM208P4.5-15-X2 on the label, the datasheet I found here http://www.promoco-motors.com/products/StepperMotors/42BYGHM%20Series.pdf says it is rated at 1.2A. So if it is skipping steps, you could increase the current to 1000mA.

Glad to help, and I'm sorry that configtool introduced those errors.

I had this issue the other day when trying to tune mine I sent a manual D param of d60 and that seemed to allow it to complete?

It was the Z speed in the slicer. Got it fixed.

You can have up to 442 points on a Cartesian printer with the Series 2 Duets, e.g. 21 x 21 points. On a delta it's still 21 points across the diameter because the grid is represented as a rectangle with inaccessible points not probed.

Good info. Have had this happen to me to.

Correct. Similar flat surface with exactly the same settings looks like this: with the replacement cable

@dc42:

Do you have black paper between the glass and the aluminium? Reflections from below the glass can cause the IR sensor to have a trigger height that varies with position.

No - I was not aware of that practice - I will give it a try.

Thanks.

Frederick