Scan Tool Issues

[jedwards921]

Did you ever resolve this?

No. Through reading and asking around on multiple sites, it's been determined that if terminal 15 is present in the 20 pin connector, no handheld scanner is going to tap into any of the systems that use terminal 15. The only way to access is by going the laptop and software route. It gets really overwhelming real fast. I got sidetracked doing some other work to the car. I'll revisit this problem later. The car is drivable. ASC just doesn't work.

 

[Jack Ratt]

No. Through reading and asking around on multiple sites, it's been determined that if terminal 15 is present in the 20 pin connector, no handheld scanner is going to tap into any of the systems that use terminal 15. The only way to access is by going the laptop and software route. It gets really overwhelming real fast. I got sidetracked doing some other work to the car. I'll revisit this problem later. The car is drivable. ASC just doesn't work.

I have a 1997 pre facelift 2.8 and I tried all types of hand held scanners without very much success. I then went down the INPA route on an old laptop but found it a bit of a faff to be honest. On the older cars if you look at the 20 pin plug and if it has pin 15 live then your car can only be accessed by an ADS enabled scanner.

I bought myself a Foxwell NT520 scanner (now superseded by NT530) and I have been able to successfully access all the modules I have tried to interrogate. They cost around £150 but they are worth every penny in my opinion.

 

[jedwards921]

I have a 1997 pre facelift 2.8 and I tried all types of hand held scanners without very much success. I then went down the INPA route on an old laptop but found it a bit of a faff to be honest. On the older cars if you look at the 20 pin plug and if it has pin 15 live then your car can only be accessed by an ADS enabled scanner.

I bought myself a Foxwell NT520 scanner (now superseded by NT530) and I have been able to successfully access all the modules I have tried to interrogate. They cost around £150 but they are worth every penny in my opinion.

Wow. That amazes me. I'm using the NT530. Is it possible for you to tell me step by step how you did it in case I'm overlooking something? I've tried 2 cables and tried reading the modules that are on the ADS side and can't see any of them. I keep being told by several others there is no way this scanner will do it. I have to go the laptop and software route.

 

[Jack Ratt]

Wow. That amazes me. I'm using the NT530. Is it possible for you to tell me step by step how you did it in case I'm overlooking something? I've tried 2 cables and tried reading the modules that are on the ADS side and can't see any of them. I keep being told by several others there is no way this scanner will do it. I have to go the laptop and software route.

When I bought my NT520 both my ABS and ASC lights were on, and I struggled to diagnose the problem with INPA and other hand held scanners. It's been a while since I used it but if I remember correctly I had to manually input my VIN number into the scanner because for some reason the auto scan took ages to complete the scan. To be honest it never fully completed the scan because being an impatient so and so I stopped the scan.

However when I manually put the VIN number into the scanner it completed the process in just a few minutes and it showed a fault in ABS module. When I opened the file it said "front left wheel sensor, electrical fault" or similar words.
I fitted a new wheel sensor and then cleared the faults. When I started the car the lights were still on but went out after driving about 50 yards.

I haven't had any other problems to diagnose but I took it to Wales with me when we went to meet Hugh and Sarah @miller1098 and I did full diagnostic scans on both Hugh's Z3M and Sarah's twin vanos 2.8. Both these cars had historical faults saved so I cleared them, but didn't do a follow up scan to see if any of the codes reappeared. I'm sure Hugh said that both their cars were running well with no lights showing so I'm assuming everything is still good.

 

[Althulas]

I must have the same problem as you guys as my 10/1998 ///M is a pig to communicate with C130 but works like a charm on the wife’s Cooper S.

I was looking at the bccables site but they only have the USB cables and the software states from 1999 onwards puzzled why they don’t offer a serial cable version for ADS owners.

I’ve searched for a cable but no cigar but came across a couple of items

https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.co.uk/ulk/itm/264093101279 But don’t fancy something looking flimsy and DIY

A more expensive option

Car Diagnostic OBD 1 & 2 https://www.amazon.co.uk/dp/B004HU1E86/ref=cm_sw_r_cp_api_i_v3-BEbFHQ38HS

but adding the price of a decent laptop with a serial port the Foxwell is looking more appealing if the ASC can be accessed for bleeding brakes if required.

 

[jedwards921]

Here's what I'm experiencing with the NT530 and how I'm trying to use it. I connect to the 20 pin port and turn the ignition to run. I select BMW on the scanner. Next I have the option of selecting smart VIN or select manually from a standard list of BMW models. I choose smart VIN first option first. It reads the VIN but doesn't pull up the details. It still tells me to input manually. I do and it pulls up the correct build date etc. I start the auto scan. It reads a couple of things and gets stuck. Only option at that point is to unplug it.
If at the previous menu I select from the list of models manually, the oldest model Z3 offered is 3/98 whereas mine is a build date of 12/97. I try it anyway, and it just skips over everything except for engine data.

 

[NZ00Z3]

I can feel your the frustration with the NT530.

According to RealOEM your ABS is used in all the E36 cars. So try selecting an E36 car and see if it communicates. I checked out my NT530 and there is a date that separates the OBD1 and OBD2 cars. The older date lets you select the module you want to talk to. The newer date asks for the car model. Try both, but I suspect that the early model E36's were all OBD1.

If that does not work, then there is possibly a fault on the data line. Time to trace wires and disconnect modules until the data line comes clear.

 

[Robert Hill]

I'm working with a 98 Z3 with the 2.8 engine. I've tried 2 different scan tools without any luck. Yes, I'm using the 20 pin connector under the hood. Yes, both units are setup for BMW and have the latest updates installed. First, I tried the Creator C310. It seemed to do everything I wanted it to do, but it wouldn't communicate and read any part of the ABS system which it should. Next, I tried the Foxwell NT310. Same results, if not worse than what the C310 gave me.
One thing I noticed while working with the NT310 is that in the screen where you can manually select the vehicle you are working with, the oldest Z3/M52 combination listed is 3/1998. My car has a build date of 11/1997. Did something happen during these 3 months that is causing these scan tools to not work with this vehicle?
I found a couple of mentions about this specific issue with pre-facelift cars via search but haven't seen a good solution yet. Any ideas?

 

[Robert Hill]

I had the same problem so I installed INPA and Progman on old laptop found faulty ECU not communicating
Sent it to ECU testing got it back in 5 days total cost for rebuild and delivery and vat £350 z3 running great
If the ECU is ok it will only cost the price of the test
Hope this helps

 

[jedwards921]

I had the same problem so I installed INPA and Progman on old laptop found faulty ECU not communicating
Sent it to ECU testing got it back in 5 days total cost for rebuild and delivery and vat £350 z3 running great
If the ECU is ok it will only cost the price of the test
Hope this helps

What were your symptoms that led you to it, other than not communicating with the scanner?

 

[Robert Hill]

Code 94 DME not communicating and throttle valve system switched off that's why I used inpa software it's what bmw use and progman let's me recode parts ecu testing give lifetime guarantee by the way I am a electrician with 40 years of classic car rebuilds hope this helps

 

[Christ87]

I've managed to get hold of a Foxwell NT630 rather graciously lent from my mate after fishing with him today.
I have an ongoing ABS issue. Both front sensors have been replaced. Fault still present. However unable to get Comms.

 

[Robert Hill]

My ECU would not communicate with my soft ware so I sent it to ECU testing to have it rebuilt
It cost me £350 that included vat and pick up and delivery pick up on Monday and it was delivered on the Friday it was plug and play with a lifetime warranty and unlimited mileage you can see there set up on you tube I now have a 2020 ECU don't listen to people telling you to get a second hand with the same serial number your ECU is not communicating with any code reader if ECU testing find no fault it will cost £60
For the test hope this helps

 

[Christ87]

My ECU would not communicate with my soft ware so I sent it to ECU testing to have it rebuilt
It cost me £350 that included vat and pick up and delivery pick up on Monday and it was delivered on the Friday it was plug and play with a lifetime warranty and unlimited mileage you can see there set up on you tube I now have a 2020 ECU don't listen to people telling you to get a second hand with the same serial number your ECU is not communicating with any code reader if ECU testing find no fault it will cost £60
For the test hope this helps

Ah I should of explained. Engine diagnostics works perfectly so I assume everything is fine there. It's the comms to the Stability control/ABS unit where it won't communicate with.
Thanks anyway

 

[NZ00Z3]

Is the ABS the only module that the scanner will not talk to?

 

[jedwards921]

i finally solved all of my problems a couple of weeks ago. For me, with the pre-facelift 98, I had to go the suggested route of finding an old laptop, getting an ADS cable, and the software. Took a little time to get it all, but in the end my problems are fixed. The handheld scanners simply will not work 100%, if the car still uses some ADS technology.

 

[Robert Hill]

You can't communicate direct to the Abs module how it works is the Abs module monitors wheel speed
And communications to ECU that all is well if you have a faulty wheel sensor the Abs thinks the car is in a skid and communicates to the ECU to close the engine throttle and light the ABS on the dash I take it you have tested the wheel sensors and removed the ABS module to check it for damage ie water ingres
Be carefully when removing the ABS module plug as it pulls up and moves back
Hope this helps

 

[Jack Ratt]

i finally solved all of my problems a couple of weeks ago. For me, with the pre-facelift 98, I had to go the suggested route of finding an old laptop, getting an ADS cable, and the software. Took a little time to get it all, but in the end my problems are fixed. The handheld scanners simply will not work 100%, if the car still uses some ADS technology.

A number of members here swear by INPA but I couldn't get on with it. My Foxwell NT520 Pro is ADS compliant and accesses all my cars modules. I have 2 x pre facelift 2.8's. The C110 and the other cheaper handheld scanners that I tried wont read ADS.

My INPA stuff is now redundant, except the old laptop, that's well past f****d. I think I paid around £70 for the ADS interface and add to that the old laptop and other cables and software and you are right on the price for a Foxwell at £150ish

 

[Christ87]

You can't communicate direct to the Abs module how it works is the Abs module monitors wheel speed
And communications to ECU that all is well if you have a faulty wheel sensor the Abs thinks the car is in a skid and communicates to the ECU to close the engine throttle and light the ABS on the dash I take it you have tested the wheel sensors and removed the ABS module to check it for damage ie water ingres
Be carefully when removing the ABS module plug as it pulls up and moves back
Hope this helps

I've not touched the module yet but I'll check it next.
The O/S sensor was full of rusty crud and I thought hey presto quick swap of sensors but that wasn't the case.
The faults gone from intermittent to permanent. I checked a couple of times with my cheap e bay scanner. Nothing. Then one day for no real reason I scanned again and got a sensor fault. "Vehicle speed sensor A". But I've never been able to scan this again and since found with some digging this to be pretty generic.
All of this was before I touched or fettled with anything so I've not caused the permanent fault I assume something has gradually failed over time and is now basically properly failed.
I've swapped out the front sensors and the rears seem visually ok. I was hoping to probe these at some stage for continuity.
It has occured to me perhaps there's a comms area from the module to the ECU or a failure of some kind in the module. Ah well I'm on furlough for a bit longer so something to do.

 

[JaydJeen]

Hey! I'm just curious if there's any update