Please look at datalogs, engine will not start
Forum rules
Read the manual to see if your question is answered there before posting. If you have questions about MS1/Extra or MS2/Extra or other non-B&G code configuration or tuning, please post them at http://www.msextra.com The full forum rules are here: Forum Rules, be sure to read them all regularly.
Please look at datalogs, engine will not start
We are trying to start my brother's 66 Mustang with MS. We have MS-I on a V3 board with MSNS-E version 29q running fuel only with MegaTune 2.25. The engine is a roller 5.0 with TrickFlow heads and Stage 1 cam with 30lb Ford Motorsports fuel injectors. It trys to start but only runs for 1 second before dying. Then we have to flood clear it to get it to start again. I know we are running too rich, but I don't know what to change. What should our Pulse Width be set to for starting and then after start enrichment? I've attached a coulpe datalogs of what is happening. Please look and see what might be off and what we must do to correct it.
-
Bernard Fife
- Super Squirter
- Posts: 1009
- Joined: Mon Feb 16, 2004 3:15 pm
Did you read this: http://www.megamanual.com/v22manual/mtune.htm#howto? A lot of people won't respond if you haven't read the relevant sections of the manual.
Looking at the datalog, it looks like you have engine code 13 (=1+4+8 = running + start-up enrich + warm-up enrich), which is good. However, you also have entered cranking mode again after starting (engine code = 3) so that needs to be fixed.
If this were mine, what I would do is increase the idle speed by turn the idle stop in a turn or two (opening the throttle) - this will help prevent the engine from going into cranking mode and make tuning much easier. You might also want to reduce the cranking speed setting to 250, if your code has that ability. Then reduce the afterstart enrichment a bit, perhaps 5% to 10%. Then try it see if that helps (get a datalog and post it, if you can).
Lance.
-
Bernard Fife
- Super Squirter
- Posts: 1009
- Joined: Mon Feb 16, 2004 3:15 pm
13 is 1+4+8 = running + start-up enrich + warm-up enrich), which is good. Engine code = 3 means cranking, which is defined to be rpm < 300 in most cases. So yes, this is normal.
In the datalog, the rpm is shown as 361, but you are showing a engine code 3, so I assume you have changed the cranking rpm setting. you should probably lower it. Generally lower is better. You want to transition for cranking mode to runing mode as soon as the engine can manage it, generally around 250 to 300 rpm.
However, with the exception of one transition period, the values in the datalog are constant, so I suspect there may be a problem with the communications. Have you set the interwrite delay to 5 or more as instructed here: http://www.megamanual.com/connect.htm?
Could you post your MSQ file so we can have a look?
Lance.
Thanks for the quick response. We haven't been having any issuse that we know of communication between the laptop and MS. This is what I have in the common.ini file.
[Constants]
writeBlocks = off ; Default is on.
interWriteDelay = 1 ; Milliseconds delay after each byte when writeBlocks is "on".
This is what the MS manual says to set it for using a USB to serial adapter and MS1.
http://www.megamanual.com/connect.htm#ms1
Also my cranking rpm is set to 300 so it doesn't make since for my rpm to be 361 and still in cranking mode. I don't know why that is happening. I tried to go to 250 but it defaults back to 300. It seems to only take 100 rpm increments.
Here is my MSQ file.
-
Bernard Fife
- Super Squirter
- Posts: 1009
- Joined: Mon Feb 16, 2004 3:15 pm
I don't know much about MSnS-E, so I can't comment on all of your MSQ, but I think that since your crank rpm is set to 300, yet you are showing cranking at 361, I would be tempted to reload the code to MegaSquirt's processor.
I would also set the interwrite delay to 5 (though that probably won't help, it can't hurt).
If relaoding the code doesn't help, I would wipe MegaTune and reinstall, then reload the code once more. The reason I suggest this is that it's possible the INI fiule has been corrupted in some subtle way (though I doubt it).
Lance.