HELP! DIYPNP almost destroyed my car
12-20-2013, 09:00 PM
#1
Newb
Thread Starter
Join Date: Dec 2013
Posts: 8
Total Cats: 1
HELP! DIYPNP almost destroyed my car
First post on this forum, so please go easy. I promise I'll add an introduction too! I really really really am hoping you guys can help. I don't have any friends who understand this stuff, so I don't have anywhere to turn. So here goes:
So first off, admittedly the DIYPNP was controlled by me, so I almost destroyed my car, but nonetheless I am quite confused. I have a 1999 miata and just finished building my DIYPNP. I got the sequential board and I believe I jumpered everything up correctly (including the seq injection jumpers). So I put on the 1999 seq base map, calibrated my sensors, verify the critical values are set (no crazy AFR, Dwell set reasonable) and I start the car. I could not get the car to start on its own, but adding some gas I was able to get it started. I "thought" it was just running rough, so I played around with the AFR maps etc to see if anything would make it run better. While burried in tunerstudio, I start to smell oil. Looking up, I notice there is a good amount of smoke and that there is certainly burning oil. At this point I let it cool and pulled the plugs; Cyl 1 & 3 were almost completely fouled and black, and cyl 2 & 4 looked normal. luckily the car runs well with the stock ECU (I was quite concerned I REALLY ruined something.....) but at this point I am assuming that cyl 1 & 3 are getting fuel, and since 1 &4 are not, the ecu is shooting more fuel into 1 & 3 to get the AFR's correct? I have my tune here (WBO2 isn't connected correct in this data log, I found that issue right away and fixed it, after which I experienced the above story). I can get another datalog for you guys if you need, but I'm still trying to figure out what I did wrong....
Also attached is the tune (re-named, I know you guys don't like it when people don't rename the tune!)
So first off, admittedly the DIYPNP was controlled by me, so I almost destroyed my car, but nonetheless I am quite confused. I have a 1999 miata and just finished building my DIYPNP. I got the sequential board and I believe I jumpered everything up correctly (including the seq injection jumpers). So I put on the 1999 seq base map, calibrated my sensors, verify the critical values are set (no crazy AFR, Dwell set reasonable) and I start the car. I could not get the car to start on its own, but adding some gas I was able to get it started. I "thought" it was just running rough, so I played around with the AFR maps etc to see if anything would make it run better. While burried in tunerstudio, I start to smell oil. Looking up, I notice there is a good amount of smoke and that there is certainly burning oil. At this point I let it cool and pulled the plugs; Cyl 1 & 3 were almost completely fouled and black, and cyl 2 & 4 looked normal. luckily the car runs well with the stock ECU (I was quite concerned I REALLY ruined something.....) but at this point I am assuming that cyl 1 & 3 are getting fuel, and since 1 &4 are not, the ecu is shooting more fuel into 1 & 3 to get the AFR's correct? I have my tune here (WBO2 isn't connected correct in this data log, I found that issue right away and fixed it, after which I experienced the above story). I can get another datalog for you guys if you need, but I'm still trying to figure out what I did wrong....
Also attached is the tune (re-named, I know you guys don't like it when people don't rename the tune!)
Reply
0
0
12-21-2013, 11:34 AM
#2
Newb
Thread Starter
Join Date: Dec 2013
Posts: 8
Total Cats: 1
So I think I found the issue, but it's not configurable....I re-checked my circuit and I have continuity to the right outputs for running sequential; however, when running in output test mode, inj 3 & 4 are not firing. Researching online, I believe the issue lies in TS. Under the Injector Drivers (See attached) everyone seems to be able to choose "additional drivers" where my only option is "standard drivers." There is no other option in the dropdown. As you can see from the screenshot, I am running 3.3.1 firmware, but is there something else that I am missing here? I am SO CLOSE to having this running, but obviously fuel is more or less important. What do I need to do to run seq?
Reply
0
0
12-21-2013, 12:03 PM
#3
Boost Czar
iTrader: (62)
Join Date: May 2005
Location: Chantilly, VA
Posts: 79,484
Total Cats: 4,076
inj 3 and 4 are connected to pt6 and pt7 respectively? did you build the extra seq. drivers or are you using the module? did you run them out to the harness connector board correctly?
Reply
0
0
12-21-2013, 12:40 PM
#4
Newb
Thread Starter
Join Date: Dec 2013
Posts: 8
Total Cats: 1
Reply
0
0
12-21-2013, 12:55 PM
#6
Newb
Thread Starter
Join Date: Dec 2013
Posts: 8
Total Cats: 1
That's what I thought too. If I had an O scope I would like to see if I am getting pulses at the pins, but right now I do not. I feel like this has to do with the fact that TS isn't using "additional drivers," but what would cause me to lose that option?
Reply
0
0
12-21-2013, 01:09 PM
#7
Boost Czar
iTrader: (62)
Join Date: May 2005
Location: Chantilly, VA
Posts: 79,484
Total Cats: 4,076
yeah i cant figure out why i cant turn on additional drivers on your map. that's the issue.
BTW you can use a multimeter in diode test mode to ground to get the outputs of the fuel drivers, it will beep when they fire.
BTW you can use a multimeter in diode test mode to ground to get the outputs of the fuel drivers, it will beep when they fire.
Reply
0
0
12-22-2013, 09:15 AM
#11
Senior Member
Join Date: Apr 2011
Location: Hollywood, FL
Posts: 807
Total Cats: 163
Make sure under "project properties" in TS you have the right ecu choice. I had this similar problem (running on 2 cylinders) when I upgraded to MS2/extra 3.3 and like a dumb *** couldnt figure it out and went back to the pre 3.3 firmware. I havent tried it again but Im convinced this was my problem. For some reason when upgrading you lose certain project properties that are normally carried over when upgrading firmware, like I found out later when my o2 gauge in TS was stuck at 12.1 when it was working fine before.
And I had a great laugh when I saw your screen name. Magic Bullet is what we referred to back in my auto repair days when people would bring in their cars with their theories of why the car is acting the way it is or when the car had major issues and they thought a "tune-up" would fix it. The ideas were so far off base that we couldnt think of a better term for them. Not to be mean but kinda like your idea in the OP that the ecu was dumping extra fuel into 1&3 to compensate for no fuel in 2&4.
And I had a great laugh when I saw your screen name. Magic Bullet is what we referred to back in my auto repair days when people would bring in their cars with their theories of why the car is acting the way it is or when the car had major issues and they thought a "tune-up" would fix it. The ideas were so far off base that we couldnt think of a better term for them. Not to be mean but kinda like your idea in the OP that the ecu was dumping extra fuel into 1&3 to compensate for no fuel in 2&4.
Reply
0
0
12-22-2013, 09:54 AM
#12
Newb
Thread Starter
Join Date: Dec 2013
Posts: 8
Total Cats: 1
Make sure under "project properties" in TS you have the right ecu choice. I had this similar problem (running on 2 cylinders) when I upgraded to MS2/extra 3.3 and like a dumb *** couldnt figure it out and went back to the pre 3.3 firmware. I havent tried it again but Im convinced this was my problem. For some reason when upgrading you lose certain project properties that are normally carried over when upgrading firmware, like I found out later when my o2 gauge in TS was stuck at 12.1 when it was working fine before.
And I had a great laugh when I saw your screen name. Magic Bullet is what we referred to back in my auto repair days when people would bring in their cars with their theories of why the car is acting the way it is or when the car had major issues and they thought a "tune-up" would fix it. The ideas were so far off base that we couldn't think of a better term for them. Not to be mean but kinda like your idea in the OP that the ecu was dumping extra fuel into 1&3 to compensate for no fuel in 2&4.
And I had a great laugh when I saw your screen name. Magic Bullet is what we referred to back in my auto repair days when people would bring in their cars with their theories of why the car is acting the way it is or when the car had major issues and they thought a "tune-up" would fix it. The ideas were so far off base that we couldn't think of a better term for them. Not to be mean but kinda like your idea in the OP that the ecu was dumping extra fuel into 1&3 to compensate for no fuel in 2&4.
Reply
0
0
12-22-2013, 10:27 AM
#13
Senior Member
Join Date: Apr 2011
Location: Hollywood, FL
Posts: 807
Total Cats: 163
Well your logic is not incorrect if everything was ok. Its just that your plugs are being fouled because the engine is just not being run right by the ecu. So how can the ecu adjust for this if its not operating correctly? And what would be feeding it the data to make it adjust for no fuel in half the engine? And make it adjust so quickly? Usually there are certain parameters that have to be met in order for fuel correction to occur so unless you set it up to do fuel correction while the engine is cold and with wildly fluctuating AFR readings, I dont think fuel correction will occur.
So Im assuming that everything has been wired up correctly, so then ecu firmware must not be properly configured or loaded. Just out of curiosity, what module did you enter to flash the firmware with and what module is entered in TS under project properties? For DIYPNP it is specific microsquirt module and not msII or microsquirt. Just covering the basics here.
Im trying to get some work done at home but I will be flashing the new msII/extra 3.3.1 release firmware to my ecu soon as the last attempt ended up with symptoms like yours. I will try to report back if Im successful this time around.
So Im assuming that everything has been wired up correctly, so then ecu firmware must not be properly configured or loaded. Just out of curiosity, what module did you enter to flash the firmware with and what module is entered in TS under project properties? For DIYPNP it is specific microsquirt module and not msII or microsquirt. Just covering the basics here.
Im trying to get some work done at home but I will be flashing the new msII/extra 3.3.1 release firmware to my ecu soon as the last attempt ended up with symptoms like yours. I will try to report back if Im successful this time around.
Reply
0
0
12-22-2013, 01:23 PM
#14
Senior Member
Join Date: Apr 2011
Location: Hollywood, FL
Posts: 807
Total Cats: 163
Frank I just flashed the 3.3.1 release firmware to my DIYPNP and it cranked up and ran well in my driveway. Once I get some chinese food in me I will take it out for a spin to confirm everything else is fine but I do believe it will be.
As mentioned earlier, I flashed 3.3.0 release a couple of weeks ago and didnt get the engine to run. It was doing much like your symptoms of running really rough and seemingly on two cylinders. SInce this car was running fine before I didnt bother to diagnose any problems other than reflashing firmware repeatedly and finally gave up and went back to the 3.3beta13 I had been running before and all was well. I was short on time then and didnt mess with it again til now.
The thing that tipped me off was a recommendation by JSMCortina over at msextra.com forums where when I flashed the release firmware and opened TS to check the AC idle up feature was working correctly, I didnt have my input available. I asked a question over there and he said to make sure to select the correct s19 file when flashing. Without noticing I selected option 2 (which is microsquirt cased) as I usually do when flashing new firmware. Well guess what, its option 3 (microsquirt module). Thats all it took to throw the whole thing off.
Now it all seems to be fine. I have my input available for ac idle up and obviously the engine runs right. I cant say we experienced the same problem but it sure sounds like we have.
Oh and make sure to go through and check all engine settings as it will change the current tune significantly.
As mentioned earlier, I flashed 3.3.0 release a couple of weeks ago and didnt get the engine to run. It was doing much like your symptoms of running really rough and seemingly on two cylinders. SInce this car was running fine before I didnt bother to diagnose any problems other than reflashing firmware repeatedly and finally gave up and went back to the 3.3beta13 I had been running before and all was well. I was short on time then and didnt mess with it again til now.
The thing that tipped me off was a recommendation by JSMCortina over at msextra.com forums where when I flashed the release firmware and opened TS to check the AC idle up feature was working correctly, I didnt have my input available. I asked a question over there and he said to make sure to select the correct s19 file when flashing. Without noticing I selected option 2 (which is microsquirt cased) as I usually do when flashing new firmware. Well guess what, its option 3 (microsquirt module). Thats all it took to throw the whole thing off.
Now it all seems to be fine. I have my input available for ac idle up and obviously the engine runs right. I cant say we experienced the same problem but it sure sounds like we have.
Oh and make sure to go through and check all engine settings as it will change the current tune significantly.
Reply
0
0
12-22-2013, 05:51 PM
#16
Newb
Thread Starter
Join Date: Dec 2013
Posts: 8
Total Cats: 1
Frank I just flashed the 3.3.1 release firmware to my DIYPNP and it cranked up and ran well in my driveway. Once I get some chinese food in me I will take it out for a spin to confirm everything else is fine but I do believe it will be.
As mentioned earlier, I flashed 3.3.0 release a couple of weeks ago and didnt get the engine to run. It was doing much like your symptoms of running really rough and seemingly on two cylinders. SInce this car was running fine before I didnt bother to diagnose any problems other than reflashing firmware repeatedly and finally gave up and went back to the 3.3beta13 I had been running before and all was well. I was short on time then and didnt mess with it again til now.
The thing that tipped me off was a recommendation by JSMCortina over at msextra.com forums where when I flashed the release firmware and opened TS to check the AC idle up feature was working correctly, I didnt have my input available. I asked a question over there and he said to make sure to select the correct s19 file when flashing. Without noticing I selected option 2 (which is microsquirt cased) as I usually do when flashing new firmware. Well guess what, its option 3 (microsquirt module). That's all it took to throw the whole thing off.
Now it all seems to be fine. I have my input available for ac idle up and obviously the engine runs right. I cant say we experienced the same problem but it sure sounds like we have.
Oh and make sure to go through and check all engine settings as it will change the current tune significantly.
As mentioned earlier, I flashed 3.3.0 release a couple of weeks ago and didnt get the engine to run. It was doing much like your symptoms of running really rough and seemingly on two cylinders. SInce this car was running fine before I didnt bother to diagnose any problems other than reflashing firmware repeatedly and finally gave up and went back to the 3.3beta13 I had been running before and all was well. I was short on time then and didnt mess with it again til now.
The thing that tipped me off was a recommendation by JSMCortina over at msextra.com forums where when I flashed the release firmware and opened TS to check the AC idle up feature was working correctly, I didnt have my input available. I asked a question over there and he said to make sure to select the correct s19 file when flashing. Without noticing I selected option 2 (which is microsquirt cased) as I usually do when flashing new firmware. Well guess what, its option 3 (microsquirt module). That's all it took to throw the whole thing off.
Now it all seems to be fine. I have my input available for ac idle up and obviously the engine runs right. I cant say we experienced the same problem but it sure sounds like we have.
Oh and make sure to go through and check all engine settings as it will change the current tune significantly.
Reply
1
1
Thread
Thread Starter
Forum
Replies
Last Post
Jike Spingleton
Cars for sale/trade
3
09-20-2016 04:33 PM
