Welcome to the North American Subaru Impreza Owners Club Wednesday September 28, 2016
Home Forums WikiNASIOC Products Store Modifications Upgrade Garage
NASIOC
Go Back   NASIOC > NASIOC Technical > Pre-2002 Factory Turbo Powertrain

Welcome to NASIOC - The world's largest online community for Subaru enthusiasts!
Welcome to the NASIOC.com Subaru forum.

You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, free of charge, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, so please join our community today!

If you have any problems with the registration process or your account login, please contact us.
* Registered users of the site do not see these ads. 
Reply
 
Thread Tools Display Modes
Old 03-15-2012, 03:40 PM   #1
eg33GC
Scooby Specialist
 
Member#: 206851
Join Date: Mar 2009
Chapter/Region: MWSOC
Vehicle:
56 Belair
Pro Street

Default evoscan cable

Some of us like to butcher our wiring harnesses, so we can't use the evoscan pnp unit
My FTDI 3v3 won't connect anymore, so maybe it went, or maybe it was the wrong voltage level all together?
my question is:
rs232-3v3
OR
rs232-5v

thanks
* Registered users of the site do not see these ads.
eg33GC is offline   Reply With Quote
Sponsored Links
* Registered users of the site do not see these ads.
Old 03-16-2012, 06:17 AM   #2
pmugabi
Scooby Newbie
 
Member#: 280926
Join Date: Apr 2011
Default

This might apply to you:

I had an issue with intermittent connections with the Evoscan cable connection to the stock wiring harness on a car.

I relocated the OBD1 connector and spliced it in right at the ECU. I had no issues after that.
pmugabi is offline   Reply With Quote
Old 03-16-2012, 12:16 PM   #3
69subaru360
Scooby Guru
 
Member#: 159682
Join Date: Sep 2007
Chapter/Region: NESIC
Location: Maine
Vehicle:
1995 WRX
2015 F150

Default

You need the 5 volt cable.
69subaru360 is offline   Reply With Quote
Old 03-16-2012, 03:22 PM   #4
eg33GC
Scooby Specialist
 
Member#: 206851
Join Date: Mar 2009
Chapter/Region: MWSOC
Vehicle:
56 Belair
Pro Street

Default

Thanks gents.
I had it directly wired, but the damn thing isn't even tripping my usb detection. Must be done.
eg33GC is offline   Reply With Quote
Old 03-31-2012, 08:44 PM   #5
eg33GC
Scooby Specialist
 
Member#: 206851
Join Date: Mar 2009
Chapter/Region: MWSOC
Vehicle:
56 Belair
Pro Street

Default

Having issues connecting with this cable..
wiring directly to the ecu at the plugs, and grounded to the chassis.

It connects, calls the ecu id 00000, and autoretrys. Any idea?
eg33GC is offline   Reply With Quote
Old 03-31-2012, 08:59 PM   #6
69subaru360
Scooby Guru
 
Member#: 159682
Join Date: Sep 2007
Chapter/Region: NESIC
Location: Maine
Vehicle:
1995 WRX
2015 F150

Default

Quote:
Originally Posted by eg33GC View Post
Having issues connecting with this cable..
wiring directly to the ecu at the plugs, and grounded to the chassis.

It connects, calls the ecu id 00000, and autoretrys. Any idea?
Have your rx and tx backwards?
69subaru360 is offline   Reply With Quote
Old 03-31-2012, 09:02 PM   #7
eg33GC
Scooby Specialist
 
Member#: 206851
Join Date: Mar 2009
Chapter/Region: MWSOC
Vehicle:
56 Belair
Pro Street

Default

nope, I checked for that and I get a failed initialization error


this is so damn infuriating as I used to have 0 issue on another obd1 jecs ecu engine using the wrong damn cable (3v3)
eg33GC is offline   Reply With Quote
Old 03-31-2012, 09:11 PM   #8
69subaru360
Scooby Guru
 
Member#: 159682
Join Date: Sep 2007
Chapter/Region: NESIC
Location: Maine
Vehicle:
1995 WRX
2015 F150

Default

You trying to read a burned chip or the stock rom from a chip on the board? You might have a bad chip.
69subaru360 is offline   Reply With Quote
Old 03-31-2012, 09:17 PM   #9
eg33GC
Scooby Specialist
 
Member#: 206851
Join Date: Mar 2009
Chapter/Region: MWSOC
Vehicle:
56 Belair
Pro Street

Default

just trying to datalog using my chips. if they were bad the car wouldn't run
eg33GC is offline   Reply With Quote
Old 03-31-2012, 09:29 PM   #10
69subaru360
Scooby Guru
 
Member#: 159682
Join Date: Sep 2007
Chapter/Region: NESIC
Location: Maine
Vehicle:
1995 WRX
2015 F150

Default

Maybe the handshake or ecu id data is corrupted?

Probably just a cable problem though.

What's the ftdi part number you got?
69subaru360 is offline   Reply With Quote
Old 03-31-2012, 09:36 PM   #11
eg33GC
Scooby Specialist
 
Member#: 206851
Join Date: Mar 2009
Chapter/Region: MWSOC
Vehicle:
56 Belair
Pro Street

Default

232r-5v-we
Evoscan recognizes it in the com ports.
tx, orange #4 on cable, rx, yellow #5
ground to dash beam

eg33GC is offline   Reply With Quote
Old 03-31-2012, 11:40 PM   #12
rob
n00b Moderator
Moderator
 
Member#: 811
Join Date: Jan 2000
Location: WA
Vehicle:
2000 RS-Ej20G
It tastes like burning

Default

short J1 and see if you can communicate with the stock ROM.
rob is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
evoscan 1.3u cable pin layout Nimm Open Source Reflashes 7 03-08-2011 07:41 PM
Tactrix or EVOScan cable needed in Central NJ. stangzroastrice Tri-State Area Forum 2 10-16-2009 06:27 PM
Would this $57 EvoScan cable work for logging w/ RomRaider? Zoinks Open Source Reflashes 5 09-10-2009 02:37 PM
EvoScan/StiScan with Cobb APv1 cable SSLegacyGT Open Source Reflashes 16 08-21-2009 06:53 PM
EvoScan Datalogging cable and Xpt map?? Dstretch33 Open Source Reflashes 8 09-04-2008 11:07 AM

All times are GMT -4. The time now is 06:21 PM.


Powered by vBulletin® Version 3.7.0
Copyright ©2000 - 2016, Jelsoft Enterprises Ltd.
Powered by Searchlight © 2016 Axivo Inc.
Copyright ©1999 - 2016, North American Subaru Impreza Owners Club, Inc.