- Sparkplug Plug-in
- HiveMQ
- Access to WAGO IoT Cloud
- Connection with ORACLE CLOUD
Sparkplug Plug-in
Thanks to the MQTT messaging protocol, connections between Cloud platforms and devices have been simplified. By possessing a minimal latency, we can say that an MQTT Cloud connection is an excellent solution for the industry. However, for some machinery and devices, establishing an MQTT Payload can be an inconvenience. The problem is solved thanks to the incorporation of the Sparkplug Plug-in in the new version of OPC Router V.4.28. Sparkplug provides a predefined MQTT Payload scheme, ensuring greater simplicity and speed when deploying the solution in an industrial environment.
New Partnership with HiveMQ
The incorporation of the MQTT broker developed by HiveMQ ensures that data transfer will be reliable, fast, and efficient. The broker sends and receives messages and information with the corresponding MQTT clients. With this new tool, we seek to facilitate the implementation and digitization of industrial environments.
Access to WAGO IoT Cloud – with WAGO Cloud Profile
The new Version 4.28 of OPC Router allows you to connect to WAGO Cloud, where you can store and analyze data from different devices and machinery. Now, with the new WAGO Cloud profile, configuration is simpler and allows direct access to data from WAGO devices.
Other New Features of Version 4.28
MQTT 5 Available in OPC Router
The new version of OPC Router incorporates the plug-in to use the new specification of MQTT 5. The new features are mostly for applications that are implemented in the Cloud, which require robustness and good error management, thus allowing the implementation of mission-critical communications. On the other hand, they also seek an easier integration of MQTT messages into existing infrastructures.
Among the new functions, we can highlight the possibility of adding an expiration time for messages and sessions. If a message is not delivered within a predefined period, the message is deleted. For example, suppose we send an MQTT message to start a machine that is critical for safety in the plant. If the message does not arrive within the determined period, it can be configured to be automatically deleted. This ensures that the message is delivered only when it is safe to start the machinery and never delayed due to latency or network interruptions.
Another function to highlight within the update is the inclusion of the concept of “negative acknowledgements” (Negative Acknowledgement). Based on predefined restrictions, the broker can perform recognition and reject particular messages. Restrictions can be based on maximum message size, quality of service (QoS), restricted functions, etc. In this way, we prevent erroneous messages or DoS (denial of service) attacks from being executed, since the broker can automatically reject these messages due to size or other predefined restrictions.
Extension in Email Plug-in
In early October, Microsoft changed the authentication of emails, for this reason, OPC Router clients who use the Email Trigger function will benefit because a more secure authentication process has been implemented.
We offer you the possibility of downloading a demo version so that you can see the new functionalities in operation. If you have any questions, do not hesitate to contact us.
