The automation is for the attributes for the RIMB that match the format <p>_<x> (where p is the port name, and x is the attribute for the port interface). The automation is done during code generation and used by the code generation.
How the automation works
For each attribute on the RIMB, an active operation is automatically added. The active operation can have either a periodic or data_received_event activation policy. This policy is controlled by the CG::Attribute::PeriodicRead property. The period for a periodic active operation policy is defined by the CG::Attribute::ReadInterval property. The active operation has access to the referenced port and attribute (matching the attribute <p>_<x> name). You can define the data reception processing policy for an attribute by setting the CG::Attribute::DataReceptionProcessingPolicy property. By default, this property is set to ByModel, which means the attribute is handled according to the model. If there is a trigger operation associated with the attribute, processing happens immediately. If there is a reception associated with the attribute, it is added to a queue.
The following figure shows generated code with automatically generated active operations.
