new live map app
sorry guys been on holidays... didnt think i would be causing this much issues.
ok firstly donner, mate ur prepatched roms available on ur website are then wrong. as i downloaded it now and just looked at it again. the xml says the address that my rom patches to. and the rom is pointing to rom addresses. so if the addresses in ur picture are correct then can u fix the zip file on ur website
i dont invent i just copy.
ok firstly donner, mate ur prepatched roms available on ur website are then wrong. as i downloaded it now and just looked at it again. the xml says the address that my rom patches to. and the rom is pointing to rom addresses. so if the addresses in ur picture are correct then can u fix the zip file on ur website
i dont invent i just copy.
I log my boost as kpa so this is what I end up with as a graph, is it possible to have these scalings adjustable? and yep changing the car by the vdr settings table but it doesn't seem to effect the graph
thanks
Andy
thanks
Andy
^^^^get a battery charger mate
i got one as i keep forgetting to disconnect the OP cable over the weekend.
andy... i will have a look... hmm forgot about kpa ppl (as i do PSI) i might have to make some adjustments in the next version....
i like it, that ppl are now starting to use it and finding bugs... lol
i got one as i keep forgetting to disconnect the OP cable over the weekend.andy... i will have a look... hmm forgot about kpa ppl (as i do PSI) i might have to make some adjustments in the next version....
i like it, that ppl are now starting to use it and finding bugs... lol
Ziad, I redownloaded ELM and repatched one of my ROMs with DMA. Was this the correct procedure to get the updated patch with the correct definitions for 88592715?
Also, for anyone adding the RAM table address to their ECUFlash definitions, there is a typo on the definition which causes v1.43 to not be able to open a DMA ROM. Here is the corrected definition FOR 88592715 :
Also, for anyone adding the RAM table address to their ECUFlash definitions, there is a typo on the definition which causes v1.43 to not be able to open a DMA ROM. Here is the corrected definition FOR 88592715 :
Code:
<table name="RAM MUT Table @ FFFFA230" category="DMA" address="3EE84" type="3D" scaling="Hex16"> <table name="X" type="Static X Axis" elements="16"> <data>-</data> <data>0</data> <data>-</data> <data>1</data> <data>-</data> <data>2</data> <data>-</data> <data>3</data> <data>-</data> <data>4</data> <data>-</data> <data>5</data> <data>-</data> <data>6</data> <data>-</data> <data>7</data> </table> <table name="Y" type="Static Y Axis" elements="2"> <data>0</data> <data>1</data> </table> </table>
Lol I tried changing maps....could replicate..the graph said evo 7...when I normally have 8 mr.
Three other I will put a toggle. In next version.
I will also check that xml..... :-(
Btw I don't like 1.43
Three other I will put a toggle. In next version.
I will also check that xml..... :-(
Btw I don't like 1.43
Thanks!
I have finally had a chance to try this out after work tonight. I am impressed and am now HOOKED on DMA logging! I love data. Thanks for the hard work!
I have a quick question. Can I grab bits? I have just setup MrFred's high/low fuel pump in EvoScan and was wondering if this is something I can setup in ELM?
Also, I rescaled my Load for my Fuel and Ignition tables from 10 to 300 to make converting my maps over easier...any I dont need 350 load yet. Anyway...I was looking in the XML and noticed half of the datatypes are string and half are int. Does this matter? I was going to move my scaling over for RPM and load and wanted to make sure.
I have a quick question. Can I grab bits? I have just setup MrFred's high/low fuel pump in EvoScan and was wondering if this is something I can setup in ELM?
Also, I rescaled my Load for my Fuel and Ignition tables from 10 to 300 to make converting my maps over easier...any I dont need 350 load yet. Anyway...I was looking in the XML and noticed half of the datatypes are string and half are int. Does this matter? I was going to move my scaling over for RPM and load and wanted to make sure.
Last edited by dingus; Jan 30, 2012 at 06:26 PM.
I have finally had a chance to try this out after work tonight. I am impressed and am now HOOKED on DMA logging! I love data. Thanks for the hard work!
I have a quick question. Can I grab bits? I have just setup MrFred's high/low fuel pump in EvoScan and was wondering if this is something I can setup in ELM?
Also, I rescaled my Load for my Fuel and Ignition tables from 10 to 300 to make converting my maps over easier...any I dont need 350 load yet. Anyway...I was looking in the XML and noticed half of the datatypes are string and half are int. Does this matter? I was going to move my scaling over for RPM and load and wanted to make sure.
I have a quick question. Can I grab bits? I have just setup MrFred's high/low fuel pump in EvoScan and was wondering if this is something I can setup in ELM?
Also, I rescaled my Load for my Fuel and Ignition tables from 10 to 300 to make converting my maps over easier...any I dont need 350 load yet. Anyway...I was looking in the XML and noticed half of the datatypes are string and half are int. Does this matter? I was going to move my scaling over for RPM and load and wanted to make sure.

What rom id did you use?
dingus, sorry no it doesnt have any thoughts to do bits. the only suggestion i would have is get the whole ram address and look for differences, crude.
anyway, i dont recomend editing the xmls directly, obviously if u make a mistake the program crashes. best to use the program to make changes. yes u can edit the scalings. goto tables and open the relevant table and change the x or y axis as u see fit.
new version is on track for early next week... unless a big bug is found. i am just working on a few small enhancments to the functionality.
anyway, i dont recomend editing the xmls directly, obviously if u make a mistake the program crashes. best to use the program to make changes. yes u can edit the scalings. goto tables and open the relevant table and change the x or y axis as u see fit.
new version is on track for early next week... unless a big bug is found. i am just working on a few small enhancments to the functionality.
I used 88590715 patched by ELM. I have never setup the altmaps...ziad said that the patched version doesnt work quite right. I just got DMA logging working. I was going to work on setting up your ROM tonight. It is the time of the year to get all the kinks worked out so when it warms up I can just jump into tuning and working on the car.
I was also poking around and saw that you didn't have a 8859 ROM with SD2.0. Id love to work on that if you are willing to help me out. I'm sure I could eventually figure it out but it may take me forever. Ziad said that the SD2.0 code and tables don't fit in the normal code limit so I am not sure what all needs to be dont to make it all work. Anyway...what would it take to get SD2.0 and DMA working on the 8859 ROM?
PS: Sorry I never responded when you offered up the 8859 ROM on the SVN thread...got hectic around that time and this is the first time (and good weather...yeah I'm one of thous...) I have had to mess with the car.
Last edited by dingus; Jan 31, 2012 at 06:37 PM.





