|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: CAN periodic status
The design was to cache previous values so that if you read more quickly than the updates are coming in, you just get the most recent values. It sounds like there is a bug. You should not be getting those errors. I'll look into it for next year if you'll create a tracker.
Thanks -Joe |
|
#2
|
||||||
|
||||||
|
Re: CAN periodic status
Quote:
|
|
#3
|
|||
|
|||
|
Re: CAN periodic status
Since we use C++, I didn't even know that there was such a feature. I've added checks to each of the various classes that use the CAN bus and Jaguars to query the Jaguars for reset, and faults after are update operation on the Jaguars. At least this way, I can determine if something has gone wrong..assuming the Jaguars are replying
![]() It's a bit of traffic on the bus but I see no alternatives, other than getting rid of the Jaguars |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|