As we finish 2019, we’re delighted to inform our customers and channel partners of the latest TBox Protocols and how TConnect can take the pain out of M2M remote connectivity.
Available from November 2019; the OPC-UA protocol will be available on the TBox LT2, TG2 and MS32(-S2).
OPC-UA on the TBox supports:
- 4 x simultaneous "client" connections - DA: Direct Access, to read and write Tags "on-line" - HA: to collect historical data of TBox, stored in Sampling Table and Chronologies - encryption and authentication through libssl.
It supports automatic configuration using TBox Tag in NodeSet2 or you can create your own NodeSet2 with your own structure of data (variables, objects, hierarchy, dependencies, methods).
Benefits of OPC-UA
OPC Unified Architecture (UA) is a new communication technology standard that was first released by the OPC Foundation in 2006 as an improvement on its predecessor, OPC Classic. OPC UA includes all the functionality found in OPC Classic. One of the most benefits is the expanded security features: OPC UA servers and clients rely on unique certificates to communicate with one another. As a direct result of the standardized security model, OPC UA allows for easy integration into pre-existing IT networks which limits configuration costs
Because of the benefits of this new protocol, more and more industrial applications have adopted the UA protocol both in the traditional OPC-centric industrial automation space and emerging areas such as energy.
Also available from November will be MQTT (Message Queuing Telemetry Transport) protocol, again available on the TBox LT2, TG2 and MS32-S2.
The MQTT Client add-on allows a TBox RTU to act as an MQTT Client.
MQTT on the TBox supports:
Benefits of MQTT
MQTT stands for Message Queuing Telemetry Transport. It is an open and standardized, simple, lightweight protocol, originally designed for constrained devices, operating on low-bandwidth or unreliable networks. The protocol utilises TCP/IP to ensure delivery of messages without error and in the correct order. These principles make the protocol ideal for “Machine-to- Machine” (M2M) and “Internet of Things” (IoT) applications.
One of the biggest challenges customers are facing with respect to M2M remote connectivity is how to access their RTU (remote telemetry unit) through a cellular network. That’s why our engineers developed TConnect for the TBox.
The primary goal of TConnect is to eliminate this challenge for our customer and end users, therefore making M2M deployment seamless.
TConnect makes connection easy to TBox outstations, to display WebForm 2.0 and reprogram it with TWinSoft, in summary TConnect is a ""facilitator"" of connections.
Who would benefit from TConnect?
Any customer or end user who has:
Or you want to:
And, it goes without saying you require all of this via a secure connection.