 |
|
Jul 10, 2009, 09:39 AM
|
#1
|
|
Evolved Member
Personal Sales Rating: ( 9)
Join Date: Jun 2003
Location: Edmonton, Alberta CANADA
Posts: 1,251
Drives: 2006 EVO IX
|
EvoScan + Logging AEM UEGO = Arghh!!!
Okay so im ready to pull my hair out...
Im trying to datalog my car with wideband but im not having any luck and get fully annoyed/frustrated in the process. FYI, i have searched via google and evom, stayed up till 1:30am and no dice!
Im getting this error...
Info: Initialize Vehicle ECU...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Info: Waiting for INIT Response...
Info: ECU ID: XXXX
Info: Connection successful...
Error: Object reference not set to an instance of an object.
Info: Datalogger Ended.
Apparently no one has any real solution except try a older version BUT I could not for the life of me find a freaking older version! Im using the new evoscan 2.6 beta, i think on my mac i have evoscan 2.5 but ive read ppl with 2.5 are having issues too. They say use like 2.2 or 2.3, i dunno....
I know the wideband is reading b/c I used terminal and im getting data stream (its pretty cool i gotta say) when i saw data stream coming i was like "perfect, k lets log and then ill see if i can see wideband" i plugged in the tatrix cable, that appeared on comport 5, i hit start and its like "link engaged" then BAM all of a sudden its like "link disengaged" and it shows the error
Im using a acer netbook, it has 3 USB ports (comport 5,6 and 7) . I know i have the right port cause I originally only plugged in the USB2Serial cable and it was on com port 7 and under the wideband i made sure to choose that port (there was a dot next to it to show i selected it)
Im ready to do Accessport lol!! Guru's please chime in!
__________________
EVOLUTION IX
|
|
Offline
|
|
Jul 10, 2009, 10:58 AM
|
#2
|
|
Newbie
Personal Sales Rating: ( 2)
Join Date: Mar 2007
Location: IL
Posts: 43
Drives: WW evo IX
|
I'm using the new evoscan and when I use it, it only logs for about 5-10 seconds... frustrating.
Yea where do you get the earlier version of evoscan??
__________________
AMS: LICP, MBC, Intake, 3" TBE = 322whp 315tq
+FP4R's=355whp 350tq
TEPHRA MOD
Last edited by awalk9905; Jul 10, 2009 at 11:48 AM.
|
|
Offline
|
|
Jul 10, 2009, 11:02 AM
|
#3
|
|
Evolved Member
Personal Sales Rating: ( 7)
Join Date: Sep 2006
Location: Palatine, IL
Posts: 1,754
Drives: Graphite Grey IX SE (88590015), '04 FZ1, Former: 35R Powered Eclipse GST, 6/4 TSi AWD, Bandit 600s
|
It looks like there is something wrong with your evoscan installation.
Try re-installing 2.5, then (if you want) make the upgrade to 2.6b11/14 and verify that your wideband menu settings are correct (both AEM is checked and the correct com port is selected).
Did you install 2.5 and then upgrade to 2.6 or just try to run 2.6 right off the bat? (which won't work)
__________________
Corn Fed 365hp/360tq - AMS FMIC, AMS LICP+UICP, AMS Front lower motor mount, Megan O2, Megan DP, Perrin HFC, Fujitsubo RM01A Cat-back, Walbro 255, RC 1200cc Injectors, GSC S1 Cams, Ghetto 3" intake +AMSoil EA Filter
- Tephra V6, JDM MAP, Direct boost ctl w/ AEM solenoid, AMS Tuned
- Pioneer DEH-P9790BT, 40GB iPod, 10W6V2, Alpine PDX-1.1000, Passport 8500 x50 Hardwired, AEM Tru-Boost (Guage only), Auto-dimming mirror, 35% Tint
|
|
Offline
|
|
Jul 10, 2009, 11:05 AM
|
#4
|
|
Evolved Member
Personal Sales Rating: ( 9)
Join Date: Jun 2003
Location: Edmonton, Alberta CANADA
Posts: 1,251
Drives: 2006 EVO IX
|
Quote:
Originally Posted by fostytou
It looks like there is something wrong with your evoscan installation.
Try re-installing 2.5, then (if you want) make the upgrade to 2.6b11/14 and verify that your wideband menu settings are correct (both AEM is checked and the correct com port is selected).
Did you install 2.5 and then upgrade to 2.6 or just try to run 2.6 right off the bat? (which won't work)
|
i d/l-ed it directly off the link the vendor gave me. Well a couple days ago b4 my wideband was hooked up I logged fine.
fostytou, are u using a AEM uego with evoscan?
__________________
EVOLUTION IX
|
|
Offline
|
|
Jul 10, 2009, 11:19 AM
|
#5
|
|
Evolved Member
Personal Sales Rating: ( 0)
Join Date: Mar 2008
Location: uk
Posts: 884
Drives: 2003 evo8 gsr jdm
|
hmmm i'm on 2.5 and LC1 gets booted off after 2mins or so too?
|
|
Offline
|
|
Jul 10, 2009, 03:44 PM
|
#6
|
|
Evolved Member
Personal Sales Rating: ( 9)
Join Date: Jun 2003
Location: Edmonton, Alberta CANADA
Posts: 1,251
Drives: 2006 EVO IX
|
anyone?
__________________
EVOLUTION IX
|
|
Offline
|
|
Jul 10, 2009, 03:51 PM
|
#7
|
|
Evolving Member
Personal Sales Rating: ( 6)
Join Date: Jan 2008
Location: Puerto Rico
Posts: 197
Drives: 2005 Evo 8
|
I am using XP with evoscan 2.5 and it works great with the AEM UEGO. I tried 2.6 and never got it to work, I think that you have to reinstall evoscan 2.5 again like "fostytou" suggested, remove evoscan 2.6 completely, remove all folders manually after you do the uninstall and try again. I am not using a USB to serial adapter, I have a serial port on my laptop so that may be something to look at, hope this helps.
__________________
2005 Rally Red Evo 8: Cobb TBE no cat, MR d/v, Perrin Intake kit, PPI LICP, BR UICP, BR Mini battery, JDM 3bar map, walbro 255
|
|
Offline
|
|
Jul 10, 2009, 04:06 PM
|
#8
|
|
Newbie
Personal Sales Rating: ( 1)
Join Date: Sep 2008
Location: Algonquin, IL (near chicago)
Posts: 65
Drives: EVO IX-SOLD, MKIV Supra
|
V2.6 is not logging my AEM UEGO either, it will read for a few seconds then just stay at 15.3. Im going back to 2.5
|
|
Offline
|
|
Jul 10, 2009, 04:06 PM
|
#9
|
|
Evolved Member
Personal Sales Rating: ( 27)
2005 Mitsubishi Lancer Evolution
Join Date: Jun 2007
Location: Oak Harbor, WA
Posts: 883
Drives: '05 Tarmac Black SSL VIII
|
Completely uninstall evoscan and your driver for the serial to USB in safe mode, reboot, install 2.5, and the serial to usb software. Make sure the serial to USB is set to com 2 or com3 or evoscan may not work properly.
__________________
FP Red*Greddy ProfecB Spec II*HKS TT*Nesei Short Route IC Piping*Synapse BOV*COMP 272s*Injen Intercooler*AFE Power Dry Filter*R/TErnie Intake*R/TErnie FULL 3" O2 housing with V-band*R/TErnie Modified DCsports 3" Down/Test/Flexpipe with V-Band*Greddy Ti-C Exhaust*255lph*Tein S-Techs*18" Volk LE-28s*Progress 25mm Rear Sway*Project Mu pads*JDM Tails*Cusco Heat Shield*Mishimoto Radiator hoses/Cap*ARC shift knob*Injector Dynamics 1000cc...
|
|
Offline
|
|
Jul 13, 2009, 04:52 PM
|
#10
|
|
Newbie
Personal Sales Rating: ( 2)
Join Date: Mar 2007
Location: IL
Posts: 43
Drives: WW evo IX
|
So how or where do you get 2.5?
__________________
AMS: LICP, MBC, Intake, 3" TBE = 322whp 315tq
+FP4R's=355whp 350tq
TEPHRA MOD
|
|
Offline
|
|
Jul 13, 2009, 05:21 PM
|
#11
|
|
Evolved Member
Personal Sales Rating: ( 1)
2008 Mitsubishi Lancer Evolution
Join Date: Jun 2008
Location: Kanagawa, Japan
Posts: 759
Drives: Lancer Evo X GSR
|
I used to have that problem until I replaced my Serial to USB adapter. Everything worked fine in Hyper Terminal but in Evoscan it didn't work. I now have a Keyspan adapter and all is working well.
|
|
Offline
|
|
Jul 14, 2009, 01:11 AM
|
#12
|
|
Evolving Member
Personal Sales Rating: ( 27)
Join Date: Sep 2007
Location: Vilseck
Posts: 111
Drives: Evo IX using up my fuel ration by the 15th of the month
|
I still have this same problem and never got my tune finished with Mellon. When I had an older version it worked but with the new version it does not. I asked the evoscan guys to give me an older version but never got one.
|
|
Offline
|
|
Jul 14, 2009, 01:17 AM
|
#13
|
|
Newbie
Personal Sales Rating: ( 0)
Join Date: May 2006
Location: LA
Posts: 53
Drives: EVO IX
|
I have had the same issues with evoscan 2.5 where it gets stuck in a loop while trying to connect to the ecu. it worked fine for a little while until i went click happy on all of the selectable fields (minus the wideband and things I dont have sensors for). I am in the middle of trying to see if the latest beta verison can clear up the issue.
|
|
Offline
|
|
Jul 14, 2009, 03:28 AM
|
#14
|
|
Evolved Member
Personal Sales Rating: ( 27)
2005 Mitsubishi Lancer Evolution
Join Date: Jun 2007
Location: Oak Harbor, WA
Posts: 883
Drives: '05 Tarmac Black SSL VIII
|
Here is an excellent write up for troubleshooting wideband logging...
Quote:
Originally Posted by bustin
Basically, you need to check EVERY part of your connection. Start from the beginning obviously and work your way to the serial -> usb...
Ok first. Make sure you have your gauge on. Keep it on while you are testing instead of turning it on and off. You will avoid testing stuff without your gauge on and getting super confused. Anyways, you need to check and see if your gauge is outputting the proper voltage. 15.0afr = roughly 2.30 volts. Ok, so your gauge is outputting signal? Cool. Thats a start.
Now after you connect your female serial adapter you need to check your voltage again. This will verify that you did indeed solder correctly and to the CORRECT PINS. If you are looking at the female serial adapter from the FRONT the pinage shown in the AEM manual IS 100% CORRECT.
( If you are hard wiring a cut cable like I did myself. The pinout colors that you will need are BROWN = DATA and your YELLOW = GROUND ) If you just soldered the pins and made a cable then thats great.
Moving on.... Now since we made a connection between our gauge output wiring and the ground we need to test this and make sure this is working correctly. The best way to test this is to go ahead and make sure your ground and your data connection are in place. For testing the adapter I took a piece of wire and inserted in into the hole. This gives you a lead that you can touch for the connection without damaging your cable or whatever. Are you getting a voltage reading the same as the output when we first started testing? If your answer is yes, then you can move on and start testing to make sure your serial to usb adapter is good. If not, READ ON.
Ok, so you're testing your connection right? No signal, or is it jumbled?
If you are getting NO SIGNAL then you either did not do your soldering correct, OR you have a bad ground. For me, this was the case after countless hours of debate and checking and rechecking. A bad ground or improper ground will lead to signal loss or total loss where you will not even see anything. You are going to need to check and see where you can ground your cable. To help you from spending 30m-2hrs to find a ground, I grounded mine into my engine bay. Just run a cable up through your firewall on the right side of the car and ground it to a bolt that touches the frame. I found this to be the best ground for me. This might vary, but I highly doubt that. Test your ground by checking your connection either through the computer of through your voltage meter. Its much easier with the meter I will assure you. Get this set and you should be golden.
If you are getting JUMBLED SIGNAL, then you need to actually go over your ground and make sure that your connection is not loose or something is touching, etc... Once you see that your ground is just fine check and see if you have any other gauges that are sharing the same ground. This is actually where I ran into an issue because my AVCR and my DEFI electronics were actually putting some "noise" back into the ground and giving my readout a jumbled or less than ideal read out. As I said above, I moved my ground into the engine bay to something that is touching a frame.
OK, so you STILL aren't getting signal?
Well, now we need to actually DISCONNECT your ground. The reason for this is because your ground is more than likely messing up your connection and not letting the signal pass through. Test your DATA connection again and see what you get. You should get a signal passing through your adapter unless you have either soldered it wrong or made a bad connection.
OK, so you got a signal through your cable and adapter but you aren't getting anything on the computer?
You need to really read and make sure you DO NOT PLUG IN THE CABLE BEFORE YOU INSTALL DRIVERS. This is critical, with Windows, this will possibly mess up your install and you will need to reboot your machine and retry the driver install. Install your drivers from your CD or the net depending where you got them. Hopefully your drivers install properly. If they do, then you need to REBOOT your machine. Once it gets back up and running and you have installed your drivers, plug in your cable. Windows should detect the device and a bubble will pop up down in the bottom right corner. It should end up saying the brand and model of the cable thats connected, and finish with saying, "your device is installed and working properly" or something to that effect.
OK so your device is installed and the computer "dings" when its plugged in? COOL. This means at least your computer and your serial to usb connection are talking. Now we just need to get the last part going.
Ok, tired of reading? I'm sorry, its complicated. Don't worry you are almost done... Sort of...
Ok, so let's pray that your cable and your serial cable work together and play nice. Obviously from this point on if your stuff works then pat yourself on the back. =D
IF IT DOESNT STILL READ.... read on... Ok, so your cable from your gauge with the female end on it is putting out signal? Ok good. Now, your serial to usb cable is recognized and working properly with your system? Good.
The best way to test and see if you are having a problem with your connector is a ghetto one at that. Remember the piece of wire we used to test the connection? We are going to actually use a "test wire" with 2 exposed ends to test our data connection and make sure the ground is STILL not the problem. To be honest, if you tested your ground properly there is a small chance that you are reading this to figure out your problem. Anyways, you will be inserting that piece of wire into the DATA CONNECTION wire port on that female adapter. Now take that test wire and touch it to that, or wrap it... whatever works for you. Now, we want to take this connection and bridge it to the serial to usb adapter to see if we can get signal through to the computer. You will need to touch the second pin from the left if you are looking at the male connector... If you get signal through to the computer then its your ground and you were lazy on the ground... No pat on the back.
IF YOU STILL GET NO SIGNAL after reading all this. Then its either going to be your serial to usb adapter is bad, which happens... It could be the driver software, and you need to uninstall and reinstall. If you STILL can't figure it out, post in here and explain in depth what's going on and I will try and help as much as I can.
|
__________________
FP Red*Greddy ProfecB Spec II*HKS TT*Nesei Short Route IC Piping*Synapse BOV*COMP 272s*Injen Intercooler*AFE Power Dry Filter*R/TErnie Intake*R/TErnie FULL 3" O2 housing with V-band*R/TErnie Modified DCsports 3" Down/Test/Flexpipe with V-Band*Greddy Ti-C Exhaust*255lph*Tein S-Techs*18" Volk LE-28s*Progress 25mm Rear Sway*Project Mu pads*JDM Tails*Cusco Heat Shield*Mishimoto Radiator hoses/Cap*ARC shift knob*Injector Dynamics 1000cc...
|
|
Offline
|
|
Jul 14, 2009, 10:22 AM
|
#15
|
|
Evolving Member
Personal Sales Rating: ( 1)
Join Date: Jun 2005
Location: Gulfport MS
Posts: 178
Drives: 2005 WW EVO VIII
|
I ran into the same issue and my problem ended up being that it wouldn't log with the interior lights on. I guess the UEGO controller in the gauge wasn't getting enough juice to power the serieal output.
Now i just log in the daytime. Some day i'll grab 12v from somewhere else.
|
|
Offline
|
|
 |
|
|
Tags
|
26, aem, beta16, cable, choose, comport, drivers, error, evoscan, installing, link, logging, uego, usb, vista, wideband  |
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
| |
|