Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Normal
Just a few clarifications on terminology... Logic chain would be data stream, and PID is OBD2 specific, it translates indirectly to data stored at a memory address. Instead of having to know each manufactures memory locations, the PID unifies it so that PID 0x04 is always calculated load, whereas with the NSX ECU memory address 0xFCB2 indicated calculated load.The baud rate is 62500 which roughly translates to 60 individual bytes (updates) per second. So, if you have a stream of 10 variables each will be updated approximately 5x per second (factoring in the 2 header bytes that identify the start/end of stream). I reworked the factory datalogging stream so that the stream length is fully customizable- but - the longer the stream the slower the individual updates. The data that is streamed is also customizable via a table in the ROM. Ideally the tuning process would be divided into modules simply because of the wealth of data that is available from the ECU. There are literally 1,024 (1k) of possible memory address that could be logged in the tuning process and ALL of them are defined .The current idea is to separate the stream into 3 14byte modules - fuel, ign and other. When all data from all 3 modules is desired simply send a command to change the first module to be 42 bytes long, streaming all 3 modules at once.-Matt
Just a few clarifications on terminology... Logic chain would be data stream, and PID is OBD2 specific, it translates indirectly to data stored at a memory address. Instead of having to know each manufactures memory locations, the PID unifies it so that PID 0x04 is always calculated load, whereas with the NSX ECU memory address 0xFCB2 indicated calculated load.
The baud rate is 62500 which roughly translates to 60 individual bytes (updates) per second. So, if you have a stream of 10 variables each will be updated approximately 5x per second (factoring in the 2 header bytes that identify the start/end of stream). I reworked the factory datalogging stream so that the stream length is fully customizable- but - the longer the stream the slower the individual updates. The data that is streamed is also customizable via a table in the ROM. Ideally the tuning process would be divided into modules simply because of the wealth of data that is available from the ECU. There are literally 1,024 (1k) of possible memory address that could be logged in the tuning process and ALL of them are defined .
The current idea is to separate the stream into 3 14byte modules - fuel, ign and other. When all data from all 3 modules is desired simply send a command to change the first module to be 42 bytes long, streaming all 3 modules at once.
-Matt
