Arkona AT300 // BladeRunner Integration Configuration

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Configuration Overview

A BLADE//runner reaches hi through NMOS. The blade registers with the NMOS registry that hi uses, and hi creates the Node from the registered resources. There is no manual template to select and no Arkona-specific setting in hi.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the license and minimum hi version in Required Configuration.
Commission the NMOS Core Integration first, and record the address of the NMOS registry that hi uses.
Use Arkona tooling for the device-side steps.
Confirm the network access in Network Requirements.

Configure NMOS Registration

Use this configuration to route BLADE//runner Senders and Receivers from hi.

Device Configuration

Confirm that NMOS IS-04 and IS-05 are enabled on the AT300. BLADE//runner supports both.
Set the NMOS registry address of the blade to the registry that hi uses. Open the web landing page of the blade, open the menu, and select Quick setup > NMOS to open the basic NMOS setup dialog. The Help section of the Advanced Settings page of the blade describes the NMOS configuration in detail. The Arkona API also exposes an NMOS enable setting, the IS-04 registry address as a writable setting, and the registry connection as a read-only status.
Keep the NMOS description, the asset tag, or a label that contains AT300 unchanged on both the NMOS Node and the NMOS Device of the blade, so that hi can identify it as a BLADE//runner.
When the blade needs device provisioning, use the Arkona provisioning workflow separately.

hi Configuration

Confirm that the NMOS registry and discovery workflow run as described in NMOS Core Integration.
Wait for hi to create the Node. hi names it Blade Runner by default.
Confirm that the Senders and Receivers of the blade appear on the Node.

Settings Summary

Setting	Device Side	hi Side
NMOS registry	IS-04 registry address of the blade	Registry used by the hi NMOS integration
Identification	NMOS description or label of the Node and the Device	Applied automatically no setting

Common Checks

Symptom	Check
The blade does not appear in hi.	Confirm that the registry connection status of the blade shows a connection, and that the registry address matches the registry that hi uses.
The blade appears as a generic NMOS Node.	Confirm that the description of both the NMOS Node and the NMOS Device contains `blade` and `runner`, that an asset tag names the manufacturer `arkona-technologies` or the product `AT300`, or that their label contains `AT300`.

Verify the Configuration

Confirm that the Blade Runner Node shows the Senders and Receivers of the blade. Connect one noncritical Receiver to a Sender from hi, and confirm in Arkona tooling that the Receiver follows.