Is my Duet wifi board really dead?



  • Hi all,

    Have been running my duet wifi board, updated with RRF3 successfully for a week. then unexpectedly it just stops.

    current status:
    Some LEDS light up, enstop LEDS switch on/off when triggered. Paneldue works but does not show warning messages from config.g file so I assume its not booting to that. Can type gcode into console but no effect.
    No wifi connection to my network.
    Have tried connecting to USB, windows computer can see USB device but says its not working. Correct driver installed and previously worked.
    Tried erasing firmware, no change in symptoms.

    Anything else I should try ?

    Thanks



  • it'd help to know which LEDs light up.

    also https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respond



  • @percyb said in Is my Duet wifi board really dead?:

    Have tried connecting to USB, windows computer can see USB device but says its not working. Correct driver installed and previously worked.
    Tried erasing firmware, no change in symptoms.

    I had a problem recently when updating my second Duet WiFi board from 2.05.1 to 3.1.1. I followed the same procedure that I used for the first Duet WiFi board and that board updated without incident. However the second board went to the phase where is says that the new firmware is installing and that never completed. Ultimately I had to erase the firmware and use the Bossa utility to install 3.1.1.

    But that didn't go smoothly as after the erase and reset of the board no COM port appeared. I reinstalled the USB drivers to no effect. I tried erase and reset again to no effect.

    So I rebooted the computer (Windows 10) and the COM port now appeared, Bossa was able to connect, the firmware was installed and all is now good.

    So when in doubt reboot Windows.

    Frederick



  • @fcwilt said in Is my Duet wifi board really dead?:

    So when in doubt reboot Windows.

    👍

    That should be a t-shirt!

    👇 👌


  • Moderator

    f56582ca-6a61-415f-8e55-b29a05af9cbe-image.png

    Sorry.


Log in to reply