Schedulability Test

A Real-Time Operating System (RTOS) is an operating system designed to process data and execute tasks within a guaranteed, predictable timeframe. Unlike general-purpose OSs, an RTOS provides deterministic scheduling and bounded latency, which are prerequisites for performing a valid schedulability test.

• Key Feature: Provides deterministic task scheduling primitives (e.g., priority-based, round-robin).
• Purpose: Ensures that high-priority tasks, like a motor control interrupt, can preempt lower-priority tasks without unbounded delay.
• Example: An autonomous vehicle's perception pipeline must process LiDAR data within a strict 100ms window to update the world model; an RTOS guarantees the task's thread meets this deadline.

Worst-Case Execution Time (WCET) is the maximum possible time a specific task or piece of code could take to execute on given hardware under the most unfavorable conditions. This is not the average time, but a proven upper bound.

• Role in Schedulability: WCET is the fundamental input (C_i) for rate-monotonic or deadline-monotonic analysis. A test is invalid if WCET is underestimated.
• Analysis Methods: Determined through static analysis of the code path or measurement via trace-based profiling under maximum load and cache miss scenarios.
• Example: A robot's SLAM task might typically run in 50ms, but its WCET—factoring in a worst-case map update—could be 120ms. The schedulability test uses 120ms.

Deterministic execution refers to a system's ability to produce the same output, within a bounded and predictable time frame, for a given set of inputs and initial conditions. It is the ultimate goal verified by schedulability analysis.

• Contrast with Non-Determinism: Garbage collection, dynamic memory allocation, and cache thrashing can introduce unpredictable delays.
• Engineering for Determinism: Requires using an RTOS, pre-allocating memory, disabling interrupts for critical sections, and using time-triggered architectures.
• Importance: A robotic arm's trajectory controller must have deterministic loop execution to ensure stable, safe motion. A missed deadline could cause violent jerks.

Time-Sensitive Networking (TSN) is a set of IEEE 802.1 Ethernet standards that provide deterministic data delivery, guaranteed latency, and synchronization for real-time communication over standard Ethernet networks. It extends schedulability from the CPU to the network.

• Core Mechanism: Uses time-aware shapers and scheduled traffic gates to reserve bandwidth for critical messages, ensuring they are not blocked by bulk data transfers.
• Relation to Schedulability: Allows system designers to treat network message delivery as a periodic task with a known, bounded latency, which can be incorporated into an end-to-end schedulability model.
• Application: In a robotic workcell, TSN ensures emergency stop signals and joint position commands always arrive within a few microseconds, regardless of other network traffic.

Hardware-in-the-Loop (HIL) testing is a validation technique where a physical hardware component (e.g., a robot's motor controller) is integrated and tested within a simulated environment that provides realistic sensor inputs and receives actuator commands.

• Complement to Schedulability: While schedulability is a theoretical verification, HIL testing is an empirical validation. It stress-tests the system to see if real-world execution times align with the WCET assumptions used in the model.
• Process: The physical controller runs its real-time software, connected to a simulator that models plant dynamics (motors, physics). Test scenarios are designed to provoke worst-case timing conditions.
• Outcome: Validates that the integrated system, including all hardware delays and interrupt latencies, still meets all deadlines under load.

Functional Safety (FuSa) is the part of a system's overall safety that depends on its components operating correctly in response to inputs. ISO 26262 is the international standard governing FuSa for road vehicles, which mandates rigorous timing analysis.

• Schedulability as a Safety Requirement: ISO 26262 requires the verification of timing constraints for Automotive Safety Integrity Level (ASIL)-rated functions. A failed schedulability test is a safety violation.
• Process Integration: Schedulability analysis is a key work product in the design and verification phases of the FuSa V-model. It must be documented and maintained.
• Example: An ASIL-D automatic emergency braking system must guarantee its perception-to-actuation loop completes within 80ms. Schedulability analysis proves this guarantee is met, even if other non-critical infotainment tasks are running.