Documentation Home Page ◇ RT-LAB Home Page
Pour la documentation en FRANÇAIS, utilisez l'outil de traduction de votre navigateur Chrome, Edge ou Safari. Voir un exemple.
OpMonitoringStart
Library
rtlab/Monitoring
Block
The OpMonitoringStart block enables you to monitor certain parts of a model.
OpMonitoringStart block
Mask
OpMonitoringStart mask.
Description
The OpMonitoringStart block enables you to monitor certain parts of a model. This block must be used with a OpMonitoringStop block The following figures shows how to insert the block inside a subsystem.
Figure 3: Initial diagram
Figure 4: Gain block has been regrouped inside an atomic subsystem
Figure 5: Monitoring blocks have been added
Figure 6: Monitoring blocks have been regrouped inside an atomic subsystem
Figure 7: Inside the atomic subsystem
An atomic subsystem must be placed between the two blocks to force Simulink to compute all the blocks inside this subsystem before outputting the values. Then atomic subsystem and monitoring block must be grouped inside an atomic subsystem to ensure the order of these blocks remains unchanged (i.e. OpMonitoringStart must call before OpMonitoringStop during a computation step).
Parameters
| Event Name | This field contains the name of the event to be registered. The same event name must be used in the corresponding OpMonitoringStop block. |
|---|
Inputs
This block has no inputs.
Outputs
The outport must be connected to an atomic subsystem. The output's value could not be used inside the model, connection is only used to force order block by the Simulink scheduler.
Characteristics and Limitations
This block has no special characteristics.
Direct Feedthrough | No |
|---|---|
Discrete sample time | Yes |
XHP support | Yes |
Work offline | No |
OPAL-RT TECHNOLOGIES, Inc. | 1751, rue Richardson, bureau 1060 | Montréal, Québec Canada H3K 1G6 | opal-rt.com | +1 514-935-2323
Follow OPAL-RT: LinkedIn | Facebook | YouTube | X/Twitter