Logging Issues with Tephra V7 94170715
Ok guys, first off sorry if this has been talked about before or for the fact that i might be retarded and it might be a simple fix that's out there somewhere. I searched for the info but some threads have hundreds of pages and i'm not sure i have the time to look through all of them.
A month ago i uploaded the tephra v7 94170715 off of the first page from the original thread. It's working great but i'm having issues logging some stuff and using Map tracer.
After i loaded the V7map i did a wot pull and tried using maptracer with evoscan 2.6 beta 6 (didn't know there were new ones out). it logged some stuff but they were funky. The values would would only show on the 0 rpm cell but did follow the load axis. I made sure that the byte rate was the same under ecuflash and the load value in evoscan which it was, at 1.2. So then i downloaded version 2.8.0005 and tried the same thing. still nothing. my boost is also not logging properly. none of them, i know there is about three of them. Interesting fact i found was that they all use the same request ID but the formulas differ. Then today i tuned my brothers Evo X with the new version of evoscan and map tracer worked just fine.
so my questions are,
How do i log boost properly with V7 and rom ID listed above?
do i have to be logging 2byte in order for Maptracer to work and that's why my brothers works since he's on mode23?
or should i be using evoscan version 2.7 for this to work?
are there any other changes i should know about that i need to make?
ps. i tried to follow all of the instructions i have found for uploading this, I don't think i missed anything but maybe i did along the way. Thanks for any help!
A month ago i uploaded the tephra v7 94170715 off of the first page from the original thread. It's working great but i'm having issues logging some stuff and using Map tracer.
After i loaded the V7map i did a wot pull and tried using maptracer with evoscan 2.6 beta 6 (didn't know there were new ones out). it logged some stuff but they were funky. The values would would only show on the 0 rpm cell but did follow the load axis. I made sure that the byte rate was the same under ecuflash and the load value in evoscan which it was, at 1.2. So then i downloaded version 2.8.0005 and tried the same thing. still nothing. my boost is also not logging properly. none of them, i know there is about three of them. Interesting fact i found was that they all use the same request ID but the formulas differ. Then today i tuned my brothers Evo X with the new version of evoscan and map tracer worked just fine.
so my questions are,
How do i log boost properly with V7 and rom ID listed above?
do i have to be logging 2byte in order for Maptracer to work and that's why my brothers works since he's on mode23?
or should i be using evoscan version 2.7 for this to work?
are there any other changes i should know about that i need to make?
ps. i tried to follow all of the instructions i have found for uploading this, I don't think i missed anything but maybe i did along the way. Thanks for any help!
Last edited by criptballer; May 8, 2011 at 11:58 AM.
Some Evoscans act differently and you may have to go to a newer or older version sometimes. Also uninstalling them and reinstalling them works.
As for logging boost. Do you have a 3bar map sensor(JDM Map sensor)? that is what the evo8/9s need in order to log boost via evoscan. Evo10s can log boost straight from the factory since they already have a 3bar map sensor.
As for logging boost. Do you have a 3bar map sensor(JDM Map sensor)? that is what the evo8/9s need in order to log boost via evoscan. Evo10s can log boost straight from the factory since they already have a 3bar map sensor.
Some Evoscans act differently and you may have to go to a newer or older version sometimes. Also uninstalling them and reinstalling them works.
As for logging boost. Do you have a 3bar map sensor(JDM Map sensor)? that is what the evo8/9s need in order to log boost via evoscan. Evo10s can log boost straight from the factory since they already have a 3bar map sensor.
As for logging boost. Do you have a 3bar map sensor(JDM Map sensor)? that is what the evo8/9s need in order to log boost via evoscan. Evo10s can log boost straight from the factory since they already have a 3bar map sensor.
in that case. should i just go with an omni 4bar sensor since i plan on runing 30 plus?
I will find the link about the 3bar map sensor... hold up.
EDIT: the 3bar only reads up to 32psi.
Last edited by LGshow19; May 8, 2011 at 12:59 PM.
Heres the Link:
https://www.evolutionm.net/forums/ec...tructions.html
Also, the 3bar sensor only goes too 32psi, so go head and get the Omni 4 bar.
https://www.evolutionm.net/forums/ec...tructions.html
Also, the 3bar sensor only goes too 32psi, so go head and get the Omni 4 bar.
Thanks for the help man. Do you know if you can use the regular WGDC type of boost control with an omni 4 bar? i was reading on the V7 thread but they talk about direct boost through the ecu and i'm not familiar with it but was wondering if i would be able to control it the old way with wgdc.
Trending Topics
Thanks for the help man. Do you know if you can use the regular WGDC type of boost control with an omni 4 bar? i was reading on the V7 thread but they talk about direct boost through the ecu and i'm not familiar with it but was wondering if i would be able to control it the old way with wgdc.
Thread
Thread Starter
Forum
Replies
Last Post




