Need logging and evoscan help!!!!! Please!!!!
Need logging and evoscan help!!!!! Please!!!!
Hey everybody, im sorry about this long, drawn out cry for help. Im a total noob and am having some problems. I have a USDM 2012 RA and recently flashed to the v30.005 gst boost pill 93 oct map. The flash was not a problem. That in itself was easy. But im having a problem with using evoscan and logging. I dont even know if the logcfg.txt file is the right file for my car. I do have a logcfg.out and it is writing data when doing standalone logging. When i try to drag the log files, the "csv" files if thats the right term, into evoscan, it gives me some errors and wont let me view anything. Is my problem my txt file, or something with evoscan and how i have it set up? Sorry for my noob post...
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
There are quite a few things to work through here...
1. Getting the right addresses, formulas, etc.
2. Using Evoscan directly to log.
3. Configuring "OP2.0 Standalone" logging.
4. Finding a way to easily view standalone logs in Evoscan.
It sounds like you mostly need help with 4, but let's work through all of them.
Not just for you, but so other people with 2012 RAs can find their feet when it comes to logging.
1. Getting the right addresses, formulas, etc.
Get/check the 2012 RA logging addresses by going to Golden's website. Scroll down to 5803000 and choose "Evoscan: View addresses".
If you're getting garbage for a field, check its address.
Also check as to whether it's a 1-byte, 2-byte or 4-byte field. Both Evoscan and OP2.0 Standalone need you to define the field size. Garbage output will occur if you're asking for the wrong number of bytes.
2. Using Evoscan directly to log.
Evoscan may or may not come with your ROM's logging info already in place.
In any case, EvoScan wants info like RequestId, RequestBytes, Eval. That's what Golden's website shows you ("Address", "Bytes" and "Eval" respectively). If you've set these up as per Golden's site, you won't go far wrong.
Also, Golden apparently has a mega-Evoscan-XML download facility, so you don't need to mess around setting individual fields. Haven't tried it myself, though.
3. Configuring "OP2.0 Standalone" logging.
Here's a sample 2012 standalone logging file. (I'll revise this if it's deficient or busted, lol)
4. Finding a way to easily view OP2.0 standalone logs in Evoscan.
If you look at the seemingly useless last four data entries above, they are the key to getting CLOSE to a .csv format that Evoscan will accept and open.
But... there's one small thing I still haven't worked out how to do in an automated way - the lack of a "LogEntrySeconds" field. This means the .csv files produced by OP2.0 still need to be edited. To that end...
Open the .csv in Wordpad, and change the first line's "time" to "LogEntrySeconds". Save.
Easy, eh? That should make the file palatable to Evoscan's Log/Power viewing menu option.
Let me know how much more info you need here, if any.
Rich
1. Getting the right addresses, formulas, etc.
2. Using Evoscan directly to log.
3. Configuring "OP2.0 Standalone" logging.
4. Finding a way to easily view standalone logs in Evoscan.
It sounds like you mostly need help with 4, but let's work through all of them.
Not just for you, but so other people with 2012 RAs can find their feet when it comes to logging.
1. Getting the right addresses, formulas, etc.
Get/check the 2012 RA logging addresses by going to Golden's website. Scroll down to 5803000 and choose "Evoscan: View addresses".
If you're getting garbage for a field, check its address.
Also check as to whether it's a 1-byte, 2-byte or 4-byte field. Both Evoscan and OP2.0 Standalone need you to define the field size. Garbage output will occur if you're asking for the wrong number of bytes.
2. Using Evoscan directly to log.
Evoscan may or may not come with your ROM's logging info already in place.
In any case, EvoScan wants info like RequestId, RequestBytes, Eval. That's what Golden's website shows you ("Address", "Bytes" and "Eval" respectively). If you've set these up as per Golden's site, you won't go far wrong.
Also, Golden apparently has a mega-Evoscan-XML download facility, so you don't need to mess around setting individual fields. Haven't tried it myself, though.
3. Configuring "OP2.0 Standalone" logging.
Here's a sample 2012 standalone logging file. (I'll revise this if it's deficient or busted, lol)
Code:
; sample logging configuration file for openport 2.0
; must be named logcfg.txt and be placed in the root directory of the
; microSD card inserted in the openport in order to work
; this sample logs using the KWP2000 ReadMemoryAddress command over the ISO15765, which works
; for CAN based mitsubishis that have had their ROMs modified to allow the use of this command.
; this command is also known as "mode23" on some forums. since this command reads directly from
; ECU memory, the paramid addresses used are different for different ROM versions.
;----------------mrmacan evox----------------
; log channel settings
type=mrmacan
paramname=RPM
paramid=0x808794
scalingrpn=x,3.90625,*
databits=16
paramname=KnockSum
paramid=0x808A9B
paramname=LoadTiming
paramid=0x8087C2
databits=16
scalingrpn=x,0.3125,*
paramname=TimingAdv
paramid=0x808A57
scalingrpn=x,20,-
paramname=Baro
paramid=0x80AB31
scalingrpn=x,0.07251887,*
sampgroup = 1
paramname=PSIG
paramid=0x808766
databits=16
scalingrpn=x,0.048828,*,Baro,-
;paramname=IPW
;paramid=0x80AB6C
;databits=16
;scalingrpn=x,0.001,*
paramname=TPS
paramid=0x808745
scalingrpn=x,0.3921569,*
paramname=ActiveWGDC
paramid=0x808BB1
scalingrpn=x,0.5,*
; log these items a little less often using a sampgroup (see subaru example for more details)
paramname=Speed
paramid=0x808837
scalingrpn=x,2,*
sampgroup = 1
paramname=FuelTrim_Idle
paramid=0x804573
scalingrpn=x,0.1953125,*,25,-
sampgroup = 1
paramname=FuelTrim_Cruise
paramid=0x804575
scalingrpn=x,0.1953125,*,25,-
sampgroup = 1
;--------------------------------
type=calc
paramname=LogEntryDate ; Dummy entry - Designed to produce an EvoScan style format
; that can be loaded into "Log and Power Graph" without (much)
scalingrpn=0 ; reformatting.
paramname=LogEntryTime ; Dummy entry
scalingrpn=0
paramname=LogNotes ; Dummy entry
scalingrpn=0
paramname=Custom ; Dummy entry - EvoScan seems to need this at the end
scalingrpn=0
4. Finding a way to easily view OP2.0 standalone logs in Evoscan.
If you look at the seemingly useless last four data entries above, they are the key to getting CLOSE to a .csv format that Evoscan will accept and open.
But... there's one small thing I still haven't worked out how to do in an automated way - the lack of a "LogEntrySeconds" field. This means the .csv files produced by OP2.0 still need to be edited. To that end...
Open the .csv in Wordpad, and change the first line's "time" to "LogEntrySeconds". Save.
Easy, eh? That should make the file palatable to Evoscan's Log/Power viewing menu option.
Let me know how much more info you need here, if any.
Rich
Thank you so much! Im also speaking for everybody else that needs the help. I am going to use you're reply and check everything you said. I have a feeling i have more than one thing wrong. My computer is not near me. But i will check when i can. One more silly thing, the logcfg file. I used one that was floating around in another thread. To be honest, im not sure if its one from a 2012. How do i go about getting the correct file? You included a sample of one from a 2012. And off the top of my head, i noticed a difference between the one you posted and the one i have. Is it something that im overlooking?
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
The key items are the data element addresses. Those vary from ROM to ROM. Use the info on Golden's site as a reference.
Work through the above, and it'll start making sense real fast. You'll be on top of it in no time.
Rich
Work through the above, and it'll start making sense real fast. You'll be on top of it in no time.
Rich
Newbie
Joined: Jul 2012
Posts: 74
Likes: 0
From: New York
This should definitely be made into a sticky.... even better, we should download all of the information in your head rich and then make THAT into a sticky 
. 1, 2 and 4 all make complete sense to me however i just wanted to ask about step 3. do i copy that or write up my own? and if i copy it where do i copy from? the whole thing or ???
. 1, 2 and 4 all make complete sense to me however i just wanted to ask about step 3. do i copy that or write up my own? and if i copy it where do i copy from? the whole thing or ???
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
You can copy the whole chunk. Use that as a starting point - you can add stuff, revise it, rework, etc.
There are loads more items to log, and a few cool tricks to squeeze more out of the limited speed. It can read using various serial/analogue styles too, for stuff like wideband input. But that logcfg.txt example should be a pretty good start.
Rich
There are loads more items to log, and a few cool tricks to squeeze more out of the limited speed. It can read using various serial/analogue styles too, for stuff like wideband input. But that logcfg.txt example should be a pretty good start.
Rich
I used the log file you posted and am still having problems. :/ i followed the instructions on goldenevo web page and i think i did it right. But when i drag my log file from the memory card and drop it into evoscan, i gives me an error. "power/torque graph missing warning: throttle position sensor >80 or missing accelerator pedal position >80. Log file will still be loaded....." and after hitting okay, nothing appears in evoscan. Whats throwing me off is that the TPS is in *the log file you posted. The same one i used. Any clue as to what the problem could be? Also, *The logs that i tried were not small. One was 872kb and the other was 256kb. If that helps any.
Trending Topics
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Zip up your logfiles and attach them here...
[edit]...and when you say you "drag and drop" files from microSD into Evoscan, be aware:
1. You need to edit them first, or Evoscan won't recognise them. In the header, change "time" to "LogEntrySeconds".
2. I'm not sure you can just "drop" them into Evoscan. Well, I can't on mine! I need to load them like this:
- Select the "Graphs & Maptracer" heading.
- Select "Log & Power Graph".
- Go find the .csv and load it.
That should show a graph of the logged data.
It may not be awesomely pretty. Not until you align the "recognised" data elements in Evoscan with the headings in your logfile, set up some suitable graph "Scaling Factors", choose purdy colours, etc.
But more on that later.
Rich
[edit]...and when you say you "drag and drop" files from microSD into Evoscan, be aware:
1. You need to edit them first, or Evoscan won't recognise them. In the header, change "time" to "LogEntrySeconds".
2. I'm not sure you can just "drop" them into Evoscan. Well, I can't on mine! I need to load them like this:
- Select the "Graphs & Maptracer" heading.
- Select "Log & Power Graph".
- Go find the .csv and load it.
That should show a graph of the logged data.
It may not be awesomely pretty. Not until you align the "recognised" data elements in Evoscan with the headings in your logfile, set up some suitable graph "Scaling Factors", choose purdy colours, etc.
But more on that later.
Rich
Last edited by richardjh; Aug 10, 2012 at 04:48 AM.
Newbie
Joined: Jul 2011
Posts: 70
Likes: 0
From: San Antonio tx
I used the log file you posted and am still having problems. :/ i followed the instructions on goldenevo web page and i think i did it right. But when i drag my log file from the memory card and drop it into evoscan, i gives me an error. "power/torque graph missing warning: throttle position sensor >80 or missing accelerator pedal position >80. Log file will still be loaded....." and after hitting okay, nothing appears in evoscan. Whats throwing me off is that the TPS is in *the log file you posted. The same one i used. Any clue as to what the problem could be? Also, *The logs that i tried were not small. One was 872kb and the other was 256kb. If that helps any.
I have the exact same issue when trying to log. I logged directly to evoscan not standalone. I can get it to log but when I go try to open the log in evoscan i gives me this exact error and nothing seems to display. I even posted a few times on here about it but was never able to get it going? I would really like to get this fixed...
I flashed to the v30.006 you posted on the GST basemap thread. And now i can view my saved logs following your instructions on how to load the saved data into evoscan. I didnt do a proper 3rd gear pull sweeping thru the entire rpm range. I did it more for just a test to see if i could get the data to load. One of the tests didnt show any knock sum. The other showed rediculous amounts. Ranging from 11-15. Could that be because of my improper test run? And how do i set a trigger to only record data on my command?
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Well done!
knocksum of 11-15? Was that, by any chance, 1500rpm-2000rpm / 55-75 load?
I wouldn't bother with switching standalone logging on/off. It's straightforward to do - people use the cruise control button for this. However 24/7 logging is one of the standalone system's strengths. If you ever have a weird issue just driving around, you've got it on logs.
It's usually not an issue to load a big log and zoom in on one area. And if you want, just take a copy of a big file and edit it to cut out stuff you don't want. For example, delete from line 2 to line <whatever>. As long as the header is intact, it'll still load into Evoscan.
Indeed, programs like Virtual Dyno much prefer to have just one "WOT pull" in the file they load.
Rich
knocksum of 11-15? Was that, by any chance, 1500rpm-2000rpm / 55-75 load?
I wouldn't bother with switching standalone logging on/off. It's straightforward to do - people use the cruise control button for this. However 24/7 logging is one of the standalone system's strengths. If you ever have a weird issue just driving around, you've got it on logs.
It's usually not an issue to load a big log and zoom in on one area. And if you want, just take a copy of a big file and edit it to cut out stuff you don't want. For example, delete from line 2 to line <whatever>. As long as the header is intact, it'll still load into Evoscan.
Indeed, programs like Virtual Dyno much prefer to have just one "WOT pull" in the file they load.
Rich
Sorry for not being too active in the past few days. Been taking care of some personal stuff. But i have been toying around with logs and evoscan on my new netbook. And for some reason all my log files show a rediculous amount of speed. For example, one said i had done a max of 214mph, when i only really did 145mph. On provate property btw. Lol. It shows the same thing on both my mac and my new windows netbook. What could be wrong?
