Quote:
Originally Posted by Mark McLeod
Well, you can never go back to testing the OTB, so updating the cRIO will at least get you back to where you can debug the original Jaguar problem.
With the cRIO updated you'll get an additional status light on the Digital Sidecar to help tell you what's happening. A fast blink means no communication, a slow blink means it's in Disabled mode, and a solid light means it's enabled in either Teleop or Auto modes.
One reason the Jaguars will blink is if they aren't connected to an activated PWM output. With the default code you're now downloading I think just pwms 1&2 on the first cRIO digital module are enabled. I was with a team last night where a third party must have moved the DB37 cable to the second module and no one had noticed. As a result their Jaguars were blinking too.
There are lots of combinations that will prevent the code from operating as advertised (including failed hardware), so work your way through triple checks without introducing new complications.
|
I am getting a "no communication" blink on the Jaguars - regardless of the position of the enable switch on the DS
If I connect my laptop to port 1 on the cRIO, I can ping 10.0.0.2. If I connect my laptop to either jack on the DS, I get no response pinging 10.0.0.5 (or 10.0.56.5 if the team number is changed).