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

    Duet Wifi problems after update to RRF3. HTTP resquest timed out

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    5
    250
    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.
    • FelixHundefined
      FelixH
      last edited by FelixH

      Hi all,

      I have a Duet-powered CNC machine (Ooznest's Workbee). I have a PanedDue display and a CNC Pendant. Everything worked just fine.

      Yesterday I updated to the latest firmware the folks at Ooznest have released. I am not expert, but I would say the firmware per se is the RRF3 and they only tweak the web environment a little bit.

      Since the update I am not able to have an stable connection to the Duet. It keeps reloading and a message tells me something like:

      Connection Fail: HTTP request timed out
      

      I have seen a post from a user who experience similar issues but, in his case it seemed to be related to the DNS cache and he solved it by flushing it. I tried it right now, but it keeps disconnecting.

      Additional info:

      • on the PanelDue display, it shows a stable connection to the WiFi. No connect / disconnect
      • I tried to reinstall DuetWiFiServer.bin (or whatever it is actually called). The problem persists.
      • On the PanelDue a warning is displayet at boot up, which reads: Error: Bad Command: N10 M409 k"network" F"v"*26

      I would appreciate any help, since I cannot use the machine if this issue is not solved...

      Thanks in advance

      EDIT: I am at a lost here. I don't understand what's happening. I just checked with some of my other Duet machines (3D Printers) and, for whatever reason, all machines show the above behavior... all of the sudden! A few days ago I printed something with one of these and I had no problem at all!

      At home I have a Linksys Mesh system. Any help would be appreciated!

      resamundefined 1 Reply Last reply Reply Quote 0
      • resamundefined
        resam @FelixH
        last edited by

        @felixh what does M552 tell you? it should be an IP address in your network. Can you connect to this one?

        1 Reply Last reply Reply Quote 0
        • FelixHundefined
          FelixH
          last edited by

          @resam Thanks! As far as I know the system reports no problems. From that point of view, everything is ok.

          I rebooted all of the Linksys nodes and tried again. It seems that it is working now without issues. Go figure! I have no idea what could have been wrong...

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

            Can you share the results of M122? The main firmware should be 3.3 and the wifi server should be 1.26

            Z-Bot CoreXY Build | Thingiverse Profile

            FelixHundefined 1 Reply Last reply Reply Quote 0
            • FelixHundefined
              FelixH @Phaedrux
              last edited by

              @phaedrux sure thing:

              M122
              === Diagnostics ===
              RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
              Board ID: 08DGM-917DA-G4MS8-6JKDA-3SJ6T-T8VH8
              Used output buffers: 3 of 24 (17 max)
              === RTOS ===
              Static ram: 23876
              Dynamic ram: 75280 of which 0 recycled
              Never used RAM 12404, free system stack 172 words
              Tasks: NETWORK(ready,13.6%,237) LASER(notifyWait,0.0%,70) HEAT(delaying,0.0%,386) Move(notifyWait,0.1%,364) MAIN(running,86.3%,519) IDLE(ready,0.0%,29), total 100.0%
              Owned mutexes: WiFi(NETWORK)
              === Platform ===
              Last reset 00:53:43 ago, cause: power up
              Last software reset at 2021-12-04 17:24, reason: User, GCodes spinning, available RAM 12604, slot 1
              Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
              Error status: 0x00
              Aux0 errors 0,0,0
              Step timer max interval 0
              MCU temperature: min 20.5, current 23.2, max 24.4
              Supply voltage: min 24.1, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
              Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/24/0, gc cycles 0
              Driver 0: position 0, standstill, SG min/max not available
              Driver 1: position 0, standstill, SG min/max not available
              Driver 2: position 0, standstill, SG min/max not available
              Driver 3: position 0, standstill, SG min/max not available
              Driver 4: position 0, standstill, SG min/max not available
              Driver 5: position 0
              Driver 6: position 0
              Driver 7: position 0
              Driver 8: position 0
              Driver 9: position 0
              Driver 10: position 0
              Driver 11: position 0
              Date/time: 2021-12-04 18:43:48
              Cache data hit count 4294967295
              Slowest loop: 30.98ms; fastest: 0.17ms
              I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
              === Storage ===
              Free file entries: 10
              SD card 0 detected, interface speed: 20.0MBytes/sec
              SD card longest read time 1.2ms, write time 15.9ms, 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 = -1 -1 -1 -1, chamberHeaters = -1 -1 -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 idle in state(s) 0
              Aux is idle 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
              Daemon is idle in state(s) 0
              Autopause is idle in state(s) 0
              Code queue is empty.
              === Network ===
              Slowest loop: 71.59ms; fastest: 0.00ms
              Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
              HTTP sessions: 1 of 8
              - WiFi -
              Network state is active
              WiFi module is connected to access point 
              Failed messages: pending 0, notready 0, noresp 0
              WiFi firmware version 1.26
              WiFi MAC address bc:dd:c2:9a:4a:85
              WiFi Vcc 3.31, reset reason Turned on by main processor
              WiFi flash size 4194304, free heap 25112
              WiFi IP address 192.168.1.212
              WiFi signal strength -60dBm, mode 802.11n, reconnections 0, sleep mode modem
              Clock register 00002002
              Socket states: 0 0 0 0 0 0 0 0
              
              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Unless otherwise noted, all forum content is licensed under CC-BY-SA