Car diagnostics online – what to do, step by step
A warning light has come on, the vehicle drives differently from usual – and the question is not how diagnostics works in theory, but what you should do in the next few minutes. This page is built as a sequence of actions: first record the fault properly, then decide whether to keep driving, then have the data read out and assessed.
Once the data has been sent, you usually receive an analysis report within one hour of complete data arriving, with a traceable assessment and recommendations for the next test steps – around the clock, at night and at weekends too, independent of repair work and parts sales.
Have your diagnostic data checked
When this approach is worthwhile
Not every irregularity needs an immediate garage appointment. The order set out on this page makes sense above all in these cases:
-
A warning light has newly appeared and you do not know how urgent it is.
-
The vehicle has noticeably lost power or is in limp-home mode.
-
The fault only occurs from time to time and is not present during the garage visit.
-
You have read out a fault code or been handed one and do not know what to make of it.
-
You are asked to approve the replacement of a component and want to understand the data first.
-
The fault memory has already been cleared and you are wondering how to proceed now.
-
You are out on the road and have to decide whether to continue the journey.
-
You want to prepare the garage visit with a clear question instead of starting it open-ended.
Safety first. If the engine warning light is flashing, if there is a severe loss of power, smoke, a smell of fuel, unusual noises, or anything unusual about the brakes or steering, do not keep driving the vehicle. Have it checked on site first – a data analysis is no substitute for an inspection of the vehicle.
How to record the fault properly
What happens in the first few minutes often decides how much a later assessment can yield at all. Diagnostic data is perishable: part of the information disappears as soon as the fault memory is cleared, or once the symptom has not occurred for a while.
Do not let the fault memory be cleared before it is documented
This is the most common and at the same time the most expensive mistake. Clearing removes not only the fault code but also what explains it: the freeze frame data from the moment it was stored, how often the entries occurred, and the order in which they arose. That is exactly what shows whether an entry was a cause or a consequence. So ask for the fault memory to be printed or exported first, and only reset afterwards – if at all.
Note the circumstances at once, while you still remember them
A few lines on your phone are enough. What matters: driven cold or warm, at idle or under load, at what speed, in which gear or driving situation, in what weather, since when the behaviour has occurred and how often. For the assessment these details are often just as telling as the fault code itself – and after two days nobody remembers them precisely.
Photograph what can be seen
Photograph the instrument cluster with the warning light lit, while it is lit. With the read-out device or the app: capture the whole screen, not just the top line. A single code typed out by hand is hard to place; a complete screen with control unit, fault status and values is not. If there are several pages: photograph all of them.
Gather receipts and replaced parts
Invoices, cost estimates and a list of the parts already replaced belong with the data. They show what has already been ruled out and prevent the same trail being followed twice. A note about a weak battery, a jump-start or a recently disconnected connector is relevant too.
Do not change several things at once
If a component, the software and the fuel are changed in one go, afterwards there is no telling what took effect – and what did not. Change one thing where possible, then drive under the conditions in which the fault occurred, and read out again. That applies to seemingly harmless measures such as disconnecting the battery as well.
If the fault memory has already been cleared
That is no reason to give up, but it does make the old print-out worthless. Drive the vehicle so that the symptom occurs once more – under the same conditions as the first time if possible – and have it read out again afterwards. A fresh read-out after the fault reappears says more than an old print-out. Mention the clearing explicitly when you send the data; it explains why frequency and history are missing.
What you have to decide in the next few hours
The practical question is usually not “what is broken” but “can I still drive it”. The three situations below are rough orientation, not a judgement of your vehicle. Whether your vehicle is roadworthy and safe in your particular case can only be established by an inspection on site – when in doubt, the more cautious option always applies.
Stop and have it checked
Flashing engine warning light, severe loss of power, smoke, a smell of fuel, unusual noises, anything unusual about the brakes or steering, warnings for oil pressure or coolant temperature lighting up: in these cases you should park the vehicle and have it checked on site rather than drive on. A data assessment can wait; engine damage cannot.
Carefully as far as the garage
Engine warning light on steadily with nothing else unusual, noticeably limited power in limp-home mode, rough running without noises: often the vehicle can still be moved as far as a garage – driven gently, without high load, without a long motorway stretch and without a trailer. If the behaviour gets worse on the way, the first point applies.
Observe and sort it out calmly
A message that came once and disappeared again, a comfort or assistance function that drops out, slightly higher consumption with no other symptoms: here there is time to document the fault properly, have it read out and have the data assessed before an appointment is made. What matters is only that you do not let it rest – a sporadic entry has a cause too.
The process for you, in four steps
1. Record
Photograph the warning light, note the circumstances, let nothing be cleared. Five minutes that make the difference later.
2. Have it read out, or read it out yourself
Ask the garage for the log of the fault memory read-out, or read it out yourself. Which routes there are for that and what they deliver is set out in detail under online vehicle diagnostics.
3. Upload
Send vehicle data, symptom description and diagnostic data through the form. Complete exports are better than single codes.
4. Receive the analysis report and go to the garage
You receive an assessment with a prioritised list of possible checks – and with it a concrete question for the garage visit, instead of an open-ended search for the fault charged by the hour.
What data the assessment needs
Required
-
Vehicle data: VIN (17 characters; the letters I, O and Q do not appear in it), model, engine, year of manufacture and mileage.
-
Description of the symptom: when the behaviour occurs – right after starting, under load, on the motorway, with a cold engine or only after a longer drive. Since when, how often, under which conditions.
-
Diagnostic data: diagnostic tester export, fault memory print-out or app export with control unit, fault code and fault status.
Helpful, if available
-
Freeze frame data with engine speed, coolant temperature, engine load or vehicle speed.
-
Live data and target/actual comparisons.
-
Screenshots from an OBD app and photos of the warning lights.
-
Invoices for work already carried out and a list of replaced parts.
-
Any indication that the fault memory was cleared, that the battery was weak or that a connector was recently disconnected.
How to make your data usable Send the complete log wherever possible rather than a code typed out by hand. Screenshots only help if every value is legible and not just the top line of the screen is shown. Photos should be sharp and show the entry in full. A special diagnostic tester is not a requirement – existing print-outs, photos or app exports are often enough, provided the fault description is meaningful.
How the analysis works
-
Describe the problem – Give the vehicle model, engine, year of manufacture and mileage – and describe when the symptom occurs.
-
Send the data – Upload fault codes, diagnostic logs, freeze frame data or screenshots through the form.
-
Assess the connections – MotorScope compares the data with the symptoms you described and the work carried out so far.
-
Receive the analysis report – Usually within one hour of complete data arriving, you receive your analysis report with a traceable assessment and a prioritised list of possible checks.
What the online assessment does – and what it does not
What the online assessment does
-
Puts fault memory, live data and symptoms into context
-
Shows which measurement is most likely to bring clarity next
-
Makes a repair recommendation verifiable before you approve it
-
Prepares the garage visit with a clear question
-
Is independent of repair orders and parts sales
What it does not do
-
Repairs and parts sales
-
Approving repairs or certifying roadworthiness
-
Replacing a personal inspection of the vehicle
-
Swapping parts on suspicion, or a guarantee of success
-
Replacing the German MOT (HU), the emissions test (AU) or any other legally required inspection
If the data does not show a clear picture, the report says so explicitly. Rather than settling on a cause prematurely, it shows which check will bring the most clarity next.
Frequently asked questions about the approach
The garage wants to clear the fault memory. Should I agree?
Ask for a print-out or export of the read-out state first. Once that state is documented, there is little against a reset – without documentation, freeze frame data, frequency and the order of the entries are lost and cannot be recovered.
I did not photograph the fault and the light is off again. Is it too late?
No. In many cases the entry stays stored in the fault memory even when the light goes out. Have it read out and describe as precisely as possible when and under what conditions the symptom occurred.
How long should I wait before reading out?
Preferably not long. The closer the read-out is to the symptom occurring, the better the freeze frame data and the fault pattern fit together. If the fault only occurs sporadically, a read-out shortly after the next occurrence says more than one weeks later.
I have already replaced parts and the fault remained. Is an assessment still worth it?
Yes, and in this case the list of replaced parts is especially important. It shows which trails have already been followed and steers the assessment towards the remaining possibilities.
Can I describe several symptoms at once?
Yes. It is best to describe them separately and with the time each occurred. Several irregularities not infrequently share a common starting point that only becomes visible in context.
What do I do if I am on the road with no garage nearby?
Decide first, using the safety notes, whether continuing to drive is defensible. The assessment itself does not depend on location and is possible around the clock, but it does not replace an inspection of the vehicle.
How quickly do I receive the analysis report?
Usually within one hour of your complete diagnostic data arriving – around the clock, at night and at weekends too. If the data is incomplete or illegible, a short query comes first; the turnaround time then starts when the missing details arrive.
What does the assessment cost?
The online assessment costs a one-off €19.99 incl. VAT per vehicle and assessment. If MotorScope is to take the data at the vehicle itself, that is available as a mobile analysis; the terms and the travel costs are set out under online vehicle diagnostics.
You will find further answers under All questions and answers.
Understand the data first. Then act with purpose.
Upload your diagnostic data and receive an independent assessment usually within one hour – before you order the next part.