Belden Horizon Data Operations is an operating system on an Industrial PC (IPC) appliance. This edge-level software seamlessly collects data from IoT devices/systems (such as sensors and PLCs) and integrates the data into the cloud or into on-premise enterprise systems. Extensive knowledge of 250+ device drivers, both legacy and newer systems, enables Belden Horizon Data Operations to manage the variety of devices in an industrial environment. Belden Horizon Data Operations software provides support for many protocols/buses (RS232, RS485, CAN, Ethernet, Fieldbus). The raw or processed data can be visualized and analyzed at the edge or sent to Belden Horizon Data Manager, in near real time.

Contact Belden to schedule a Belden Horizon Data Operations Demo.

The latest versions of the following browsers:

If you encounter any issues with Belden Horizon Data Operations, make sure to remove any ad blockers.

Try the Belden Horizon Data Operations Installation and Deployments guide to start learning about concepts and procedures.

Yes, you can use Belden Horizon Data Operations without Belden Horizon Data Manager. You can collect data from a device and visualize data through Belden Horizon Data Operations with the DeviceHub and Flows components.

No, you should only access the machine using the WebUI or the provided Terminal User Interface.

Outbound

Inbound:

Yes. You can use the LDAP/Active Directory. In the Belden Horizon Data Operations navigation panel, select System > LDAP/AD Auth.

You can attempt to log in five times before you are locked out. With each attempt, the timeout increases until you are locked out after the fifth try. You can restart to reset the timeout counter.



An admin can reset a user's password from the System > User pane. The user must restart after a reset by the admin. An admin password cannot be reset due to security. If you are an admin that has forgotten your password, you must reinstall.

Upgrade is next to the core license on the License pane. Only a single core license is allowed. If you have a different core license, you can use Upgrade. Using Upgrade replaces the current core license.



Add License on the License pane is used to add a feature/pack license such as Analytics or a Marketplace add-on.

Use Upgrade next to the core license on the License pane. You need a .upd file for the new version and a currently installed version of Belden Horizon Data Operations that supports upgrades to the new version. See Software Updates for details on which version you must start from to begin the upgrade process from Belden Horizon Data Operations.

Review the Industrial Systems Connection Guide.

DeviceHub provides the mechanism for connecting to physical devices (PLCs, sensors) to collect data from them.

Try double-checking connection parameters and firewall settings.

Use the Remote Access service, along with Belden Horizon Data Operations and Belden Horizon Data Manager configurations.

No, the PLC cannot be programmed from Belden Horizon Data Operations. The PLC (Programmable Logic Controller) needs to be already programmed before setting up in Belden Horizon Data Operations. Belden Horizon Data Operations reads the PLC data.

Try setting the polling interval for DeviceHub Tags. See Add Tags for more information about length of time. Polling PLC registers too often may cause too much data to be sent over the network from which the Belden Horizon Data Operations is connected.

Flows offers flow-based programming with a drag-and-drop flow editor. It is for data manipulation, data normalization, and visualization.

Flows has an import/export feature to share flows.

The Flows Manager module has a max limit of 4 concurrently running flows. If a flow crashes, the module tries to restart it 5 times, and then stops it permanently. This causes the module to reach the limit, which generated the “limit reached” error. When you see that error, download the flow file, delete the flow instance. start a new one, import it, and then edit the flow logic to make sure it will not crash. Soon a warning status will be implemented for the flows, which is expected to obviate the confusion.

Before exporting nodes, select the nodes and connecting wires within a flow tab. See Manage the Flow Canvas.

The most likely cause of this is due to the use of custom nodes. If a custom node is used in your flow, you must download and reinstall the custom nodes. Custom nodes are not included in backups.

See OPC UA Client for more information about supported servers.

For containers, we rely on the security that Docker offers. For deployment, you can use certificate-based authentication to add a private registry (Belden Horizon Data Manager, quay.io, Google Container Registry - GCR, Azure Registry, Docker Trusted Registry, Docker Hub.) and then use images on these registries to launch containers.

The Applications > Containers section only displays containers that are currently active or stopped.

Since none of the uploaded images have been used with a Docker command, the Applications > Containers section does not display anything related to those images. You must construct the correct Docker command and run it.

Only after running the Docker command will anything related to the uploaded images appear in the Applications > Containers section.

See The Docker Run Command-Line Reference for more information about how to structure a Docker command to run a container.

If you ran the Docker command and the image does not appear in the Applications > Containers section, open a new ticket, and provide the Docker command that was used.

Belden Horizon Data Operations does NOT have MQTT broker. It has an MQTT client. However, you can launch a container with MQTT broker and connect to it.

For the System>External Storage feature, passwords with the special character comma(,) are not supported. Change the password to not contain comma or commas.

A Backup is a .DAT file that cannot be customized and contain a predetermined list of configuration settings.



A Template is a .json file that can be customized to contain a list of selectable configuration settings.



The key difference between the two are the use purposes. Restoring a hardware-damaged Belden Horizon Data Operations Device should be done with a Backup while cloning a Belden Horizon Data Operations Device to other devices should be done with a Template.



Furthermore, a restore operation will replicate and overwrite the Belden Horizon Data Operations device's system state from the backup (.DAT) file. On the contrary, a Template upload operation will append (and not overwrite) its configurations settings to the Belden Horizon Data Operations device.