Yes and it's correct.
Evoscan scaling is x*0.2745-20 Request ID A1
I'm guessing you don't have the EFI 3000GT ECU selected.
http://i.imgur.com/PLmII.jpg
Printable View
Yes and it's correct.
Evoscan scaling is x*0.2745-20 Request ID A1
I'm guessing you don't have the EFI 3000GT ECU selected.
http://i.imgur.com/PLmII.jpg
That's what I have and efi 3000gt ecu has been selected since I started all this.
It reads right around 0psi at idle, and any boost at all reads the max psi. Hmmm...
Any chance its an issue with the pin differences between jesters 94-97 PnP ecu and an actual 98-99 ecu?
Best to shoot Adam a message.
Are you using pin 74 on the PNP Flash ecu??
Here is the link on the chromedecu.org website Chromed ECU | Sensor Scaling
Hmm. I found my problem. I bought the wrong sensor LOL. DOH!
I got an EVO 8 sensor. Whoops!
LOL!!! You get to wear the dunce hat.
I should have guessed based on that Adam doesn't change anything with the map input. Its the same on all ECUs.
Haha, well glad you figured it out!
Hi guys - I have the Evo X MAP and scaling setup per the other posts for it. Using Chrome 2.0 and just started doing some logging in EvoScan 2.9 using MAP Scaled field for the first time (had been relying on LCDBC output before). EvoScan shows -3.25 PSI with engine off.
I think this is correct given I'm at 5k feet above sea level in Fort Collilns, CO assuming the sensor is reading absolute pressure and scaling is based on sea level.
I'd like to zero this out in EvoScan so its showing relative boost/vac. Should I just change the EvoScan formula from x*0.2745-20 to x*0.2745-16.75 to accomplish this or am I better off changing scaling in Chrome?
I had thought about tying the map scaled equation into the baro sensor in order to get a relative pressure reading. Since map sensors can't compensate for barometric pressure on their own, this would make it more accurate.
For now, edit the evoscan formula to add another 3.25 like you are saying.