TD_D mod journey. From stock to the 'bastardmobile'

[Td_d]

Hehehe... thanks Holy, much obliged - I'm also curious to see what it does. It makes sense on the resolution - I saw something similar being done on the RomRaider forums, where people were changing the A / B learnt ranges to capture 'hard to capture' areas in the MAF scale.

I didn't have a chance to actually look at the data, got on the road straight afterwards, christ, what a nighmare drive, roadwork 40% of the way, took over 9 hours, I'm knackered...

 

[HolyCrapItsFast]

I love driving but if that time is spent sitting in traffic I would rather watch my aunt tweez her clit for six hours. :lol:

I know what you mean

 

[IGOTASTi]

I gotta see Holy's aunt now!

 

[HolyCrapItsFast]

Oh yeah... She's a looker :lol:

 

[Paul.c]

:rofl:

 

[Td_d]

Jeesh, I'm not on for 2 days and you guys are already whoring it up in here :lol:

 

[HolyCrapItsFast]

It's what we do! LOL

 

[Td_d]

Ok! I'm back for 2 days (then out for another 4, back on Wed) - here's the next log - actually felt very smooth, no real discernable stumble (felt a small 'murmer' if I can call it that here and there at around 3000, much hardly discernable).

http://dl.dropbox.com/u/3099895/TD D 17 Mar 2011 Log A.rar

 

[Td_d]

Oh - another I've noticed is that starting / cranking, excuse the pun, is a little cranky - and I've seen on the logs that it's pulling fuel massively on cold start (-28 to -30 combined learnt and corrected). I'm running another log now, and it looks slightly different to the first one (but also pulling fuel on idle - different at the top end). I'll post it, just in case.

http://dl.dropbox.com/u/3099895/TD D 17 Mar 2011 Log B.rar

Damn, just realised I hadn't updated the MAF table in the spreadsheet, DOH!

 

[HolyCrapItsFast]

And these logs were taken on rom 750RC_3-03-2011_Rev-A.hex?

 

[Td_d]

Yes indeed!

 

[HolyCrapItsFast]

Okay... This is going to take quite a while to compile.

 

[HolyCrapItsFast]

Something is still not quite right. The Learned Trims should have been 0 long ago and it seems like I'm running in circles with this.

I need you to take another log but this time do not reset the ECU. I'm looking for a good count of learned data this time.

Is there anyway of getting a log with less resolution? There is just to much data in such a small span of time and it is fucking around with the averages. I guess what I'm asking is what are you using to take logs. The OpenPort 2?

Did you perform the following... Intake and Manifold boost leak test. Check for leaks in the exhaust and headers. Clean the Maf Sensor.

The other thing that can cause what we are seeing is a bad Front O2 sensor and it may not even throw a code. Also is the Rear O2 sensor still installed?

Anyway, before I give you another rom please log some more with out resetting the ECU. and just re-verify that our latest rom (3-03-2011-A) is installed. Warm up the car fully before taking the log and just a short 10 to 15 minutes will do.

Thank you!

 

[HolyCrapItsFast]

Maybe add a whole shit load of parameters just to slow it down some.

 

[Td_d]

I'm using the OpenPort 2.0 - but I'm also using the CAN onboard logging which is massively faster than the SSM logging (I think about 10x more) - hence the volume. What I can do is reconfigure the card to use SSM logging, which will be lower resolution. I'll check the MAF sensor, clean it - as far as I know the O2 sensors were left alone, so should still be there.

I'll have to do this when I'm back on Wednesday, it will land up being too tight today... thanks again for the help!

 

[HolyCrapItsFast]

Yeah SSM logging sounds better in this situation.

No problem, any time! Always glad to help!

Looking forward to your return.

 

[Td_d]

Right - managed to reconfigure the OP2.0 to ssm logging - your intuition was correct. With the much more reasonable level of data, the learnt corrections are very close to zero - small patch on idle that's a little rich , but between -2% and -4% - which would make sense since this was the part we struggled the most with, and hence tinkered the most with.

Here's the logs - http://dl.dropbox.com/u/3099895/TD D 24 Mar 2011 Logs.rar

 

[HolyCrapItsFast]

http://www.drift-ready.com/Files/TD_D/3-24-2011.zip

Okay Things are looking not that bad. Here ya go... I made fine corrections this time so hopefully this will do it. I would like to verify load compensations just one more time.

 

[Td_d]

Great! When I crunched the numbers I was relieved, was beginning to expect a major mission. Load comps can be refined - still some lumpiness on the low end.

Thanks Holy, will load and test drive tommorow.

 

[HolyCrapItsFast]

Very good! Yeah just drive it enough to confirm what we did and then to get the load comp correct I need you to drive around really long and log. About an hours worth of driving both town and highway... No WOT.

I know this is allot to ask but that is the only way to get good enough data scatter for the tool to compile.:|

I can wait if need be but it has to be done. :tup: