ECUFlash / Evoscan / Mitsulogger Questions
#1547
Silver Sponsor
iTrader: (-1)
my first instinct is that the xml file you are using has got bad settings in it. but it also could be something that I can write some code to do a workaround to cater for your bad xml file. or it could actually be a bug with particular xml settings. best to send me your hex, xml, and base xml file, and I can check it out.. send to hamish at evoscan dot com. cheers.
#1548
thats not strange.. that looks fantastic..
now follow the 2nd instruction I said in a few posts back..
after pressing Ctrl+H in ultraedit, now press CTRL+G and goto the location
0xf52 for evo7/8/9/airtrek
0x1021a for Evo 5/6
0x1fefa (for vr4/galant/legnums/mirage)
0x2fefa (for vr4/galant/legnums/mirage)
and take a screenshot of each for us to look at.
now follow the 2nd instruction I said in a few posts back..
after pressing Ctrl+H in ultraedit, now press CTRL+G and goto the location
0xf52 for evo7/8/9/airtrek
0x1021a for Evo 5/6
0x1fefa (for vr4/galant/legnums/mirage)
0x2fefa (for vr4/galant/legnums/mirage)
and take a screenshot of each for us to look at.
Ok :-)
Here is the screenshot.
thanks
#1549
Evolved Member
my first instinct is that the xml file you are using has got bad settings in it. but it also could be something that I can write some code to do a workaround to cater for your bad xml file. or it could actually be a bug with particular xml settings. best to send me your hex, xml, and base xml file, and I can check it out.. send to hamish at evoscan dot com. cheers.
#1550
Has anyone had any problems getting the start/stop datalogging hot keys to work before?
I recently got a new laptop which is Windows 7 64-bit. For some reason now when I want to start/stop logging, EvoScan isn't responding to Ctrl + Space. Often it will work once with the hot keys, then stop responding to them in subsequent logs. So then I have to go up to File menu and manually select Start or Stop DataLogger.
My old XP laptop works fine with the hot keys.
I've made sure both the Ctrl and Space keys are working well on this laptop, so it seems to be some random glitch...
This is running EvoScan v2.9.0023
I recently got a new laptop which is Windows 7 64-bit. For some reason now when I want to start/stop logging, EvoScan isn't responding to Ctrl + Space. Often it will work once with the hot keys, then stop responding to them in subsequent logs. So then I have to go up to File menu and manually select Start or Stop DataLogger.
My old XP laptop works fine with the hot keys.
I've made sure both the Ctrl and Space keys are working well on this laptop, so it seems to be some random glitch...
This is running EvoScan v2.9.0023
#1551
Evolved Member
i edited my xml file , added 2 byte load and its correct values and mut table and checked the 2 byte load for logging.
Since then live tracer isnt showing any value from the grid which i logged. the past logs which were done with out editing the xml are displaying the values.
help.
Since then live tracer isnt showing any value from the grid which i logged. the past logs which were done with out editing the xml are displaying the values.
help.
#1554
Silver Sponsor
iTrader: (-1)
i edited my xml file , added 2 byte load and its correct values and mut table and checked the 2 byte load for logging.
Since then live tracer isnt showing any value from the grid which i logged. the past logs which were done with out editing the xml are displaying the values.
help.
Since then live tracer isnt showing any value from the grid which i logged. the past logs which were done with out editing the xml are displaying the values.
help.
{"Load", "LoadMUT2Byte", "LoadCalc", "EngineLoad", "AbsoluteLoad", "Load160", "ECULoad", "Load11bit4", "Load1B", "AbsLoad", "AccLoad", "LoadMIVEC", "LoadLowIATSTiming", "LoadFuel"}
{"RPMMUT2Byte", "RPM", "2ByteRPM"}
the grid stops searching when it finds the first column above with data...
#1555
Silver Sponsor
iTrader: (-1)
Has anyone had any problems getting the start/stop datalogging hot keys to work before?
I recently got a new laptop which is Windows 7 64-bit. For some reason now when I want to start/stop logging, EvoScan isn't responding to Ctrl + Space. Often it will work once with the hot keys, then stop responding to them in subsequent logs. So then I have to go up to File menu and manually select Start or Stop DataLogger.
My old XP laptop works fine with the hot keys.
I've made sure both the Ctrl and Space keys are working well on this laptop, so it seems to be some random glitch...
This is running EvoScan v2.9.0023
I recently got a new laptop which is Windows 7 64-bit. For some reason now when I want to start/stop logging, EvoScan isn't responding to Ctrl + Space. Often it will work once with the hot keys, then stop responding to them in subsequent logs. So then I have to go up to File menu and manually select Start or Stop DataLogger.
My old XP laptop works fine with the hot keys.
I've made sure both the Ctrl and Space keys are working well on this laptop, so it seems to be some random glitch...
This is running EvoScan v2.9.0023
#1556
Evolving Member
iTrader: (14)
Hello,
I've just started to log my evo 9. I can get all values to log including my aem wideband. I having no luck logging load.I've tried logging all the different load related values and I get many different values but cannot get a correct load value to display. I know one of the load checkboxes stops at 160 so that doesn't help me. I am not tephra modded so I know I can't use the 1 and 2 byte logging. Which load checkbox should I be using?
I've just started to log my evo 9. I can get all values to log including my aem wideband. I having no luck logging load.I've tried logging all the different load related values and I get many different values but cannot get a correct load value to display. I know one of the load checkboxes stops at 160 so that doesn't help me. I am not tephra modded so I know I can't use the 1 and 2 byte logging. Which load checkbox should I be using?
#1558
Silver Sponsor
iTrader: (-1)
Hello,
I've just started to log my evo 9. I can get all values to log including my aem wideband. I having no luck logging load.I've tried logging all the different load related values and I get many different values but cannot get a correct load value to display. I know one of the load checkboxes stops at 160 so that doesn't help me. I am not tephra modded so I know I can't use the 1 and 2 byte logging. Which load checkbox should I be using?
I've just started to log my evo 9. I can get all values to log including my aem wideband. I having no luck logging load.I've tried logging all the different load related values and I get many different values but cannot get a correct load value to display. I know one of the load checkboxes stops at 160 so that doesn't help me. I am not tephra modded so I know I can't use the 1 and 2 byte logging. Which load checkbox should I be using?
#1559
Silver Sponsor
iTrader: (-1)
I will include the latest evo7base.xml in the new EvoScan version v2.9.00092
FIX:
copy the file evo7base.xml from Ecuflash folder: C:\Program Files (x86)\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\
copy the file to this folder: C:\Users\ahernh\Documents\EvoScan v2.9\ROMS\
NOTE: you can't just delete the evo7base.xml because it is part of the EvoScan installer progra, and it will keep re-creating it everytime you try to delete that file.
#1560
Silver Sponsor
iTrader: (-1)
Yes I understand that, it won't open for me in Evoscan , ECUFlash has never been an issue?
I'm really only wanting to use the map trace function to speed up tuning. Currently it's really laborious open the xl file, move the logged cells so everything is on the same screen, freeze the top row then start scrolling etc.
I appreciate the time taken to get the above result, it just didn't work?
I'm really only wanting to use the map trace function to speed up tuning. Currently it's really laborious open the xl file, move the logged cells so everything is on the same screen, freeze the top row then start scrolling etc.
I appreciate the time taken to get the above result, it just didn't work?
multiple copies (x3) of your rommetadata xml folder, old versions of ecuflash and evoscan.
the actual fix was simple.. remove all the duplicate copies of rommetadata xml folders. install the latest clean verison of ecuflash with default XMLs
your ROM is 20030013 JDM Galant VR4.xml and it already comes default as part of the latest ecuflash.
I copied your kenneth mods xml into that file, and named it 20030013 JDM Galant VR4 Kenneth mods.xml
now you are all good to go! it works on both Ecuflash and Evoscan no problems at all.
Cheers,
Hamish.