Jump to content



Member Since 20 Mar 2012
Offline Last Active Mar 11 2015 07:51 AM

#298217 Mk2 Xenon Headlamp Retrofit

Posted by jarp on 20 October 2013 - 09:02 PM

Where i am not clear on things though is how the jets are operated. Are they operated when washing windscreen with lights on? or do they have a separate different switch purely for headlight washers?
Have you not ever used yours before?

What you did explain makes perfect sense. I thought there are some kind of motor or solenoid which pops washer up from bumber but pressure makes more sense. That's what I meant with that dummy jet comment...

My headlamp washers do operate simultaneously every time I use windscreen washer. There are no separate switch for them and I cannot prevent headlamp washers operating even if I would like to.

I will look into wiring issue again but not sure if I have time soon... Thanks for your link I will look into it and try to locate that controller connector!

#297443 Mk2 Xenon Headlamp Retrofit

Posted by jarp on 17 October 2013 - 06:33 AM

Jari if you ever do get the chance to take out your headlight checking for looms under it, could you take a picture of what the washer jet looks like for me please? i would like to know how it's connected to the car so i can do mine


Sorry it took this long, I was away for a while... I took one headlight off and took picture of washer jet. Picture is attached (click to enlarge). Its from left hand drive car, right side headlamp.


You can see from the picture how water hose is connected, but I do not see any electrical connections? Are these just dummy jets, one separate pump is somewhere else (too lazy to check schematics now ;)? Or then connections are hidden inside car chassis, cannot see there properly...


Ps. My headlamp connectors have only 7 wires so no HIDs for me - at least without adding extra wires but that would be too much...

Attached Thumbnails

  • focus_headlamp_washer.jpg

#295476 Mk2 Xenon Headlamp Retrofit

Posted by jarp on 09 October 2013 - 07:02 AM

Great pictures, thanks! Did you find rear sensor also? Ah yes, adaptive lighting is AFS then yes, the control module is the same. If you go to ELMConfig and Headlight Control Module and then configurration, you can see that you can configure module as HID or AFS (and yes there is HID configuration option for GEM also). But if you will retrofit HIDs to your car, won't you lose AFS? Or does AFS support both halogen and HID? I really do not know since I never took any look to AFS schematics or anything...


I really do not know why I have washers but not HID :-) Perhaps the car originally had HIDs or something but they broke and halogens were retrofitted b dealer instead as they are cheaper. Or something like that. I will check out the wires when I have some time, thank you for your great pictures!


Ps. According to schematics sensor connector should be on right hand side on both left hand drive and right hand drive cars. Yes I have left hand drive indeed.

#294834 Mk2 Xenon Headlamp Retrofit

Posted by jarp on 06 October 2013 - 07:02 PM

Ah, those connectors are color coded for your convenience... Comparing them to your pictures, that 2 pin connector just next to you headlights, having black and green-yellow wires, it should be... C744 to headlamp washer :-) I'll try to verify that tomorrow if I have spare time.

That 6-pin connector, I do not know what it is. It seems not to be related to HID-lights, shape is wrong and colors also...

#294828 Mk2 Xenon Headlamp Retrofit

Posted by jarp on 06 October 2013 - 06:41 PM

Connectors should look like this (pictures attached)...

Attached Thumbnails

  • front_level_sensor.png
  • hid_module.png

#294826 Mk2 Xenon Headlamp Retrofit

Posted by jarp on 06 October 2013 - 06:35 PM

Wow, lot's of pictures :) I will try check my washers tomorrow and see how they are connected. I checked out schematics of headlight washers and there is not that much components in it. Probably quite possible to retrofit also if one founds suitable wrecked car. Buying parts as new would be too expensive I think...


However I didn't read schematics throughout enough, it seems they give hint about locations of these connectors. HID Control Module is connected to harness 14401 together with heater blower motor, navigation, radio, cluster, diagnostigs, heating control etc. It most likely is located somewhere in console...


Front leveling sensor is connected to the same harness than right head lamp (14K733), should be just next to it after right front sensor (no idea what it is). Cannot locate rear leveling sensors...

#294806 Mk2 Xenon Headlamp Retrofit

Posted by jarp on 06 October 2013 - 05:14 PM

Further research, this HID Control Module is called "Electronic Headlamp Control Unit" and it just could be, that unit from AFS lights will work with HID lights if properly reconfigured using ELMConfig... Anyways it is something like this:




According to the schematincs and judging from the picture there is one big connector for this unit. Now, where is it? When I yesterday replaced cabin air filter I saw few unused connectors on center console, but I am not sure if any of them was big enough for this one... It just could be that there are no wires insalled on non-HID Focus...

#294788 Mk2 Xenon Headlamp Retrofit

Posted by jarp on 06 October 2013 - 04:06 PM

Unfortunatelly schematics wont say a word about locations of connectors or anything like that :/

I used a bit time to triple check schematics and really, there should be nothing else needed apart from wiring. To sum it up, halogen lights are driven by GEM, which takes inputs from Headlamp Switch and Multi Function Switch. Same goes with HID lights, they are driven by GEM etc. Hardware seems to be the same, connectors, wires and pin numbering etc. are the same.

However, with halogen lights there is wire from Headlamp Switch (manual leveling knob) to headlamp module(s) (for leveling motor of course). With HID lights there are no knob and this wire from lamps goes to HID Control Module instead, which takes inputs from Front Level Sensor and Rear Level Sensor.

Since the same physical wire and connector is used for leveling signal no matter if signal comes from manual knob or HID Controll Module, there seems to be "Jumper for Halogen Lights" which is used to reroute this signal (and some more signals for HID Control Module). I have no idea if this jumper is present on cars without HID lights...

Anyways, I would speculate that really, this would be needed to retrofit HID lights to Focus (again, if wirings would be the same):

- Add HID Control Module
- Add Front Level Sensor
- Add Rear Level Sensor
- Replace headlamp assemblys with HID versions
- Change "jumper for halogen lights" to HID position
- Use ELMConfig to check that you can communicate with HID Control Module. Configure it according to you car type.
- Use ELMConfig to reconfigure GEM for HID

I have NO IDEA if this actually would work or break something. But according to shcematics, this could be just enough... Now somebody please locate all these modules for us :)

Ps. No idea why I have headlamp washers. Perhaps original owner though it would be good idea to buy those as extras...

#283850 Guide For Focus Mk2/mk2.5 C-Max/kuga ~Elm 327 Cable And Ff2 Program

Posted by jarp on 20 August 2013 - 03:07 PM

how would i know if i have a ftdi chip in my elm cable

do you also need to install extra drivers

thankyou for the lengthy post explaining it all


If you have older OS like Windows XP, you have to manually download right drivers. Windows 7 does this automatically, you plug in device, Windows loads drivers from the Internet and Everything Just Works. You can check what you have from device manager:


* Launch device manager

* Expand Ports (COM & LPT)

* Right-click correct COM port and choose Properties


From here you should see Manufacturer and if you have FTDI chip, it says FTDI. Porbably Prolific for PL2303. I think, if you have Windows 7 and plug in FTDI's device wirth FT232R chip, Windows will automatically donwload latest dirvers which supports both VCP and D2XX at the same time... But you can compare the version number to one in FTDI's website. My version for FTDI's drivbers is and D2XX protocol works just fine.


But if you have older Windows, you will see unknown device or something in device manager. You can still right-click and choose properties and then you can go to Details and choose Hardware Ids. From here you can see strings (VID and PID) which will tell you what device you have there. Just google them...

#283847 Guide For Focus Mk2/mk2.5 C-Max/kuga ~Elm 327 Cable And Ff2 Program

Posted by jarp on 20 August 2013 - 02:57 PM

I will continue a bit actually, if somebody is interested. So this emulation layer after emulation can cause problems by itself. But why are we having problems? Why do other devices work and other do not? Well, hello China! As USB took over and serial ports started to dissapear but still all the devices supported only serial protocol (again, it's trivial to implement compared to USB protocol), few companies smelled money. Let's make Serial-USB bridge chips so that hardware vendors do not need to do anything else than add one chip to their devices and software vendor's do not need to do anything at all! Great idea, and great profit!


Chinese being chinese, they of course smelled money also and started to clone thise bridges. As far as I know, most often cloned device is Prolific's PL2303. This was a bit unfortunate, because back in times Prolific's drivers were crap. And Chinese cloned these chips and sometimes cloned chips were inferior. And Chinese used Prolific's drivers for their cloned chips. Inferior chips and crappy drivers. You can imagine. Prolific got their act together and started to improve their drivers... and blocked cloned chips while they were doing it! So if you have cloned PL2303 chip, latest dirvers from Prolific do not work and you are forced to use crappy drivers for your crappy cloned chip! This is the reason why somebody said that their device do not work on Win7 but works on Win Vista. Or works with old drivers etc etc etc. 


Ah, and China... ELM327 chip made by ELM Electronics based on Canada gained also popularity. So of course it was doomed to be cloned by Chinese. They had released version 1.0 of their chip and it was cloned. After that ELM Electronics realized that they need to protect their IP and they implemented copy protection for newer versions like 1.4b which had support for all cool features and had lot's of bugs fixed etc. Poor Chinese, unable to clone never verions... Well, just label these 1.0 chips... let's say... 1.5, it's better than 1.4b! People will buy them, they won't understand! And that exactly was what happened. Old buggy cloned chips is now inside most of the ELM327 devices sold in eBay and DX! Don't know if Chinese ever were able to bypass this copy protection or did they perhaps develop their own better chips based on this v1.0, but essentially, if you are buying anything else than genuine ELM Electronics ELM327 chip, it's Russian roulette. You just do now know what you get. You may get well-working device or you may get alfunctioning device! And you ask why your device won't work 500 000 bps? :)


So, if you really want to get real deal without problems, buy device which has genuine FTDI FT232R bridge inside (AFAIK these are not cloned - at least not often, so as long as you get FTDI, youre good). And as you are doing right thing already (do you really wan't to give your money to Chinese pirates?), you may just as well grab genuine ELM Electornics ELM327 chip also. Price difference is not that much...


Of course, problem is, that how do you know if you get genuine ELM327? I really do not know. I actually asked this directly from ELM Electronics. They answered, that you just cannot know. You will have to trust the seller. So ask seller if their devices have genuine chips inside and you're done your best...


I think I will cease my rant here, I hope this information is usefull for you who are wondering how things do work and why some devices will work and some will not...

#283844 Guide For Focus Mk2/mk2.5 C-Max/kuga ~Elm 327 Cable And Ff2 Program

Posted by jarp on 20 August 2013 - 02:39 PM

Just downloaded the latest version of this wonderful software.
can someone explain what the driver option is for please.
(V)CP and FTDI D2XX option

can you update the PCM on a Focus ST 2.5 MK2.5



If your ELM327 device has FTDI bridge inside, download D2XX drivers from FTDI's site and use D2XX.


You see, back in history computers had one or two serial ports (usually named COM1, COM2 etc, you remember). All the software etc. were able to communicate with devices via serial ports using serial protocol (RS232). And then came the USB (port and protocol, nothing to do with serial ports or protocol), replacing serial ports from computers. But yet still lot's of devices (like ELM327 chip!) uses serial protocol today, as it is so much easier to implement than USB. Child can implement serial protocol to their devices, you know, but USB, it's whole different thing. Same goes with software, they support serial protocol and serial ports as it's simple to implement and of course because devices still use them! However, here comes dilemma... We do not have serial ports anymore on our computers!


Here comes serial-USB bridges, like Prolific's PL2303 or FTDI's FT232R. They are able to communicate with devices like ELM327 using serial protocol and then transport serial data to computer via USB connection. On computer, there are drivers for these bridge chips and these drivers do communicate with these chips over the USB. Drivers do create virtual serial ports (opposed to real hardware serial ports), often called VCP (virtual COM port) and expose serial data read from USB to software via virtual serial ports. Software supporting serial ports (or COM ports, as they are often called) then can connect and their point of view they are just "talking serial" directly to devices. But behind the scenes whole chain is:


Serial Device <-> Serial-USB Bridge <-> USB Port <-> Drivers <-> Virtual Serial Port <-> Software


While back in days we had:


Serial Device <-> Serial Port <-> Software


Now, as USB and serial protocols are totally different species, this multilayered emulation can give problems. As you have found out, speed problems etc. Now, FTDI has implemented D2XX protocol, so that if software does support it, software can communicate directly with Serial-USB Bridge bypassing Virtual Serial Port. So chain becomes:


Serial Device <-> Serial-USB Bridge <-> USB Port <-> Drivers <-> Software


So one problematic emulation layer is removed. This requires, of course, support from the drivers and from to software, since this is vendor specific thing instead of standard thing. ELMConfig supports D2XX, so if you have FTDI chip inside of your ELM327, you should use D2XX, it's more reliable for obvious reasons.


Ps. You could, of course, connect ELM327 chip directly to serial port, if you have one and you would have the skills. This would eliminate all the emulation layers etc. Though, where do you find serial ports anymore and where do you find fast enough serial ports? Old computers had slow serial ports... Cannot remember what was the usual speed limit back in old days...

#280593 Guide Fitting Cruise Control Focus Mk2 & Mk2.5 And Ford C-Max

Posted by jarp on 07 August 2013 - 08:41 AM

Wait... I have not yet received my 500kbps capable ELM327 dongle so I really do not know, but this got my attention:


"I get the warning as in picture 5 There is a Non Empty VID Block etc I click on yes."


Will this not overwrite your previously loaded VID which had CC enabled? So in essence you just rewrote original firmware back to the PCM without any modifications...


This is just a quess. I have never reprogrammed PCM or anoything, but judging from wording in your screenshots, I would suspect that this is the case. Though, I do not know if it is safe to answer no either! Perhaps you could check those Russian forums using Google translator?


Edit: Perhaps this can be checked out by reading again firmware and VID block from the PCM and seeing if CC is enabled or not? If it is enabled then it must be something else...