We know 2byte airflow uses request id 02 and 03 and depending on the rom id you point those to the correct location. I just want to know has anyone got this working in logworks. If so could you show what you added to the protocol.xml(probably similar to 2byteload) and also what calculation did you use in the formula calculator? Thanks in advance.

 

Here is the formula that you would use, assuming that you altered your MUT table for requests 02 and 03 to be the two bytes of airflow:

6.29/64*((256*requestID02)+requestID03)

Here is a link to the thread by jcsbanks about the 2 byte airflow mod:https://www.evolutionm.net/forums/sh...d.php?t=240981


Eric

 

I was planning on waiting for Santa Klause's release of beta 2 but what the heck, I guess it's time to try.

ChrisW has as well as 12r99gst

Hey 12r99gst, I just plug that (above) in the dat collection/calc like the load (I allready fixed the addresses and stuff)?

 

Yes, it's done identical as the 2byte load, except you have to reference request 02 and 03, assuming that is where you modified your MUT table with the new variables for your ROM.

For LogWorks, you might use something like this for the formula calc:

MC(2byte_Airflow;Hz;0;3000) = ((Airflowmsb * 256) + Airflowlsb)*6.29/64

Just change Airflowmsb and Airflowlsb to whatever you called them in the protocol.xml file.


Eric

 

Thx man I will test it out tomorrow.

 

The loadmsb and loadlsb use load as units, do i change that to hz also for the logworks protocol?

 

Yep, just change to Hz.

 

I rated this thread

I will try the airflow on LW3 tonight

 

What is the advantage of logging the 2byte airflow? How does that help with tuning?

I do understand that the 1 byte clips above 1602 hz, but I do not see how the 2byte airflow helps in tuning. I just do not want to add a patch to the Rom that is not essential to tuning.

 

Helps in scaling the maf correctly, which will help you car run optimal when modding your car plus you get to know how much air you car is taking in at a certain rpm vs other turbos when you upgrade.

 

Logged 2 byte airflow finally. I couldn't get 2 byte air and load to display at same time yet.

nj1266, airflow is very important to tuning, more so than boost psi. Airflow hz is directly proportional to the volume of air the engine conumes, boost isn't (due to VE) but does represent a good dirty standard of comparison of engine load

Airflow vs IPW essentially is A:F, I noticed some dont bother logging IPW either but it tells you alot.

Does anyone know if there is a way to log 2 byte without all the data collection and math entries for each log every time - seems like a lot of work to get the value (esp when it gets an error 50% of the time with the beta)

Another thing - my airflow is about 200 rpm (0.2 sec) early compared to the other logs. How do I correct this?

 

Notice 2 byte load and air is about 200 rpm (0.2 sec) earlier than the regular airflow, timing rpm, IPW and tps, AFR seems to be early too.

 

post corrected below(?)

 

C6 Can you post what you added to the protocol exactly. When I added mine something started logging, but I am not sure if the info I put in was correct?

 

I see, the 2 byte is scaled lower then the red air. I was confused by not reading the scales of the two.