I'm assembling a vehicle data logger and have run into an odd issue. The vehicle uses a non-standard CAN communication format. All vehicle systems (except the engine itself) are handled through a single ECU. Frames are transmitted cyclically with N different frames in a cycle. Every frame has an identical arbitration code. The payload of every frame is 8 bytes, and the first byte is a secondary identifier that cycles from 1 to N to indicate which data are being transmitted in the following 7 bytes.
e.g.
This presents problems: to a database, every frame will be interpreted the same way because they all share identical arbitration IDs. As far as I know, there isn't a way to create a database file that differentiates messages based on the contents of the data field. Are there any ways of doing so?
My current solution is just to log data frames straight to TDMS. From there, I can load the TDMS files and interpret each frame - either using a case structure or a call to some C++ code I have. Of course, I could do that on-line as well, but I'm crunched for time and that sounds like a pain. It would be much easier if there was a way to construct the database to parse out messages into signals.
Thanks!
