Application and api are switched in FileStatistics
Hello Tobias, another thing we noticed is that the information for the application and the api seem to be switched in FileStatistics. Below is the information your parser example prints out for one of our files. applicationId: 184 applicationVersion: 245.61.0 apiVersion: 2.1.10.0 We recorded our files with CANoe 10.0.114 so we expected something like applicationId: 2 applicationVersion: 10.0.144 apiVersion: 3... or 4... Would be very grateful if you could check this. Cheers, Daniel
Comments (7)
-
repo owner -
repo owner - changed status to open
-
repo owner -
assigned issue to
-
assigned issue to
-
repo owner Hi Daniel,
I checked the files I have and provided a patch in branch feature/issue-29. Application ID and version are now corrected.
Another field is likely the objectsRead. But despite the name, this seems to be the number of devices from which logging data is captured. I have a log from CANlog, where it shows 6. CANoe 6.1 and 7.1 shows 10 here. And all newer CANoe/CANalyzer versions show 1.
I as I dropped apiVersions, there are now some unknown fields where I haven’t figured out yet what they are good for.
Bye
Tobias
-
repo owner Hi Daniel,
I also fixed apiNumber now.
There is one unknownField, which shows 1, 6, or 10. Might be the objectsRead, but can also be compressionLevel. I still need to figure this out.
Bye
Tobias
-
repo owner Hi Daniel,
last field identified. It’s the compressionLevel. I checked my BLFs and the LogContainers therein. It’s consistent with FileStatistics, with one exception. If FileStatistics.compressionLevel = 10, then the LogContainers are compressed with level 6, which is the default.
I’ll merge this to master.
Bye
Tobias
-
repo owner - changed status to resolved
Changes merged to master.
- Log in to comment
Hello Daniel,
I checked it with some of my BLFs. Most show correct behavior like this:
This correctly shows apiVersion (binlog v5.0.0.0) and applicationVersion is often 0.0.0.
However in one of my files I found what you described:
If this is from CANoe 10.0.114, then I would expect to see 10, 0, 114 values somewhere in the FileStatistics, but 114=0x72 is nowhere there. Also the numbers from the API version 3 or 4 or nowhere in the fileStatistics. That’s really weird.
I found another example from the examples provided with CANoe:
This was recorded with CANoe 9.0.39. It shows 9.0 at the position, where your BLF contains the 10.0 for CANoe 10.0.
I’ll check further, but you seem to found something
Bye Tobias