Topics created by Furbyhaxx

@furbyhaxx We support mDNS, you should be able to use that.

Duet boards (both in SBC and standalone mode) announce the "product" property which always starts with "Duet".

@Veti said in Strange bed distortion on delta machine:

strange it looked like
http://boim.com/DeltaUtil/CalDoc/Calibration.html
Tower Placement Symmetry

That, and incorrect rod length, I’d say.

Ian

@Furbyhaxx this problem has been solved

https://forum.duet3d.com/topic/19121/m701-causes-reboot-3-2-beta2/8?_=1602322980348

@Furbyhaxx said in PanelDue Stopped working:

this line was missing from my config:

what was really missing was the user reading the upgrade notes.

https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md#reprapfirmware-310

Upgrade notes:

<snip>
All PanelDue users: the PanelDue connector (or IO_0 on Duet 3) is no longer dedicated to PanelDue, therefore if you connect a PanelDue to this port you must use the following command in config.g to enable it: M575 P1 S1 B57600. You can use baud rates other than 57600, however the IAP files all assume 57600 baud; therefore if you use another baud rate then PanelDue will not display firmware update progress.

(or maybe the "All PanelDue users" part followed by Duet3 specific info makes it unclear if it applies to Duet 2? It does.

Check basics first:

Must be in /sys Must be named exactly "resume.g" Try putting an M117 "this is resume.g" in the file, to see if it really is/isn't being executed. Is pause.g being executed? How are you resuming? DWC?

thanks, when I mesaure across GND and Z PROBE IN I get constant 3.2v, when probe is not triggered and around 17v with a 10k resistor. without the endstop connected I also read 3.2 between GND and Z PROBE IN, is there something defective?