Tags: 
3rd party HW-SW

The AN75 demonstrates how to control power output(s) on NETIO devices from the Q-SYS enviroment by using JSON API.

Do you have any questions?

Support devices:

  • NETIO: all devices running with FW 4.0.5. **
  • Q-SYS:Q-SYS Designer 9.2+ 

**Note: functions as (temperature read out, Energy counter reset, Output rename available from NETIO FW 5.0.3++

 

NETIO device can be control following way via Q-SYS ecosystem:

  • Switch any socket ON/ OFF/ Reset
  • Switch all sockets ON/ OFF/ Reset with individual delay
  • Read out the energy consumption data at NETIO devices supporting power meatering function
  • Others: Device name, Temperature, UpTime, State, Reset Energy Counter…etc

 

 

 

 

 

Configuration NETIO device Q-SYS driver – JSON API

1) Configuration of NETIO device

  • Open the web-interface of NetIO PDU and select M2M API Protocols option
  • Select JSON API and check Enable JSON API checkbox
  • Enable READ-WRITE option
  • If you enable both READ-OLNY and READ-WRITE options, be sure to use read-write credentials in Crestron module to be able to control outputs.
  • Push “Save Changes” button

 

 

 

2) Open Q-SYS Designer. From Plugins module select NETIO Networked Power Socket

 

 

 

3) From Plugins properties - select required model f.e. PowerPDU 2Kx

 

 

4) click File-> Emulate

 

5) Specify Connection Setup details:

  • (IP Address, Port, Username, Password…). Username & Password shall match with values from Step1 - Configuration of NETIO device

Accordingly, you should be able see Connection Setup Status

 

Empty Connection setup Connection Setup confirmed – status OK Connection Setup not confirmed -Status Connection lost – wrong Port number

 

 

6) Plugin overview Control & Measurement

After successful device connection, details will be displayed

 

Plugin Control Section Plugin Electrical parameters measurement section

 


 

FAQs

Is there any limitation as Max number of devices (IP addresses)?

No, One device per plugin, maximum number of plugins depend on what Core the plugins are running on.

 

Is there any limitation with Max number of programs running?

One program per Core, Q-SYS calls it design, so one design per Core.

 

Is communication drive by “event” or  by “time period”?

It is both "event" and "time period", it reads the values like current, phase etc. of the device each 300 ms.
 

Ask for a price or technical parameters

For device testing use name/password demo/demo