Duet 3 6HC dead, I is sad (fixed!)

kb58

Well it was fun while it lasted...

Was gradually bringing up a cubeXY printer, checking out all the steppers and switches. Things were going well, but while updating config.g, hitting SAVE this time didn't complete the write and everything hung up.

All Ethernet communications stopped, and the green LED on the Ethernet connector went out. The four power LEDs on the board remain lit, and the STATUS LED continues to blink slowly, but other than that, it's completely dead.

I disconnected everything except power and tried connecting a PanelDue, but it failed to connect as well.

I erased the board and the Status LED is very dimly lit. BOSSA was used to reload code and the STATUS LED started flashing again, but all comms remains dead. The PanelDue also does not connect. At the time of failure, power had been on for a while, and no steppers were running, so it's doubtful that it's power-related, but more likely, "infant mortality."

The board (1.01a) is about a month old, is there any sort of warranty on them? Guess I'll contact Filistruder, sigh. Perfect timing, too, as I had planned to take off the week of July 4 to get the board fully up and running. Apparently not.

I guess I'm writing in the vain hope that someone has a miracle solution, but with a background in HW and SW, and currently working in Field Support, I know what this probably means

Phaedrux

It sounds like you're still able to flash it with firmware, so that's good. Can you send commands to it over USB via YAT?

The paneldue will only connect when the command to set the baud rate and port is sent. M575 P1 B57600 S1

Try working through this guide: https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respond

kb58

@phaedrux Okay, thanks, I'll look through that guide.

BTW, what specific binary files have to be loaded? I loaded only the "firmware_MB6HC" binary (I'm running the board in standalone mode). Are any other binaries required for a from-zero code load?

Phaedrux

That looks like the correct firmware file. The bootloader is already in there and can't be damaged so it should boot up fine once the firmware is flashed. The pulsing diagnostic light is a good sign.

We need to know if you can still communicate with the board over usb terminal. If it can accept commands than it may just be an SD card problem.

kb58

@phaedrux Just connected with YAT, but haven't tried sending any commands.

kb58

@kb58 FWIW, the SD card was installed once at the start and never removed nor touched, but I hear you.

kb58

@kb58 Randomly, I tried querying the board with "M27" (SD printing), and it did reply with "Not SD printing", so that's something.

Also tried M119:

Phaedrux

Send M115 to see what firmware is flashed.

Send M122 for a full diagnostic report.

Send M552 S1 to enable networking and see if the port lights up.

Send M575 P1 B57600 S1 to enable the paneldue.

If you pull the SD card and put it in a PC is the file system still intact?

kb58

@phaedrux

kb58

@kb58

kb58

@kb58

Interesting... the green network LED is blinking now... huh.

kb58

@kb58

This worked as well. Confirmed that the PanelDue was NOT connecting, entered the above string, and it connected.

What does this all mean?

kb58

@kb58 You asked, "If you pull the SD card and put it in a PC is the file system still intact?"

Yes, there are a ton of files in there. I haven't messed with the SD card or added anything, but yes, the file structure seems normal. Not sure to go from here, but a huge THANK YOU for getting me out of the worst of this mystery.

Rebooting the board (unplugging the USB briefly) confirms that the ports are back to not working. Should I manually reenable and refresh config.g?

Phaedrux

@kb58 said in Duet 3 6HC dead, I is sad...:

What does this all mean?

Power off, pull the SD card and check it in your PC. It sounds like the SD card either isn't being read, or it doesn't have a config.g on it.

Phaedrux

@kb58 said in Duet 3 6HC dead, I is sad...:

Should I manually reenable and refresh config.g?

Check if config.g exists in the /sys/ folder on the SD card.

kb58

@phaedrux yes

kb58

@kb58 Oh now this is interesting... zero file size.

kb58

@kb58 Fixed!!!!!!!

Deleted config.g and renamed the backup to .g, and it's all working again. Wonder how that happened, but regardless, a huge thank you, phaedrux!

tecno

@kb58

Take a backup of your sys folder !!!

kb58

@kb58 For anyone else who has their controller freezing up immediately after editing config.g:

Apparently the existing file on the SD card is first erased, and then the edited file takes its place. If the write fails, the controller has nothing to fall back on, so config.g has to be rewritten via other means.