|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: CAN failure!!!!!!!!
Yes we have CAN enabled as a serial bridge
|
|
#2
|
||||
|
||||
|
Re: CAN failure!!!!!!!!
Do you have Console out enabled? What does your intialization code and wiring look like? 1 always has to be connected to the cRIO first.
|
|
#3
|
||||
|
||||
|
Re: CAN failure!!!!!!!!
We ran the example code and i did exactly as it instructed to run the code, i changed the IP to 10.19.39.2 and we have only one CAN jag and it is wired into the crio through a serial port and it has the terminator attached as well. I don't know about console out.
|
|
#4
|
|||||
|
|||||
|
Re: CAN failure!!!!!!!!
Make sure it's off. The console's serial communication will interfere with the CAN serial communication. Are you using an older 8-slot or a newer 4-slot cRIO?
|
|
#5
|
||||
|
||||
|
Re: CAN failure!!!!!!!!
We are using the newer 4 slot crio. On the console out part, all i know is that it was switched to the left (not towards the modules).
|
|
#6
|
||||
|
||||
|
Re: CAN failure!!!!!!!!
Please tell me you have withheld your cRIO or have a backup. It would be very hard to debug code if you didn't. if you have, I would try and reimage the cRIO. On the 4 slot, the DIP switches are not hardware switches. Remember, when you are downloading code, have Console Out be on if you want console feedback, off if you don't need it. Make sure your CAN cables are correct. Also, are you using the BlackJaguar or the Grey/Tan one? Only the BlackJaguar has a CAN bus on it.
|
|
#7
|
||||
|
||||
|
Re: CAN failure!!!!!!!!
I will double check the the console out switch when i get a chance we do have a back up crio. We are using a black jag.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|