Not at all. Info, please?

 

Cobb's software does a poor job of protecting encrypted tune files, they are left in plain text in memory at various times during execution. It requires no real circumvention or reverse engineering, just the ability to read ram with a debugger, etc.
I basically found this out by accident by running strings on a core dump.

 

Yes. I am aware of this.
Anything is possible in hex if you know what to look for.

 

I guess nothing could prevent a skilled person from getting at this data, but if I can do it, clearly they didn't try hard enough.

 

Where do you think the first EFIDude calibrations came from?
They didn't even remove the copyright info when they ganked it.
A user on this forum in Florida (his last name is Greene, I don't remember his user name) bought an AccessPORT on March 1st, 2008.
That calibration almost immediately turned up in the EFIDude offering.

Cobb changed their system shortly thereafter, but it wasn't really much better.

 

Got massive thunderstorm at the moment, logs on my desktop. my maf is post 25 i think, red and yellow lines.
Logs will have to wait a day or 2

3rd gear WOT gonna be hard to do around here. rest shouldn't be that hard. I gonna give one more day for ltft to level out, Only drive the car maybe 10-15 minutes a day on work days. I'll keep ya posted.

 

Calculate the difference between commanded AFR and logged AFR. Graph that.

 

If you can post the idle data and the cruise data, that is a good start.
You should adjust the maf in those two area's before doing the WOT runs anyway.

Whaddya mean a 3rd gear WOT is hard to do .... take it for a spin to the Airport.
Lots of spots on the way out there to open the taps
Or you could head towards Espanola.

Log these values at the very least:
· Equiv. Ratio
· Calculated Load
· Long Term FT1
· Mass Airflow
· RPM
· Short Term FT1
· Vehicle Speed
· Accel. Pedal Position

 

I run on the straight to falcon after the turn to the airport, that damn hill dont give me much time to slow down for the other side though. Don't wanna have an accident or a cop on the other side haha.

 

I'll go grab some logs right now, be back in 30 minutes, I'll do my wot there and do all my cruise sets to the airport. I'll do idle and wot and do cruise at 3-8 in 500 blocks in whatever gear i can get away with around 90. brb.

 

Here ya go, go nuts haha, seems the ap dont store much logs. only log 6 to 15 was on it.

 

Wow
Lots of stuff there

I will have a look at it

 

It stores 10, IIRC.

lol. Part-throttle, steady-state logs at 7k RPM. You can stop at 4200, you know.

Logs look normal to me. They aren't tuned correctly, but there isn't anything wrong, per se. Just fix it right and you should be fine.

Indeed. Took me almost 3 full minutes. I was gonna quit before that, but I am waiting for my ramen to boil.

 

right so first
You gotta label the log files dude
example
WOT 2nd gear
Cruise 3 rd gear

First couple logs of cruise I guess (6-9) look good.
Log 10 WOT logs good .. you are almost at MBT

After that the logs look like they are from a different tune. You start showing trim at idle and at 3000 rpm
And the WOT logs are adding 2% fuel

None of the trims look really bad yet.
Take 2 percent from the fuel map in the entire area from 4500 rpm and 88% calc load and up ... relog

 

Ya ... 10 ... maybe 9 ...
I can't remember either ... .all I know is it starts replacing the oldest logs first

 

Yeah they all the same drive, would the closed loop going til 4k be screwing up my LTFT, I noticed the trims go everywhere if i floor it under 4k. I tried everything, idle, wot 2nd and 3rd, and cruising at 3-8 every 500 rpm, some different gears because of traffic. I wish i used the rpm on the ap though, i didn't think the rpm gauge was that bad. Tomorrow i'll try wcs's suggestions when i finish work, Give me a good set of things to log, so your not reading stuff you dont need to. I think 2 and 3 wot should be good considering i am only changing the top end of the maps. if there is anything else specific you want me to log let me know.
Night

For 11 to 15 hmmmm
11 was 2nd wot
12 was 3rd wot
13 was 2rd wot, i think i was getting rev happy haha
14 was 100 cruise in 6th. i was trying to change the displayed data and didn't notice i started logging. for whatever it is worth.
15 was coasting to my driveway, figured i would grab an idle after all that **** to see my trims, not sure if you needed it.

 

Sigh...

EDIT - I have to admit; This is really frustrating to watch.

 

Really, I find it a good learning experience MM. Don't worry, I'll try not to drive you mad lol. Think happy thoughts.

 

Perhaps, but it seems antithetical to "learning" when the methodology is so scatterbrained.

 

Really?
I think that building those kind of LTFTs over a single drive is pretty damn bad. Just look at how the AFRs change from log 11 to 13.

 

I got the feeling those logs didn't occur all in the same drive cycle.
If they had I would have expect to seem them earlier.

Not suddenly build in this particular logging session.

That all being said, 3ish trim is not bad but I don't know how fast trim builds and whether is builds faster if things are worse or not.

I'm guessing that's why Jeff's asks for several drive cycles to let these things settle in ... you never know it may stay at that trim level and not get any worse... it could actually get better.

 

The thing about LTFT and STFT are the breakpoints wreak havoc on your tuning if you don't know where they are or how to log around them.

I would have thought by now oltmann or someone else would have deconstructed my instructions instructions in this thread.

 

IMO, LTFT should only have to account for changes to sensors output over a long period of time.

Maybe this is perfectionism, but I've found that LTFTs building that soon mean the sensors are miscalibrated enough that WOT AFRs will vary too much based on gear, grade, temp, etc.

Do you want to hit your targets once, or every time?

Of course, my psychiatrist says that, "[I] seem very methodical." Maybe it's just me.

 

LTFT doesn't always set over a long time. Sometimes - often, really - it is nearly immediate.
It depends on a balance of ECT and the amount of time spent in a particular breakpoint.
I've watched LTFT build 4 or 5 points in a matter of seconds if a "pocket" in an otherwise smooth breakpoint is covered in equivalent STFT. But only if the conditions were right.

I've also watched a breakpoint suddenly build 3 LTFT points out of nowhere on a tune that was stable for many, many months because the right combination of load and ECT were met because of a change in BARO and IAT. I've also watched that same tune dial out that same LTFT the next day.

The methodical way to approach this is to find the breakpoints (though there are 5, only 3 really count) and learn to build a realistic fuel curve that matches the MAF to resultant AFR, after you have identified your relative injector scaling.

Also, you have to actually understand what the CL tables adjust, not what they seem to adjust.

 

I think this thread covers it pretty well. Or I could link to one of the times Flashwing explained it, but I don't want to get him in trouble again.