Does your vehicle report that this pid
is supported?

Test for the raw hex response to see
the full response. Maybe you are looking
at the wrong bytes if supported.

PID 0x66 should have a 5 byte response.

The first byte tells you how many MAF sensors are supported

Bytes B and C are for sensor 1, D and E for sensor 2.

The scaling is multiply by 0.03125.

I think that means your equation becomes (256B + C)*0.03125 but I'm not that familiar with how you get Torque to combine data bytes.

For Sensor 2 (if fitted) the bytes would be D and E.

I've seen others who had it working on Torque pro or on other Obd2 gauges .And i also know the sensor is there and it can be read out with a tuner device like ex. hondata.

So it must be supported yes.
I gathered some information from a data dump from someone with the exact same vehicle.From there i had these values

"Supported" - "Mode (hex)","PID (hex)","Data bytes returned",Description,"Min value","Max value",Units,Formula

0 - 1,10,2,"MAF air flow rate",0,655.35,grams/sec,"((A*256)+B) / 100"

0 - 1,50,4,"Maximum value for air flow rate from mass air flow sensor",0,2550,g/s,"A*10, B, C, and D are reserved for future use"

0 - 1,66,5,"Mass air flow sensor"

How do you test for raw hex respond?
And shouldn't the equatation then be ((256*B)+C)*0.03125
?

I now tested these equatations :

((256*B)+C)*0.03125 this gave lower readings when giving gas and higher readings releasing the gas.

((B*256)+C)/100
This gave better readings not sure if this works properly the readings go up when i give some gas sometimes.
Need to drive around to actually test it properly but i'm afraid to screw somethings up in the engine.

The equation for 0110 is not
the same as 0166. It seems to
me if it was there would be no
need for 0166. Go with Crispy.

Use the Test button in the pid
editor while connected to your
vehicle to see the raw hex response.

Look under Adapter Status icon
information to see list of supported
OBD sensors.

Your table shows "0" for Supported?

I checked if the vehicle supports the pid but i don't see any maf sensors listed.But this was also the case with the other sensors like ECT and IAT ,those also had a 0 for supported and those work perfectly now.
I took a screenshot of the test with this equatation ((B*256)+C)/100
But i Cant seem to upload it here?

Result for equatation is 44.16
Response was 416007114001
B=17
C=64

If the sensor wasn't supported at all ,then i could not get any readings out of it right?
The Maf sensor flow rate also works on a lufi OBD2 gauge .
So it is possible but i need to find out the correct equatation.

Was expecting 4166AABBCCDDEE. Not
4160...?

4160 07 11 40 01

07: 0000 0111 - 0166, 0167 and 0168 supported.

11: 0001 0001 - 016C and 0170 supported.

40: 0100 0000 - 0172 supported.

01: 0000 0001 - 0180 supported.

Quote from Capp777 on February 24, 2020
Was expecting 4166AABBCCDDEE. Not
4160...?

4160 07 11 40 01

07: 0000 0111 - 0166, 0167 and 0168 supported.

11: 0001 0001 - 016C and 0170 supported.

40: 0100 0000 - 0172 supported.

01: 0000 0001 - 0180 supported.

Now that you mentioned it i somehow put in 0160 instead of 0166.
Oops need to try this again...

So i tried it again using this equatation ((256*B)+C)*0.03125 and pid 0166.
The maf now works!
This is what i got out of the test
41660100080000
Would this now work properly ?

Quote from Hondanickx on February 24, 2020
So i tried it again using this equatation ((256*B)+C)*0.03125 and pid 0166.
The maf now works!
This is what i got out of the test
41660100080000
Would this now work properly ?

End Quote.

It should based upon Chrispy's posting.

Int16(B:C)*(1/32)

Another way to write same equation.

Thank you all for the information!

have i need ait 1 and iat 2 pids any one know it?