Topic: crome experts, super rich on decel (Read 8420 times)

stealthiskey · « **on:** February 02, 2012, 11:00:40 PM »

got the civic back together, holset h1c, 3 bar, and vitara pistons.

A slightly modified version of the old tune is running ok, but if I let off the gas and start engine braking, the air-fuel goes from max lean (normal) to super rich, like 8:1.

Tried a different O2 sensor, same result, plus you can hear it backfiring on occasion. If I stay on the gas so it's just above 20 inHg it's fine (15:1), but as soon as I let the engine draw more vaccuum it goes nuts. Actually flooded the engine and stalled out a few times. I tried to zero out the fuel vals in the highest vaccuum columns, but its still doing it. (can tell it is in fact dropping out fuel to an extent, but beyond certain vac levels the zeroes have no effect)

Anyone had anything like this before? It sometimes did something similar on the old tune/setup, but not near as bad. Someone once suggested a glitch with the fuel tools plugin?

DasPoop · « **Reply #1 on:** February 02, 2012, 11:26:51 PM »

Calibrate your tps.

stealthiskey · « **Reply #2 on:** February 02, 2012, 11:36:48 PM »

I recently checked on the tps via freelog, it appeared to be working proper. Plus the super rich issue goes away at 0% throttle if the clutch is in or neutral. Only under high vaccuum no throttle.

Also, as I understand the TPS only tells the ECU when to engage/di.... disengage closed loop.

Had to double check up there, but I do in fact have closed loop disabled.

DasPoop · « **Reply #3 on:** February 03, 2012, 12:57:45 AM »

it also tells it when to turn off your injectors under decel.

PhilStubbs · « **Reply #4 on:** February 03, 2012, 08:04:16 AM »

Try leaning the next vac column over. You probably aren't getting into that first one much.

92CXyD · « **Reply #5 on:** February 03, 2012, 09:40:41 AM »

Quote from: SecksyPeePee on February 03, 2012, 08:04:16 AM

Try leaning the next vac column over. You probably aren't getting into that first one much.

+1

What wideband you using and is it ground properly to the engine block?

referring to http://www.realhomemadeturbo.com/forum/index.php/topic,1195.0.html

DSharp · « **Reply #6 on:** February 03, 2012, 10:23:32 AM »

you should be getting a fuel cut on decel, first find out why your not.

stealthiskey · « **Reply #7 on:** February 03, 2012, 11:25:56 AM »

New info, I'll post more later. This is not the cause of my problem, but it exacerbates it.

I uploaded the same bin, but without the datalogging plugin. It dropped afrs by about 3 pts in boost 14.x. to 11.x. it also improved the high vac afr from 8.x to 10.x

I remember having a similar issue years ago, but this is a different laptop with a fresh crome 1.5.0 install which came with dlrtp plugin 2.0.

Looking back I think my fix previously was to use the older dlrtp 1.5 instead.

I suspect there is a glitch in 2.0, and I may be able to succcessfully retune the vac columns with 1.5

DSharp · « **Reply #8 on:** February 03, 2012, 12:05:04 PM »

Waaay back when I used freelog, i had to manually change the data logging ?protocol? in freelog because cui changed up the way crome communicated through the datalogger port. I don't know if free log was updated for the 2.0 data logger. I think freelog was setup for datalogger 1.8 back then. That was about 5 years ago so things are probably different now.

92CXyD · « **Reply #9 on:** February 03, 2012, 12:12:46 PM »

Quote from: DSharp on February 03, 2012, 12:05:04 PM

Waaay back when I used freelog, i had to manually change the data logging ?protocol? in freelog because cui changed up the way crome communicated through the datalogger port. I don't know if free log was updated for the 2.0 data logger. I think freelog was setup for datalogger 1.8 back then. That was about 5 years ago so things are probably different now.

yeap I tried freelog recently and could not get it work like it should.

Did some research on pgmfi and that was pretty much problem, datalog protocol.

stealthiskey · « **Reply #10 on:** February 03, 2012, 12:18:22 PM »

Heh not much has changed in 5 yrs. I think I encountered that as well. I wonder if anyone has realised that adding dlrtp 2.0 to a tune will cause the car to run 3 points leaner in boost! Or its possible tuners add it in right away and tune out the discrepancy without ever noticing.

Still it seems screwy though, I suspect it also throws my high vac afrs in the opposite direction. My philosophy with crome has always been to use as few plugins as possible, due to possibility of software glitches.

DSharp · « **Reply #11 on:** February 03, 2012, 02:21:29 PM »

no that was never a problem. Data logging protocol will only affect data logging. If your actual AFR changes then something else is the cause. You should have verified what the wide band is actually reading by now other than just what you see through crome data logging. all it take is a volt meter and 5 min.

stealthiskey · « **Reply #12 on:** February 03, 2012, 03:48:39 PM »

Clarification: NONE of this is being observed through datalogging. I enabled the plugin in the bin, but still haven't gotten around to setting up freelog.

These are ACTUAL afr changes, evidenced by moates o meter real time, the innovate LC-1 logworks software (serial communication to rule out grounding offsets), audible backfires, and gas smell in the exhaust. Spark plugs and engine bay temps also confirm.

stealthiskey · « **Reply #13 on:** February 03, 2012, 04:03:22 PM »

Quote from: stealthiskey on February 03, 2012, 12:18:22 PM

I wonder if anyone has realised that adding dlrtp 2.0 to a tune will cause the car to run 3 points leaner in boost!

Quote from: DSharp on February 03, 2012, 02:21:29 PM

no that was never a problem.

I'd like to look into this further. I had this problem years ago when I first started, and never really understood the cause, but the symptom was clear as day.

My first attempt with crome was a bone stock d16z6, stock injectors. Copied p28 tables into p30 bin and everything worked fine. Once I started trying the datalogging plugin the afrs went to shit. Looking back I must have downloaded the dlrtp 1.5 and always used that instead. I remember having two dlrtp options in the plugin manager.

Would be interested if someone could confirm my results independently.

Tim · « **Reply #14 on:** February 03, 2012, 05:07:55 PM »

I seem to remember a thread on pgmfi about one of the newer dlrtp causing a bug like this.

I don't remember the details, I was just browsing trying to get caught up with crome cause a buddy wanted me to tune his car with it.

92CXyD · « **Reply #15 on:** February 03, 2012, 05:27:30 PM »

Quote from: Tim on February 03, 2012, 05:07:55 PM

I seem to remember a thread on pgmfi about one of the newer dlrtp causing a bug like this.

I don't remember the details, I was just browsing trying to get caught up with crome cause a buddy wanted me to tune his car with it.

I use both Crome 1.5.3 and 1.6.2 and had no issue with this.

The only issue I have now is 1.6.2 has expired and need another update.

But 1.5.3 seems to be very stable.

If you want Pro version there is a guy on D-series selling licenses for $50.

He says it totally legit license.

When I had 1.6.2 working I could Crome Gold.

After seeing what problems people are having with EcTune, I think I'll stick with Crome for a while longer.

PhilStubbs · « **Reply #16 on:** February 03, 2012, 05:53:32 PM »

After using Neptune, I can't imagine wanting to use anything else. I still have to tune the local scum on crome though. Not trying to bash people using Crome with that statement, but there are some guys around here completely neglect their cars but boost them.

HiProfile · « **Reply #17 on:** February 03, 2012, 06:00:14 PM »

Quote from: SecksyPeePee on February 03, 2012, 08:04:16 AM

Try leaning the next vac column over. You probably aren't getting into that first one much.

I tuned an ancient Haltec once and that was the case. With your setup it's likely the MAP sensor, since newer freescale sensors can't read more than 22-24" Hg. I can't recall the exact number, but I know the new sensors are different from Crome's presets. If you didn't input your specs manually your EMS & sensor won't be in sync.

PhilStubbs · « **Reply #18 on:** February 03, 2012, 07:55:20 PM »

that explains my 26inhg at idle with freescale sensor using stock settings. after some searching sewell found settings that made it all right while on his dyno.

stealthiskey · « **Reply #19 on:** February 04, 2012, 09:21:18 AM »

Quote from: HiProfile on February 03, 2012, 06:00:14 PM

Quote from: SecksyPeePee on February 03, 2012, 08:04:16 AM
Try leaning the next vac column over. You probably aren't getting into that first one much.

I tuned an ancient Haltec once and that was the case. With your setup it's likely the MAP sensor, since newer freescale sensors can't read more than 22-24" Hg. I can't recall the exact number, but I know the new sensors are different from Crome's presets. If you didn't input your specs manually your EMS & sensor won't be in sync.

I suspected something like this. Was looking for my post on how I calibrated the new sensor, but it seems to have been lost in the latest server fuckup. I'll try adjusting the adjacent vac columns

DSharp · « **Reply #20 on:** February 05, 2012, 12:52:11 AM »

Interesting.

I used to have an issue of my car leaning considerably with increasing electrical loads. Problem disappeared when I replaced the ECU. After that I never had the problem again with the car or the the ECU that gave the problem initially. Now I have different but also equally strange and unheard of issues with ectune. I assume that there is something fucked up with my car.

Just the nature of the beast I guess.

News:

Author Topic: crome experts, super rich on decel (Read 8420 times)