Kangaroo land should be asleep Dead easy to make these sorts of variables adjustable in custom routines. The values have to be loaded from memory anyway, so you just need Dave to tell you where the 4.7V reference is stored. 4.7/5.0*255=240 if he is using a byte value.

 

Yeah he is using a byte value. Its Sunday and 4:53am in Aussie world right now (someone call and wake him,lol).

 

Hot damn, its actually working,lol. Imusta been doing something different when I tried last night. I set my idle cells to -1 in one map and +15 in the other map to see it change in evoscan. Now I gotta confirm the other features. The valet stuff is being a real pain.

Tephra, do you have a description of what each table does exactly for the new valet settings?

 

OH yeah...

you talking about the v4.2? it's just 3 options for it: Rev limit, how long it takes for you to set the valet mode and the duration for the flashing light.

 

THis is V4.3 but the valet seems to be the same. When I shut off the valet mode (blinking fast) it still blinks slow afterward.

SO I did some logging and its REALLY hard to get a smooth timing graph with 272 cams,lol. If I hold the gas at 2000rpm, it stays solid at 30* one map but when I switch it, it seems to rapidly bounce between 30 and 35* (its supposed to be 35*). I wonder if its the cams or if its rapidly switching between the 2 maps. I'll do some more logging later.

 

why don't u have map A) aggressive and map B) stock so you can tell the difference for sure.

 

Oh trust me, the maps are at a minimum of 5* off from each other. CLoser to 7* degrees. The problem is one seems to stay at the desired timing and the other bounces between (what seems to be) the alt map settings and the aggressive settings.

 

Jamie, things are happening fast when you are around!

 

+1!

 

Thanks guys I am very driven and passionate about my goals once I set them. Its a blessing and a curse,lol. I've been given the evil eye from my fiance QUITE a few times already since I started 'understanding' the ECU possibilites of the Evo,lol. Its not pretty.

I'd be working on this right now if I didn't think she'd cut off my manhood while I slept tonight!

You guys are great too, my ideas are nothing without all of yours to bounce off of.

 

bobbit bobbit


Jamie don't sleep

 

Sleep is for the weak...or STI owners

 

oooh i'm telling

 

Ok, did some more logging. Don't know if everyone can see the 8929 data item I have, if you can't I can give you the code to add to evoscan so you can see this log. the standard timing maps are set to 13* in one huge block in both the high and low maps, the ALT maps are set to 20*. Notice how the ALT map seems to fluctuate between the standard and ALT map settings????

I'm adding a snapshot and CLCK HERE for a link to the .csv file

 

so you got it working?

right well on your ROMID you can log 0xFFFF8425 and see what maps the ECU is currently using.

if 0xFFFF8425 = 00 then its using stock maps, if its 03 then its using altmaps. That might help in your logging!

ps 0xFFFF8424 is actually 4 bytes long, but rather than stuffing around logging all 4 we will just log the 2nd one...

also the 240/255 thing is static at the moment but Its easy to make it a tunable knob!