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

    Was working, now can't connect to WiFi

    Scheduled Pinned Locked Moved
    General Discussion
    4
    25
    812
    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.
    • Phaedruxundefined
      Phaedrux Moderator @flyeyes
      last edited by

      @flyeyes said in Was working, now can't connect to WiFi:

      tried to send more, but "flagged as spam."

      Try again.

      What error do you get when you try to enter the SSID?

      What do these produce?

      M552
      M552 S-1
      M552 S0
      M552 S1
      M588 S"*"

      Z-Bot CoreXY Build | Thingiverse Profile

      flyeyesundefined 2 Replies Last reply Reply Quote 0
      • flyeyesundefined
        flyeyes @Phaedrux
        last edited by

        @phaedrux

        All of those are in the above messages, but to recap:

        M552 returns "no remembered networks"

        M552 S1 returns many, many lines of no network available

        M552 S0 works as expected

        M588 S"*" erased all of the networks as expected, but I cannot add the SSID and password back. Have tried dozens of times (literally)

        1 Reply Last reply Reply Quote 0
        • flyeyesundefined
          flyeyes @Phaedrux
          last edited by

          @phaedrux

          I did get it to work briefly (just now) while connected to serial (I've been doing the exact same thing dozens of times for days without success) but its still wonky. the WiFi will hook up while I'm connected to serial via USB, but I lose it and it won't connect if I unplug the USB and then power the board up normally.

          I know documentation says to not use USB and an external power supply at the same time, but I did try briefly to get the WiFi going on USB, turn on the printer, and unplug WiFi.

          This worked until I rebooted the board, and no connectivity after that. Got it going again with USB, but can't power cycle without losing connectivity

          1 Reply Last reply Reply Quote 0
          • Phaedruxundefined
            Phaedrux Moderator
            last edited by

            So does it have a saved SSID now or not?

            Does your config.g have a M552 S1?

            The last test would be to see if it will run in standalone WIFI access point mode.

            https://duet3d.dozuki.com/Wiki/M589

            Z-Bot CoreXY Build | Thingiverse Profile

            flyeyesundefined 1 Reply Last reply Reply Quote 0
            • flyeyesundefined
              flyeyes @Phaedrux
              last edited by

              @phaedrux

              Yes, it seems to be working now. I have no idea what I did differently, which bothers me a bit because it worked fine when I first configured it, then after a week quit working, and now it’s working fine as far as I can tell.

              I haven’t done anything differently, but I will watch it for now. If it quits again I’m just going to plug it into the pi or start over with a different board.

              1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator
                last edited by

                Well if we can identify what's wrong or if there is something wrong and it's under warranty you can get it replaced.

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • terbospaghettiundefined
                  terbospaghetti
                  last edited by terbospaghetti

                  I'm having this same problem.

                  I can save and forget networks as long as the wifi module has been set to active with m552 S0, but not with S-1 or S1 modifiers. When I try to check the status of the wifi module with M552 by itself, I consistently get "wifi module is changing modes" until there's an SPI timeout message like the one at the bottom of the excerpt below.

                  I've successfully reinstalled wifiserver.bin twice (i'm doing this over USB with pronterface and a 24vPSU for the board), but this has yielded no changes in anything. If I just let it sit, it'll eventually give me a bunch of these in a row:

                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  WiFi reported error: network scan failed
                  WiFi module is idle
                  Error retrieving WiFi status message: SPI timeout
                  Error retrieving WiFi status message: SPI timeout
                  
                  WiFi module is idle
                  Failed to change WiFi mode: SPI timeout
                  

                  Once the SPI timeout message(s) come, m552 reports that the wifi module is disabled.

                  I know it's not a poor signal issue, as I've tried within a foot or two of the router.

                  Here's my m122 if it helps:

                  >>> M122
                  SENDING:M122
                  === Diagnostics ===
                  RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
                  Board ID: ZJ21Z-NV9RL-D65J0-40KMN-L3X2Z-HFGNV
                  Used output buffers: 1 of 40 (40 max)
                  === RTOS ===
                  Static ram: 102724
                  Dynamic ram: 106504 of which 0 recycled
                  Never used RAM 34476, free system stack 157 words
                  Tasks: NETWORK(ready,7.6%,328) HEAT(notifyWait,0.0%,364) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,1.1%,115) MAIN(running,90.4%,426) IDLE(ready,0.0%,29) AIN(delaying,0.8%,264), total 100.0%
                  Owned mutexes: USB(MAIN)
                  === Platform ===
                  Last reset 00:14:30 ago, cause: software
                  Last software reset at 2022-01-09 18:47, reason: StuckInSpinLoop, Display spinning, available RAM 41956, slot 1
                  Software reset code 0x408f HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043380f BFAR 0xe000ed38 SP 0x20002a4c Task IDLE Freestk 43 ok
                  Stack: 00087e75 000888a8 61000000 a5a5a5a5 00087e75 a5a5a5a5 a5a5a5a5 2000390c 0001676d 20019104 2002ec9c 20002a68 200190fc 00000004 2001e0dc 2001e0dc 20002a68 2001e0d4 00000001 20002ac4 4e49414d 00000000 00000000 00000001 00000001 17c2fb96 00000000
                  Error status: 0x04
                  Error status: 0x04
                  
                  Aux0 errors 0,0,1
                  MCU revision 3, ADC conversions started 870849, completed 870849, timed out 0, errs 0
                  Step timer max interval 597
                  MCU temperature: min 26.1, current 33.1, max 33.3
                  Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
                  Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                  Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0
                  Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0
                  Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0
                  Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0
                  Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0
                  Driver 5: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0
                  Driver 6: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 13591, writes 9, timeouts 0, DMA errors 0
                  Date/time: 1970-01-01 00:00:00
                  Cache data hit count 1789008195
                  Slowest loop: 99.69ms; fastest: 0.12ms
                  === Storage ===
                  Free file entries: 10
                  SD card 0 detected, interface speed: 22.5MBytes/sec
                  SD card longest read time 0.5ms, write time 0.0ms, max retries 0
                  === Move ===
                  DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
                  === MainDDARing ===
                  Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                  === AuxDDARing ===
                  Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                  === Heat ===
                  Bed heaters = 0 -1, chamberHeaters = -1 -1
                  === GCodes ===
                  Segments left: 0
                  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
                  USB is ready with "M122" in state(s) 0
                  Aux is assembling a command in state(s) 0
                  Trigger is idle in state(s) 0
                  Queue is idle in state(s) 0
                  LCD is idle in state(s) 0
                  SBC is idle in state(s) 0
                  Daemon is idle in state(s) 0
                  Aux2 is idle in state(s) 0
                  Autopause is idle in state(s) 0
                  Code queue is empty.
                  === CAN ===
                  Messages queued 7836, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 4354/0/0
                  Tx timeouts 0,0,4353,0,0,3481 last cancelled message type 4514 dest 127
                  === Network ===
                  Slowest loop: 200.13ms; fastest: 0.00ms
                  Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                  HTTP sessions: 0 of 8
                  - WiFi -
                  Network state is disabled
                  WiFi module is disabled
                  Failed messages: pending 0, notready 0, noresp 2
                  Socket states: 0 0 0 0 0 0 0 0
                  
                  Phaedruxundefined 1 Reply Last reply Reply Quote 0
                  • Phaedruxundefined
                    Phaedrux Moderator @terbospaghetti
                    last edited by

                    @terbospaghetti said in Was working, now can't connect to WiFi:

                    I can save and forget networks as long as the wifi module has been set to active with m552 S0, but not with S-1 or S1 modifiers.

                    That's normal.

                    The M587 command will fail if the WiFi module has not yet been taken out of reset. So if the WiFi module has not been started, send M552 S0 to put it in idle mode first.
                    https://duet3d.dozuki.com/Wiki/M587

                    @terbospaghetti said in Was working, now can't connect to WiFi:

                    I consistently get "wifi module is changing modes"

                    Not normal.

                    @terbospaghetti said in Was working, now can't connect to WiFi:

                    I've successfully reinstalled wifiserver.bin twice

                    Have you been able to verify that the correct version is installed with a M122 when the wifi has connected?

                    Z-Bot CoreXY Build | Thingiverse Profile

                    terbospaghettiundefined 1 Reply Last reply Reply Quote 0
                    • terbospaghettiundefined
                      terbospaghetti @Phaedrux
                      last edited by

                      @phaedrux said in Was working, now can't connect to WiFi:

                      Have you been able to verify that the correct version is installed with a M122 when the wifi has connected?

                      Not sure where I would look or what it should say, but the process was successful according to the console in pronterface

                      Phaedruxundefined 1 Reply Last reply Reply Quote 0
                      • Phaedruxundefined
                        Phaedrux Moderator @terbospaghetti
                        last edited by

                        @terbospaghetti said in Was working, now can't connect to WiFi:

                        Not sure where I would look or what it should say,

                        In the M122 report at the end there is a section for wifi

                        - WiFi -
                        Network state is disabled
                        WiFi module is disabled
                        Failed messages: pending 0, notready 0, noresp 2
                        Socket states: 0 0 0 0 0 0 0 0
                        

                        When it's active it would say what wifi server version it's running.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        ddxdesignundefined terbospaghettiundefined 2 Replies Last reply Reply Quote 0
                        • ddxdesignundefined
                          ddxdesign @Phaedrux
                          last edited by

                          @flyeyes @terbospaghetti
                          This kind of thing happened to me and part of my resolution dance, along with a big chain of FW upgrades to current, was in discovering that my modem/router had smashed the 2.4ghz and 5ghz networks into one automode SSID. And the Duet doesn't like 5ghz I think. I had to dig into my router config and force the two networks to separate SSIDs, after which the Duet was much better about seeing the 2.4ghz network even after a restart or a few days switched off. Not perfect, but much better.

                          Maybe looking into that could help.

                          terbospaghettiundefined 1 Reply Last reply Reply Quote 1
                          • terbospaghettiundefined
                            terbospaghetti @ddxdesign
                            last edited by

                            @ddxdesign good thinking, but I've got two discrete networks, one 2.4 and one 5ghz.

                            I tried to post the m122 info that @Phaedrux asked for yesterday but couldn't do it for some reason, maybe I should try again in a moment

                            1 Reply Last reply Reply Quote 0
                            • terbospaghettiundefined
                              terbospaghetti @Phaedrux
                              last edited by

                              @phaedrux here you go, as requested. It will only show idle or "changingmode"
                              Example 1:
                              === Network ===
                              Slowest loop: 1.27ms; fastest: 0.00ms
                              Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                              HTTP sessions: 0 of 8

                              • WiFi -
                                Network state is active
                                WiFi module is idle
                                Failed messages: pending 0, notready 0, noresp 0
                                WiFi firmware version 1.26
                                WiFi MAC address 8c:aa:b5:15:42:25
                                WiFi Vcc 3.39, reset reason Power up
                                WiFi flash size 2097152, free heap 31248
                                Clock register 00002002
                                Socket states: 0 0 0 0 0 0 0 0

                              Example 2:

                              === Network ===
                              Slowest loop: 1.30ms; fastest: 0.00ms
                              Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                              HTTP sessions: 0 of 8
                              - WiFi -
                              Network state is changingMode
                              WiFi module is trying to connect
                              Failed messages: pending 0, notready 0, noresp 0
                              WiFi firmware version 1.26
                              WiFi MAC address 8c:aa:b5:15:42:25
                              WiFi Vcc 3.39, reset reason Power up
                              WiFi flash size 2097152, free heap 28024
                              Clock register 00002002
                              Socket states: 0 0 0 0 0 0 0 0
                              

                              Curiously tho, I can turn on AP mode and get into DWC that way. That would be a great workaround if it worked in the config.g file, but the wiki says that's a no-no.

                              Phaedruxundefined 1 Reply Last reply Reply Quote 0
                              • Phaedruxundefined
                                Phaedrux Moderator @terbospaghetti
                                last edited by

                                @terbospaghetti said in Was working, now can't connect to WiFi:

                                That would be a great workaround if it worked in the config.g file, but the wiki says that's a no-no.

                                Does it say that? I think it says you shouldn't setup the SSID and password params in config.g, but to enable access point mode you'd just have M552 S2 to turn on AP mode.

                                Regardless, it's odd that it works fine in AP mode, but not with the router. That indicates the hardware itself is fine and the problem is some incompatibility with the router or settings.

                                Z-Bot CoreXY Build | Thingiverse Profile

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