hi human interface®
hi human interface®
English
Breadcrumbs

Arkona AT300 // BladeRunner

Arkona AT300 // BladeRunner

Driver Maturity

Production

Recommended for normal production use.

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.

Minimum hi Version: v2.7.0

Overview

In hi 3.0.0, hi controls the Arkona AT300 // BladeRunner as an NMOS IP Transceiver. Use the NMOS Core Integration page for the supported NMOS discovery and connection-management behavior. hi 3.0.0 does not provide an AT300-specific VAPI Parameter Control integration.

Network Requirements

  • Permit hi to reach the NMOS registry and device API endpoints used by the commissioned NMOS workflow.

  • Use the endpoint addresses and transports advertised or configured for NMOS. hi uses no fixed TCP port for the BladeRunner.

  • For general NMOS network and firewall requirements, see NMOS Core Integration.

Standards Conformance

Standard

Conformance

Notes

AMWA NMOS

Implemented by the shared hi NMOS integration

hi controls the BladeRunner as an NMOS IP Transceiver; see

NMOS Core Integration

for API and feature scope.

Operator Workflow

  • UI Surface in hi: NMOS device discovery and routing workflows.

  • Template Selection: The Arkona device template is hidden from the manual template picker; use the NMOS discovery workflow.

  • Template Defaults: hi names a new Node Blade Runner, with short name BladeRunner and product name Blade Runner AT300.

  • Optional Provisioning: A separate Arkona provisioning capability is available. It is disabled by default and enabled by the provisioning workflow.

  • Device Administration: Use Arkona tooling for chassis setup, firmware, and hardware diagnostics.

Connection Details

Property

Value

Protocol

AMWA NMOS IP Transceiver

Transport

As advertised or configured for the NMOS APIs
see

NMOS Core Integration

Default Port

Not specified (device-dependent); use the advertised or configured NMOS endpoint.

Authentication

hi uses no Arkona-specific credentials; follow the commissioned NMOS endpoint configuration.

Encryption in Transit

Follow the commissioned NMOS endpoint configuration; hi has no Arkona-specific TLS setting.

Connection Model

hi uses the NMOS registry and device endpoints

Required License

hiNMOS

Traffic Flow

Bidirectional NMOS resource and connection-management traffic

Required Configuration

Parameter

Description

Default

NMOS discovery and endpoint configuration

Configure according to the

NMOS Core Integration

page and the device's advertised resources.

-

Device-Side Setup

Follow Arkona AT300 // BladeRunner Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature

Access

Exposed Operation and Scope

NMOS IP Transceiver

Read-only discovery and read/write connection management

hi controls the device through the shared NMOS IP Transceiver workflow. Its supported NMOS operations are defined on the

NMOS Core Integration

page.

Arkona Provisioning Capability

Provisioning workflow
disabled by default

A separate capability that the provisioning workflow enables. It is not Parameter Control.

Device Coverage

Tested With identifies devices that have been tested with hi. Potentially Compatible (Not Yet Verified) identifies devices that use the same protocol or connection method but have not been tested with hi. Device-specific configuration, firmware, and feature support can affect results.

Tested With

  • Arkona Technologies AT300 BLADE//runner

Potentially Compatible (Not Yet Verified)

Known Limitations

  • Validate the BladeRunner's NMOS resources and connection behavior on the installed firmware.

  • The optional provisioning capability is disabled by default.

  • hi applies this template to an NMOS Node and Device only when both identify as a BLADE//runner: the NMOS description contains blade and runner, an asset tag names the manufacturer arkona-technologies or the product AT300, or the label contains AT300. Otherwise hi uses the generic NMOS Node template. The label can be renamed on the device, so hi uses it only as a fallback.

  • The BLADE//runner transmit and receive driver software assumes IPv4, and the blade does not list IPv6 addresses. Use IPv4 addresses for the NMOS registry and the blade.

  • BLADE//runner release 2.7 is not state-compatible with earlier releases. Adapt the configuration scripts and apply them again after the upgrade. After such an upgrade, confirm that the blade still registers with the NMOS registry that hi uses.

What's Not Supported

  • AT300-specific Arkona VAPI schema-based Parameter Control, including parameter reads, writes, and subscriptions.

  • Direct Arkona VAPI access to /data/schema.json or /socket through a hi device integration.

  • Chassis setup, firmware updates, and hardware-level diagnostics; use Arkona tooling.

Trademarks

Note

Arkona Technologies, AT300, and BladeRunner are trademarks of Arkona Technologies GmbH.

All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.

RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with Arkona Technologies unless explicitly stated.