Logging AEM wideband on Evoscan2.7
#1
Evolving Member
Thread Starter
iTrader: (15)
Join Date: Jul 2008
Location: Buffalo, NY
Posts: 170
Likes: 0
Received 0 Likes
on
0 Posts
Logging AEM wideband on Evoscan2.7
I'm trying to log my AFR's with my AEM wideband 02 sensor. I have it wired through the rear oxygen sensor on my Evo 8 ecu.
I wired everything up correctly and now I'm trying to figure out how to modify Evoscan 2.7 to accept the modification. The current FAQ wants me to put an xml bit into the "Data.xml" file. This file does not exist on the new v2.7 of evoscan.
Does anyone have any information to steer me in the correct direction? I cannot downgrade for 2.5 or 2.6 for some reason. Also, I hear you need to modify 3 locations on the mut table instead of just mut12.
Please help...
I searched my *** off.
Thanks,
Alex
I wired everything up correctly and now I'm trying to figure out how to modify Evoscan 2.7 to accept the modification. The current FAQ wants me to put an xml bit into the "Data.xml" file. This file does not exist on the new v2.7 of evoscan.
Does anyone have any information to steer me in the correct direction? I cannot downgrade for 2.5 or 2.6 for some reason. Also, I hear you need to modify 3 locations on the mut table instead of just mut12.
Please help...
I searched my *** off.
Thanks,
Alex
#3
Evolved Member
iTrader: (33)
Join Date: Jul 2002
Location: Raleigh, Transplanted from Toronto, Canada
Posts: 5,313
Likes: 0
Received 1 Like
on
1 Post
This forum moves a little slow at times. Try to pm some of the gurus (mrfred, etc). Does it work fine on the previous versions of evoscan? If so then you might to contact Hamish (he maintains evoscan) directly from the evoscan website. He does get on here but I don't think it's often.
#4
Evolving Member
iTrader: (3)
You just need to create new (or modify existent) string in Evoscan for appropriate request (can be found in ROM in MUT table where 8409 is) and input appropriate formula for calculations (based on the WBO2 calibrations, keep in mind ECU sees not volts, but values in the range 0-255, when evaluating your formula). That should complete the deal.
At least this approach works like a champ in my EDM EvoIX.
At least this approach works like a champ in my EDM EvoIX.
#5
Evolving Member
iTrader: (1)
Join Date: May 2008
Location: Wausau WI
Posts: 128
Likes: 0
Received 0 Likes
on
0 Posts
The MUT table should be fine. What he is dealing with is that the instructions for logging his wideband point to the procedure for v2.6 but Hamish nixed the data.xml file in favor of a new system. The problem with getting help is not many people have played with v2.7 yet because it is new and most people already have their logging set up well.
Honestly the best place to look would be the help tab in evoscan. Normally that would be a sarcastic RTFM answer but in this case it really could be the most helpful.
Honestly the best place to look would be the help tab in evoscan. Normally that would be a sarcastic RTFM answer but in this case it really could be the most helpful.
#6
Evolving Member
Thread Starter
iTrader: (15)
Join Date: Jul 2008
Location: Buffalo, NY
Posts: 170
Likes: 0
Received 0 Likes
on
0 Posts
I'd like to even downgrade to 2.5 or 2.6 so the old xml could work, but as of right now i have no way to. The serial I have is for 2.7 and only 2.7.
I would try and create a new xml string but at the same time, i'm not too good at any of this at all. So if anyone could possibly walk me through the process that'd be immensely helpful.
I would try and create a new xml string but at the same time, i'm not too good at any of this at all. So if anyone could possibly walk me through the process that'd be immensely helpful.
#7
Evolving Member
Thread Starter
iTrader: (15)
Join Date: Jul 2008
Location: Buffalo, NY
Posts: 170
Likes: 0
Received 0 Likes
on
0 Posts
Actually to be honest with you guys, on my version of 2.7 I have a category in my logger labled: "WB02" under the description of "WB02" it says: "You can wire in an external sensor into your ecu to get this value."
Maybe 2.7 has this feature built in?
Any idea how I can access this guru's? I see it has a location, however I do not know what that means or how I should get at it.
If we can figure this out then I'm sure it'll avoid stupid questions like this in the future.
Maybe 2.7 has this feature built in?
Any idea how I can access this guru's? I see it has a location, however I do not know what that means or how I should get at it.
If we can figure this out then I'm sure it'll avoid stupid questions like this in the future.
Trending Topics
#8
Evolving Member
iTrader: (1)
Join Date: May 2008
Location: Wausau WI
Posts: 128
Likes: 0
Received 0 Likes
on
0 Posts
You should just be able to change the eval field in the WBo2 to the equation that you're using for evaluating the sensor voltage. The variable x refers to the value returned by the ecu to evoscan. After that also change the RequestID field to the RequestID used by the input that you've hijacked, and in this case that should be the rear o2 sensor so simply copy that request for the WBo2 field.
This way to do it has (nearly?) always been an option, I do not know if there is also a configuration file that can easily be edited with completed logging definitions.
This way to do it has (nearly?) always been an option, I do not know if there is also a configuration file that can easily be edited with completed logging definitions.
Thread
Thread Starter
Forum
Replies
Last Post
Cbr1000love
General Engine Management / Tuning Forum
0
Jan 30, 2016 11:57 AM
evo4mad
ECU Flash
1880
May 5, 2015 06:22 PM