Wifi Connection Failing
-
Hi - I have a fresh out of the box Duet WiFi that is not staying connected. I ran through setup and configured per online instructions with no problems, but I am finding that the wifi will stop working at random times and will usually fail on start up with network scan failed. The symptoms are exactly as described in this post so will not repeat them again. I would not bother posting since but vendor I bought the board is insisting that I post again before they will take the board back. (Rather lame I think!)
https://forum.duet3d.com/topic/22157/wifi-reported-error-network-scan-failed
-
@wcarper Please post the result of the command M122 and M98 P"config.g" and the config.g file.
Did you try to change the Channel of your WiFi ? This can sometimes help. -
@siam Changing Wifi channel did not help. Here are the results from DWC when the connection happened to work and from YAT when random failure occured
M122 When Connected
10/22/2021, 7:53:38 AM 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 + DueX5
Board ID: 0JD0M-9P6B2-NJ4S8-6JKF0-3S06T-TA6QL
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 76824 of which 12 recycled
Never used RAM 13704, free system stack 184 words
Tasks: NETWORK(ready,12.4%,244) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,364) DUEX(notifyWait,0.0%,24) MAIN(running,86.8%,443) IDLE(ready,0.7%,29), total 100.0%
Owned mutexes: WiFi(NETWORK) HTTP(MAIN)
=== Platform ===
Last reset 00:01:45 ago, cause: power up
Last software reset at 2021-10-20 17:24, reason: User, GCodes spinning, available RAM 10496, slot 0
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 30.9, current 36.3, max 36.4
Supply voltage: min 24.0, current 24.2, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/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, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, standstill, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-10-22 07:53:37
Cache data hit count 3831143755
Slowest loop: 5.82ms; 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 3.8ms, write time 0.0ms, 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 = 0 -1 -1 -1, chamberHeaters = 3 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is ready with "M122 " 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.
=== Filament sensors ===
Extruder 0 sensor: ok
Extruder 1 sensor: ok
=== DueX ===
Read count 1, 0.57 reads/min
=== Network ===
Slowest loop: 15.83ms; 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 48:3f:da:a6:e2:d3
WiFi Vcc 3.41, reset reason Power up
WiFi flash size 2097152, free heap 25536
WiFi IP address 192.168.1.119
WiFi signal strength -46dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
10/22/2021, 7:55:29 AM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 245CWhen Connection Fails
m122<CR>
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later + DueX5
Board ID: 0JD0M-9P6B2-NJ4S8-6JKF0-3S06T-TA6QL
Used output buffers: 1 of 24 (24 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 76824 of which 12 recycled
Never used RAM 13704, free system stack 193 words
Tasks: NETWORK(notifyWait,12.4%,337) HEAT(delaying,0.0%,336) Move(notifyWait,0.1%,364) DUEX(notifyWait,0.0%,24) MAIN(running,85.3%,467) IDLE(ready,2.2%,29), total 100.0%
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 00:00:33 ago, cause: power up
Last software reset at 2021-10-23 12:33, reason: User, GCodes spinning, available RAM 10496, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x0c
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 40.2, current 43.6, max 43.7
Supply voltage: min 0.0, current 0.4, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0, ok, SG min/max not available
Driver 6: position 0, ok, SG min/max not available
Driver 7: position 0, ok, SG min/max not available
Driver 8: position 0, ok, SG min/max not available
Driver 9: position 0, ok, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 1426401587
Slowest loop: 4.97ms; fastest: 0.13ms
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 3.2ms, write time 0.0ms, 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 = 0 -1 -1 -1, chamberHeaters = 3 -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 ready with "m122" 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.
=== Filament sensors ===
Extruder 0 sensor: ok
Extruder 1 sensor: ok
=== DueX ===
Read count 1, 1.77 reads/min
=== Network ===
Slowest loop: 14.67ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 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 48:3f:da:a6:e2:d3
WiFi Vcc 3.41, reset reason Power up
WiFi flash size 2097152, free heap 27040
WiFi IP address 255.255.255.255
WiFi signal strength 31dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok
M98 P"config.g"
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 250C
Warning: Heater 3 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
ok - WiFi -
-
@wcarper please follow this guide: https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors
and please post your config.g -
@wcarper you have good signal strength and in both M122 reports you posted the wifi module is reporting as successfully connected.
When the connection fails do you get anything reported in the temrinal program when you are connected over USB?
-
While I appreciate the help, I guess I am not making this clear.
-
These are not AJAX errors. The wifi just stops working. The error on DWC indicates that connection is lost and trying to reset. On the PANEL DUE - it indicates that network scan failed (just like the other post._
-
If you look closely at the M122, when it fails it shows a bogus IP address of 255.255.255.255 but when connected it is an appropriate non routable address.
-
This is not my first rodeo with Duet Wifi, I have built 3 different printers with this board and this is the ONLY one that has a problem.
Config.g
; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.2 on Thu Sep 02 2021 15:40:23 GMT-0600 (Mountain Daylight Time); General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"W3R Cheribundi" ; set printer name; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S0 ; physical drive 0 goes backwards and is mapped X
M569 P1 S0 ; physical drive 1 goes backwards and is mapped YLeft
M569 P2 S0 ; physical drive 2 goes backwards and is mapped to open
M569 P3 S0 ; physical drive 3 goes backwards and is mapped to E0 (left)
M569 P4 S1 ; physical drive 4 goes forwards and is mapped to E1 (right)
M569 P5 S1 ; physical drive 5 goes forwards and is mapped to Y Right
M569 P6 S1 ; physical drive 6 goes forwards and is mapped to Z1
M569 P7 S1 ; physical drive 7 goes forwards and is mapped to Z2
M569 P8 S0 ; physical drive 8 goes backwards and is mapped to Z3M584 X0 Y1:5 Z6:7:8 E3:4 ; set drive mapping
M350 X16 Y16:16 Z16:16:16 E16:16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00:80 Z320.00:320.00:320.00 E415.00:415.00 ; set steps per mm
M566 X900.00 Y900.00:900.00 Z60.00:60.00:60.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00:6000.00 Z180.00:180.00:180.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00:500.00 Z20.00:20.00:20.00 E250.00:250.00 ; set accelerations (mm/s^2)
M906 X1500 Y1900:1900 Z1900:1500:1500 E1900:1900 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 Z300 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
;M574 Z1 S2 ; configure Z-probe endstop for low end on ZM574 Z1 S1 P"duex.e3stop + duex.e4stop + duex.e5stop" ; configure stops with independent switches for each motor
;This command is for the endstops and must be in order as M584; Z-Probe
;M558 P5 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
;G31 P500 X0 Y0 Z1.05 ; set Z probe trigger value, offset and trigger height
;M557 X15:285 Y15:285 S60 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M308 S2 P"e1temp" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2
M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H2 S280 ; set temperature limit for heater 2 to 280C
M308 S3 P"duex.e2temp" Y"thermistor" T100000 B4138 ; configure sensor 3 as thermistor on pin duex.e2temp
M950 H3 C"duex.e2heat" T3 ; create chamber heater output on duex.e2heat and map it to sensor 3
M307 H3 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit
M141 H3 ; map chamber to heater 3
M143 H3 S75 ; set temperature limit for heater 3 to 75C; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P1 S1 H-1 ; set fan 0 value. Thermostatic control is turned off and set to run continuously
M950 F2 C"fan2" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P2 S1 H-1 ; set fan 0 value. Thermostatic control is turned off and set to run continuously; Lights Map to Heater 3
M950 F3 C"duex.e3heat"
M106 P3 S0 H-1 C"Chamber Light"
M106 P3 S0 ; Start Light off;M106 P8 S1
; Tools
M563 P0 S"Left Extruder" D0 H1 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S195 ; set initial tool 0 active and standby temperatures to 0C;
M563 P1 S"Right Extruder" D1 H2 ; define tool 1
G10 P1 X20 Y-1 Z0 ; set tool 1 axis offsets
G10 P1 R0 S195 ; set initial tool 1 active and standby temperatures to 0C;Filament Sensors
M591 P1 C"e0stop" S1 D0 ; filament monitor connected to E0 endstop
M591 P1 C"e1stop" S1 D1 ; filament monitor connected to E1 endstop; Custom settings are not defined
; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
; Allow for Config Overide G Code
M501 -
-
@wcarper said in Wifi Connection Failing:
If you look closely at the M122, when it fails it shows a bogus IP address of 255.255.255.255 but when connected it is an appropriate non routable address.
Thanks for pointing that out I missed it.
Is the address it has when its working a fixed IP or one allocated by DHCP? If DHCP as a test can you give it a fixed address with M587 and see if the issue still occurs?
-
I created a fixed address as suggested and for a couple of weeks it worked, but now failing again. According to Matterhackers where I bought the board they will not take it back for exchange for a working board until we have completed this tech support request. Can you acknowledge this is a defective board so that I can get one that works. I use this as part time business and every time this board fails it is affecting my revenue.
-
@wcarper said in Wifi Connection Failing:
WiFi IP address 255.255.255.255
WiFi signal strength 31dBm, mode 802.11n, reconnections 0, sleep mode modemAlso of note is that the signal strength is 31dB!! Not -31dB as you'd expect.
I'm not entirely sure it's a hardware issue, as it seemed to be working on a fixed address, however without much else to go on swapping the hardware would at least help eliminate that as an issue. Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out. Upon completion your seller will be able to exchange your board.
-
@phaedrux There are 2 other duets running in the shop in addition to this one and they operate without issue. The problem is isolated to this board.
-
@wcarper Just to close the loop - I received the warranty replacement board and it has completely resolved the issue. Also, I inadvertently left the SD card on the returned board so at least you will be able to see all the settings!
