Evo IX - EvoScan Datalogging Issues
#1
Evolved Member
Thread Starter
iTrader: (52)
Join Date: Aug 2007
Location: SoCal
Posts: 1,200
Likes: 0
Received 0 Likes
on
0 Posts
Evo IX - EvoScan Datalogging Issues
Hello,
My wife and I are the proud owners of an Evo IX SE. Up until last weekend, she had been sitting in our garage collecting dust for ~2 1/2 years. Reason? Long story. Bottom line is there wasn't anything wrong with her as she was simply missing some vital parts (turbo, radiator, etc.). Anyways, she is back up and running from the stand-point that we can "limp" her around the block. She is running a basemap for our current mod list (see signature link) and will be fully tuned within a month or so.
In the mean time I wanted to do some datalogging to make sure that she can make the 1 1/2 hour trip to the tuner (Reese Tuning). The primary change between now and when she last ran is engine management--she is now on the OEM ECU vs. the prior AEM EMS. Anyways, when trying to do some datalogging I am unable to see values pertaining to fuel trim. This concerns me as I have no clue what the issue(s) is(are) (mechanical, electrical, etc.).
Any thoughts?
My wife and I are the proud owners of an Evo IX SE. Up until last weekend, she had been sitting in our garage collecting dust for ~2 1/2 years. Reason? Long story. Bottom line is there wasn't anything wrong with her as she was simply missing some vital parts (turbo, radiator, etc.). Anyways, she is back up and running from the stand-point that we can "limp" her around the block. She is running a basemap for our current mod list (see signature link) and will be fully tuned within a month or so.
In the mean time I wanted to do some datalogging to make sure that she can make the 1 1/2 hour trip to the tuner (Reese Tuning). The primary change between now and when she last ran is engine management--she is now on the OEM ECU vs. the prior AEM EMS. Anyways, when trying to do some datalogging I am unable to see values pertaining to fuel trim. This concerns me as I have no clue what the issue(s) is(are) (mechanical, electrical, etc.).
Any thoughts?
#2
Evolved Member
iTrader: (10)
If the rear o2 periphery bits are disabled then fuel trims won't log, I don't remember off hand which one it is though.
If you want, send me your map and I'll compare it with mine, as my trims log properly. Should at least allow you to rule out anything software-related.
If you want, send me your map and I'll compare it with mine, as my trims log properly. Should at least allow you to rule out anything software-related.
#3
Evolved Member
Thread Starter
iTrader: (52)
Join Date: Aug 2007
Location: SoCal
Posts: 1,200
Likes: 0
Received 0 Likes
on
0 Posts
If the rear o2 periphery bits are disabled then fuel trims won't log, I don't remember off hand which one it is though.
If you want, send me your map and I'll compare it with mine, as my trims log properly. Should at least allow you to rule out anything software-related.
If you want, send me your map and I'll compare it with mine, as my trims log properly. Should at least allow you to rule out anything software-related.
#7
Evolved Member
Thread Starter
iTrader: (52)
Join Date: Aug 2007
Location: SoCal
Posts: 1,200
Likes: 0
Received 0 Likes
on
0 Posts
When putting the turbo back on, I found out that I didn't have a front O2 sensor. I ended up buying a used OEM front O2 sensor from a local member. I immediately ran into clearance issues as the top of the O2 sensor was hitting the wastegate actuator. We have the Invidia O2 housing, and the sensor placement is horrible! Anyways, with that OEM sensor we were still unable to log fuel trims and STFT. So, I thought the sensor was bad and ended up buying a Denso (who apparently makes the OEM sensor) O2 sensor. This sensor is slightly shorter than the OEM one, so there was no more clearance issues. I then tried to datalog and experienced the same issues. I decided to check out the wiring going to the OEM ECU. I saw a purple wire pinned into location 71 (front O2 sensor) and learned that that was the Zeintronix wideband O2 sensor, which is located in the test pipe. I saw a white wire not connected to anything, and figured it was for the front O2 sensor. So, I removed the purple wire and plugged in the white wire (into 71). I noticed another white wire going into 73 (rear O2 sensor). I tried datalogging again and had zero changes. So, I thought that the white wire going into 73 might actually be for the front O2 sensor (process of elimination right?). I removed the white wires from 71 and 73 and plugged the wire from 73 into 71 thus leaving the wire originally from 73 unconnected. Confusing much? Anyways, no change.
Last edited by 1QYK9; Aug 28, 2011 at 07:45 AM.
Thread
Thread Starter
Forum
Replies
Last Post