Quote:
Originally Posted by rrossbach
Sorry if this is a dumb question, but I'm not clear on what behavior you're seeing.
How many Jaguars do you have connected to the CAN bus? If it's only one, and you are just seeing an enum response with device id 0, have you tried resetting the id of that Jag to something >=2 via bdc-comm? If not, follow the steps on page 10 of the bdc-comm user's guide and let us know the results.
If you still have multiple Jags on the CAN bus, let us know what you see in bdc-comm.....do you see all the Jags except the one with device id 0?
You may just need to assign a new id to the Jaguar that currently thinks it is id 0.
- Ron
Team #2607 controls mentor
[EDIT: to answer your question, the enum responding that there's one device with id 0 is (I'm almost positive) a valid response, provided that's the actual situation on the CAN bus]
|
Well, I've tried resetting the Jaguar's ID, but it has no effect. I even tried replacing it with a different black Jaguar, but no change.
I'm pretty sure 0 is not a valid ID for a device on the CAN network, but I don't know if the host might appear as having an ID of 0 (regardless of whether the CAN bus itself is working or not).
When I connect another Jaguar, the enumeration still only reports a single device with an ID of 0.
Currently I am working with the BDC-COMM, and a USB to Serial device (Keyspan brand). Once I get that working, I'll move back to the cRIO.