[Bug]: I erased the firmware by shorting the erase pins I installed driver files again from https://github.com/Duet3D/RepRapFirmware/blob/dev/Driver/WindowsDriverFiles.zip. I got the usual message after updating the USB driver with yellow triangle (right click, installed from the unzipped download (folder name WindowsDriverFiles) and it responded with "Unknown USB Device (Device Descriptor Request Failed). I have used the same USB cable that was working with YAT before I erased the DUet3 board. I use a powered USB hub. I see the little diag LED faintly lit, solid on, the bright red LED between USB socket and SD card and the green and red LEDs in the corner of the board on solid.

[jtreg]

Duet Forum Discussion Thread

https://forum.duet3d.com/topic/35958/erased-firmware-now-i-cannot-connect-via-usb/2?_=1719087556964

Which Duet products are you using?

• Duet2-Wifi
• Duet2-Ethernet
• Duet Expansion Breakout Board
• Duex2
• Duex5
• Duet2-Maestro
• Maestro Dual Driver Expansion
• Duet3-6HC
• Duet3-3HC
• Duet3-1XD
• Duet3-1LC
• Duet3-Tool Distribution Board
• Duet3-Mini5+
• Duet3-Mini2+
• Raspberry Pi or other SBC
• SmartEffector
• Magnetic Filament Sensor
• Laser Filament Sensor
• PT100 Daughterboard
• Thermocouple Daughterboard
• PanelDue
• Other
• None

Firmware Version

Reprapformware 3.1

Duet Web Control Version

N/A

Are you using a Single Board Computer (RaspberryPi) with your Duet?

• Yes I use a SBC.
• No I do not use a SBC.

Please upload the results of sending M122 in the gcode console.

M122 Report

Please upload the content of your config.g file.

Config.g N/A

Please upload the content of any other releveant macro files.

N/A

Details specific to your printer.

N/A

Links to additional info.

N/A

What happened?

Expected result driver to install so that I can connect to my Duet3 board

Observed result with "Unknown USB Device (Device Descriptor Request Failed).

Steps to reproduce Right click on driver (yellow triangle) press button "Update driver"

[jtreg]

Advised by Duet3D technical specialist to get a decent USB cable supporting high speed data transfer as the chip on the board requires high speed mode, this may be the cause of the problem. I will update here with result when new cable arrives.