211Ratsbud

iTrader: (1)

46 and 47 didn't provide any real difference in load.

Boosted Tuning

iTrader: (12)

Try 48 and 49.

211Ratsbud

iTrader: (1)

Those read The same if not closer to v7 load

Boosted Tuning

iTrader: (12)

Lol, well last, but not least, try 42 and 43.

If its not those, then its a different issues, then the wrong load logged.

nonschlont

iTrader: (3)

6B48/49 for temp+Baro load. @ 0,0 and 0,1 in the MUT table

jedibow

iTrader: (1)

Address 840B is a hack that tephra wrote into the ROM for version 7, you cannot change the value that 1 byte load logs. You would have to contact tephra and have him re-write the protocol for the address at 840B. Like boosted originally suggested log both 1-byte load at address 41, and then change your MUT table address for for positions 00, and 01 for 2 byte load. Quick question before you do that, are you using the patch to log airflow in g/s or lb/min? because if you are then you will no longer be able to as these addresses are currently located in MUT locations 00, and 01. Also if you change them be sure to uncheck the tephra option in EcuFlash for "Enable airflow calcs"

Hope this helps,

George

211Ratsbud

iTrader: (1)

6D87 is in my MUT table at 33. Is there more than one ign request to log? IE one before a compensation is added? or should the timng requested be after everything?

07EvoIX

i only know of 2 timing requests. actual timing and TimingMap/TimingRAW. TimingMap/TimingRAW is what the ECU is targeting and the other is what the enging is actually doing.

again i only know the address for an ADM IX so not sure if your address is correct or not. maybe someone can advise

cheers

211Ratsbud

iTrader: (1)

I mis titled the log, but the loads between v7 and 2b were so close mostly with in 10 load, and even more within 5 that it doesnt explain the obvious 2* difference where I have 0* in my map, and that log pulls 2*! not much knock there but its there at times.

211Ratsbud

iTrader: (1)

Anyone see this regularly ?

10isace

iTrader: (12)

Subscribed! I'm having the same problem.

211Ratsbud

iTrader: (1)

Have you logged timing map yet?

el.guerrero

same problem on my 8458 rom

211Ratsbud

iTrader: (1)

Post rom id with log if you can.

10isace

iTrader: (12)

Since I started using Evoscan v2.9, I lost the ability to log my timing map. I can't remember if it's something I added to my other Evoscan versions. I'll figure it out.

94170715