Device-Based Tags

For instructions on how to set up a device, see Devices. For applicable restrictions, see Device View.

Device-based tags retrieve data from physical devices connected to the Cloud via a variety of supported protocols. Choice of the protocol affects the available configurable parameters. Only protocol-matching tags can be created within a device; otherwise, tag setup procedure is the same as for function tags at non-device locations.

The following protocols are supported:

Devices generally share the following parameters:

Name, Custom name
Device labels used across different interfaces; see explanation here.
Enable(d)
Unless checked, the Edge server will not attempt connecting to the device.

Tag Editor provides general coverage of tag parameters; special remarks on devices and device-based tags as well as information on their uniquely implemented parameters can be found in the respective articles above.

The following terminology is used in these articles:

Server
Entity responsible for handling tag-collectible, client-receivable data; also the recipient of writable values. Contextually may refer to software, firmware, or device-level logic.
Client
The Edge server, which functions as the recipient of tag-collectible data and/or pushes writable values to the server.
MQTT falls out of these definitions since its two-way communication model involves middleware that acts as a server; see MQTT for details.
Target device
Physical hardware the Edge server connects to, either directly or via networking stack or other form of middleware; typically hosts, provides, or acts as, a server.
Data endpoint
A single variable, whether a scalar or an array, whose value is communicable by means of a tag. Readings from a temperature sensor, valve positions, flow meter data, etc. are typical data endpoints for the Cloud.
Edge server
In the context of the Cloud, the hardware and software package that provides an interface between devices and the Cloud. Additionally, the Edge server contains the local database for history storage; it also runs local HMI and hosts its web UI.

Sub-articles hereunder omit information on TCP/IP stack configuration and/or other networking parameters.