Duet2/RRFW 3.3 -estop'd it Now dead PanelDue7 connecting

SputnikOC3d

Cant wifi connect - cant get data from paneldue console

stuck at "connecting"

Cant get M122 or M115 or anything really - its stuck and I am too ...

Bit flustered with having to be a hardware and firmware guru to use my printers. Dont expect it to be drop dead simple all the time, but certainly not this fussy and complex.

SputnikOC3d

=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later<LF>Board ID: 08DGM-917NK-F2MS4-7J1F0-3S86T-KYTDD<LF>
Used output buffers: 1 of 24 (12 max)<LF>
=== RTOS ===<LF>
Static ram: 23876<LF>
Dynamic ram: 73544 of which 12 recycled<LF>
Never used RAM 16984, free system stack 193 words<LF>
Tasks: NETWORK(ready,9.8%,517) HEAT(suspended,0.0%,386) MAIN(running,90.2%,398) IDLE(ready,0.0%,29), total 100.0%<LF>
Owned mutexes: USB(MAIN)<LF>
=== Platform ===<LF>
Last reset 00:28:47 ago, cause: reset button or watchdog<LF>
Last software reset at 2021-09-26 22:18, reason: User, GCodes spinning, available RAM 11992, slot 0<LF>
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a<LF>
Error status: 0x00<LF>
Step timer max interval 0<LF>
MCU temperature: min 37.9, current 37.9, max 37.9<LF>
Supply voltage: min 1.7, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no<LF>
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0<LF>
Driver 0: position 0, ok, SG min/max not available<LF>
Driver 1: position 0, ok, SG min/max not available<LF>
Driver 2: position 0, ok, SG min/max not available<LF>
Driver 3: position 0, ok, SG min/max not available<LF>
Driver 4: position 0, ok, SG min/max not available<LF>
Driver 5: position 0<LF>
Driver 6: position 0<LF>
Driver 7: position 0<LF>
Driver 8: position 0<LF>Driver 9: position 0<LF>
Driver 10: position 0<LF>
Driver 11: position 0<LF>

Date/time: 1970-01-01 00:00:00<LF>
Cache data hit count 4294967295<LF>
Slowest loop: 300.09ms; fastest: 0.13ms<LF>
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0<LF>
=== Storage ===<LF>Free file entries: 10<LF>
SD card 0 detected, interface speed: 20.0MBytes/sec<LF>
SD card longest read time 0.0ms, write time 0.0ms, max retries 0<LF>
=== Move ===<LF>DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000<LF>
=== MainDDARing ===<LF>
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>
=== AuxDDARing ===<LF>
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>
=== Heat ===<LF>
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1<LF>
=== GCodes ===<LF>Segments left: 0<LF>
Movement lock held by null<LF>
HTTP is idle in state(s) 0<LF>Telnet is idle in state(s) 0<LF>
File is idle in state(s) 0<LF>
USB is ready with "M122" in state(s) 0<LF>
Aux is idle in state(s) 0<LF>
Trigger is idle in state(s) 0<LF>Queue is idle in state(s) 0<LF>
LCD is idle in state(s) 0<LF>Daemon is idle in state(s) 0<LF>
Autopause is idle in state(s) 0<LF>
Code queue is empty.<LF>=== Network ===<LF>
Slowest loop: 0.17ms; fastest: 0.00ms<LF>
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions<LF>HTTP sessions: 0 of 8<LF>
- WiFi -<LF>
Network state is disabled<LF>
WiFi module is disabled<LF>
Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485<LF>
Socket states: 0 0 0 0 0 0 0 0
<LF>ok<LF>

SputnikOC3d

Connected via YAT and got hte above diag info.

Looks like SD card is not being read. How can I get to the data on the card if any ?

What is the proper reset procedure if applicable. Theres some note about : Remove the SD card and Reset. But is there an actual step by step to do a "reset" properly ?

I have powered off the machine completely.
Removed SD Card
Plugged in USB ONLY no VIN Power with SD CARD removed
Pressed the Reset Button
Powered off by removing the USB
Let power off completely
Inserted SD Card
Plugged USB cable back in - still no VIN power
RED DIAG LED remains lit.

In YAT ...

M98 P"config.g"<CR><LF>
Warning: Macro file config.g not found
<LF>ok<LF>

SputnikOC3d

Seriously ?

https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_1

Take the on-board SD card out and put it in a computer
Delete any existing firmware files in /sys
Copy the new firmware binary file to the /firmware (if RRF 3.3beta1 or later is installed) or /sys folder (for earlier firmware versions)
Also copy the relevant IAP file (see Required Files, above) into /sys
If your board is a Duet WiFi, also copy the new DuetWiFiServer.bin file into /sys
Eject/safely remove the SD card from the PC
Replace the on-board SD card in the Duet 2 WiFi
Restart the Duet 2 WiFi and connect with Pronterface or YAT
Send command M997 S0 to install the firmware.
Press the Disconnect button in Pronterface, then when the USB port disappears and reappears about 20 seconds later, press Connect.
Send M115 to confirm the new firmware version
If the board is a Duet WiFi, send M997 S1 to install the WiFi module firmware

M997 S0<CR><LF>
Error: M997: In-application programming binary "0:/firmware/Duet2_SDiap32_WiFiEth.bin" not found<LF>ok<LF>
M997 S1<CR><LF>
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found<LF>ok<LF>

SputnikOC3d

Does anyone really understand how absurd and obtuse all this is ?

File locations on the Duet SD card
With all firmware versions up to RRF v3.2.2, all firmware update files are stored in the ‘0:/sys/’ directory.
From RRF v3.3beta1, to avoid too many files in this folder, all firmware update files are stored in ‘0:/firmware/’ directory.
This means if you have upgraded from, for example, RRF v3.2.2 to RRF v3.3beta1 (the firmware, IAP and DWC files will be put in the ‘sys’ directory), then update to RRF v3.3beta2 by just uploading the firmware binary (which it will put in the ‘firmware’ directory), you’ll get a message that the IAP file is missing, because it expects to find it in ‘firmware’. Upload the IAP file from the v3.2.2 release, and it should put it in the ‘firmware’ folder.

SputnikOC3d

Your Duet rejected the HTTP request: page not found
Check that the SD card is mounted and has the correct files in its /www folder

T3P3Tony

This post is deleted!

SputnikOC3d

@T3P3Tony / @Phaedrux - any chance someone could look this over real quick and at least tell me where to look to get the dwc installed on my sd card - so I might begin to try and configure a new sd card.

My other related post to this machines issues has now gone 5 days now - with zero reply. Ive done my fair share of google and forum thread searching for the answers as well.

SIam

@sputnikoc3d Have you tried to read the SD-Card with your PC ? If yes can you see the files on it?
I would make first a new SD-Card, maybe your old one have a defect. Here you can find how you can set up a new SD-Card https://duet3d.dozuki.com/Wiki/SD_Card#Section_Creating_the_file_structure

SputnikOC3d

@siam - Thank You.

I did try and read the old factory supplied 8 GB SD card. Windows 10 in a pc card reader - tells me its unreadable or unformatted.

In the 20 some -odd searches I did on the doczuki till 2 am, for stuff like the link you sent I got nothing remotely close to that url - guide - Uggghhhh ... Guess I was getting referenced to the pages that help you fix or update an existing working and previously formatted SD Card. Didnt see links from those to the one you posted which might be smart for future reference and ... it might be wise to have someone review the texts above and massage that language a bit to make it like crystal clear for people. When following docs in unknown territory - people tend to NOT make assumptions and read docs and take them very literally - and dont imply or impune guesswork in the process. That said these docs should leave no room misunderstanding.

As well as indicate where and how to get all needed file to operate the machine onto the sd card
DWC included.

Guess I get to start all over fresh from scratch. FUN.

SputnikOC3d

@siam - another thing ... The RED LED for Diag mode is still on after several reboots and or attempts at removing the sd card and pressing the reset button.

My machines last moves were to home z with the bl touch pin out and down and I estopped it ...

Maybe its in diag mode as it finds no confi.g et al ...

SIam

@sputnikoc3d
~~It seems to me that you have pressed the erase button on your duet, in this case you should follow this docu to fix this issue~~

When the LED for Diag is lit, then is the duet board in program mode

https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_2~~

SputnikOC3d

@siam - pretty sure mine has a soft reset button and the erase is a jumper - no ?

SIam

@sputnikoc3d forget my last posting the firmware seems to run, so it will be make sense to create a new SD-Card

NightLonk42

Any chance this is a RatRig build?

SputnikOC3d

@nightlonk42 - No Caribou / Zaribo bedslinger