ASG vs FlexRay

FlexRay and ASG want the same thing: a known instant for every value. FlexRay gets there by having the integrator design and validate a global communication schedule, then hold every node’s clock tightly enough to keep to it.

ASG gets there by construction. The schedule is a single fixed 1 ms window, the same for every vehicle, and adding a zone consumes a carrier rather than schedule time.

At a glance

FlexRay

The deterministic bus for chassis and powertrain: a repeating cycle split into a static TDMA segment for scheduled signals and a dynamic segment for the rest, optionally mirrored on a second channel for redundancy.

ASG

A control architecture whose determinism is intrinsic. There is no cycle to lay out: every zone commits the shared state on the same 1 ms grid.

Topology

FlexRay network

ASG single ring

FlexRay: one or two channels wired as a bus or star, with a global schedule of static and dynamic slots. ASG: one ring, one fixed 1 ms window, no schedule to lay out.

How they differ

How determinism is achieved

FlexRay
A static segment of fixed slots, plus a validated global schedule and tight clock synchronisation across every node.

ASG
A single fixed 1 ms commit. No per-signal slots and no schedule to lay out or re-validate.
Changing the design

FlexRay
A new scheduled signal can mean re-laying the cycle and re-validating timing across every node on the bus.

ASG
Declare the zone; it joins the existing window. The 1 ms figure does not move.
Transmission efficiency

FlexRay
Single-bit differential NRZ; long frames need very tight frequency matching, which adds cost to every controller.

ASG
Each symbol carries 2 to 4 bits plus a synchronisation element, raising the effective rate and easing the clock-accuracy demand.
Data and processing

FlexRay
The schedule aligns transmission; aligning transmission with computation is left to the application.

ASG
Every module receives the full state vector tied to the same synchronisation grid, so processing across the whole vehicle is direct.
Redundancy

FlexRay
A second physical channel and a bus guardian protect against a single-channel fault.

ASG
Local blocks self-protect in about 10 microseconds; physical path redundancy is added by design where a function needs it.
Scope

FlexRay
A communication bus; control stays in the ECUs.

ASG
Protocol, real-time OS and channel as one system, covering every electromechanical unit.

Common ground

Both are time-triggered: values arrive at known instants, not whenever a node decides to send.
Both give a consistent per-cycle snapshot of the scheduled signals.
Both are aimed at control, not at bulk data.

The matrix

FlexRay and ASG, side by side.
Dimension	FlexRay	ASG
What it is	A communication bus with a time-triggered schedule layered on top.	A control architecture: protocol, real-time OS and ring channel as one system.
Topology	One or two channels, wired as a bus, a star, or a hybrid.	Single ring routed through the vehicle volume; zones attach within a wire-length budget.
Medium	Dedicated differential pair per channel. Power routed separately.	Power and data on the same conductors (PLC over 12 / 24 / 48 V), or a twisted pair.
Media access	TDMA: fixed slots in a static segment, mini-slot contention in a dynamic segment.	Frequency-division. Each zone has its own carrier (a diad); no contention for the channel.
Timing model	Global schedule you configure: a fixed cycle of static and dynamic slots.	One global commit every 1 ms. Every zone updates in the same instant.
Determinism under load	Deterministic in the static segment once the schedule is validated; dynamic segment is best-effort.	Fixed. Every event lands on the 1 ms grid regardless of how many zones or events.
Raw data rate †	10 Mbit/s per channel.	~2.7 Mbps on the shared channel; capacity added by carriers, not by frame time.
Vehicle-wide state	Partial. A consistent snapshot per cycle for scheduled signals, assembled by the application.	Native. Every module holds the whole committed state vector each millisecond.
Compute model	Sequential per ECU, coordinated by the shared schedule.	Distributed and time-parallel: every module computes on the same state in the same window.
Harness impact †	Two pairs per channel plus power; the most wiring-heavy of the buses.	One ring carrying power and data. ~200-300 m of wiring per vehicle in ASG's own figures.
Fault handling	Bus guardian and dual channels give redundancy against a single-channel fault.	10 us local reaction in each block acts as an electronic fuse; no relays needed.
Standardisation & maturity	ISO 17458. Proven in series production, though newer programmes lean toward Ethernet.	ISO-compliant seven-layer protocol; pre-series. Standard number and assessments still to be cited.
Tooling & ecosystem	Established but narrower, and contracting as programmes move on.	Early. A public simulator; silicon, stacks and test tools are in development.

† derivation still to be confirmed. Legacy figures are the nominal values from the published standards; ASG figures are set out on the methodology page.

Where FlexRay is the better choice today

In production now
FlexRay has shipped in series vehicles since 2006. Its determinism is proven on the road; ASG’s is demonstrated on the bench and in test vehicles.
A known quantity
Integrators know how to build and sign off a FlexRay schedule, and the analysis tools exist. ASG’s toolchain is younger.
Explicit physical redundancy
The dual-channel option is a well-understood answer to single-fault tolerance for safety-relevant functions.
Standard maturity
ISO 17458 is complete and stable. ASG’s protocol is ISO-structured, but the reference is still to be cited and assessments are pending.

Questions

If both are time-triggered, why change?

The difference is where the work goes. FlexRay needs a bespoke schedule designed and re-validated as the vehicle changes. ASG’s schedule is a single fixed window that never changes with content or car.

Is FlexRay’s dual channel safer than ASG?

Physical channel redundancy is an explicit FlexRay strength. ASG’s answer is a fast local reaction in every block plus a simpler harness; where dual-path redundancy is required it is added by design.

Can a FlexRay cluster stay in place during a transition?

Yes. The zone module joins the existing FlexRay schedule as a node, reads its frames, and folds them into the shared vehicle state on the 1 ms commit, replying on the FlexRay cycle where a controller expects it. That translation is built into the module, so a chassis or powertrain cluster can move across one domain at a time with no separate gateway.

Is FlexRay being replaced anyway?

Newer premium programmes tend to move chassis traffic toward Automotive Ethernet with TSN. ASG is a different bet: keep the determinism, drop the schedule and the harness.

Open the simulator Full comparison matrix