View Single Post
  #1   Spotlight this post!  
Unread 23-01-2010, 14:42
Randy Forgaard's Avatar
Randy Forgaard Randy Forgaard is offline
Parent 1729, former mentor 3126
FRC #7129
Team Role: Parent
 
Join Date: Oct 2009
Rookie Year: 2010
Location: Hollis, NH, USA
Posts: 48
Randy Forgaard is a splendid one to beholdRandy Forgaard is a splendid one to beholdRandy Forgaard is a splendid one to beholdRandy Forgaard is a splendid one to beholdRandy Forgaard is a splendid one to beholdRandy Forgaard is a splendid one to beholdRandy Forgaard is a splendid one to behold
Trouble getting BDC-COMM to see the black Jaguar

We are having trouble using BDC-COMM to update the firmware and set the CAN ID on a black Jaguar. We're hoping someone can see what we might be doing wrong. Here’s what we’ve done:

1. We very carefully followed the instructions at www.luminarymicro.com/jaguar to create the RS232 adapter using the approved DigiKey parts.

2. We created a CAN terminator, per www.luminarymicro.com/jaguar, using the approved DigiKey parts.

3. We created a 6-pin modular phone cable to go from the RS232 adapter to the black Jaguar, again using the instructions at www.luminarymicro.com/jaguar.

4. We don’t have an RS232 port on our computers, so we used an off-the-shelf USB-to-RS232 converter to add an RS232 port to our laptop.

5. We plugged our RS232 adapter (that we created above) into the USB-to-RS232 converter, and used our 6-pin modular phone cable to go from the RS232 adapter to the “left” port on the black Jaguar.

6. We plugged our CAN terminator into the right port on the black Jaguar.

7. We provided 12V power to the black Jaguar.

8. We run BDC-COMM (downloaded from www.luminarymicro.com/jaguar) on the computer.

9. At this point, we have two problems: (a) The black Jaguar is flashing “red” slowly, as though it has a fault condition (per the Jaguar documentation); and (b) BDC-COMM cannot see the black Jaguar at the other end of the cable, even though we have the COM port setting set correctly in BDC-COMM.

It’s possible we might have a broken Jaguar, or incorrectly-created cables, or our off-the-shelf USB-to-RS232 converter might not be working. We’ve been very careful and double-checked everything, but it’s still possible we have one of these problems. However, I just want to check to see if anyone sees anything above that we are doing incorrectly, due to a misunderstanding on our part, etc.

Any help appreciated!
Reply With Quote