Jaguar yellow blinking light after updates

[Team 691]

After updating the DS, cRIO, and labView to the latest versions, and attempting to run the code in the "Joystick Motor Control in 10 Minutes" video, we have seemed to lose connection to the jaguars. They worked fine in the benchtop tests, but are not working now that everything is updated. In labview, we are receiving input from the joysticks. Tried new pwm cables and jaguars...no dice.

Cheers

[Mark McLeod]

It all worked for your bench test after the firmware was updated on both the DS and cRIO?

Then it'd have to be how you downloaded your code example.

What steps did you take to download the example code?
Did you use the "Run" button or did you download?

[Team 691]

We did not do any bench tests after both the DS and cRIO were updated. It was our understanding that after the DS was upated, it could no longer run the OTB benchtop tests.

As for the code, it is exactly as it is in the video, with the exception of the removal of the watchdog class being set to false (which is default now, so ive read).

To run the program from labview, we hit the "Run" button on the far left bottom. Arrow goin to the right. Should we be using the download button? I thought that was only for remote testing. We still have the DS wired to the laptop.

Also remember that the joystick input is being read in the code, so it is at least functioning partially.

[Mark McLeod]

A bench test was ready to run after the firmware updates.
It's just nice to be able to know it worked right before you made a change.
It wasn't the same as the OTB code, but you can see the test called out in the Control System manual. It's never too late either to go back and bench test it, by formatting the cRIO once more.

Using the run button is okay. It tells me where you are.
The IP address should be 10.6.91.2 rather than 10.0.0.2.
Can you post the vi you created, so we can check it?

Is the status light on the Digital sidecar a solid green or is it blinking? It's the LED by the 2-pins to the right of the 12v power connector.

What's the status on the DS (Battery: No comms, No code, or a battery voltage)?

P.S. The LabVIEW palette has changed a bit since that video was made, so I'd like to see what you chose as substitutes.

[Team 691]

Well, it seems that everything is working now. Unfortunately, only one of our 4 jaguars seems to work :\ Since the chances of getting only 1 out of 4 working jaguars is pretty low, is there a way we might have disabled the jaguars that don't function? We have not touched or removed any of the jumpers on them yet.

Thank you for your help by the way, we appreciate it greatly.

[Mark McLeod]

I'd think it'd be extremely unlikely that you'd be unlucky enough to end up with 3 out of 4 Jaguars broken out of the box. Although, 330 did get one Jaguar missing the PWM connection, but that was pretty obvious.

What are the symptoms of the broken ones?

If you're getting blinking yellow...
Unlike last year, this year the Jaguar's will blink unless code is explicitly setup to drive them. So PWM's 2 though 10 will give you a blinking yellow light with the code example you're using.
Since you have at least one working you can plug the working PWM and cable into each of the others as a test.

[PHSRobotics]

We are having the same blinking yellow jaguar problem but our status light on the digital sidecar is BLINKING. Any thoughts on that?

[Mark McLeod]

If the Digital Sidecar status light (RSL) is blinking, then the Jaguars will be forced to blink. That light means the cRIO has been disabled.
The RSL takes precedence over any Jaguar staus light.

The DS blinking can have several causes:
-- The DS disable obviously
-- It could also be because no code is running on the cRIO (indicated by a DS Battery status of "No code")
-- Or by failing to feed the Watchdog regularly (also indicated by a DS Battery status of "No code")
-- Or by a firmware mismatch between the DS and cRIO (indicated by a DS battery status of "No comm")
-- Or failed connection, wireless or wired, between the DS and cRIO (indicated by a DS battery status of "No comm")

[Russ Beavis]

RSL light decoding -
http://decibel.ni.com/content/docs/DOC-3120

Has anyone used the Diagnostic Window application yet? This could be a very useful application to help with debugging such problems.
http://thinktank.wpi.edu/article/138

Russ