Introduction
The Devices module offers a comprehensive suite of features for connecting to, configuring, and monitoring various devices like PLCs, sensors, actuators, and other data acquisition devices. This includes support for multiple protocols such as Modbus, OPC, and TCP/IP, ensuring seamless connectivity and interoperability between different devices and systems.
Additionally, our platform provides configuration and diagnostic tools to simplify device setup and management. These tools include device discovery, network scanning, and real-time monitoring of device status and performance. Users can also adjust device parameters like data acquisition intervals, thresholds, and alarms to optimize system performance and efficiency.
On this page:
Key Functionalities
Over 50+ Native Communication Drivers
Connectivity is a crucial aspect of our platform. We support a broad array of industry-standard protocols, facilitating seamless communication with PLCs, historians, databases, and other devices. We continuously add new drivers, and our SDK simplifies the process of adding any additional driver not already included.
MQTT Tools
We've integrated a built-in MQTT Broker into our platform, offering standalone operation or integration with specific projects. When linked to a project, our MQTT Broker can expose all project namespaces and properties.
Our broker supports Sparkplug B clients and original MQTT clients, including those that don't adhere to the Sparkplug B specification like Mosquitto, as well as Azure IoT. We also provide an MQTT Client simulator (with Sparkplug) to streamline testing and accelerate development.
HiveMQ Integration
As your applications grow or if you seek the benefits and support of an enterprise-class MQTT Broker, you can purchase a bundled HiveMQ subscription license with any product.
OPC-UA
Our platform’s projects can seamlessly function as an OPC-UA server and can also act as an OPC-UA client to interact with other servers. Additionally, our platform supports OPC-DA Server, OPC-DA client, OPC-XML-DA, and OPC-HDA for enhanced compatibility with legacy systems.
Store-and-Forward
We've incorporated Store-And-Forward functionality into our software platform when publishing data to the Canary Historian or an MQTT Broker. This means we temporarily store message data for later transmission to its destination if the network is inaccessible for any reason.
Process Isolation and Multi-threading
Data communication operates within its own .NET domain, utilizing a WCF layer to isolate the drivers from the main real-time database. We create multiple threads for each protocol and device node to ensure maximum performance.
Built-in Performance Monitoring
We generate statistics on system messages, success and error messages, dynamic blocks created, cycle time, and execution time on each block. This allows for fine-tuning high-performance applications. Additionally, our comprehensive set of testing, deployment, and diagnostics tools ensure fast and reliable application development and installation.
Devices negative error code
For Module Information and Property Watch, there are negative error codes that represents specific messages that can help to find the root cause of the error. In the Module Information, refer to the LastErrorCode column. On Property Watch, refer to @Device.Channel.ChannelName.Status. See below the list of negative error codes:
- 0 Success
- -1 BuildCommandException
- -2 ParseCommandUnsolicitedException
- -3 ParseReplyException
- -4 BuildReplyUnsolicitedException
- -5 ChannelException
- -6 NodeException
- -100 Base Send Error
- -101 Base SendAndWait Error
- -102 TCP Create Error 1
- -103 TCP Create Error 2
- -104 TCP Create SocketError
- -105 TCP Connect Callback Error
- -106 TCP Receive Error
- -107 UDP Create Error
- -108 UDP Receive Error
- -109 Serial Create Error
- -110 Serial Receive Error
- -111 TCP NotConnected
- -112 Start message timeout
- -113 Receiving bytes timeout
- -114 End message timeout
- -115 Connect timeout
- -200 ProtocolError
- -201 InvalidProtocol
- -202 InvalidStation
- -203 InvalidCommand
- -204 InvalidMsgSequence
- -205 InvalidCheckSum
- -206 InvalidAddress
- -207 InvalidModifiers
- -208 ProtocolErrorCloseSocket
Infrastructure designed from the Core
Check Communication Drivers.
Learn more at Devices, Field Communication.
In this section...