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.
-
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 -
-
did you open the web controll over IP adress or over dns Name ?
-
@kylemoo said in Connected via web control then next day can't connect?:
WiFi IP address 192.168.0.114
WiFi signal strength -61dBm, reconnections 0, sleep mode modem-61dBm is quite a weak signal; see note in THIS link:
Values in the range -30 to -50 are good, -50 to -60 is OK, -60 to -70 is marginal. Anything below -70 is weak and likely be unreliable. See below for how to improve RSSI.
But you do have a defined IP address. Are you using DHCP for assigning the IP address? Has it changed since yesterday? Connect to 192.168.0.114. Alternatively, use your machine name to connect, with .local on the end.
Are you actually getting the error message "Your Duet rejected the HTTP request: page not found"? This usually means that the files on the SD card in /www are missing or corrupt. Try:
- Download and unzip the "DuetWebControl-SD.zip" file from HERE
- Remove the SD card from the printer, put it in a PC, and copy the files to the /www folder on the SD card
- Replace SD card in the printer and try connecting again.
Ian
-
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.
-
@kylemoo said in Connected via web control then next day can't connect?:
Does that happen a lot with Duet2wifi boards?
No more than any other WiFi device, in my experience.
If your Duet is set up to use DHCP, so gets its address from the router, connecting using the printer name with .local on the end means you don't need to keep track of the IP address if the router resets. However, using the printer name to connect will depend on your router and your PC supporting mDNS/DNS-SD (also known as zeroconf and Bonjour, longer article about this here), which is the network protocol used for this. Generally, routers less than 5 years old should support it. For your PC, see this article, but basically Apple Macs (and, I think, Windows 10) support it, while Linux and Windows (other versions) need to have it installed.
Alternatively, set your Duet to a fixed IP address, using M587 to update the stored WiFi access point information (run this from the console), eg:
M587 S"your_wifi_network_SSID" P"your_wifi_password" I"192.168.0.114"
Then the IP address you connect to will always be the same.Ian
