Back again: finding a solution to an unresponsive board.
-
This post is deleted! -
This post is deleted! -
This post is deleted! -
This post is deleted! -
I see you've made some posts and then deleted them. Were you able to get the board to respond?
-
@Phaedrux @droftarts Good morning From Ms. Thanks for your help first and foremost, having you all a few clicks away has helped me get this far. @Phaedrux Yes i have had some progress. My board wouldn't jump when it was plugged via usb, so i plugged it back to the VIN and did the reset again. This time the diag light kind of blinked once. Unplugged it from there and went back USB and it was found via BOSSA software then flashed the 3.5.3 release. Now I'm back into the DWC this morning, I figure I have to tune everything once again since its been so long. The last time I got this far, my bed heater kept faulting even after the PID tune and programing. At this point i'm im going to put a new thermistor on the bed and do a new test all together just to be sure it's alright down there. I've been following a few threads about it here; https://docs.duet3d.com/User_manual/Troubleshooting/Heater_faults
https://forum.duet3d.com/topic/26122/heater-fault-on-heated-bed-because-it-s-rising-to-slow/54
-
@Phaedrux
the fault
Heater 0 fault: temperature rising too slowly: expected 2.32°C/sec measured 0.21°C/sec -
A common reason for heater faults are that the tuning results are not saved after the tuning. The reults must either be saved with M500 and reloaded with M501 in config.g or the results must be manually copied into config.g.
-
@Phaedrux Okay, so ill run another and be sure to save with M500. The M307 generated after the tune isn't saving it anymore?
-
The M307 that it generates must be manually added to config.g. Or using M500 saves it to configoverride.g and M501 loads that at startup.
