Jaguar Reset to Address 1

[charrisTTI]

Programming language is java; using the serial bus to connect to the black jag; six motor controllers installed with ids 10, 11, 12, 13, 14, 15. Robot is driving fine. Put robot back on the cart, and attached camera wiring. Robot would not run anything. Exception thrown from Jaguar init function when constructing the CANJaguar class. Disconnected serial bus from cRIO and attached to pc. Ran the comm application. Now had ids 1, 10, 11, 13, 14. Turns out that two jaguars had "forgotten" their id and reverted to 1. First jag to be initialized was 11, but init of 11 would throw the exception. My best guess is some sort of "static discharge" event, although I cannot say for sure that one occured. Any other ideas?? I would hate for this to happen in the middle of a match.

[MikeE]

Originally Posted by charrisTTI

Programming language is java; using the serial bus to connect to the black jag; six motor controllers installed with ids 10, 11, 12, 13, 14, 15. Robot is driving fine. Put robot back on the cart, and attached camera wiring. Robot would not run anything. Exception thrown from Jaguar init function when constructing the CANJaguar class. Disconnected serial bus from cRIO and attached to pc. Ran the comm application. Now had ids 1, 10, 11, 13, 14. Turns out that two jaguars had "forgotten" their id and reverted to 1. First jag to be initialized was 11, but init of 11 would throw the exception. My best guess is some sort of "static discharge" event, although I cannot say for sure that one occured. Any other ideas?? I would hate for this to happen in the middle of a match.

We had exactly the same thing occur last night. One of the grey Jags reset to ID 1 during a battery change. I'm also assuming a surge or static event, but it's concerning.

[charrisTTI]

Yes, both of the ones which reset on us were the old style.

[Radical Pi]

Same thing happened here. Was doing a test drive, noticed one side of the bot was slower than the other and one of the jags was blinking yellow. I have absolutely no idea what caused the reset. I originally thought I had just missed that jag in the original setup of the bus, but now that other people had this problem I think it wasn't just me.

btw when you setup the jag that reset did you daisy-chain to that one from the black jag? I remember the one that reset was the only one we didn't have a cable long enough to reach from the black jag, so I had another grey one on the bus.

[MikeE]

Originally Posted by Radical Pi

Same thing happened here. Was doing a test drive, noticed one side of the bot was slower than the other and one of the jags was blinking yellow. I have absolutely no idea what caused the reset. I originally thought I had just missed that jag in the original setup of the bus, but now that other people had this problem I think it wasn't just me.

btw when you setup the jag that reset did you daisy-chain to that one from the black jag? I remember the one that reset was the only one we didn't have a cable long enough to reach from the black jag, so I had another grey one on the bus.

As long as only one Jag reset to 1, then daisy chaining works. We had it happen twice yesterday, once earlier in the day when the students were working with the robot (I was a little sceptical of the report at first) and also later in the evening when I saw it with my own eyes.

[Radical Pi]

Out of curiosity, what are the IDs of the Jags that reset? Our's was 6.

[MikeE]

Originally Posted by Radical Pi

Out of curiosity, what are the IDs of the Jags that reset? Our's was 6.

IIRC it was 10 or 11.

[dyanoshak]

For those of you who are having this problem. Are you able to recreate it reliably?

Does it happen during a specific window of time during robot operation?

Just to be clear, has ID resetting only been seen on Gray Jags?

If you are able to recreate the problem reliably, what do the Jaguar LEDs do before, throughout, and after the event that causes the ID to reset?

I am trying to figure out if this could possibly be a software problem. For example, could the CRIO be sending out a rogue Assign ID command?

Your help is greatly appreciated!

-David

[Radical Pi]

As I remember, I had set the IDs and tested the system, and then the electronics board was mounted on the bot. There was never any power to the system until we powered on to download new code and test the bot. When the robot was used for the first time, the jag had been reset.

In terms of the LED, the only thing I noticed was a blinking yellow

[biojae]

Originally Posted by dyanoshak

For those of you who are having this problem. Are you able to recreate it reliably?

Does it happen during a specific window of time during robot operation?

Just to be clear, has ID resetting only been seen on Gray Jags?

If you are able to recreate the problem reliably, what do the Jaguar LEDs do before, throughout, and after the event that causes the ID to reset?

I am trying to figure out if this could possibly be a software problem. For example, could the CRIO be sending out a rogue Assign ID command?

Your help is greatly appreciated!

-David

On my little test board, i have 5 black jaguars and 2 gray jaguars.
Bl-Bl-Bl-G-Bl-G
2 3 4 5 6 7

I have been able to reproduce this twice.
The first time, the power to the bus was off for about 6 hours. The Gray jag with ID 7 reset itself to 1.

The second time, the power was off for slightly more then a day.
This time, both gray jags set themselves to ID 1 leading to an interesting time trying to re-assign IDs.

Upon power up, the jags just blink yellow happily, no weird blinks.

[duane]

We had two Jaguars reset this evening. We attributed it to anamolies related to the recent updates where everything had to be updated including the cRio. This meant that the serial jaguar driver was removed. We've restored everything now.

Both the Jaguars that reset were gray. We only have one black.

We will certainly be keeping an eye on this problem. I have high hopes for CAN but the problems we are seeing are a bit disconcerting.

[dyanoshak]

Hi all,

We just uploaded new Jaguar firmware (89) that should address this problem.

Please check this thread out:

http://www.chiefdelphi.com/forums/sh...d.php?p=923925

-David