...
The first page contains some generic configurations.
Here is a description of each generic configuration field. This information is also displayed in tooltips or alt text by hovering the mouse over each of the fields.
Use an RT core for asynchronous computation |
---|
...
| |
Listening timeout (ms) |
...
Total amount of milliseconds the driver waits for a response when sending a command to the PMU. | |
Enable verbose mode |
...
If enabled, additional information is displayed in the HYPERSIM log. | |
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. |
Master Configuration
When creating a new C37.118 master I/O interface configuration, one device is preconfigured with the following editable settings:
These parameters are applied to one PMU that the C37.118 master driver attempts to communicate with to get its measurements measurement data:
ID |
---|
...
Identifier of the PMU, as described per IEEE Std C37.118.2-2011 standard. The C37.118 master must know the identifier of the remote PMU it is connecting to. If the ID is not correct, users cannot receive data from the remote PMU device. | |
Protocol |
...
Select TCP, UDP or TCP and UDP depending on how the remote PMU device is configured to communicate. TCP port: Specifies the TCP port to be used by the C37.118 master to establish a connection with the C37.118 slave (PMU). |
...
Only visible when operating in TCP or in TCP+UDP mode. UDP port: The UDP port to be used by the C37.118 master to establish a connection with the C37.118 slave (PMU). |
...
Only visible when operating in UDP or in TCP+UDP mode. Use specific port for reception: Only visible when operating in UDP.
NIC name: Desired network interface name. The interface name should be selected based on the information given by the Linux command "ifconfig". For testing purposes, if users must connect the C37.118 master driver to an instance of the C37.118 slave driver running on the same simulator, the loopback network interface must be used ("lo"). IP address: The IP address of the remote PMU. For testing purposes, if users must connect the C37.118 master driver to an instance of the C37.118 slave driver running on the same simulator, the loopback IP address must be used (127.0.0.1). |
Phasors representation |
---|
...
Can be either polar or rectangular depending on the PMU configuration. | |
Phasors format |
...
Can be either INT16 or FLOAT depending on the PMU configuration. | |
Enable automatic data request |
...
If enabled, the C37.118 master driver automatically sends a command to the PMU, once it is connected and receives its configuration. If disabled, a connection point is available to trigger the start of data transmission. | |
Apply phasor factor automatically |
...
As per IEEE Std C37.118.2-2011 standard, each phasor configured in INT16 format can have a factor that needs to be applied to the received value.
| |
Apply digital valid-bit mask automatically |
...
As per IEEE Std C37.118.2-2011 standard, the PMU can send digital values configured with a valid-bit mask. If enabled, the mask will automatically be applied to the received digital values before sending them to the model. |
Each stream has a configurable number of phasors, analog and digital values.
...