PDA

View Full Version : OBD port pinout



PaddyB
08-07-2010, 03:45 PM
Been looking at the OBD port on my PFL & I'm curious about the pinout.

Pins 4, 5, 7 & 16 are there which means it can talk ISO9141/14230. Pin 1 is also present & is mentioned in the specs as propriety - in our case for displaying error codes when grounded.

Pins 9, 11 & 12 are also present. These are not mentioned in any specs I've seen. Does anyone know what they do ??

Cheers.

foxdie
08-07-2010, 04:07 PM
It's funny you should be bringing this up now, I've been doing some research into this myself the last couple of days, I'll share my findings;

First of all, here's what I believe to be the pinout from my trawlings of various forums;

Pinouts for the diagnostic connector on the car:

Suspected L-Line (ISO9141-2) - Goes to C3P6 on EFI ECU - Grey with red stripe
N/C
N/C
GND (Chassis) - Black
GND (Signal) - Black
N/C
K-Line (ISO9141-2) - Goes to C3P12 on EFI ECU - Red with white stripe
N/C
ETACS Terminal - Green with orange stripe
N/C
Unknown - Yellow with dark stripe
Unknown - Yellow with dark stripe
N/C
N/C
N/C
+VE (12V from car) - Red with black stripe

uploaded/51922/1278674039.jpg

There are 2 important points at this stage:

We're told to short Pin 1 (suspected L-Line) to Pin 4 (GND) to get EFI (engine) diagnostics mode, I currently believe this is WRONG as it's mentioned in numerous forums to move Pin 1 on the cars connector to Pin 15 on the cars connector, and Pin 15 is typically the L-Line as part of the ISO9141-2 standard.
Some cables come with Pin 9 connected to Pin 15, you MUST remove this pin from the cable (or the car, but highly recommend the cable), this has been known to DISABLE THE BRAKES on the car by confusing the ABS system

I've tried the inverse of the first bullet above (I tried "adding" pin 1 to my generic vag-com cable and bridging it to pin 15), I didn't have any luck though but I now suspect that to have been a bug in EvoScan v2.5, I'm going to try with v2.7 Beta later tonight.

I have more information, I'm digging it up now, I'll add more to this post when I've got more :)

foxdie
08-07-2010, 04:10 PM
Here we go, taken from My Rolling Road (http://www.myrollingroad.com/showthread.php?t=31) (Evo specialist forum), pin 9 is for the ETACS terminal, I've amended my post above.

I'm not sure why this would relate to our cars though, I don't think we have ETACS (Electronic Time and Alarm Control System)?

PaddyB
08-07-2010, 04:23 PM
I was wondering about ETACS too. I've read that on MMCS equipped cars ETACS is a system that allows the user to change things like rear intermittent wipe period, how long the lights stay on, etc. Makes sense for it to be pinned out.
Well kind of.

On later MMC cars, ETACS can also control the windows/sunroof/mirrors. MMC ETACS is also found on Hyundai & some Kia cars too. It looks like it might be interesting ....

foxdie
08-07-2010, 04:25 PM
And some further musings on why we shouldn't be bridging Pin 1 to GND;

My reasons for looking into the above was because I was frustrated at my generic cable not being able to log AYC / ABS.

It's well known that OpenPort 1.3U cables will connect to the ABS / AYC system, and after looking at the schematics for such a cable I realised my generic VAG-COM cable was nearly identical (same chipset, near identical layout etc)..

Another thing I noticed was that some people were noting that they couldn't log until they'd moved the wire in Pin 1 to Pin 15 on the cars diagnostics connector, and after looking at ours I realise we may be on the same lines.

A couple of months ago I tried bridging Pin 1 to Pin 15 on my VAG-COM cable (as it's easier to do than the car diagnostic connector), but when testing it I found I could neither log the AYC/ABS systems or the EFI (engine) system either so I reverted my cable back and went back to the drawing board.

I've since learnt that the version I was using (v2.5) had quite a few people bitching that they couldn't log AYC / ABS with their OpenPort 1.3U cables, and subsequently a couple of revisions later the problem is supposedly fixed, so I've upgraded to v2.7 and will try it later this evening and report back :)

Ps. There's confusion over upgrading, Hamish (the EvoScan developer) implemented new licensing methods, you don't need to purchase the software again to get an upgrade, you just need to file a support ticket on his brand new but hidden website (http://evoscan.limitless.co.nz/) with your old key / registered email and he'll issue you out an updated license key ;)

Nutter_John
08-07-2010, 04:28 PM
or you just could goto

www.evoscan.com

foxdie
08-07-2010, 04:47 PM
or you just could goto

www.evoscan.com

Ahh he has that many of the damned things ;)

foxdie
09-07-2010, 12:16 PM
Okay small update, first I'm bumping because I've updated my first post (http://www.clubvr4.com/forum/showpost.php?p=563714&postcount=2) to include an image of the OBD connector on the car, and wire colourings.

I tried moving pin 1 to pin 15 and had no luck, EvoScan v2.7 just wouldn't connect. When it was trying to connect, the dash lights started flashing briefly, then stopped.

I guess I'm just going to have to bite the bullet and buy a 1.3U cable.

foxdie
09-07-2010, 12:31 PM
Referencing Kitty's VR4's awesome EFI ECU Pinout (http://www.clubvr4.com/forum/showpost.php?p=445748&postcount=1) thread, I've updated the pinout list above.

foxdie
09-07-2010, 03:22 PM
Hmm, hopefully some more interesting titbits, with more "thinking out aloud" ;)

Referencing a couple of Kitty's VR4's pinouts for AYC systems, there's mentions of the 2 lines, for this example we're using the ASC-AYC pinout (http://www.clubvr4.com/forum/showpost.php?p=471715&postcount=1) research, on the 12 pin (3rd / C3) connector, we've again got a mention of the 2 MUT-II cables, RED-WHITE (C3P2) and GREY-RED (C3P8), I guess it makes sense that all relevant devices use these 2 lines to communicate with the MUT-II.

What's interesting is the K-Line (RED-WHITE) is listed as "Diagnosis data input/output", and the L-Line (GREY-RED) is listed as "Diagnosis change input", which would make sense that you'd use the second line to select which ECU you wish to speak to if you're using a common line for data exchange.

So bringing this line low (GND'ing it) allows you to communicate with the EFI ECU, I wonder what happens if it's held high? Personally I don't think it's that simple, but I'm willing to try for science at the weekend :)

Davezj
09-07-2010, 03:50 PM
interesting stuff, but holding pin 1 high will select which ECU?

you have a few to choose from ayc, tcu, abs, SRS.

foxdie
09-07-2010, 03:59 PM
interesting stuff, but holding pin 1 high will select which ECU?

you have a few to choose from ayc, tcu, abs, SRS.

Yeah that's a given! I was just musing.. "if holding it low selects EFI, what does holding it high get?" :)

I guess I need to get my hands on an OpenPort 1.3U and a 2 channel logic analyser / oscilloscope or something :)

Edit: WOO! 1337 posts :D

Davezj
09-07-2010, 07:29 PM
you may well find that if what suspect is true about the single wire data in/out is occurring, then pin 1 is actually and address line and it is just convenient that the engine ecu is at address 0000.

PaddyB
09-07-2010, 08:29 PM
Been a looking.

Pins 1 & 7 go to a lot of places.
Engine ECU: pins 56 & 62 resp.
A/T ECU: pins 23 & 63 resp.
TCL ECU: pins 1 & 14 resp.
ABS ECU: pins 14 & 7 resp.

Pins 1 & 11 goes to A/C ECU pins 18 & 17 resp.

Pin 1 also goes to keyless entry ECU, pin 7.

Pin 12 is a single wire interface to the MUT-II connector.

Pin 9 goes to the ETACS ECU, pin 8. Thats the thing that does the ding ding ding when you've left your keys in. It also switches interior lights off, the intermittent rear wipe intermittentness & it's also plumbed into the sunroof (if fitted), power windows, central locking & lots of other stuff.

So my best guess ATM is that:
pins 1 & 7 is an addressable bus,
pins 9 & 12 are single wire interfaces to ETACS & MUT-II resp.
pins 1 & 11 go to the aircon but can't thhnk how that might work
pins 4 & 5 are ground
pin 16 is 12V (10A fused)

PaddyB
09-07-2010, 09:09 PM
There's also the 'other' diagnostic connector to muddy the water, the 12 pin one.

Reading on ISO 9141: the K line (pin 7) is a single wire addressable bus. Any device can talk & listen on this line. The L line (susp pin 1) is exactly the same as the K line but only external hardware can talk on this line.

What I'm trying to achieve is a OBDII data logger; thus far I've acquired an embedded micro with UARTS & ADC agogo. Seeing as ISO 9141 is not an open protocol I'm considering getting an ELM323 to do this bit.

scott.mohekey
10-07-2010, 12:19 AM
My thoughts are that pin 1 is a 'bus enable'. Holding it high will have the same effect as not doing anything I imagine, unless it floats (which is unlikely). It's possible it needs to be pulsed to select different ecus. But from what Paddy says above about pin 7 being addressable, that pin is simply bus enable.

PaddyB
10-07-2010, 01:26 AM
I'm building on fox's hypothesis that pin1 is really a relocated pin15 (is his fault really)

If we agree that pin 7 in the ISO 9141-2 K-line then all devices on that line can talk & listen to each other. I can't find out [yet] if a packet header states the source/destination - what I've read (which isn't the spec) suggests that it's some time multiplexed system. It's supposed to be the same as RS232, etc. except levels so it should be sniffable.

The true nature of pin 1 is the issue - if it is pin 15 then why not put it there. Pin 1 is reserved for proprietry use according to the spec so what's going on there is not in the public domain. All I know is that it goes to every ECU available, even more that pin 7. Might be bus enable - very possible - but I'd imagine that these systems would chatter with each other regardless of the state of pin 1

I have 'scope, openport 1.3 & evoscan - I'll endeavour to have a go this w/e. If it carries the same signals as pin 7 (the K line) during initialisation then it woudl suggest it's the L-line.

scott.mohekey
10-07-2010, 02:25 AM
Sorry, when I say bus enable, I mean for diagnostic purposes. I.e. it would be my guess that during normal operation, pin 1 is always floating/high.

foxdie
10-07-2010, 09:50 AM
I'm building on fox's hypothesis...
Are you MAD? :D


... that pin1 is really a relocated pin15 (is his fault really)
It's my fault Mitsubishi put a pin someplace different when designing a car whilst I was still in high school? /pan


If we agree that pin 7 in the ISO 9141-2 K-line then all devices on that line can talk & listen to each other. I can't find out [yet] if a packet header states the source/destination - what I've read (which isn't the spec) suggests that it's some time multiplexed system. It's supposed to be the same as RS232, etc. except levels so it should be sniffable.
There's a buttload of useful information in this forum (http://www.myrollingroad.com/forumdisplay.php?f=16) that may be of help, including this thread (http://www.myrollingroad.com/showthread.php?t=60) that includes some diagnostics of the MUT Protocol.


The true nature of pin 1 is the issue - if it is pin 15 then why not put it there. Pin 1 is reserved for proprietry use according to the spec so what's going on there is not in the public domain. All I know is that it goes to every ECU available, even more that pin 7. Might be bus enable - very possible - but I'd imagine that these systems would chatter with each other regardless of the state of pin 1
There will be some sequence of HIGH/LOWs sent down this immediately before or after the init sequence sent down the K-line..


I have 'scope, openport 1.3 & evoscan - I'll endeavour to have a go this w/e. If it carries the same signals as pin 7 (the K line) during initialisation then it woudl suggest it's the L-line.
Do it! We need that info! :)

Does your scope do logging to external storage of 2 channels at once? Scope both the K and L lines out, and then try connecting to each individual system one after the other :)

+rep will be due in good course ;)

wintertidenz
11-07-2010, 05:01 AM
I thought pin 9 was disconnected so you could access AYC and ABS systems? I had to remove that pin to access anything about the AYC ECU at all on my generic cable.

PaddyB
12-07-2010, 10:46 PM
Alright - in a attempt to solder a couple of flyleads onto my openport 1.3 cable i've totally shagged it. So if anyone knows the component values for R1 & C10 I'd be forever grateful (& have resurrected my openport cable).

For thosetempted to follow in my footsteps there's a huge blob of hotmelt (that removed those components) that holds it all together - that'll need heating up a bit to aid separation otherwise you'll wreck it.

Interesting though - pin 1 on the plug doesn't track anywhere but it's shorted to another pin. It's unclear which pin now (my technique's too destructive) but my best guess would me pin 9 ?!?!

The openport 1.3 cable has pins 1, 4, 5, 7, 9, 11, 15 & 16 but then it's not really designed for our car.

scott.mohekey
12-07-2010, 11:00 PM
I've attached the schematic for the openport 1.3 cable. You can see that it doesn't actually have anything on pin 1. From memory, it relies on the connection to mitsis extra diag port, which is labelled as BOOT on the schematic.

foxdie
13-07-2010, 11:36 AM
Alright - in a attempt to solder a couple of flyleads onto my openport 1.3 cable i've totally shagged it. So if anyone knows the component values for R1 & C10 I'd be forever grateful (& have resurrected my openport cable).

For thosetempted to follow in my footsteps there's a huge blob of hotmelt (that removed those components) that holds it all together - that'll need heating up a bit to aid separation otherwise you'll wreck it.

Interesting though - pin 1 on the plug doesn't track anywhere but it's shorted to another pin. It's unclear which pin now (my technique's too destructive) but my best guess would me pin 9 ?!?!

The openport 1.3 cable has pins 1, 4, 5, 7, 9, 11, 15 & 16 but then it's not really designed for our car.

The idea is you're meant to physically remove Pin 9 from the OpenPort 1.3U cable for it to work with our cars, that or remove Pin 9 from the cars connector and tape it up with insulation tape or something.

Oh and move Pin 1 on the cars connector to the position of Pin 15.

When I get paid at the end of the month I'll see if buy an OpenPort 1.3U, there's a guy near Nick Mann in Redditch who sells them for under 90 quid (http://www.gb-ent.com/index.php?option=com_virtuemart&Itemid=26&page=shop.product_details&flypage=garden_flypage.tpl&product_id=480&category_id=111&manufacturer_id=0&vmcchk=1&Itemid=26).


I've attached the schematic for the openport 1.3 cable. You can see that it doesn't actually have anything on pin 1. From memory, it relies on the connection to mitsis extra diag port, which is labelled as BOOT on the schematic.

Indeed, but from what I can gather, you just need to apply +12V to 3 pins on the reflash connector to set the EFI ECU to RW mode, I haven't really inspected it that much to say which goes where though.

PaddyB
13-07-2010, 04:19 PM
Scott - a really big thank you for that. Much appriciated.



The idea is you're meant to physically remove Pin 9 from the OpenPort 1.3U cable for it to work with our cars, that or remove Pin 9 from the cars connector and tape it up with insulation tape or something.

What problems should removing pin 9 solve ?? I can't remember have any.

scott.mohekey
13-07-2010, 11:05 PM
Agreed, I've used this very cable many times without any modifications to the cable or the car.

foxdie
14-07-2010, 01:39 PM
As I stated earlier, it's been known to affect the brakes when trying to log the AYC/ABS system because it interferes, I did have some references for this but the only one I can find at the moment is this one;

http://www.myrollingroad.com/showpost.php?p=528&postcount=2

Davezj
14-07-2010, 01:43 PM
so all you are doing with pin 1 (which is a chassis GND on the connector in the car) is grounding pin 4, and pin 5 via the cable internally. which is done be the sullins connector normally.

PaddyB
14-07-2010, 05:53 PM
so all you are doing with pin 1 (which is a chassis GND on the connector in the car) is grounding pin 4, and pin 5 via the cable internally. which is done be the sullins connector normally.

No Dave,

On the car: pins 4 & 5 are ground already. Pin 1 isn't ground & it's goes to a load of places (see one of my previous posts on this thread).

On the cable: pin 1 is shorted to pin 9, I think but I broke the link when pulling it apart.

On the car again: It's suggested that pin 1 may in fact be the L line relocated from pin15. If Evoscan (or another suitable scan tool) does it right then, when pin1 on the car is hooked up to pin 15 on the cable, the init pulse should be seen on both at comms startup AFAIK.

PaddyB
14-07-2010, 07:55 PM
This is interesting. Just looking at the schematic the Scott posted up & it shows pin 9 is tracked to pin 15 - don't forget that pin 9 is shorted to pin 1 also. There could be some mileage to be had in shielding pin 9 - pins 1 & 15 would then be connected in the plug.

Davezj
14-07-2010, 08:18 PM
No Dave,

On the car: pins 4 & 5 are ground already. Pin 1 isn't ground & it's goes to a load of places (see one of my previous posts on this thread).

On the cable: pin 1 is shorted to pin 9, I think but I broke the link when pulling it apart.

On the car again: It's suggested that pin 1 may in fact be the L line relocated from pin15. If Evoscan (or another suitable scan tool) does it right then, when pin1 on the car is hooked up to pin 15 on the cable, the init pulse should be seen on both at comms startup AFAIK.


yeh my bad paddy.

PaddyB
27-07-2010, 12:42 AM
Alright - Openport 1.3 cable has been [hopefully] repaired. If I'm lucky I didn't lift the pads off when I yanked the blob of hotmelt off.

I've removed pin 9 (as it's tied to pin 15 inside the openport cable) so now pin 1 is connected to pin 15 only & put fly leads on 4/5, 7 & 15. I'll try when it's light tomorrow & post my findings.

A big thankyou to Scott for posting up the schematic & to Davezj - who gave me 2 embedded PC boards some time ago, 1 of which has been seriously cannibalised in the search for a 10nF cap.

foxdie
30-07-2010, 04:16 PM
Bah.

So I was gonna get myself either a 1.3U or a 2.0 from a guy in Redditch (just down the road), found the retailer (Grant620 from the MLR) mid-July but couldn't afford it until now.. The guys just moved to Somerset :(

"FFFFFFUUUUUUUUUUUUUUU" :bigcry:

PaddyB
30-07-2010, 10:17 PM
OK. I've deployed the necromanced OpenPort1.3U cable sans pin 9 & the first thing I noticed was all the flashing lights were going mental. Specially the engine management light which was just strobing randomly.

[Aside: I suppose I should have used the cable with pin 9 still connected to see if I've introduced any behaviour in the fix but heyho]

Things calmed down when I connected the USB end to the PC - the dash lights started flashing normally (every half sec) with the exception of the engine managment light (still mental) & the scope went from 12V noise on 1 & 5V noise on pin 7 to a steady 0V & 12V resp.

Note that pin 1 on the car is pin 15 in the OBD spec - which we suspect to be L-line. Pin 7 is the K-line. Hereafter they are refered to as the K-line & L-line (even if it might not be the L-line). On the pics pin 15 is the upper trace & pin 7 is the lower trace.

Initiating comms:

EFI ECU
Pic 1 show the start of the data the talking to the EFI ECU. The L-line is asserted for 750ms, 600ms later the K-line goes low & a long time later the K-line shows comms. The L-line is at 0V hereon.

Now I don't know if I made an arse of the triggering but I didn't always see the L-line pulse when initialising comms when the last ECU I'd talked to was the EFI. So if I'd last logged from an ECU other than the EFI I always saw the pulse when starting logging the EFI, but if I stopped logging on the EFI & restarted it the pulse was not always observed. Hope that makes sense.

AYC ECU:
Pic 2 shows this. The L-Line behaves exactly the same but the K-line starts some comms (Manchester encoded prolly). The scope period was not optimal on these traces - there missing info here. I'll have to revisit this when my laptop battery has recharged.

ACD ECU:
Looked the same as the trace for the AYC ECU. But the trace could be incomplete. I'll have to do more over a longer time frame.

ABS ECU:
L-line as before but different trace on the K-line from the previous captures. Again could be incomplete. See pic 3

CAUTION: When I was communing with the ABS ECU I thought to test the logging by dabbing the brake. Scared myself sh!tless as a noise like a machine gun started as soon as I'd touched the brake. Switched everything off & started again - this time stayed away from the brake pedal but some time into the process the noise started again. Switched off the engine & the noise continued until I unplugged the USB cable from the PC. So I'm guessing the noise is electrical (solenoid edit - mean relay) in origin.

TCU ECU:
I couldn't make contact with this one.

I don't know what else the L-line does after the intiation pulse as I wasn't scoping it so it may do more than the 750ms pulse, it may not

foxdie
31-07-2010, 10:59 AM
I did warn you it'd mess with your brakes ;) You'll find it was most likely activating the ABS solenoid. Do NOT drive the vehicle if you hear that noise or you may find yourself driving into a wall, which we don't want naturally :)

Regardless, that's a big leap in the right direction for debugging the connections, so I've +rep'ed you :)

We could do with longer traces as well, from init right through to data being captured, as well as capturing different modes like reading values, reading DTCs and clearing DTCs, that would be most beneficial.

Also, what are you using for a logic probe / logger? I want one :smitten:

PaddyB
31-07-2010, 11:21 AM
I did warn you it'd mess with your brakes ;) You'll find it was most likely activating the ABS solenoid. Do NOT drive the vehicle if you hear that noise or you may find yourself driving into a wall, which we don't want naturally :)


But I'd be in the in the car driving by which point it'd be too late.:uhoh:



Regardless, that's a big leap in the right direction for debugging the connections, so I've +rep'ed you :)

We could do with longer traces as well, from init right through to data being captured, as well as capturing different modes like reading values, reading DTCs and clearing DTCs, that would be most beneficial.

Also, what are you using for a logic probe / logger? I want one :smitten:


Cheers for the rep.
Agreed about the longer traces - we need to capture an entire (& known) message.

Anyone got any info on the protocol ??

I'll go back to it later once I've put the hoover round.

I was using something like this (http://cgi.ebay.co.uk/TEKTRONIX-TDS-210-OSCILLOSCOPE-/180540058984?cmd=ViewItem&pt=UK_BOI_Electrical_Test_Measurement_Equipment_ET&hash=item2a0906ad68) but I paid £170 for mine some years ago - that said there's no scope for adding options or capturing to USB. I would still really like one of these (http://cgi.ebay.co.uk/Tektronix-THS730A-Digital-Real-Time-Oscilloscope-DMM-/150472091091?cmd=ViewItem&pt=UK_BOI_Electrical_Test_Measurement_Equipment_ET&hash=item2308d5e5d3). No wonder my wife thinks I'm sad.

foxdie
31-07-2010, 11:26 AM
Take a look at this (http://www.coolcomponents.co.uk/catalog/product_info.php?products_id=496), it's about the size of a phone, feature rich and pretty cheap too :)

Edit: I just realised it's only single channel. Bah.

I did find some info on the protocol on another forum, just about to go shopping but I'll dig it up for you this afternoon ;)

evonut270
08-08-2010, 05:32 PM
pin 1 is used to place the ecu into daignostic mode.pin 9 is to do with the AYC system which in turn shares info with the ABS system.iv not heard of any complications with brakes not working etc on any evo iv looked at which will share the same system. do Legnums have ACD?

Turbo_Steve
08-08-2010, 09:02 PM
Nope, they don't: they just wish they did :(

foxdie
29-08-2010, 11:27 AM
Just to add to this, Tim (TAR) got back to me not long ago, to clear up confusion;
Both 1.3U and 2.0 cables will let you access the EFI / ABS / AYC ECUs.
For the 1.3U cable only, you must remove Pin 9 for it to work with ABS / AYC. You do NOT need to remove Pin 9 on a 2.0 cable.
Only the 2.0 cable will allow you to reflash a 7202 / 7203 EFI ECU.
The 1.3U cable, despite being half the price, is reportedly significantly faster at polling the ECUs for data, this means you'll get more samples per second for logging things like fuel trim and other EFI ECU parameters.

Uray25
06-10-2010, 02:54 PM
Maybe a stupid Question, but does the Legnum support OBD or not ?

Because i'd like too fit this:
http://www.plxdevices.net/product/display/dm100OBD.php

Don't know which data to expect though, or is it a waste of my money ?

foxdie
06-10-2010, 04:48 PM
Uray, it will most likely not support that device.

The physical port is the same but the pin arrangements differ slightly
The communication protocol is different on VR4s to regular OBD2 protocols

Hope this helps.

Uray25
07-10-2010, 09:27 AM
Thanks for the info, thought as much. Just wnated to be sure.
Will steer clear of ODB items for our VR4's then.

foxdie
22-03-2011, 03:59 PM
Sort-of-bump.

I believe if we keep up with this we may be able to modify cheap OBD-II cables and / or build significantly cheaper versions of the Tactrix / OpenPort 1.3U cables (hopefully one day even the 2.0 cables) opening our cars up to more people :)

I'm going to look into getting an OpenPort 2.0 adapter soon as well as a logic analyser so we can properly debug the communication.

lathiat
22-03-2011, 04:22 PM
Has already been done!

See
http://www.myrollingroad.com/forumdisplay.php?f=16

lathiat
22-03-2011, 04:25 PM
However the evo scan guys like to sell Tactrix cables I think it will only work with them specifically by intent. Could be wrong.

foxdie
23-03-2011, 12:22 PM
CLaNZeR is a seriously clued up guy when it comes to this kinda thing and we've referenced his work in previous posts, however his work on that forum has ground to a halt in the last 12-18 months with only minor updates here and there.

From my perspective, his last development update was he was working on a SMD-based PCB for the MUT-II adapter, nothing further was released.

ersanalamin
20-06-2011, 02:59 AM
Okay just curious does anyone know about the ETAC ECU part number for Galant VR4 1997 pfl? does EC5A 1997 and EC5A 2002 and EA5A V6 2000 share the same ETAC ECU?

foxdie
02-07-2011, 09:09 AM
I did warn you it'd mess with your brakes ;) You'll find it was most likely activating the ABS solenoid. Do NOT drive the vehicle if you hear that noise or you may find yourself driving into a wall, which we don't want naturally :)
But I'd be in the in the car driving by which point it'd be too late.:uhoh:

I found out something interesting today, it only activates the solenoid when you issue "Request 02" to the ABS ECU (This is to get the wheel speed for the Front Right wheel), you can log everything else and it doesn't seem to foul the ABS Solenoid (don't hold me to it though, I've only tested this in a stationary car!)

Also, I thought I'd try driving the car on a private stretch of road with it fouling the ABS Solenoid, the symptoms are that it feels like there's a brick under the pedal, you cannot brake at all!.

Oddly though, sometimes after I stopped moving it would stop activating the ABS Solenoid, and reactivate it when I stopped. Again, don't hold me to this, my ABS sensors are a bit screwy at the moment too :)

foxdie
12-08-2011, 01:54 PM
I found out something interesting today, it only activates the solenoid when you issue "Request 02" to the ABS ECU (This is to get the wheel speed for thOddly though, sometimes after I stopped moving it would stop activating the ABS Solenoid, and reactivate it when I stopped. Again, don't hold me to this, my ABS sensors are a bit screwy at the moment too :)

Re-reading this thread, I realise the above quoted text may not be true as my ABS ECU is a bit on the wonky side right now :)

Will take a look at my car tomorrow whilst at the RR meet to try and see what wiring is messed up and try logging with my OpenPort 2.0. Also putting money aside for this bad boy (http://proto-pic.co.uk/products/DSO-Quad-%252d-Pocket%252dSized-Digital-Oscilloscope.html) :D

scott.mohekey
12-08-2011, 11:13 PM
also putting money aside for this bad boy (http://proto-pic.co.uk/products/dso-quad-%252d-pocket%252dsized-digital-oscilloscope.html) :d

want!