HELP - crank but no start
09-12-2014, 10:23 PM
#21
Junior Member
Thread Starter
Join Date: Nov 2012
Posts: 61
Total Cats: -2
Replaced a section of the positive bat cable that melted and it's not heating up anymore as it has good contact to the terminal. Still cranking poorly..
The battery is charging overnight, I'll give it a try tomorrow.
If it's not the battery then I have no ideas at this point but I'll upload my tune file to be sure I have a right firmware.
The battery is charging overnight, I'll give it a try tomorrow.
If it's not the battery then I have no ideas at this point but I'll upload my tune file to be sure I have a right firmware.
Last edited by firefaux; 09-12-2014 at 11:19 PM.
Reply
0
0
09-13-2014, 10:51 AM
#24
Junior Member
Thread Starter
Join Date: Nov 2012
Posts: 61
Total Cats: -2
its fully cranking normally now that the battery is charged but still not firing up.
I smell gasoline and see the wideband go super rich.
Now I have to wait for my wife to be free to test for spark
I smell gasoline and see the wideband go super rich.
Now I have to wait for my wife to be free to test for spark
Reply
0
0
09-13-2014, 11:23 AM
#26
Senior Member
Join Date: Apr 2011
Location: Hollywood, FL
Posts: 807
Total Cats: 163
Are you doing the spark test in TS or cranking over the engine?
Do you have all the plugs out?
If you have stock ignition system and spark at cyl 1, you should also have spark at cyl 4.
Might be a setting you overlooked in ignition set-up. I'll take a look at the msq again. To confirm, stock ignition on a 91, right?
And a log of the event won't hurt either.
Do you have all the plugs out?
If you have stock ignition system and spark at cyl 1, you should also have spark at cyl 4.
Might be a setting you overlooked in ignition set-up. I'll take a look at the msq again. To confirm, stock ignition on a 91, right?
And a log of the event won't hurt either.
Reply
0
0
09-13-2014, 12:32 PM
#28
Senior Member
Join Date: Apr 2011
Location: Hollywood, FL
Posts: 807
Total Cats: 163
Your ignition settings I am assuming are untouched other than the trigger offset of 3.5*.
Is that verified with a light?
Edit: just tried reading your project properties and it gave me an error for the ini file you are using. Tried reading a random msq for mspnp2 I picked off MT.net and read the properties fine. Same for the base map from diyauto.
Might have something to do with your problem.
Is that verified with a light?
Edit: just tried reading your project properties and it gave me an error for the ini file you are using. Tried reading a random msq for mspnp2 I picked off MT.net and read the properties fine. Same for the base map from diyauto.
Might have something to do with your problem.
Last edited by hector; 09-13-2014 at 12:45 PM.
Reply
0
0
09-13-2014, 01:05 PM
#29
Junior Member
Thread Starter
Join Date: Nov 2012
Posts: 61
Total Cats: -2
It was at 3.5 until I tried to crank it and it moved way off to the other side.
I uploaded the mspnp2.ini is that the correct one. I thought I heard you mention ms extra. I see a .ini file in there as well.
I uploaded the mspnp2.ini is that the correct one. I thought I heard you mention ms extra. I see a .ini file in there as well.
Reply
0
0
09-13-2014, 01:30 PM
#30
Senior Member
Join Date: Apr 2011
Location: Hollywood, FL
Posts: 807
Total Cats: 163
I honestly have never uploaded an ini file, I always let TS do it for me.
Every time I update firmware, it prompts me that the firmware version is different in the controller than in TS and would I like for TS to get the correct ini file for the firmware to which I always click yes. It does it for me and I then go to a restore point right before I updated the firmware and I'm done.
According to the instructions http://www.msextra.com/doc/pdf/Megas...ing_Up-3.3.pdf
the only time you insert the ini yourself is when you have beta firmware or TS is outdated. From the manual:
I wish I knew what is wrong but I just get the feeling its the loading of the firmware that's messing with you. I hate to sound like some crazy math teacher and may be way off base, but I would say to clear your head, sit down and thoroughly read and wrap your head around the instructions for loading new firmware as it is really the only difference from when your car ran to now.
The loading firmware instructions start on page 15 of the first link above.
I mentioned MS2/Extra as that is the code your ecu uses. I guess you can call it the operating system. I mention it so you don't try to use MS3 or other code.
Every time I update firmware, it prompts me that the firmware version is different in the controller than in TS and would I like for TS to get the correct ini file for the firmware to which I always click yes. It does it for me and I then go to a restore point right before I updated the firmware and I'm done.
According to the instructions http://www.msextra.com/doc/pdf/Megas...ing_Up-3.3.pdf
the only time you insert the ini yourself is when you have beta firmware or TS is outdated. From the manual:
iv. Other / Browse
This method is recommended only if TunerStudio is not able to detect your Megasquirt, or if you are using a
beta version of the firmware.
The firmware on your Megasquirt may have been provided on a disk or downloaded as a .zip file from the
MegaSquirt Engine Management Systems website. If you have downloaded your firmware and haven't done so already extract the
contents of the zip file to a directory of your choice.
Clicking in the box next to “Other / Browse” opens a screen which lets you browse to your firmware folder.
From here you should be able to select the .ini file that you want to use. It is essential that you use the .ini file
that is appropriate to your Megasquirt. There are four .ini files to choose from:
1. megasquirt2.ini – used for MS2.
2. microsquirt.ini – used for Microsquirt.
3. mspnp2.ini – used for the DIYautotune MSPNP2.
4. microsquirt-module.ini – used for the generic Microsquirt Module. (If you have purchased a
proprietary Megasquirt-2 product based on the Microsquirt Module it is worth contacting the
manufacturer to confirm which firmware/ini version you should use).
Select the file that is appropriate to your Megasquirt and then click Next.
This method is recommended only if TunerStudio is not able to detect your Megasquirt, or if you are using a
beta version of the firmware.
The firmware on your Megasquirt may have been provided on a disk or downloaded as a .zip file from the
MegaSquirt Engine Management Systems website. If you have downloaded your firmware and haven't done so already extract the
contents of the zip file to a directory of your choice.
Clicking in the box next to “Other / Browse” opens a screen which lets you browse to your firmware folder.
From here you should be able to select the .ini file that you want to use. It is essential that you use the .ini file
that is appropriate to your Megasquirt. There are four .ini files to choose from:
1. megasquirt2.ini – used for MS2.
2. microsquirt.ini – used for Microsquirt.
3. mspnp2.ini – used for the DIYautotune MSPNP2.
4. microsquirt-module.ini – used for the generic Microsquirt Module. (If you have purchased a
proprietary Megasquirt-2 product based on the Microsquirt Module it is worth contacting the
manufacturer to confirm which firmware/ini version you should use).
Select the file that is appropriate to your Megasquirt and then click Next.
The loading firmware instructions start on page 15 of the first link above.
I mentioned MS2/Extra as that is the code your ecu uses. I guess you can call it the operating system. I mention it so you don't try to use MS3 or other code.
Reply
0
0
09-13-2014, 10:15 PM
#32
Junior Member
Thread Starter
Join Date: Nov 2012
Posts: 61
Total Cats: -2
This is the tune file of when I followed your instructions and just uploaded mspnp2.s19 from the uploader and put a file of the base maps in mstunerstudio. This is before I discovered the oil leak. My money hole just got bigger 
Last edited by firefaux; 09-14-2014 at 12:00 AM.
Reply
0
0
09-14-2014, 09:43 AM
#34
Senior Member
Join Date: Apr 2011
Location: Hollywood, FL
Posts: 807
Total Cats: 163
I don't know how you are updating your firmware. From your last post it sounded to me like you opened and unzipped the 3.3.2 firmware file, then opened TS and loaded the mspnp.s19 file to it.
Is that what you did?
Is that what you did?
Reply
0
0
09-14-2014, 02:34 PM
#35
Junior Member
Thread Starter
Join Date: Nov 2012
Posts: 61
Total Cats: -2
I uploaded the .s19 file when I unzipped the 3.3.2 and placed the win uploader into the unzipped file for it to detect the firmware options. It ended up giving me a choice of firmwares in the folder and I picked "MSPNP2" as instructed. Opened TS afterwards and loaded the base maps. I got an mismatch error but nothing like what you have in that picture
Reply
0
0
09-14-2014, 04:28 PM
#36
Senior Member
Join Date: Apr 2011
Location: Hollywood, FL
Posts: 807
Total Cats: 163
So to load your firmware you:
1. unplugged your coils
2. connected your laptop to the mspnp
3. made sure all instances of tunerstudio were shut down
4. you ran "ms2loader_win32"
5. accepted all default prompts and got to where it says to make sure megasquirt is powered up.
6. powered up mspnp/turned key to run
7. let loader scan serial ports automatically to find mspnp for you
8. accepted communications port found by loader
9. when asked what type ecu entered mspnp2 and hit enter
10. waited for confirmation everything had been loaded properly
Then you opened tunerstudio and with mspnp powered on and connected to laptop:
1. selected project, new project
2. selected "detect" so tunerstudio could automatically detect the firmware on the mspnp
3. selected accept after confirming new firmware (should be 3.3.2mp for you)
4. went on to project settings and confirmed your settings there and hit next
5. went to comms page and hit next
6. went to dash page and hit next
7. and tunerstudio started from there?
At no time should you have to upload a file manually. The loader and tunerstudio do everything for you. So I find it confusing with the way you mention of loading or uploading files. You very well may be doing things right and I am just not understanding how you are explaining it.
I took a look at your msl and it shows cranking rpms of 1rpm and 13rpm for very brief moments. Clearly thats not right.
I also opened your msq and certain things dont look right to me. Plus the screen I got trying to open the project properties. Although that may have been some kinda glitch on my pc as its not coming up now.
Have you tried doing a spark output test just to see if things are working right? At least you won't drain the battery cranking it over needlessly and it could confirm..... I don't know what it could confirm but at least you know the ignition side of the system is working.
It just doesn't make sense that a firmware update could go so wrong.
1. unplugged your coils
2. connected your laptop to the mspnp
3. made sure all instances of tunerstudio were shut down
4. you ran "ms2loader_win32"
5. accepted all default prompts and got to where it says to make sure megasquirt is powered up.
6. powered up mspnp/turned key to run
7. let loader scan serial ports automatically to find mspnp for you
8. accepted communications port found by loader
9. when asked what type ecu entered mspnp2 and hit enter
10. waited for confirmation everything had been loaded properly
Then you opened tunerstudio and with mspnp powered on and connected to laptop:
1. selected project, new project
2. selected "detect" so tunerstudio could automatically detect the firmware on the mspnp
3. selected accept after confirming new firmware (should be 3.3.2mp for you)
4. went on to project settings and confirmed your settings there and hit next
5. went to comms page and hit next
6. went to dash page and hit next
7. and tunerstudio started from there?
At no time should you have to upload a file manually. The loader and tunerstudio do everything for you. So I find it confusing with the way you mention of loading or uploading files. You very well may be doing things right and I am just not understanding how you are explaining it.
I took a look at your msl and it shows cranking rpms of 1rpm and 13rpm for very brief moments. Clearly thats not right.
I also opened your msq and certain things dont look right to me. Plus the screen I got trying to open the project properties. Although that may have been some kinda glitch on my pc as its not coming up now.
Have you tried doing a spark output test just to see if things are working right? At least you won't drain the battery cranking it over needlessly and it could confirm..... I don't know what it could confirm but at least you know the ignition side of the system is working.
It just doesn't make sense that a firmware update could go so wrong.
Reply
0
0
Thread
Thread Starter
Forum
Replies
Last Post
Frank_and_Beans
Supercharger Discussion
13
09-12-2016 08:17 PM
Mikel
MEGAsquirt
4
09-28-2015 04:46 PM
