|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Consistent CANTimeoutException via CAN-serial interface
Also you may have CAN id conflict. Have you verified the individual ID's are in fact discrete by pressing the user button on each Jag?
|
|
#2
|
|||
|
|||
|
Re: Consistent CANTimeoutException via CAN-serial interface
@Mike: After 48 hours of consistent connection failures between the cRIO and the Jaguar, we've now gone the last two hours without a timeout since shortening the cable. My concern about noise is not on the CAN side, but on the serial connection from the cRIO to the Jaguar. We are running on flat wire, and we put the CAN terminator in the DB9 on the cRIO side of the connection. Running the two protocols on parallel wire pairs within the same cable may have caused crosstalk or noise problems on the serial, especially since the serial connection is at such a high bitrate.
@Joe: I really like your suggestion of moving the CAN terminating resistor over to the RJ-12 connector in order to isolate the serial line, or I may even remove the resistor entirely if it turns out that it's not really necessary (per Mike). |
|
#3
|
||||
|
||||
|
Re: Consistent CANTimeoutException via CAN-serial interface
Quote:
Ahh, I misunderstood your statement about the cable length. I was not suggesting that you remove one of the resistors, just pointing out that it can work in most cases with only one resistor. We recommend and use both resistors in practice. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|