...
Each slave has multiple parameters:
| ID | This parameter is a unique identifier needed for each slave. The C37.118 master must use this identifier to connect with a given slave interface. |
| Protocol | Select TCP, UDP or TCP and UDP depending on the desired behavior. |
When using TCP or TCP and UDP protocols, the combination of the IP address and TCP port has to be unique for each slave.
...
Both ports must be different from one another.
| TCP port | Specifies the TCP port used by the C37.118 master to establish a connection with the C37.118 slave. |
| UDP port | Specifies the UDP port used by the C37.118 master to establish a connection with the C37.118 slave. |
| NIC name | The desired network interface name. The proper interface name should be selected based on the information given by the Linux command ifconfig. |
| IP address | The IP aliasing functionality can be used to give each slave a different IP address even though the same network interface will be used. |
Each slave will have its own IP alias (i.e. eth0:0, eth0:1 ...) and they should appear in the list displayed by the Linux command ifconfig.
Note: If the C37.118 master driver is used to connect to the slave running on the same target, the localhost address (127.0.0.1) must be used as well as the loopback network interface lo.
| Frequency | This parameter is the nominal frequency and can be either 50 or 60 Hz |
| Data rate | The data rate value (frames per sec.) depends on the frequency set above. |
...
| Custom |
...
| data rate |
...
| Custom data rate | (Available only if data rate is set to custom) Specifies the custom data in frames per second from 1 to 512 included | |
| Phasors representation | Can be either POLAR or RECTANGULAR | |
| Phasors format | Can be either INT16* or FLOAT | |
| Analogs format | Can be either INT16 or FLOAT | |
| Frequency format | Can be either INT16** or FLOAT | |
| Header | Additional text information if required. This information will be returned to the C37.118 master after a 'Header frame' request command. | |
| Round packet timestamp | By activating this option, the fraction of seconds written into the packet is rounded to simulate a timestamp perfectly aligned on the UTC time. If an external synchronization source is used, the time quality indication code is set to 0 (normal operation) However, if there is no external clock, the code is set to F (fault, clock failure, time not reliable) which is the standard behavior when the external clock is absent. |
*Following the standard, a scaling factor will be automatically applied. See Phasor Configuration > Phasor unit for more information.
**Following the standard, a scaling factor will be automatically applied. See Slave Connectable Points > Frequency Rate Of Change for more information.
Phasor Configuration
Each slave contains a list of phasors to be configured depending on the desired name, type, and unit.
Each phasor has three parameters:
| Phasor name | This parameter helps the user to connect signals to the model through auto-naming, meaning it has to be unique for each signal. |
| Phasor type | Select the type of each phasor between CURRENT and VOLTAGE. |
| Phasor unit | Specifies the unit of each phasor measurement. If the data format is INT16, each unit has a conversion factor of 10^-5 Volts or Amperes on the phasor magnitude. |
For example, if the signal connected to the phasor input has a magnitude of 11 000 and the specified unit for this phasor is 100, the value will be interpreted as (11 000 * 100 * 10^-5) = 11 by the C37.118 master.
...
Each analog has three parameters:
| Analog name | This parameter helps the user to connect signals to the model through auto-naming, meaning it has to be unique for each signal. |
| Analog type | Select the type of each analog between SINGLE POINT, PEAK, and RMS. |
| Analog unit | Specifies the unit of each analog measurement. It is a user-defined scaling that must be part of the reported data frame in order for the C37.118 master to interpret it. |
Digital configuration
Each slave contains a list of digitals that are to be configured depending on the desired name and unit.
Each digital has two parameters:
| Digital name | This parameter helps the user to connect signals to the model through auto-naming, meaning it has to be unique for each signal. |
| Digital unit | Specifies the mask of each digital. Two 16-bit words are provided for each digital word. |
- The first word is used to indicate the normal status of the digital input by returning a 0 on a logic (XOR) with the corresponding digital input (also referred to as status word).
- The second word indicates the current valid inputs to the PMU by setting the bit in the binary position corresponding to the digital input to 1 and all other bits to 0.
- If the digital status words are used for something different than a Boolean status indication, the use of masks is left to the user, such as min or max settings.
...
Once the driver has been configured as desired, the user will have to connect points in the model to points in the driver by using the designated RT-LAB GUI. This connection panel will show all the driver's and model's connectable points, once the model has been compiled. It is also possible to make connections to LabVIEW Dashboards panels.
The driver's connectable points depend on the number of slaves and on the number of phasors, analogs, and digitals of each slave. Saving the configuration will automatically update the list of connections available.
The following lists the driver connectable points for the monitoring queues, a slave, a phasor, an analog, a digital and the external clock signals.
Monitoring Queues Connectable Points
| Connectable Name | Description | Direction |
|---|---|---|
| Main Queue | Utilization rate (%) of the main processing queue of the driver | To model |
| PMU Queues | Utilization rate (%) of the processing queue of each slave | To model |
Slave Connectable Points
...
| Connectable Name | Description | Direction |
|---|---|---|
| Frequency ROC | Frequency Rate Of Change value (in hertz per second Hz/s)
| From model |
| Frequency deviation | Frequency deviation value (in millihertz mHz)
| From model |
Phasor Connectable Points
If the phasor representation is POLAR, the phasor connectable points are:
| Connectable Name | Description | Direction |
|---|---|---|
| Magnitude | Magnitude value | From model |
| Angle | Angle value in |
| radians* | From model |
*Note regarding the angle: if the phasor format is INT16, the driver will automatically apply a scaling factor of 104. For example, if the signal connected to the phasor input has a an angle of 3.1222 radians and the phasor format is INT16, the value sent will be (3.1222 * 104) = 31222. Most third party tools (such as PMU Connection Tester and Wireshark) automatically apply the inverse factor and convert to degrees.
This scaling feature is defined by the standard. If the data format is FLOAT, this scaling does not apply.
If the phasor representation is RECTANGULAR, the phasor connectable points are:
| Connectable Name | Description | Direction |
|---|---|---|
| Real part | Real part value | From model |
| Imaginary part | Imaginary part value | From model |
Analog and Digital Connectable Points
...
If the general parameter Use external clock is set to true and Auto-connect to external synchronization if present is set to false, additional connectable points appear:
| Connectable Name | Description | Direction |
|---|---|---|
| Synchronized | Boolean indicating the external clock is properly synchronized | From model |
| Epoch | External clock epoch time value | From model |
| Nanoseconds | External clock nanoseconds value | From model |
The example model provided with RT-LAB is already packaged with connections between the driver and the model. It can be used to understand how the connections between the model and the driver should be done.
...
- A configuration containing 100 slaves streaming 16 phasors each at a data rate of 60 frames per second has been tested and validated
- Other functional configurations can be created by modifying the number of slaves, phasors, the data rate, etc...
- Custom data rate value must be between 1 and 512 frames per second
- Statistic word is not supported and will be 0 within all reported packets
- Time quality leap second information is not implemented and will be 0 within all reported packets
- Configuration reported by the C37.118 slave following a CFG-1 or CFG-2 command is the same
- Configuration frame #3 is not supported
- Fraction of second (FRACSEC) value of the data frames is reported in microseconds
- External synchronization has been fully tested using Spectracom TSync-PCIe and Oregano syn1588 PCIe NIC cards.
- On 32bit OPALRTOPAL-Linux RTLinux (x86-based) platforms (such as RedHat 5.2), a maximum of 2000 PMUs can be handled by one I/O interface instance. If more are required, it is recommended to use an extra interface instance for every 2000 PMUs needed. This limitation is not present on OPALRTOPAL-Linux RTLinux (x64-based) platforms.