Hondata

Ok, so I've had a Hondata S300 for a while now but have only recently bought myself a PLX wideband to do some tuning.
Engine mods are:
S300
ITR IM + TB
Cheapy 4>2>1 extracters
No PS, AC
PLX Wideband
Hondata IM gasket
Stock injectors
Chassis is a 1992 DA6 (JDM) Facelift so has OBDI.

I've had some problems with making changes to the high speed fuel table, in the sense that I'll record a datalog (2nd gear, WOT from ~2,000rpm > ~8,400rpm) I'll load the datalog, make the suggested changes to the fuel values, re-run a 2nd gear sweep and will have datalogged essentially an identical A/F.

Because I started with a ratty old calibration (untouched fuel tables) that I've been using to muck around with things like Launch Control, etc I thought I might've buggered something up, so I started with a fresh P30 calibration. (I have a JDM PR3 OBDI ECU in my JDM facelift DA6 and the P30 was the closest I could find to suit the B16A2 I have)

Here's how I did things tonight:

I modified the P30 tune to have all my settings for LC, FTS, Datalogging & Wideband. Uploaded this tune to the ECU & went for a quick drive. Oh, I also unchecked Closed Loop.

See "1st_run.s3d" and "DA_Settings_No_Tune.skl" for the unchanged fuel map & the datalog to correspond with it.

I loaded up the datalog & the calibration, checked the high speed fuel tables & made the suggested adjustments, saved the altered calibration as a different filename & uploaded it to the ECU. I only adjusted Col's 7-10, 5750rpm - 8950rpm.

Check "2nd_Run.s3d" for the datalog of the resulting 2nd gear sweep.

I once again checked the datalog loaded the unmodified calibration (is that right?) and made the suggested changes again to the high speed fuel table, and saved these changes to the modified calibration.

Went for run #3

Am I doing something wrong? I had some help initially from a friend who'd tuned his car in this exact way, and he said he made three sweeps in total, one for a base, second after a major change to the tables & third to check the minor changes made to the tables.
So far I'm on my third sweep and I've still got an A/F of 12.xx between 5,800rpm & 8,400rpm. What gives?

Apologies for the massive story :P

Oh, also, running SManager 1.4.4.1, have no trouble downloading datalogs, or (seemingly) no trouble uploading calibrations.

You shouldn't have to keep loading an unmodified calibration to the ECU. Perhaps I'm not fully understanding what you are doing...

Have you reade any of the Tuning guides at http://www.hondata.com/stech.html ?

Spunkster wrote:You shouldn't have to keep loading an unmodified calibration to the ECU. Perhaps I'm not fully understanding what you are doing...

You're right I shouldn't but I'm having limited success tuning the current values, or I'm having success tuning the current values but the datalog is telling lies.

Spunkster wrote:Have you reade any of the Tuning guides at http://www.hondata.com/stech.html ?

I haven't but I'll put them at the top of my list of things to do :)
I have read the guide written by Jeff Schaefer though.

I guess my problem isn't with interpreting the fuel changes suggested/required to bring the A/F nearer my targets, but more towards the fact that I'm continually getting the same A/F before and after I've made said changes.

So I went out for another shot at tuning tonight.
But this time instead of relying on the onboard datalogging I decided to have a go at realtime datalogging.

Seemed to have more luck this time, as we were adjusting fuel based off the estimated fuel change table that was calculating as we went. (using the same method as above, 2nd gear WOT @ 2krpm through to redline)

So I think I might have an onboard datalogging problem, several times we tried to clear the memory on the on-board datalogging only to find there was ~120kb of data still stored, but no recorded/listed datalog entries.
It seemed a bit random as to whether or not we'd fully clear the datalog memory.

Is there anything I can do to fully clear the datalog memory other than click "Delete All" in the "download from ECU" dialogue box? (because this failed to clear the datalog memory several times) can I re-flash the firmware/hardware code on the ECU itself in case there's something odd going on there?
It seems that once I get exceed that magic ~120kb marker datalogs start to behave themselves a bit.

Also I noticed that after a WOT run when I let off my A/F would shoot up to 20:1 now I understand this is normal to see some leaning out in A/F but all the way to max lean value seems a bit excessive to me?

Have a look at your datalog where u jump off the gas......
Now have a look at the injector data.....

Notice they have switched completely off,like about 0.6sec(or whatever u have it set too) after u jumped off the throttle?

Its called 'Fuel Overrun CutOff',its an emissions/economy/etc feature,its completely normal,u will find the settings on the TPS tab.

Edit:sorry dont know about your datalog woes.
Also didnt look at your datalogs, incase there isnt an instance of u jumping off the throttle & your wondering what the hell is this guy on about....

fly_n wrote:Have a look at your datalog where u jump off the gas......
Now have a look at the injector data.....

Notice they have switched completely off,like about 0.6sec(or whatever u have it set too) after u jumped off the throttle?

Its called 'Fuel Overrun CutOff',its an emissions/economy/etc feature,its completely normal,u will find the settings on the TPS tab.

Edit:sorry dont know about your datalog woes.
Also didnt look at your datalogs, incase there isnt an instance of u jumping off the throttle & your wondering what the hell is this guy on about....

Right you are :)I do have a datalog where I'm off the gas for a good 3-4 sec and the duty cycles is 0% and the A/F is 19.6blah, I wasn't too worried about that as I know the engines not under load at those points. And perhaps it's not helped by running in open loop. *shrug* oh well.

Semi-meaningful bump ;)