Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    WiFi disconnect errors

    Scheduled Pinned Locked Moved
    General Discussion
    15
    79
    11.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ukflyerundefined
      ukflyer
      last edited by

      Not without issuing an M552 S-1 & M552 S1.

      The logs are being taken from MacPronterface which is connected via USB

      1 Reply Last reply Reply Quote 0
      • ukflyerundefined
        ukflyer
        last edited by

        If I had to guess I would say that it is almost as though the Web Server has shutdown rather than the WiFi connection.

        Just started a print which is predicted to run for 2 hours plus so will keep an eye on it.

        1 Reply Last reply Reply Quote 0
        • BMMalundefined
          BMMal
          last edited by

          • A M122 diagnostic report produced when WiFi was connected
          === Diagnostics ===
Used output buffers: 3 of 32 (17 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20beta11 running on Duet WiFi 1.0 + DueX5
Board ID: 08D6M-91AST-L23S4-7JTD8-3S86K-1PX1K
Static ram used: 15488
Dynamic ram used: 98920
Recycled dynamic ram: 280
Stack ram used: 1368 current, 9220 maximum
Never used ram: 7164
Last reset 01:51:24 ago, cause: software
Last software reset reason: User, spinning module GCodes, available RAM 3032 bytes (slot 0)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 2
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 28.0, current 28.2, max 28.7
Supply voltage: min 24.3, current 24.5, max 24.8, under voltage events: 0, over voltage events: 0
Driver 0: ok
Driver 1: ok
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Driver 5: standstill
Driver 6: ok
Driver 7: standstill
Driver 8: standstill
Driver 9: standstill
Expansion motor(s) stall indication: no
Date/time: 2017-12-04 11:26:10
Cache data hit count 4294967295
Slowest main loop (seconds): 0.119764; fastest: 0.000112
=== Move ===
MaxReps: 7, StepErrors: 194, FreeDm: 215, MinFreeDm 159, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 12230, completed moves: 12221
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 0 is on, I-accum = 0.0
Heater 4 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
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 "G1 X163.249 Y162.84 E0.01646" 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 state is running
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.20b10
WiFi MAC address a0:20:a6:16:e6:c6
WiFi Vcc 3.26, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 27952
WiFi IP address 10.0.0.115
WiFi signal strength -29dBm, reconnections 0, sleep mode modem
HTTP sessions: 1 of 8
Socket states: 0 2 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
[[language]]

```- The make and model of your WiFi router
**Asus RT AC56U**
- Does the problem occur mainly (or only) during printing, or does it occur equally frequently when the printer is idle?
**Both but more so when printing**
- When the problem occurs, are you able to reconnect by pressing the Connect button in DWC?
**Rarely. I have been issuing the wifi module reset command from Paneldue as a work around most of the time.**
- If you are unable to connect, are you still able to ping the IP address of the Duet WiFi?
**No. Timesout**
- Anything else that you think may be correlated with disconnections occurring
**It seems that mine is more likely to lose connection if I leave the focus on the Web Control tab in Chrome. I don't know if this is because fewer things are updated when Web Control is not the focus?**

          Duet Ethernet - Most likely the most recent Edge firmware
          Duet X5
          7" Panel Due V2
          Cartesian, 4 Nozzles with Flex3Drives, Heated Chamber, Simple Switch Filament Sensing

          1 Reply Last reply Reply Quote 0
          • KeeganBundefined
            KeeganB
            last edited by

            I get these all the time, but here is a recent longer log both the wifi debugging output and then the M122 from a few mins after the final disconnect.

            [c]WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(808) p->ref == 1
            WiFi: lwip: ../src/src/core/ipv4/ip.c(652) p->ref == 1
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start…
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0
            WiFi: state: 5 -> 2 (7c0)
            WiFi: rm 0
            WiFi: pm close 7
            WiFi reported error: Lost connection, auto reconnecting
            WiFi: reconnect
            WiFi: state: 2 -> 0 (0)
            WiFi: scandone
            WiFi: state: 0 -> 2 (b0)
            WiFi: state: 2 -> 3 (0)
            WiFi: state: 3 -> 5 (10)
            WiFi: add 0
            WiFi: aid 3
            WiFi: cnt
            WiFi:
            WiFi: connected with Virus 2.0, channel 4
            WiFi: dhcp client start...
            WiFi reported error: Auto reconnect succeeded
            WiFi: ip:10.0.1.161,mask:255.255.255.0,gw:10.0.1.1
            WiFi: pm open,type:2 0[/c]

            M122:

            [c]>>> M122
            SENDING:M122
            === Diagnostics ===
            Used output buffers: 3 of 32 (19 max)
            === Platform ===
            RepRapFirmware for Duet WiFi version 1.20beta11 running on Duet WiFi 1.0
            Board ID: 08DDM-9FAM2-LW4SD-6JTF0-3S86N-TLWZX
            Static ram used: 15488
            Dynamic ram used: 97952
            Recycled dynamiWiFi:
            c ram: 1248
            Stack ram used: 4328 current, 9364 maximum
            Never used ram: 7020
            Last reset 142:06:05 ago, cause: power up
            Last software reset reason: User, spinning module GCodes, available RAM 7296 bytes (slot 3)
            Software reset code 0x0003, HFSR 0x00000000, CWiFi: LINK
            FSR 0x00000000, ICSR 0x00400000, BFAR 0xe000edWiFi: xmit: 0
            38, SP 0xffffffff
            Error status: 1
            [ERROR] Error status: 1

            Free file entries: 9
            SD card 0 detected, interface speed: 20.0MBytes/sec
            SD card longest block write time: 35.2ms
            MCU temperature: min 29.3, current 34.3, max 35.4
            Supply voltaWiFi: recv: 0
            ge: min 12.2, current 12.5, max 12.9, under voltage events: 4, over voltage evenWiFi: fw: 0
            ts: 0
            Driver 0: ok
            Driver 1: ok
            Driver 2: ok
            Driver 3: ok
            Driver 4: standstill
            Date/time: 2017-12-04 21:25:50
            Cache data hit count 4294967295
            Slowest main loop (seconds): 0.115WiFi: drop: 0
            319; fastest: 0.000041
            === Move ===
            MaxReps: 5, StepErrors: 0, FreeDm: 127, MinFreeDm 120, MaxWait: 31071115ms, Underruns: 0, 0
            Scheduled moves: 446029, completed moves: 445999
            Bed compensation in use: none
            Bed probe heights: -0.053 -0.047 0.022 0.040 -0.0WiFi: chkerr: 0
            10
            === Heat ===
            Bed heater = 0, chamber heater WiFi: lenerr: 0
            = -1
            Heater 0 is on, I-accum = 0.3
            Heater 1 is on, I-accum = 0.5
            === GCodes ===
            Segments left: 1
            Stack records: 2 allocated, 0 in use
            Movement lock held by null
            http is idle in state(s) 0
            telnet is idle in staWiFi: memerr: 0
            te(s) 0
            file is doing "G1 X-4.645 Y-19.013 E0.14745 F1787.3" in state(s) 0
            serial is ready with "M122" 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.
            NetWiFi: rterr: 0
            work state is running
            WiFi moduWiFi: proterr: 0
            le is connected to access point
            Failed messages: pending 0, notready 0, noresp 0
            WiFi firmware version 1.20b10
            WiFi MAC address 5c:cf:7f:ef:51:6f
            WiFi Vcc 3.38, reset reason Turned on by main processor
            WiFi flash size 419430WiFi: opterr: 0
            4, free heap 28520
            WiFi IP address 10.0.1.161
            WiFi signal stWiFi: err: 0
            rength -46dBm, reconnections 31, sleep mode modem
            HTTP sessions: 1 of 8
            Socket states: 0 0 0 0 0 0 0 0
            Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
            WiFi: cachehit: 0
            WiFi:
            WiFi: ETHARP
            WiFi: xmit: 97
            WiFi: recv: 420
            WiFi: fw: 0
            WiFi: drop: 7246
            WiFi: chkerr: 0
            WiFi: lenerr: 0
            WiFi: memerr: 0
            WiFi: rterr: 0
            WiFi: proterr: 7246
            WiFi: opterr: 0
            WiFi: err: 0
            WiFi: cachehit: 48603
            WiFi:
            WiFi: IP
            WiFi: xmit: 48776
            WiFi: recv: 65007
            WiFi: fw: 0
            WiFi: drop: 0
            WiFi: chkerr: 0
            WiFi: lenerr: 0
            WiFi: memerr: 0
            WiFi: rterr: 0
            WiFi: proterr: 0
            WiFi: opterr: 0
            WiFi: err: 0
            WiFi: cachehit: 0
            WiFi:
            WiFi: IGMP
            WiFi: xmit: 76
            WiFi: recv: 168
            WiFi: drop: 0
            WiFi: chkerr: 0
            WiFi: lenerr: 0
            WiFi: memerr: 0
            WiFi: proterr: 0
            WiFi: rx_v1: 0
            WiFi: rx_group: 0
            WiFi: rx_ge: 21563
            WiFi: recv: 61223
            WiFi: fw: 0
            WiFi: drop: 0
            WiFi: chkerr: 0
            WiFi: lenerr: 0
            WiFi: memerr: 0
            WiFi: rterr: 0
            WiFi: proterr: 0
            WiFi: opterr: 0
            WiFi: err: 0
            WiFi: cachehit: 0[/c]

            Artemis
            Rostock Max v2
            Orion

            1 Reply Last reply Reply Quote 0
            • dc42undefined
              dc42 administrators
              last edited by

              Thanks. It looks like we have two issues, possibly related. We'll have a new build of DuetWiFiServer soon which may resolve one or both of them.

              Duet WiFi hardware designer and firmware engineer
              Please do not ask me for Duet support via PM or email, use the forum
              http://www.escher3d.com, https://miscsolutions.wordpress.com

              1 Reply Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators
                last edited by

                Hi all,

                Please can anyone who is running main firmware 1.20beta10 1.20beta11 and DuetWiFiServer 1.20beta10 and still experiencing WiFi disconnection problems try DuetWiFiServer 1.20b11, available here https://www.dropbox.com/s/ttoa6d9l9d0lrqe/DuetWiFiServer-1.20b11.bin?dl=1.

                As before, if possible connect a PC running a host program via USB too and send M111 S1 P14 to enable WiFi module debugging.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                1 Reply Last reply Reply Quote 0
                • darookeeundefined
                  darookee
                  last edited by

                  After installing DuetWifiServer 1.20b11 I could not connect to the Duet over Wifi and got these messages in Repetier-Host:

                  13:24:06.852 : WiFi: Fatal exception (0):
13:24:06.864 : WiFi: epc1=0x40100004, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
13:24:06.868 : WiFi: Fatal exception (0):
13:24:06.880 : WiFi: epc1=0x40100004, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
13:24:06.882 : WiFi: Fatal exception (0):
13:24:06.895 : WiFi: epc1=0x40100004, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000

                  Reverting to DuetWifiServer 1.20b10 for now…

                  I'm running "Firmware Version 1.20beta11 (2017-11-28)", could this be the issue? I did realize too late that you said '...running 1.20beta10...' 😐

                  1 Reply Last reply Reply Quote 0
                  • KeeganBundefined
                    KeeganB
                    last edited by

                    @dc42:

                    Hi all,

                    Please can anyone who is running main firmware 1.20beta10 1.20beta11 and DuetWiFiServer 1.20beta10 and still experiencing WiFi disconnection problems try DuetWiFiServer 1.20b11, available here https://www.dropbox.com/s/ttoa6d9l9d0lrqe/DuetWiFiServer-1.20b11.bin?dl=1.

                    As before, if possible connect a PC running a host program via USB too and send M111 S1 P14 to enable WiFi module debugging.

                    I can test this tonight. Thanks.

                    Artemis
                    Rostock Max v2
                    Orion

                    1 Reply Last reply Reply Quote 0
                    • dc42undefined
                      dc42 administrators
                      last edited by

                      @darookee, thanks for your report. I meant DuetWiFiFirmware 1.20beta11, not beta 10.

                      Please can you try installing the new DuetWiFiserver file twice (i.e. send M997 S1 from USB or PanelDue after installing it the first time), in case the problem is the same as the one we had earlier.

                      EDIT - I am about to generate a slightly modified version of the new DWS. Please wait for that version.

                      Duet WiFi hardware designer and firmware engineer
                      Please do not ask me for Duet support via PM or email, use the forum
                      http://www.escher3d.com, https://miscsolutions.wordpress.com

                      1 Reply Last reply Reply Quote 0
                      • dc42undefined
                        dc42 administrators
                        last edited by

                        Please try this version https://www.dropbox.com/s/u7vpp2wg4rlqs8l/DuetWiFiServer.bin?dl=1 installing it twice if necessary.

                        EDIT: Scratch that, I need to do some more work on it.

                        Duet WiFi hardware designer and firmware engineer
                        Please do not ask me for Duet support via PM or email, use the forum
                        http://www.escher3d.com, https://miscsolutions.wordpress.com

                        1 Reply Last reply Reply Quote 0
                        • BMMalundefined
                          BMMal
                          last edited by

                          So far 1.20 beta 11 seems better for me. I'm going to try printing with it. I know you're doing more work but just figured I'd give it a try since I already have it installed. I have not had any issues with having to install the server twice in order to get things working.

                          Been printing for an hour now with 1.20 beta 11 and no disconnects.

                          Duet Ethernet - Most likely the most recent Edge firmware
                          Duet X5
                          7" Panel Due V2
                          Cartesian, 4 Nozzles with Flex3Drives, Heated Chamber, Simple Switch Filament Sensing

                          1 Reply Last reply Reply Quote 0
                          • dc42undefined
                            dc42 administrators
                            last edited by

                            Thanks for the feedback!

                            Duet WiFi hardware designer and firmware engineer
                            Please do not ask me for Duet support via PM or email, use the forum
                            http://www.escher3d.com, https://miscsolutions.wordpress.com

                            1 Reply Last reply Reply Quote 0
                            • darookeeundefined
                              darookee
                              last edited by

                              @dc42 I was away for the weekend and could not try again until now. It now installed without a problem through the WebUI at first try.

                              1 Reply Last reply Reply Quote 0
                              • dc42undefined
                                dc42 administrators
                                last edited by

                                Please can everyone following this thread try DuetWiFiFirmware 1.20RC4 with DuetWiFiserver 1.20RC1 and report back. The files are here https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-WiFi/Edge. Note, after installing the new wifi firmware, you may need to power down/up and/or install DuetWiFiServer a second time (by sending M997 S1 from USB or PanelDue) before you can get a connection.

                                Duet WiFi hardware designer and firmware engineer
                                Please do not ask me for Duet support via PM or email, use the forum
                                http://www.escher3d.com, https://miscsolutions.wordpress.com

                                1 Reply Last reply Reply Quote 0
                                • darookeeundefined
                                  darookee
                                  last edited by

                                  Just did a 2h print without WiFi issues and the printer was up for at ~24h without any WiFi related interruptions. Looks good so far, but my 'no connection' errors occured pretty randomly 😐

                                  1 Reply Last reply Reply Quote 0
                                  • KeeganBundefined
                                    KeeganB
                                    last edited by

                                    Ok, so before updating to the latest RC firmwares, I was still running 1.20 beta 10 (I believe), but I did just put in a new router! This is the 3rd router I have tried using. This one is a Netgear Orbi mesh network with 1 base router and two satellites.

                                    I continued to get the frequent and random disconnects, BUT with this new router I can click connect in DWC and it has reconnected every single time. This is a huge improvement.

                                    I just updated to the latest RC firmwares, so now I will test some more.

                                    Artemis
                                    Rostock Max v2
                                    Orion

                                    1 Reply Last reply Reply Quote 0
                                    • KeeganBundefined
                                      KeeganB
                                      last edited by

                                      Artemis
                                      Rostock Max v2
                                      Orion

                                      1 Reply Last reply Reply Quote 0
                                      • KeeganBundefined
                                        KeeganB
                                        last edited by

                                        and now, even after a power cycle, DWC won't connect at all.

                                        EDIT: For some reason, after 2 power cycles the wifi module was just sitting idle. M552 S1 worked and it is connected (at least for now), but why wouldn't the M552 S1 in the config.g start the module on power up?

                                        Artemis
                                        Rostock Max v2
                                        Orion

                                        1 Reply Last reply Reply Quote 0
                                        • dc42undefined
                                          dc42 administrators
                                          last edited by

                                          There is something about the wifi module starting up when the firmware has just been changed from the old SDK to the new one, which seems to take a few resets to sort out.

                                          Duet WiFi hardware designer and firmware engineer
                                          Please do not ask me for Duet support via PM or email, use the forum
                                          http://www.escher3d.com, https://miscsolutions.wordpress.com

                                          1 Reply Last reply Reply Quote 0
                                          • KeeganBundefined
                                            KeeganB
                                            last edited by

                                            Ok, thats good to hear. As a positive update, it has stayed connected with NO ISSUES since I manually started the module up. I also changed the channels on the router from what they were (neither were channel 1, or others that i have seen reported as possibly problematic).

                                            Everything seems to be going well right now. I will continue testing.

                                            Artemis
                                            Rostock Max v2
                                            Orion

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA