Duet Web Control Unresponsive

  • I've been having problems with the Duet Web Control since upgrading from 2.04 to 2.05.1 not responding. It seems to be okay until I perform a print. After I have trouble getting anything to respond unless I refresh the web page/session. I've been primarily using Chrome to access the site.

    When using /reprap.htm I have no problems, so I believe it may just be a problem with the HTML.

    When the problem occurs I have these issues:
    After a print I cannot upload another, I receive an error and cannot upload.
    Click on the Console, I cannot get a response from G-Code. The "Send" button will change to the twirling circle and never come back.
    When attempting to change the temps on heaters I can typically get my first command to respond, but subsequent actions do not occur. If attempting to change temps there will the stretchy action bars showing something is happening, but never stop.

    Duet Web Control 2.0.7
    Board: Duet WiFi 1.02 or later + DueX5
    Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05.1 (2020-02-09b1)
    Duet WiFi Server Version: 1.23

    Any suggestions / known issues?

  • Moderator

    @Gamefanatic3D When it happens next time, can you connect via USB, open a serial console (eg YAT) and send M122? This should report what's going on. Post the M122 output into your reply.


  • After a print, I made another print and attempted to upload from a Chrome browser. The upload button shows "UPOLOADING" with the circle spinning. Waiting long enough I hear the printer starting in the background...

    I had the reprap interface opened in Internet Explorer prior so I performed the M122 and got this output:

    ‎3‎:‎56‎:‎57‎ ‎PM
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later + DueX5
    Board ID: 08DGM-9T6BU-FG3S8-6J1F8-3SJ6S-1BL7H
    Used output buffers: 3 of 24 (22 max)
    === RTOS ===
    Static ram: 25712
    Dynamic ram: 94472 of which 0 recycled
    Exception stack ram used: 544
    Never used ram: 10344
    Tasks: NETWORK(ready,628) HEAT(blocked,1176) DUEX(suspended,160) MAIN(running,1664) IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 02:50:34 ago, cause: software
    Last software reset at 2020-02-22 13:06, reason: User, spinning module GCodes, available RAM 10280 bytes (slot 1)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 17.5ms, max retries 0
    MCU temperature: min 40.4, current 40.6, max 44.5
    Supply voltage: min 12.2, current 12.4, max 12.5, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max 0/1023
    Driver 1: standstill, SG min/max 0/487
    Driver 2: standstill, SG min/max 0/129
    Driver 3: standstill, SG min/max 0/72
    Driver 4: standstill, SG min/max 0/113
    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
    Date/time: 2020-02-22 15:56:56
    Cache data hit count 4294967295
    Slowest loop: 225.21ms; fastest: 0.08ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0, FreeDm: 160, MinFreeDm: 121, MaxWait: 17ms
    Bed compensation in use: mesh, comp offset 0.000
    === DDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    Heater 0 is on, I-accum = 0.2
    Heater 1 is on, I-accum = 0.6
    === GCodes ===
    Segments left: 0
    Stack records: 2 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 doing "M190 S70.00" 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: 200.33ms; fastest: 0.08ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8
    - WiFi -
    Network state is running
    WiFi module is connected to access point 
    Failed messages: pending 0, notready 0, noresp 1
    WiFi firmware version 1.23
    WiFi MAC address cc:50:e3:14:e3:17
    WiFi Vcc 3.33, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 25144
    WiFi IP address
    WiFi signal strength -47dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    === Filament sensors ===
    Extruder 0: pos 188.09, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
    Extruder 1 sensor: ok

    Refreshing the Chrome browser returns control for a while longer.

  • I just went ahead and updated to 3.0 (2020-01-03b3) and everything is working so far. Probably just a bug or bad update, because it was working before and after the 2.05.1 update.

Log in to reply