![]() And we need a trace of a whole session since the beginning, also including the preliminary AT commands. Otherwise, if you are able to get a long enough listing of TX/RX flow, we could simply start from this, trying to convert it into a dictionary. Ideally, it would be useful through some application to get the whole traces of a complete set of queries to real ECUs for all possible commands please suggest a tool if exists, consider also that, if I have to run it myself, I can only use a real engine and I suspect some queries might be invasive (I would like to avoid reprogramming an ECU which modifies the performance, or damages the engine or invalid the warranty). I assume you only added the RX commands in the example, I can't find the TX part. At first glance, it looks pretty easy to extend the dictionary to support this.
0 Comments
Leave a Reply. |