@JamesM Is the bed heater running on AC (e.g. mains)? If so, stressing out the SSR is of lesser importance - assuming your SSR is zero crossing (best if it is in this case) you need a frequency much lower than the frequency of the power supply, e.g. a tenth of the mains frequency or lower (personally I use 3Hz).

@Melfesto check your start gcode in your slicer

@OwenD That's it. Many Thanks

@Phaedrux Thanks a lot.

I didn't set the endstop pin to active-low.

On another note, how do I run the bed leveling?
Also, how do I set the Z offset?

I'm getting an error of "Z probe 0 not found" when trying to run G29 or G32
My Z "probe" is the stock tronxy one that I managed to get it to work, even though it requires 6v minimum. the duet thinks its a "switch" with the way I've gotten it to work.

Thanks

EDIT: I figured it out.
I went through the configurator again, on endstop config I set it to z-probe, then on probe type = switch

@achrn Thank you.
Using a modifier seems more convenient to me, but if there is only one object on the table, we get the wrong G-code ...
In the future, I will only use the basic settings...

@simobone19 the axis limits set by M208 are for the head reference point, which is the point from which all offsets are measured. It follows that if a tool has a positive Z offset, then for that tool to reach Z=0 the M208 lower Z limit will need to be negative. So you can either set your M208 lower Z limit to -1.85mm in config.g or you can adjust the M208 lower Z limit in your tpost#.g file for each tool.

@c310 the MAX31855 chip is for interfacing to thermocouples only. It cannot interface to PT100 or PT1000 sensors.

For PT100 sensors we make a similar daughter board that uses the MAX31865 chip.

@Phaedrux Don't know about PrusaSlicer but I will look into it, thanks

Please keep it to a single topic

https://forum.duet3d.com/topic/30594/significant-z-offset-of-bed-mesh?_=1670008389610

@Tryptamine said in Significant z Offset of bed mesh:

I measure it by homing (G28) which probes the middle of the bed once, then I drive the z axis u til the nozzle almost touches the bed.

You should be using this procedure to set your G31 Z value.

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing

@jens55 this is how it works:

Decide where you want the Head Reference Point (HRP) to be. All offsets will be relative to this point. On a single nozzle machine it is usually chosen as the tip of the nozzle. On a single head/dual nozzle machine it cold be chosen as the tip of one of the nozzles, or midway between them. On a tool changer it would be somewhere on the tool pickup head. The E3D tool changer has a Z probe n the tool pickup head and the position of that probe is normally used as the HRP.

Then define the M208 limits as where the HRP can reach, and all G10 and G31 offsets relative to the HRP. Exception: for historical reasons the G31 Z parameter is the height of the HRP at which the probe triggers, whereas if expressed as an offset it would be the negative of that value.

@dc42 Thank you. That is a nice starting point, but I do not like it as error catching mechanism. When I use my usual slicer, the print bed size should be set correctly and I expect no problems. But when the gcode comes from somewhere else – for instance I experiment with some other slicing software – that is where I would like to have those errors caught.

However. As far as I understand, RRF cannot help me at the moment. Thus I will close this thread as solved and write something in the Firmware Wishlist section.

@fraksken I suggest you check the crimp connection between the fan wires and the connector, in case the problem is a bad crimp or a broken wire.

@knicklicht the simplest option may be to increase the setting in Prusa Slicer for the minimum length of filament to be extruded for the skirt. I was having the same issue with small prints on one of my printers and that's how I fixed it.

Alternatively, put code in either the slicer start GCode or start.g to print a prime line.

@Mattq4 i should add the fix would be up your z axis jerk/acceleration and maybe max speeds etc

@dc42 The non-helpful answer is “short”. The transition from smooth to clunky is not sharp and depends on speed and acceleration settings. My impression is that @deckingman is right: When the machine starts decelerating when it is still accelerating, the effect of the inertia of the gantry is amplified.

(I’ve run the same machine with a jerk controlled driver, and with that, the moves are always smooth. That is why I’m hopeful for the 3.5.)

@dc42 Thank you!

That was it. M204 defaults to 20'000 mm/s^2. Starting to lose steps at 24'000 mm/s^2. Not bad for an Ultimaker 2 that's close to 10 years old.

@darkuncle33

Your M665 H value is way to high for a Q5.
with a stock q5 it should be no more than 220.

See here for tuning a heater.

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Heaters_tuning

Be sure to save the results after running the M303 command to tune the heater, either with M500 to save it to config-override.g (and you must add M501 to the end of your config.g to load it at startup), or you must manually enter the resulting M307 command in your config.g