HI everyone - just had ABS/Stabilisation ,Front Assist unavailable, errors - which could be a wheel speed sensor.

I have a MAxiECU scanner with the Skoda module, and when I interrogate 11 modules I get the following report:

Can anyone help me decode the numbers.

System: Brake System
ECU Name: Bosch 9 ESP (UDS)

000271 Permanent Unknown fault code
000224 Intermittent Unknown fault code
000194 Intermittent Unknown fault code

 

System: Brake System
ECU Name: ABS/ESP (UDS)

0x000271 Permanent Unknown fault code
0x000224 Intermittent Unknown fault code
C10B422 Intermittent Vehicle deceleration; upper threshold exceeded

 

Have you or anyone else been coding these items or perhaps fitted new parts?

 

Have you got one of these DSG/auto type gearboxes?

 

 

6 hours ago, peter51 said:

when I interrogate 11 modules I get the following report

Have you tried doing a general error report and got any error codes, if so did you try deleting them all then driving the car for a while to see if any returned?

 

Do you actually have a problem with the car (warnings or lights) or is it the MaxiECU that is reporting a fault and may be at fault itself with its programming?  Is your MaxiEcu fully up to date for VWSkoda models in your region?

 

The German marques generally have very complex intertwined computer programming so need specialised program scan tools, lower priced scan tools may throw up their own difficulties with the car, if you have access to another higher level and/or more VW scan tool to check what results that gives to confirm or deny the MaxiEcu?

 

 

I'm surprised in Aus you buy European cars when Japanese cars seem the much more obvious choice, do VW sell Skodas at low prices in Aus?

 

Thanks for your reply.

No coding and no new parts fitted. It is a 5 speed manual CJZD engine Fabia 2017 MKIII.

I purchased MaxiEcu because it was a European company based in Poland - thinking this scanner would be great for all European cars.

Unfortunately it has been the opposite experience for VAG diagnostics. I have reported such issues several times to customer support in Poland - but no luck. However it does have some good features with other brands so its not going in the bin yet.

 

There were 3 errors reported on the message centre which are fairly common if there is a wheels speed sensor issue.

The problem is to find out which sensor on which wheel so I dont have to pull out the oscilloscope to check each wheel sensor. 

I scanned all the modules and the errors above were reported - but these numbers need to be decoded into an OBD code or some other plain language.

I put these numbers in google with no luck hence I posted here.

 

Skoda has a reasonable following in Australia - along with VW/Audi - albeit we are a very tiny market.

I bought this MKIII Fabia new - it was very cheap at the time. The car is extremely enjoyable to drive and I have just done 81,000 miles without an issue. 

Japanese cars are well made but have no soul. I could have bought a Honda but it was noisy inside, was poorly appointed and the stereo sounded like one from the 90,s.

 

Maybe someone can recommend a good scanner model for this car - one that is bidirectional.

Here VCDS (previously VAG-Com) is favourite, a to me horrible looking presentation (like programs from the 1990s or before) legacy system but many are used to it and like it.  There's only one pin in Sydney for Briskoda owner.  I've never seen it but I think you can bang it on an old laptop to make it a dedicated machine but I don't know.

 

Otherwise I guess the usual names that have their hardware, cases and connectors all made at the the same places in China (and who knows stolen software bits from China), but those do depend on the model even with the same manufacturer/provider for how good the programs on it are and of course you can use it on loads of other makes and models.  A neighbour had a TopDon that covered can/van makes I'd never heard of out your way but it did have it's limits for my wife's 2015 Fabia but certainly had bi-directional capabilities.

 

Having Googled the numbers I wonder if it's the sensors or just the wiring or connectors to them a better scan tool would pin this down more (but probably be the sensors given all the posts about this for VWs) and a better scan tool would say which sensor if it is the sensor, could be other of course.

 

I've owned a few Japanese cars (always very reliable) and they were more interesting models but I can understand some models might lack spirit (as German cars generally do for me) but when we had to replace things like front dampers when I know others with 20+year old and 28+ year old Toyotas still on all factory suspension I'd find them less boring. 😆

 

We only got to 20,000 miles before the first issue and had other issues after that and have ongoing niggles, so our lost is your gain, or visa-versa. 😆

 

I bought my Skodas in the mid to late 1980s (before VW took over, and actually the quality dropped initially with them) and they were different, very cheap and fun to drive (rear-engine, RWD) now it's just VW making them cheaper so as not to spoil their named brand (and formerly making them heavier so they didn't go quicker than the VW models too apparently).

 

Good luck, someone might be along here with all the info you need or past experience to help you.

 

8 hours ago, peter51 said:

Maybe someone can recommend a good scanner model for this car - one that is bidirectional.

bidirectional ?

 

OBDEleven works on VAG cars, and I use it on all three VAG car that I have.

https://obdeleven.com/

 

Thanks. AG Falco

Thanks for the recommendation - Ill have a look at it.

Bidirectional tools make diagnostics easy because you can actuate many components - so you can verify communication pathways and or voltage drops/relay function along the actuation wiring.

A bit like but more than taking a live or earth supply to a component to see if actuates, if the component actuates then you can look for an issue in the power supply (or communication.

 

All scan tools are only another diagnostic tool that require correct interpretation and conformation of the info they give, sometimes they point to the culprit but certainly not always, many using a scan tool might replace a part when it's merely shooting the messenger not solving the issue.

 

 

Solved -  by updating to the latest software for my scanner - cost another 65USD. There were some fairly large database files and a firmware upgrade for the bluetooth dongle.

This time The DTC,s were correctly decoded and suggested the right rear wheel speed sensor.

This was confirmed by graphing each wheel speed sensor output via the new software - finding a dealer with the part in stock was the hard bit.

20minutes to change it and all back to normal.

Thanks for inputs from other posters.

 

On 06/05/2024 at 11:12, nta16 said:

Is your MaxiEcu fully up to date for VWSkoda models in your region?

Some makes of scan tools have info sent from users to help with updates, you might have to enable this feature, obviously the more users that have their reports sent to the scan tool maker that their programs have issues the quicker and better the updates with be.  You can also I think send photos if you have a camera on the scanner.  Some also have user forums that can be good. too.

 

Many professionals (and non-professionals) are too lazy to carry out full updates and forget this when they plug into a make/model/year for a first time.  I used to always update my neighbour's scanner before I borrowed it (and fully charge the battery) and some of the available updates were interesting, the files for the VW Phaeton were huge, not that we would ever see such a beast, and I guess more about halo/ego marketing for the scanner maker given the level of scan tool my neighbour had.  And stuff for Asian market commercial vans from a brand I had never heard of, but my neighbour had as he has a very compressive motor car website. - https://motor-car.net/