$EE How to get MAF Hz in datastream

I've looked at a couple different .adx files and none seem to have it.
Anybody know the specific info to add it?
i.e. packet offset address, data size, and conversion equation...

I'd like to get the data using ALDLdroid, as my tuning laptop bit the dust.

it's only the e-side as far as i know (not in the factory datastream, which is pure t-side), so you basically have to:

- patch the e-side to enable mode1 datastream messages
- create a datastream with the appropriate memory address in it

....if you flash your bin with eehack this is already done for you ...

since all the useful data is from the t-side, this means you do have to make two separate queries for data, slowing the rate of the t-side data by quite a bit, one of the disadvantages of this type of ecm. i'm not sure how much control aldldroid gives you over query rates of various messages. that's why i had to add variable rates to eehack, so you can get your main message at a high rate and auxiliary data at a reduced sample rate.

if you're willing to make that sacrifice, and a recent eehack patch is installed, 0xE4 0x01 0x00 [checksum] will give you back a message of which the second byte is the maf raw frequency (i don't seem to have the conversion to actual hz handy, im sure i could dig it up)

My .bin should be patched then, as I've always used EEHack to flash?

When I tuned $OD_MAF on my Jeep, I created a history table in Tunerpro.
Using Hz(Y) and grams/sec.(X) with an ouput of Lambda(Z).

Unless there is an easier way in TunerPro that I'm overlooking? Which wouldn't surprise me...
Not going to schlep my new-ish Win10 laptop around in the car.
Blows that my junker tuning laptop 'bit the big one.

people tuning lt1s always derive the percieved maf hz from afgs. nobody tunes lt1 maf using hz. might want to stick to using the variables more easily available from this ecm. $0d has lots o stuff that ee doesn't

It would just be nice to have the data to use. I read a thread from 3-ish years ago, and someone else was asking the same.
Figured maybe it was relatively easy to grab?

Quote:

---

Originally Posted by RobertISaar

MAF Hz is on the E-side, 16-bit, word 185.

the problem here is that you normally don't communicate with the E-side... it's all done through the T-side. E and T pass some information to each other through the SPI link on a regular basis, but MAF Hz isn't one of them. MAF G/S gets passed, but the T-side uses it for a couple of functions. so at this point, there are a few options:

mode 3 request to the E-side to grab ONLY MAF Hz immediately after grabbing a T-side frame(really simple to setup, little impact on logging)

grab mode 1 packets from the E-side, edit in MAF Hz if necessary(obviously, very little to no t-side parameters will be available)

graft MAF Hz into the SPI link and read it over T-side mode 1(would need to find a 16 bit value to replace that the T-side doesn't also use for some function)

---

I was unsure of how to configure/change the .adx (if possible) to get the data is all.
Nevermind I guess, it isn't worth the effort I guess.

as stated above, it's in a totally separate datastream, so even if you did go through the effort, is it worth substantially reduced resolution of your more important data...?

if it is, hand me the adx you use, and i'll get you started

.. but probably isn't

Appreciate the offer, but it sounds like it is not worth the effort?

Was merely an idea, a sanity check for tuning the maf (tables) per say. Just a way to look @ different data in a TunerPro table.

Pretty sure that was me that asked..... Never got it and lost interest as things got busy else where.

Quote:

---

Originally Posted by Skinny Pedal

Pretty sure that was me that asked..... Never got it and lost interest as things got busy else where.

---

It was you...this was the thread.
http://www.gearhead-efi.com/Fuel-Inj...ency-on-EE-def

I was thinking a MAF Hz table with lambda as output data might be useful.