Duet 3 Diag Light Dim & duet3 unresponsive



  • Hi There -

    I've been struggling back+forth with trying out the 3.2 betas, back and forth, but after a few attempts to update/downgrade (I've cycled between 3.1.1/3.2beta1(or 2) a few times in the last day) somehow my duet stopped talking to anything w/out me physically touching things.

    So, I go and check it out, the Diag+ethernet lights are dim (and constantly) lit. Crap, I think, as I reset the power. Nope, still not getting a blink. Just constant dim light. DCS+DSF will not talk to it. All of the voltage-status lights are fully lit, matching the LED brightness of my 3HC that seems to be working normally (blinking panic that no CAN connection exists)

    Things I've done/noticed:
    Unplugged pretty much everything that moves (that's plugged into the duet 3, I have a duet3hc that does all of the tools)
    Checked resistance of the VSSA fuse - 0.000 (also did a cont check, beeped at me)
    Checked Voltages of 5V and 3.3V - both strong
    Tried erasing flash and flashing via bossa - doesn't recognize it.
    Lights up if 5v not enabled but plugged in via USB. Still dim on the diag light/ethernet light.
    I use an ATX power supply - previously, it would not stay powered until the rpi was booted the full way up (and hold the PS_on pin on to keep the PSU on) Now, the PS_on pin is held and it will stay on as soon as the duet power lights power up. Weird.
    Can't find warm components- touched about everything that looked like a mosfet/power related on the board (topside only)
    Inspected components visually for scorch marks - none found sofar

    Could use some help as I'm a bit baffled. I have a multimeter and a 4-channel oscilloscope if needed.

    Luke



  • If you don't get a bossa port after erasing the flash (presumably with the jumper?) then unless the usb port(s), cable or host is faulty the cpu isn't working so if the 3.3v rail is okay then most likely faulty cpu.

    I would have tried it stand-alone before erasing the flash, but again, with no bossa port when there is no pi or sd card is "no bueno".



  • @bearer said in Duet 3 Diag Light Dim & duet3 unresponsive:

    If you don't get a bossa port after erasing the flash (presumably with the jumper?) then unless the usb port(s), cable or host is faulty the cpu isn't working so if the 3.3v rail is okay then most likely faulty cpu.

    Yep Jumpered it, attempted several times with resets.

    I would have tried it stand-alone before erasing the flash, but again, with no bossa port when there is no pi or sd card is "no bueno".

    Yeah, I probably? should have tried that standalone, but I'm very used to having the Pi being the driver, its never run standalone (as I use a HDMI touchscreen for interface)

    I also concluded that the CPU probably let out the magic smoke somewhere as well 😞

    Luke



  • Alright - after chatting around with some others, it appears that the duet 3 is EXTREMELY picky when it comes to USB cables - I disconnected every non-running device in the house from its microusb cables, and on the 13th cable IT CONNECTED - on one of my sketchier ones, hilariously. jank.jpg
    Its back and chooching. Sorry for the fuss.



  • You're not the first to have had success after trying more than one cable, but I think 13 is a new record! (And clearly not such an unlucky number!)

    I'd be very interested to see the result if you were to repeat the testing of all 13 cables; to see if there is a difference establishing a serial connection to the running firmware as opposed to the bossa bootloader just because it sounds rather extreme.



  • @Luke-sLaboratory How did you manage to get beta 1 specifically installed? I've been trying to get DSF to downgrade from beta 2 to beta 1 without success due to dependency errors.
    Any ideas?



  • iirc he cloned a sd card with beta1

    @jay_s_uk said in Duet 3 Diag Light Dim & duet3 unresponsive:

    dependency errors.

    i poked that one as well, seems to be something weird going on with 1, 1-1, 1+1 and some of them depending on 2.



  • yea, its a bit of a pain for the LPC/STM lot as we're still on beta 1 at the moment.
    The dependency errors are preventing new users or users who accidentally ran updates from using beta 1.
    Sorry for hijacking the thread btw



  • @bearer I'm a bit miffed at it myself, I had used 6 high-quality cables before writing the post, never heard the windows "I FOUND THE THING" or any other indication that it could talk.

    @J-boy
    No problem - hijack away!
    I've been using DuetVersions by danal to flip between all of them.

    https://github.com/DanalEstes/DuetVersions

    I have scripts now set up for 3.1.1 stable so its two-click to revert to known good for me.



  • @Luke-sLaboratory i used Danals script too but I have yet to get beta 1 to install


  • Moderator

    alt text


Log in to reply