Quote:
Originally Posted by galewind
We blew a jag, which caused our system to go batty...
My HYPOTHESIS is that since it was on our CAN network, it caused our 2CAN to go haywire, which caused it to stop responding. This caused (or something else caused) the cRio to max out its CPU cycles and stopped responding.
In the meantime, our turret (which is on a separate victor) started turning, and the system wasn't watching our potentiometer voltage go beyond its desired limit. Thus, we sheared our turret belt and the potentiometer coupling (just a piece of surgical tubing).
|
When you attempt to use CAN to communicate to a blown Jag it blocks the thread until it timeout (default is 0.02sec which is 1 normal teleop cycle). I recommend running all CAN Network communications in separate threads for each mechanism and out of your main DS communication thread (so that it doesnt delay other functions waiting for a response). In Labview, this usually means placing these commands in separate loops in the Periodic Taks VI.