Using this approach, you can create instances of RRS
Controller-Specific Profiles. These profiles can be selected from the
predefined RRS Profiles list (hint: use "Filter profile type: RRS) or can be defined manually via custom User
Profiles based on the same RRS attribute definitions. RRS
Controller-Specific Profile instances thus created can then be
associated with Robot Motion activities in a Robot Task using the
Teach command. See
Managing Applicative Profiles for further details.
Note that:
- RRS controller-specific profile instances may be set on any robot operation/activity. Note that, unless explicitly stated otherwise (i.e. as being "non-modal"), RRS attributes are by default "modal". That is, during RRS simulation the last RRS attribute value setting will continue to get used in all subsequent robot operations/activities until changed again when another RRS controller-specific profile instance containing that same attribute is set on some subsequent operation/activity.
- If custom User Profiles are created, the RRS attributes added into
them must adhere to the following rules:
- The attribute names and types must exactly match the RRS attribute
specifications shown in controller-specific customization pages
under the "Customizing" section of this manual.
- Any attribute whose name contains "\" must be added as an ordered
group of attributes into the User Profile. In other words, if an
attribute named "abc\..." needs to be added, then:
- All attributes that begin with "abc\..." must be added, and
- These attributes must be added in the same order as they appear in
the controller-specific customization pages of the "Customizing"
section.