I'm working on support for a new car. I've been capturing two kinds of can logs, one where the car doesn't move (importantly the odometer doesn't change) and the other where I drive somewhere (odometer and tpms values change).
I've noticed it can be difficult to obtain a can log for the latter case. For example today I tried to create a can log for the trip to pick up lunch. Before starting the car (or even waking it up) I started a can log and verified it it was active:
OVMS# can log start vfs crtd /sd/ct5-13.crtd
CAN logging to VFS active: Type:vfs Format:crtd(discard) Vehicle:CT5 Path:/sd/ct5-13.crtd OVMS# can log status #1: open Type:vfs Format:crtd(discard) Vehicle:CT5 Path:/sd/ct5-13.crtd Size:149 Messages:1 Dropped:0 Filtered:0 Rate:0.0% /sd/ct5-13.crtd: running Size:149 Messages:1 Discarded:0 Dropped:0 Filtered:0 Rate:0.0%
When I arrive at my destination, I turned the car off and then used the ios ovms app to check the log:
can log status
CAN logging inactiveSo my can log was no longer active.
When I got back home I ssh'ed into the module and found that the log was present but with a length of zero and a bogus timestamp:
OVMS# vfs ls /sd
[DIR] 05-Jul-2019 19:48 backup/
0 30-Nov-1979 00:00 ct5-10.crtd
75.8M 30-Mar-2026 11:51 ct5-11.crtd
35.5M 30-Mar-2026 21:17 ct5-12.crtd
0 30-Nov-1979 00:00 ct5-13.crtd
[DIR] 05-Jul-2019 19:48 logs/
[DIR] 29-Mar-2026 09:58 scripts/In cases where I have successfully captured a can log while driving I used the app to stop logging *before* turning the car off. But every time I've tried where I've turned the car off before stopping the can log has failed.
My expectation is that changing ms_v_env_on should not impact can logging. This feels like a bug but I allow that there might be something happening here that I do not understand.
It also appears that nothing new is written to the normal log file while can logging is active; is that expected?
CraigP.S. I configured opendkim to not sign messages to ovmsdev@lists.openvehicles.com