Notices
ECU Flash

new live map app

Old Feb 9, 2012 | 02:41 AM
  #406  
ziad's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2007
Posts: 529
Likes: 1
From: Melbourne
a small donation to keep the project going results in me sending u a registration key.... but before u do that have a play with it, see if u like the program and it does what u want it to do, or is beneficial to you.... i for a long time used it without that feature (until i built it cuz i got lazy).... a map can be copied to clipboard by right clicking and select copy all. then u can CTRL + V into ecuflash to copy it there.

the ram2disk just makes it quicker.
Reply
Old Feb 9, 2012 | 02:16 PM
  #407  
burgers22's Avatar
Evolved Member
 
Joined: Jan 2006
Posts: 953
Likes: 2
From: Oxfordshire
Send him money......he makes cool stuff to play with!
Reply
Old Feb 9, 2012 | 08:53 PM
  #408  
ziad's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2007
Posts: 529
Likes: 1
From: Melbourne
^^lol i thought that was reserved for tephra
Reply
Old Feb 9, 2012 | 08:56 PM
  #409  
dingus's Avatar
Newbie
15 Year Member
Liked
iTrader: (3)
 
Joined: Jul 2010
Posts: 78
Likes: 1
From: Arkansas
Originally Posted by evoscan
MUTII DTC is for 1997 Evo4 only.

OBDII DTC is for 1998+ Evo5/6/7/8/9

CAN DTC is for 2007+ EvoX
Oh okay. I was getting a weird math error in EvoScan when trying to pull codes with OBDII...an arithmetic overflow error or something. Had to restart EvoScan it to be able to log again or clear DTC. EvoScan, any ideas on the error?

EDIT: Tried it again and got the same result. See the attached screenshot...
Attached Thumbnails new live map app-evoscan_error.png  

Last edited by dingus; Feb 9, 2012 at 08:59 PM.
Reply
Old Feb 14, 2012 | 09:56 PM
  #410  
ziad's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2007
Posts: 529
Likes: 1
From: Melbourne
guys 0443 is up. small changes.

mainly gui changes, fixed the bugs with scaling in VDR. also decided to use most/all afr/map data so that it gives more accurate picture. and fixed the name of the car.

as usual let me know of any issues
Reply
Old Feb 17, 2012 | 11:20 AM
  #411  
Raptord's Avatar
Evolved Member
iTrader: (10)
 
Joined: Mar 2009
Posts: 3,525
Likes: 20
From: Gatineau, Quebec, Canada
Found a minor bug in .443 Ziad; When editing the Ecu Definition and adding a new X or Y axis element, if I click cancel it will still add an empty element rather then actually cancelling.
Reply
Old Feb 20, 2012 | 05:32 AM
  #412  
ziad's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2007
Posts: 529
Likes: 1
From: Melbourne
yep verified... cheers for that.. so u actually testing it atleast.
Reply
Old Feb 20, 2012 | 05:48 AM
  #413  
Raptord's Avatar
Evolved Member
iTrader: (10)
 
Joined: Mar 2009
Posts: 3,525
Likes: 20
From: Gatineau, Quebec, Canada
Yes, it's starting to get warmer so when I get some time off from midterm exams and such I'll try livemap again on my car
Reply
Old Feb 20, 2012 | 08:52 AM
  #414  
CDrinkH2O's Avatar
EvoM Guru
15 Year Member
Liked
Loved
Community Favorite
iTrader: (7)
 
Joined: Nov 2006
Posts: 1,147
Likes: 162
From: San Francisco
Bugs? - Updates to live maps not applied

Hi Ziad - I think there may be a bug in the latest version because changes made in Livemap are not written to RAM. (Yes I'm running on Altmaps . I'm not sure if this is a problem with the Livemap software, the patched ROM, or with the ROM/RAM vectors and need some help to troubleshoot and understand what is happening here.

I have the same problem as Seijuro:
https://www.evolutionm.net/forums/8109174-post131.html

I'm running 96530706 Tephra V7 on my 2005 USDM VIII (originally on 96940011) and normally use the main maps for E85 and the Alt maps for 91. First I downloaded and successfully installed the Livemap software on Win 7. Next I followed your PDF instructions (thanks!) to patch my ROM and added the DMA stuff. I then used Ecuflash to open the patched ROM and copied my main maps over the top of my Alt maps, so that I have the E85 settings available for Livemap. Next I flashed the patched ROM to my car and went through your instructions to reset DEAD, started the engine, started the app, and rewrote the RAM. All seemed to go well. I was able to populate all the tables by reading from RAM. Tracing, and logging data all worked great.

When I made changes to the ignition table and wrote them to RAM with the engine running, the status indicator (bottom left) showed it's was written, but the logged values are unchanged in that cell.

I have already tried changing the DMA vectors from ROM to RAM addresses so changes can be written to RAM per Seijuro's post #138. It now looks like this:



Unfortunately this did not fix the problem. The patched ROM (originally 96530706 Tephramod-V7) has not been changed in any other way. I'm lost at this point. Any ideas on what to try next?

Last edited by CDrinkH2O; Feb 20, 2012 at 02:18 PM.
Reply
Old Feb 20, 2012 | 12:20 PM
  #415  
ziad's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2007
Posts: 529
Likes: 1
From: Melbourne
the vectors were the FFFF xxxx or were they 0003 xxxx when the rom was patched by my program?

can u please send ur rom and ur evolivemap folder to me, livemap at mztec dot org
Reply
Old Feb 20, 2012 | 02:10 PM
  #416  
CDrinkH2O's Avatar
EvoM Guru
15 Year Member
Liked
Loved
Community Favorite
iTrader: (7)
 
Joined: Nov 2006
Posts: 1,147
Likes: 162
From: San Francisco
Originally Posted by ziad
the vectors were the FFFF xxxx or were they 0003 xxxx when the rom was patched by my program?

can u please send ur rom and ur evolivemap folder to me, livemap at mztec dot org
The vectors were 0003 after I patched my 96530706 ROM using Livemap. I checked them using ECUFlash by opening the -DMA patched ROM. I will zip and email you my patched ROM and evolivemap folder in the next 5 minutes.

Either way the changes I make in Livemap are written to RAM, but they are not affecting the AltMap settings seen by the ECU. I'm guessing the ECU is using a different space for AltMaps. What should my vector settings be?

I noticed the RAM addresses in 0443 are different than labelled in the patched ROM. For example Alt High octane timing bigmap is at FFFF A34D. I changed the vectors in the patched ROM so they are the same as those in Livemap and reflashed, but .... changes made in the timing map still don't seem to write to RAM. They definitely don't update the ign timing used by the ECU and as shown in the display on the right of the Livemap screen.

Last edited by CDrinkH2O; Feb 20, 2012 at 05:59 PM. Reason: Update on changed vector addresses
Reply
Old Feb 22, 2012 | 05:42 PM
  #417  
Raptord's Avatar
Evolved Member
iTrader: (10)
 
Joined: Mar 2009
Posts: 3,525
Likes: 20
From: Gatineau, Quebec, Canada
Ziad, tried out the livemap again tonight, running great so far. Changed timing at idle while the car was running to verify it was working properly and it was (the engine's sound even changed as soon as I loaded the changes, very cool!)

Looking forward to experimenting some more with this in the next few weeks! Sending a small donation your way as promised now that it's working!
Reply
Old Feb 23, 2012 | 06:46 PM
  #418  
ziad's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2007
Posts: 529
Likes: 1
From: Melbourne
carl i have replied to ur email, in my test DMA appear to be working but the rom is behaving strangly. but i figure i might talk about the addresses issue here.

the address (vectors in ecuflash) are the pointers to the start of the table, most tables have a header, and hence the vector address is different then the address for the viewable table. as we dont care about the header and only care about whats in the table. if u check ecuflash the address is different from vector address.

internally the ecu obviously prefers to see the table header.


on a slightly different note, a public thank you for all the people who have donated. it is greatly appreciated.

i plan on using the money to pay for hookers, gambling, drugs and alcohol and the rest i will invest... to pay for my divorce (joking)
Reply
Old Mar 4, 2012 | 04:25 AM
  #419  
burgers22's Avatar
Evolved Member
 
Joined: Jan 2006
Posts: 953
Likes: 2
From: Oxfordshire
I've done an initial test on my 9055, looks fine so far. Question about the AFR logging. The original AFR patch used MUT12, and I notice a MUT table posted in post 349 has 0x8409 in MUT12 which matches the original log AFR with ECU. The ELM MUT request for WB02 has MUT39 defined. What set up are people using?

BTW good choice on chemicals and hookers, silly to waste the money.......
Reply
Old Mar 4, 2012 | 07:05 AM
  #420  
donner's Avatar
Evolving Member
iTrader: (1)
 
Joined: Aug 2009
Posts: 199
Likes: 2
From: Europe
Originally Posted by burgers22
I've done an initial test on my 9055, looks fine so far. Question about the AFR logging. The original AFR patch used MUT12, and I notice a MUT table posted in post 349 has 0x8409 in MUT12 which matches the original log AFR with ECU. The ELM MUT request for WB02 has MUT39 defined. What set up are people using?

BTW good choice on chemicals and hookers, silly to waste the money.......
In my prepatched roms (and xml's) I use MUT 3C for AFR, this is used as this is originally rear O2 request and in tephra roms replaced with his log variable 0x8409. Of course this works only if you have wired your wideband to rear O2 input.
Reply

Thread Tools
Search this Thread

All times are GMT -7. The time now is 12:17 PM.