mesh grid compensation crashing dwc

  • hi i thought i would have a little play with mesh grid compensation but every time i run mesh grid compensation about half way through the connection between duet wifi and the dwc browser disconnect and wont reconnect until i reset the board and reopen the browser. I have tried different spacing and probing radius but same thing happens every time. I cannot say whether this is firmware related since i have not used the mgc for quite sometime.

    duet wifi v1.4
    firmware 2.02 rc3

  • administrators

    To help me diagnose this:

    1. Which version of DWC are you using? Please upgrade to 1.22.4 if you are using an earlier version.

    2. Does DWC give an error message when the disconnection occurs?

    3. After it disconnects, if you refresh the browser tab (F5 in most browsers), does it connect again?

  • hi thanks for getting back to me. i am using dwc 1.22.4-b1 and i get the following message................
    The connection between the browser and your machine has been interrupted.

    Reason: Host unreachable

    Please wait while a new connection is being established...

    if i refresh the tab i get the page not available error i have to shutdown the printer and close the browser power up the machine and then open the browser again and then dwc will fire up

  • Moderator

  • Ok so I've been revisiting this today. I updated to the full vesion of dwc and it is still doing the same thing, the light next to the wifi chip is solid blue to say its connected but i cant reconnect without restarting both the browser and printer

  • administrators

    Press control-shift-J to open the browser debugging console, then see if any exceptions or other errors are reported when the disconnect occurs.

  • Hi this is what is shown in the console


  • That just continues on and on until i restart the machine and browser

  • administrators


    1. Is that error message at the very top the first one? If so, that one is normal when loading DWC. But the "connection reset" errors are not normal.

    2. Please send M122 from USB after the problem has occurred, and post the report here.

    3. If you send M552 S-1 followed by M552 S1 (from PanelDue or from USB) to reset and restart the WiFi module, are you able to connect?

  • once the dwc disconnects the duet is completely unresponsive to usb also when i connected the panel due it worked ok again no problems but when i disconnected the panel due it went back to playing up

  • administrators

    Please try with RRF 2.02RC4 and DWC 1.22.5 in case it makes a difference. If the problem persists, please post a M122 report taken immediately before you trigger this problem.

  • I am already using the latest firmware a dwc i will post the m122 report

  • once i start mgc i cant get m122 to work

  • administrators

    What is mgc ?

  • Mesh grid compensation

  • administrators

    Please post your config.g file. Also send M557 without parameters and report the response.

    This thread may be related:

  • 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

  • ; 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

  • 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

  • administrators

    @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

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

  • administrators

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

    once i start mgc i cant get m122 to work

    1. Do you mean that M122 doesn't even work if you send it from USB?

    2. 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.

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

  • administrators

    1. Can you confirm that the only command you send to do mesh probing is G29?

    2. 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?

    3. If loading an existing height map using G29 S1 works, are you able to save it again using M374 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.

  • 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

Log in to reply