Switched to MSnS-E and now it won't start

tristanlee85 · Post by **tristanlee85** » Sun Jul 16, 2006 11:17 am

I originally had the MS1 and a decent VE table for normal driving. I decided to upgrade to get a larger VE table and extra goodies when I get down the road. Now that I've switched over, the car won't start nor will it attempts.

I'm getting a cranking RPM of 250 - 300 and in the "More cranking stuff" menu, I've set my cranking RPM to 400. I also tried 450. I went through and changed everything to how it was on the MS1 (constants, etc) and it just won't even try to fire.

If it helps, here is my MSQ file. I'm using the 029q2 code.

http://www.plastikhosting.net/uploads/t ... -06_01.msq

tristanlee85 · Post by **tristanlee85** » Sun Jul 16, 2006 1:53 pm

Is it possible to re-program it back to the MS1 code?

renns · Post by **renns** » Sun Jul 16, 2006 2:43 pm

When I loaded your .msq, MT reported a bunch of errors in audit.log. Mostly pressure units inconsistencies. That could be due to my .ini file setup though.

From a quick glance at your settings, a couple items popped up:

Are you running the early MPX4115 map sensor? That unit was only used on a few of the early MS boxes. The default today is teh 250kPa unit.

Your cranking pulse widths all show as 0.1ms, which is likely the cause of your no-start situation. Go into the cranking page and set up the cranking pulse width table using the cranking values you had from your earlier setup.

Hope that helps,
Roger.

tristanlee85 · Post by **tristanlee85** » Sun Jul 16, 2006 2:53 pm

I'll try the 250kPa sensor. I'm using the v3.0 board so it should be the 250kPa. I missed that. As far as the prining pulses, on the MS1 original code, I didn't set any priming pulse simply because I was getting a tach reading and it was starting up just fine.

tristanlee85 · Post by **tristanlee85** » Sun Jul 16, 2006 2:54 pm

Also, I opened the audit.log file, but I'm not sure exactly that to look for. It's giving my 6 errors.

tristanlee85 · Post by **tristanlee85** » Sun Jul 16, 2006 2:57 pm

I mean, I found the warning, but I don't know what to look for and what exactly to change.

Code: Select all

C:\Program Files\MegaSquirt\car1\tristanlee85-MSnSE_fuel-only_v029q2_7-16-06.msq:Open
   WARNING(03): Value from option list "HCutLCType" = "INVALID" not found.

   WARNING(03): Value from option list "HCutType" = "INVALID" not found.

   WARNING(03): Value from option list "OvrBCutType" = "INVALID" not found.

   WARNING(03): Value from option list "freqDiv" = "INVALID" not found.

   WARNING(03): Value from option list "crankpwip" = "INVALID" not found.

   WARNING(03): Value from option list "pwmidlewhen" = "INVALID" not found.


Warning Details
---------------

   WARNING(03) means that the value expressed in the file for the
               constant was not found one of the options listed in the
               current configuration.  The constant was not altered, so
               you probably want to look more closely at this one and
               see what caused the mismatch.

C:\Program Files\MegaSquirt\car1\tristanlee85-MSnSE_fuel-only_v029q2_7-16-06.msq:Close


C:\Program Files\MegaSquirt\car1\tristanlee85-MSnSE_fuel-only_v029q2_7-16-06.msq:Open
   WARNING(03): Value from option list "HCutLCType" = "INVALID" not found.

   WARNING(03): Value from option list "HCutType" = "INVALID" not found.

   WARNING(03): Value from option list "OvrBCutType" = "INVALID" not found.

   WARNING(03): Value from option list "freqDiv" = "INVALID" not found.

   WARNING(03): Value from option list "crankpwip" = "INVALID" not found.

   WARNING(03): Value from option list "pwmidlewhen" = "INVALID" not found.


Warning Details
---------------

   WARNING(03) means that the value expressed in the file for the
               constant was not found one of the options listed in the
               current configuration.  The constant was not altered, so
               you probably want to look more closely at this one and
               see what caused the mismatch.

C:\Program Files\MegaSquirt\car1\tristanlee85-MSnSE_fuel-only_v029q2_7-16-06.msq:Close


C:\Program Files\MegaSquirt\car1\tristanlee85-MSnSE_fuel-only_v029q2_7-16-06.msq:Open
   WARNING(03): Value from option list "HCutLCType" = "INVALID" not found.

   WARNING(03): Value from option list "OvrBCutType" = "INVALID" not found.

   WARNING(03): Value from option list "freqDiv" = "INVALID" not found.

   WARNING(03): Value from option list "crankpwip" = "INVALID" not found.

   WARNING(03): Value from option list "pwmidlewhen" = "INVALID" not found.


Warning Details
---------------

   WARNING(03) means that the value expressed in the file for the
               constant was not found one of the options listed in the
               current configuration.  The constant was not altered, so
               you probably want to look more closely at this one and
               see what caused the mismatch.

C:\Program Files\MegaSquirt\car1\tristanlee85-MSnSE_fuel-only_v029q2_7-16-06.msq:Close

tristanlee85 · Post by **tristanlee85** » Sun Jul 16, 2006 4:11 pm

Well I changed the MAP sensor to 250kPa, but left the priming pulses at .1ms because that's how it was on my last config for the MS1 original code. It just cranks and cranks. Doesn't even try to fire.

tristanlee85 · Post by **tristanlee85** » Sun Jul 16, 2006 4:27 pm

Well, I got it to crank up and idle...barely idle, but at least it idles. I just upped the priming pulses to 11ms and 60, 80, and 100*F. Now I just need to work with the afterstart to keep it idling.

renns · Post by **renns** » Sun Jul 16, 2006 5:01 pm

Glad you are making progress. It's odd that you were able to get the engine started with 0.1ms cranking pw. Maybe there's enough residual fuel in the inlet manifold, or you have a massive priming pulse to compensate? In any case, on with the tuning! If you do need to switch back to the standard V3.0 code, that can be done at any time. Instructions are at megasquirt.info. I use EasyTherm, but I'm biased!

Roger.

Post by **jsmcortina** » Mon Jul 17, 2006 5:18 am

Note that it is the cranking pulsewidth you need to tune for startup and not the priming pulse.
Having all 0.1 is incorrect.

James