Topics created by sjason1377

You're the man, David. We are lucky to have someone like you who is so involved in interacting and helping out the community while at the same time being the main developer. Thank you!

edit: didn't realize the last person bumped up an old thread...whoops. Either case, the sentiment remains. 🙂

Please explain what you mean by "doesn't work". For example:

Do M401 and M402 deploy and retract the BLTouch?

If M401/402 are working, what happens if you test the probe using a G30 command, as described at https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe? There is no need to run M401 or M402 explicitly, because deployment and retraction of the BLTouch should be automatic.

If that is working correctly, what happens when you run G29 mesh bed compensation? (assuming you have set up the mesh details using a M557 command in config,g).

Exfat is a Microsoft proprietary patented disk format, and is therefore not supported by the Duet. Use FAT16 if your SD card is 8Mb or smaller, else FAT32.

https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

https://github.com/dc42/RepRapFirmware/releases the latest can be found here.

Try uploading the latest version of iap4e.bin, and then installing the firmware.

Check the size of the firmware file you have downloaded. It should be roughly 300kb. If it is much smaller, then you have downloaded the file incorrectly.

Where is it showing Halted: in Duet web Control, or in PanelDue? Either way, when you reset the Duet it may take a little while for DWC and PanelDue to get new status info from the Duet and update the display.

What type of endstop is it?

@chrishamm A forked version of http://gcode.ws is used in OctoPrint (the original version does not support G2/G3 commands whereas the OctoPrint fork does). Sadly it is integrated into the OctoPrint repo and not a separate fork.

@sjason1377 said in trouble with z probe offset:

what firmware should i be using?

I suggest either 2.0 or 2.0beta1.

I am using 16x. So that problem cleared up by itself. Now firmware refuses to respect the z probe offset. I have to g92 it manually. no consistency. I'm not writing in config.g or any files and things are acting up. too many inconsistency to mention. So how many bugs can I expect if I get new firmware?

@phaedrux thanks for the clarity! plain simple understanding.

Put an M42 in your slicer start, and end, script.

See: https://duet3d.dozuki.com/Wiki/Using_servos_and_controlling_unused_IO_pins

@sjason1377 Oh, and regarding how you did regarding being level: nearly 0.4mm difference between highest and lowest point is a lot when you look at the fact that many people print at 0.2mm layer height. But this could also be defined by outliers solely so (without fully understanding the meaning of RMS error) this is a little hard to tell. You might want to upload the image of the height map as displayed in DWC.

ajax disconnects all the time now