Moving Robots via CRI
While many use cases can be solved solely by a robot program some require the robot to move to coordinates from external sources. For these cases CPRog/iRC and TinyCtrl offer the following interfaces:
- Camera interface (2D coordinate, orientation and object type)
- Jog via CRI (velocity values)
- Program variables via CRI (position or scalar number), we generally recommend this approach!
This article gives an overview on how to use these interfaces to command the robot to move to specific positions.
Camera interface
The camera interface uses a simple text-based TCP/IP protocol that is based on the IFM O2D camera. It transmits 2D coordinates (integer), an orientation value (float) and a object class value (integer). If you do not want to use the CRI protocol this can be used to transmit coordinates or arbitrary values, however some extra calculations might be necessary to shift the integer values to decimal accuracy, if needed. This article describes how to use the camera interface: Remote Variable Access#Camera interface
If you want to integrate an O2D camera follow this guide: 2D Camera Integration
Jog via CRI
The CRI Ethernet Interface includes the ALIVEJOG command, which can be used to move the robot by specifying velocity values per joint or cartesian axis. The velocity values are in percent. This approach could be used for joystick-like motion.
Positioning commands via CRI
Currently no CRI commands for moving the robot to specific positions are available. Instead we suggest the program variable approach as described in the following section.
Program variables via CRI
The recommended approach is to use the CRI Ethernet Interface to transmit position or scalar variables that can be read and changed in robot programs. This article describes the CRI commands in question: Remote Variable Access#CRI Ethernet Interface
