Skip to content
Snippets Groups Projects
Commit 616da3ea authored by Mirko Wächter's avatar Mirko Wächter
Browse files

doc fix

parent 45f673e2
No related branches found
No related tags found
No related merge requests found
......@@ -60,11 +60,11 @@ You can create a local clone really easy like this:
#include <RobotAPI/libraries/core/remoterobot/RemoteRobot.h>
#include <RobotAPI/interface/core/RobotState.h>
VirtualRobot::RobotPtr localRobot(RemoteRobot::createLocalClone(robotStateComponentPrx));
VirtualRobot::RobotPtr localRobot(RemoteRobot::createLocalClone(robotStateComponentPrx, robotStateComponentPrx->getRobotFilename(), robotStateComponentPrx->getArmarXPackages()));
\endcode
Now, you have a local robot clone with the robot state from the timestamp where the clone method was called.
This offers only basic functionality of the RobotPtr like joint names, joint values, robot nodes, robot node sets, robot node poses and transformations.
If you need all functionality, pass the filepath to the clone method (this path can be retrieved from the RobotStateComponent if both processes are on the same filesystem or have the same filesystem structure).
If you pass in an empty filename (or omit) to the clone method only limited functionality is available (only coordinate transformations).
This clone call should be done once, since it can take a moment.
In each cycle of a control loop, the local robot should just be synced to retrieve the current joint values:
\code
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment