...
For each new usable module instance, the new OpInputs and OpOutputs must be configured and connected.
Connections
Once the driver has been configured as desired and associated with the proper model subsystem, the user will have needs to connect points in the model to points in the driver by using the designated RT-LAB GUI. This connection panel the Dashboards interface. The Dashboards interface will show all the driver's and model's connectable pointsconnectable points (from both, the driver and the model), once the model has been compiled. It is also possible to make connections to Dashboards panels. Refer to the Dashboards documentation for more details
The example model provided with RT-LAB is already packaged with connections between the driver and the model. It can be used as an example to understand how the connections between the model and the driver should be done.
The connection points depend on the number of usable modules, channel diagnosis enabled and IO status (IOCS/IOPS) enabled.
Under each category, the configured operations will show up with the names that have been given by the user in the driver configuration GUI. If the icon is blue, it is a IO device output that can be written by a IO controller and this signal is returned to the simulation at the beginning of each time step. It means that this signal needs to be connected to an OpInput block of the Simulink model.
If the icon is red, it is a model output. It means that this signal needs to be connected to an OpOutput block of the Simulink model. With 'IO status (IOCS/IOPS)' enabled, additional connection points are available and can be used in the model to indicate if both IO device and controller are well connected and exchanging data.
With 'Channel Diagnosis' enabled, additional connection points are available and can be used in the model to send diagnosis data on a specific submodule to the IO controller.
...