|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Jaguar communication issue
Check the connection between the PWM cable and the Jaguar. We have had problems with this before, and as a result, we always hot glue the cables to the Jaguars, as driving in a match could shake the PWM cables loose.
|
|
#2
|
|||
|
|||
|
Re: Jaguar communication issue
We also hot glue the pwm cables. This year we even made a lexan casing that went around the electronic part of our robot. Because it was clear, the refs and everybody could see our electronics, but the tubes couldn't get stuck in the cables. The casing had a hole for the light, and a slit where the power switch was available. We put velcro around it, so it easily came on and off.
|
|
#3
|
|||||
|
|||||
|
Re: Jaguar communication issue
I've had a busy last week(two robotics demos, the offseason MARC competition), but I tried the code with a different cRIO, Digital Sidecar, and Jaguars. I had the same result happen where the PWM channel seemed to be allocated incorrectly, so I talked through my drive code with a recently graduated programmer. We isolated the issue to a wrongly attached wire, automatically sending null commands to the Jaguar. So, that was the issue after all.
Thanks a lot for the help anyway. I've learned a bit about debugging, and hopefully I'll be able to bring this knowledge forward into my next project, next build season, and beyond. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|