Does anyone have experience with the OBD1 evoscan cable and using evoscan?
http://www.evoscan.com/evoscan-gps-o...i-/-aldl-12pin
Printable View
Does anyone have experience with the OBD1 evoscan cable and using evoscan?
http://www.evoscan.com/evoscan-gps-o...i-/-aldl-12pin
I have it...but I ordered it 1 day before I found out I have a lower bearing failure..so it will probably be some time before I will be able to test it out. Hopefully it wasn't a waste of money. Maybe you could test it for me? haha...of course returning it after the results.
Quote:
Originally Posted by Forest Gump
Bump..
I would also like this information.
Zach
I'm not running their cable, but I do use evoscan with obd1. I have some old school serial cables and I just use a usb-serial adapter. I'd go with their cable as the adapter you need (if you have an old serial cable) is a PITA to get. I think I went through 3 adapters before getting the right one with some kind of special protocol.
what are your experiences vs say HHH
I could test this out the next time that I see an OBDI 3/S since I have the cables+software for all years. They are pretty much the same deal when it comes down to it, however, EvoScan already incorporates audible alerts and is set up for wideband input. HHH is more user-friendly in presentation IMO.
I have three as well man... LOL! Luckily, two of them are actually being used.Quote:
Originally Posted by Hans@GZP
Quote:
Originally Posted by Hans@GZP
what version of evoscan do you have. I can't get 2.5 or 2.7 to use
my com obd1 cable, the option is greyed out, but hhh works fine.
Quote:
Originally Posted by bboyalan
Im OBD1 however having some issues getting it running correctly.. but in your area so when it is running I can get in contact.
The issue is that the ODBI ECUs use a non-standard 1952 bps data rate that few USB to Serial chipsets support. Adapters build from the FDTI chips seem to support it like the Keyspan USA-19HS.Quote:
Originally Posted by Hans@GZP
I'm using 2.7Quote:
Originally Posted by Forest Gump
Make sure you are trying to connect with a "1.3 cable" and not the "2.0 cable". The FDTI chipset is also a necessity. I found that out the hard way.
thanks Hans, I'll try that, I do have the Keyspan USA-19HSQuote:
Originally Posted by Hans@GZP
Is there a particular driver you used, I'm using The one from keyspan
I just used the driver from the cable manufacturer. I forget where I got the cable... probably buy.com or something.
i cant seem to connect to the 1g ecu with evoscan.
ive got shivers cable, ftdi chipset usb to serial [ngear], evoscan 2.7&2.8+ [my serial doesnt work for 2.5/2.6]. tried on windows xp and 7 same result.
the usb to serial is good cause i can loop back and transmit data to myself and evoscan recognizes the drivers that are installed. it just trys to connect and gets stuck on INIT response from ecu and goes into retry multiple times.
i also got obdii cable and have been able to log a 94&96 no problem. just the 12pin doesnt work. ive tried on a 91 stealth, 91 eclipse and my own 90 gto and no response from ecu all times. any ideas?
edit: update. got serial and tried 2.5&2.6 still same thing, gets stuck on "waiting for init response..." and just keeps retrying. even tried the the data.xml file provided on 3si. ive tried different orders of turning car on connecting and starting the program but nothing.
yeah I never got this to work and gave up. using hhh
I'm with you, HHH is definatly the easiest logger to use.Quote:
Originally Posted by Forest Gump
Does HHH or Evoscan 2.7 work with the cables that 3sx or Ebay sells? Got a cable a while back and was using MMCD with my Palm M515 but my PDA died and now I don't have a way to datalog. I wouldn't mind using my laptop to log now since I'm going to be using it to tune my Maftpro anyways...my cable is an OBD1 plug to a serial plug, but I do have a serial to usb adapter that works with my laptop
I know the HHH cables are funky and anything other than their cables won't work.
I bet it would work with the Evoscan though.
Hmm, just trying to make sure which software would work before I spend the money on it, really don't wanna spend another $60 on a cable....
bump. still looking for answer...Quote:
Originally Posted by rez604
got it to work!
in simple terms: turns out my obdi cable has its receive and transmit pins setup to communicate with a palm pilot. to communicate with the pc program these two need to be swapped. did this and all is good now. if you want more detailed info look into how dte and dtc communicate with each other.
logging 1G with evoscan 2.8 :) its such a nice program once you get it to work properly lol
yeah I tried a null modem adapter and couldn't get evoscan to work, but HHH does. It is a software or configuration problem for me. I'm going to be using the emanage ultimate's logger mostly now anyway. Can't beat 50 samples a sec and 10 minutes internal logging.
I'm not using a HHH cable btw, it is a logger cable off the scanmaster 3 I have.
That's the first i've heard of HHH working with anything besides an HHH cable. Interesting.
since your past evoscan, this is something for others to try if they are still having trouble connecting even with a null cable: turn down the transfer/buffer rates under the advanced properties in device manager. this seemed to help my connection to get faster sample rates.Quote:
Originally Posted by Forest Gump
the problem was the evoscan software wouldn't detect the right com ports, even with the drivers installed.
just got mine recently and after some wiring issues at my ECU I got it sampling data much better.. my MAFT Pro is throwing a CEL, and while I can check OBD1 the old fashioned way with the analog meter, I'm having trouble distinguishing exactly which CEL it is, and was hoping the EVOSCAN would identify it.... so far, I can't get the ECU to initialize the DTC function of the EVOSCAN