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

    Please help: Duet Wifi stuck on Wifi Idle, No Networks, etc

    Scheduled Pinned Locked Moved
    General Discussion
    4
    37
    1.3k
    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.
    • ddxdesignundefined
      ddxdesign @jay_s_uk
      last edited by

      @jay_s_uk No USB, it's all through the panel due. SeeMe says they do not recommend connecting to this machine through USB - to do everything from the panel. Running 2.02 FW (12/24/18). That's odd because I got the machine brand new 8 mos ago, but then again maybe their machines use older FW on purpose (assuming there have been new FWs in the ensuing time)

      SIamundefined jay_s_ukundefined 2 Replies Last reply Reply Quote 1
      • SIamundefined
        SIam @ddxdesign
        last edited by SIam

        @ddxdesign said in Please help: Duet Wifi stuck on Wifi Idle, No Networks, etc:

        SeeMe says they do not recommend connecting to this machine through USB

        and this is why : https://duet3d.dozuki.com/Wiki/USB_ground_loops

        if you disconnect your printer from mains, you can connect the USB cable to use YAT (the duet board will be powered by the USB connection)

        Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
        Duet WiFi 1.02 or later + DueX5
        RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
        Duet WiFi Server: 1.26
        Duet Web Control 3.4.0beta4 (2021-09-27)

        ddxdesignundefined 1 Reply Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk @ddxdesign
          last edited by

          @ddxdesign there's no issues with connecting to the board through USB. Would definitely make it easier to get an output from things.
          The paneldue is good but can make general troubleshooting difficult.
          As @SIam pointed out, ground loops are the main issue but if you use a laptop powered from the battery (not on charge) you are perfectly fine.

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          1 Reply Last reply Reply Quote 0
          • ddxdesignundefined
            ddxdesign @SIam
            last edited by

            @siam Hmm; where my printer is, I would have to use my laptop on battery to get to anyways, so maybe this isn't a concern?

            jay_s_ukundefined 1 Reply Last reply Reply Quote 1
            • jay_s_ukundefined
              jay_s_uk @ddxdesign
              last edited by

              @ddxdesign definitely not a concern.
              Would make the troubleshooting easier

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              ddxdesignundefined 1 Reply Last reply Reply Quote 0
              • ddxdesignundefined
                ddxdesign @jay_s_uk
                last edited by

                @jay_s_uk OK let me see if I can remember how to use Yat...

                ddxdesignundefined 1 Reply Last reply Reply Quote 2
                • ddxdesignundefined
                  ddxdesign @ddxdesign
                  last edited by ddxdesign

                  @jay_s_uk Alrighty, from YAT the full M122 output is:

                  === Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later<LF>Board ID: 08DLM-996RU-N85S4-7JKF4-3SN6P-TU97R<LF>Used output buffers: 1 of 20 (13 max)<LF>=== RTOS ===<LF>Static ram: 25524<LF>Dynamic ram: 98864 of which 0 recycled<LF>Exception stack ram used: 432<LF>Never used ram: 6252<LF>Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3636) IDLE(ready,200)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 69:35:24 ago, cause: power up<LF>Last software reset at 2021-08-22 09:46, reason: User, spinning module GCodes, available RAM 6212 bytes (slot 3)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 8<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 40.4, current 40.6, max 41.6<LF>Supply voltage: min 13.0, current 13.1, max 13.1, under voltage events: 0, over voltage events: 0, p[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]

                  jay_s_ukundefined 1 Reply Last reply Reply Quote 1
                  • ddxdesignundefined
                    ddxdesign
                    last edited by ddxdesign

                    I did just discover some new-firmware instructions from seemecnc; I will have to allocate a big chunk of time to trying this I think. EDIT: Sigh, have to go buy an SD-to-USB thing.

                    1 Reply Last reply Reply Quote 1
                    • jay_s_ukundefined
                      jay_s_uk @ddxdesign
                      last edited by

                      @ddxdesign you need to increase the end of line settings to get the full output.
                      If you have a look at that link I posted a few pages up, it tells you all the settings you need to change in YAT

                      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                      ddxdesignundefined 1 Reply Last reply Reply Quote 0
                      • ddxdesignundefined
                        ddxdesign @jay_s_uk
                        last edited by ddxdesign

                        @jay_s_uk Well, did that, but now when I paste in the true full output, I can't post it - forum gives me a Flagged As Spam error...

                        SIamundefined 1 Reply Last reply Reply Quote 2
                        • SIamundefined
                          SIam @ddxdesign
                          last edited by

                          @ddxdesign said in Please help: Duet Wifi stuck on Wifi Idle, No Networks, etc:

                          @jay_s_uk Well, did that, but now when I paste in the true full output, I can't post it - forum gives me a Flagged As Spam error...

                          please try it again now

                          Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
                          Duet WiFi 1.02 or later + DueX5
                          RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
                          Duet WiFi Server: 1.26
                          Duet Web Control 3.4.0beta4 (2021-09-27)

                          ddxdesignundefined 1 Reply Last reply Reply Quote 0
                          • ddxdesignundefined
                            ddxdesign @SIam
                            last edited by

                            @siam Alrighty, how's this?

                            === Diagnostics ===
                            RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
                            Board ID: 08DLM-996RU-N85S4-7JKF4-3SN6P-TU97R
                            Used output buffers: 1 of 20 (4 max)
                            === RTOS ===
                            Static ram: 25524
                            Dynamic ram: 98820 of which 0 recycled
                            Exception stack ram used: 424
                            Never used ram: 6304
                            Tasks: NETWORK(ready,1260) HEAT(suspended,1232) MAIN(running,3788) IDLE(ready,200)
                            Owned mutexes:
                            === Platform ===
                            Last reset 00:44:43 ago, cause: software
                            Last software reset time unknown, reason: Heat task stuck, spinning module FilamentSensors, available RAM 6024 bytes (slot 0)
                            Software reset code 0x00ad HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f80f BFAR 0xe000ed38 SP 0x20004a54 Task 0x4e49414d
                            Stack: 0044bcc7 004495f2 21000000 00000000 00000000 00000000 00000000 3e178897 3e1cd04f 41800000 3e3a4b83 3e63a760 3e92581f 3ccd4e65 3eccdf1a 3e221bcd 3f800000 c0a00000 00000000 60000010 e000ed04 20004ad0 00000000
                            Error status: 1
                            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 40.4, current 40.9, max 41.8
                            Supply voltage: min 13.0, current 13.1, max 13.3, 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: 1970-01-01 00:00:00
                            Cache data hit count 4294967295
                            Slowest loop: 1.21ms; fastest: 0.07ms
                            I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
                            === Move ===
                            Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
                            Scheduled moves: 0, completed moves: 0
                            Bed compensation in use: mesh
                            Bed probe heights: 0.000 0.000 0.000 0.000 0.000
                            === 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 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.
                            === Network ===
                            Slowest loop: 1.30ms; fastest: 0.00ms
                            Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
                            HTTP sessions: 0 of 8

                            • WiFi -
                              Network state is disabled
                              WiFi module is disabled
                              Failed messages: pending 0, notready 0, noresp 0
                              Socket states: 0 0 0 0 0 0 0 0
                              ok
                            ddxdesignundefined jay_s_ukundefined 2 Replies Last reply Reply Quote 0
                            • ddxdesignundefined
                              ddxdesign @ddxdesign
                              last edited by

                              BTW network/wifi is disabled now just cause I stopped the module so it wouldn't flood the screen with errors any more

                              1 Reply Last reply Reply Quote 0
                              • jay_s_ukundefined
                                jay_s_uk @ddxdesign
                                last edited by

                                @ddxdesign ok, that's a good first step.
                                Can you try enabling the WiFi module using M552 S0 and then post the output of just the WiFi section from M122?

                                Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                                ddxdesignundefined 1 Reply Last reply Reply Quote 0
                                • ddxdesignundefined
                                  ddxdesign @jay_s_uk
                                  last edited by ddxdesign

                                  @jay_s_uk OK here you go:

                                  • WiFi -
                                    Network state is running
                                    WiFi module is idle
                                    Failed messages: pending 0, notready 0, noresp 0
                                    WiFi firmware version 1.22
                                    WiFi MAC address f4:cf:a2:66:97:85
                                    WiFi Vcc 3.38, reset reason Turned on by main processor
                                    WiFi flash size 4194304, free heap 33632
                                    Socket states: 0 0 0 0 0 0 0 0
                                    ok

                                  EDIT: when I run M587 now it looks like at least it remembers my current network as part of the known networks list, but it won't connect or anything still.

                                  jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                                  • jay_s_ukundefined
                                    jay_s_uk @ddxdesign
                                    last edited by

                                    @ddxdesign can you try this WiFi firmware here?
                                    https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/DuetWiFiServer-1.23.bin
                                    I believe it should work ok.
                                    You will need to place it in the sys folder of the SD card.
                                    Take a backup of the one already there (in fact, backup all the SD card contents just in case).
                                    Then put the SD card back in, power up the board and using YAT, send M997 S1.
                                    Once flashed send M552 S0
                                    Then M558 S"*"
                                    Then M587... With your WiFi details.
                                    Hopefully that sends ok, then use M552 S1 to activate the WiFi

                                    Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                                    ddxdesignundefined 1 Reply Last reply Reply Quote 0
                                    • ddxdesignundefined
                                      ddxdesign @jay_s_uk
                                      last edited by

                                      @jay_s_uk Yeah I know SeeMe has instructions for updating the RR FW itself but I couldn't see mention of the Wifi FW. Either way I will have to go out and buy an SD card reader with a USB plug. My new laptop is supposed to be fancy (for gaming) but has no SD port...

                                      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                                      • jay_s_ukundefined
                                        jay_s_uk @ddxdesign
                                        last edited by

                                        @ddxdesign thats a shame.
                                        well when you are ready or need any more help just drop a message here.
                                        If they give you instructions for upgrading the firmware to 2.05.1 then go through with that too.

                                        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                                        ddxdesignundefined 1 Reply Last reply Reply Quote 0
                                        • ddxdesignundefined
                                          ddxdesign @jay_s_uk
                                          last edited by

                                          @jay_s_uk the instructions I found as of August of this year are to take the RRFW up to 3.2.2 but I just went through them again and nothing about the wifi FW. So hopefully the two won't clash and I can do it all.

                                          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                                          • jay_s_ukundefined
                                            jay_s_uk @ddxdesign
                                            last edited by

                                            @ddxdesign ah, if going to 3.2.2 then you will need 1.25 of the wifi firmware which can be found here https://github.com/Duet3D/DuetWiFiSocketServer/releases/download/1.25/DuetWiFiServer.bin
                                            I'm assuming they provide new config files etc? as a fair amount of syntax changed between RRF2 and RRF3

                                            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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