EXata CPS | Communication Interface with HYPERSIM

In order to exchange information properly during the simulation, certain steps need to be taken to map the EXata CPS nodes to the HYPERSIM I/Os.

1. When the HYPERSIM model is ready: configure the I/O interfaces. Select the virtual Ethernet ports and IP addresses that will be used to interface with EXata CPS.
2. For example, in this HYPERSIM model, there are two pairs of GOOSE publishers and subscribers. Pub1 and Pub2 are mapped to veth0-10.10.1.6 and veth1-10.10.1.7. Sub1 and Sub2 are mapped to veth2-10.10.1.8 and veth3-10.10.1.9.

   
   

   
   Note: A virtual interface is recognized with the keyword 'vethX' where X is an integer. The new virtual interface will have the IP address of the 'IP address of the virtual interface' field. However, if the protocol of the I/O Interface is a TCP/UDP server, the value found in the field 'IP address' will be given to the new virtual interface.
   
   
3. Add an EXata CPS Configurator I/O Interface instance and link a network interface card with EXata. This is needed for a license check.
4. For example, the next figure shows how to link eno2 to EXata.
   
   
   
   Note: To reach an external device (hardware-in-the-loop simulation) an ARP Entry must be added based on the IP and MAC address of the external device.
   
   
5. During the load of the model, these operations will be performed:
   
   
   1. An exata_opalrt_configfile.json file will be created in the project directory under the EXata folder. This file is a configuration link between EXata and the IO Interface Configuration.
   2. A script named vethscript.sh will be executed on the target. This script will create the virtual interfaces needed.
   3. The network interface linked with EXata will be migrated inside the network namespace of EXata.
      
      Refer to the HypConsole log to see the output of these operations.
      
      
6. Create the communication network model in EXata CPS.  You can load the .json file generated in step 5 in the EXata CPS GUI by navigating to Scenario Properties > General > CPS Settings.

After loading the .json file, in design mode, navigate to the Mapping widget and select File as an option in the IP Address Input Type field. The content of the .json file will be visible as a dropdown menu in the OPAL-RT Device and Interface Name fields.