Page Content
Your system was fully tested at the factory. However, you can execute the tests to check if all is functioning as expected and get familiar with RT-LAB and your system. This step is optional.
Execute a Simple Functional Test and Demo
For a simple functional test of your system, you can execute one of the model examples provided as demos.
For example, you can load and execute the “rtdemo1” demo model, which is a PID controller. This model does not use the I/Os of your system.
If this model is running as expected, you know that your system basic configuration is correct.
The procedure is explained in this page of the RT-LAB user documentation: https://opal-rt.atlassian.net/wiki/x/MoiPC
Execute the Integration Test Model (Loopback Test)
We provide you a project file containing the integration test model used to test your system in the factory.
Please refer to this page in the RT-LAB user documentation for details: https://opal-rt.atlassian.net/wiki/x/_QiPC
The project includes the bitstream you need to use in your models.
Note that in the OPAL-RT user documentation, the words “bitstream” and “firmware” are used as synonyms.
Download, on your PC, the project file below, that includes the integration test model file.
What Is the Integration Test Model (Loopback Test)
The integration test model is a loopback model that outputs digital or analog signals from the simulator DB37 I/Os connectors to the digital or analog input DB37 I/Os connectors.
Signal readouts are viewed through the scopes of the MATLAB Simulink console of the model.
To validate the model, each output connector (digital or analog) should be physically connected to the corresponding input connector to read the signals received.
They can be connected all at once, or one at the time.
Connect the I/O Cables
Use the loopback flat ribbon cable IDC40 to DB37M and the loopback board DB37, 40 positions with Vuser. See this page.
Before connecting the cables, make sure that the voltages or other electrical specifications are compatible with OPAL-RT DB37/DB9 specifications of I/O modules OP5330, OP5342 and, OP5369. See section OP4512 I/O System for all DB37 and DB9 pin assignment.
Refer to these pages for more details
Your bundle I/O connectors are described here: HIL2GO-100 - OP4512 I/O System
Connecting the I/O loopback kit is explained here: https://opal-rt.atlassian.net/wiki/spaces/PHDGD/pages/144662112/OP5707XG+Installation+and+Configuration#Connecting-the-I%2FO-Loopback-Kit
Also read this knowledge base article: How to power the different DB37 boards for digital outputs
Use the Integration Test Model (Loopback Test)
Once the model downloaded, follow these instructions to use the model.
The main steps are described below. See this RT-LAB user documentation for details.
Also, don’t forget to view our video tutorials RT-LAB - Real-Time Simulation Systems Fundamentals and register for your FREE online self-pace e-learning courses.
Use the current workspace or use an existing workspace or create a new workspace in RT-LAB.
Import the integration project with the integration test model in RT-LAB:
Click File > Import
Select General > Existing Projects into Workspace
Choose Select archive file, then click the Browse button
Select the downloaded zip file and click Open, then click Finish
Build the integration test model:
In the “HIL2GO_100_integration_test” tree, click Models.
Right click on IO_test and select Simulation > Build configurations…
Select your target (simulator) in the drop-down list “Development Node: on OPAL-RT (x64-based)”
Click OK.
The model start building up. When done, the build log can be viewed under the Compilation tab in the bottom right panel.
Load the model.
Execute the model.
Use the MATLAB Simulink console to view signals and check if all the inputted signals corresponds to the outputted signals. See the sections below.
Din and Dout Loopback Test
Connect the loopback board to a Dout DB37 connector and connect the cable to a Din DB37
It is not mandatory to connect Vuser to a power source, but the Vuser Source switch must be set to “INT. 12V”
Observe the Dout feedback on the Din using the integration model
See the examples below.
Ain and Aout Loopback Test
Connect the loopback board to an Aout DB37 connector and connect the cable to an Ain DB37
Observe the Aout feedback on the Ain using the integration model.
See the example below
Execute the eHS Test Model
We provide you below a project file containing a test model using eHS FPGA-based power electronics toolbox.
Download it on your PC.
To run the model and test the eHS functionalities, the steps are the same as the ones explained in the Execute the Integration Test Model (Loopback Test) section above.
Please refer to this section for detailed instructions.
What Is the eHS Test Model (eHS Loopback Test)
The eHS test model is a loopback model that outputs analog signals from the simulator DB37 I/Os connectors to analog inputs of DB37 I/Os connectors, and passing thought an eHS block in between.
Signal readouts are viewed through the scopes of the MATLAB Simulink console of the model.
If the outputted signals can be read in the console, it means that the signals were transmitted successfully through the eHS block.
The content of the eHS test block can be viewed in the project eHS test model. Expand the section below to view some screen captures.
Connect the I/O Cables
To validate the eHS test model, the analog output connector should be physically connected to the corresponding input connector to read the signals received.
For this bundle, analog outputs are on connector P1 of Group 2 - Section B (2B-P1) and analog inputs are on connector P1 of Group 2 - Section A (2A-P1).
Use the eHS Test Model
Import the eHS bitstream configuration file in Schematic Editor by following the instructions is the next section.
Connect the analog outputs to the analog inputs using the I/O cables as described in this section:
Import the project with the eHS test model in RT-LAB
Build the test model
Load the test model in the simulator
Execute the model
Observe the Aout feedback on the Ain using the eHS test model. Expand the section below to see how.
If the signals can be read in the console, it means that the signals were transmitted successfully thought the eHS block and that eHS is functioning and configured correctly.
NEXT STEP > it’s up to you. You may want to: