MS3 Enhanced P0106 MAP Sensor
#2
Elite Member
iTrader: (10)
Join Date: Jun 2006
Location: Athens, Greece
Posts: 5,987
Total Cats: 359
P0106 is an internal barometer fault code. It essentially checks the barometer and MAP sensor reading 1 second after the ignition is on and while RPM is still 0. If the difference between the two is more than 6.4kPa, the P0106 code is stored. One reason the code may be triggered is if you almost immediately crank the engine (so the MAP reading starts to go low) but the ECU still hasn't detected any RPM. Please check if this code happens if you wait until the fuel pump stops priming, and then crank.
What other codes are you getting?
What other codes are you getting?
#3
Oh, thanks, Reverant, that may have been the issue.
The other ones I keep getting are:
The other ones I keep getting are:
- P0219 overspeed
- P0217 overtemp
- P0116 clt range/performance
- P0122 tps out of range
- P0112 intake air temp low input
#4
Elite Member
iTrader: (10)
Join Date: Jun 2006
Location: Athens, Greece
Posts: 5,987
Total Cats: 359
P0219 is stored if the ECU sees more than 8500rpm while the engine has been running for more than 45 seconds.
P0217 is stored if the ECU sees more than 108C (227*F) while the engine has been running for more than 45 seconds.
P0216 is a complex one and may be a bug, as I get it too some times. It essentially checks the coolant temp over time, checking the internal real time clock as a reference. I would recommend disabling this one.
P0122 registers if the ECU reads a TPS value of less than -5%, so you may need to re-check your TPS calibration.
P0217 is stored if the ECU sees more than 108C (227*F) while the engine has been running for more than 45 seconds.
P0216 is a complex one and may be a bug, as I get it too some times. It essentially checks the coolant temp over time, checking the internal real time clock as a reference. I would recommend disabling this one.
P0122 registers if the ECU reads a TPS value of less than -5%, so you may need to re-check your TPS calibration.
#6
Elite Member
iTrader: (10)
Join Date: Jun 2006
Location: Athens, Greece
Posts: 5,987
Total Cats: 359
Did you ever get a configuration error in TunerStudio? When it happens, the RPM gauge goes to 65000+ RPM, and so it may trigger the CEL. Also, is it somewhat persistent? Ie if you clear the codes, does it come back again?
#9
Saw the Est Air Intake Temperature gauge going all over the place today (noticed -20F to 100F) for 20+ mins of driving. I don't have CLT/MAT blending so that should be solely the MAT sensor. Saw the AFR gauge jumping around as well, assume because of the MAT Air Density Table correction. I've attached an MSL log but I don't think I can view it myself unless I get megalogviewer, is that right?
#11
Rev, I forgot that I always do wait until the beeping stops before I crank the engine. I got into that habit 10 years ago when I was using a PC-Pro controller. I keep getting P0106, does this mean there is something wrong inside the MS3?
P0106 is an internal barometer fault code. It essentially checks the barometer and MAP sensor reading 1 second after the ignition is on and while RPM is still 0. If the difference between the two is more than 6.4kPa, the P0106 code is stored. One reason the code may be triggered is if you almost immediately crank the engine (so the MAP reading starts to go low) but the ECU still hasn't detected any RPM. Please check if this code happens if you wait until the fuel pump stops priming, and then crank.
What other codes are you getting?
What other codes are you getting?
#12
Elite Member
iTrader: (10)
Join Date: Jun 2006
Location: Athens, Greece
Posts: 5,987
Total Cats: 359
Please send me a log as follows:
1) Connect the laptop to the ECU
2) Open TunerStudio and your project
3) Click datalogging -> Start
4) Switch the ignition on
5) Wait 10 seconds
6) Start the car, let it idle for 20 seconds
7) Click Datalogging -> Stop
8) Send me the log.
1) Connect the laptop to the ECU
2) Open TunerStudio and your project
3) Click datalogging -> Start
4) Switch the ignition on
5) Wait 10 seconds
6) Start the car, let it idle for 20 seconds
7) Click Datalogging -> Stop
8) Send me the log.