Querying Component Status with TCP

Each Component in Hippotizer has a string pin to report it’s status in real time. These can be found in the pin tree under each component.

The status pin carries the state of the component and an info tag.

The state can be:

• Config
• Run
• Limited
• Problem

Each component has specific responses

DMX2

If no Devices have been created it will return an empty string, if one or more devices are enabled it will return a comma separated list of the status of each Device:

Example:

“Artnet0:OK,Artnet1:OK,Artnet2:No Data,sACN_1:OK”

It will give an OK if and DMX data has been received at a rate of 1 Hz or more. On each device universe.

Sync Component

Will return: Running or No Data for each of the two External Timecode sources separated by a comma:

Example:

“EXT1:Running,EXT2:No Data”

Output Manager

Will be one of the following:

“Just Started”
“Waiting for Engine Component”
“Waiting for Engine Component to Start”
“Waiting for Eingine Component to Reconfigure” -> yes, there is a spelling mistake !
“Running”
“Configuring”
“Error – Waiting for Reset”
“Unknown”

LED Component

Returns one of the following statuses

“run” -> normal operation, no problems
“config” -> one or more components are being reconfigured
“limited” -> there is an issue that is not stopping system from working but needs attention
“problem” -> A major issue is stopping normal operation of the system

For all of the above except “run” there is also a component name and a description of the issue or operation, far too many to list here.

Example:

“System Status=run, Message=”

Or

“System Status=config, Message=Media Manager : Media Files Syncing”

Or

“System Status=problem,Message=Engine : Viewports Overlapping On Output”