Evo X Logging
#466
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.
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.
#467
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
https://www.evolutionm.net/forums/ev...ml#post7176324
evo4mad describes how to install the beta like this:
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.
- You still need to install EvoScan v2.5 full registered version first. Available here.
#468
Evolved Member
iTrader: (1)
Join Date: Jun 2008
Location: Kanagawa, Japan
Posts: 1,018
Likes: 0
Received 0 Likes
on
0 Posts
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.
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.
#469
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.
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.
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?
#470
Evolved Member
iTrader: (1)
Join Date: Jun 2008
Location: Kanagawa, Japan
Posts: 1,018
Likes: 0
Received 0 Likes
on
0 Posts
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?
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?
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.
#471
I will try beta15 in a day or two, but I'm simply trying to get clarication on conflicting methods of install of beta14.
#473
Evolved Member
iTrader: (9)
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.
#474
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!
#477
Evolving Member
Join Date: Jun 2007
Location: New Zealand
Posts: 109
Likes: 0
Received 0 Likes
on
0 Posts
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
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
#479
Evolving Member
Join Date: Jun 2007
Location: New Zealand
Posts: 109
Likes: 0
Received 0 Likes
on
0 Posts
#480