makymak
Members-
Posts
195 -
Joined
-
Last visited
Profile Information
-
Gender
Not Telling
-
Interests
Keeping my cars as oem as possible!!!
-
Location
Milky-way
Car Info
-
Model
LHD Fabia 6Y 1.4L 16V AUB Elegance, LHD Octavia 1U 1.6L AVU Elegance, a Honda
-
Year
0
Recent Profile Visitors
905 profile views
makymak's Achievements
-
Sorry for the late reply. Life runs like crazy! That's very good news! So, we both have the wrong module. My car has also (K) while according to vin number it should have the (L) version. My car with the oem/genuine (K) version: - when the engine worms, the fans run at low speed. - when the a/c is on, the fans run constantly at low speed. - can't run high speed, due to the fault/no need to because the car never overheated. With an aftermarket (K) version: - when the engine worms, the fans run at low speed. - the a/c can't engage at all. I suspect that this module is programed to run the fans at high speed when the a/c is on. Due to the error it can't run the high speed so the module doesn't allow the a/c compressor to engage. Both modules throw the same error code. I will have to try the (L) version, too.
-
My findings are the same as @kareems No short to ground, no discontinue from ecu to fan control module. If I disconnect the fan plug from the module, the ecu throws an error that the fan control 1 and 2 are either open or short to + No short to ground error. I suspect the error is at the fan(s). I need further investigation.
-
No cruise control dashboard light
makymak replied to homodel's topic in Skoda Octavia Mk I (1996-2004)
No cruise control indicator on mk1. Sorry. -
First of all, this setup is very rare among the VW group. The majority of the family cars use a two stage temperature sensor (more correctly, a two stage switch) on the radiator and this sensor is feeding the respective module (which is quite plain) Our car has an analog temperature sensor which is feeding directly the ecu and the ecu is giving the orders to the module to operate the fans. If I remember correctly, to test this kind of setup, you need to heat up the sensor or to simulate it's region of resistance (it's a simple thermistor). The control module has all the circuitry, including the fan relays. If you want to test only the fans you need to bypass the module. It's not very difficult, each fan has three wires, one for positive low speed, one for positive high speed and one ground. Furthermore, each speed is protected from different fuses in the fuse box. The green scuttle connector I guess is under the scuttle panel, protected by a waterproof cover. At my left hand drive Octy it is under the wipers motor (I learned that when I retrofitted the cruise control). If you are concerned about overheating, you can hardwire the low and high speed so it always runs the fans at high speed. Too noisy, I'm afraid. Do remember that if the problem comes to coolant fan control 1 (the low speed), the A/C also won't run, as a prevention measure.
-
Thank you, Pete! I was hoping to see you here! Your help is always useful and accurate. I will check it and report. I will try first pin 7 on the control module, maybe tomorrow, as the access is very easy. But I have to wait for the holidays to go to get into the scuttle connections as it needs some working. Hope it's not the ecu itself that is short-circuited.
-
I have the very same problem with my 1.6l Octy. Never found a solution no matter how much I searched it. No documentation, either. I tried different fan control modules but the problem persisted. The fans are working ok so the problem is somewhere else. If not fixed, the fans will only run at the low speed. This never gave me an overheating problem even with the A/C on at the hot summer days we have here. If you find the solution, please let me know!!!
-
When my nephew crashed the Octy, the error was "short to something" don't remember anymore. I'm not saying that this is the situation with the OP. It's a possibility, though. Most obvious, it is just a faulty crash sensor. After a collision, no diagnostics (including the vcds) can reset the crash sensor errors. It's documented in the wiki. Furthermore, if a sensor is coded for a specific car, it cannot be recoded. It's only one time writing to the eeprom, allowed. To reset a deployed sensor or to change the coding you need access to the eeprom either internally or by special cabling to the sensor and of course the appropriate code. My nephew's Octy now has a crash sensor from a Leon. Never gave any problem. Me too, hope not to find out its functionality....
-
Has the car been involved in a front collision? This error usually comes when the front airbags are deployed and the crash sensor (g190) shuts off the engine for safety reasons. If not, then the module itself has a problem. The g190 is under the main console below the ashtray. Be careful when messing with the srs system. It's your safety and airbags don't react well if not all the precautions are taken. As for the 01329 the wiki describes it accurately.