Problem Starting Car..Possible problem with Ectune?
Moderator: Gaskleppie
-
- Posts: 13
- http://phpbb3styles.net
- Joined: Wed Sep 03, 2008 9:57 pm
- Location: Washington
Problem Starting Car..Possible problem with Ectune?
Ok been driving this car for a while now on ectune, gsr ctr cams t3/t4. I parked it one night ,next morning it wont start! I mean it CAn start if u hold ur foot on the gas, but its REALLY rough and nothing but smoke, oh! and do i mean smoke (100% fuel burning) comes out of the exhaust. No codes, nothing changed. It kinda seems like its just dumping fuel non stop? But i chanced the injectors to a brand new set of precisions, and still he same. Car ran PERFECT before this, i dont know if its a problem with the ecu/chip maybe the chip was fried somehow? I tried using another ecu with the same chip and still the same thing. When cranking it sounds like it wants to start sometimes, and when you hold the gas down it will stay on very rough like and once u let go it dies. It has spark, i checked for that. So any ideas?
- Gaskleppie
- <font color=gray>Site Admin</font><br><font color=green>eCtune Authorized Tuner</font>
- Posts: 1263
- Joined: Tue Apr 03, 2007 11:22 am
- Location: Netherlands
- Contact:
Dealt with something simiar to this and it was the map sensor that was messed up. Check to see if there is anything fishy with the Map Voltage. Also, did you swap in different sized injectors or different brand? You might have to retune with new injectors because I have learned that no 2 sets are the same.
I have no clue how to do that, i did not tune my own car im sorry. Im just a concerned consumer/owner. I just found a way to get it started (stil running like complete crap tho) since normal cranking and stepping on the gas wont work anymore. I just disconnect the resister box really really quickly and it revs up (of course putting it back in a split second after) at that point i can keep it alive by reving it normally. This is just completely odd, it literally sat for the night and next morning began doing this. It just spews obsurd amounts of fuel smoke now. thats all..
- JaredKaragen
- Posts: 1504
- Joined: Fri Nov 23, 2007 4:00 am
- Location: Bay Area, Ca
- Contact:
I did a reflash of someone's EEPROM for a CROME basemap once; all the sidden, his car was in limp mode.... just came out and tried to drive it and it was a solid CEL; reflashed EEPROM, and worked like a charm. it could be either the EEPROM itself; a connection to the ECU, or the solder job on the ECU itself; pretty common for any of those 3 before all else IMHO.
95 Sol Si : D16z6 : TD04H-13C 74 Civic 1200 : 100% Stock
I experienced something that sounds like tehe samething... but it was with a PW0 ECU. A newer type of the Nokia DKU5 cable was used for logging. For some reason this cable showed activity at Rx,Tx and/or GND (although not connected to a laptop!) which caused the ECU to do do some sort of reset every now and then. The 'reset rate' could be as high as four to five times per minute. Sometimes nothing was wrong for 10 minutes and at the other moment it could be all wrong for the next 15 minutes. The 'reset' was noticible as it caused hickups in the engines behaviour and a popping sound from the exhaust. But still 'drivable' thou. It feels like a faulty ignition module. Except for one time, engine almost didn't start after a 20 minutes lunch break at McD's. Once it started, engine was running on three and a half cylinder. Clear white smoke and some liquid sputtering from the exhaust. First thought at that moment... headgasket. But it didn't smell like that and also temperature and pressure of the coolant remained perfect. No bubbels or other signes of faulty coolant stuff. When I connected the laptop to the logger cable to see what was going on, everything was fine again. I disconnected the laptop and remained clueless of what was going in. As a reaction of frustration, I pulled the log cable from the ECU. And all of a sudden everything was back to normal as it always used to be. I drove another week without ANY problem. And then.... I made the move to eCtune
Bottom line... it sounds like a hardware related problem. Is the chip still firmly in the socket? Is it possible the logger hardware is causing strange behaviour? The easiest thing to do is disconnect the logger hardware, pull out and push back in the chip. And try again... with the logger hardware still disconnected. But as Calvin already mentioned... go back to you tuner and try to find the problem together with him.
