mesh grid compensation crashing dwc
-
once the connection crashes the probing continues to the end and it saves the height map to the sd card and i am able to load it and use it. the crash occurs not as soon as i start probing but after a few probe points. i can confirm that i am using the latest firmwares and dwc releases
-
Ah OK, I see now that in your first post you said the disconnect occurs half way through probing.
What type of Z probe is it? Do you have any deployprobe.g or retractprobe.g files in /sys on the SD card?
-
PS - also, are you initiating probing from DWC? if so, do you still get a disconnect if you initiate it from USB or PanelDue instead?
-
the z probe is the smart effector and i don't have any deployprobe.g or retractprobe.g. if i deploy using usb i get the same problem but if i have the paneldue connected everything woks as it should no matter how i start the g29 command
-
When you run it with the PanelDue disconnected, is the PanelDue cable still plugged into the Duet? I'm wondering whether it could be picking up noise.
I've just disconnected the PanelDue on my delta, powered up, homed the printer and run mesh bed probing from DWC. No problems. Then I increased the number of points to 11x11, probed again, and still no problems.
-
Yes the cable is still pluged in. I'll unplug it and try again
-
i unplugged the cable and the problem went away i plugged the cable back in as before and the issue did not return. thankyou for your help
-
@monster-delta, I am surprised that leaving the cable connected caused a problem. Please can you tell me what type it is (the ribbon cable or the 4-way cable), and how long it is?
-
Its the ribbon cable that was supplied with the paneldue. I was suprised aswell and would of never thought to remove it but it worked and i don't seem to be able to recreate the issue but might be worth putting a note in the wiki to be on the safe side
-
In that case it was probably caused by the high capacitance of the ribbon cable. Something probably caused data to be written to PanelDue, and that was likely being coupled back into the receive wire through the cable capacitance. The received data probably caused an error message, and the cycle repeated. I have seen this happen on computers. But I am surprised it caused network disconnections.
