Hello to all tuning gurus...

I'm getting pretty frustrated in attempting to get a solid tune for my evo (Evo is a 2010 GSR). I was tuned by Ivey but decided to go with an etune after I installed some parts. Everything is good and solid except for my inability to log my AFR.

Im running evoscan 2.9. I have an AEM UEGO wideband. I initially just thought I could log via rear O2 according to this thread: http://www.evoxforums.com/forums/showthread.php?t=18511 ...I had everything hooked up properly and ready to go, but we couldnt get evoscan to read an AFR ... according to my tuner, the request ID for 2010s cant be identified to use for logging

So im like ****, ok then.... so I hook up a serial connection following this thread: http://www.evoxforums.com/forums/showthread.php?t=21747

I then ordered and have the keyspan adaptor and software installed from this thread: http://www.evoxforums.com/forums/showthread.php?t=16567

I select the correct com port, and I try the three different UEGO versions in evoscan (idk what the difference is) ... but the WDB parameter STILL reads just 0 (zero) when attempting to log

so wtf.

i want to get this sorted out but am running out of ideas.

anyone have any info?? please help

 

that's odd

 

Ok it's fixed now. For those interested, here's what we did (me any my friend who knows computer stuff...mostly just my friend who did all the work lol) :

We opened the raw serial port using PuTTY (could have used HyperTerminal as well), and saw the proper output of the AFR from the gauge. This told us that the AFR is being reported from the gauge... so the gauge is good.

Next, we opened Evoscan and saw that it was displaying 0 in the external wideband column.

Then, we noticed a little error at the bottom:
Code:

AEM Error: Conversion from string "14.2" to type 'Double' is not valid

So, why would Evoscan think that 14.2 cannot be converted to a Double (basically a decimal number for all you non-programmers)... and why is his Windows clock in 24hr format? As it turns out, in his Regional Settings his location was set to Luxembourg. Apparently, in Luxembourg, they use commas as the decimal separator, not a period. Changed it back to the US and all is well.

Cheers