Printable View
So I finally got around to installing my PNP flash ECU with Chrome V2, and I have 2 problems.
When no lift to shift is enabled there is an RPM limit of 6500. I don't see a setting set to 6500 rpm. The rpm limit that I do see is set to the stock rpm of 7200.
Also, when the CEL on knock feature is enabled, I get random fault codes being thrown.
Launch control and fuel pump on clutch both work great.
Any thoughts?
under the launch control listing the should be one that says NLTS RPM
Yeah that's set to 5000. So when NLTS is supposed to be activating, it rev limits 5000rpm. The 6500rpm limit its giving me is at all times.Quote:
Originally Posted by Kx1984
hmmmmm(scratches goatee)
No clue about your rev limit issue... Did you raise fuel cut? You gotta do that on a not stock car.
Your not getting erroneous CELs. Evoscan is broken. It can't read DTCs properly for some reason. Hammish can't be bothered to fix it. Turn off knock on CEL and you'll get the same random codes.
I'm on stock injectors running 12-13psi on 19T's, and with NLTS off, I get to 7200 rpm no problem. I'll look into what the fuel cut is set at though.Quote:
Originally Posted by Greg E
As far as the CEL, I'm getting a constant CEL on the dash with 'CEL on knock' enabled. I didn't verify with a scan tool that Evoscan was correct in telling me what the codes were, but with 'CEL on knock' disabled, I get no CEL on the dash.
Is it just me?
Email me the .bin flashed to your car and the .xml file you're using.
nonstopmix@gmail.com
Will do when I get home tonight.Quote:
Originally Posted by Greg E
Also I did get a CEL this morning in the dash with NLTS and knock CEL disabled. Launch control didn't work. Restarted the car and it was gone, and launch control worked again. Very random it seems.
Every time someone tells me their launch control didn't work, its always been because they didn't push the pedal far enough. :)
Lol i thought that might have been it so i tried again making sure to floor it, same problem. It paused at 4k for a splIt second and then shot up to redline. Car off then on fixed it.Quote:
Originally Posted by Greg E
I think I see the problem. The .bin file you sent me is the same file you have flashed to the car correct?
Your CEL is on because your car is a 97 and you didn't disable any of the periphery 2 CEL codes for the missing systems in your car.
Your fuel cut table is still set for stock so you're getting fuel cut at 6200rpms. If not this, then you're either running too rich and fouling out the spark plugs or you're running too lean and running out of fuel from running 14psi with 19Ts and stock injectors.
Log your TPS and verify it's getting above 80% and still shooting past the 4000rpm stationary rev limit. Remember the vehicle speed must be less than 6 mph too in order for that rev limit to be used. Above 6mph it'll use the clutch in rev limit.
As far as the CEL, you are correct. I misunderstood the tuning guide where it says to disable bits 13-15 on 96-97's as meaning only in Periphery0, instead of all the Peripheries. So the CEL in the dash problem is solved.Quote:
Originally Posted by Greg E
I just went out and retested NLTS, and it appears to be working fine. At first I thought it wasn't, but it seems I'm used to resting my foot on the clutch pedal when I know a shift is coming up (I used the cruise cut wire). Took some getting used to but it seems to be working. According to my logs I got up to 6700rpm with no cutout. I think I was just scared to let it run out to 7k while trying to get used to the NLTS. I'll run it out to redline another time to be sure, but I'm pretty sure all is well! Everything works!
So thank you!!
I do have one other question about the fuel cut thing you mentioned. On Evoscan, am I looking at "2byte ECUload" to compare to the "LOAD" column under "Fuel Cut (double mod)"? If so, I'm safe for now with the stock fuel cut, but a couple more psi than the 12-13 I'm running and I'll have to change the values.
Awesome. :)
Make sure you disable the bits in periphery 2 not periphery 0.
thats normal. i set my timer for a really high value (30,000 ms to be exact... which is 30 seconds) so that i could rev the car out. i will set the tables where they need to be later after the car is tuned.Quote:
Originally Posted by TwIzTeD_3kGt
Yeah that's probably what I'll end up doing until I know what my final load numbers are going to be. Just wasn't sure if the 2byte ecu load numbers in evoscan directly correlated to the load numbers in ecuflash?Quote:
Originally Posted by futurevr4man
Yes. The same value being logged is the same value used for fuel cut and all the table axises.Quote:
Originally Posted by TwIzTeD_3kGt
I've had the NLTS go off several times during pulls, the only way to run out a gear everytime for me is to pull up on the clutch with my foot. Seems that cruise switch is really sensitive, but my cruise has never shut off on me either so I dunno whats happening during a pull.
I've found that I sub-consciously put my foot on the clutch every time I know a shift is coming. So first gear is tough to keep the foot off, especially while sideways, and I've stopped quite a few pulls short already. It's taking some getting used to, but it's never gone off on it's own so far.Quote:
Originally Posted by sublime_whatigo
Chrome gives you the ability to operate with the starter switch too if the cruise switch isn't working for you. One value needs to be changed.
My concern with using the starter kill switch is that it won't rev limit until after the clutch is in, which I would think could result in over-revving up to the stock limiter. Something a little less sensitive than the cruise kill would be nice. Does the switch adjust? I just want it maybe another inch or two further into pedal travel.