i download EvoScanv2.7Beta1 to see if it would solve aem wideband problem. but i still get same error. on hyper terminal the values are straight forward. nothing wrong their. mitsulogger works.


2009-08-17,07:31:01.79687,LogDataItems WDB AEM InputStream:15.2
15.2
15.2
152
,Input string was not in a correct format.,,
2009-08-17,20:16:42.26562,LogDataItems WDB AEM InputStream:.6
14.6
14.6
14.1
1.1
,Input string was not in a correct format.,,
2009-08-17,20:17:34.04687,LogDataItems WDB AEM InputStream:
15.4
!5.4
,Input string was not in a correct format.,,
2009-08-17,20:17:57.14062,LogDataItems WDB AEM InputStream:
14.5
!4.5
,Input string was not in a correct format.,,
2009-08-17,20:18:12.26562,LogDataItems WDB AEM InputStream:
14.7
14.7
14.7
14&7
14,Input string was not in a correct format.,,
2009-08-17,20:20:02.85937,LogDataItems WDB AEM InputStream:12.4
12&4
12,Input string was not in a correct format.,,
2009-08-17,20:44:47.26562,LogDataItems WDB AEM InputStream:18.3
!8.3
18,Input string was not in a correct format.,,
2009-08-17,20:45:03.40625,LogDataItems WDB AEM InputStream:15.0
15.0
14.1
14.1
14.1,Input string was not in a correct format.,,
2009-08-17,20:46:58.96875,LogDataItems WDB AEM InputStream:14.9
14.9
14.9
14.7
14.7,Input string was not in a correct format.,,

 

So are you only having problems logging the uego with the touchscreen unit? Do you have problems with a laptop? Do you use a serial to USB cable?

 

yeah this is with the car pc... i am using serial port.. pin 2 and pin 5

 

Hey hamish,
is there a way to save the date/time format on the gps logger? My unit keeps defaulting to 12:00pm Jan, 2003.

 

Beta1 fixed the AEM issue I was having. I'm running a laptop with Vista SP1 with a Mode23 X.

 

would an evo 7 suffice? id be willing to help if you could aslo help me get my evoscan/cable to comunicate with the ayc/acd system

 

yes make sure its charged up and the bottom switch remains on.
then under option set date and time
but if you have to turn the switch off then the date is lost

 

I re wrote the AEM logger code from scratch, and tested it on an AEM with EvoX mode 23 and OpenPort2.0
EvoScanv2.7Beta2

Give it a try out now... The reason it changed from v2.5 to v2.6 is because I had to support Vista64bit users as well, so now that I have rewritten it, please check it out, and give me as much feedback as you can. cheers, Hamish.

 

xbox4414, can you please check the v2.7 beta2 (see post above), see if its still ok for you, since I rewrote the AEM code.

Aman: also try Windows version of EvoScan v2.7 beta2 (see post above), but looking at your logs: you AEM device is not wired well enough. hundreds of your AEM readings are corrupt "14&7" <-- that looks like a loose ground wire or something, do you see those sorts of characters in Terminal too? either way the new version will be better because it picks up the first AEM values coming down the line now.

The new version is very responsive when I compared it to the AEM display device now, its great.

 

Hamish,

Could you check your support tickets please? I lost email from a server crash so no longer have my serial # and I put in a support ticket last week...

Thanks!

 

Yeah I'm away today, otherwise I clear them each day. I'll get back to you.

 

I have logged using Mode23 2008 JDM EVOX (Aus spec car) using 2.6 and find my RPM log samples have repetative readings? Any ideas.
Thanks.

 

yes i do see different char in terminal too.. ground are good bolted right to chassis.
i tested EvoScan v2.7 beta2 it log fine for few seconds then it slow down then stop freezes up and it will stop and will try to reconnect then them same thing again . only when logging Aem but everything else works... no problem their..

with the engine not running aem logging work fine. engine running it doesn't. is it possible that aem controller is messed up

 

Hamish, I have not gotten a chance to check beta2. Beta1 was running fine for me. I'll check beta2 tomorrow.

-Ray

 

HOLY ****!!! THIS I WANT!

subscribed