Evoscan and Serial UEGO problem!
May 19, 2011, 02:25 AM
#1
Evolved Member
Thread Starter
iTrader: (4)
Join Date: Jan 2009
Location: Toronto, Canada
Posts: 578
Likes: 0
Received 0 Likes
on
0 Posts
Evoscan and Serial UEGO problem!
So here I go...
I have the AEM Inline Wideband UEGO (with Serial output) - http://www.aemelectronics.com/engine...nline-uego-50/ and http://www.aemelectronics.com/Images...%2030-2310.pdf
I have the serial output set up - tested in Hyperterminal but using 19200, instead of 9600 as per information on this thread (http://forums.nasioc.com/forums/show....php?t=2171742). With 9600 I'm getting gibberish symbols. Where as 19200 I am getting coherent numbers and information.
Using the AEM Serial Software found (http://forum.aempower.com/forum/index.php?topic=26370.0) I am able to display a valid AFR reading and get logs/values.
However in the current form of Evoscan I believe it uses the old "9600" setup which works with particular models. The one I have uses the "19200" bits per second value. Is there a way I can tweak it internally? Or have it tweaked or settings for it to be adjusted?
In evoscan, as is I get the following error - The I/O operation has been aborted because of either a thread exit or an application request.
From: http://www.romraider.com/forum/viewt...t=7207&start=0
Not sure if the code he posted has any relevant information for me/us
Also, I noticed that the sensor takes values as lambda and in the case of the AEM software gauge thing. It converts it to AFR.
Sample:
I have the AEM Inline Wideband UEGO (with Serial output) - http://www.aemelectronics.com/engine...nline-uego-50/ and http://www.aemelectronics.com/Images...%2030-2310.pdf
I have the serial output set up - tested in Hyperterminal but using 19200, instead of 9600 as per information on this thread (http://forums.nasioc.com/forums/show....php?t=2171742). With 9600 I'm getting gibberish symbols. Where as 19200 I am getting coherent numbers and information.
Using the AEM Serial Software found (http://forum.aempower.com/forum/index.php?topic=26370.0) I am able to display a valid AFR reading and get logs/values.
However in the current form of Evoscan I believe it uses the old "9600" setup which works with particular models. The one I have uses the "19200" bits per second value. Is there a way I can tweak it internally? Or have it tweaked or settings for it to be adjusted?
In evoscan, as is I get the following error - The I/O operation has been aborted because of either a thread exit or an application request.
From: http://www.romraider.com/forum/viewt...t=7207&start=0
Not sure if the code he posted has any relevant information for me/us
Also, I noticed that the sensor takes values as lambda and in the case of the AEM software gauge thing. It converts it to AFR.
Sample:
Time,Lambda,TC1,TC2,
0,1.011,Ready,No-errors,
1,1.011,Ready,No-errors,
2,1.013,Ready,No-errors,
3,1.010,Ready,No-errors,
4,1.013,Ready,No-errors,
5,1.014,Ready,No-errors,
6,1.015,Ready,No-errors,
7,1.017,Ready,No-errors,
8,1.018,Ready,No-errors,
9,1.020,Ready,No-errors,
0,1.011,Ready,No-errors,
1,1.011,Ready,No-errors,
2,1.013,Ready,No-errors,
3,1.010,Ready,No-errors,
4,1.013,Ready,No-errors,
5,1.014,Ready,No-errors,
6,1.015,Ready,No-errors,
7,1.017,Ready,No-errors,
8,1.018,Ready,No-errors,
9,1.020,Ready,No-errors,
May 19, 2011, 06:33 PM
#2
Evolving Member
Join Date: Apr 2011
Location: West Seneca NY
Posts: 125
Likes: 0
Received 0 Likes
on
0 Posts
I have the AEM UEGO A/F Gauge so not sure if the IN Line unit works the same but did you
select the AEM UEGO in the drop down WideBand(WDB) menu?
Also how is the inline serial terminated?
Does it already have a RS 232 connector?
Are you using an USB to RS 232 adaptor? If so make sure it has the FTDI chip set and not the Prolific.
Athanasios
select the AEM UEGO in the drop down WideBand(WDB) menu?
Also how is the inline serial terminated?
Does it already have a RS 232 connector?
Are you using an USB to RS 232 adaptor? If so make sure it has the FTDI chip set and not the Prolific.
Athanasios
May 28, 2011, 06:02 PM
#3
Evolving Member
iTrader: (2)
Join Date: Jan 2009
Location: Arizona
Posts: 198
Likes: 0
Received 0 Likes
on
0 Posts
Same issue here laksman91 - Evoscan does not seem compatible with the AEM UEGO Inline. I sumibtted a ticket to Hamish - I'd be happy to tinker with the source code of Evoscan to make it work (even sign an NDA if he wanted). I just want Evoscan to work with the inline UEGO. 
Jul 8, 2011, 04:18 AM
#4
thanks MikeJones, who chatted to me on skype, and we tested out the new EvoScan v2.9 on AEM Uego 115200 xwifi usb virtual com port edition, and it worked sweet.
I just need someone with a AEM inline 19200 wideband to test it. please email me wideband at evoscan.com if you have one of those.
thanks,
Hamish.
I just need someone with a AEM inline 19200 wideband to test it. please email me wideband at evoscan.com if you have one of those.
thanks,
Hamish.
Aug 7, 2011, 04:01 PM
#5
Evolving Member
iTrader: (2)
Join Date: Jan 2009
Location: Arizona
Posts: 198
Likes: 0
Received 0 Likes
on
0 Posts
thanks MikeJones, who chatted to me on skype, and we tested out the new EvoScan v2.9 on AEM Uego 115200 xwifi usb virtual com port edition, and it worked sweet.
I just need someone with a AEM inline 19200 wideband to test it. please email me wideband at evoscan.com if you have one of those.
thanks,
Hamish.
I just need someone with a AEM inline 19200 wideband to test it. please email me wideband at evoscan.com if you have one of those.
thanks,
Hamish.
Aug 8, 2011, 03:05 AM
#6
what custom values would you put in the serial settings? it is the data analyst parsing of the byte stream that changes, not the custom values. so its really is best just to contact me direct on skype and get a working version within a few hours.
Thread
Thread Starter
Forum
Replies
Last Post
sirchumpalot
Evo X Engine Management / Tuning Forums
3
Aug 6, 2014 01:19 PM
