_dg Posted March 17, 2004 Report Posted March 17, 2004 I've tracked down what I think is the best value OBD-2 lead on the net. I've just got one from www.skpang.co.uk Leads from Quote
charles Posted March 18, 2004 Report Posted March 18, 2004 is this cable compatible with the ford 2,3 16V ODHC engine? I heard that only the newest models are compatible with the OBD-2 standard. Quote
_dg Posted March 18, 2004 Author Report Posted March 18, 2004 I don't think its a cable issue, but down to the software. I read elsewhere on the net (possibly at the forum on www.onboarddiagnostics.co.uk ) that vag-com (the software) will read all the VW parts of the galaxy, and also VW engines. But as the zetec is a ford engine, then it can not be accessed from vag-com. I'll give it a try the weekend and advise. Aparently my 2.3 was made about the time of the facelift, and may or may not have some of the facelift electronics. Obviously there must be a way of accessing the engine data, but this may be fords own software and not readily available to anyone else. I'll try and find out though Quote
MrT Posted March 19, 2004 Report Posted March 19, 2004 I believe that the pin outs in the plug are different for different systems. I have the same plug on my wife's fiesta but it does not even recognise it as connected, never mind read anything with software. Earlier Ford models use the PWM protocol as compared to the ODB-II. Some later Ford models use DCL. Has anyone found a good cheaper alternative to VAG-COM as it is rather pricey? Quote
Guest yurir Posted March 19, 2004 Report Posted March 19, 2004 I've been doing some research on this subject with a view to developing an open design for an OBD diagnostic tool (hardware & software). OBD2 (or EOBD) is a standard that has tried to amalgamate all the different existing diagnostic protocols by providing an overall "wrapper" layer on top of the existing protocols, which will provide a standard level of information, on all systems supporting OBD2.This means that the underlying communication protocol to the actual devices on the "OBD2 bus" (stictly speaking, there is no such thing) can vary and to achieve a workable specification, OBD2 adopted 3 existing protocols, and specified a common 15 pin connector (J1962/OBD).The protocols are: SAE J1850 PWM (pulse width modulation) SAE J1850 VPW (variable pulse width, similar to above, but different) ISO9141/14230 (modified RS422 protocol) In 2001, J2284 CAN was also added, as it is useable as an operational (as opposed to diagnostic only) inter-device communication protocol. But only really expensive or sophisticated cars are using this yet. Clearly, any interface and software you use has to support the underlying protocol on your particular vehicle.A good site for information on trying to identify the protocol used is http://www.elmelectronics.com/obdindex.html. As far as I've been able to determine, Ford have been using J1850 PWM on all their in-house systems since 1995.On vehicles which use "imported" systems e.g. VW engine/autobox (i.e. Galaxy 2000+), they have had to adopt ISO9141. I haven't yet been able to determine whether they will continue to use J1850 PWM on their new bespoke systems, or whether there will be an eventual shift to ISO9141 or J2284 CAN. In anycase, the VAG-COM software assumes an ISO9141 protocol, which is why it doesn't have a lot of hope with pre-2000 Galaxys. As it happens my current Galaxy (1998) uses J1850 PWM and my initial design efforts will concentrate on this protocol, but there is no reason why the others could not be supported; if anything, the "new" ISO9141 will be even easier to support. CAN could be a little more tricky. And as far as I can see, J1850 VPW will not be particularly useful to UK users (unless you have a Voyager or some such), and is probably on the way out, so that will be last on my list. Yuri. Quote
Richmond Posted March 19, 2004 Report Posted March 19, 2004 Yurir, Any chance of you posting an English translation? Quote
Guest yurir Posted March 19, 2004 Report Posted March 19, 2004 English Translation VAG-COM software will not work on pre-2000 Galaxy ! There is other free software that will work with the lead tracked down by _dg (see http://www.scantool.net) ! Hai.(Anyone seen "Lost In Translation" ?) :P Quote
Richmond Posted March 19, 2004 Report Posted March 19, 2004 I can understand that; thanks. Yurir, if I wanted to a bit of diagnosis on my 2002 Galaxy V6, exactly what hardware (inc leads) and software would I need? Cost -ish? I'd be running it on a Sony Vaio lap top, Windows XP Prof. What info would I get, and how is it presented on the screen? Is it comprehensible to a non-computer person? I suppose it must be, given that it's used by mechs. Quote
MrT Posted March 20, 2004 Report Posted March 20, 2004 Some sites to start at: VAG-COM On Board Diagnostics Excellent UK Hardware Supplier I have used the demo of VAG-COM on my 2001/2 V6 Galaxy with SKPang's cable. I find VAG-COM rather pricey for what it is. I could not get Scantool to work, on my Dell laptop would not recognise any port on the car as present. Quote
NikpV Posted March 20, 2004 Report Posted March 20, 2004 Sony Vaio lap top, Windows XP Prof. Does your laptop have a serial port? They don't appear to do the leads for usb ports, so you would need a PCMCIA card with serial ports or usb/serial converter. If anybody can correct me please do since my laptop is a Vaio with no serial ports :P Quote
NikpV Posted March 20, 2004 Report Posted March 20, 2004 Typical - answering my own post just found a USB version usb version Quote
charles Posted March 20, 2004 Report Posted March 20, 2004 yurir, it is still not clear to me.you say that from 95 on all ford models use the SAE J1850 PWM protocol. But How do I know if my car '97 2,3l is OBD-II compliant (neccessairy to work with the standard software, f.e. from scantool.net ? Quote
_dg Posted March 20, 2004 Author Report Posted March 20, 2004 I had a brief try with the lead from skpang and vag-com on my galaxy. The only module that got some response was the 'instrument' module and then just some VW reference numbers came up. I noticed that the lead only has 5 pins, and these do not correspond to some of the locations of the metal connectors in my galaxy socket - ie not all the pins in the connection block are used. The OBD 2 test from vag-com stated that the car modules were not OBD 2 compliant. The lead I have is supposed to be an OBD 2 lead, but as the pins are not connecting to some of the ones in the galaxy plug, I am not sure if a different lead is required. I'll try and give the lead and software a try in another car, just to confirm if it working correctly, and then spend more time back on my galaxy. Quote
Guest chrisH Posted March 21, 2004 Report Posted March 21, 2004 I've just got a hold of the shareware version of VAG-COM and the 'cheap' serial cable from Skpang. I also get the message that the system is not odb2 compliant. I can get it to work reading the error messages (DTC's I think thats what there called) but not much else. Any information I gleen from this equipment I will gladly post here for all the budding VAB-COMmers amounst us. In the mean time I'll work blindly like the rest of you. Chrish. ps. Mines a Galaxy 98 TDI. :huh: Quote
Guest yurir Posted March 22, 2004 Report Posted March 22, 2004 Richmond Posted on Mar 19 2004, 18:36:08 I can understand that; thanks. Yurir, if I wanted to a bit of diagnosis on my 2002 Galaxy V6, exactly what hardware (inc leads) and software would I need? Richmond, your most guaranteed bet would be the USB lead from Ross-Tech (~$99) and their VAG-Com software (~$230).Alternatively, you could try the ISO9141 interface from SK Pang Electronics or ScanTool ( Quote
Richmond Posted March 22, 2004 Report Posted March 22, 2004 Yurir, thanks for that. I think I need to have a look at the output before I spend the money. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.