Notices

Evo X Logging

Thread Tools
 
Search this Thread
 
Old Jun 24, 2009 | 02:20 AM
  #466  
Sanci's Avatar
Newbie
 
Joined: Jun 2009
Posts: 2
Likes: 0
From: Hungary
Excuse me my English not too good.
Evo X MR is for me, and I am useful evoscan-t.
I would like to know whether it may be log SST transmission temperature of oil.
Somebody knows it for this the can-id and the formula?
Thanks.
Reply
Old Jun 24, 2009 | 05:33 PM
  #467  
crcain's Avatar
Evolved Member
 
Joined: Oct 2002
Posts: 2,788
Likes: 1
Originally Posted by mrfred
Is this the one that you tried? If yes, then there is something wrong with your setup because I know this Data.xml works. The proper way to get EvoScan 2.6b14 installed is to install v2.5, then drop the 2.6b10 files on v2.5, and then drop the 2.6b14 files onto v2.6b10. Did you do that?

https://www.evolutionm.net/forums/ev...ml#post7176324
Is this correct?

evo4mad describes how to install the beta like this:

Originally Posted by evo4mad
21st June 2009: EvoScan v2.6 Beta15.zip Download EvoScan Beta15 here(registered users only)
- You still need to install EvoScan v2.5 full registered version first. Available here.
Reply
Old Jun 24, 2009 | 05:49 PM
  #468  
SiC's Avatar
SiC
Evolved Member
iTrader: (1)
 
Joined: Jun 2008
Posts: 1,018
Likes: 0
From: Kanagawa, Japan
Originally Posted by crcain
Is this correct?

evo4mad describes how to install the beta like this:
crcain,

Beta 15 has a setup program and beta 14 was just the program file. So to install beta 15, just click on the file and let it install itself as long as you have 2.5 installed. For beta 14 you need to install 2.5 and put the beta 14 files into the install directory of 2.5.
Reply
Old Jun 25, 2009 | 08:52 AM
  #469  
crcain's Avatar
Evolved Member
 
Joined: Oct 2002
Posts: 2,788
Likes: 1
Originally Posted by SiC
crcain,

Beta 15 has a setup program and beta 14 was just the program file. So to install beta 15, just click on the file and let it install itself as long as you have 2.5 installed. For beta 14 you need to install 2.5 and put the beta 14 files into the install directory of 2.5.
So you're saying mrfred was wrong?

Once I read what mrfred wrote, I thought I had found my problem, because I did find it odd that beta11 included an executable and about 6 ".dll" files. While beta14 just had an executable and a data file.

So you are 100% sure that the install of beta14 is to just extract the executable and data file to a virgin 2.5 dir?
Reply
Old Jun 25, 2009 | 02:23 PM
  #470  
SiC's Avatar
SiC
Evolved Member
iTrader: (1)
 
Joined: Jun 2008
Posts: 1,018
Likes: 0
From: Kanagawa, Japan
Originally Posted by crcain
So you're saying mrfred was wrong?

Once I read what mrfred wrote, I thought I had found my problem, because I did find it odd that beta11 included an executable and about 6 ".dll" files. While beta14 just had an executable and a data file.

So you are 100% sure that the install of beta14 is to just extract the executable and data file to a virgin 2.5 dir?
I'm not saying anyone is wrong, I'm just saying what I did.

BTW, why don't you just install beta 15? That comes with all the install files including the newest dll files and it creates it's own directory so it wont overwrite your previous 2.5.
Reply
Old Jun 25, 2009 | 02:38 PM
  #471  
crcain's Avatar
Evolved Member
 
Joined: Oct 2002
Posts: 2,788
Likes: 1
Originally Posted by SiC
I'm not saying anyone is wrong, I'm just saying what I did.

BTW, why don't you just install beta 15? That comes with all the install files including the newest dll files and it creates it's own directory so it wont overwrite your previous 2.5.
So you successfully logged using beta14 by simply extracting the executable and the data file in a virgin 2.5 directory?

I will try beta15 in a day or two, but I'm simply trying to get clarication on conflicting methods of install of beta14.
Reply
Old Jun 25, 2009 | 04:35 PM
  #472  
SiC's Avatar
SiC
Evolved Member
iTrader: (1)
 
Joined: Jun 2008
Posts: 1,018
Likes: 0
From: Kanagawa, Japan
Originally Posted by crcain
So you successfully logged using beta14 by simply extracting the executable and the data file in a virgin 2.5 directory?

I will try beta15 in a day or two, but I'm simply trying to get clarication on conflicting methods of install of beta14.
I never used beta 10 so I never had those files on my PC.

Why don't you just go straight to beta 15, it's alot easier since it comes with an installer.
Reply
Old Jun 25, 2009 | 04:44 PM
  #473  
Hiboost's Avatar
Evolved Member
iTrader: (9)
 
Joined: Apr 2005
Posts: 3,222
Likes: 8
From: Rochester, NY
I just installed b15 and it worked fine in it's seperate install directory. I did import over a few XML file settings and put them in the order I usually log them in for easy review in excel. The 2 byte load doesn't seem to have a formula attached to it though, not sure what the range of values is for that yet.
Reply
Old Jun 25, 2009 | 10:01 PM
  #474  
crcain's Avatar
Evolved Member
 
Joined: Oct 2002
Posts: 2,788
Likes: 1
Originally Posted by SiC
I never used beta 10 so I never had those files on my PC.

Why don't you just go straight to beta 15, it's alot easier since it comes with an installer.
It would be a lot easier if you would just answer my question.

Have you succesfully logged with beta14 by simply taking the beta14 executable and data file and replacing them with files from a _virgin_ 2.5 install? Yes/No.

You keep telling me to use beta15 because it has an installer and that is easy to use. My problem isn't knowing how to extract an archive to a dir buddy. What I am trying to figure out is if my experience in using beta14 and it not working is related to unclear requirements of how to get it up and running, or if it was some glitch on my end.

Unfortunately asking you simple questions is becoming painful!
Reply
Old Jun 25, 2009 | 10:06 PM
  #475  
tephra's Avatar
Thread Starter
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
unless 15 isn't working for you then forget about 14...

AFAIK 15 comes with a full installer - so you dont need to stuff around with installing previous versions then replacing the exe..
Reply
Old Jun 25, 2009 | 11:42 PM
  #476  
GST Motorsports's Avatar
Account Disabled
iTrader: (8)
 
Joined: Sep 2007
Posts: 3,366
Likes: 1
From: Hayward
Originally Posted by crcain

Have you succesfully logged with beta14 by simply taking the beta14 executable and data file and replacing them with files from a _virgin_ 2.5 install? Yes/No.
Raises hand!

Yes I have.
Reply
Old Jun 26, 2009 | 12:10 AM
  #477  
onboost's Avatar
Evolving Member
 
Joined: Jun 2007
Posts: 109
Likes: 0
From: New Zealand
tephra,

i just tried to edit my orig 52360016 xml with the mode 23 stuff so i can log the factory settings but my stooopid vista wont let me. i have mode 23 enabled on my current tune (running a 52360018) and that is working fine. Are you able to help me?

i have teamviewer if that helps
Reply
Old Jun 26, 2009 | 12:34 AM
  #478  
tephra's Avatar
Thread Starter
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
save the .xml someplace else - then copy it manually into the ecuflash directory.

i think if you try to edit and save vista poo's itself!
Reply
Old Jun 26, 2009 | 01:25 AM
  #479  
onboost's Avatar
Evolving Member
 
Joined: Jun 2007
Posts: 109
Likes: 0
From: New Zealand
Originally Posted by tephra
save the .xml someplace else - then copy it manually into the ecuflash directory.

i think if you try to edit and save vista poo's itself!
you the man
Reply
Old Jun 26, 2009 | 07:52 AM
  #480  
crcain's Avatar
Evolved Member
 
Joined: Oct 2002
Posts: 2,788
Likes: 1
Originally Posted by GST Motorsports
Raises hand!

Yes I have.
Thank you! That is all I wanted to hear. I guess something was wrong with my setup OR the addresses SiC gave me for the 52360016 rom were wrong. I'm going to switch to the 52360018 AND use beta15 and see if I can be successful.
Reply



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