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

    Trigger wifi reconnect during long print

    Scheduled Pinned Locked Moved
    Duet Web Control
    3
    11
    629
    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.
    • dc42undefined
      dc42 administrators
      last edited by dc42

      Assuming you are running recent versions of RRF and DuetWiFiServer, the Duet continuously tries to reconnect if it loses the connection.

      If for some reason it keeps failing to reconnect, then you could try resetting the wifi module (M552 S-1) followed by restarting it (M552 S1 assuming you run it in client mode). You could do this in a macro, commanded from a PanelDue or from a trigger.

      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
      • clytle374undefined
        clytle374
        last edited by clytle374

        It was updated to latest version end of November or December. It's been much better recently.

        Can this be done through USB?

        Wifi light is off, not blinking, just off

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

          @clytle374 said in Trigger wifi reconnect during long print:

          Can this be done through USB?

          Yes, you can send those 2 commands via USB.

          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
          • droftartsundefined
            droftarts administrators @clytle374
            last edited by

            @clytle374 said in Trigger wifi reconnect during long print:

            It was updated to latest version end of November or December. It's been much better recently

            You may be on 2.04, or one of the 2.05RC releases. Best to update to 2.05 release: https://github.com/dc42/RepRapFirmware/releases/tag/2.05
            @dc42 put in a lot of work to resolve the wifi disconnection issues. When you are next able to connect, please can you send M122 and post the response.

            Ian

            Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

            1 Reply Last reply Reply Quote 0
            • clytle374undefined
              clytle374
              last edited by

              I'm back online, here's the version info

              RepRapFirmware for Duet 2 WiFi/Ethernet 2.05 (2019-12-13b1)
              Duet WiFi Server Version: 1.23
              
              Duet Web Control 2.0.4
              
              

              Can I run M122 while printing?

              droftartsundefined 1 Reply Last reply Reply Quote 0
              • droftartsundefined
                droftarts administrators @clytle374
                last edited by

                @clytle374 Yes, it should be okay to run M122 when printing!

                Ian

                Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                clytle374undefined 1 Reply Last reply Reply Quote 0
                • clytle374undefined
                  clytle374 @droftarts
                  last edited by

                  @droftarts

                  M122 output

                  M122
                  === Diagnostics ===
                  RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.02 or later
                  Board ID: 08DGM-917DA-G4MSJ-6JKDA-3SN6N-KSRB9
                  Used output buffers: 6 of 24 (16 max)
                  === RTOS ===
                  Static ram: 25712
                  Dynamic ram: 92584 of which 416 recycled
                  Exception stack ram used: 512
                  Never used ram: 11848
                  Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3800) IDLE(ready,160)
                  Owned mutexes: WiFi(NETWORK)
                  === Platform ===
                  Last reset 09:57:05 ago, cause: reset button or watchdog
                  Last software reset at 2019-12-30 07:03, reason: User, spinning module GCodes, available RAM 12088 bytes (slot 1)
                  Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
                  Error status: 12
                  Free file entries: 9
                  SD card 0 detected, interface speed: 20.0MBytes/sec
                  SD card longest block write time: 7.6ms, max retries 0
                  MCU temperature: min 42.3, current 42.6, max 42.9
                  Supply voltage: min 11.6, current 12.1, max 12.3, under voltage events: 0, over voltage events: 0, power good: yes
                  Driver 0: ok, SG min/max 0/395
                  Driver 1: ok, SG min/max 0/415
                  Driver 2: ok, SG min/max 0/414
                  Driver 3: ok, SG min/max not available
                  Driver 4: standstill, SG min/max not available
                  Date/time: 2020-01-08 12:35:31
                  Cache data hit count 4294967295
                  Slowest loop: 14.02ms; fastest: 0.07ms
                  I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                  === Move ===
                  Hiccups: 0, FreeDm: 156, MinFreeDm: 108, MaxWait: 0ms
                  Bed compensation in use: none, comp offset 0.000
                  === DDARing ===
                  Scheduled moves: 724836, completed moves: 724801, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
                  === Heat ===
                  Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
                  Heater 0 is on, I-accum = 0.1
                  Heater 1 is on, I-accum = 0.6
                  === GCodes ===
                  Segments left: 1
                  Stack records: 1 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 F3600.000" 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.31ms; fastest: 0.08ms
                  Responder states: HTTP(0) HTTP(0) HTTP(1) 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:0d:22:c1
                  WiFi Vcc 3.35, reset reason Turned on by main processor
                  WiFi flash size 4194304, free heap 22792
                  WiFi IP address 192.168.0.13
                  WiFi signal strength -51dBm, reconnections 0, sleep mode modem
                  Socket states: 0 0 2 0 0 0 0 0
                  
                  droftartsundefined 1 Reply Last reply Reply Quote 0
                  • clytle374undefined
                    clytle374
                    last edited by

                    If I'm reading this properly I'm on the latest firmware.
                    Thanks
                    Cory

                    1 Reply Last reply Reply Quote 0
                    • droftartsundefined
                      droftarts administrators @clytle374
                      last edited by

                      @clytle374 said in Trigger wifi reconnect during long print:

                      Error status: 12

                      Referring to Error_codes_and_software_reset_codes this means:

                      0x04 Output buffer starvation
                      0x08 Output stack overflow

                      RRF 2.04 and 2.05 had changes to fix most instances of these. I've referred this thread to @dc42 to have a look at.

                      Ian

                      Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                      clytle374undefined 1 Reply Last reply Reply Quote 0
                      • clytle374undefined
                        clytle374 @droftarts
                        last edited by clytle374

                        @droftarts

                        My internet in the building with the printer is a special kind of horrible, the main DSL hasn't been much better. I've spent the last 2 days working on the system. Fixed DSL, I think. Ran ethernet to building and removing the cheap wifi booster out here.

                        I've changed the wifi name and password in the config.g file on the duet. But it's still connecting to the old wifi. How do I get it to change over?
                        NEVERMIND: That was way harder than it should be.
                        Thanks
                        Cory

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