Originally Posted by nj1266

I am using the Logworks plug-ins for the tactrix cable. There isn't a way that Evoscan/Mitsulogger can log boost outside of the OBD2 port. As such, I cannot compare their boost logs from the OBD2 port to another logger. Logworks integrates data from the OBD2 port and data from the LM1/LMA2 into one log and you can see how much slower the response from the OBD2 vs. the LM1/LMA2 when it comes to boost.

I have attached a log. The OBD2 boost column is labeled "OpenPort_Boost". The LM1/LMA2 JDM boost column is labeled "PSI" and the GM 3 Bar boost column is labeled "GM_Boost." Notice how the OpenPort_Boost column keeps giving the logger the same boost numbers. This is because the ECU has a slow response time and cannot keep up with the requests from the LM1/LMA2.

Originally Posted by mrfred

I'm still not clear on what you mean. You are referring to the ODB2 port, but there are two common protocols that can be used to log data from the ECU over the ODB2 port: ODB2 and MUT III. The ODB2 protocol is is notoriously slow. However, the MUT III protocol is sufficiently fast if setup properly. EvoScan and Mitsulogger both use the MUT III protocol. What does LogWorks use?

Originally Posted by kreionic

Log works using both aswell. OBD II and mut III

Originally Posted by mrfred

Which are you using NJ?

Originally Posted by mrfred

I'm still not clear on what you mean. You are referring to the ODB2 port, but there are two common protocols that can be used to log data from the ECU over the ODB2 port: ODB2 and MUT III. The ODB2 protocol is is notoriously slow. However, the MUT III protocol is sufficiently fast if setup properly. EvoScan and Mitsulogger both use the MUT III protocol. What does LogWorks use?

Originally Posted by nj1266

I am using MUTIII according to the protocols.xml file in Logworks. Even though MUTIII is faster than the OBD2, it is still slower than the Innovate logger.

Originally Posted by mrfred

How many ECU parameters are you logging via the MUT III? If you limit the number of parameters to about 10, I think you'll find the that logging speed is quite good. I'm logging about 10 lines per second with no repeat quantities (except where limited by resolution).

Originally Posted by nj1266

The current Logwork tactrix plug-in is limited to logging 10 parameters. So I log 10 parameters. The 2byteload and IDC are calculated after I log with the Logworks formula collection.

The ECU is slow and that is why logging boost from the port lags behind logging boost via LM1/LMA2. I had the same thing happen when I logged RPM via the port and via the LM1/LMA2. The RPM numbers from the ECU lagged behind the RPM numbers via LM1/LMA2.

Originally Posted by mrfred

Can you post your logs?

Originally Posted by nj1266

I did on the first page of this thread. Here is the post

https://www.evolutionm.net/forums/sh...8&postcount=15

Originally Posted by mrfred

I want to see the raw data.

Originally Posted by nj1266

Do you want to see the log? If so, the log is attached to the post.