Quote:
Originally Posted by mjcoss
Checked last night and no such luck. All look Jaguar connectors look fine to me. We also tested that the end to end termination was reading the correct resistance. So back to the same issue we had last year with CAN: Intermittent timeout of messages, with no clear cut root cause or solution.
One experiment that I will be running tonight is the use of sync groups. My code makes extensive use of sync groups for updating any motors that are linked together, I doubt that it's involved with my problem but I'll grasp at any straw at this point.
Unfortunately, looking at the forums CAN issues seem to be just as rampant this year  You'd think we'd learn our lesson. |
Seeing as you're in Bridgewater, NJ (which I often drive thru)...and I'm in Mount Olive, NJ...if you'd like to work together on this at some point please feel free to contact me.
That being said, the timeout errors are a little different in nature between the 2CAN and RS232 bridge.
Can you share which you are using?