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. |
Sorry to hear you're still having trouble. Do you have LabVIEW installed? Have you read Tutorial 9 on the getting started window in LabVIEW? It describes best practices and may give you some ideas to consider.
What language are you programming in? The C++ implementation saw some improvements this year, to come up to the level that LabVIEW was last year. LabVIEW then surpassed it again (wrt supporting the new Jag firmware features). C++ may support the new features a little later this season. The Jag firmware was released too late to get all the APIs updated to support them in time for kick-off release.
-Joe