History of MembersPage/EricN/Sensor
Older Newer
2006-01-19 18:57:06 . . . . MembersPage/MarcellGal [don't worry about MAP-slope]
2006-01-19 09:14:16 . . . . EricN [cleaned]
2005-10-10 23:31:39 . . . . d64-180-145-165.bchsia.telus.net [ditched honda map sensor for a GM one, looks better but truck has no vacuum to b]
2005-08-05 21:30:39 . . . . MembersPage/JörgenKarlsson [MAP sensor]
2005-08-05 20:14:23 . . . . EricN


Changes by last author:

Changed:
MAP - This one may be a problem. Havent looked to hard into it but if I set the MAP range in MegaTune to 104 KPA (I assume that is normal for a naturally aspirated engine) megatune only shows 60 kpa (ish). If I set the range to around 160 KPA, I get it right. (I am at sea level).

I gave up on the Honda map sensor and went with a GM one. Way less hassle, everything works the way it should now. The Honda sensor still read in a linear fashion but I couldnt configure it to swing to readings that I am used to.

----

Honda MAP sensor

With the honda sensor, if I set the MAP range range to around 160 KPA, I get it right. (104kPa at sea level). The Honda sensor still read in a linear fashion, so this is perfect. You shouldn't worry about proper MAP-range being 160 kPa (config.kpaoffs=50, that is decimal 80). This means the sensor slope is 5V/160kPa, it is a charactersitics of the sensor. Values near 102, 246 and 390 are often used for sensors (GM 104 kPa, Motorola 250 and 400 kPa respectively). The fact that your sensor will never see >104 kPa pressure does not effect the slope of the sensor.

Maybe MAP-range in MegaTune should be renamed to MAP-slope ? Or MAP-range(slope).

Anyway, gave up on the Honda map sensor and went with a GM one. Way less hassle, everything works the way it should now.