Standard Industrial Protocols

Modbus TCP

The Modbus protocol, developed in the 1970s, allows an application to query a server, and to retrieve and/or write values. These values represent sensor readings or control set points. But note, the variable names and the units are not provided when querying a Modbus server, only the values.
Modbus may be used as a base and therefore has derivatives developed by organisations or companies (e.g. Sunspec protocol) that meet industry specific requirements.
Make sure to enable Modbus TCP for read and write on the machine(s). Similarly to the static IP address, this can usually be done in the network settings of the machine or in a web portal that communicates with the machine. Note the Modbus port that is used for the machine as this will need to be sent to the person implementing the connections.
Make sure the machine is not open to the Internet as Modbus does not have any inherent security. Again, this can usually be done in network settings.
Once Modbus TCP has been enabled on the machine, there are several setup parameters that need to sent to the person implementing the connections in order to ensure a successful connection:
1. Machine brand and model: This allows us to understand the type of machine that is being connected. 2. Preferred name for machine: This allows us to name the data source correctly.
3. Modbus TCP type: Standard Modbus TCP, industry specific Modbus, etc.
4. IP Address: Provide the static IP address of the machine.
5. Modbus Port: Default value is usually 502. If different, please send to the person implementing the connections.
6. Modbus Address: Default value is usually 1. If different, please send to the person implementing the connections. If multiple machines are connected, they each need a unique address, and these must all be sent to the person implementing the connections. Note: this is NOT the IP address, it is a separate value.
7. Register mapping: A mapping of all the variables to their Modbus registers is required, which can often be found in the machine's manufacturing guide. In this case, the guide should be sent to the person implementing the connections.

Ethercat

If the machine communicates via Ethercat, please consult your Ardexa Account Manager.

Profibus

If the machine communicates via Profibus, please consult your Ardexa Account Manager.
Copy link
Outline
Modbus TCP
Ethercat
Profibus