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

    duet wifi connection issues

    Scheduled Pinned Locked Moved
    Firmware installation
    3
    17
    2.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.
    • IanWaltonundefined
      IanWalton @dc42
      last edited by

      @dc42

      SENDING:M122
      === Diagnostics ===
      Used output buffers: 1 of 32 (1 max)
      === Platform ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
      Board ID: 08DDM-9FAM2-LW4S4-6J1D8-3SD6R-T3SZX
      Static ram used: 16152
      Dynamic ram used: 100448
      Recycled dynamic ram: 2184
      Stack ram used: 3576 current, 4528 maximum
      Never used ram: 7760
      Last reset 00:00:21 ago, cause: software
      Last software reset time unknown, reason: User, spinning module GCodes, available RAM 7864 bytes (slot 3)
      Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
      Error status: 0
      Free file entries: 10
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest block write time: 0.0ms
      MCU temperature: min 31.6, current 31.9, max 32.0
      Supply voltage: min 12.2, current 12.3, max 12.3, under voltage events: 0, over voltage events: 0
      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
      Slowest main loop (seconds): 0.000259; fastest: 0.000049
      === Move ===
      MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
      Scheduled moves: 0, completed moves: 0
      Bed compensation in use: none
      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: 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 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 ===
      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 starting
        WiFi module is disabled
        Failed messages: pending 0, notready 0, noresp 0
        Socket states: 0 0 0 0 0 0 0 0
        === Expansion ===

      network state is starting
      wifi module is disabled

      hmmm, ive got a spare sd card somewhere, going to try reformatting it and starting fresh

      1 Reply Last reply Reply Quote 0
      • IanWaltonundefined
        IanWalton @ayudtee
        last edited by

        @ayudtee

        sigh, im a dumbass, macro wasnt correct name, but, i corrected it and got it to run

        hasnt changed anything though 😞

        1 Reply Last reply Reply Quote 0
        • IanWaltonundefined
          IanWalton @dc42
          last edited by

          @dc42

          config file contents

          ; Configuration file for Duet WiFi ver 1.

          ; General preferences

          G90 ; Send absolute coordinates...
          M83 ; ...but relative extruder moves
          M555 P1 ; Set firmware to look like RepRapFirmare

          ; Network

          M550 PCR10 ; Set machine name
          M552 S1 ; Enable network
          M587 S"PLUSNET-Q6QW" P"xxxxxxxx" ; access point

          ; Drives

          M569 P0 S1 ; Drive 0 goes forwards
          M569 P1 S1 ; Drive 1 goes forwards
          M569 P2 S1 ; Drive 2 goes forwards
          M569 P3 S1 ; Drive 3 goes forwards
          M350 X16 Y16 Z16 E16 I1 ; Configure microstepping
          M92 X80 Y80 Z4000 E420 ; Set steps per mm
          M566 X900 Y900 Z12 E120 ; Set maximum speed changes
          M203 X6000 Y6000 Z180 E1200 ; Set maximum speeds
          M201 X500 Y20 Z250 E250 ; Set accelerations
          M906 X800 Y800 Z800 E800 I30 ; Set motor currents (mA)
          M84 S30 ; Set idle timeout

          ; Axis Limits

          M208 X0 Y0 Z0 S1 ; Set axis minima
          M208 X300 Y300 Z400 S0 ; Set axis maxima

          ; Endstops

          M574 Y2 S1 ; Set active high endstops

          ; Z-Probe
          M574 X1 Z1 S2 ; Set endstops controlled by probe
          M558 P1 H5 F120 T6000 ; Set Z probe type to unmodulated and the dive height + speeds
          G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
          M557 X45:275 Y45:275 S20 ; Define mesh grid

          ; Heaters
          M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
          M143 H0 S120 ; Set temperature limit for heater 0 to 120C
          M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
          M143 H1 S280 ; Set temperature limit for heater 1 to 280C

          ; Fans
          M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
          M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
          M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

          ; Tools
          M563 P0 D0 H1 ; Define tool 0
          G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
          G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

          ; Automatic power saving
          M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

          ; Custom settings are not configured

          ; Miscellaneous
          ;M501 ; Load saved parameters from non-volatile memory

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

            @ianwalton said in duet wifi connection issues:

            WiFi -
            Network state is starting
            WiFi module is disabled

            That bit suggests either an incomplete wifi firmware installation or an incompatible wifi firmware version. I suggest you do this:

            • download DuetWiFiServer.bin again from https://github.com/dc42/RepRapFirmware/releases/tag/1.21
            • use a PC to copy it into /sys on the SD card
            • safely remove/eject the SD card from the PC
            • put it back in the Duet, then start the Duet
            • send M997 S1 from YAT to install it, and check that it reports success
            • send M552 S0. It should respond "WiFi module is idle" after a few seconds.
            • then you can try sending the M587 command again from YAT to set your access point SSID and password.

            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
            • IanWaltonundefined
              IanWalton
              last edited by

              did as you asked
              M997 reported successful upload.
              M552 S0 does not respond

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

                After sending M552 S0, please wait a few seconds, then run M122 and post the result here.

                PS - also try sending M552 S-1 before the M552 S0.

                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
                • IanWaltonundefined
                  IanWalton
                  last edited by

                  M552 S-1returns ''WiFi module stopped''
                  M552 S0 returns nothing

                  M122 returns
                  === Diagnostics ===
                  Used output buffers: 1 of 32 (9 max)
                  === Platform ===
                  RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
                  Board ID: 08DDM-9FAM2-LW4S4-6J1D8-3SD6R-T3SZX
                  Static ram used: 16152
                  Dynamic ram used: 100448
                  Recycled dynamic ram: 2184
                  Stack ram used: 3576 current, 4720 maximum
                  Never used ram: 7568
                  Last reset 01:20:22 ago, cause: reset button or watchdog
                  Last software reset time unknown, reason: User, spinning module GCodes, available RAM 7864 bytes (slot 3)
                  Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
                  Error status: 0
                  Free file entries: 10
                  SD card 0 detected, interface speed: 20.0MBytes/sec
                  SD card longest block write time: 0.0ms
                  MCU temperature: min 31.9, current 32.0, max 32.5
                  Supply voltage: min 12.2, current 12.3, max 12.3, under voltage events: 0, over voltage events: 0
                  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
                  Slowest main loop (seconds): 0.099909; fastest: 0.000050
                  === Move ===
                  MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
                  Scheduled moves: 0, completed moves: 0
                  Bed compensation in use: none
                  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: 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 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 ===
                  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 starting
                    WiFi module is disabled
                    Failed messages: pending 0, notready 0, noresp 0
                    Socket states: 0 0 0 0 0 0 0 0
                    === Expansion ===
                  1 Reply Last reply Reply Quote 0
                  • IanWaltonundefined
                    IanWalton
                    last edited by

                    i did a M122 after the S-1 and the only difference i could see was ''network state is disabled''

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

                      I am beginning to suspect that your WiFi module is faulty because the "Network state is starting" state should not persist. But first, another test please. Do you have a M552 command in config.g? If so:

                      • remove it or comment it out
                      • restart the Duet, wait a few seconds, run M122 and post the result here
                      • send M552 S0, wait a few seconds, run M122 and post the result here.

                      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
                      • IanWaltonundefined
                        IanWalton
                        last edited by IanWalton

                        you can see whats in my config.g file further up.
                        i commented out all the network stuff, rebooted and the wifi led didnt flash

                        first m122
                        === Diagnostics ===
                        Used output buffers: 1 of 32 (1 max)
                        === Platform ===
                        RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
                        Board ID: 08DDM-9FAM2-LW4S4-6J1D8-3SD6R-T3SZX
                        Static ram used: 16152
                        Dynamic ram used: 100248
                        Recycled dynamic ram: 2384
                        Stack ram used: 3576 current, 4504 maximum
                        Never used ram: 7784
                        Last reset 00:00:41 ago, cause: software
                        Last software reset time unknown, reason: User, spinning module GCodes, available RAM 7784 bytes (slot 0)
                        Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
                        Error status: 0
                        Free file entries: 10
                        SD card 0 detected, interface speed: 20.0MBytes/sec
                        SD card longest block write time: 0.0ms
                        MCU temperature: min 31.3, current 31.4, max 31.8
                        Supply voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0
                        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
                        Slowest main loop (seconds): 0.000153; fastest: 0.000049
                        === Move ===
                        MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
                        Scheduled moves: 0, completed moves: 0
                        Bed compensation in use: none
                        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: 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 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 ===
                        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 2779096485, notready 2779096485, noresp 2779096485
                          Socket states: 0 0 0 0 0 0 0 0
                          === Expansion ===

                        sent m552 s0, no reply on yat
                        M122 returns

                        === Diagnostics ===
                        Used output buffers: 1 of 32 (9 max)
                        === Platform ===
                        RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
                        Board ID: 08DDM-9FAM2-LW4S4-6J1D8-3SD6R-T3SZX
                        Static ram used: 16152
                        Dynamic ram used: 100448
                        Recycled dynamic ram: 2184
                        Stack ram used: 3576 current, 4664 maximum
                        Never used ram: 7624
                        Last reset 00:02:15 ago, cause: software
                        Last software reset time unknown, reason: User, spinning module GCodes, available RAM 7784 bytes (slot 0)
                        Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
                        Error status: 0
                        Free file entries: 10
                        SD card 0 detected, interface speed: 20.0MBytes/sec
                        SD card longest block write time: 0.0ms
                        MCU temperature: min 31.1, current 31.9, max 31.9
                        Supply voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0
                        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
                        Slowest main loop (seconds): 0.099142; fastest: 0.000049
                        === Move ===
                        MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
                        Scheduled moves: 0, completed moves: 0
                        Bed compensation in use: none
                        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: 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 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 ===
                        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 starting
                          WiFi module is disabled
                          Failed messages: pending 0, notready 0, noresp 0
                          Socket states: 0 0 0 0 0 0 0 0
                          === Expansion ===
                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA