Duet Web Control 404 error

[dc42]

If you think the Duet reset itself, get a M122 report out of it before you do another software reset.

[ockray83]

M122 report:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DJMSN-6J9FA-3S86J-TARZG
Used output buffers: 3 of 20 (10 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98620 of which 0 recycled
Exception stack ram used: 432
Never used ram: 6496
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3788) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 02:29:51 ago, cause: software
Last software reset at 2020-05-09 10:59, reason: Stuck in spin loop, spinning module GCodes, available RAM 6268 bytes (slot 2)
Software reset code 0x4043 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20001efc Task 0x5754454e
Stack: 00443523 00446ee6 21000000 dc000000 4153df1c 00000000 00000000 434b3217 436a1fe6 bdb81c00 4893afd1 cb295ff9 422b1a1b 00000000 476c1e00 37d33333 3f800000 60000000 411fcb61 20000010 00000004 00000000 00000004
Error status: 8
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 39.6, current 42.9, max 44.6
Supply voltage: min 12.6, current 12.9, max 13.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, SG min/max 0/1023
Driver 1: ok, SG min/max 0/1023
Driver 2: ok, SG min/max 0/608
Driver 3: ok, SG min/max 0/1023
Driver 4: standstill, SG min/max not available
Date/time: 2020-05-09 13:30:07
Cache data hit count 4294967295
Slowest loop: 342.01ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 121, MinFreeDm: 120, MaxWait: 509865ms, Underruns: 0, 0
Scheduled moves: 105415, completed moves: 105385
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
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
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 doing "G1 X13.922 Y-3.572 E25.24059" in state(s) 0
serial is idle 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.61ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 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:73:5b:e9
  WiFi Vcc 3.39, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 25240
  WiFi IP address 10.0.0.17
  WiFi signal strength -71dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0

EDIT: The router isn't responding to the duet again. Same as before, started a print, able to use DWC for a while, then the same error connection reset page as before.

Upon print finish (different file this time) the printer froze again and I could not command it to do anything until I pressed the red stop button. it then reset and would go to home.

M552 shows it is connected to the network. Cycling S0, S1 doesn't seem to do anything as it still shows connected to the network after sending S0 and after sending S1. I'm still unable to connect to DWC.

The duet now seems to freeze up after every completed print and will not move until it reboots. What should I try next?

[ockray83]

I've had a couple of short prints in which I can maintain DWC access, but anything longer than about 4 hours ends up disconnecting.

With the short prints, the head retracts to the home position as it should at the end of a print.

Any time a print results in a disconnect from DWC, it will still freeze at the end of the print. This is very irritating as I'm usually left with a blob of drool on the top of my print if I'm not there to intervene right when the print finishes.

I'm really at a loss as to why loss of DWC access would result in the printer freezing up at the completion of a job.

Any input or assistance is greatly appreciated.

[bot]

This sounds like an issue I see sometimes. Are you on ethernet or wifi?

[ockray83]

Wi-fi. My printer is in my shop in the basement, my router is on the 1st floor, maybe 10ft away from the printer's location.

EDIT: So much for my theory on long prints being related to disconnects. I'm in the middle of a 2 hour print and I've lost DWC again.

[ockray83]

I'm reaching a peak of frustration with the disconnecting issue. It seems like its happening more frequently. I'm trying to change some settings to improve the printer's accuracy and I cannot stay connected to DWC for more than five seconds at a time before getting an error message that says request time out.

I cannot keep my printer going with an interface that behaves like this. Can anyone please help me?

[dc42]

Which version of DWC are you using?

The duet now seems to freeze up after every completed print and will not move until it reboots. What should I try next?

When it freezes, are you able to connect via USB/YAT and get a M122 report?

[ockray83]

Sorry for the delay, i've been sick the past couple days and hadn't made it back into the workshop.

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.02(RTOS) (2018-12-24b1)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6

I've been able to connect via YAT when i lose DWC connection. The connection seems stable so far this morning, I haven't been disconnected yet and I've been on for about 30 minutes so far.

[dc42]

Your WiFi and DWC versions are OK, but your main firmware version (2.02) is old. I suggest you upgrade it to 2.05.1.

[ockray83]

I've just updated the duet, I will see how stable the connection remains and report back.

[ockray83]

I am still experiencing disconnects (just had one). I also have network errors when trying to upload g-code files or update my config file, which causes it to disappear from the system and needs to be manually uploaded via sd card. I'm also getting several new errors in the lower right hand corner of the screen when I start up the printer and press home:

[Phaedrux]

https://duet3d.dozuki.com/Wiki/FAQ#Section_I_get_this_error_message_Error_G0_G1_insufficient_axes_homed

Your homing files need to be updated to have S2/H2 on moves of axis that are not yet homed. This is usually for lifting the Z axis for clearance before homing X and Y. In fact, the error message is giving you the exact line causing the issue G1 Z-25 F6000 Adding H2 to that line will stop that error message.

[ockray83]

That applies to delta printers as well?

[Phaedrux]

It applies to moving any axis before it is homed.

[ockray83]

I haven't been able to update the homing files yet, as I have not been able to successfully connect to DWC today. It looks like the issue is still going on after the firmware update.

[Phaedrux]

@ockray83 said in Duet Web Control 404 error:

WiFi signal strength -71dBm

Are you still getting low signal strength? -70 is borderline. If you can move the printer temporarily to a better location for signal to see if that helps the issue. If it does, secondary access point added closer to the printer, a wifi repeater or powerline wifi access point would be a possible solution.

[ockray83]

Most of the time it seems to be in the mid to high 60's. Moving the printer upstairs to get it closer to the router really isn't an option (cats like the printer too much), but I should be able to move the router downstairs closer to the printer. I'll try that next.

[ockray83]

It has been a couple of weeks since I moved the router closer to my printer. I am happy to say that after moving the router to within about a 6ft line of sight with my printer, I have been enjoying DWC undisturbed by constant dropouts, save for one instance today, which I believe I can attribute to mistakenly trying to upload a g-code file into the job list via Slicer while another print was in progress.

I had enough confidence in the system's stability now that I invested in a smart effector & rods for the printer as well and I couldn't be happier with the result.

Thank you to everyone that replied and helped out a new user struggling. When I get around to building a second printer, I know what board I'm putting in it.