Back again: finding a solution to an unresponsive board.

Phaedrux

Please disconnect all cables and devices (including SD card) from the board and connect it via USB to your computer.

What LEDs light up on the board?
Does anything show up in device manager?
In the top menus of device manager check the Show Hidden Devices option.

Can you show a photo of the board when doing this?

gabrealek

@Phaedrux hello. My apologies for the late reply. Work has been working lately. I just plugged the board in and went to click show hidden devices and the board still isn't coming up

.

droftarts

@gabrealek Try the following:

Mount the Duet a bit better. It looks like it is cable tied to a plastic plate. It may be enough that something is shorting out behind. Also check for any shorts (metal debris stuck between pins) on the front and back of the board. Post pictures of both sides of the board if you're not sure.
Check that the reset switch is not stuck in. It may be stuck in a reset loop if it is.
Do the erase procedure again. Though I can see the red diag LED is on, and there's no SD card, it's possible the firmware is stuck. Put a jumper on the erase pins, apply power, wait a couple of seconds, remove power, remove jumper from erase pins.
Check the USB socket is not damaged, or poorly soldered. See https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#sd-card-socket
When powered, does anything get hot? Specifically the main processor, the SD card holder or the WiFi module. They shouldn't get more than luke warm to the touch.
Try different USB cables, as many as you have. Many USB cables are charging only cables, and the data lines are not connected. Usually cables with a thicker cable are more likely to be power and data.
In case it's a Windows issue, check if you can see the Duet on another computer or Raspberry Pi, or use a Linux live USB. See the Linux tabs here to check if it's seen: https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet#h-2-connect-your-duet-via-usb

Let me know if any of those work.

Ian

gabrealek

This post is deleted!

gabrealek

This post is deleted!

gabrealek

This post is deleted!

gabrealek

This post is deleted!

Phaedrux

I see you've made some posts and then deleted them. Were you able to get the board to respond?

gabrealek

@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

gabrealek

@Phaedrux
the fault
Heater 0 fault: temperature rising too slowly: expected 2.32°C/sec measured 0.21°C/sec

Phaedrux

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.

gabrealek

@Phaedrux Okay, so ill run another and be sure to save with M500. The M307 generated after the tune isn't saving it anymore?

Phaedrux

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.