Please help: Duet Wifi stuck on Wifi Idle, No Networks, etc

ddxdesign

@dc42 Thank you for the suggestion; I'll try it. Is there a way to check from the panel itself whether the firmware is in there?

ddxdesign

@dc42 Update: I did try it and it says "Warning: M996 command is not supported."

Beyond trying to fix it right now, I have to ask: How does something like this go from working every day for months to, after a 3 day period of being powered off, suddenly just deciding not to work anymore?

jay_s_uk

@ddxdesign it should be M997 S1

ddxdesign

@jay_s_uk Aha, ok, that did work to redo the firmware it looks like. now to try all the setup stuff again.

ddxdesign

@dc42 @jay_s_uk OK, firmware seemed to work but everything else once again no dice. If I can't load up customers' orders to print, this $1600 machine has just become a sculpture. UGH.

jay_s_uk

@ddxdesign where's it getting stuck at now?
Can you get an output of M122?

ddxdesign

@jay_s_uk M588 still not working "Failed to reset to factory" - M587 not working "Failed to add network" - M122 shows, lets see.... aside from the version IDs and things it says:

Use output buffers 1 of 20 (12 max) === RTOS === Static ram 25524 Dynamic ram 98864 of which 0 recycled Exception stack ram used 432 Ne (it just cuts off there)

jay_s_uk

@ddxdesign what are you using to connect via USB? YAT?
Can you set it up using the instructions here? https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7#s7
If you have issues with getting it going, can you confirm the firmware version using M115?

ddxdesign

@jay_s_uk No USB, it's all through the panel due. SeeMe says they do not recommend connecting to this machine through USB - to do everything from the panel. Running 2.02 FW (12/24/18). That's odd because I got the machine brand new 8 mos ago, but then again maybe their machines use older FW on purpose (assuming there have been new FWs in the ensuing time)

SIam

@ddxdesign said in Please help: Duet Wifi stuck on Wifi Idle, No Networks, etc:

SeeMe says they do not recommend connecting to this machine through USB

and this is why : https://duet3d.dozuki.com/Wiki/USB_ground_loops

if you disconnect your printer from mains, you can connect the USB cable to use YAT (the duet board will be powered by the USB connection)

jay_s_uk

@ddxdesign there's no issues with connecting to the board through USB. Would definitely make it easier to get an output from things.
The paneldue is good but can make general troubleshooting difficult.
As @SIam pointed out, ground loops are the main issue but if you use a laptop powered from the battery (not on charge) you are perfectly fine.

ddxdesign

@siam Hmm; where my printer is, I would have to use my laptop on battery to get to anyways, so maybe this isn't a concern?

jay_s_uk

@ddxdesign definitely not a concern.
Would make the troubleshooting easier

ddxdesign

@jay_s_uk OK let me see if I can remember how to use Yat...

ddxdesign

@jay_s_uk Alrighty, from YAT the full M122 output is:

=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later<LF>Board ID: 08DLM-996RU-N85S4-7JKF4-3SN6P-TU97R<LF>Used output buffers: 1 of 20 (13 max)<LF>=== RTOS ===<LF>Static ram: 25524<LF>Dynamic ram: 98864 of which 0 recycled<LF>Exception stack ram used: 432<LF>Never used ram: 6252<LF>Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3636) IDLE(ready,200)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 69:35:24 ago, cause: power up<LF>Last software reset at 2021-08-22 09:46, reason: User, spinning module GCodes, available RAM 6212 bytes (slot 3)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 8<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 40.4, current 40.6, max 41.6<LF>Supply voltage: min 13.0, current 13.1, max 13.1, under voltage events: 0, over voltage events: 0, p[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]

ddxdesign

I did just discover some new-firmware instructions from seemecnc; I will have to allocate a big chunk of time to trying this I think. EDIT: Sigh, have to go buy an SD-to-USB thing.

jay_s_uk

@ddxdesign you need to increase the end of line settings to get the full output.
If you have a look at that link I posted a few pages up, it tells you all the settings you need to change in YAT

ddxdesign

@jay_s_uk Well, did that, but now when I paste in the true full output, I can't post it - forum gives me a Flagged As Spam error...

SIam

@ddxdesign said in Please help: Duet Wifi stuck on Wifi Idle, No Networks, etc:

@jay_s_uk Well, did that, but now when I paste in the true full output, I can't post it - forum gives me a Flagged As Spam error...

please try it again now

ddxdesign

@siam Alrighty, how's this?

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85S4-7JKF4-3SN6P-TU97R
Used output buffers: 1 of 20 (4 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98820 of which 0 recycled
Exception stack ram used: 424
Never used ram: 6304
Tasks: NETWORK(ready,1260) HEAT(suspended,1232) MAIN(running,3788) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:44:43 ago, cause: software
Last software reset time unknown, reason: Heat task stuck, spinning module FilamentSensors, available RAM 6024 bytes (slot 0)
Software reset code 0x00ad HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f80f BFAR 0xe000ed38 SP 0x20004a54 Task 0x4e49414d
Stack: 0044bcc7 004495f2 21000000 00000000 00000000 00000000 00000000 3e178897 3e1cd04f 41800000 3e3a4b83 3e63a760 3e92581f 3ccd4e65 3eccdf1a 3e221bcd 3f800000 c0a00000 00000000 60000010 e000ed04 20004ad0 00000000
Error status: 1
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 40.4, current 40.9, max 41.8
Supply voltage: min 13.0, current 13.1, max 13.3, under voltage events: 0, 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 4294967295
Slowest loop: 1.21ms; fastest: 0.07ms
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: mesh
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: 2 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: 1.30ms; 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 disabled
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok