Automated systems

Simple and complex automated systems are consistently making in-roads into everyday life.

Such systems started gaining traction in the manufacturing industry several years ago, and their uptake continues to rise unabated.

An automated system comprises two parts: the operative part performs the operations, while the control part, which takes the form of a programmable logic controller, manages the inputs and sends orders to the operative part.

The operative part can be broken down into two major families: actuators which perform a physical action (movement, rotation, etc.), and sensors which detect and send information about the physical action.

Protocols have been developed to allow all these components and the two parts of the automated system to communicate with each other. Some communication protocols are proprietary, while others are freely distributed.

ALERT is capable of retrieving information directly from the source using such non-proprietary protocols as BACnet (dedicated protocol for building automation and control) and Modbus, so that operators can be clued into any incidents affecting the system.

BACnet protocol

The BACnet protocol was masterminded by ASHRAE (American Society of Heating, Refrigerating and Air-Conditioning Engineers).

BACnet is currently an open standard protocol (ANSI and ISO) that is recognized around the world. It is designed to allow for data delivery between building management systems for applications such as ventilation, air-conditioning, lighting, access control and fire safety systems and their associated services.

ALERT features a dedicated BACnet interface for managing technical alarms generated directly by BACnet devices without any need for a third-party system.

Micromedia International is actually a member of the BACnet France association.

Modbus protocol

Modbus is a non-proprietary communication protocol that is used extensively in programmable logic controller networks (PLC).

Its simple design and reliability have proven a tremendous success ever since the protocol was developed in 1979. Modbus was initially designed to work through serial data lines (RTU mode), but it continues to enjoy mainstream status after the protocol was scaled up to support Ethernet networks (TCP mode).

A Modbus network comprises passive slaves/servers (RTU mode/TCP mode) and an active master/clients (RTU mode/TCP mode).

ALERT offers a dedicated Modbus interface for connecting in RTU and TCP mode as the master/client to fetch the necessary information for managing alarms. Commands can also be used to write in the Modbus variables to interact with the devices if necessary.

For further details, please do not hesitate to contact us.