Jump to content

The Colonel

Members
  • Content count

    12
  • Joined

  • Last visited

  • Feedback

    0%

About The Colonel

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  • Location
    Berkshire

Garage

  • Garage
    2003 E39 530D Sport Touring; 2016 MINI JCW Cabriolet
  1. The Colonel

    INPA can't connect to all modules on the car

    I thought I'd post an update in case anyone is interested. I've now run the car every day for more than one week, and I can report not one single error message or malfunction has been detected. Since I've disconnected the wire from the K-bus, which I believe is the one from the Webasto auxiliary heater, all modules known to be on the car can be accessed through INPA and I've successfully cleared the faults that were present. I have never been able to access the K-bus modules previously, and the Webasto has never worked, during my ownership. It seems the faulty module affecting the K-bus communications has altered somewhat over time, since the other K-bus modules worked fine until a couple of months ago. During this time, I've suffered various faults and errors which have come and gone. These included a frequent failure of the car to go to sleep (causing excessive current drain while parked); error message to say rear suspension is inactive; no rain-sensing wiper operation; occasional non-operation of the remote key to lock the car; non-operation of the indicator lights when locking the car; and probably some others that I've forgotten. Since disconnecting the Webasto from the K-bus, all of these faults have cleared and everything has worked properly all week. So if anyone is having wierd issued like this, first check your battery is good (mine wasn't so I replaced it) and then isolate the problem area and take a methodical approach to narrowing it down. Many thanks to the people who contributed to solving this problem, it's so nice to get in the car and not be confronted with error messages and boings from the dashboard all the time.
  2. The Colonel

    INPA can't connect to all modules on the car

    Thank you Clavurion for this information. My car was built in July 2003 so I suppose it has no LWR. The only other thing I thought I might find is the SZM centre console switch. My car only has DSC and PDC on this switch unit, plus a Trafficmaster, and these all have dedicated control modules so I'm guessing that probably doesn't require an SZM. Anyhow, I now have access through INPA to all the modules I need; I've cleared my airbag fault and hopefully identified the module (Webasto) that was previously preventing the car from going to sleep. I've had a few other odd faults but now I've cleared the error memories I'll monitor things and see what problems remain, if any.
  3. The Colonel

    INPA can't connect to all modules on the car

    Progress! I separated all eight K-bus wires from X10116 behind the glovebox and labelled them. Then I connected each one in turn to the wire from the IKE and ran INPA to look for the modules that I hadn't previously been able to see. Here are the results: Wire no. Module 1 IKE Instrument Cluster 2 EWS3 Immobiliser 3 Unknown - (no working module) 4 MRS4 Airbag 5 EHC Rear suspension 6 RLS Rain & Light sensor 7 IHKA Heater/AC control panel 8 ZKE3 General Module So then I connected all wires together except no. 3 and checked again that I could still read all these modules with INPA. I also read and cleared all faults stored in the modules. I noted that the IHKA reported a short on the Auxiliary Heater. Wire 3 presumably connects to a faulty module. However, there are four modules that I believe are fitted to the car, which I've still been unable to see in INPA. These are: LWR (Headlight Aim - car has Xenons), SZM (Centre console switch), GR2 (Cruise control) and the Webasto auxiliary heater. So I'll have to access the connectors on these modules to identify which one connects to wire 3. Does anyone have any idea why I can't see the other 3 modules?
  4. The Colonel

    INPA can't connect to all modules on the car

    You are right. I have now removed the instrument cluster (IKE) and positively identified the K-bus line from there to the multi-way connector behind the glovebox. It was in fact the one I had disconnected, so the K-bus was isolated and therefore none of the modules was visible to the OBD port. Unfortunately I ran out of time and haven't yet tried INPA again. However, I've never in the past been able to access many of these K-bus modules through INPA, so there may well be another fault on the bus. I will take it step-by-step and try connecting the K-bus wires individually to the IKE, checking INPA each time, and see what I find out. Thank you again for your help. I'm optimistic that I'll make progress tomorrow.
  5. The Colonel

    INPA can't connect to all modules on the car

    I think you're onto something here. I've decoded the modules listed on each bus in the diagram you referred me to and compared to the list of modules I can access using INPA. I've also searched for modules not listed to see which bus they connect to (K-bus or I-bus). I found that all the modules I can access are on the I-bus, and all those I can't access are on the K-bus. So it appears that I probably have a K-bus problem. I can't actually connect to any K-bus module. I have a high OBC cluster with widescreen. I have a Webasto aux heater, which seems to be a common culprit for K-bus issues. Also a Trafficmaster - can anyone confirm if this is a K-bus device? I've found a blown fuse near the battery for the Webasto, which has never worked in my ownership, so probably worth starting here and unplugging the unit behind the front wheel.
  6. The Colonel

    INPA can't connect to all modules on the car

    Thank you, yes I will try this. There seem to be several people reporting favourably on Cableshack and they seem to get access to all modules, so I will give them a call. I just wanted to be sure I hadn't missed something fundamental first.
  7. The Colonel

    INPA can't connect to all modules on the car

    Thank you. I don't recall seeing Functional Jobs or anything like it, but I'll check when I get home.
  8. The Colonel

    INPA can't connect to all modules on the car

    It's not a daft question, I'm pleased you're checking the basics because I feel there must be something fundamental wrong that I can't see. But yes, I have been selecting Old Models/E39. I've read somewhere that you can get a readout of all modules fitted (and working) on a car, but I've not been able to find the command for that. Is it an INPA function? If so, where do I find it?
  9. The Colonel

    INPA can't connect to all modules on the car

    So, thinking more about this issue where INPA can't access several modules on the car, I have come up with the following ideas as to what may be wrong with my setup to cause these modules to be unreachable: Incompatible or faulty cable Corrupted software installation or missing files I've done something wrong There's a fault in the car preventing these modules from communicating to the OBD port (note: my E39 is a 2003 model with only one OBD connector under the dash) As a reminder, I've used two different cables and two different INPA versions installed on two different laptops, yet the problem is much the same in each case. This suggests to me that items 1 and 2 above are not likely to be the problem, but I'm willing to be corrected if anyone knows differently. I'm assuming that the INPA installation includes files for all modules on the supported vehicles? I don't know about number 3, otherwise I'd fix it, so there is a possibility here. Anyone know of any 'gotchas'? Possibility 4 is something I've only just considered. Is it feasible that modules such as airbag, immobiliser, ZKE3, rain & light sensor etc. could be operating OK on the car, but can't communicate to INPA? Any thoughts/comments would be welcome. Also if anyone in the Berkshire area has a working INPA they'd be willing to try on my E39, please let me know.
  10. The Colonel

    INPA can't connect to all modules on the car

    I understand that the E39 uses two separate lines to talk to the modules, pins 7 and 8 on the OBD connector. You have to connect these two together inside the plug on your cable. Possibly the connection between the two has broken. Engine and gearbox are on one line (pin 7?), everything else I believe is on the other. Check your cable with a multimeter, you should have continuity between 7 and 8. If not, that might be your problem.
  11. The Colonel

    INPA can't connect to all modules on the car

    Yes, I can connect to several modules including steering angle sensor, KOMBI/IKE, LCM, PDC, Widescreen monitor, CD changer, telephone, video module as well as engine and gearbox. I can read and clear errors on most of these. I did solder together pins 7 & 8 on the VAGCOM cable, which I guess you were driving at. Stew99, thanks for confirming that you can read all modules on your E39. I've not been able to find any reference to other people being only able to read some modules; seems people have it working 100% or not at all. I did wonder if perhaps my original copy of INPA was missing some files, but finding the 5.06 version and trying that gives much the same result, so that doesn't appear to be the problem. I have had some K-bus issues recently (car wasn't going to sleep) and I did disconnect one wire from the K-bus multi-connector behind the glovebox - but I don't know which module's wire I disconnected. It's still disconnected and car now goes to sleep. However I've had my original OBD cable for 5 years and it's never connected to all modules, so I don't think this problem is likely to be caused by the recent K-bus issues. Does anyone know of a source of INPA that's proven 100% working? Most links I've found are dead.
  12. Hello, this is my first post on this forum; I've found lots of answers here previously, but can't find the answer to this one. My car is a 2003 E39 530D Sport Touring, and I'm having quite a few electrical gremlins at the moment. The battery was on its last legs so I've replaced that, but still have several issues to track down and want to check/clear some errors using INPA. The problem is, I can only read and reset errors on some modules on the car, other modules return the error: 'IFH0009 no response from control unit'. I'm using an old laptop running XP and INPA 5.02. I bought a USB-OBD EDIABAS cable which came with INPA and other BMW software. The installation worked for several modules and allows me to read and clear faults etc., but for other modules it won't connect. I did a lot of searching and found some guides which mentioned using a VAGCOM cable with FT232RL chip, so thinking the cable might be causing the problems, I bought one of these and installed a new driver for it. I still have the same problem, I can only connect to some modules. I also found online a later (mainly German language) version of INPA (5.06) and installed it under Windows 7 on another laptop. It also only permits access to some modules (I think the same ones) using either cable. Modules I can't access include the Airbag, Air Suspension unit, AC, Immobiliser EWS, Rain & Light sensor RLS, Cruise Control GR2 and Central Body Electronics ZKE3. I'm pretty certain all of these are fitted to the car. Does anyone else have similar problems, or can you access all the modules on your car using INPA?
×