Here are the classes, structs, unions and interfaces with brief descriptions:
[detail level 123]
| ▼Nflexiv | |
| ▼Nrdk | |
| CRobotEvent | Information about a robot event |
| CRobotInfo | General information about the connected robot |
| CRobotStates | Robot states data in joint and Cartesian space |
| CPlanInfo | Information of the on-going primitive/plan |
| CJPos | Data structure representing the customized data type "JPOS" in Flexiv Elements |
| CCoord | Data structure representing the customized data type "COORD" in Flexiv Elements |
| CDevice | Interface to control the peripheral device(s) connected to the robot |
| CFileIO | Interface to exchange files with the robot. Only certain types of file can be transferred |
| CGripperParams | Data structure containing the gripper parameters |
| CGripperStates | Data structure containing the gripper states |
| CGripper | Interface to control the gripper installed on the robot. Because gripper is also a type of robot device, this API uses the same underlying infrastructure as rdk::Device, but with functions tailored specifically for gripper controls |
| CMaintenance | Interface to run maintenance operations on the robot |
| CModel | Interface to obtain certain model data of the robot, including kinematics and dynamics |
| CRobot | Main interface to control the robot, containing several function categories and background services |
| CSafetyLimits | Data structure containing configurable robot safety limits |
| CSafety | Interface to manage safety settings of the robot. A password is required to authenticate this interface |
| CScheduler | Real-time scheduler that can simultaneously run multiple periodic tasks. Parameters for each task are configured independently |
| CToolParams | Data structure containing robot tool parameters |
| CTool | Interface to manage tools of the robot. All updates take effect immediately without a power cycle. However, the robot must be in IDLE mode when applying changes |
| CWorkCoord | Interface to manage work coordinates of the robot. All updates take effect immediately without a power cycle. However, the robot must be in IDLE mode when applying changes |