Setting RRS-II Controller-Specific Attributes/Profiles

Using this approach, you can create instances of RRS-II Controller-Specific Profiles. These profiles can be selected from the predefined RRS-II Profiles list (hint: use "Filter profile type: RRS-II") or can be defined manually via custom User Profiles based on the same RRS-II attribute definitions. RRS-II 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:

• An instance of any RRS-II Controller-Specific Profile used in any part of a Robot Task must first be set on the very first robot motion operation so as to effectively initialize the underlying set of RRS-II attributes at the start of the robot program. Instances of the same RRS-II Controller-Specific Profile can then be set on any subsequent robot motion operation as the values of the underlying RRS-II attributes needs to be changed. Note that, unless explicitly stated to work otherwise, the last RRS-II attribute value setting will continue to be used in subsequent robot motion operations during an RRS-II-based simulation unless the attribute's value is explicitly changed in that robot motion operation.
• If custom User Profiles are created, the RRS-II attributes added into them must adhere to the following rules:
  • The attribute names and types must exactly match the RRS-II attribute specifications shown in Customizing the RRS-II RTM Interface and Customizing the RRS-II VTM Interface.
  • 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 Customizing the RRS-II RTM Interface and Customizing the RRS-II VTM Interface.