Tags: 
M2M API
3rd party HW-SW

This application note AN82 demonstrates how to control power outputs on NETIO PDUs from the Evertz MAGNUM-OS broadcast control platform using the MAGNUM-OS Reflex engine

Do you have any questions?

The integration enables broadcast facility operators to manage power distribution directly from the MAGNUM control room — including remote outlet switching, power-cycle (reset), real-time energy monitoring, and alarm correlation via MAGNUM-NMS.

 

NETIO PDUs connect to MAGNUM-OS via the NETIO JSON API (HTTP REST). Once configured, Reflex periodically polls the NETIO device for outlet status and energy data, and exposes ON/OFF/Reset commands as MAGNUM control actions. Outlet state changes can be surfaced as alarms in the MAGNUM-NMS alarm table, enabling power events to be correlated with other broadcast facility events.

 

Integration highlights

  • Read NETIO device name, outlet names, and outlet ON/OFF states
  • Switch any outlet ON, OFF, or trigger a Reset (power cycle)
  • Read per-outlet electrical measurements: Load (W), Current (mA), Voltage (V), Power Factor, Phase, Energy (Wh)
  • Display outlet status and measurements on a MAGNUM Control Dashboard
  • Generate MAGNUM-NMS alarms on outlet state change (e.g. Output 1 Off Alarm)
  • Support multiple NETIO PDUs simultaneously — one Reflex driver instance per device

 

 

 

Configuration of NETIO device within EVERTZ MAGNUM OS

The integration relies on the NETIO JSON API (over HTTP/HTTPS). MAGNUM uses its built-in JSON Datasource and HTTP request capabilities to send commands to the PDU and receive status updates.

 

Preparing the NETIO Device

  • Log in to the NETIO device web interface.
  • Go to M2M API Protocols >> JSON API.
  • Enable the protocol and set Enable READ-WRITE.
  • Configure a Username and Password for the API (e.g., netio / netio).
  • Save changes

 

 

 

Configuring MAGNUM OS Reflex driver

The NETIO Reflex driver is provided as a pre-built MAGNUM-OS Reflex configuration (.yaml). Import it into MAGNUM-OS and configure the following parameters:

 

  • In the MAGNUM-OS web interface, navigate to the Reflex configuration section.
  • Import the NETIO Reflex driver configuration file.
  • Set the device IP address and credentials:
  • url: http://{NETIO_IP_ADDRESS}/netio.json
    • username / password — match the Read-Write credentials from Step 3.1
    • Set the polling interval (recommended: 2000 ms).
  • Map Reflex context variables to MAGNUM Control Dashboard widgets (outlet state buttons, measurement labels).
  • Optionally configure MAGNUM-NMS alarm rules: trigger an alarm when any outlet State changes to 0 (OFF) unexpectedly.

 

Special thanks

Let us thank especially Derek Louwerse from  EVERTZ for the module development. We are excited to have such partner as Derek.

 

FAQs

 

  • Can one MAGNUM-OS instance control multiple NETIO PDUs? Yes. Create one Reflex driver instance per NETIO device IP address. Each instance is independent
  • Can NETIO outlet alarms appear in MAGNUM-NMS? Yes. Reflex can feed outlet state changes into MAGNUM-NMS alarm tables, enabling correlation with other facility alarms.
  • Is polling or event-driven communication used? Reflex uses periodic HTTP GET (configurable interval). Control commands (POST) receive an immediate JSON response.

Ask for a price or technical parameters

For device testing use name/password demo/demo