I wonder if this is the same old problem we've had (are having?) with CAN2/3, where it just goes deaf after a while.  I saw it all the time with the OBD2ECU task, which listens to CAN3 (typically) for Head-Up Display polling requests and fulfills them with data from the metrics.

To regain message flow, my workaround is to stop the OBD2ECU task, power cycle the External 12v going to the HUD, then re-start the task.  (If I recall, the essential part is to have the HUD running before starting the OBD2ECU task.)  I've got an event-driven script to do this whenever I start the car, and that typically takes care of things.  Unfortunately, I don't see how you'd do that with the Focus support.

I spent some time a few years ago trying to figure out why the CAN driver seemed to be getting stuck, but made little headway.  It seemed like everything was fine - no errors or unserviced interrupts - but data ceased to be received none the less.  I believe Michael and others have spent some significant time on it as well, but haven't been following the topic for a while.  From my past life writing drivers, the symptom is that of a race condition where an interrupt gets cleared by the driver but not acted upon.  The chip is left with unfinished business patiently waiting forever for someone to take care of it, and the driver is waiting forever for something to do.  Was a "fix" ever implemented?

Greg


Simon Ehlen wrote:
RE: [Ovmsdev] Not processing canbus frames anymore

On 4/4/22 23:05, Craig Leres wrote:

> Which vehicle type are you using?

 

My vehicle type is a Ford Focus electric, the module is still in the early stages of development.


> What I see is that any version I boot works for a little while.

> But after some length of time, the canbus stops working and

> I get flatbed  alerts because the module does not detect that the car is running.

 

That's how it is for me, too. I have read-only access to the CAN buses without additional polling. After some time I notice that the values are no longer updated, if I then look at the bus with 'can can2 status', I see that neither interrupts nor packets come in, although the bus is definitely still active. Either a module reset or a restart of the bus let the messages flow again.
 
On which bus do you have the problem? So far I could only observe this on CAN2 and CAN3. CAN1 was not stalled as far as I can tell.
 

Kind regards,

Simon


_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev