Duet Wifi-Establishing Wifi connection requires multiple resets
-
I purchased a Duet Wifi in April and have had to press the reset button multiple times to connect anytime I restart or power it on. the issue appears to be the same as https://forum.duet3d.com/topic/7223/duet-wifi-establishing-wifi-connection-requires-multiple-resets .
If I connect to it via USB it shows that the network is up and connected to the AP but the web interface will not load and I am unable to ping it via the IP address. Included below are the results from YAT after a reboot when I am unable to connect to the web interface. If I am connected by USB I can issue S0 and S1 three times and the interface will come back up.
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.02(RTOS) ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2018-12-24b1
ok
M552
WiFi module is connected to access point ATThnW4n6a, IP address 192.168.1.175
ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS4-6J9DA-3SD6M-TSYVA
Used output buffers: 1 of 20 (1 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98524 of which 0 recycled
Exception stack ram used: 360
Never used ram: 6664
Tasks: NETWORK(ready,1412) HEAT(blocked,1232) MAIN(running,3812) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:09:26 ago, cause: power up
Last software reset at 2019-05-03 10:28, reason: User, spinning module GCodes, available RAM 6528 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 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 27.1, current 33.4, max 33.7
Supply voltage: min 0.5, current 24.4, max 25.2, under voltage events: 1, over voltage events: 0, power good: yes
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
Cache data hit count 2128103128
Slowest loop: 1.11ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 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 ===
Slowest loop: 15.74ms; 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 cc:50:e3:0d:23:3c
WiFi Vcc 3.34, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 26256
WiFi IP address 192.168.1.175
WiFi signal strength -45dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
ok
- WiFi -
-
Tagging @dc42 for input
-
Two possibilities;
-
Your router is not passing on requests to the Duet. When the Duet says it is connected but you can't access it, log on to your router admin page and see whether the Duet is in the list of attached devices, with the correct IP address. Also try entering "arp -a" on the command line of your PC and check whether the Duet's IP address is listed. Adding an IP address reservation for the Duet in your router may also be helpful, if you haven't done that already.
-
Router is passing requests on but the WiFi module is ignoring them. The WiFi module could be faulty.
HTH David
-
-
Checking on the router when I am unable to connect the Duet is listed as an attached device with the correct IP. Also arp -a shows the Duet with the correct IP but I am still unable to ping it until I press the reset button multiple times. As far as adding a reservation to the router I am not sure that would make a difference as I am using a static IP address that was setup with the M587 command.
-
Some routers have an option to ping a target, can the router itself ping the printer ?
Is your pc connected via lan or wlan ? switch to using it in the other connection type to check if you can access the printer then.
Try it from a different pc if you have one around, maybe it is some windows/pc security setting that has the problem and not the duet or router. -
Oddly enough I do seem to be able to always ping it from the router. From the laptop wired and wireless both give the same results. Tried it from three different laptops and all give the same results so I do not feel like it is an issue from the computer side.
-
@nwolfe said in Duet Wifi-Establishing Wifi connection requires multiple resets:
Oddly enough I do seem to be able to always ping it from the router. From the laptop wired and wireless both give the same results. Tried it from three different laptops and all give the same results so I do not feel like it is an issue from the computer side.
If you can always ping the Duet from the router, but often not from a PC connected to the router, that suggests that the router/access point/switch is not passing the ping request on to the Duet, or not passing the reply back.
Have you another router that you can try?
-
I wanted to drop back in you give you an update. during my testing I managed to corrupt my config.g file so I ended up formatting the card and copied my backup files to it. After doing this I have no longer had any issues connecting to the web console after a power up or restart.
