Duet2 Wifi dropping connection often.

  • My duet has started dropping wifi randomly, and taking a minute or two to come back on. I've run M122 after one of these disconnects and got this, which doesn't seem to show an issue:

    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-9568A-F23SJ-6J9FA-3SN6M-TUT7H
    Used output buffers: 1 of 24 (7 max)
    === RTOS ===
    Static ram: 25712
    Dynamic ram: 93176 of which 380 recycled
    Exception stack ram used: 384
    Never used ram: 11420
    Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3800) IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 00:45:43 ago, cause: power up
    Last software reset at 2019-12-25 20:27, reason: User, spinning module GCodes, available RAM 11260 bytes (slot 0)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    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 21.8, current 39.6, max 39.9
    Supply voltage: min 24.3, current 24.5, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes
    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
    Date/time: 2019-12-26 15:09:22
    Cache data hit count 4294967295
    Slowest loop: 7.44ms; fastest: 0.06ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0, FreeDm: 160, MinFreeDm: 158, MaxWait: 278441ms
    Bed compensation in use: none, comp offset 0.000
    === DDARing ===
    Scheduled moves: 12, completed moves: 12, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === 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 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: 15.38ms; fastest: 0.00ms
    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 0
    WiFi firmware version 1.23
    WiFi MAC address REDACTED
    WiFi Vcc 3.38, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 25024
    WiFi IP address 192.168.1.REDACTED
    WiFi signal strength -50dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0

  • please go through this list step by step and report back on each step to help with the troubleshooting.

  • I've done all of the steps on that post, except the minimum ajax retries, as I can't find it in DWC2.0.4. I've changed my router's 2.4 ghz band to 6, and the board has line of sight with the router. Since the band change, I'm seeing -45db for signal, so that's not it. Also, I'm not seeing ajax errors anywhere, just "Connection interrupted, attempting to reconnect...
    Network error"

  • Also, seems to be happening every 3ish minutes and lasting 60 seconds before it reconnects

  • administrators

    Could it be an IP address conflict? Does either the Duet or anything else on your network use a static IP address?

  • @dc42 In the past with a different router, I had assigned an IP address to the duet on the router side, but never assigned a static ip on the board. AFAIK, nothing on my network uses a static IP, considering my subnet went from 10.0.0.x to 192.168.1.x on this new router, and I haven't had anything not connect to it. Should I maybe try a static IP?

Log in to reply