Hey,

Looking to see if anyone can help me with a ECU or firmware issue im having.

Running a MSPNP 1 90-93 ecu, worked great up until recently. Was running MSnS Extra 029q.

I tried to load HiRes firmware last Saturday, It failed right near the end of the load, did not do the final boot check at the end i think. Also my main relay went out, i believe during the firmware load attempt. This caused a few more problems, which i think are resolved now.

Anyways, i have been attempting to reload the old firmware back on. I have had a few successful loads. Would get over 1700 lines, said that it was complete, ecu lights come on, fuel pump primes, gets detected by tuner studio, can creat a project and load tune etc. How ever, one time when i attempted to start the car i would get fuel during cranking but not spark. When i put key back to ON after cranking it would backfire, so it sparked at that point. Another time after what seemed to be a successful firmware load i would get spark during cranking but not fuel. So still not starting by then. Both these firmware loads were with boot jumper in place.

Then i attempted a firmware load without boot jumper, said it was successful, showed 12.5V for controller, ask to load map etc. I got it set up once again with tuner studio. Now the car would start but ran like crap; if i did not hold throttle it would stall, PW and DC values were out to lunch, afr's pig rich, spark angle at like 55, etc. Will post a log and tune file from this start up.

Always had the coils unplugged for firmware loads.

Is my ECU acting up or is the firmware not going on properly?

If anyone can help that would be greatly appreciated, super frustrated with this!

 

you are driving around with the timing locked at 10° for starters. the rest of the map seems fine -- if the firmware failed to load properly you would even be able to load a tune or communicate.

 

Thanks for your reply brain!

I am not driving around at all since i cannot get it to run. In the tune it is set to -10 which =use map. What did you see see that indicates it is locked to 10 degrees?

I have had what seem to be successful firmware loads but it will not run. What should i be seeing at the end when firmware is finished loading? How many bytes should it report?

Also almost everytime i go to load a map it gives a difference report for nitrous system, this i have never seen in the past. Also now in some of these recent logs it has an indicator for NosON, but none of my logs before have had this.

This all started when i tired to load the 9697 without MAF firmware, it failed and right when it failed my injectors started clicking and were actually putting in fuel. Nothing else came on when i put key to ON but the injectors. Now i cant reload the old firmware and have it work properly.

 

for some reason i thought i only saw 10, not -10.

iirc its like 1730 bytes? 1830? something like that.

difference report is cause of additional features in newer firmware compared to your old, just ignore them.


did you remember to unplug your coils the first time? its possible you damaged them during the flash.

 

Always had the coils unplugged, they are fine!

The 1700 is for the lines, as they call it in the firmware load. Needs to get over 1700 lines to be done. The bytes is after this, when it gets over 1700 lines and it says complete and successful etc it also tells you the voltage at controller and i noticed something about bytes. My last one that i saw said 27 thousand ish bytes. So im thinking that's how much information got loaded?

At this point i am only trying to reload back the 90-93 without afm firmware (MSnS Extra 029q), i did two attempts for the hi res and both times it gets over 1700 lines and fails right after that.

I noticed that when i get the project set up in tuner studio the intial tune that is loaded to the ecu is the default one, it is in the default files folder from 90-93 without afm folder. It has the nitrous system set to turned off and so does the tune that i go to load on. But it gives a difference report that does not match what each tune file has in nitrous system. So something is iffy there.

I have had lots of successful firmware loads with or without the jumper. However its when i go to get everything set up that things are off. I have had it where it does not detect that i have a vtps so i cant calibrate it. Then i have had it where everything loads on fine but i dont get spark while cranking, however it does spark when key turns to ON because i get a backfire. Then another time it would spark while cranking but no fuel going in. I have also had it where the load is successful but no lights on the ecu come on, and i have had successful loads where the lights come on when ecu has power to it.

The most success i have had so far is everything got loaded, ecu lights came on, calibrated tps, set up project, loaded tune, coolant and IAT were showing believable values etc. The car started but it was dumping fuel. PW and Duty Cycle were out to lunch. That log that i posted is of this start up. Would stall right after starting but i held the throttle a bit to keep it going just to get some data for the log. Can you check it and tell me what you think?

 

Update:

Loaded firmware again, set up the project, loaded tune. Still runs like crap, PW and Duty cycle are improved from before but still not right. Dont think i was getting spark in all 4. I have a few logs from me starting it.

When i have key to ON on the ecu main board lights D16 and D14 or on bright. While it is running, i see one light on bright and one that is on but dimmer. Dont know which it was exactly, either still D16 and D14 or to the right of them if you are looking down on the board.

Also i have a screenshot from when the firmware load completed, showing amount of lines it got to and the bytes value. Let m,e know if it looks normal.

 

Here are the files mentioned in previous post.

 

Anybody have any ideas???

Is this more likely to be a ecu issue or a firmware not loaded properly issue?

 

The firmware is loading correctly. But where did you get the firmware file? did you run easytherm to create it? did you put the two .therm files into the proper tuner studio directory? your MAT and CLT are reading mighty low.

Your MAP is reading low.

Your GVE% [255] suggests your fuel map isn't loaded -- did you even load your old msq tune?

 

I am using the files from the MSPNP 1 setup files or Megasquirt Folder. Using the download firmware, ini and inc files from 90-93 without afm folder. I believe they have already been easythermed, and ready to go. This is what i used last year and worked fine. MAT and CLT values are correct, i am using celsius so maybe that is why they seem low.

I think my map reading is fine, this is how it was before when comparing to some of my older logs from when it worked.

Yes i loaded my old tune after setting up the project. Inc files are where they need to be, project configuration/ ini file is where it needs to be.If i go and connect to the ecu tune and all will be there. What is weird though, is that right after firmware loaded i opened tuner studio and detected ecu, set up the project, loaded my tune. Then i shut it down and when i reconnected it gave a difference report that suggested only my tune was in tuner studio and the ecu had nothing on it based of what was in tuner studio settings and what the controller settings were. So i told it to use tuner studio settings, never had the difference report since then.

Let me know what you think.

 

ill have to look at the actual tune when have access to TS, but seeing 255 in the GVE% is probably an issue.

 

Yeah GVE is not right, not sure what is causing it to go that high. Looking at an older log it stayed in the 50-60's. But now it goes from 50-255 constantly. Firmware corrupted possibly?

Also back when i attempted to load the 9697 without maf hi res firmware. It got above 1700 lines but failed and right then my injectors started working. Any idea why that happened. I tried to load that firmware a couple times and it happened both times, failed and injectors came on. I dont know why i cant load that firmware.

 

you are loading the firmware. 1700 lines is normal.

 

I know 1700 lines is normal. What i am trying to figure out is why it fails to successfully complete the load right after it gets above 1700 lines loaded, to me it seems that it is basically done at that point. And then on top of that why the injectors start working when ecu gets power. Nothing gets detected by tuner studio as well.

I am currently trying to get it back up and running with my old firmware since that is all that will successfully load at this pont. But i want hi res on it, just can not get it to load on.

 

try this firmware file

http://ozmx5.com/viewtopic.php?f=4&t=19

 

About to try the 90-93 without afm from that link.

So i will take the ini and s19 file from the folder i just downloaded from the link, create a copy folder of the previous 90-93 without afm folder, delete the ini and s19 files from it, copy in the new ini and s19 files, run download fimrware bat, if successful i will now use the new ini and whatever inc files are in mtcfg folder.

The s19 is the firmware that is loaded on right? Download firmware bat is just what is used to load it?

Thanks for all your help so far brain!

 

Made some progress. I used a different usb port on my computer. I was able to load the hi res and detect it, while loading the whole time the lines increased by 10 if that means anything, set up the project, loaded the tune, no weird difference reports(i have had it where it would keep giving nitous stage 2 difference reports constantly), tps calibrated, in my data log it looks like it did before dont have extra things in there like NosON and some others. So it all seems fine.

But i am not getting spark during cranking. If i let the engine sit for a bit and then turn key to ON i get a small backfire so it has spark when key is ON. Too me everything looks good when comparing it to an old cranking log from when it ran good. Dont know what to check in logs to see if spark is there. Pulled the plugs, very wet and top of pistons wet a bit.

Am i ok using a MSnS Extra 029 tune file with the hi res? Will post a tune and log.

 

Finally got it running and with the Hi Res. I used my spare USB to DB9 cable and a different usb port, worked first try. Guess it was a cable issue the whole time not lading the firmware correctly.

Thanks for your help Brain!