Glanz: aiMOOC über GPT aiMOOC Action erstellt

2026-08-31T07:59:59Z

aiMOOC über GPT aiMOOC Action erstellt

Neue Seite

{{T}}
[[Category:English]]
[[Category:Automotive Diagnostics]]

{{BR}}
= Introduction =

Automotive diagnostics is the structured process of identifying the '''root cause''' of a vehicle fault by combining symptoms, service information, measurements, scan data, and physical inspection. In a modern workshop, a diagnostic trouble code is usually a starting point rather than a final answer. Your job is to collect evidence, test a hypothesis, repair only what has been proven faulty, and then verify that the vehicle works correctly.

This aiMOOC is designed for apprentices, trainees, and vocational students. It assumes that you are learning in a supervised workshop and have access to suitable service information and basic test equipment. You will work with [[English:On-board diagnostics|on-board diagnostics]], [[English:Automotive electronics|automotive electronics]], electrical measurements, sensor signals, network communication, and mechanical checks. The central principle is simple: '''measure first, replace parts only after the fault has been demonstrated.'''

[[File:MaxScan OE509 collage.jpg|500px|frameless|center]]

A scan tool can read useful vehicle information, but the tool does not automatically identify the defective part. You must interpret what the vehicle reports and compare it with what should be happening.

{{#ev:youtube|https://www.youtube.com/watch?v=YcwBeNQbJ5A|500|center}}

{{BR}}
== Learning Goals ==

By the end of the course, you should be able to explain a professional diagnostic workflow, use basic scan data and electrical measurements safely, distinguish symptoms from causes, select suitable tests, interpret evidence, document your reasoning, and confirm a repair. You should also understand when a fault requires higher-level equipment, manufacturer information, or a specially qualified technician.

{{BR}}
= The Diagnostic Mindset =

Good diagnostics is not guessing. It is a repeatable reasoning process. A useful workflow is to '''confirm the complaint, gather information, inspect, scan, test, repair, and verify'''. The exact order may change with the vehicle and fault, but every step should reduce uncertainty.

A customer may report that a vehicle "loses power", "will not start", "uses too much fuel", or "shows a warning light". These are symptoms. Many different causes can produce the same symptom. A loss of power, for example, could involve air measurement, fuel delivery, ignition, exhaust restriction, mechanical condition, control strategy, low system voltage, or network communication. Professional diagnostics therefore turns a vague symptom into a set of testable questions.

The strongest diagnostic conclusions combine several forms of evidence. You might compare a DTC with freeze-frame data, inspect a connector, check a wiring diagram, measure a circuit under load, and compare a sensor waveform with a known-good example. When all of those observations point in the same direction, your diagnosis becomes much stronger.

{{#ev:youtube|https://www.youtube.com/watch?v=pRZ4leVqUPI|500|center}}

The workshop lesson in this real-world case is not to trust a first hunch simply because a code and a symptom appear to match. Test the circuit or component so that your decision is based on evidence.

{{BR}}
= Safety and Work Preparation =

Diagnostics often takes place around moving parts, hot surfaces, pressurized systems, fuel, batteries, lifting equipment, and electrical energy. Before any test, identify the hazards and follow the workshop's risk assessment, manufacturer instructions, and local safety rules. Wear the required personal protective equipment and keep leads, clothing, hair, and tools away from rotating components.

Never use a meter setting, probe, breakout lead, or oscilloscope connection unless it is appropriate for the circuit. Resistance measurements are normally made only on de-energized circuits unless the manufacturer specifies a different approved procedure. A current range connected incorrectly can create a short circuit. Back-probing, pin tension checks, and terminal repairs should use methods that do not damage connectors.

Hybrid and battery-electric vehicles introduce high-voltage systems that require specific training, tools, personal protective equipment, and isolation procedures. If you are not qualified for the vehicle's high-voltage work, do not open, disconnect, probe, or attempt to depower those circuits. Escalating a job to a qualified technician is part of competent diagnostics.

{{BR}}
= Start With the Vehicle and the Complaint =

Before connecting equipment, identify the vehicle accurately. Model, model year, engine or drive unit, transmission, market, option codes, software level, and previous repairs can change the correct test procedure. Use reliable service information that applies to the exact vehicle.

Confirm the complaint whenever it can be reproduced safely. Ask when the symptom occurs: cold or hot, at idle or under load, on rough roads, after rain, during charging, at a particular speed, or only after a long drive. Note warning lamps, noises, smells, messages, and recent work. An intermittent fault often becomes much easier to diagnose once the operating conditions are known.

A visual inspection can reveal loose grounds, damaged wiring, fluid contamination, split hoses, missing fasteners, overheated connectors, incorrect fuses, poor previous repairs, and obvious mechanical damage. Visual inspection is not a substitute for testing, but it can prevent unnecessary electronic diagnosis.

[[File:Check-Engine-Light.jpg|500px|frameless|center]]

A malfunction indicator lamp tells you that the control system has detected a condition that meets its monitoring criteria. It does not tell you which part to replace.

{{BR}}
= On-Board Diagnostics and Scan Tools =

[[English:On-board diagnostics|On-board diagnostics]] provides standardized access to emissions-related diagnostic information on compliant vehicles, while manufacturer-specific diagnostic systems can offer much broader access to modules, tests, coding, and guided procedures. Regulations and supported functions vary by market, vehicle type, and model year.

[[File:2016-07 ODB-II connector 01.JPG|500px|frameless|center]]

The standardized diagnostic link connector used for OBD-II and EOBD is a 16-position connector. A scan tool may communicate with the engine controller and, depending on the tool and vehicle, with transmission, brake, restraint, body, climate, steering, battery, and other control modules.

{{BR}}
== Diagnostic Trouble Codes ==

A [[English:Diagnostic trouble code|diagnostic trouble code]], or DTC, records that a control module detected a condition outside its expected logic. Many standardized DTCs begin with a letter such as P for powertrain, B for body, C for chassis, or U for network communication. The remaining characters identify a fault family and a more specific condition. Manufacturer-specific information is often essential for interpreting the code correctly.

A code usually describes '''what the module detected''', not the component that must be replaced. A sensor circuit code can be caused by the sensor, wiring, terminal fit, power supply, ground, module input, contamination, or a mechanical condition that makes the sensor signal implausible. Always read the exact code definition and diagnostic procedure for the vehicle.

Do not erase codes before saving useful evidence. Clearing codes can remove freeze-frame information, reset readiness information, and make an intermittent problem harder to reproduce.

{{BR}}
== Freeze Frame, Readiness, and Live Data ==

Freeze-frame data stores selected operating conditions from around the time a monitored fault was detected. Depending on the system, it can include engine speed, load, temperature, speed, fuel control information, voltage, and other parameters. Use it to recreate the conditions under which the fault occurred.

Readiness monitors show whether certain self-tests have completed. After codes are cleared or power is disconnected, some monitors may return to a not-ready state until their operating conditions are met again. This is important when verifying emissions-related repairs.

Live data displays parameters reported or calculated by control modules. A single number can be misleading without context, so compare related PIDs, operating conditions, and manufacturer specifications. Graphing data can reveal dropouts, slow responses, and relationships that are difficult to see in a list.

{{BR}}
= Electrical Diagnostics =

Electrical faults are common because modern vehicles depend on stable power, grounds, signal circuits, and data networks. A [[English:Multimeter|digital multimeter]] is one of the most important diagnostic tools, but the meter must be used with the correct function and range.

[[File:Auto mechanic checking old car battery voltage.jpg|500px|frameless|center]]

'''Voltage''' is electrical potential difference. '''Current''' is the flow of charge. '''Resistance''' opposes current flow. Ohm's law links these quantities, but real vehicle circuits also include semiconductor devices, pulse-width modulation, inductive loads, and network communication. Always understand the circuit before testing it.

{{BR}}
== Voltage Drop Testing ==

A voltage drop test measures the loss of voltage across part of a circuit while current is flowing. It is especially useful for finding unwanted resistance in power and ground paths. A connection may show acceptable resistance with no load but fail when the starter, motor, heater, lamp, or other load is operating.

For a valid voltage drop test, the circuit must be in the operating state that produces the complaint. Compare your measurement with the manufacturer's limit and the circuit design. Avoid memorizing one universal maximum because acceptable values depend on the circuit, current, and test location.

{{BR}}
== Fuses, Grounds, and Connectors ==

A fuse protects a circuit from excessive current; it does not prove that the rest of the circuit is healthy. Check why a fuse failed before replacing it, and always use the specified type and rating. Grounds should be inspected for corrosion, loose fasteners, damaged straps, paint, heat damage, and voltage loss under load.

[[File:Car fuse box Layout.jpg|500px|frameless|center]]

Connector faults may be intermittent. Look for water entry, spread terminals, pushed-back pins, fretting, corrosion, poor crimps, and harness strain. Use approved terminal tools and avoid piercing insulation unless the service procedure specifically permits it.

{{BR}}
= Sensors, Actuators, and Control Logic =

A control module makes decisions from inputs and then controls outputs. Inputs can include temperature, pressure, position, speed, oxygen concentration, current, and switch states. Outputs include injectors, ignition coils, motors, solenoids, relays, heaters, lamps, and communication messages.

A sensor may produce an analog voltage, a frequency, a digital square wave, a resistance change, or a network message. Before testing, determine the sensor type, expected supply, ground arrangement, signal behavior, and connector pinout from the wiring diagram.

[[File:Oxygen sensor.gif|500px|frameless|center]]

An oxygen sensor is one example of an input used by engine management. Its correct interpretation depends on sensor type, operating temperature, control strategy, exhaust conditions, and the vehicle's service information. A signal that looks unusual may be the result of another fault elsewhere in the system.

Actuator testing also requires context. An actuator that does not move may lack power, lack ground, have an open coil, be mechanically jammed, be disabled by control logic, or not be receiving a command. A bidirectional scan-tool command can be useful, but only when you understand the expected result and the safety implications of commanding the component.

{{BR}}
= Using an Oscilloscope =

An automotive oscilloscope displays how voltage or current changes over time. This makes it useful for signals that are too fast or too dynamic for a normal multimeter display. You can examine crankshaft and camshaft signals, injector control, ignition events, pulse-width-modulated actuators, network activity, current ramps, and intermittent dropouts.

[[File:Spark plug.svg|500px|frameless|center]]

A useful waveform depends on correct connection, voltage range, time base, sampling, trigger, and probe choice. Begin with a safe expected range, capture the signal, and then adjust the display. Compare the result with service information or a known-good waveform from the same system when possible. Do not assume that a visually similar pattern is automatically correct.

{{#ev:youtube|https://www.youtube.com/watch?v=nmGubcuzbtU|500|center}}

The oscilloscope becomes most powerful when it answers a specific diagnostic question. For example, a scope can show whether a signal disappears during the exact moment an engine stalls, or whether two related signals keep their expected timing relationship.

{{BR}}
= Vehicle Networks and Communication Faults =

Modern control modules communicate over networks such as [[English:CAN bus|Controller Area Network]], commonly called CAN. A communication fault can create many warning messages because one missing module or damaged network segment may affect several systems at once.

Network diagnosis begins with service information and a full vehicle scan. Note which modules communicate, which do not, and which U-codes are current or history. Then inspect network power supplies, grounds, connectors, topology, and the physical bus as specified by the manufacturer.

Some high-speed CAN networks use two 120-ohm terminating resistors in parallel, producing a measurement near 60 ohms across the bus when the network is correctly powered down and isolated for resistance testing. This is a common example, not a universal rule. Always follow the vehicle-specific wiring diagram and procedure, and never use an ohmmeter on an energized network.

An oscilloscope can display CAN High and CAN Low activity and help reveal shorts, opens, interference, or abnormal signal levels. However, decoding network problems requires an understanding of topology and module behavior; a waveform alone is not a complete diagnosis.

{{BR}}
= Mechanical Problems Can Create Electronic Symptoms =

Electronic data can reflect a mechanical problem. Low compression, incorrect valve timing, restricted intake or exhaust flow, vacuum leaks, fuel pressure faults, cooling problems, and worn components can all alter sensor values and control corrections.

A diagnostic plan should therefore include mechanical tests when the evidence points in that direction. Depending on the fault, this may involve compression or leak-down testing, pressure measurement, vacuum analysis, smoke testing, temperature comparison, relative compression, or physical timing checks. Use equipment and procedures that are appropriate for the engine, fuel system, and vehicle technology.

The key question is always: '''what evidence would distinguish one possible cause from another?''' This prevents you from replacing electrical parts when the real fault is mechanical, and it prevents unnecessary mechanical work when the fault is in a circuit.

{{BR}}
= A Practical Diagnostic Workflow =

A professional workflow can be summarized as follows. First, verify the complaint and collect vehicle information. Second, perform a visual and basic safety inspection. Third, scan all relevant modules and save DTCs, freeze-frame data, and useful live data before clearing anything. Fourth, consult the wiring diagram, technical information, and test specifications. Fifth, form one or more hypotheses and choose tests that can prove or disprove them. Sixth, repair the confirmed root cause using the correct method. Finally, repeat the original test conditions, rescan the vehicle, check for returning faults, and document the result.

When a test does not support your hypothesis, change the hypothesis rather than forcing the evidence to fit. Good technicians are willing to be wrong early because every valid test removes one possibility.

{{BR}}
= Repair Verification and Documentation =

A repair is not complete when a new part has been installed. You must verify that the original symptom is gone, the repaired system operates correctly, and no new fault was introduced. Repeat the same conditions that produced the complaint whenever it is safe and practical.

After an emissions-related repair, check DTC status, relevant live data, and readiness information. After a network repair, confirm communication with the affected modules and check for recurring U-codes. After an electrical repair, repeat the load or waveform test that originally proved the fault. After a mechanical repair, repeat the relevant pressure, compression, temperature, or performance measurement.

Document what the customer reported, what you observed, which tests you performed, the measurements obtained, the root cause, the repair, and the verification result. Clear documentation helps the next technician, supports quality control, and explains your reasoning to the customer or supervisor.

{{BR}}
= Hybrid, Electric, and Advanced Vehicle Systems =

Diagnostics increasingly includes high-voltage propulsion, battery management, power electronics, regenerative braking, thermal management, driver-assistance systems, and software-controlled functions. The same evidence-based logic still applies, but the safety requirements and test equipment may be very different.

High-voltage insulation or isolation faults are an example. Their diagnosis can involve dedicated insulation test equipment and manufacturer procedures. Such testing should be performed only by personnel trained and authorized for the vehicle and voltage level.

{{#ev:youtube|https://www.youtube.com/watch?v=00eEj_EgMas|500|center}}

Use demonstrations of high-voltage diagnostics to understand concepts, not as instructions to reproduce hazardous tests. In the workshop, follow the manufacturer's high-voltage isolation procedure, required personal protective equipment, and qualification rules.

Advanced driver-assistance systems can require calibrated targets, level floors, controlled lighting, ride-height checks, wheel alignment, or manufacturer scan-tool routines. Treat calibration as a measured procedure, not an adjustment by eye.

{{BR}}
= Professional Communication and Diagnostic Ethics =

A diagnostic recommendation should be understandable and evidence based. Avoid claiming certainty that your tests do not support. If a test only shows that a circuit is abnormal, say that; do not name a component until you have isolated the cause.

Good professional practice also means protecting customer data and vehicle access. Diagnostic tools can store identification information, scan reports, and sometimes security-sensitive data. Follow workplace policies for data handling, tool accounts, software updates, and secure access.

You should also know when to stop. If the correct diagnosis requires equipment, service information, authorization, or competence that you do not have, record what you have established and escalate the job. Knowing your limits is a technical skill.

{{BR}}
= Interactive Tasks =

{{BR}}
== Quiz: Test Your Knowledge ==

{{MC}}

'''What is the best interpretation of a diagnostic trouble code?'''
(It identifies a detected condition that requires further diagnosis)
(!It always names the failed part)
(!It proves that the wiring is good)
(!It means the control module must be replaced)

{{E}}
<br>

{{MC}}

'''Why should freeze frame data be saved before codes are cleared?'''
(It can show operating conditions when a monitored fault was detected)
(!It permanently increases battery voltage)
(!It recalibrates every vehicle sensor)
(!It repairs intermittent wiring faults)

{{E}}
<br>

{{MC}}

'''What is a major advantage of voltage drop testing?'''
(It can reveal unwanted resistance while a circuit is carrying current)
(!It measures tire tread depth)
(!It replaces the need for service information)
(!It is performed only with the battery disconnected)

{{E}}
<br>

{{MC}}

'''When is a resistance measurement normally made on a vehicle circuit?'''
(When the circuit is de energized and the procedure allows the test)
(!While a starter motor is cranking)
(!While a high voltage battery is connected)
(!Whenever a warning lamp is illuminated)

{{E}}
<br>

{{MC}}

'''What does live scan data show?'''
(Parameters reported or calculated by control modules during operation)
(!Only the price of replacement parts)
(!Only mechanical compression values)
(!A guaranteed diagnosis without testing)

{{E}}
<br>

{{MC}}

'''Why is an oscilloscope useful in automotive diagnostics?'''
(It shows how electrical signals change over time)
(!It automatically repairs damaged wiring)
(!It measures wheel alignment angles without sensors)
(!It replaces every other diagnostic tool)

{{E}}
<br>

{{MC}}

'''What should you do when a test result disproves your first hypothesis?'''
(Revise the hypothesis and use the evidence to choose the next test)
(!Ignore the result and replace the suspected part)
(!Clear all codes and stop testing)
(!Disconnect the warning lamp)

{{E}}
<br>

{{MC}}

'''What is the correct response if you are not qualified for high voltage vehicle work?'''
(Escalate the work to a properly qualified technician)
(!Open the battery pack to inspect it)
(!Use a standard test lamp on the high voltage circuit)
(!Bypass the safety interlock to continue)

{{E}}
<br>

{{MC}}

'''Why can a mechanical fault produce unusual scan data?'''
(Mechanical conditions can change the signals and corrections seen by control modules)
(!Scan tools convert mechanical faults into wiring shorts)
(!Mechanical systems never affect sensors)
(!Electronic modules cannot monitor engine operation)

{{E}}
<br>

{{MC}}

'''When is a diagnostic repair complete?'''
(When the original fault is corrected and the result has been verified)
(!When any new part has been installed)
(!When all stored data has been erased)
(!When the customer first reports the symptom)

{{E}}
<br>

{{BR}}
== Memory Game ==

<div class="memo-quiz">
{|
|-
| FreezeFrame || Stored operating conditions associated with a detected fault
|-
| VoltageDrop || Electrical potential lost across part of a loaded circuit
|-
| Oscilloscope || Instrument that displays an electrical signal over time
|-
| Actuator || Device controlled by a module to perform a physical action
|-
| ReadinessMonitor || Self test status used by an onboard diagnostic system
|-
| RootCause || Underlying fault that actually creates the observed problem
|}
{{E}}
<br>

{{BR}}
== Drag and Drop ==

<div class="lueckentext-quiz">

{| class="wikitable"
! Match the correct terms.
! Topic
|-
| '''Confirm the complaint'''
| Verify the reported symptom under safe conditions
|-
| '''Save diagnostic evidence'''
| Record codes freeze frame and relevant scan data
|-
| '''Form a hypothesis'''
| Use symptoms diagrams and evidence to identify possible causes
|-
| '''Perform a targeted test'''
| Choose a measurement that can prove or disprove a possible cause
|-
| '''Verify the repair'''
| Repeat the original conditions and confirm correct operation
|}
{{E}}

<br>
...
<br />

{{BR}}
== Crossword Puzzle ==

<div class="kreuzwort-quiz">
{|
|-
| Scanner || What tool communicates with vehicle control modules and reads diagnostic data
|-
| Voltage || What electrical quantity represents potential difference
|-
| Waveform || What oscilloscope display shows how a signal changes over time
|-
| Connector || What joins wiring circuits and can suffer corrosion or poor terminal fit
|-
| Grounding || What circuit path can create faults when it has excessive resistance
|-
| Readiness || What monitor status shows whether an onboard self test has completed
|}
{{E}}
<br>

{{BR}}
== LearningApps ==

<iframe> https://learningapps.org/index.php?s=Automotive+Diagnostics </iframe>

{{BR}}
== Cloze Text ==

<quiz display=simple>
{'''Complete the text.'''<br>
|type="{}"}
Professional diagnosis begins by confirming the { complaint } before replacing parts. A diagnostic trouble code identifies a detected { condition } rather than automatically naming a failed component. Freeze frame data can help you recreate the { operating conditions } present when a monitored fault was detected. A voltage drop test is most useful while the circuit is carrying { current }. An oscilloscope displays a changing electrical signal as a { waveform }. Live data should be compared with related parameters and manufacturer { specifications }. Mechanical faults can change the electronic data reported by { sensors }. High voltage work must be performed only by appropriately { qualified personnel }. A repair must be followed by a repeatable { verification } of the original symptom. Accurate notes provide evidence of the diagnostic { reasoning } used in the job.
</quiz>

<br>

{{BR}}
= Open-Ended Tasks =

{{BR}}
=== Easy ===
# [[English:Diagnostic vocabulary map|Diagnostic vocabulary map]]: Create a one-page visual map that connects symptom, DTC, test, measurement, root cause, repair, and verification in your own words.
# [[English:Vehicle warning lamp survey|Vehicle warning lamp survey]]: Photograph or sketch five warning lamps on a training vehicle or approved simulator and explain what information each lamp does and does not provide.
# [[English:Scan report practice|Scan report practice]]: With supervision, make a short scan report for a training vehicle that records vehicle identity, module status, DTCs, and useful freeze-frame information without clearing any data.
# [[English:Workshop interview script|Workshop interview script]]: Write six clear questions you could ask a customer or instructor to narrow down an intermittent vehicle complaint.

{{BR}}
=== Standard ===
# [[English:Voltage drop investigation|Voltage drop investigation]]: On a low-voltage training circuit, measure the voltage drop across selected connections under load, compare the results with the circuit specification, and explain which result deserves further investigation.
# [[English:Live data comparison|Live data comparison]]: Record several related PIDs during two safe operating conditions, graph them, and explain which relationships are normal or suspicious.
# [[English:Wiring diagram trace|Wiring diagram trace]]: Choose one sensor circuit from approved service information, trace power, ground, signal, connectors, and control module connections, and produce an annotated diagram.
# [[English:Diagnostic case video|Diagnostic case video]]: Produce a three-minute video that documents a supervised diagnostic case from complaint through evidence, hypothesis, targeted test, and verification.

{{BR}}
=== Advanced ===
# [[English:Intermittent fault project|Intermittent fault project]]: Design a safe diagnostic plan for an intermittent electrical fault and explain how data logging, wiggle testing, thermal conditions, or vibration could help reproduce it without damaging the vehicle.
# [[English:Network fault analysis|Network fault analysis]]: Using a trainer or approved vehicle, compare a healthy network scan with a provided faulty scenario and justify the next network test from the communication pattern and wiring topology.
# [[English:Oscilloscope evidence study|Oscilloscope evidence study]]: Capture or analyze supplied known-good and faulty automotive waveforms, identify measurable differences, and defend which additional test would confirm the root cause.
# [[English:Cross system diagnosis|Cross system diagnosis]]: Investigate a case in which an electrical symptom could have a mechanical cause, or a mechanical symptom could have an electrical cause, and present an evidence chain that distinguishes at least three plausible causes.

{{:Open Task - Create a MOOC}}

{{BR}}
= Learning Assessment =

# [[English:Diagnostic reasoning assessment|Diagnostic reasoning assessment]]: Given a symptom, DTC, freeze-frame record, and wiring diagram, rank three plausible causes and justify the first two tests you would perform.
# [[English:Electrical evidence assessment|Electrical evidence assessment]]: Interpret a set of loaded and unloaded voltage measurements and explain which connection is faulty and why the resistance problem may not appear in a simple continuity test.
# [[English:Scan data assessment|Scan data assessment]]: Compare two live-data graphs from the same operating condition, identify the abnormal relationship, and explain what additional measurement would distinguish a sensor fault from a mechanical fault.
# [[English:Network diagnosis assessment|Network diagnosis assessment]]: Use a module communication map and a group of U-codes to propose the most efficient next test without assuming that every listed module is defective.
# [[English:Repair verification assessment|Repair verification assessment]]: Design a post-repair verification plan that recreates the original complaint conditions, checks diagnostic data, and defines objective pass criteria.
# [[English:Professional judgment assessment|Professional judgment assessment]]: Read a scenario involving a high-voltage or advanced driver-assistance system and explain which work can be performed by the trainee, which must be escalated, and what information should be documented.

<br>
<br>

{{BR}}
= Evidence of Learning =

# '''Knowledge''': You can explain the purpose and limits of DTCs, freeze frame, readiness monitors, live data, multimeters, oscilloscopes, and vehicle networks.
# '''Diagnostic process''': You can move from complaint to evidence, hypothesis, targeted test, repair, and verification without relying on unnecessary part replacement.
# '''Measurement skill''': You can select appropriate low-voltage electrical tests, connect equipment correctly, record units, and compare results with valid specifications.
# '''Interpretation skill''': You can relate electrical, electronic, network, and mechanical evidence instead of treating each system in isolation.
# '''Professional product''': You can produce a clear diagnostic report containing vehicle information, symptoms, test results, root cause, repair, and verification.
# '''Transfer achievement''': You can apply the same evidence-based reasoning to an unfamiliar vehicle or fault while recognizing when manufacturer procedures, specialist equipment, or higher qualification are required.

<br>
<br>

{{BR}}
= OERs on the Topic =

The English Wikipedia article on [[English:On-board diagnostics|On-board diagnostics]] provides additional background on OBD history, standardized interfaces, diagnostic data, and DTCs.

<iframe> https://en.m.wikipedia.org/wiki/On-board_diagnostics </iframe>

<br>

{{BR}}
= Linked Learning Areas =

{| align=center
{{:D-Tab}}
'''[[English:Automotive Diagnostics|Automotive Diagnostics]]'''
# [[English:On-board diagnostics|On-board diagnostics]]
# [[English:Diagnostic trouble code|Diagnostic trouble code]]
# [[English:Automotive electronics|Automotive electronics]]
# [[English:Multimeter|Multimeter]]
# [[English:Oscilloscope|Oscilloscope]]
# [[English:CAN bus|CAN bus]]
# [[English:Automotive safety|Automotive safety]]
# [[English:Vehicle maintenance|Vehicle maintenance]]
|}

[[Category:English]]
[[Category:Vocational Education]]
[[Category:Automotive Diagnostics]]
[[Category:Automotive Technology]]
[[Category:Vehicle Maintenance]]
[[Category:Automotive Electronics]]
[[Category:Electrical Engineering]]

{{BR}}
= aiMOOC Projects =
[[Category:English]]
[[Category:Automotive Diagnostics]]
[[Category:Vocational Education]]
[[Category:Automotive Technology]]
[[Category:Vehicle Maintenance]]
[[Category:Automotive Electronics]]
[[Category:Electrical Engineering]]
[[Category:AI_MOOC]]
[[Category:GPT aiMOOC]]
{{MT}}

English:Automotive Diagnostics - Versionsgeschichte

Glanz: aiMOOC über GPT aiMOOC Action erstellt