Printer slowly responds to G-code



  • For an undetermined reason, after a short time being powered on my printer starts responding extremely slowly. All G-code commands eventually work, but take upwards of 10 seconds to execute. I'm currently running 2.02RC2 and DWC 1.22.1.

    When I power cycle the printer things work normally for upwards of several hours, but sometimes as little as 2-3 minutes.

    Any ideas why this might be happening?



  • Can you post the results of an M122 diagnostic when it is exhibiting the problem?


  • administrators

    Do you have a DueX2 or DueX5 connected to your Duet? This type of problem can be caused by not having a short and thick enough ground wire between the VIN terminal blocks of the Duet and DueX. Another symptom is a large I2C error count in the M122 report.



  • I do have a Duex5 connected. Running M122 showed approximately 3000 I2C errors after I left the printer running for a few minutes. I replaced the ground wire with a thicker wire, but everything is in a fairly tight enclosure, so I can't see everything clearly. The new wire is about 6 inches long, an inch or so shorter and much thicker. Strangely, the old wire worked fine for the last 3 months with no changes. My next step is to just reseat all of the power wires, which might be difficult.

    Measuring the voltage at the terminal on the Duex5 still reads 12v, like normal.

    New behavior has started as well. Now no LEDs light up on the Duex5 and the servos and endstops no longer work. The stepper motor I have connected to it still works. Is this possibly a loose connection?

    Here is my new M122 output
    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02RC1(RTOS) running on Duet Ethernet 1.02 or later + DueX5
    Board ID: 08DDM-9FAM2-LW4SD-6J9F2-3S46R-K2XBW
    Used output buffers: 1 of 20 (15 max)
    === RTOS ===
    Static ram: 28460
    Dynamic ram: 98040 of which 0 recycled
    Exception stack ram used: 356
    Never used ram: 4216
    Tasks: NETWORK(ready,400) HEAT(blocked,1232) MAIN(running,3476)
    Owned mutexes:
    === Platform ===
    Last reset 00:02:11 ago, cause: power up
    Last software reset details not available
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 31.0, current 31.0, max 31.1
    Supply voltage: min 12.3, current 12.4, max 12.4, under voltage events: 0, over voltage events: 0
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Driver 5: standstill, SG min/max not available
    Driver 6: standstill, SG min/max not available
    Driver 7: standstill, SG min/max not available
    Driver 8: standstill, SG min/max not available
    Driver 9: standstill, SG min/max not available
    Expansion motor(s) stall indication: yes
    Date/time: 2018-10-30 15:54:35
    Slowest loop: 195.02ms; fastest: 106.14ms
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 4, completed moves: 4
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    Heater 0 is on, I-accum = 0.0
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 0 in use
    Movement lock held by null
    http is idle in state(s) 0
    telnet is idle in state(s) 0
    file is idle in state(s) 0
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 196.62ms; fastest: 0.03ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8
    Interface state 5, link 100Mbps full duplex
    === Expansion ===
    DueX I2C errors 3029


  • administrators

    @gizmotronx5000 said in Printer slowly responds to G-code:

    DueX I2C errors 3029

    This + the fact that the endstps on the Duex 5 do not work any more indicates an issue with the I2C circuit. This can be cause by a poor ground between the Duet and the Duet (which hopefully is solved with the thick dort wire between the two. it can also be cause by the ribbon cable which carries those signals. Has that been disturbed?


  • administrators

    New behavior has started as well. Now no LEDs light up on the Duex5 and the servos and endstops no longer work. The stepper motor I have connected to it still works. Is this possibly a loose connection?

    That sounds like the DueX isn't receiving +5V power from the Duet through the ribbon cable. The stepper motor and fan drivers don't use +5V, but the heater and servo drivers do.



  • Unplugging wires and reseating them seems to have fixed it. Thanks!


Log in to reply