Turns out my wifi router had to get reset and now all is fine. Very strange. Does that happen a lot with Duet2wifi boards? Thanks for the reply and help.
Posts made by kylemoo
-
RE: Connected via web control then next day can't connect?
-
RE: Connected via web control then next day can't connect?
M122 output below for reference
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.04 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SJ-6J9DL-3SD6S-1SX3D
Used output buffers: 1 of 24 (10 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93000 of which 0 recycled
Exception stack ram used: 264
Never used ram: 12128
Tasks: NETWORK(ready,540) HEAT(blocked,1232) MAIN(running,3740) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:01:14 ago, cause: reset button or watchdog
Last software reset details not available
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 28.0, current 28.1, max 28.4
Supply voltage: min 1.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 254962359
Slowest loop: 3.68ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, 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: 1446.61ms; 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 60:01:94:2e:a6:89
WiFi Vcc 3.40, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25944
WiFi IP address 192.168.0.114
WiFi signal strength -61dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
Connected via web control then next day can't connect?
Re: Your Duet rejected the HTTP request: page not found
I just received my duet2 wifi and I set up the connection via YAT. I can comm with the board via usb. The first day I connected also via web control just fine. I updated the firmware to 2.04 and everything still worked fine.
disconnected the usb and came back to it the next day and web control doesn't work? Any help would be appreciated.