Quote:
Originally Posted by charrisTTI
Can the firmware update process leave the jag in a "ready to die" state? After updating the firmware on each of the devices, I used bdc to confirm that the version and type of software was correct for each module. The robot then had new code loaded and was driven for 30 minutes to 45 minutes. After turning the robot off and then on again the Jaguar at the end of the chain (with terminating resistor installed) failed to start. Was it already gone, just waiting for a power cycle to reveal the problem, or does something get sent on the bus which causes a problem, or is it a power on glitch. If I use these same jaguars (ver 89) in PWM mode, could a power cycle cause them to go bad. Should we switch back to Victors? The robot goes in the crate tomorrow.
What is the difference between recover, update from the command line, and boot from the command line? Can I recover a brown jag connected to a black jag?
|
What do you mean by "failed to start." Does it blink at all or is the LED dark? Was this last Jaguar gray or black?
Recover pushes out firmware to any Jaguar on the bus that is stuck in the boot loader. That is why it is important to only use recover with one "bricked" jag at a time. Update sends out an update to a specific Jaguar based on its ID. It is not recommended to update firmware on a large CAN network on the robot. You should connect to each Black Jaguar individually, or a Gray Jag through one Black Jag.
You can recover a Gray Jag connected to a Black Jag.
-David