Tell us which warning light came on and what your car was doing at the time. We’ll confirm which scanner checks your vehicle supports, explain the findings and agree on the next step with you.
Diagnostic information updated 29 October 2026 · Independent multi-brand workshop
Tell us the vehicle’s year of manufacture, variant, engine or fuel type, and the exact warning message. Different versions of the F8 Spider may have different control units and require different diagnostic access.
Read the service guide for the Ferrari F8 Spider →
This is a model-specific enquiry page. The workshop can confirm which checks your model year and control system support.
CarTech Hub uses LAUNCH Scan Plus X and XTOOL Compass for scanner-assisted fault finding in Sawkuchi, Guwahati. Share your car’s make, model, year, fuel type and warning message so we can confirm the relevant scanner coverage before your visit.
Ask about a Scan Plus X check when reporting a warning light, starting problem or electronic-system concern. We first confirm communication with the relevant control unit and the diagnostic functions available for your vehicle.
The installed software, vehicle year, engine and control unit determine which checks are possible. Code reading, live-data checks and service functions are confirmed for the job before work begins.
LAUNCH official vehicle-coverage resource ↗XTOOL’s Compass information lists fault-code reading and clearing, live data, freeze-frame information, actuator tests and reports from scans before and after work. Availability depends on the vehicle and supported system.
We use the relevant information to investigate your complaint and explain the next check. XTOOL lists Compass and Compass Master configurations separately, so optional hardware and programming access are confirmed for each task.
XTOOL official Compass product information ↗We accept scanning enquiries for Indian, Japanese, Korean, European and other car brands. A brand or model listing does not confirm access to every control unit. The vehicle’s ECU, software version, licence, security access and any required accessories affect the work we can accept.
Ask separately about service resets, adaptations, coding, programming, ADAS calibration or EV high-voltage work. These need the right equipment and procedures; they are not automatically part of a basic scan. A fault code helps direct an investigation and does not by itself prove which part needs replacing.
XTOOL vehicle and function lookup ↗ Find your brand and model →
CarTech Hub first records the warning and the driving conditions in which it appeared. On supported vehicles, the technician reads the engine, ABS or airbag control module and checks whether its fault codes are current or stored. For an engine complaint, freeze-frame data and sensor readings can show the engine’s operating conditions when the fault occurred. For ABS, individual wheel-speed readings can help isolate an inconsistent signal. An airbag warning calls for a restraint-system assessment using the manufacturer’s procedures. The technician explains any further tests and discusses the repair estimate with you before you approve the work.
A fault code is one clue. The technician compares it with the symptoms you describe and the condition of the vehicle before recommending further checks.
Share the vehicle details, warning message, recent work and the conditions in which the issue appears.
We check whether the scanner supports the system you want tested and agree with you on what the initial assessment will cover.
Available codes and data guide further electrical or mechanical checks. A stored code alone does not justify replacing a part.
Discuss what is confirmed, what still needs testing and the estimate before approving further work.
Where appropriate, repeat relevant checks and review the original complaint. Clearing the warning light alone is not a completed diagnosis.
The directory has 765 model entries across 36 brands, including earlier generations and variants. Choose your car and tell us its model year, fuel type, variant and warning message. The workshop will confirm which control units it can check and which repairs it can undertake.
70 matching model entries · Showing 1–24 · Browse Ferrari diagnostics
Coverage depends on the model year, control unit, software and access requirements. Tell us the symptoms or warning message so we can check whether the relevant function is supported before you visit.
A code records a condition detected by the car. A technician may need to inspect wiring, power supply, mechanical components or operating conditions before recommending a replacement.
Programming and calibration are separate jobs. Before booking, ask what hardware and software access the work requires, whether a trained technician is available and what the work would cost for your vehicle.
Bring your vehicle details, a description of the symptoms, relevant service records and any earlier scan report. Tell us about recent battery work and whether anyone cleared the fault codes.
The Spider’s two-section retractable roof adds a distinct diagnostic question. Confirm the actual roof functions and supported procedures. An engine connection on the shared family does not establish roof-controller or initialization capability.
Record the stage where movement stopped and the message, without repeated cycling. Include recent body, roof or supply work. These facts help define the enquiry without assuming which latch, sensor or mechanism caused the interruption.
Use the correct dual-clutch application and complete operating context. A reported value is not a universal remaining-life guarantee. Ask which supported findings justify the next test or repair and which mechanical questions remain unassessed.
Clearing a message does not verify panel fit, seals or physical attachments. Record movement and water-entry concerns separately. The accepted roof inspection and any electronic procedure should produce distinct findings rather than a single implied restoration result.
Provide earlier reports, intake or exhaust changes and the conditions of the warning. The actual twin-turbo build must guide interpretation. A component name in a code does not by itself establish a failed turbocharger or required replacement.
No software or calibration task follows automatically from code reading. Confirm the relevant system, authorized access and accepted procedure for this build. The report should retain unsupported roof, drivetrain or body functions as explicit limitations.