Confused.colin Posted December 3, 2013 Report Posted December 3, 2013 Hi, I've been trying to read fault codes from my 04 2.3L Petrol Galaxy. Following the advice of some posts on this site, I downloaded VCDS lite and also purchased a basic OBD2 reader (as the Mk2 2.3 Petrol Galaxy has a Ford Engine Module and therefore needs the OBD2 reader). One or two of the peripheral modules could be connected to with VCDS and I managed to read the stored fault code in one of them, however most of them refused the connection. I also found that the OBD2 reader could not connect and when I ran the OBD2 query in VCDS Lite, it told me that my car was not OBD2 compatible. So I'm a bit lost now; I really wanted to look for fault codes on the engine module, but don't know how to connect. Does anyone have any advice or a recommended model of OBD2 reader that should work with my model? Thanks in advance! Quote
seatkid Posted December 3, 2013 Report Posted December 3, 2013 VCDS an acronym for "VAG-COM Diagnostic System" software is for volkswagen group (VAG) cars, therefore only works on the modules of VW origin. Your petrol engine is Ford so VCDS cannot read the ECU etc..... Quote
Confused.colin Posted December 3, 2013 Author Report Posted December 3, 2013 VCDS an acronym for "VAG-COM Diagnostic System" software is for volkswagen group (VAG) cars, therefore only works on the modules of VW origin. Your petrol engine is Ford so VCDS cannot read the ECU etc..... Thanks very much for your response - I understand what you mean about the VW modules I have read some other posts which say that I should be able to read the ECU using a standard OBD2 reader (For example - http://www.forum.fordmpv.com/smf2/ford-galaxy-reference-library/ford-galaxy-software-solutions-(vag-com-vcds-vagtacho)/ ) Is that true, and if so, do you have any idea why my OBD2 reader could not connect, and when I ran the ODB2 connection test from VCDS, it said the car was not OBD2 compliant? Quote
sparky Paul Posted December 3, 2013 Report Posted December 3, 2013 (edited) Forget about VCDS, that's for using with the VAG-COM cable to connect to the VW modules. To connect to the Ford engines, you need to use the generic EOBD/OBD2 interface with OBD2 software. I find ScanTool v1.13 software works well, you should be able to find a copy on the net somewhere, or if you got the diddy little software cd-r with the interface, it's probably on there. Edited December 3, 2013 by sparky Paul Quote
Confused.colin Posted December 7, 2013 Author Report Posted December 7, 2013 Thanks very much for the advice. Turns out relay 30 had a dodgy joint and needed repair, so ECU had lost power. This was the reason I wasn't getting anything from the ECU - a blob of solder on relay 30 meant that my OBD2 reader was then able to pick up the fault codes. VCDS lite works well for the non-engine modules (as these are still VAG compatible). Cheers everyone 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.