...
For more information on the general use of the I/O Interface Configuration, see I/O Interface Configuration.
General Configuration
Use an RT core for asynchronous computation |
|
VerboseEnable verbose mode | If enabled, additional information is displayed in the HYPERSIM log during the loading of the model. |
| Enable virtual mode | In virtual mode, the model can be executed even if this I/O interface is not compatible with the hardware configuration of the system. The connections between the model and the I/O interface will be done during the initialization, but the I/O interface will not do anything. The virtual mode can be used to troubleshoot problems on a system without having the required hardware, or to prepare a model with different I/O interfaces even if the final hardware platform is not available. |
Slave Configuration
General Parameters
Mode | Select TCP or RTU. |
| Slave ID | ID of the Modbus slave. Each slave must be configured with a unique identification number. This is due to the fact that:
|
Cycle output rate (ms) | Defines the rate (in milliseconds) at which the data from the model is written in the slave's outputs (coils and holding registers). When the slave's outputs are controlled both from the model and from the master, this parameter must be set to a value greater than the time step of the model. Otherwise, the write operations made by the master are never reflected in the model. |
Byte ordering | Defines how 32-bit data is encoded. Any of the byte ordering cases are possible (ABCD, BADC, CDAB, DCBA). ABCD refers to the network byte order. |
| Permit read/write requests with address gaps | From the lowest address to the highest address configured, this option creates dynamically new coils, discrete inputs, holding registers and input registers at every address that is not defined by the user and assigns a value of 0. |
TCP Specific Parameters
NIC name | The desired network interface name. The proper interface name should be selected based on the information given by the Linux command "ifconfig". If a Modbus master is running on the same machine as the Modbus slave, the loopback network interface must be used ('lo'). If the driver is running on Windows this field will be ignored. |
IP address | The IP address of the Modbus slave. If a Modbus master is running on the same machine as the Modbus slave, the loopback IP address must be used (127.0.0.1). |
TCP port | Select the TCP port on which the slave will wait for a connection. |
RTU Specific Parameters
Modbus slave ID | ID of the Modbus slave. In RTU mode, many slaves can be connected on the same physical serial link. Because of that, each Modbus slave must be configured with a unique identification number. |
Serial port | Path to the serial interface to be used. The default serial interface name of the first port on a SuperMicro motherboard (OPAL-RT chassis) is "/dev/ttyS0". |
Serial baudrate | Speed at which Modbus RTU slave is configured to communicate. |
Serial data bits | Number of data bits the Modbus RTU slave is configured to communicate. |
Stop bits | Number of stop bits the Modbus RTU slave is configured to communicate. |
Serial parity | Parity at which the Modbus RTU slave is configured to communicate. |
...
. |
For each slave instance, the inputs and outputs must be configured. The slave will reply to the master requests continuously as fast as possible.
...