Track car intermittently runs like crap
#124
Attached is a pic of my injector settings. I did not set up the tune when I installed the Rotrex. Any suggestions would be greatly appreciated.
Thanks,
#125
Retired Mech Design Engr
iTrader: (3)
Join Date: Jan 2013
Location: Seneca, SC
Posts: 5,012
Total Cats: 859
Interesting question. I was messing with the idle since I had read those settings don't carry over when upgrading from 1.2.X when the problem recurred. Should I do the update and then the injectors? That was not my plan.
Attached is a pic of my injector settings. I did not set up the tune when I installed the Rotrex. Any suggestions would be greatly appreciated.
Thanks,
Attached is a pic of my injector settings. I did not set up the tune when I installed the Rotrex. Any suggestions would be greatly appreciated.
Thanks,
#128
mkturbo.com
iTrader: (24)
Join Date: May 2006
Location: Charleston SC
Posts: 15,194
Total Cats: 1,687
I would highly suggest upgrading to 1.4.1 before you keep diagnosing things. There are a ton of changes, and a lot of your current settings will need to be updated. Fuel/Spark tables should stay the same, but a ton of the small things will need to be messed with.
Yes you can upgrade to the newer firmware without turning on the car. You will need to unhook the injectors and coil pack, but the car just needs power. This is the link to the thread about upgrading firmware.
Yes you can upgrade to the newer firmware without turning on the car. You will need to unhook the injectors and coil pack, but the car just needs power. This is the link to the thread about upgrading firmware.
Last edited by shuiend; 01-09-2017 at 03:47 PM.
#130
Retired Mech Design Engr
iTrader: (3)
Join Date: Jan 2013
Location: Seneca, SC
Posts: 5,012
Total Cats: 859
I would highly suggest upgrading to 1.4.1 before you keep diagnosing things. There are a ton of changes, and a lot of your current settings will need to be updated. Fuel/Spark tables should stay the same, but a ton of the small things will need to be messed with.
Yes you can upgrade to the newer firmware without turning on the car. You will need to unhook the injectors and coil pack, but the car just needs power. This is the link to the thread about upgrading firmware.
Yes you can upgrade to the newer firmware without turning on the car. You will need to unhook the injectors and coil pack, but the car just needs power. This is the link to the thread about upgrading firmware.
#131
mkturbo.com
iTrader: (24)
Join Date: May 2006
Location: Charleston SC
Posts: 15,194
Total Cats: 1,687
Reverant has unequivocally stated that the MS3-Basic does not need the coils disconnected during a FW upgrade. See #8
#133
Retired Mech Design Engr
iTrader: (3)
Join Date: Jan 2013
Location: Seneca, SC
Posts: 5,012
Total Cats: 859
As to your IAC disconnect question in the other thread, I have no idea what you are talking about.
#134
DAMMIT DAMMIT DAMMIT
Gents,
I have the new Force Flow injectors installed that Nigel sent me, and updated to the 1.4.1 firmware. She idled fine in the driveway yesterday, so I took her for a ride around town today after work. Did some easy 2nd and 3rd gear pulls, and generally drove around for about half an hour. I decided I'd take her to work tomorrow and do some highway driving. I headed home and had an opportunity to get into WOT. She got above about 6000 rpm, stumbled badly and backfired. The check engine light came on. I slowed down and pushed in the clutch. The idle rpms were up around two grand. They slowly dropped to normal. Otherwise the car was idling/running fine afterwards.
I was not expecting problems, so I was not data logging. I went around again and set up logging. The same thing happened. The logs are attached.
There were no issues pulling through the gears WITHOUT going into WOT.
I don't think this is related to my previous issue. Any help would be greatly appreciated.
I have the new Force Flow injectors installed that Nigel sent me, and updated to the 1.4.1 firmware. She idled fine in the driveway yesterday, so I took her for a ride around town today after work. Did some easy 2nd and 3rd gear pulls, and generally drove around for about half an hour. I decided I'd take her to work tomorrow and do some highway driving. I headed home and had an opportunity to get into WOT. She got above about 6000 rpm, stumbled badly and backfired. The check engine light came on. I slowed down and pushed in the clutch. The idle rpms were up around two grand. They slowly dropped to normal. Otherwise the car was idling/running fine afterwards.
I was not expecting problems, so I was not data logging. I went around again and set up logging. The same thing happened. The logs are attached.
There were no issues pulling through the gears WITHOUT going into WOT.
I don't think this is related to my previous issue. Any help would be greatly appreciated.
#135
Boost Czar
iTrader: (62)
Join Date: May 2005
Location: Chantilly, VA
Posts: 79,734
Total Cats: 4,126
look at the idle PWM log. CL didn't activate and therefore the idle valve never closed (you have it always staying open in your tune), and thus the idle never went down until it was finally triggered at the 168sec mark.
in your tune max decel load% is 25. you never quite passed 25kPa when you came back to idle therefore it never passed the parameters needed to go back into CL idle.
i would tune the initial duties table, and tune that value so it makes sense to where your motor typical idles -- you want it just a few kPa below the normal idle load, which looks like maybe 32kPa on your car, so try 28.
your tune is also using a range of 18-80% pwm for the idle valve, was that tuned? seems like a larger swing than i see on most installs.
in your tune max decel load% is 25. you never quite passed 25kPa when you came back to idle therefore it never passed the parameters needed to go back into CL idle.
i would tune the initial duties table, and tune that value so it makes sense to where your motor typical idles -- you want it just a few kPa below the normal idle load, which looks like maybe 32kPa on your car, so try 28.
your tune is also using a range of 18-80% pwm for the idle valve, was that tuned? seems like a larger swing than i see on most installs.
#136
I brought that quote from the idle adjustment thread. Just to clarify, you saw that in the log from post #134 in this thread? That is a new problem. Last time I had something like that it was fixed by replacing the crank position sensor with a new OEM unit AND turning off Noise Filtering. The "new" OEM sensor is in there, although it has a few thousand miles on it, and Noise Filtering is Off. Jeez.
It doesn't seem the same as before, however. This is much more violent. And that was with a different bottom end, so different toothed wheel, crank pulley, etc...
Could flashing in the firmware updates have done something to the crank position sensor?
Thanks,
It doesn't seem the same as before, however. This is much more violent. And that was with a different bottom end, so different toothed wheel, crank pulley, etc...
Could flashing in the firmware updates have done something to the crank position sensor?
Thanks,
Last edited by poormxdad; 01-21-2017 at 07:52 AM.
#137
Retired Mech Design Engr
iTrader: (3)
Join Date: Jan 2013
Location: Seneca, SC
Posts: 5,012
Total Cats: 859
I brought that quote from the idle adjustment thread. Just to clarify, you saw that in the log from post #134 in this thread? That is a new problem. Last time I had something like that it was fixed by replacing the crank position sensor with a new OEM unit AND turning off Noise Filtering. The "new" OEM sensor is in there, although it has a few thousand miles on it, and Noise Filtering is Off. Jeez.
It doesn't seem the same as before, however. This is much more violent. And that was with a different bottom end, so different toothed wheel, crank pulley, etc...
Could flashing in the firmware updates have done something to the crank position sensor?
Thanks,
It doesn't seem the same as before, however. This is much more violent. And that was with a different bottom end, so different toothed wheel, crank pulley, etc...
Could flashing in the firmware updates have done something to the crank position sensor?
Thanks,
Shows up in the high speed log you took also, assuming taken at the same time.
I'm no expert on the filtering, but I have to have mine on, and I have my Global Delay set to 2. Also, my table is 200RPM / 400uS: 500 / 200: 2500 / 40: 7500 / 13. This has worked well with both the stock trigger, and the 36-2. Only "Noise Filter Enabled" is on. Rest are all off.
Not saying this will fix your sync loss, just saying what cured mine.