The last VehicleLogs file that I pulled with the correct year was 202009190502.tar
Since then, I'm seeing file names like 200103161832.tar and 200208092332.tar
Is this a permanent error in the Linux system running internally, or is it a matter of setting the date?
I've read on this forum about updates to the log parser, but I'm talking about the file name, which is set by the car when it writes the log to the USB drive.
I see that I don't have the latest firmware (4.7.2? ... I have 4.6.8), so I'm in the process of scheduling a firmware update at the local service center.
On a related note, does anyone know whether the latest firmware puts the correct year in the filename, or is the the problem unrelated to firmware revision?
Since then, I'm seeing file names like 200103161832.tar and 200208092332.tar
Is this a permanent error in the Linux system running internally, or is it a matter of setting the date?
I've read on this forum about updates to the log parser, but I'm talking about the file name, which is set by the car when it writes the log to the USB drive.
I see that I don't have the latest firmware (4.7.2? ... I have 4.6.8), so I'm in the process of scheduling a firmware update at the local service center.
On a related note, does anyone know whether the latest firmware puts the correct year in the filename, or is the the problem unrelated to firmware revision?