triggerframe protocol

[ds]

Hi,

i searched in the forum and wiki but did not find documentation describing the triggerframe protocol / file format. Is there any available resource for it?

i have two goals to achive:

• main is to convert logs to standard MDF format https://www.asam.net/standards/detail/mdf/wiki/ as many data analyser tools exists for this format. (i am already using a proprietary one as a TCS developer). i like vemstune but the log viewer part is really a weakness.
• secondly i wrote a small program which translates the AIM output of vems to be compatible with RacheChrono's own format (https://racechrono.com/article/2572) so i can get engine rpm / throttle etc. on the video overlay during racing. However it would be very useful to have a full log in case something went wrong (i do not have an SD card). Also i would prefer not to enable AIM if it also enables the one byte unprotected prtocoll (as far as i know this is the case)

Can anyone provide me a description of the triggerframe log format?

Thnanks in advance

as i am not allowed to write reply.....
thanks.
i actually found that page http://www.vems.hu/wiki/index.php?page=SerialComm%2FTriggerFrameFormat already (it refers to other source files which i do not have). i also made a prototype program from vemstune ini files (eg  vemsTune-v3-1.2.23.ini) which is working but there are other frame types than described on the wiki page.
i tought that there is a documentation somewhere available. (eg which commands can be sent what will be the answer, possible frame types) If the whole source is available this can be found out but still not convenient at takes lot of time.

[jrussell]

Documented here: http://www.vems.hu/wiki/index.php?page=SerialComm%2FTriggerFrameFormat

Contents depend on firmware version, which should be obvious.

[gunni]

What must be understood also is that Vemstune itself produces alot of the channels offline you find when you look at log viewer, you´d have to look into the program files to see the calculations so you can produce the same channels, otherwise you are not getting the same amount of channels as you get in vemstune/log viewer.

[ds]

Even  the channels coming out of the ECU needs some calculations. Which also not documented. So anyway thanks for the pointers. ( And it seems that my assumption was correct there is no documentation exists.)

[jrussell]

Even  the channels coming out of the ECU needs some calculations. Which also not documented. So anyway thanks for the pointers. ( And it seems that my assumption was correct there is no documentation exists.)

A lot of it is set up in the vemstune config files, so it can be grabbed from there.