Documentation
FieldTalk Modbus Slave Library for .NET
MbusSlaveServer Class |
Base class which implements the Modbus server engine.
SystemObject
FieldTalk.Modbus.SlaveMbusSlaveServer
FieldTalk.Modbus.SlaveMbusIpServerBase
FieldTalk.Modbus.SlaveMbusSerialServerBase
FieldTalk.Modbus.SlaveMbusSlaveServer
FieldTalk.Modbus.SlaveMbusIpServerBase
FieldTalk.Modbus.SlaveMbusSerialServerBase
Namespace: FieldTalk.Modbus.Slave
Assembly: FieldTalk.Modbus.Slave (in FieldTalk.Modbus.Slave.dll) Version: 2.11.0-eval+eb1ecbe71c969eff5d7c05d58da16dade0474678
The MbusSlaveServer type exposes the following members.
| Name | Description | |
|---|---|---|
| MbusSlaveServer | Initializes a new instance of the MbusSlaveServer class |
| Name | Description | |
|---|---|---|
| addDataTable | Associates a protocol object with a Data Provider and a
Modbus slave ID. | |
| Dispose | Implement IDisposable. | |
| Finalize | Destructor. (Overrides ObjectFinalize.) | |
| getConnectionStatus | Checks if a Modbus master is polling periodically. | |
| getPackageVersion | Returns the library version number. | |
| getSuccessCounter | Returns how often a message transfer was successful. | |
| getTimeout | Returns the currently set master time-out supervision value. | |
| getTotalCounter | Returns how often a message transfer has been executed. | |
| isStarted | Returns whether server has been started up. | |
| resetSuccessCounter | Resets successful message transfer counter. | |
| resetTotalCounter | Resets total message transfer counter. | |
| serverLoop | Modbus slave server loop | |
| setTimeout | Configures master transmit time-out supervision. | |
| shutdownServer | Shuts down the Modbus Server. |
This class realises the server engine. The server engines processes
Modbus messages, parses the function codes and upon receipt of a valid
master query it calls Data Provider methods to exchange data with the
user application.
For a more detailed description which Modbus data and control functions have been implemented in the server engine see section Server Functions common to all Protocol Flavours.
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.