OFT not reading MAF volts
 

Out of the 10 or so datalogs I have done, my off reads 0v for may at all times am I doing something wrong?

http://datazap.me/u/brzeddie/log-145...=0&data=1-3-13

BTW, this is on a F00C.

talk to the oft guys on phone, it an errot in the oft logging on some newer ecu calibrations, the logging addresses are different for each ecu calibration id

You have an MY15. MAFV hasn't been added to MY15.
Use MAF instead and extrapolate the value to your maf scale table.

How would I go about doing that? Is it something like 60g/s = 3.2v?

Look at or print out the maf scale table in your tune

OK, got it. I get lots of ltft spikes ±10-15 and ld like to rescale my maf sensor using the vgi tool, but it looks impossible without MAFv. On datazap I can see the spikes and see where they are occurring roughly, I guess I can try adjusting the g/sec up and down to see if I can zero in on this.

You could possibly use excel or similar to convert the maf flow to maf v using the maf scale table.



which intake do you have ?

I have a stock intake, with a drop in. After rescaling my maf range from 1.13v-4.4v, I've been inputting multiple logs into the vgi tool. Instead of mafv, I input g/sec and its giving me graphs, not sure if its right, because cl shows nothing, but ol gives me this. During these 12 pulls my highest g/sec was 168. I've seen as high as 171g/sec, so I'm surprised the corrected graph suggests to lower the 4.4 column, cause the 4.23@175.14.

Well I'm a complete noob when it comes to this tuning. I think I understand something, then the next day I read something else on here and it changes. The wild ltft swings I was experiencing have gone away. When I put my header on I couldn't get the secondary o2 sensor out. I was able to do that yesterday and installed it. I thought I could just clear codes and be fine without it, but reinstalling the 2nd o2 has fixed what I was chasing. No more wild AFR swings. Without the 2nd o2, I also noticed my car would go into open loop at 10% throttle every time , and my idle aft would slowly drop in the 12's and stay there while idling. I thought it was the maf sensor scaling, but now the trims and AFR are acting better now.

While the primary 02 sensor is used for fuelling, the secondary 02 is also used for some cruise correction cat efficiency and likely some other stuff.


Unless you get into the tune and disable a whole heap of stuff your going to need the secondary 02 sensor working and connected else all sorts of weird stuff, like you found, will happen.

was having the same issue with my OFT not reading my MAFv aswell as IAM and maybe even other things that I probably don't notice. Emailed Shiv multiple times in the past month and still not ONE response about this. I was later told by two ppl here it has something to do with 2016 Cal IDs and it is being worked on. But anyway yesterday when I was gonna do some data logging the MAFv and IAM magically was showing a reading. Maybe there was an update that I wasn't aware of.

Maybe, my oft I've had only a month. Hw ver.200 fw ver.136. My iam has always worked just not mafv. I contacted Shiv and this is what he wrote.

The new ROMs don’t quite support all the new datalogging PIDs. But it is something that we will be adding very soon!


Best Regards,
Shiv Pathak
OpenFlash Performance

That vas on March 24th. Can't wait for that to happen so I can get the maf scale closer, especially from 5000rpm up. I get readings of 10.5 AFR around 7k, right now I'm just slowly lowering the maf scale in the upper ranges down. Now I have 5k and up at 11.8-12.2afr range.

The only changes I made wss a few days ago when I flashed the new OFH tune aI wonder if that fixed it.

Update: So I flashed back to the Stage 2 (non ofh specific tune), and now I am no longer getting the MAF voltage and IAM readings again.

I've only run the stage 1 93 tune and the el e85 tune F00C, both of those have the iam working.

Hmm...maybe I should try the 93 tune too. F00C for me too.

@steve99 @Shiv@Openflash as you may already read about my issues with my OFT not reading MAF voltage aswell as IAM and maybe even other data channels aswell I would like to add that when I flashed the new OFH tune on my car using a non OFH (1320 uel) now all those data channels are working fine as I now get MAF voltage and IAM readings with the OFH map. Is there a way I could take OTD Stg 2 91 UEL F00C tune and apply only tune numbers/values/parameters whatever is the proper word onto the OFH tune and overwrite those values just so that I could have the tune from OTS stg 2 but also have what ever it is about the OFH map that allows the OFT to read the MAF voltage, IAM???

The oft logging works by reading ECU ram addresses. unfortunately for each rom type ie B01C D00C F00C ect these addresses change.


It possible that your older tune was based on a rom id where the logging addresses did not work, but the newer tune is based on a rom that the addresses work.


something you will have to take up with oft guys.


internally in oft it likely looks something like we use with Tactrix, and each rom type will have a different address


paramname = IAM
paramid = 0xFFF8119C
isfloat = 1


paramname = MAF_V
paramid = 0xFFF842AC
databits = 16
scalingrpn = x,0.000076293945,*

paramname = IAT
paramid = 0xFFF87C64
isfloat = 1

paramname = ECT
paramid = 0xFFF87C68
isfloat = 1

paramname = BattVolt
paramid = 0xFFF87C6C
isfloat = 1

paramname = MAF
paramid = 0xFFF87C70
isfloat = 1

paramname = OilTemp
paramid = 0xFFF87C74
isfloat = 1


　

Or I guess it is easier if i used romraider and change the values in the table of the OFH and put that of the numbers from the OTS stage 2. Or is it much more complicated than that? Lol damn. I guess this calls for a "custom tune" from openflash. Do you do your own custom tuning? What.part in the map do you mainly make adjustments to?

I think it may be a problem with the oft logging or the tune.


post up a copy of the tune that was getting heaps of knock,

Here is the OTS Stg2 91 UEL F00C that I use from the latest OTS v2.076 off the website. I checked the older OTS v2.072 and OTS v2.074 and the dates on this one .bin are all dated 9/21/2015 and in the release notes

"9/22/15
v2.069
-Added Flat-foot-Shift (FFS) and Launch Control (LC) functionality to all 6MT F00C ROMs.
-Added revised XML file (with FFS and LC defined) for F00C Calibration ID."

I double checked my old logs and it appears i've been running -5 FLKC the whole time since I bought and flashed with the OTS map and that is almost 2 months now. I'm really hoping im not destroying my motor. My car is only 6 months old from the dealership damn lol

I take it back, the el e85 tune doesn't have iam working. Also my flck runs -2.5 to -3.2 or so.

I just looked at the F00C tune you posted up in romraider. The rom is actually a F00C rom its not had any calid changes.

also the max timing is about 24 degrees in base B plus about 2.5 in Knock correction so total max is about 26 at engine load 1.3

Strangely the logs you posted show ignition advance of 33 degrees, this appears to be bogus as does the FLCK parameter as is constantly -5, even when your coasting off the throttle.

ie the tune looks ok, but i think the logging parameters are mostly incorrect.

Just want let you know that Shiv sent me a stg 2 91 uel f00c rom to test if the OFT reads the MAFv and IAM. After flashing this I am happy to say that the OFT does report MAFv and IAM and FLKC (btw flkc used to report mostly -5. but now it is at "0" most of the time) And as he requested, I did somde some 2k-7.5k WOT 3rd gears pulls and sent him the logs.
here are my logs from the pulls after this flash

http://www.datazap.me/u/dru670/stg-2...data=1-2-12-13

this is what I was getting with the OTS Stg 2 91 UEL prior

http://www.datazap.me/u/dru670/ots-s...d?log=0&data=1

Some slight knock, have seen worse. I would focus on getting your maf scale right, first.

Yes it all seems to be logging normal now timing and FLKC now look normal

MAF scale?....oh boy...ill be up till 4am again studying on how to do that lol.

Just check links of steve99's sig. He made guide to describe / simplify that and many other things.

Awesome, I look forward to the fixes for the other tunes then!

Same issue here on a 2016 BRZ F00C cal id

please help

does anybody know if this issue is solved (MY16 not reading MAF voltage, IAM, etc) with OTS 4.0 roms recently released ?

Yes will work on v4 as they are based on A01G or I rom which logging works fine