Welcome to the 2GNT Forum! Interested In Advertising with 2GNT?
Home | Site Background| Info&Specs| Mods & Tech Info | CAPS | Part Reviews | Donate | 2GNT Stickers |
Search Printer-friendly copy Email this topic to a friend 0 Users in Chat
Top 2GNT Technical Performance/Engine Engine Management Systems & Controllers topic #5452
View in linear mode

Subject: "RE: Megasquirt load vs map sensor" Previous topic | Next topic
740 turbo brickJan-02-12 11:22 PM
Member since Jun 09th 2008
831 posts,
Click to send email to this author Click to send private message to this author Click to view this author's profile Click to add this author to your buddy list
#5457, "RE: Megasquirt load vs map sensor"
In response to In response to 4




          

The only time Ive had an issue with it saying anything other than 98-100 when not running is when the sensor wasnt calibrated right. I have the 3 bar sensor and it was calibrated for 2.5, making my gauge read like 85% or so.


95 Eclipse GS: 10.5:1, Crower 2's and MSII
186 WHP - 150 WTQ
14.697 @ 93.85 MPH......Gone, but not forgotten
99 420A Avenger: Given to my sister
99 GS OZ: Sold
03 Evo 8: Family Car with balls

  

Report This Post to Admin Printer-friendly copy | Reply | Reply with quote

Megasquirt load vs map sensor [View all] , SilvrEclips, Jan-01-12 12:10 PM
  RE: Megasquirt load vs map sensor, AdministratorCODE4, Jan-01-12 12:21 PM, #1
RE: Megasquirt load vs map sensor, SilvrEclips, Jan-01-12 12:33 PM, #2
      RE: Megasquirt load vs map sensor, AdministratorCODE4, Jan-01-12 07:53 PM, #3
           RE: Megasquirt load vs map sensor, SilvrEclips, Jan-01-12 09:17 PM, #4
                RE: Megasquirt load vs map sensor, 740 turbo brick, Jan-02-12 11:22 PM #5
                     RE: Megasquirt load vs map sensor, SilvrEclips, Jan-10-12 09:06 PM, #6

Top 2GNT Technical Performance/Engine Engine Management Systems & Controllers topic #5452 Previous topic | Next topic
Powered by DCForum+ Version 1.2
Copyright 1997-2003 DCScripts.com

I generated this page in 0.018359899520874 seconds, executing 14 queries.