E-Gas Monitoring Concept
The three-level monitoring architecture for electronic throttle control from the E-Gas V6.0 guideline: what each level checks, how faults are detected and handled, and what the reference analysis does and does not let you reuse.
Free account: a preview of this guide, plus the full Functional Safety Concept guide, 3 templates and 5 exams a month.
- Chapters
- 12
- Chapters
- Fictional design examples
- 4
- Fictional design examples
- Figures and interactive diagrams
- 60+
- Figures and interactive diagrams
Quick answers
- What is the E-Gas monitoring concept?
- The E-Gas monitoring concept is a standardized three-level safety architecture for electronic throttle control in gasoline and diesel engines, published by the EGAS Workgroup of automotive manufacturers (current version 6.0). Level 1 performs the function, computing the torque request from the pedal signals. Level 2 independently monitors Level 1 by recalculating permissible torque and can trigger a reaction. Level 3 monitors the controller itself through a separate hardware module and a question-and-answer exchange. The pattern has been widely reused for other powertrain functions.
- What do the three E-Gas monitoring levels do?
- Level 1 is the functional level: it interprets driver demand, checks pedal signals and computes the torque request. Level 2 is function monitoring: a separately specified path that checks Level 1 results against a permissible torque and commands a fault reaction when they disagree. Level 3 is controller monitoring: it checks that the processor running Levels 1 and 2 still executes correctly, and can force a safe state through a path the faulty processor cannot block. Each level catches faults the others cannot see.
Included in Pro and Expert
This page is the outline. The full guide is in Pro.
The complete E-Gas Monitoring Concept guide, 12 chapters, is part of the Pro and Expert plans. A free account lets you preview it and includes the complete Functional Safety Concept guide, 3 templates and 5 practice exams a month.
See what Pro includes
Why it pays for itself
Understand the reference architecture
Learn the three-level structure of function level, function monitoring and controller monitoring that became a template for powertrain safety, why each level exists, and which faults only it can catch.
Reason about fault reactions
See how detected faults lead to degraded operation, currentless actuators or engine shutdown, and why the safe reaction and its time budget are always specific to the vehicle and the fault.
Reuse the guideline without misusing it
Know which results of the E-Gas reference analysis belong only to its reference item, so your project repeats its own item definition and HARA instead of copying a classification.
What you’ll be able to do
Explain the three levels
Describe what function, function monitoring and controller monitoring each detect, and why they must stay independent.
Use the reference analysis correctly
Know which E-Gas results are scoped to the reference item and what a real project must redo.
Reason about fault reactions
Connect detected faults to safe-state reactions within a project-specific time budget.
Adapt the concept to an engine
Recognize how torque monitoring changes between gasoline and diesel engines.
Plan verification
Choose fault injection, coverage and validation activities that show the mechanisms work.
Chapter by chapter
- 01
Overview
Get the key technical picture of electronic throttle control and see why the fault tolerance time is always project-specific.
- Key technical specifications
- Core safety concepts
- Project-specific timing
- 02
Safety Goals
Study the four reference safety goals for acceleration and deceleration and why their classification belongs to the reference item only.
- Unintended acceleration
- Absence of acceleration
- Deceleration goals
- 03
3-Level Monitoring Architecture
Explore function, function monitoring and controller monitoring levels in an interactive architecture diagram.
- Interactive architecture diagram
- Level-blindness fault injector
- Physical separation
- 04
Safety Mechanisms
Survey the detection and reaction mechanisms used across the three levels, from plausibility checks to monitored shutdown.
- Detection mechanisms
- Reaction mechanisms
- Driver override priority
- 05
Sensors & Hardware
Look at pedal and throttle sensing, the throttle body, controller hardware and power supply from a safety point of view.
- Pedal value sensor
- Electronic throttle body
- Power supply distribution
- 06
Q&A Protocol
Understand how the question-and-answer exchange lets an external module confirm that the function controller still executes correctly.
- Q&A swimlane
- Error-counter state machine
- Answer-window timing
- 07
Fault Reactions
Follow how detected faults lead to a safe state within a time budget, with competing shut-off paths on one time axis.
- Fault-category tree
- Shut-off path race
- Fault-to-safe-state budget
- 08
Engine Variants
See how monitoring adapts to manifold injection, direct injection and diesel engines, each with a different torque path.
- Engine variant decision tree
- Gasoline engine variants
- Diesel reverse calculation
- 09
Software & Communications
Examine a typical AUTOSAR-based software stack, task scheduling, CAN communication and the protected Q&A interface.
- AUTOSAR-based stack
- Task scheduling example
- CAN and SPI interfaces
- 10
Verification & Validation
Plan software, hardware and system testing, structural coverage, validation scenarios and hardware metric context for the concept.
- Fault injection bench
- Structural coverage methods
- Validation scenarios
- 11
Fictional Design Examples
Walk four fictional fault cases from detection to state transition and review the design decisions behind them.
- Pedal sensor faults
- Brake override
- Q&A protocol failure
- 12
Pitfalls & References
Avoid common misreadings of the E-Gas concept and see how the guideline relates to ISO 26262 and supporting standards.
- Common pitfalls
- Primary reference
- Scope and source note
Read all 12 chapters with Pro or Expert.
Start with a free account: a preview of this guide, the complete Functional Safety Concept guide and 5 practice exams a month, then upgrade when you need this guide.
Pro plan pricingExpert plan pricingNot just text: the visual toolkit
Interactive architecture block diagram
Three-level, system overview and physical separation views of the concept.
Level-blindness fault injector
Inject a fault and see which monitoring level can and cannot detect it.
Q&A error-counter state machine
How the monitoring module counts wrong or late answers.
Engine variant decision tree
Which torque monitoring path fits which engine type.
Fault injection bench
A test setup for showing that mechanisms react as specified.
Four fault cases on a throttle controller
The guide walks four fictional fault scenarios, each with a timeline and state transitions, then discusses the design decisions behind them.
- A single pedal sensor fault
- Non-plausible readings between the two pedal sensors
- Brake override while the pedal is pressed
- A failure of the question-and-answer protocol
- Design decisions and rationale across the cases
- Timeline and state transition after one pedal channel fails
- Each point in the list, worked through step by stepIn the full guide
The full example is in the guide, part of the Pro and Expert plans.
Who this guide is for
- Powertrain and engine ECU engineers implementing or maintaining torque monitoring
- Safety engineers who need to justify a monitoring architecture against an unintended-acceleration goal
- Engineers carrying the three-level idea into other safety-relevant ECU functions
- Anyone who has seen "Level 2" in a powertrain design and wants to know what it actually does
Frequently Asked Questions
Common questions about E-Gas Monitoring Concept
Start the course today
The full guide is part of the Pro and Expert plans. A free account opens a preview of it, the complete Functional Safety Concept guide, 3 work product templates, 1 guided process, the Markov and RBD simulators and 5 practice exams a month. No credit card required.
Continue with
Where this topic leads next.
- System levelSystem Architectural Design and Safety ArchitectureA list of technical safety requirements does not tell you what to build. This guide turns them into elements, boundaries and interfaces, allocates every requirement with a reason, and verifies the result before hardware exists.
- Concept phaseItem Definition & Concept-Phase InitiationGet the first ISO 26262-3 step right: define the item boundary, interfaces, operating modes, and assumptions of use that HARA, safety goals, and the whole safety case inherit from the concept phase.
- Concept phaseHazard Analysis & Risk Assessment (HARA)Learn how to identify vehicle-level hazards and assign ASIL ratings through Severity, Exposure, and Controllability assessment. Covers operational situations, FTTI concepts, and advanced topics for ADAS and distributed systems.