The only "bug" I have with 2.7 is for some reason it won't display or clear OBDII codes... I already sent a trouble ticket to Hammish... I am glad that I still have OBDII Scantech installed!

 

Ah. That won't be an issue for a while. Good to know.

 

That's strange because I'm using 2.6 right now and it works perfectly AEM Uego...

 

If you still need a copy of V2.5 pm me your email address

 

I have 2.5 for ya. Just IM me.

 

Very strange. Jay @ boosted tuning says he's heard of this problem before.
When I log, it works for a split second then stays at the same AFR. I upgraded to 2.7 and the problem is solved.
However, I don't like the idea of not being able to read/clear codes. Never know when I may need to do that.
Jay: I'll hit you up, today, for 2.5.

 

Kaj, send me your e-mail and I will send you OBDII scantech...

 

done.

 

and done

 

you da man. are you this nice to everyone, or is it just 'cause i've bought 2 AEM serial wires? LOL

 

Does this work with the AEM Inline UEGO?

 

I'm not sure why everyone buys those connectors to solder to. I just used an old serial cable I had lying around and soldered directly to the pins on the male side. Then I bought a serial > usb 1 foot converter (ideally its best to keep this short) and connected it to my laptop.


Btw has anybody figured out how to fix the evoscan 2.7 logging for the UEGO? I can log it with mitsulogger but evoscan shows ~10.7 all the time...

 

EvoScan v2.8 works great with AEM UEGO for this. Log a support call if its still an issue, I can connect remotely to take a look.

what about connecting the AEM directly to the ecu, less usb cables then?
more links at the bottom of this page:
http://www.evoscan.com/technical-veh...ideband-review

 

When does 2.8 come out?

 

<<<<<<<<<<<<<<<<do it again lol