l2r99gst

iTrader: (2)

Everything in the altmaps section is copied to RAM. You don't have to do anything for that to happen. Any table that is in the alt maps space and has it's table pointer set to the RAM location is ran from and tuned from RAM.

Correct on tuning your fuel.

The realtime changes you are making are just to the RAM maps, just as in DSMLink, for example. The changes will be permanent in RAM for as long as you keep battery power to the ECU. If you want it permanently flashed to your ROM, then you copy your tuned RAM tables into the ROM tables and flash. So basically, you can tune a million times until you are happy, then flash once. Or just run from you RAM maps and never disconnect your battery.

03whitegsr

iTrader: (8)

Thank you, makes sense.

Still trying to figure out what for and when to use the ROM2RAM and Reset Dead buttons?

ziad

iTrader: (1)

ROM2RAM: copies the 2k data block from a ecuflash hex file (ALT MAP Space) to the ram... i generally use it to copy the whole contents across. ok i have two files... one is the main flash file it has changes made to it that change non alt map stuff... like say idle settings, rev limit. which i call base rom.... then the changes i made to the alt maps i copy to secondry roms.... this way i have a copy of all the major steps.... no once i am happy with a current tune or change some table that is not in rom i create a new base rom. then just change the alt maps on secondry roms

ziad

iTrader: (1)

also, say if u wanted to make many changes... like u r changing some bits of the timing map, fuel, wgdc... it might be easier to save them to the ecuflash hex file and just load it from there.

this was more of a problem when we had to edit each cell one by one... i found it easier to make changes in ecuflash and just load them.. but now that u can just select cells and hit + or - or = and make big changes its not that important.

DEAD: on some ecus usually pre Evo9, ecuflash does not clear all ram contents. this can sometimes mean that the code does not know that new ROM maps have been written that might be different than whats in the ram... clicking on DEAD will reset and cause the ECU to copy rom tables to RAM.
again a problem in my car... where because the logging mut table was in ram, after a reflash the car wont start as its got gibberish for timing and fuel tables as well as the ram mut table would be gibberish and hence livemap wont start. clicking the DEAD button would cause the ecu to reload data.

tephra

iTrader: (6)

good job dude!

u comp test your motor yet?

ziad

iTrader: (1)

on a cold engine... 160,170,170,170..... i already told the bad news to the bearded man. looks like he has some thinking to do. as the minimum is supposed to be 140, and 163 being the sign of a good motor. and 14the max variance between the cylinders.

tscompusa2

iTrader: (22)

those numbers are good cold. did the one that had 160 read that different consistently?

i just tried to log with the live map and it was giving me a error to connect, does the car have to running for it to start working? it kept erroring like it couldnt find the port. evoscan works right away tho. i flashed my ecu to one of the dma roms in tephra v7 thread and it just timed out.

ziad

iTrader: (1)

so u got the livemap non sd version of 9653. as long as the car ignition is on ON. it will work... do u have two FTDI devices connected?? sometimes i did notice that ecuflash 1.42 doesnt giveup the cable after a reflash (saying that it hasnt done it for ages now). on the bottom of the window what status messages come up. does it say DMA then some error message. or does it say request not read.

the common error messages are:
Unable To Open Port
Init failed
Request Read Error

tscompusa2

iTrader: (22)

Request Read Error

no i just had one connected. i flashed to the livemap 9653 than turn ign off/on than opened prog and i got the error everytime.

ziad

iTrader: (1)

have u tried a ecu reset (or unplug the ecu)? or tried clicking on reset DEAD try that.

try the DEAD.

jcsbanks

Had a quick download of your latest ziad, and it is well organised, impressive!

tscompusa2

iTrader: (22)

tried all of that, it kept giving the same error. does the app only read a specific com port or something?


actually i didn't disconnect the negative from battery and let the memory reset itself, i bet thats what it is.. the memory still had
info from the old rom still in it you think? ill try that and also try switching to diff com / usb ports. its weird tho why is evoscan
user friendly and connects no matter what? your prog has to read a certain set of bytes in the memory to activate or something?

ziad

iTrader: (1)

hmm have u tried the app that came with the rom itself... if that doesnt work then u have some problem that i have no idea how to fix...... unless u put the wrong rom on the car.

the reason evoscan works is cuz it uses basic MUT protocol that is standard built into by mitsubishi. DMA/Livemap is something that was added into the ecu as additional. u can think of like evos run fine on normal petrol.... but without conversion dont work with e85. evoscan is like petrol and livemap is like E85

and thanks for the nice comments John... it wont have been possible without you for sure

ziad

iTrader: (1)

wow just noticed that ppl have accessed the download page 45 times... so i assume its 45 downloads... didnt think there were this many people interested.... only one unhappy person so far.

tscompusa2

iTrader: (22)

i just now noticed the file Evo Live Map-v7final-bigmap im sure it will work after that, and also i was in a hurry when i was doing it cause i was in shorts and the garage was 25F.