Monitoring is the ability of the edinn system to obtain data directly and automatically from the processes.

The edinn system has a powerful architecture which totally isolates, from the "brain" of the system, the data acquisition. This allows different monitoring methods to be valid and they all generate exactly the same results in terms of information analysis and management. The idea behind is: you provide basic data from your processes, and the edinn system will provide you with all the valuable information.

The edinn system allows different methods to monitor processes:

  • edinnBOX_1: this monitoring method connects with edinn monitoring BOXes (eBOXes). Please find more information here.
  • URL (edinnHIP): by sending URLs to the server, we are sending and receiving data to and from the system.
  • edinn OPC Bridge (edinnHIP): installing an application named edinn OPC Bridge in the server of the organization connects to the OPC Server, the OPC Bridge will automatically send data from the OPC Server installed locally where the edinn OPC Bridge is intalled, to the edinn server.
  • OPC (DA and UA): the edinn system is an OPC client which can connect to virtually every OPC Server. This monitoring method is not explained in this manual.
  • Manual: is when the user manually indicates results or other situations by using the edinn terminal or other manual methods.
  • Cameras (Vision): it allows to detect presence and pass of a product by using IP or USB connected cameras. This monitoring method is not explained in this manual.
  • MQTT: allows to connect to brokers (or servers) using this protocol.
  • Other: there are other monitoring methods (for example FaconSvr) and no limitation has been found so far in terms of monitoring.

Need help?