SAE.MAP not working properly with C7Z06

[wesam]

Is there any special PID to use with C7Z06
SAE.MAP reading incorrectly with this car
the testing car is 2016 C7Z06 with stock tune
key on engine off reading 64kpa while it should read 100 kpa also under boost it should read around 150 kpa while it reads only 110 kpa
Log_1G1Y92D61G5603306_0003.efi

[joecar]

Try logging the other MAP pids GM.MAP2 and GM.MAP3.

Also log the MAP voltage GM.MAP.

Is the MAP sensor ok (does the scaling match the sensor...?)...?

[Blacky]

Hi Wesam,

There was an issue in one of the recent updates where some SAE PID scaling values were not being stored correctly in the log file (AFR, MAF and MAP). In the log file you posted the MAP scaling is set to 0 which means "use default SAE scaling". I presume GM have defined a custom scale for the MAP PID in the C7Z06. If they have defined a custom scale for it then it is not being recognized correctly by the software version that you are using to log the data. I recall fixing that issue in a recent update.

Have you tried the latest beta software available here: https://forum.efilive.com/showthread...Beta-Release-4
If you are already using that version, try logging with the V8 pass-thru scan tool or with the FlashScan in standalone black-box logging mode.

Regards
Paul

[wesam]

Hi Wesam,

There was an issue in one of the recent updates where some SAE PID scaling values were not being stored correctly in the log file (AFR, MAF and MAP). In the log file you posted the MAP scaling is set to 0 which means "use default SAE scaling". I presume GM have defined a custom scale for the MAP PID in the C7Z06. If they have defined a custom scale for it then it is not being recognized correctly by the software version that you are using to log the data. I recall fixing that issue in a recent update.

Have you tried the latest beta software available here: https://forum.efilive.com/showthread...Beta-Release-4
If you are already using that version, try logging with the V8 pass-thru scan tool or with the FlashScan in standalone black-box logging mode.

Regards
Paul

Thanks Paul
I'm using the latest public release as i'm in bussiness production
But i will try with the latest beta on my other laptop if it does not need firmware update
Yes it seems the scaling is wrong just in LT4 cars

[wesam]

Hi Wesam,

There was an issue in one of the recent updates where some SAE PID scaling values were not being stored correctly in the log file (AFR, MAF and MAP). In the log file you posted the MAP scaling is set to 0 which means "use default SAE scaling". I presume GM have defined a custom scale for the MAP PID in the C7Z06. If they have defined a custom scale for it then it is not being recognized correctly by the software version that you are using to log the data. I recall fixing that issue in a recent update.

Have you tried the latest beta software available here: https://forum.efilive.com/showthread...Beta-Release-4
If you are already using that version, try logging with the V8 pass-thru scan tool or with the FlashScan in standalone black-box logging mode.

Regards
Paul

Hi Blacky
I installed the latest release candidate and test it
It still has the same problem KOEO 64 kpa idle 19 kpa and WOT is less than expected
please advice

[Blacky]

Hi Blacky
I installed the latest release candidate and test it
It still has the same problem KOEO 64 kpa idle 19 kpa and WOT is less than expected
please advice

Are you using V7 or V8 pass-thru logging?
Or are you using Black Box standalone logging?

When using V8 pass-thru, please save a trace file* after attempting to log about 2-3 seconds of data that shows the incorrect MAP scaling.
Send the *.htx trace file and the *.pld log file to me at paul@efilive.com

* Save the trace file using the EFILive Control Panel->[F8: Trace] option.

Regards
Paul

[wesam]

I'm using V7 pass thru logging
Should i email you a log file ?

[Blacky]

Have you tried it with V8 pass-thru? That's where it was fixed. I'm not sure it was ever fixed back in V7.

Regards
Paul

[wesam]

Have you tried it with V8 pass-thru? That's where it was fixed. I'm not sure it was ever fixed back in V7.

Regards
Paul

No I didn't I still using V7 because i don't have time to setup MAPs and PIDs and still don't know how to setup calculated PIDs in V8
I will be glad for you if you solve this issue in V7

[Blacky]

Until/unless I know the changes made to V8 actually fix the problem there's no point going back and making the same (possibly not-working) changes in V7.
So if you can just do a simple log of 3 or 4 parameters: say RPM, TPS, MAF and MAP in V8 pass-thru with KOEO, transitioning to KOEO for just a few short seconds (or the trace files get too big), that would help me out a lot.

Save the *.htx rtrace file from the V8 Control Panel (more info on saving trace files here: https://support.efilive.com/kb_artic...8552-EOAJ-5912
Send both the *.htx trace file and the *.pld log file saved in the V8 scan tool.

Regards
Paul