When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Dear people, I use ziads great app for more than two years now, but never did any latency tuning. Now I have to and find out that latency has some strange behavior. It doesnt read the rom table as flashed properly, but instead displays the standard evo values, not the ones flashed. When live and trying to write, it takes more than three times write command to eventually say written, but no change really.
Dear people, I use ziads great app for more than two years now, but never did any latency tuning. Now I have to and find out that latency has some strange behavior. It doesnt read the rom table as flashed properly, but instead displays the standard evo values, not the ones flashed. When live and trying to write, it takes more than three times write command to eventually say written, but no change really.
Someone sees the same?
Cheers
You *have* to use the ELM software version that was used to patch the ROM! There were changes to the RAM-Addresses the software reads/writes, so you might end up overwriting completely different data! I experienced similar problems with the injector scaling and latency tables when using a pre-patched tephra7 ROM and the latest ELM. Just look at the vector table and the addresses set in the ELM software - if they differ use a "virgin" ROM and make a clean patch. After patching a non-elm tephra7 ROM with the latest ELM-Software it works flawlessly for me. Haven't done much with it yet as the car was only driven ~1km from the workshop to the garage, but dialing in the latencies and adjusting timing and fuel maps for more stable idle worked perfect.
Any support for Speed Density 2.0 with the 3D VE table? Would be awesome to have a friend drive my car around and get my cruise VE as close as possible making changes in real time as I can see what's happening.
Injector Latency post in application patching assistance/question:
This has been touched on in previous posts but not clearly answered & I'm having issues starting the car on roms patched with the latest version & yep I've reset DEAD. Im on MAF not SD
After patching a clean ROM & modifiying the XML as outlined in the app my Injector Latency table is now incorrect. I've trying simply pasting the correct values in but no dice, car wont start on Alt Maps, Main remains okay & starts no problem. Car will however run very badly if swtiched to ALT maps after starting & will stall on idle at first opportunity
Used EvoLiveMap through several version & Beta expiries so I'm not a first timer, maps/tables the copy/pasted between main & alt.
Do the Map vectors still need to be changed post ROM patch? Cant find a clear answer, tried both anyway still wont start on alt maps. Any ideas fellas?
what version of ecuflash is everyone using? i've downloaded and copied my maps into the rom, but i cannot use the latest version of ecuflash w the 1.3u cable.
so do i install an older version, say 1.29 and then copy tephra xml into the evo metadata folder.
after that use the 1.3u cable to pull my current rom (for backup) and then flash the DMA rom?
cas i flashed it once and car wouldn't start so i went back to my backup but had to go thru the hassle of uninstalling old ecuflash and then reinstalling latest version because my original backup was an srf file :/
are u happy if i put them as an extra tab under utilities..i will try the new tab control, i can hide tabs in it apprently... which is a feature lacking in the microsoft standard ones
ahh yes will need to increase the font of the text boxes too
EDIT: here is something, let me know what u think. notice that the tab pages are bigger is size now. its till 1025x600 resolution... and no i havent moved the text boxes to a new tab page... will be easy enough to do.
