MB_InitRTU block
Short summary
Name |
MB_InitRTU |
→POU type |
|
Category |
more system blocks, blocks for Modbus, block with internal error diagnostic |
Graphical interface |
|
Available since |
version 2.0.9 (for library System) for Raspberry Pi as well as |
Functionality
The block initializes a →Modbus/RTU connection and returns a handle which is used with other Modbus blocks to communicate with a Modbus RTU bus coupler.
Note on the usage
In order to determine the state of a Modbus connection, use this block always together with the block MB_GetState . This is for the following reasons:
The connection has not been established yet, when logi.CAD 3 returns from the block.
Usually, it is possible to use the connection for the actual communication only within the next cycle of the application.
Hence, this is valid : It is imperative that you are using MB_GetState in order to determine the state of a Modbus connection within each cycle of the application. Make sure that the application contains the required steps depending on the return code of MB_GetState. Do not use internal variables within the application for determining the state of a connection.
Inputs, outputs
|
Identifier |
Description |
|
Inputs: |
Device |
STRING |
device name of the Modbus RTU bus coupler |
Baud |
DINT |
transmission speed for this connection (with initial value 115200) |
|
Parity |
MB_PARITY |
usage of an error detecting bit for this connection as specified in data type MB_PARITY |
|
DataBit |
DINT |
number of data bits for this connection (with initial value 8) |
|
StopBit |
DINT |
number of stop bits for this connection (with initial value 1) |
|
TimeoutRW |
TIME |
timeout for read/write function calls (with initial value T#500ms) |
|
Outputs: |
MBHandle |
DINT |
a handle which identifies the connectiont (with initial value -1) |
RC |
DINT |
return code of the function call:
|
Input EN and output ENO are available when →calling
the block. See "Execution control: EN, ENO" for information on input EN and output ENO.
Internal error diagnostic for block
The block checks the following error cases (if applicable for the block):
The resources necessary to establish the connection (e.g. memory) are not available.
The requested function of the Modbus stack could not be executed.
The forwarded handle is not valid (anymore).
The requested amount of data cannot be processed by the Modbus connection.
There are no more handles to establish the connection (up to 256 connections can be established at present).
An internal problem of the Modbus connection occurred.
The LibModbus system service has not been loaded and/or you have no permissions to use Modbus (no enabled feature in the license for the →runtime system).
In such an error case, the output ENO of the block is set to value FALSE (or an equivalent). Moreover, the output RC returns the appropriate code (see the above table under RC).
Example for usage within ST-editor
Best practice in order to get to know the usage of the Modbus blocks: Create a new project based on the project template Moving Light with Modbus Access and study this sample project. This project does not contain a usage of this block but of other blocks. Please study those in order to get to know how to use this block.