Difference between revisions of "Modbus Interface"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | This article describes the | + | This article describes the Modbus interface available in Exigo. |
| − | {{Note}} ''The | + | {{Note}} ''The Modbus Interface is not official implemented.'' |
The Exigo Controller implements a Modbus TCP slave (server) interface on the standard Modbus port, TCP port 502. The Modbus interface in Exigo has two main features: <br> | The Exigo Controller implements a Modbus TCP slave (server) interface on the standard Modbus port, TCP port 502. The Modbus interface in Exigo has two main features: <br> | ||
| Line 7: | Line 7: | ||
* Pre-programmed PA calls and announcements can be triggered by writing to Modbus coil registers. | * Pre-programmed PA calls and announcements can be triggered by writing to Modbus coil registers. | ||
| + | == Exigo status to Modbus == | ||
[[Category:Exigo features]] | [[Category:Exigo features]] | ||
Revision as of 10:37, 19 March 2019
This article describes the Modbus interface available in Exigo.
The Modbus Interface is not official implemented.
The Exigo Controller implements a Modbus TCP slave (server) interface on the standard Modbus port, TCP port 502. The Modbus interface in Exigo has two main features:
- Status about amplifiers and panels connected to the Controller can be read from Modbus 16 bit input registers
- Pre-programmed PA calls and announcements can be triggered by writing to Modbus coil registers.
