You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's probably possible. But, it sure would help if I knew what all the fields mean. At first I thought it was
TimeStamp, Length, ID, byte0, byte1, etc but it's not.
The second number certainly isn't length like I thought. I'll have to dig into their code a bit to figure out what each field is.
Also, quite a lot of the traffic listed is well over 8 bytes. Some lines might even be over 64 bytes. SavvyCAN is capable of loading CAN-FD frames where there are up to 64 bytes. The file you linked to isn't raw CAN traffic but rather NMEA traffic already collected into messages from the individual frames. It might not be that easy to import.
I believe the data is NMEA 2000 and the messages over 64 bytes are from fast packet messages that have been combined. Am I understanding correctly that *.dbc files cannot specify fast packet message format? Would be amazing if could also specify a JSON decode file such as this one https://github.com/canboat/canboat/blob/master/analyzer/pgns.json#L20161 that handle NMEA 2000 (fastpacket) data.
Is it possible to read logs in this format? If not what would be involved in adding this functionality?
Link to log from canboat GitHub project
I think this format is "Actisense" format.
The text was updated successfully, but these errors were encountered: