Accessing the I/O Interface Configuration

The C37.118 master communication protocol is configured in the I/O Interface Configuration tool opened through the HYPERSIM ribbon.

For more information on the general use of the I/O Interface Configuration, see also I/O Interface Configuration.

General Configuration

The C37.118 master I/O interface is configured within several pages. For the moment, the I/O interface cannot be configured directly by connecting to a specific PMU and asking for its configuration. This configuration method is slated for a future release, but for the moment, the user must have the following information to receive phasor, analog, and digital data from a PMU.

• IP address
• Operating mode (TCP, UDP or TCP + UDP)
• TCP and/or UDP ports
• PMU identifier (ID)
• Phasor representation
• Phasor format
• Phasor, analog and digital names

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:
  • If set to true, the driver reserves a real-time CPU core for its communication system and is able to handle a bigger number of slaves and phasor, analog and digital values.
  • If set to false, the communication system defaults to core 0 (running with the operating system).
• 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.

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 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.
    • When enabled, specifies the master UDP port through which packets from the current C37.118 slave are expected.
    • When disabled, this port is chosen randomly from the list of free ports.
    • Local port: Only visible when operating in UDP and when the option Use specific port for reception is selected. As described above, it is the UDP port on which the master is expecting packets from the current C37.118 slave.
  • 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.
  • If enabled, the phasor factor value is automatically applied to the received values before sending them to the model.
  • If disabled, the received values are sent directly to the model but the phasor factor is still available in the model via a connection point. Only available if the phasor format is configured in INT16.
• 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 model.

Each stream has a configurable number of phasors, analog and digital values.

Phasor Configuration

For each phasor, there is a configuration field representing the phasor name that needs to match the phasor name configured in the remote PMU:

Analogs Configuration

For each analog configuration, there is a configuration field representing the analog name that needs to match the analog name of the remote PMU:

Digitals Configuration

For each digital configuration, there is an option to enable the reception of the normal bit states.

• When enabled, a connection point will be available to monitor the normal status word of the current digital signal. The current input is at its normal state when a logic exclusive-or (XOR) between itself and the status word is equal to 0.
• When disabled, this connection point is not available.

For each bit of a digital channel, a name must be configured. This name needs to match the name of the bit configured in the PMU.