CAN "GetStatus" Function not working

[Efiske]

Hi,

We just started using CAN this year, and we're running into some problems. The CAN Jaguar is able to move motors just fine, but returns nothing when we try to get information about it using the Get Status VI (We're using LabView). None of the CAN examples that involve getting a value from Get Status seem to be working (Position Control example, Current Control example, Speed control example, etc.).

The normal motor palette Get Output works fine, and each Jaguar responds properly when hooked up to the BDC-COMM. What could be causing this error?

Thanks in advance,
Team 2367

[EricVanWyk]

GetStatus has a required input that indicates which statuses you are interested in. What have you selected?

[Efiske]

I used the default example code, which should have that constant built-in... e.g. the encoder example has the "Speed" option selected for Get Status.

[kuh-nig-its-EL]

Team 1939 is also experiencing this problem. We used all the same components as were in the examples on CAN. Any help on this front would be very appreciated. This component is vital to our robot.

-Ethan Lopez

[dakaufma]

Team 449 is having this problem as well. To give a few more details:
--It used to work on our test board, but doesn't now. On the other hand, some encoders have changed, some encoder wires have changed, the jaguars have changed, the code has changed, and the cRIO has changed, so it could still be any of a variety of hardware problems.
--We can read limit switch values correctly, but get 0 for position and speed (yes, we set it to use a quadrature encoder and set the appropriate number of counts per revolution). We haven't tried reading voltage, current, or temperature.
--At some point we couldn't control the jaguars in speed/position mode with BDC-COMM, but I'm not sure if that is a current problem or if it has been resolved.
--One jaguar (the turret) does seems to be reading the encoder and responding appropriately. Our drive jaguars seem to be reading the encoders incorrectly, but we think that is a separate problem (we are using one encoder per side, so we have to splice the encoder cables to two jaguars). None of the jaguars report non-zero speeds or positions (note that GetStatus doesn't return errors, just zeros). We'll see tomorrow if the flywheel has this problem as well.

Has anyone made any progress on this issue?

Thanks for your help.

[Todd]

Team 1071 is also having this problem. Speed values are output correctly over BDC-COMM and Current data is reported properly through the cRio, however when attempting to read speed values over our cRio the value returned is simply always 0. No errors are reported from the GetStatus vi, the values are just always 0. We've tried this on numerous jaguars with numerous encoders, numerous wiring, etc. We've selected quadrature encoder and set the correct CPR. I've confirmed with the GetSpeedRef vi that the jaguar is being properly configured, and I can't really debug much further than that.

Based on some of these other comments I can't help but speculate that there's something wrong with the current firmware or Labview CAN libraries?

Is there anyone that is able to access speed data from an encoder through a CAN Jaguar?

[dakaufma]

Is there anyone that is able to access speed data from an encoder through a CAN Jaguar?

We got it to work for our flywheel on our test board. Since I last posted I found another CD thread (http://www.chiefdelphi.com/forums/showthread.php?t=101475) that I think relates to our problem. I don't think we are using old encoders, but like the original poster in that thread we were using grey jaguars when GetStatus worked. We're going to test it tomorrow.

Hope this helps.

[Efiske]

Using grey jaguars fixed our problem... which is really weird.

Everything in GetStatus works now :/

Thanks everybody!

[dakaufma]

Problem solved (ideas from this CD thread: http://www.chiefdelphi.com/forums/showthread.php?t=101475). Switching to newer encoders didn't work for us, but switching to a grey jaguar did.