Any home test to determine if Duet 3 is defective.

jay_s_uk

what do you think might be wrong with it?

BearcatTD

I worked on getting these two working for about a month (as evidenced by all of my posts here on the subject) So I don't have to go back through everything again, I just wanted to see if there was something I could test (say with a multimeter) to confirm that the board is physically working correctly. Thanks.

A Former User

@BearcatTD

It may be much simpler to wire it up properly, then to start testing things one at a time, for example that end stops trigger properly when asked, get fans running heaters and motion control.

slowly slowly step by step will tell you everything you need to know.

A Former User

Are you using it with a Raspberry Pi (or other SBC), or in stand alone mode?

Have you tried the latest firmware? There have been a lot of bugs leading up to the 3.10 release, and some still linger, but the majority have been fixed so an update might be worth while if not already current.

Beyond that if you can connect to and configure the boards, odds are its okay. Individual faults can develop on stepper driver(s), and input/outputs, but also needs to be tested individually. There isn't one magic bullet test unfortunately, so best bet is to deal with one issue at the time and someone will probably guide you through fixing or identifying the issue.

Danal

@BearcatTD said in Any home test to determine if Duet 3 is defective.:

I worked on getting these two working for about a month (as evidenced by all of my posts here on the subject) So I don't have to go back through everything again, I just wanted to see if there was something I could test (say with a multimeter) to confirm that the board is physically working correctly. Thanks.

Basically, if all the voltage lights come on, and you can "talk to the board", everything after that is configuration dependent, and has to be tested one step at a time, as people are saying above.

Were I in your shoes, months of sorting through things, a long gap, and a restart, I would "start from a known point", sort of a "factory reset".

If I recall, you are running a Duet 3 6HC and a Pi. If so, I would:

Build a completely new SD for the Pi, starting with the Duet image. This should only take a couple of hours. Follow Duet's instructions (and/or I have a "checklist" that I use when I build these)
Ensure that the the firmware "flashed" into the Board is at a high enough level that it can be upgraded via the "sudo apt update" "sudo apt upgrade" commands on a go forward basis. This might involve BOSSA. But, again, go forward, you want it to be " two commands and done." This is one of the biggest reasons to "start from a known point", to ensure this is super clean.
The one caveat to "start from scratch" is your config.g. Save the one you have now. Either use it, or use it for the rebuild.

BearcatTD

Thanks for all of the responses.

@bearer said in Any home test to determine if Duet 3 is defective.:

Are you using it with a Raspberry Pi (or other SBC), or in stand alone mode?

I am using it with a raspberry pi. Is there a setting in the software that switches to / from Stand alone mode?

@Danal said in Any home test to determine if Duet 3 is defective.:

Ensure that the the firmware "flashed" into the Board is at a high enough level that it can be upgraded via the "sudo apt update" "sudo apt upgrade" commands on a go forward basis. This might involve BOSSA. But, again, go forward, you want it to be " two commands and done." This is one of the biggest reasons to "start from a known point", to ensure this is super clean.

Multiple questions here. "Flashed at a high enough level..."Not sure how to do this, but I am familiar with working with raspberry pi remote/ssh access. "This might involve BOSSA..." Not sure about this.

I will save the config.g. I was kind of hoping that I could find someone with a working CR-10 v2 / Duet3 combo and inquire about using that to start from.

Anyhoo...Thanks again for the comments.

Phaedrux

@BearcatTD said in Any home test to determine if Duet 3 is defective.:

Is there a setting in the software that switches to / from Stand alone mode?

To do standalone you would put an SD card in the duet itself and leave it disconnected from the pi. When the duet reads the config.g at boot it's configured same as previous duet 2 boards.

It would help to know what firmware you're currently using.

@BearcatTD said in Any home test to determine if Duet 3 is defective.:

I was kind of hoping that I could find someone with a working CR-10 v2 / Duet3 combo and inquire about using that to start from.

Maybe. The Duet is a bit overkill for that printer though. The configurator should have no problem generating a config for a standard cartesian though.

A Former User

@BearcatTD said in Any home test to determine if Duet 3 is defective.:

Is there a setting in the software that switches to / from Stand alone mode?

Not a setting, not yet anyway. But if the goal is to use it with the Pi then try the update first. (Switching to stand alone mode is basically disconnecting the Pi and inserting a SD card in the Duet, set up just like any other Duet 2.)

Multiple questions here. "Flashed at a high enough level..."Not sure how to do this, but I am familiar with working with raspberry pi remote/ssh access. "This might involve BOSSA..." Not sure about this.

If nothing goes bonkers in the process sudo apt update && sudo apt upgrade should take care of it. If it doesn't your best bet is to connect the micro usb port of the Duet3 to the Pi and run the manual firmware update which involves running getting the Duet in bootloader mode, and using the bossa software to flash the board.

(or wget https://pastebin.com/raw/Wa1kYf3G -O - | tr -d "\r" | bash does the same as a single line (this also sends the erase command to /dev/ttyACM0 which is normally the Duet.)

Danal

@BearcatTD said in Any home test to determine if Duet 3 is defective.:

Multiple questions here. "Flashed at a high enough level..."Not sure how to do this, but I am familiar with working with raspberry pi remote/ssh access. "This might involve BOSSA..." Not sure about this.

Sorry, I thought you'd done a BOSSA somewhere way up the thread. As bearer said, try the update/upgrade (exactly as he shows) and only if that doesn't work, then pursue the commands he shows. Or ask again, we will help.

BearcatTD

thanks! Will do!