Let go of my Lego

James looks at how the interconnected car can cause you headaches

By James Dillon |

Published:  03 May, 2017

"Electronic Lego" is a phrase that was introduced to me by an engineering manager when I worked for the diagnostic company Crypton around 25 years ago. In the late 1980s the Company had developed engine tuning machines which moved away from bespoke central processing units (the so called Big Box tuners) to a PC based system. The elements of the PC based system could not just be bought and fitted together (like lego) and be expected to work. The PC components and peripherals had to be carefully selected, including the compatibility of their drivers and software to ensure a robust PC based diagnostic machine could be created. Over the past 10 years or so motor vehicles have moved away from their previous Lego like construction, where replacement parts were free to be plugged in and replaced at will. The change was due partly to the modern vehicle being constructed as a rolling network of computers and partly to the advent of the factory fitted immobiliser, where transponder keys and the relationship between vehicle computers became prevalent.


Anything remotely related to the immobiliser (instrument panel, body computer, engine computer, etc.) required coding. The coding process synchronised the new part which was foreign to the system. Information was exchanged relating to the vehicle VIN number, the start point for rolling security codes was synchronised and the vehicle system registry was updated with regard to the replacement component. This entire process was carried out offline. The processes were invoked by a scan tool with suitable functionality and the vehicle could "self-update" without having to refer to the big bad world of the internet. Definitely not electronic Lego. In some cases, the vehicle manufacturer would require independent workshops to register to enable them to have access to security PIN code retrieval (in case the customer lost the original vehicle security PIN information). This type of setup could preclude independent workshops from carrying out certain tasks, unless they were equipped with the correct scan tool and unless they had registered with the relevant vehicle manufacturer regarding authorised access to retrieve security PIN codes, which, in itself was onerous.


Over the past couple of years we have seen a new dimension; the online aspect of vehicle coding and programming. This new dimension, sometimes loosely referred to as DoIP, sees the vehicle having to be connected to the vehicle manufacturer server, via a vehicle to network interface, to enable the interchange of data to occur. The workshop involved (and in some cases the individual vehicle technician) must have a valid login to the relevant vehicle manufacturer server. Vehicles that conform to this DoIP protocol undergo a validation process once they are connected to the server. Access to vehicle manufacturer web portals usually has two tiers of access, the first provides access to technical information and usually some form of basic vehicle electronic access. The second requires formal authorisation and will open up security related functions. Once vehicles are connected, an online validation process occurs. Depending on the vehicle manufacturer, this can range from a simple validation of the VIN, right up to a full computer scan of VIN, part number and software version management. This is the point at which the situation can become particularly interesting and is best explained by a real-world example.


Imagine a vehicle which, at some time in its recent past, suffered an issue with a component such as an airbag, an entertainment or instrument module. Buying a new replacement module was prohibitively expensive and so the vehicle owner sourced a used module. Garage A fitted the used unit, but discovered that it did not function correctly as it was subject to the guardianship of a system called component protection (a system designed to restrict the market for stolen cars/parts). Garage A did not have the required access or authorisation to the vehicle manufacturer server, so they called out a guy who had a tool which could solve the component protection problem and the unit was unprotected using this tool, most likely of Eastern European origin. The module worked correctly and everyone was happy, for now. Seems like electronic Lego doesn't it? Sometime later, and perhaps after a change of ownership, the vehicle develops a symptom which requires analysis. The new owner lands at Garage B who search for technical service bulletins using the vehicle manufacturer portal and discover that there is a software update for the engine and transmission computers which will solve the customer's reported symptom. The vehicle is booked in and Garage B connects the vehicle to the manufacturer server via their account. As its first step, the system performs a software version check (all of the fitted components are checked for software version and VIN) to ensure that the engine and transmission are running the older, problematic version of software. The vehicle fails this check and is ungracefully ejected from the process which now cannot be completed for no apparent reason. Garage B reports back to the customer that the vehicle requires further investigation and the customer agrees to rebook the vehicle. In the following days, Garage B receive a telephone call from the police vehicle crime unit. They have received a call from the vehicle manufacturer who had identified a stolen computer during a scan of a vehicle connected to their server from garage B. They have the VIN, the vehicle make and model and the time and date and computer from which the vehicle was connected. They want to know the why, what, who and where of the vehicle. Oh! Definitely not electronic Lego now and this mess will require much metaphorical elbow grease to clean up.


There are obvious implications which are beyond the scope of this article, but the situation described here is real and is affecting workshops now. The use of OEM anddealer equipment by go-ahead businesses is growing and the implications of situations as described here must be considered. Training and education for garages is a big part of this and in order help garages, we have recently added manufacturer specific diagnostic equipment courses to our training programme.


James, through Technical Topics is running a range of vehicle manufacturer diagnostic equipment & software training courses the first of which cover VW & Audi and Vauxhall/Opel. Call 01278 428 699 for details and booking.

Related Articles

Most read content


Sign Up

For the latest news and updates from Aftermarket Magazine.


Where should the next Automechanika show be held?


©DFA Media 1999-2019