mesh grid compensation crashing dwc

Monster Delta

M557
Grid: X-270.0:270.1, Y-270.0:270.1, radius 275.0, X spacing 27.0, Y spacing 27.0, 441 points
Grid: X-270.0:270.1, Y-270.0:270.1, radius 275.0, X spacing 27.0, Y spacing 27.0, 441 points

Monster Delta

; Configuration file for monster deltA

; Communication and general
M111 S0 ; Debug off
M550 monster delta ; Machine name (can be anything you like)
M551 Preprap ; Machine password (used for FTP);
;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0x42 ; MAC Address (hexadecimal)
;*** Wifi Networking
M552 S1 ; Enable WiFi
M555 P2 ; Set output to look like Marlin
M575 P1 B57600 S1 ; Set auxiliary serial port baud rate and require checksum (for PanelDue)

; Axis and motor configuration
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes backwards
M569 P4 S0 ; Drive 4 goes backwards
M574 X2 Y2 Z2 S0 ; set endstop configuration (all endstops at high end, active high)
M581 E0 S0 T0 c1 ; filament runout sensor

M665 L569.765 R287.593 H766.542 B275.0 X-0.297 Y-0.148 Z0.000
M666 X-3.819 Y2.367 Z1.451 A-0.16 B-0.10 ; put your endstop adjustments here, or use auto calibration to find themmal)
M350 X32 Y32 Z32 E16 I1 ; Set 16x microstepping with interpolation
M92 X160.00 Y160.00 Z160.00 ; Set axis steps/mm (20 tooth pulleys, 0.9deg/step motors)
M906 X1700 Y1700 Z1700 E1200:1200 ; Set motor currents (mA)
M201 X3000 Y3000 Z3000 E1000:1000 ; Accelerations (mm/s^2)
M203 X18000 Y18000 Z18000 E3600:3600 ; Maximum speeds (mm/min)
M566 X800 Y800 Z800 E100:100 ; Maximum instant speed changes
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
m84 s300
; Thermistors and heaters
M305 P0 T100000 B3950 R4700 H0 L0 ; Typical Chinese bed thermistor. Put your own H and/or L values here to set the bed thermistor ADC correction.
M305 P1 X200 ; E3Dv6 hot end. Put your own H and/or L values here if necessary to set thefirstnozzlethermistor ADC correction.
M301 H0 P20 I1.00 D1000 T2.15 W150 B5 ; PID settings for the bed
M301 H1 P20.0 I1.000 D1000.0 ; PID settings for extruder
M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B1 ; PID settings for extruder 0
M570 S200 ; Allow extra heating time

; Tool definitions
M563 P0 D0 H1 ; Define tool 0
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
M92 E467.20 ; Set extruder steps per mm for first and second extruders

M563 P1 D1 H1 ; Define tool 1
G10 P0 S0 R0 ; Set tool 1 operating and standby temperatures
M92 E467.20 ; Set extruder steps per mm for first and second extruders

; Z probe and compensation definition
M558 P5 R0.4 H10 F3000 ; Z probe is IR and is not used for homing any axes, Z probe dive height 3mm, probing speed 300mm/min, travel speed 12000mm/min
G31 X0 Y0 Z-0.1 P100 ; Set the zprobe offset and threshold (put your own values here). For a delta, use zero X and Y offset.
M557 R275 S27
;*** If you are using axis compensation, put the figures in the following command
M556 S78 X0 Y0 Z0 ; Axis compensation here

M207 S5 F3600 Z0.5 ; Set firmware retraction details
M572 D0 S0.8 ; set pressure advance

T0 ; select first print head
M501 ;load config_override.g

Monster Delta

I have tried adjusting the mesh grid spacing up to 100mm and various figures inbetween, i tried reloading the config file but neither has worked. I find it really strange that it only works with the panel due plugged in wich seems to be the opposite issue to the post you linked

dc42

@monster-delta, I just wanted to let you know that I haven't forgotten about this issue, but I find it puzzling and right now I am out of ideas

Monster Delta

@dc42 no worries there's no real rush the printer is working fine appart from this issue.

dc42

@monster-delta said in mesh grid compensation crashing dwc:

once i start mgc i cant get m122 to work

Do you mean that M122 doesn't even work if you send it from USB?
Please can you temporarily double the mesh spacing to 54.0 and try again. I am wondering whether the fact that you are using the maximum number of points is related to the problem.

Monster Delta

yes thats correct m122 doesnt even work through usb. i have tried double triple ad quad roupling the mesh spacing its exactly the same

dc42

Can you confirm that the only command you send to do mesh probing is G29?
Does the G29 command write a new heightmap.csv file to the SD card? If so, after restarting the Duet, are you able to load that height map using G29 S1 without provoking this problem? And are you able to use the "View height map" function of DWC without any problems?
If loading an existing height map using G29 S1 works, are you able to save it again using M374 https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M374_Save_height_map without getting a disconnection?

I'd like to get to the bottom of this problem before I do the 2.02 release. The above tests should help determine whether it is probing, saving the height map to file, or activating it that is causing the problem.

PS - also, please check in the DWC Settings General page that you really are running RRF 2.02RC4, DWS 1.21 and DWC 1.22.5.

Monster Delta

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

dc42

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?

dc42

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?

Monster Delta

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

dc42

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.

Monster Delta

Yes the cable is still pluged in. I'll unplug it and try again

Monster Delta

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

dc42

@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?

Monster Delta

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

dc42

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.