This year, our team was planning on using PWMs for controlling our Jags, but came across the rule saying that we have to use CAN communications if we want to use Jags.
We have never implemented CAN before, and are having trouble with it. We’ve checked, and all of our cables (db9 to rs232, 6P6C, etc.) have been tested and are functioning. We are trying to update the firmware on our Jags but we can’t seem to get the BDC-COMM to detect them. When we click enumerate, we don’t get the board information like we should.
We do have a terminator on the right side of the jag when we attempt to use BDC-COMM. To the best of our knowledge, we have everything wired correctly.
The BDC-COMM version we have is version 107, and I saw somewhere that the newest version was supposed to be installed with the NI Update Suite.
So, being rather ignorant of the CAN configuration, could you tell me if this is still a wiring issue somewhere, an issue with the BDC-COMM version, or something else entirely?
You can use PWM to control Jags, that’s legal. Which rule did you read that made you think otherwise?
To keep things simple, I would try to reflash each Jag one at a time using BDC-COMM (just like you described) using serial only. So in other words…
Laptop/PC------ UsbToSerial adapter----------- serial rx and tx on RJ11 on the left side (See Jag doc for pinout).
That should work for discovering one jag and flashing it with BDC-COMM. No need for termination resistor or rj11 daisy chaining since your just using BDC-COMM to reflash.
I think when we were trying to figure out CAN for use on our PCM, we came across a rule that we thought meant that we had to use it on our Jags.
It was late at night however, and we were kind of at our wit’s end at that point. A cursory glance probably led to a misunderstanding.
Well, if PWMs are legal, this is a non issue. If we decide to try to implement CAN anyways, I suppose we’ll give it another shot. Most likely we will stick with PWM.