A professional vehicle diagnosis should normally begin with a complete overview of the electronic systems installed in the vehicle or equipment.
Reading only the engine ECU may reveal an engine fault code, but it can miss related problems stored in the transmission, braking, suspension, aftertreatment, body, trailer or communication systems.
A JalTool full system scan helps technicians identify supported control units, record active and stored diagnostic trouble codes and build a structured starting point for the repair.
After the repair, a second scan and diagnostic report can help confirm which faults were corrected, which codes returned and which systems still require attention.
This guide explains how to use JalTool full system scanning, live data, actuator tests and diagnostic reports as part of a professional workshop, fleet or mobile diagnostic workflow.
What Is a Full System Scan?
A full system scan is a diagnostic process that attempts to communicate with the supported electronic control units installed in a vehicle, machine or connected system.
Depending on the application, the scan may include:
- Engine control system
- Transmission control system
- ABS, EBS and brake controllers
- SCR, AdBlue and exhaust aftertreatment systems
- Suspension and steering systems
- Instrument cluster
- Body and comfort controllers
- Trailer electronic systems
- Retarder control system
- Auxiliary equipment controllers
- Vehicle gateway and communication modules
The number of detected systems depends on the manufacturer, model, production year, vehicle configuration, diagnostic connector and installed controllers.
A Full Scan Is a Diagnostic Overview
It identifies supported systems and available faults. It does not automatically identify the physical cause of every code or complete the repair.
Technicians must continue with live-data analysis, circuit testing, component inspection and supported service procedures.
Why Scan Every Supported System?
Find Related Faults
An engine problem may also create transmission, aftertreatment or communication faults in other controllers.
Identify Network Problems
Several modules reporting communication faults can indicate a shared power, ground, CAN or gateway problem.
Record the Initial Condition
A pre-repair scan documents the electronic condition before fault codes are cleared or components are replaced.
Avoid Unnecessary Parts
Comparing faults between systems can prevent replacement of a component that is only reacting to another problem.
Verify the Repair
A post-repair scan helps confirm whether relevant faults remain active or return after testing.
Create Customer Records
Diagnostic reports provide organized information for workshop files, fleet records and customer communication.
Full System Scan vs Manual ECU Selection
| Method | Main Purpose | Best Use | Possible Limitation |
|---|---|---|---|
| Full System Scan | Checks multiple supported controllers and records an overall fault overview. | Initial diagnosis, vehicle inspection and final verification. | May take longer and may include unrelated historical faults. |
| Manual ECU Selection | Opens one selected electronic system directly. | Detailed diagnosis after the relevant controller is identified. | Can miss faults stored in related systems. |
| Quick Fault Check | Provides a faster view of available trouble codes. | Preliminary workshop screening. | May not provide the same depth as individual system diagnosis. |
| Post-Repair Scan | Rechecks systems after repairs and fault clearing. | Repair verification and report preparation. | Some faults require an operating cycle before they can be tested. |
Use the full scan to find the diagnostic direction. Use individual ECU access to investigate the fault in detail.
Pre-Scan Before Beginning the Repair
A pre-scan should be completed before clearing codes, disconnecting batteries or replacing electronic components whenever practical.
Record:
- Vehicle or equipment identification
- Production year
- Engine and transmission information
- Current mileage or operating hours
- Customer complaint
- Warning lights and display messages
- Detected electronic control units
- Active diagnostic trouble codes
- Stored or historical trouble codes
- Available fault descriptions
- Communication failures
- Relevant live data and freeze-frame information
Do Not Clear Fault Codes Before Saving Them
Clearing codes can remove information about the original fault condition, including status, frequency or available operating data.
Save the pre-scan and relevant screenshots before changing the vehicle.
Active, Stored and Intermittent Fault Codes
| Fault Status | General Meaning | Workshop Interpretation |
|---|---|---|
| Active or Current | The controller currently detects the fault condition. | Diagnose the relevant circuit, value or operating condition before clearing. |
| Stored or Historical | The fault occurred previously but may not be present now. | Review its relationship to the complaint and recent repair history. |
| Intermittent | The condition appears and disappears. | Inspect wiring, connectors, vibration, temperature and operating conditions. |
| Communication Fault | Expected messages from another controller were missing or implausible. | Check power, grounds, CAN circuits and whether the related module is operating. |
| Pending or Not Confirmed | The system detected a possible fault that may require another operating cycle. | Record it and complete the correct verification conditions. |
Exact status descriptions vary between manufacturers and electronic systems. Interpret the terminology shown for the selected controller.
Why Fault Codes Should Be Compared Across Systems
Electronic control units share information through the vehicle network.
For example:
- An engine-speed signal fault may affect transmission shifting
- A low-voltage event may create faults in several ECUs
- An ABS wheel-speed fault may affect stability and transmission systems
- An engine fault may disable a DPF regeneration request
- A gateway problem may create communication faults across the vehicle
- A trailer power problem may appear in both tractor and trailer systems
Replacing every component named in every controller would be inefficient and expensive.
Look for the fault that can explain the largest number of related symptoms.
Using Live Data After the Full Scan
Fault codes identify the area in which the controller detected a problem. Live data helps show what the system is reporting now.
Depending on the supported ECU, JalTool may display:
- Engine speed and load
- Temperatures and pressures
- Sensor voltages
- Switch and pedal status
- Wheel speeds
- Transmission positions
- Clutch or actuator values
- DPF and SCR information
- Battery and supply voltage
- Requested and actual values
- Controller configuration and status
Compare Related Values
A single value is often less useful than a comparison.
Useful comparisons may include:
- Requested pressure vs actual pressure
- Requested actuator position vs actual position
- Multiple temperature sensors on a cold engine
- Individual wheel-speed channels
- Upstream vs downstream NOx values
- Battery voltage in several controllers
- Pedal request vs throttle or brake response
Using Data Graphs
Supported graphing can help technicians observe values that change over time or under load.
Graphs can be useful for identifying:
- Intermittent sensor dropouts
- Slow pressure buildup
- Unstable supply voltage
- Unexpected temperature changes
- Wheel-speed differences
- Actuator response delays
- Requested and actual value deviations
Record the operating conditions during the test so that the graph can be interpreted correctly.
Live Data Is Not Automatically a Component Test
An implausible sensor value may be caused by the sensor, wiring, connector, power supply, mechanical condition or ECU input circuit.
Using Actuator and Component Tests
After reviewing fault codes and live data, a supported actuator test may help determine whether the ECU can command a component.
Depending on the system, supported tests may operate:
- Relays
- Solenoid valves
- Fuel injectors
- Cooling fans
- Throttle or EGR actuators
- Transmission actuators
- ABS or EBS valves
- AdBlue pumps and dosing components
- Warning lights or buzzers
- Suspension valves
Secure the Vehicle Before Active Tests
Actuator tests can move mechanical parts, operate valves, start fans or change hydraulic, pneumatic and electrical conditions.
Follow the displayed instructions and keep personnel away from moving, hot or pressurized components.
A Successful Actuator Test Does Not Prove the Complete System
An active test may confirm that:
- The diagnostic tool can communicate with the ECU
- The ECU accepts the command
- The electrical circuit responds
- The component produces an audible or visible reaction
It may not confirm:
- Correct output under full load
- Correct fluid or air pressure
- Correct mechanical movement
- Correct flow rate
- Correct performance during normal operation
Combine actuator tests with electrical, mechanical, pressure and performance checks.
Professional JalTool Diagnostic Workflow
Record the Customer Complaint
Document warning lights, symptoms, operating conditions, recent repairs and when the problem occurs.
Identify the Vehicle or Equipment
Record the manufacturer, model, year, engine, transmission, VIN or serial number where appropriate.
Confirm the Diagnostic Connection
Use the correct cable, adapter, connector and power arrangement for the selected application.
Check Battery and System Voltage
Confirm stable voltage before scanning, clearing faults or running service procedures.
Perform the Initial Full System Scan
Scan all supported controllers and save the complete pre-repair result.
Group Related Faults
Separate active, historical, communication and low-voltage faults and look for a common cause.
Open the Relevant ECU
Review detailed codes, available status information and related live data in the selected controller.
Inspect and Test the Physical System
Check wiring, connectors, power, grounds, sensors, actuators and mechanical components.
Run Supported Component Tests
Use actuator tests only after securing the vehicle and understanding the procedure.
Complete the Confirmed Repair
Repair the underlying electrical, mechanical, pneumatic, hydraulic or software-related cause.
Complete Required Service Functions
Perform supported resets, calibrations, adaptations or replacement procedures where required.
Perform a Post-Repair Scan
Recheck all supported systems, confirm relevant faults do not return and save the final diagnostic report.
Pre-Scan vs Post-Scan Report
| Report | When It Is Created | Main Purpose |
|---|---|---|
| Pre-Scan Report | Before fault clearing, disassembly or component replacement. | Records the initial electronic condition and supports diagnosis. |
| Mid-Repair Report | After testing or partial repair where additional work remains. | Records progress and helps compare changing fault conditions. |
| Post-Scan Report | After the repair, calibration and controlled verification test. | Confirms final system status and records remaining faults. |
| Fleet Inspection Report | During scheduled vehicle or equipment inspections. | Creates repeatable records for maintenance planning. |
What Should a Diagnostic Report Contain?
Depending on the supported application and available report functions, a professional record may include:
- Workshop or technician information
- Customer or fleet information
- Vehicle manufacturer and model
- VIN, chassis or equipment serial number
- Production year
- Mileage or operating hours
- Scan date and time
- Detected control units
- Active and stored faults
- Available fault descriptions
- Communication failures
- Relevant live-data results
- Tests or procedures completed
- Repairs performed
- Remaining recommendations
Add clear workshop notes when the generated report does not include every physical inspection or repair detail.
Why Diagnostic Reports Improve Workshop Efficiency
Organized reports help workshops:
- Document the vehicle condition before repair
- Explain faults to customers
- Record which codes were active
- Compare pre-scan and post-scan results
- Reduce disputes about pre-existing faults
- Support fleet maintenance planning
- Track repeated or intermittent problems
- Provide information for another technician
- Maintain a professional service history
Save Reports by Vehicle and Date
Use a consistent folder and file-naming system so that technicians can locate previous scans during future visits.
Recommended Report File Name
Use a name that identifies the vehicle, scan stage and date.
Recommended format:
Customer_Vehicle_Identifier_ScanStage_Date
Examples:
- ABC-Fleet_Volvo-FH_VIN123_Pre-Scan_2026-08-01
- ABC-Fleet_Volvo-FH_VIN123_Post-Scan_2026-08-01
- Customer01_Caterpillar-Loader_SN456_Diagnostic_2026-08-01
Using Full Scans for Fleet Maintenance
Fleet workshops can use repeatable scanning procedures to monitor vehicle condition over time.
A fleet scan workflow may include:
- Scanning during scheduled maintenance
- Recording mileage or operating hours
- Comparing recurring fault codes
- Identifying low-voltage or communication patterns
- Monitoring aftertreatment-related faults
- Recording component replacement procedures
- Confirming repairs before vehicles return to service
A fault that appears repeatedly across several vehicles can also indicate an operating, maintenance or environmental pattern rather than an isolated component failure.
Truck and Trailer Full System Scanning
Commercial trucks can contain separate controllers for the engine, transmission, brakes, suspension, retarder, body, gateway and aftertreatment systems.
When a trailer is connected, additional faults may be stored in:
- Trailer ABS or EBS controller
- Trailer suspension system
- Refrigeration unit
- Tractor-trailer communication circuits
- Power-supply and connector systems
Scan both the tractor and trailer where the customer complaint involves the complete combination.
Bus and Coach Scanning
Buses and coaches may combine powertrain systems with braking, suspension, body, climate and passenger-related electronic controllers.
A complete scan can help identify whether a warning originates from:
- Engine or aftertreatment system
- Transmission
- ABS or EBS
- Electronic suspension
- Door or body controller
- Climate-control system
- Vehicle communication network
Read the JalTool Bus Diagnostic Tool Guide for additional bus and coach information.
Agricultural and Construction Equipment Scanning
Agricultural and off-highway machines may combine engine, transmission, hydraulic, implement, steering and aftertreatment controllers.
A machine complaint can be influenced by:
- Engine derating
- Hydraulic pressure faults
- Transmission problems
- Implement communication
- Aftertreatment faults
- Low system voltage
- Controller communication loss
Diagnose the complete machine rather than opening only the engine ECU.
Material Handling and Marine Diagnostics
Forklifts, telehandlers, lifting equipment and marine applications can contain multiple electronic control systems with manufacturer-specific connectors and procedures.
Review:
Common Full System Scan Mistakes
Scanning Only the Engine ECU
Related faults may be stored in the transmission, brakes, aftertreatment or gateway systems.
Clearing Codes Before Saving the Report
Always preserve the original electronic condition before changing it.
Replacing Every Component Named in the Scan
A fault code identifies the detected condition, not necessarily the failed part.
Ignoring Historical Faults Completely
Historical codes may explain intermittent customer complaints or previous voltage and communication problems.
Treating Every Historical Fault as Active
Confirm the current status and whether the fault returns after clearing and testing.
Ignoring Communication Faults
Several related communication codes can identify a shared network or power problem.
Running Active Tests Without Securing the Vehicle
Actuators, valves, motors and other components can operate unexpectedly.
Clearing Codes Without Completing the Repair
Fault clearing does not repair wiring, sensors, mechanical problems or control-unit failures.
Skipping the Post-Repair Scan
Always confirm whether relevant faults return after the repair and controlled test.
Failing to Save Reports
Diagnostic records are valuable during repeat visits, fleet maintenance and customer communication.
JalTool as a Jaltest Alternative for Full System Scanning
Workshops searching for a Jaltest full system scan, Jaltest diagnostic report or Jaltest alternative generally require more than a basic engine code reader.
JalTool is designed to provide the same supported professional diagnostic function categories and vehicle segments as Jaltest, including compatible full system scanning, fault-code diagnosis, live data, component tests, calibrations and diagnostic reporting.
Exact access must still be confirmed for the manufacturer, model, production year, ECU and installed system.
JalTool remains the independent product, purchasing platform and technical support brand promoted in this guide.
JalTool Package Options
JalTool Main Unit
Intended for customers who already have compatible computer equipment and the required diagnostic cables or adapters.
Main Unit with Accessories
Combines the JalTool main unit with the selected commercial-vehicle diagnostic cables and adapters.
Main Unit, Accessories and Laptop
Includes the diagnostic unit, accessories and a prepared laptop for customers who require a more complete workshop configuration.
The packages provide the same activated JalTool diagnostic platform. Their main difference is the physical accessories and computer equipment included.
Compare current configurations on the JalTool Pricing page .
How to Confirm Full Scan Compatibility
Before ordering, prepare:
- Vehicle or equipment category
- Manufacturer
- Exact model
- Production year
- Engine and transmission information
- VIN or serial number where relevant
- Required ECU or system
- Required diagnostic procedure
- Diagnostic connector photograph where necessary
- Current warning lights or fault codes
A listed manufacturer does not automatically guarantee every model, ECU or function.
Search the JalTool Vehicle Coverage page and request confirmation for the exact application.
Information to Send JalTool Support
- JalTool package and software information
- Vehicle or equipment manufacturer
- Exact model and production year
- Engine and transmission information
- VIN, chassis or serial number where appropriate
- Complete initial scan screenshot
- Relevant fault codes
- Required ECU, test or service function
- Diagnostic connector type
- Cable or adapter being used
- Complete communication or procedure error
Use the JalTool Support Center or send the information to JalTool@outlook.com .
JalTool Full System Scan Checklist
Confirm These Points During Diagnosis
- The customer complaint has been recorded
- The vehicle or equipment is correctly identified
- The correct diagnostic cable and adapter are used
- Vehicle or equipment voltage is stable
- The initial full system scan is completed
- The pre-scan report is saved
- Active and stored faults are separated
- Communication and low-voltage faults are reviewed
- Related faults across multiple systems are compared
- Relevant live data is recorded
- Requested and actual values are compared
- Wiring and connectors are inspected
- Physical system checks are completed
- The vehicle is secured before active tests
- Supported actuator tests are completed safely
- The underlying cause is confirmed before parts replacement
- Required resets or calibrations are completed
- A controlled verification test is performed
- The post-repair full scan is completed
- The final diagnostic report is saved
Frequently Asked Questions
Can JalTool perform a full system scan?
JalTool provides full system scanning for compatible vehicles and equipment, allowing technicians to scan supported electronic control units.
Can JalTool scan more than the engine ECU?
Depending on the application, JalTool may access supported transmission, brake, suspension, aftertreatment, body, trailer and auxiliary systems.
Can JalTool create diagnostic reports?
JalTool provides supported diagnostic report functions for organizing vehicle information, scan results and workshop records.
Should I clear all fault codes after scanning?
Save the initial scan first. Clear appropriate codes after inspecting or repairing the underlying condition.
Does a fault code identify the failed component?
Not always. The code identifies the condition detected by the controller. Wiring, connectors, mechanical faults and related systems must also be tested.
Can JalTool display live data?
Compatible ECUs may provide supported sensor values, operating parameters, requested values, actual values and controller status information.
Can JalTool graph live data?
Supported data channels may be displayed graphically to help identify irregular or intermittent values.
Can JalTool run actuator tests?
Compatible systems may provide supported component tests for valves, relays, motors, injectors and other actuators.
What is the difference between a pre-scan and post-scan?
The pre-scan records the initial condition. The post-scan checks the systems again after repair and verification.
Can fleets use JalTool diagnostic reports?
Diagnostic reports can help fleets document recurring faults, scheduled inspections, repairs and final vehicle status.
Is JalTool a Jaltest alternative for full system diagnosis?
JalTool is designed to provide the same supported professional diagnostic function categories as Jaltest while remaining an independent JalTool product.
Does JalTool require an annual subscription?
No subscription fee. One-time purchase. Lifetime free use.
Final Thoughts
A JalTool full system scan provides a structured starting point for diagnosing compatible trucks, buses, trailers, agricultural machinery, construction equipment, material handling equipment and marine applications.
Begin by saving the complete pre-scan before clearing codes or replacing components.
Compare related faults across multiple control units, then use supported live data, graphs and actuator tests to investigate the underlying cause.
After completing the repair and required calibration procedures, perform a second full scan and save the post-repair diagnostic report.
This workflow helps workshops improve documentation, avoid unnecessary parts replacement and provide customers or fleet managers with a clearer repair record.
Exact scan coverage and functions depend on the manufacturer, model, production year, ECU and installed system. Confirm compatibility before ordering or promising a specific procedure.
Confirm Your Vehicle and Diagnostic Functions
Send JalTool the manufacturer, model, production year, engine, ECU, diagnostic connector and exact scanning or service procedure required.
Review the JalTool full system scan and diagnostic functions .
Search the JalTool vehicle and equipment coverage .
Compare the JalTool main unit, accessories and laptop packages .
Get assistance from the JalTool Support Center .
Review common questions on the JalTool FAQ page .
Read the JalTool Transmission and Clutch Adaptation Guide .
Read the JalTool Bus Diagnostic Tool Guide .
Review the JalTool Material Handling Diagnostic Guide .
Review the JalTool Marine Diagnostic Tool Guide .
Learn more on the About JalTool page .
Read more professional diagnostic articles on the JalTool Technical Blog .
Jaltest is mentioned only to explain the professional diagnostic-function and vehicle-coverage positioning of JalTool. JalTool remains the product, purchasing platform and support brand promoted in this article.
Diagnostic coverage and available functions depend on the manufacturer, model, production year, engine, ECU, installed system, diagnostic connection and purchased configuration. Compatibility should be confirmed before purchase.
Active tests, calibrations and service procedures should only be performed by trained technicians following the displayed instructions and applicable vehicle, equipment and workshop safety procedures.
Lifetime use refers to continued use of the purchased and activated JalTool configuration. It does not automatically guarantee unlimited future software upgrades or compatibility with every future vehicle.