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

    Wifi/Web Console issues

    Scheduled Pinned Locked Moved Solved
    General Discussion
    7
    44
    2.2k
    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.
    • MrsDelishundefined
      MrsDelish
      last edited by

      M552 S0 = turn off networking, you do not want that in your config.g if you want networking.

      config.g that contains this should connect if a ssid and pw is previously set.
      ; Network
      M552 S1 ; enable network
      M586 P0 S1 ; enable HTTP
      M586 P1 S0 ; disable FTP
      M586 P2 S0 ; disable Telnet

      gcode wiki M552

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

        @shaun said in Wifi/Web Console issues:

        why the wifi is not even coming on when i power the board?

        What is the power supply? Do the rest of the lights and everything else come on?

        When it is powered by the PSU, can you connect via USB as well and send M122 with the correct YAT line endings and report what the diagnostic replies with?

        Z-Bot CoreXY Build | Thingiverse Profile

        Shaunundefined 1 Reply Last reply Reply Quote 1
        • Shaunundefined
          Shaun @Phaedrux
          last edited by Shaun

          @phaedrux said in Wifi/Web Console issues:

          @shaun said in Wifi/Web Console issues:

          why the wifi is not even coming on when i power the board?

          What is the power supply? Do the rest of the lights and everything else come on?

          When it is powered by the PSU, can you connect via USB as well and send M122 with the correct YAT line endings and report what the diagnostic replies with?

          Ill get this when i get home, PSU is as per vendor recommendations.

          Red light by the USB power port, 2 more lights to the left of that. No blue wifi light.

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

            Understood.

            With the line endings of YAT changed we will be able to see the end of the diagnostic report which contains the wifi section. Without that we're kind of blind as to what's going on.

            Can you also include the contents of config.g from the /sys folder on the SD card?

            That contains your current configuration and what you will be editing going forward. It can be edited from the web interface once you can get reliably connected to it. Until then it may require pulling the SD card unfortunately.

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • A Former User?
              A Former User @Shaun
              last edited by

              @shaun said in Wifi/Web Console issues:

              OK, so could you help me figure out why the wifi is not even coming on when i power the board?

              Sure, when you set aside your assumptions as start doing as suggested. The output from M587 and all of the M122 output please.

              Shaunundefined 1 Reply Last reply Reply Quote 0
              • Shaunundefined
                Shaun @A Former User
                last edited by

                @bearer said in Wifi/Web Console issues:

                M122

                M587<CR>
                M587: Failed to retrieve network list
                ok
                M122 <CR>
                === Diagnostics ===
                RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
                Board ID: 08DGM-9T6BU-FG3SN-6J9F4-3SD6R-TUZHF
                Used output buffers: 1 of 24 (1 max)
                === RTOS ===
                Static ram: 25680
                Dynamic ram: 93244 of which 0 recycled
                Exception stack ram used: 304
                Never used ram: 11844
                Tasks: NETWORK(ready,1876) HEAT(blocked,1236) MAIN(running,4184) IDLE(ready,160)
                Owned mutexes:
                === Platform ===
                Last reset 00:00:55 ago, cause: power up
                Last software reset at 2019-09-02 22:49, reason: User, spinning module GCodes, available RAM 11844 bytes (slot 3)
                Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
                Error status: 0
                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 26.5, current 30.2, max 30.5
                Supply voltage: min 0.6, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
                Driver 0: ok, SG min/max not available
                Driver 1: ok, SG min/max not available
                Driver 2: ok, SG min/max not available
                Driver 3: ok, SG min/max not available
                Driver 4: ok, SG min/max not available
                Date/time: 1970-01-01 00:00:00
                Cache data hit count 101580001
                Slowest loop: 0.16ms; fastest: 0.06ms
                I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                === Move ===
                Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
                Bed compensation in use: none, comp offset 0.000
                === DDARing ===
                Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
                === 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 ===
                Slowest loop: 0.15ms; 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 2779096485, notready 2779096485, noresp 2779096485
                  Socket states: 0 0 0 0 0 0 0 0
                  m552 s0
                  ok
                  WiFi module started
                  m122
                  === Diagnostics ===
                  RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
                  Board ID: 08DGM-9T6BU-FG3SN-6J9F4-3SD6R-TUZHF
                  Used output buffers: 1 of 24 (10 max)
                  === RTOS ===
                  Static ram: 25680
                  Dynamic ram: 93288 of which 0 recycled
                  Exception stack ram used: 304
                  Never used ram: 11800
                  Tasks: NETWORK(ready,1656) HEAT(blocked,1236) MAIN(running,3768) IDLE(ready,160)
                  Owned mutexes:
                  === Platform ===
                  Last reset 00:04:05 ago, cause: power up
                  Last software reset at 2019-09-02 22:49, reason: User, spinning module GCodes, available RAM 11844 bytes (slot 3)
                  Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
                  Error status: 0
                  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 30.2, current 31.6, max 31.7
                  Supply voltage: min 1.7, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
                  Driver 0: ok, SG min/max not available
                  Driver 1: ok, SG min/max not available
                  Driver 2: ok, SG min/max not available
                  Driver 3: ok, SG min/max not available
                  Driver 4: ok, SG min/max not available
                  Date/time: 1970-01-01 00:00:00
                  Cache data hit count 461723815
                  Slowest loop: 99.34ms; fastest: 0.06ms
                  I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                  === Move ===
                  Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
                  Bed compensation in use: none, comp offset 0.000
                  === DDARing ===
                  Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
                  === 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 ===
                  Slowest loop: 1.22ms; 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 running
                  WiFi module is idle
                  Failed messages: pending 0, notready 0, noresp 0
                  WiFi firmware version 1.23
                  WiFi MAC address 84:f3:eb:41:4e:f8
                  WiFi Vcc 3.39, reset reason Turned on by main processor
                  WiFi flash size 4194304, free heap 30176
                  Socket states: 0 0 0 0 0 0 0 0
                  ok
                  m587
                  Remembered networks:
                  Spiffy IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
                  ok
                  M587 s"Spiffy" p"Password1"
                  ok
                  M587
                  Remembered networks:
                  Spiffy IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
                  ok
                  m122
                  === Diagnostics ===
                  RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
                  Board ID: 08DGM-9T6BU-FG3SN-6J9F4-3SD6R-TUZHF
                  Used output buffers: 1 of 24 (10 max)
                  === RTOS ===
                  Static ram: 25680
                  Dynamic ram: 93288 of which 0 recycled
                  Exception stack ram used: 304
                  Never used ram: 11800
                  Tasks: NETWORK(ready,1656) HEAT(blocked,1236) MAIN(running,3756) IDLE(ready,160)
                  Owned mutexes:
                  === Platform ===
                  Last reset 00:05:15 ago, cause: power up
                  Last software reset at 2019-09-02 22:49, reason: User, spinning module GCodes, available RAM 11844 bytes (slot 3)
                  Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
                  Error status: 0
                  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 31.4, current 32.3, max 32.4
                  Supply voltage: min 1.7, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
                  Driver 0: ok, SG min/max not available
                  Driver 1: ok, SG min/max not available
                  Driver 2: ok, SG min/max not available
                  Driver 3: ok, SG min/max not available
                  Driver 4: ok, SG min/max not available
                  Date/time: 1970-01-01 00:00:00
                  Cache data hit count 602028484
                  Slowest loop: 0.33ms; fastest: 0.06ms
                  I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                  === Move ===
                  Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
                  Bed compensation in use: none, comp offset 0.000
                  === DDARing ===
                  Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
                  === 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 ===
                  Slowest loop: 0.14ms; 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 running
                  WiFi module is idle
                  Failed messages: pending 0, notready 0, noresp 0
                  WiFi firmware version 1.23
                  WiFi MAC address 84:f3:eb:41:4e:f8
                  WiFi Vcc 3.39, reset reason Turned on by main processor
                  WiFi flash size 4194304, free heap 30176
                  Socket states: 0 0 0 0 0 0 0 0
                  ok

                .....

                1 Reply Last reply Reply Quote 0
                • Shaunundefined
                  Shaun
                  last edited by

                  Rebooting device.....
                  m122
                  === Diagnostics ===
                  RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
                  Board ID: 08DGM-9T6BU-FG3SN-6J9F4-3SD6R-TUZHF
                  Used output buffers: 1 of 24 (1 max)
                  === RTOS ===
                  Static ram: 25680
                  Dynamic ram: 93244 of which 0 recycled
                  Exception stack ram used: 244
                  Never used ram: 11904
                  Tasks: NETWORK(ready,1876) HEAT(blocked,1236) MAIN(running,4468) IDLE(ready,160)
                  Owned mutexes:
                  === Platform ===
                  Last reset 00:00:37 ago, cause: power up
                  Last software reset at 2019-09-02 22:49, reason: User, spinning module GCodes, available RAM 11844 bytes (slot 3)
                  Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
                  Error status: 0
                  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 31.1, current 33.0, max 33.2
                  Supply voltage: min 1.5, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
                  Driver 0: ok, SG min/max not available
                  Driver 1: ok, SG min/max not available
                  Driver 2: ok, SG min/max not available
                  Driver 3: ok, SG min/max not available
                  Driver 4: ok, SG min/max not available
                  Date/time: 1970-01-01 00:00:00
                  Cache data hit count 68946894
                  Slowest loop: 0.15ms; fastest: 0.06ms
                  I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                  === Move ===
                  Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
                  Bed compensation in use: none, comp offset 0.000
                  === DDARing ===
                  Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
                  === 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 ===
                  Slowest loop: 0.15ms; 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 2779096485, notready 2779096485, noresp 2779096485
                    Socket states: 0 0 0 0 0 0 0 0
                    ok

                  Config.g
                  ; Configuration file for Duet WiFi (firmware version 2.03)
                  ; executed by the firmware on start-up
                  ;
                  ; generated by RepRapFirmware Configuration Tool v2.0.0 on Sun Sep 01 2019 16:01:34 GMT+0100 (British Summer Time)

                  ; General preferences
                  G90 ; send absolute coordinates...
                  M83 ; ...but relative extruder moves
                  M550 P"CR10" ; set printer name
                  M911 S10 R11 P'M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000' ; set voltage thresholds and actions to run on power loss

                  ; Drives
                  M569 P0 S1 ; physical drive 0 goes forwards
                  M569 P1 S1 ; physical drive 1 goes forwards
                  M569 P2 S1 ; physical drive 2 goes forwards
                  M569 P3 S1 ; physical drive 3 goes forwards
                  M584 X0 Y1 Z2 E3 ; set drive mapping
                  M350Z16 I0 ; configure microstepping without interpolation
                  M350X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
                  M92 X80.00 Y80.00 Z4000.00 E420.00 ; set steps per mm
                  M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
                  M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
                  M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
                  M906 X950 Y950 Z950 E950 I30 ; set motor currents (mA) and motor idle factor in per cent
                  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 X1 Y1 Z1 S1 ; set active high endstops
                  M574 Z1 S3 ; set endstops controlled by motor stall detection

                  ; Z-Probe
                  M574 Z1 S2 ; set endstops controlled by probe
                  M558 P5 H5 F0 T6000 ; set Z probe type to switch and the dive height + speeds
                  G31 P0 X0 Y0 Z0 ; set Z probe trigger value, offset and trigger height
                  M557 X15:215 Y15:195 S20 ; define mesh grid

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

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

                  ; Tools
                  M563 P0 D0 H1 F0 ; 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

                  ; Network
                  M552 S1 ; enable network
                  M586 P0 S1 ; enable HTTP
                  M586 P1 S0 ; disable FTP
                  M586 P2 S0 ; disable Telnet

                  ; Custom settings are not defined

                  m115
                  FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2
                  ok

                  Anything else?

                  1 Reply Last reply Reply Quote 0
                  • A Former User?
                    A Former User
                    last edited by

                    Does it make any difference using M552 S1 P"Spiffy"

                    if you have a look at the markdown page, especially the code block, you'll be able to make the output a lot easier to read
                    https://commonmark.org/help/

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

                      From the console can you please send the following:

                      M552 S0
M588 S"*"
M587 s"Spiffy" p"Password1"
M552 S1
M122

                      This will take the wifi module to idle, clear all saved SSIDs, re-add your SSID, and re-enable the module and hopefully connect. Then the diagnostic should show the connection stats.

                      How far away is the access point from the printer?
                      Do your other devices get a strong signal in that area?
                      Is the access point 2.4Ghz? 5Ghz won't work.

                      Z-Bot CoreXY Build | Thingiverse Profile

                      1 Reply Last reply Reply Quote 0
                      • Shaunundefined
                        Shaun
                        last edited by

                        m122
                        === Diagnostics ===
                        RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
                        Board ID: 08DGM-9T6BU-FG3SN-6J9F4-3SD6R-TUZHF
                        Used output buffers: 1 of 24 (1 max)
                        === RTOS ===
                        Static ram: 25680
                        Dynamic ram: 93244 of which 0 recycled
                        Exception stack ram used: 304
                        Never used ram: 11844
                        Tasks: NETWORK(ready,1244) HEAT(blocked,1236) MAIN(running,4468) IDLE(ready,160)
                        Owned mutexes:
                        === Platform ===
                        Last reset 00:12:58 ago, cause: power up
                        Last software reset at 2019-09-02 22:49, reason: User, spinning module GCodes, available RAM 11844 bytes (slot 3)
                        Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
                        Error status: 0
                        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 32.6, current 35.4, max 35.5
                        Supply voltage: min 1.5, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
                        Driver 0: ok, SG min/max not available
                        Driver 1: ok, SG min/max not available
                        Driver 2: ok, SG min/max not available
                        Driver 3: ok, SG min/max not available
                        Driver 4: ok, SG min/max not available
                        Date/time: 1970-01-01 00:00:00
                        Cache data hit count 2516579683
                        Slowest loop: 99.70ms; fastest: 0.06ms
                        I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                        === Move ===
                        Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
                        Bed compensation in use: none, comp offset 0.000
                        === DDARing ===
                        Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
                        === 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 ===
                        Slowest loop: 15.36ms; 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 running
                          WiFi module is connected to access point
                          Failed messages: pending 0, notready 0, noresp 0
                          WiFi firmware version 1.23
                          WiFi MAC address 84:f3:eb:41:4e:f8
                          WiFi Vcc 3.39, reset reason Exception
                          WiFi flash size 4194304, free heap 23696
                          WiFi IP address 192.168.0.19
                          WiFi signal strength -60dBm, reconnections 0, sleep mode modem
                          Socket states: 0 0 0 0 0 0 0 0
                          ok

                        So now my problem is still powering down and then moving the board to my printer. wifi remains disabled

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

                          @shaun said in Wifi/Web Console issues:

                          WiFi signal strength -60dBm

                          I suspect this is the problem. -60 is already on the low end. When you move to the printer location I suspect the signal is too weak for it to connect.

                          You may find this helpful: https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors

                          Z-Bot CoreXY Build | Thingiverse Profile

                          Shaunundefined 1 Reply Last reply Reply Quote 0
                          • Shaunundefined
                            Shaun @Phaedrux
                            last edited by

                            @phaedrux

                            Thanks but i think you misunderstood. the wifi is disabled after power cycle.

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

                              @phaedrux said in Wifi/Web Console issues:

                              When it is powered by the PSU, can you connect via USB as well and send M122

                              Can you check this?

                              Z-Bot CoreXY Build | Thingiverse Profile

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

                                I don't think it's disabled, I think it's trying to find an SSID and cannot, so it stops.

                                It's working and connecting reliably when you're powered via USB, correct?

                                Z-Bot CoreXY Build | Thingiverse Profile

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

                                  If you have M552 S1 in config.g and you do not also have another M552 command in there that cancels it, then when it has finished running config.g is will do a site scan and connect to the strongest network that you have told it about via M587. So:

                                  1. Make sure there is exactly one M552 command in config.g and it has parameter S1.

                                  2. Retype that line in case it contains hidden characters.

                                  3. When you start the Duet, look out for the blue LED on the WiFi module flashing.

                                  If it tries to connect but fails, the state falls back to Idle, not Disabled. State Disabled is what you get if you never used M552 to enable the WiFi module, or if you send M552 S-1.

                                  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
                                  • Shaunundefined
                                    Shaun @Phaedrux
                                    last edited by

                                    @phaedrux At my desk, i power cycle the board and the wifi doesnt light up. check the config and wifi disabled.

                                    there in lies my problem.

                                    1 Reply Last reply Reply Quote 0
                                    • Shaunundefined
                                      Shaun
                                      last edited by

                                      Thanks for all the help, ive managed to resolve this issue myself. Nothing like recompiling the Config.g from scratch.

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

                                        I assume you mean run through the configurator again to get a new set of configs?

                                        It's not so complicated once you're connected. The config.g is just a plain text file with gcode commands. You can edit it right from the web interface.

                                        Z-Bot CoreXY Build | Thingiverse Profile

                                        1 Reply Last reply Reply Quote 0
                                        • A Former User?
                                          A Former User
                                          last edited by

                                          Something i noticed which may or may not have a bearing on things, I thought that in the config.g that the network section was always generally at the start of the file, in this gents case it was well down his list.

                                          So does the duet execute the g code in the order in which its in the file or is it irrelevant and you can put the g code in any order at all ?

                                          Shaunundefined 1 Reply Last reply Reply Quote 0
                                          • A Former User?
                                            A Former User
                                            last edited by A Former User

                                            Everything is executed line by line, be it a config file or a sliced file to print.

                                            The order is only important for a few commands, more so in RRF3 as you have to define pins and stuff before using commands that use them etc. The wiki has some notes on the commands where the order do matter.
                                            (But as evident in another recent thread having the network config at the top may allow you to have working network even if there is a problem further down in the config file?)

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