Chief Delphi - CAN vs PWM

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)

- CAN (http://www.chiefdelphi.com/forums/forumdisplay.php?f=185)

- - CAN vs PWM (http://www.chiefdelphi.com/forums/showthread.php?t=87299)

Quote:

Originally Posted by ratdude747 (Post 986539)

i'm confused. the six wire cord is only for the first bit?

ok... i assume 8 wire patch cord with rj12 pluds (2 wires not used) would work?

From the cRIO to the first (black) jaguar, 5 wires are used. 3 for the serial chatter, 2 for the CAN bus with a 100 ohm resistor at the end connected between them.

After that, only 2 wires are used by the bus. It doesn't hurt though to have more wires in the cable.

Quote:

Originally Posted by Radical Pi (Post 986651)

Team 1718 just posted the PowerPoint slides from today's LabVIEW & CAN seminar. It has an explanation of the CAN cabling, with pictures.

we are doing can

i have a terminator and serial cable made.

for some reason the TI program fails to see the jag... and the cable and terminator are good (the terminator on the serial cable is good too)

any advice?

edit- some things that might matter:

i am trying to flash a new black jag.

the cable was made from a chopped serial cord from the 2009 KOP. I used a multimeter to probe the wires to obtain the correct wires. I then crimped 5 wires into the rj-12 and soldered the 3 correct serial wires and the term. resistor to the plug cables. i verified correct pinouts with my multimeter.

the cable is about 6 ft long... maybe it is too long?

edit2- nope, shortening it to 2 ft didn't help (i was sent home with the goods to try and fix the issue)

somewhere it was mentioned that a specific vs. of the bdc-comm was needed... any truth to that?

RatDude747, make sure you don't have the RJ-14 connector backwards.
This is what the male connector should look like:

Quote:

Originally Posted by kamocat (Post 993959)

RatDude747, make sure you don't have the RJ-14 connector backwards.
This is what the male connector should look like:

my wire colors are non-standard but according to everything i have seen, the connector is not backwards

Quote:

Originally Posted by ratdude747 (Post 993967)

my wire colors are non-standard but according to everything i have seen, the connector is not backwards

What do you get when you enumerate?

my guess is a bad jag.

i will try one from the new KOP tomorrow...

still not working even with a kop jag

it is acting as if it is not getting a signal... i wonder if my rj-12 is bad (i had to reuse one off an old cable as the clips did not get ordered as planned).

any other ideas?

And you're plugging it into the left port of the Jag?

Assuming the BDC-COMM is installed correctly, and your Jaguar has power, the issue is either your RS232 port or your adapter cable.

There's three options I would suggest:

Find a local team that can help you.
Go to the hardware store and get connectors, and a cable with standard wire coloring
Buy an adapter box from digikey

If you want to try to test the cable, use the cRIO to enumerate. If you get a "0" back, then I believe your tx/rx are reversed.

ok... i have very good news!

IT'S ALIVE!!!

the issue was the used plug... it apparantly had some damage blocking terminal 3. I corrected the damage and it worked flawlessly... had i not been in a rush to clean up I would have snared some pictures.

I now have a black jag and a gray jag with new firmware; the black's ID is 2 and the gray's is 3.

the programmer claims to have done CAN before; and i read somewhere that there is a "black jag" reflash option for the cRIO. any confirmation on that?

Quote:

Originally Posted by ratdude747 (Post 995266)

You cannot update the Jaguar firmware from the cRIO.
However, the cRIO reimaging tool can install the BlackJagBridge plugin on the cRIO for you. (This allows it to communicate with the Black Jaguar over RS232)

Quote:

Originally Posted by kamocat (Post 995348)

i meant reflashing the cRIO. the jags were reflashed using my laptop. sorry about my poor wording

the clips have been ordered and this should work pretty well (knock on wood).

maybe i should explain the whole old connector thing

the cable was actually a REALLY long 4 wire cable with a 6c plug. the cable used pins 3-6, with 1 and 2 empty. it had the other plug damaged and long replaced, so we got a good 20+ feet for 4 wire oval for free.

to make the plug work, i needed to add a wire to pin 1 (pin 2 is NC). to do that, I first cut the plug off with about 1.5" of cable hanging. I then removed the oval part. next, I cut a paper clip at an extreme angle to make the point at the edge instead of center. then I put it in the hole for wire 1 and used it and a pair of needle nose pliers to remove the contact. due to the angle cut, I was able to get to under the connector and twist it to act as a cam of sorts to push up the contact. I then used the pliers to pull the contact.

I then put a bare wire in wire hole 1 and put the contact back in. next i re-crimped the plug (and locking in all 5 wires). i soldered the serial wire and my 100 ohm resistor to my 5 wires coming from the plug. I then used electrical tape to isolate the wires and resistor leads. i tested the cable with a multimeter, neglecting to see the slight damage.

jerry rigging at its best, but if you need a serial cable fast, it works. even I was surprised it worked...

Quote:

Originally Posted by ratdude747 (Post 995351)

i meant reflashing the cRIO. the jags were reflashed using my laptop.

Yes, he is correct. It's very easy.
It's the "CAN Driver Plugin" option. You don't even need to select "Format Controller", and I believe it takes less than a minute.

random question:

are usb to serial adapters compatible with the serial cable?

reason I ask is the team laptops are newer lenovo thinkpads (celeron cpu) which have no serial... the team's desktop I donated has it but is not portable, so I have been using my personal laptop for now (dell latititude d400).

too bad TI doesn't have bdc-comm in a linux flavor... good thing my laptop is a dualboot.