new live map app
#571
My live map won't run anymore . It says the beta has ended but when I download the 'new' version...same error pops up. Anyone else have this issue, or is it because I haven't donated?
#574
I am mean........I put in hard limits so people well use the latest version....but then I am lazy and don't update the program..........
Lol, been on a very long holiday...back now, so will release and update, just got to work out where was I with bugs and all
Lol, been on a very long holiday...back now, so will release and update, just got to work out where was I with bugs and all
#576
new version is up. a few changes. there are now additional maps that are in available in ram. but only for evo7/8/8mr (evo9 is under development)
but with the new version and the new maps, obviously u will need to repatch your rom. i recon repatch and then just copy the ign/fuel/boost etc tables back. also note the change in ecuflash xml due to moving the maf/injector scalings to ram, as u will need to update your ecuflash xmls otherwise you will cause issues.
but with the new version and the new maps, obviously u will need to repatch your rom. i recon repatch and then just copy the ign/fuel/boost etc tables back. also note the change in ecuflash xml due to moving the maf/injector scalings to ram, as u will need to update your ecuflash xmls otherwise you will cause issues.
#578
ziad, I just updated to the new version, updated ecuflash xml & re-patched my ROM(9653xxx6).
I am noticing that when I open the Alt Inj latency table in ecuflash using the address 38280 that the latency values are all jacked up, the MAF Comp table looks fine.
Should this be a concern or can I just input the correct values?
I am noticing that when I open the Alt Inj latency table in ecuflash using the address 38280 that the latency values are all jacked up, the MAF Comp table looks fine.
Should this be a concern or can I just input the correct values?
#579
mate i will have a look through the code and get back to you. Is yours SD or normal MAF rom?
but first thing if you can do is see if the correct values are shown when u read injector latencies in RAM (in ELM). if they read as per what they should be. then most probably the address i gave u is wrong, which is more than likely the explanation here.
but first thing if you can do is see if the correct values are shown when u read injector latencies in RAM (in ELM). if they read as per what they should be. then most probably the address i gave u is wrong, which is more than likely the explanation here.
#580
Yeah, I'm on 2d SD.
The car is currently down right now waiting for the parts to move a full size battery to the trunk, the PC-680 is completely shot. If I get some time later today I'll hook up a set of jumper cables & flash the new ROM in & check it out.
The car is currently down right now waiting for the parts to move a full size battery to the trunk, the PC-680 is completely shot. If I get some time later today I'll hook up a set of jumper cables & flash the new ROM in & check it out.
#581
the autopatching feature is not recomended for SD cars, as i havent tested the patching there and possibility (even though a small one) that the autopatcher will overwrite stuff.
but i will investigate the problem regarding the table not showing up properly as it might be a mistake from me.
but i will investigate the problem regarding the table not showing up properly as it might be a mistake from me.
#583
What are the chances this app could be expanded work with the earlier generation (H8) ECUs? What information do you need? I've got most of the maps labeled out in several different ROMs for the EVO, DSM and 3000GT.