Assembly Automation
This section covers how to control the hardware of a booked Assembly programmatically — during a test run or as part of a larger automation flow. There are three complementary approaches:
- Assembly Manager — a C# library for switching devices on and off directly from CANoe test cases, without dealing with access handling or REST specifics.
- Device Sequences — ordered lists of device operations that you save and replay on an Assembly through the vHaaS UI or API.
- Direct HAI REST API — low-level control of the HAI extension boards (multiplexer and relay cards), described below.
Direct hardware control via the HAI REST API
The optional extension boards of an Assembly are controlled by its HAI. Where the hardware itself is described under Fundamentals, the endpoints to drive it are collected here.
Multiplexer boards
See the Assembly page for what the multiplexer board does.
Caution
The multiplexing devices have to be initialized by deactivating all channels
(activate_channel: null).
Configuration body
The configuration endpoint takes a single activate_channel field: a capital character from
A to D to activate that channel, or null to deactivate all channels.
-
Status endpoint — get the current state of the multiplexer hardware.
-
Configuration endpoint — configure the Multiplexer-Board hardware.
Relay cards
See the Assembly page for what the relay card does.
Configuration body
Both endpoints address a specific card via the i2c-address path parameter (a two-digit
hexadecimal string, e.g. 0x27). The configuration body is an array of channel entries, each
with a channel (A–G) and a status ("on" or "off"). Multiple entries can be sent in
one request.
-
Status endpoint — get the current state of the relay-card hardware.
-
Configuration endpoint — configure the relay-card hardware.