Jaguars not passing CAN communications

[linuxboy]

Hi all,
So I made a post a while ago about only seeing the first Jaguar in the chain. I believe this is an extension of that issue, however I am not sure. I re-followed the CAN on a Budget document to the letter (last time we didn't crimp our own wires). Anyway I can get two Jaguars working on the bus (ID 1 and 2), however the third Jaguar (ID 3) cannot be enumerated. If I change its (ID 3) to ID to 2 and switch the wiring so that the Jaguar that had ID 3 becomes a drop in replacement for the one that had ID 2. This should be drop in replacement however, will not work unless it is first in line, and any Jaguars following it will not show up.
Basically I think I've isolated the problem to the Jaguars, the only problem with this theory is 5 out of 7 Jags are exhibiting this behavior, and I really doubt that I've managed to break 5 whole Jaguars. Are there any tests you guys suggest to diagnose / fix the problem?

Thanks,
Oliver

[Alan Anderson]

Rule of thumb: When you have a problem on a CAN bus, look for a termination issue at the other end of the chain from where the problem manifests itself. If the first couple of Jaguars work but any farther ones do not, check the termination at the end closest to the cRIO.

[jwakeman]

I have four black jaguars i want to include in my network. Right now I can only see one jaguar at a time. I am able to communicate with all four Jaguars individually but if I try to chain two together i only see the first in the chain.

Originally Posted by linuxboy

Hi all,
So I made a post a while ago about only seeing the first Jaguar in the chain.

Can you post a link for that thread here? It may be helpful to me.

Originally Posted by Alan Anderson

Rule of thumb: When you have a problem on a CAN bus, look for a termination issue at the other end of the chain from where the problem manifests itself. If the first couple of Jaguars work but any farther ones do not, check the termination at the end closest to the cRIO.

I made the cable to connect the rs232 port to the first black Jag. I included the terminating resistor in the CAN plug end of the cable instead of in the RS-232 plug. The cable is probably 2 or 3 feet long. Do you think this could be causing the issue i described above? I can explain my cable construction more clearly if required..

[linuxboy]

Hi,
Here is the old thread, I don't know that it ever got resolved.

You need a terminating resistor on both ends of the cable (the serial port end and the terminator end).

I managed to get it working by remaking the DB9 connector a couple times. I highly recommend this tutorial on it as it is pretty easy to understand.

Oliver

[jwakeman]

Originally Posted by linuxboy

You need a terminating resistor on both ends of the cable (the serial port end and the terminator end).

The following is from the MDL-BDC-24 - Getting Started Guide:

RS232 Cable Assembly
Follow these steps to complete cable assembly (shown in Figure A-4):
1. Take the Modular Adapter and cut the black wire as short as possible. This wire is unused.
2. Cut off the terminals on the Red and Green wires. Strip then solder the Red and Green wires
to the 100 resistor. Use a section of heat shrink to protect the resistor and solder connections.
3. Insert remaining terminals into the DB9 receptacle. Pin numbers are indicated on the plastic
connector body.
– WhitePin 3
– Blue2
– YellowPin 5
4. Slide the back-shell over the connector, then insert the modular cable to complete the
assembly.

This sounds like they only expect 1 terminating restistor to be part of the RS232 - CAN cable, at the RS232 end. I looked at the guide you linked to and it does seem they expect a resistor at each end of the cable..seems like a conflict here but the "Getting Started Guide" does look more official to me. I attached this document. I guess it makes sense that this cable should only contain one resistor. If i understand correctly you want one resistor at each end of your network. If this cable contains two resistors it seems you would end up with three total resistors once you add one at the tail end of you daisy chain..

[FrankJ]

Terminating resistor has nothing to do with the RS232 bus. It terminates the RS422 bus that is in the same plug. The other terminating resistor is in the unused port on the last Jag in the daisy chain (making a total of 2). The bus will mostly run without the terminating resisters, but will be subject to noise. It will also be the first troubleshooting question.

I found to get all the Jags to communicate that I had to power up the jags with them all connected & then restart the BCD-COMM com. A little concerning because it seems to me that the new jags should be recognized as they are plugged in.

[linuxboy]

Originally Posted by FrankJ

I found to get all the Jags to communicate that I had to power up the jags with them all connected & then restart the BCD-COMM com. A little concerning because it seems to me that the new jags should be recognized as they are plugged in.

This is something I noticed as well that I forgot to mention. It seems like some of the time hotplugging works, and other times, it does not, and you need to power on all the Jags at the same time. I don't know if that really is necessary, but its worth a shot.

Oliver

[taichichuan]

Probably restating the obvious here, but make sure that you reprogram the CAN IDs on the Jags before plugging them into the bus. By default, the Jags all come with the same ID set. So, even if the termination is correct, you'll only see one of them. You can reprogram the IDs using the BDC_COMM application. Follow the getting started guide for details. BTW, you can get a complete set of working CAN cables w/ terminators and the RS-232 cable from http://www.estoprobotics.com/estore/ if you're interested.

HTH,

Mike

[jwakeman]

Originally Posted by taichichuan

BTW, you can get a complete set of working CAN cables w/ terminators and the RS-232 cable from http://www.estoprobotics.com/estore/ if you're interested.

Yes! I will be buying a couple of those starter packs. I would like to think i am capable of making the cables myself but at this point I just want to take some of the mystery out of this and using cables that i can reasonably assume are proper will go along way towards maintaining my sanity!

[jwakeman]

Originally Posted by jwakeman

Yes! I will be buying a couple of those starter packs. I would like to think i am capable of making the cables myself but at this point I just want to take some of the mystery out of this and using cables that i can reasonably assume are proper will go along way towards maintaining my sanity!

We got the cables from e-stop electronics. Unfortunately, I am still seeing some flakiness in the CAN network. I have successfully had all four nodes on the network at once but it is still not reliable. I am looking for some specific diagnostics steps I can perform. I suspect it could be noisy/poor power supply, grounding issues, cable issues (even though i bought them). Armed with a oscilloscope and multimeter are their specific measurements i can make to look for termination/noise issues? Thanks!

[Mike Copioli]

Originally Posted by jwakeman

We got the cables from e-stop electronics. Unfortunately, I am still seeing some flakiness in the CAN network. I have successfully had all four nodes on the network at once but it is still not reliable. I am looking for some specific diagnostics steps I can perform. I suspect it could be noisy/poor power supply, grounding issues, cable issues (even though i bought them). Armed with a oscilloscope and multimeter are their specific measurements i can make to look for termination/noise issues? Thanks!

Do you have access to a 2CAN? If you do you may use it to help diagnose the problem. An o-scope will not tell you much unless you know how CAN operates, the 2CAN however can diagnose if your CAN connectivity is the issue.