Does this log seem normal?
Does this log seem normal?
I'm having trouble interpreting much in my logs from Evoscan. Can someone take a look and see the numbers look normal? For example, LTFT seems to only go between 0-4.41. Is that normal? The boost numbers are definitely not correct. Thanks in advance for any info.
https://datazap.me/u/obiwan/37?log=0...-34&solo=16-18
https://datazap.me/u/obiwan/37?log=0...-34&solo=16-18
I'm having trouble interpreting much in my logs from Evoscan. Can someone take a look and see the numbers look normal? For example, LTFT seems to only go between 0-4.41. Is that normal? The boost numbers are definitely not correct. Thanks in advance for any info.
https://datazap.me/u/obiwan/37?log=0...-34&solo=16-18
https://datazap.me/u/obiwan/37?log=0...-34&solo=16-18
And normally, people take a log selecting the list that are preinstalled in the evoscan's 'Select ECU' dropdown to fits your evox's year and market(eg. 'Golden 2011 USDM v2 EVOX', 'RAX Fast logging - Rev E EVOX', etc). Is that not enough for you?
You're giving me too much credit. I wouldn't know where to start creating my own logging items. This is straight out of the box setup. I have a 2014 USDM EVOX GSR. I've tried Golden 2013, RAX Fast, etc. But the only one that seems to provide numbers that are remotely reasonable is the defualt EVOX CAN MUTIII. So, If you have experience with the logs, can you at least look at the LTFT, STFT, and O2 and tell me if those numbers are remotely in line with normal, or if you see abnormalities. Just ignore the other items if you don't know what they are. Alternatively, help me figure out why I can't find an ECU in the list the provides normal output. Does anyone else have a 2014 that can provide feedback? The prior owner swapped out the ECU, so maybe it's for another year? I'll connect with ECUFlash again and see if it can help me identify the year of the ECU. Finally, I just bought the car and it has a LOT of problems, so I appreciate your patience as I try to unmask layers of issues and unknowns. If I could do it over again, I'm not sure I would purchase the car.
Last edited by craigebaker1; Mar 15, 2020 at 08:18 AM.
> The prior owner swapped out the ECU, so maybe it's for another year?
I think that is possible. Can you save the rom by ecuflash and attach it to your post? That way we can see your current rom id. If you can't attach because it's a tuned rom, save the rom by ecuflash and check the id by yourself. The rom id is 4 bytes from 0x5002a. ( If you cannot read / save the rom with ecuflash, the previous owner may have tuned and the ecu is locked. )
I recommend RAX FAST LOGGING. To use this, you need to apply RAX Patch to your rom. Alternatively, logging in mode 23 is recommended. In both cases, you need to apply a patch to enable mode23.
I think that is possible. Can you save the rom by ecuflash and attach it to your post? That way we can see your current rom id. If you can't attach because it's a tuned rom, save the rom by ecuflash and check the id by yourself. The rom id is 4 bytes from 0x5002a. ( If you cannot read / save the rom with ecuflash, the previous owner may have tuned and the ecu is locked. )
I recommend RAX FAST LOGGING. To use this, you need to apply RAX Patch to your rom. Alternatively, logging in mode 23 is recommended. In both cases, you need to apply a patch to enable mode23.
> The prior owner swapped out the ECU, so maybe it's for another year?
I think that is possible. Can you save the rom by ecuflash and attach it to your post? That way we can see your current rom id. If you can't attach because it's a tuned rom, save the rom by ecuflash and check the id by yourself. The rom id is 4 bytes from 0x5002a. ( If you cannot read / save the rom with ecuflash, the previous owner may have tuned and the ecu is locked. )
I recommend RAX FAST LOGGING. To use this, you need to apply RAX Patch to your rom. Alternatively, logging in mode 23 is recommended. In both cases, you need to apply a patch to enable mode23.
I think that is possible. Can you save the rom by ecuflash and attach it to your post? That way we can see your current rom id. If you can't attach because it's a tuned rom, save the rom by ecuflash and check the id by yourself. The rom id is 4 bytes from 0x5002a. ( If you cannot read / save the rom with ecuflash, the previous owner may have tuned and the ecu is locked. )
I recommend RAX FAST LOGGING. To use this, you need to apply RAX Patch to your rom. Alternatively, logging in mode 23 is recommended. In both cases, you need to apply a patch to enable mode23.
thanks for the guidance. Can I do all this with the fuel pump disabled? I have the TB and intake manifold off to make sure those gaskets aren’t leaking. Just found out they were brand new, so also wondering if I can tighten back down or if I need to completely replace now since I I tightened them.
There are two things you need to do:
1. Save your rom with ecuflash and check rom id. Then post the rom id, your evox market(USDM?), year(2009? 2010?). (If you cannot check the rom id, attach the rom to your post.)
2. Set mode 23 to your rom and flash(write) it to your ECU. (If you use RAX FAS LOGGING, also set the RAX Patch. These are required for logging with evoscan.
If you don't know how to do it, ask a question.
Trending Topics
Okay. Rax patches loaded and using EvoScan 2.8 for reading codes and v2.9 for logging. Please take a look at my logs below at idle. I have a wandering AFR problem at idle and cruise I've been fighting forever. I've replaced the front O2, boost tested, smoke tested, reran EBCS and WG lines, fixed exhaust leaks, checked fuel pressure, sent injectors to ID for cleaning and flow testing, cleaned MAF sensor, tightened fuel line connections, hmm, probably missing something but this is the majority of what I've done.
Thanks in advance for reviewing my logs and providing feedback!
https://datazap.me/u/obiwan/log-1586...5-6-9-17-25-30
Thanks in advance for reviewing my logs and providing feedback!
https://datazap.me/u/obiwan/log-1586...5-6-9-17-25-30
Last edited by craigebaker1; Apr 25, 2020 at 07:28 AM.
It is possible that there is something wrong with the throttle body, unstable TPS might be the cause of unstable AFR.
Did you check or replace your throttle body?
I recently took the throttle body and intake manifold off to inspect for leaks. I cleaned the throttle plate, but probably not thoroughly. I'm going to replace the intercooler pipe that connects to the TB this week and will inspect and clean the TB at that time. What should I look for that could be failing on the TB?
I recently took the throttle body and intake manifold off to inspect for leaks. I cleaned the throttle plate, but probably not thoroughly. I'm going to replace the intercooler pipe that connects to the TB this week and will inspect and clean the TB at that time. What should I look for that could be failing on the TB?
I've heard that if someone who doesn't know how to clean an electrical controlled throttle body clean it, it can be destroyed.
Looking at your chart, what seemed to work with AFR was STFT, not TPS. (I misunderstood the color of the curves.) As you mentioned the TPS continues fine vibratation. The STFT looks normal as long as seeing its curve.
Last edited by crimson red; Apr 27, 2020 at 09:06 AM.
Am not an expert, I had similar issue when I cleaned my Throttle body and it acted up for sometime till I realized I have to do the throttle body relearning procedures, check this thread
https://www.evolutionm.net/forums/ev...lls-start.html
https://www.evolutionm.net/forums/ev...lls-start.html
Thread
Thread Starter
Forum
Replies
Last Post







