TD_D mod journey. From stock to the 'bastardmobile'

[HolyCrapItsFast]

That's my issue with the other site now - it's like wading through treacle to find the gems of info (which inevitably sit in older threads, there's a surprise).

Because all the smart ones are here. And the smart ones that are left there are abrasive, condescending and argumentative and you usually have to choke them to get any kind of useful information because apparently they are in possession of some information that, if leaked to the public, would cause the down fall of western society as we know it.

Then there are the ones who sound smart but their so called facts are not based on any real data.

 

[Td_d]

Because all the smart ones are here. And the smart ones that are left there are abrasive, condescending and argumentative and you usually have to choke them to get any kind of useful information because apparently they are in possession of some information that, if leaked to the public, would cause the down fall of western society as we know it.

Then there are the ones who sound smart but their so called facts are not based on any real data.

Exactly. Maybe it's an occupational hazard of heading towards 40, and excuse my French, but when the fuck did everybody become so sensitive?

 

[HolyCrapItsFast]

I know what you mean. There certainly is no excuse for it because I'm 45... or is it 46... I lost count. But anyway I don't think I'm like that.

 

[Td_d]

^ definately not, you've been a tremendous resource - not to be misunderstood, I meant there just seems to be so much precious behaviour (both from the abrasive experts, and from general users) on the site that it just makes it painful to browse. I always land up here within 5 minutes!

Eh... it's past 11pm here, I guess I better drag my ass off to bed... will aim to get some decent logs to you tomorrow, and maybe we can nail closed loop and test drive my (now properly seated and welded) wideband in the next couple of days.

 

[HolyCrapItsFast]

Okey dokey!

 

[Td_d]

Right, managed to get some logs today, only problem - I didn't realise that the mechanic had flashed a new map on :lol:

That being said - it's driving very smoothly - no stumbles, good power delivery - and looking at the graph from crunching the log, latencies and flow scale are spot on - MAF scale could be cleaned up a bit, but not horrendous. Still crunching the numbers, will upload graph as soon as it's done. Whilst the pressure sensor is in, looks like it wasn't plugged in - atmospheric pressure still 1.5 bar, so will have to check under the hood tomorrow to make sure. I also need to recalibrate the wideband (very nicely welded this time - every time the mechanic does the work himself - great stuff - delegated - hmm....).

 

[Td_d]

View attachment 814

I think those first swings are anomalous, due to infrequent data (very low on the g/s scale)

http://dl.dropbox.com/u/3099895/24 Feb 2011.rar

 

[HolyCrapItsFast]

View attachment 814

I think those first swings are anomalous, due to infrequent data (very low on the g/s scale)

http://dl.dropbox.com/u/3099895/24 Feb 2011.rar

Ugh! This guy simply does not know how to scale a MAF.

Take a look at the A/F Learned column and note how all over the place it is. That column should be mostly 0's. The A/F Correction column should be mostly with in +/- 6-8%. The idle trims suck also.

Can you email me your current tune and I will have to compare it to what we did last. Maybe I can compile a hybrid of the two or maybe we should just refine what he did... What are your thoughts?

Also the next time you log get rid of Manifold Absolute Pressure and add Manifold Relative Pressure. If you are not able to fix the atmospheric pressure sensor then we will have to work with what we got.

 

[HolyCrapItsFast]

No... If you are going to remain at the same altitude you can simply tune and be done. But if you change altitude in any way your tune will not follow and you run a risk.

NC is not exactly straight and level. :tup: I guess it depends how high or low before it makes a difference and to what extent I don't know.

 

[Td_d]

I actually think he didn't scale it all today - just slapped on a base map for the current hardware - I'd actually be interested to compare this map to what we got to before, compare.

Fuji - I actually think the sensor is not plugged in - it's too late for me to check though, will need to do it in the morning. Will change to relative, Holy, just in case in the meantime. Let me PM you the link to the map now.

 

[Td_d]

On a different note, got a couple of bonuses over the past couple of days... intercooler swapped out with an APS; boost controller changed to HKS EVC (really more to get a better fitting solution internally, but great controller); instead of BCs I got TEINs; and the whitelines front and rear adjustable 22mm sways are on. I still cannot believe the difference the suspension upgrades have made, the is incredibly tight in the corners now...

 

[HolyCrapItsFast]

It must be a base tune. I wouldn't use any of it. It is RUBBISH! :lol:

 

[Td_d]

Ok... I have to apologise, blond moment - the logs (44 and 43) that I sent are _not_ the new ones. I keep on forgetting to check everytime it comes back - the CAN logging patch is not checked - so it was not logging. My bad...

On the positive side - atmospheric pressure is back! Yeeha, the sensor is working. Pressure today is 0.840 bar - told you we're high up.

Let me take a nice long log now, and see what it comes back with (I already saw the idle trims are well off, -11.90) and then we can continue. I see no reason not to continue with your map where we left off - I think the disasterous last logs had more to do with the sizeable leak in the downpipe.

 

[HolyCrapItsFast]

Okay well that's good news. :lol:

Yes I suggest taking a log with the last map we loaded. There will probably be some stumble but deal with it till we get a good log and we have a chance to adjust it.

Also this time remember to warm up the car and reset the ECU before logging. Also let it idle for two minutes before logging. I don't want to see any residual data

 

[Td_d]

Ok - here's a nice long log, town and highway using the last map we loaded (14 Feb) - also managed to replicate the stumble quite consistently - just before 3000 RPM, partial throttle and loading it up (most pronounced in 1st, and 3rd and 4th).

http://dl.dropbox.com/u/3099895/TD_D_26_2_2011_A - .rar

 

[HolyCrapItsFast]

Okay! Having a look now.

 

[HolyCrapItsFast]

I just wanted to confirm before I continued.

This is definitely a log of the last map we mad? (750rc_2-14-2011-Rev_A.hex)

I knew there would be differences after everything was fixed but not that much.

 

[Td_d]

Yup, that's exactly the one. I was looking at the idle trims and thinking - those are really high...

Would a different intercooler possibly do that?

 

[HolyCrapItsFast]

Yes possibly. That plus all the other repairs put together.

Now that everything is good, things are not good if that makes sense. I need to think.

I feel that we may need to start all over again.

 

[Td_d]

I was worried that might the case - it's had a lot of mechanical work in the last 2 weeks, so maybe a clean slate is not a bad idea. Are you worried about the latency and scaling as well (still scrunching the data in the background, so not yet clued as to the general shape of the MAF scale...)