MSPNP MSPNP specific Megasquirt related discussion.
Sponsored by:
Sponsored by:

MSPNP Pro Bad MAP sensor?

 
Old 11-06-2015, 06:48 PM
  #1  
Newb
Thread Starter
 
Join Date: Jul 2013
Location: Alfred, Maine
Posts: 35
Total Cats: 3
Default MSPNP Pro Bad MAP sensor?

My read out for the map sensor is bouncing around 16-4 Kpa with out the vacuum line attached. there is no change when it is attached to the car.
my car will fire up sputter and die.
I thought i may have been a clogged line so i disconnected it and nothing.
anyone else seen this / have a suggestion for fix?
Should i send it in for repair?
this is currently my only car so kinda really sux.

I have been extremely happy with my PNP Pro until this happened.
abenson100 is offline  
Old 11-09-2015, 04:04 PM
  #2  
Supporting Vendor
 
Matt Cramer's Avatar
 
Join Date: Sep 2006
Posts: 2,329
Total Cats: 62
Default

Try recalibrating the sensor under Tools -> Calibrate MAP/ Baro. If that doesn't fix it, check to be sure the internal / external MAP selection jumper isn't loose.
__________________
Matt Cramer
www.diyautotune.com
Matt Cramer is offline  
Old 11-09-2015, 11:29 PM
  #3  
Newb
Thread Starter
 
Join Date: Jul 2013
Location: Alfred, Maine
Posts: 35
Total Cats: 3
Default

so installing new firmware brought the map sensor back but now i have a bunch of errors. attached is my tune from before this all went side ways.

see below


40 Warnings:
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:tsw_pin_f equal to the proposed Digital In 4
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:tsw_pin_s equal to the proposed Digital In 4
Warning: Value in .msq '"TPSdot"' for parameter: EAElagsource is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.
Warning: Value in .msq '"Off"' for parameter: boost_ctl_settings_initialvals is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.
Warning: Value in .msq '"Basic"' for parameter: boost_ctl_settings_tunemode is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:ac_idleup_io_in equal to the proposed Digital In 4
Warning: Value in .msq '"Basic"' for parameter: boost_ctl_settings_tunemode2 is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:vss_opt4 equal to the proposed Digital In 4
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:ltt_but_in equal to the proposed Digital In 4
Warning: MSQ Units Mismatch for tc_minmap! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:shift_cut_in equal to the proposed Digital In 4
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:dualfuel_pin equal to the proposed Digital In 4
Warning: n2o1_time array size does not match the currently loaded configuration,
rescaled .msq values to match configuration.
Warning: n2o1_rpm array size does not match the currently loaded configuration,
rescaled .msq values to match configuration.
Warning: n2o1_duty array size does not match the currently loaded configuration,
rescaled .msq values to match configuration.
Warning: n2o1_pw array size does not match the currently loaded configuration,
rescaled .msq values to match configuration.
Warning: n2o2_pw array size does not match the currently loaded configuration,
rescaled .msq values to match configuration.
Warning: n2o1_retard array size does not match the currently loaded configuration,
rescaled .msq values to match configuration.
Warning: n2o2_time array size does not match the currently loaded configuration,
rescaled .msq values to match configuration.
Warning: n2o2_rpm array size does not match the currently loaded configuration,
rescaled .msq values to match configuration.
Warning: n2o2_duty array size does not match the currently loaded configuration,
rescaled .msq values to match configuration.
Warning: n2o2_retard array size does not match the currently loaded configuration,
rescaled .msq values to match configuration.
Warning: launch_time array size does not match the currently loaded configuration,
rescaled .msq values to match configuration.
Warning: launch_retard array size does not match the currently loaded configuration,
rescaled .msq values to match configuration.
Warning: psEnabled array size does not match the currently loaded configuration,
noSizeMutation set for parameter values transfered to new array size where possible.
Warning: psCondition array size does not match the currently loaded configuration,
noSizeMutation set for parameter values transfered to new array size where possible.
Warning: psCondition row:0, col:48, Invalid value: 0.0, Set to the 1st valid value: 60.0
Warning: psCondition row:0, col:49, Invalid value: 0.0, Set to the 1st valid value: 60.0
Warning: psCondition row:0, col:50, Invalid value: 0.0, Set to the 1st valid value: 60.0
Warning: psCondition row:1, col:48, Invalid value: 0.0, Set to the 1st valid value: 60.0
Warning: psCondition row:1, col:49, Invalid value: 0.0, Set to the 1st valid value: 60.0
Warning: psCondition row:1, col:50, Invalid value: 0.0, Set to the 1st valid value: 60.0
Warning: psConnector array size does not match the currently loaded configuration,
noSizeMutation set for parameter values transfered to new array size where possible.
Warning: psConnector row:48, col:0, One or more value below minimum: 0.0, Set to the minimum value: 32.0
Warning: psInitValue array size does not match the currently loaded configuration,
noSizeMutation set for parameter values transfered to new array size where possible.
Warning: psPortValue array size does not match the currently loaded configuration,
noSizeMutation set for parameter values transfered to new array size where possible.
Warning: psOutSize array size does not match the currently loaded configuration,
noSizeMutation set for parameter values transfered to new array size where possible.
Warning: psOutOffset array size does not match the currently loaded configuration,
noSizeMutation set for parameter values transfered to new array size where possible.
Warning: psThreshold array size does not match the currently loaded configuration,
noSizeMutation set for parameter values transfered to new array size where possible.
Warning: psHysteresis array size does not match the currently loaded configuration,
noSizeMutation set for parameter values transfered to new array size where possible.
Attached Files
abenson100 is offline  
Old 11-09-2015, 11:47 PM
  #4  
Newb
Thread Starter
 
Join Date: Jul 2013
Location: Alfred, Maine
Posts: 35
Total Cats: 3
Default

Got it started for about 10 minutes then the sensor went back to reading 7.8 kpa constantly
abenson100 is offline  
Old 11-12-2015, 04:12 PM
  #5  
Newb
Thread Starter
 
Join Date: Jul 2013
Location: Alfred, Maine
Posts: 35
Total Cats: 3
Default

all jumpers are glue in place from the factory.
the sensor calibration was set correctly. I changed it and changed it back but the was no effect.
abenson100 is offline  
Old 11-12-2015, 07:33 PM
  #6  
Ben
Supporting Vendor
iTrader: (33)
 
Ben's Avatar
 
Join Date: Jul 2006
Location: atlanta-ish
Posts: 12,651
Total Cats: 111
Default

Sounds like a fault in the sensor itself then. Send email to [email protected], and one of my guys will get you squared away.
__________________
DIYAutoTune.com Tech Support
10AE-T|BEGi S4|MSPNP-Pro EMS|Enthuza Duals|6UL|Etc
Track Rat|2001|VVT|MS3-Pro EMS|Enthuza|Exocet in Progress

Originally Posted by concealer404 View Post
Buy an MSPNP Pro, you'll feel better.
Ben is offline  
Old 11-12-2015, 10:06 PM
  #7  
Newb
Thread Starter
 
Join Date: Jul 2013
Location: Alfred, Maine
Posts: 35
Total Cats: 3
Default

Thanks Ben. I have contacted your support email. I think i was talking with you actually.
abenson100 is offline  
Old 01-31-2016, 08:03 PM
  #8  
Newb
Thread Starter
 
Join Date: Jul 2013
Location: Alfred, Maine
Posts: 35
Total Cats: 3
Default

just got my PNP back from DIY. it took the post office 2 weeks to deliver a 2-day express.
everything seems to be up and working now. thats for the warranty repair of the MAP sensor you guys are great.
abenson100 is offline  
 
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
psyber_0ptix
Engine Performance
34
12-10-2016 08:51 PM
.one lane
MSPNP
11
11-14-2015 10:09 PM
Tim18t
MEGAsquirt
5
11-09-2015 04:06 PM
akbloom
Miata parts for sale/trade
5
11-09-2015 11:48 AM
Wino
MSPNP
4
11-02-2015 08:17 PM


Thread Tools
Search this Thread
Quick Reply: MSPNP Pro Bad MAP sensor?


Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

© 2019 MH Sub I, LLC dba Internet Brands

We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.