Hi folks,
Has anyone else noticed this? I grab a monthly log from my 2.0 Roadster, just to keep abreast of anything the car might be noticing, and to keep a historical record. I had done some driving on 7/27, 8/1, and today 8/2, but the log as seen by VMSParser.exe stops with a daily charge back on 7/21/21. None of the drives or daily charges after this are listed. The graphical parser (TeslaGLOP) does show the post-7/21 activity, so it appears that the log itself is ok. I checked just running the parser directly, and with the -p or -c options.
No alerts were recorded by the OVMSv3 monitor around that time.
What's magic about 7/21/2021 that might be confusing the VMSParser? Might there be something in the log on 7/22 that might be tripping it up?
Has anyone else noticed this? I grab a monthly log from my 2.0 Roadster, just to keep abreast of anything the car might be noticing, and to keep a historical record. I had done some driving on 7/27, 8/1, and today 8/2, but the log as seen by VMSParser.exe stops with a daily charge back on 7/21/21. None of the drives or daily charges after this are listed. The graphical parser (TeslaGLOP) does show the post-7/21 activity, so it appears that the log itself is ok. I checked just running the parser directly, and with the -p or -c options.
No alerts were recorded by the OVMSv3 monitor around that time.
What's magic about 7/21/2021 that might be confusing the VMSParser? Might there be something in the log on 7/22 that might be tripping it up?