ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

I was able to reproduce this with a local, simulated NaoQI 1.12. I assume it's a bug in NaoQI 1.12 and will happen in the same way if you directly use the API. motionProxy.getAngles('Body', useSensors) will return zeros when not running directly on the robot and useSensors=True, while this used to work in NaoQI < 1.12.

I created a new parameter "~use_joint_sensors" in nao_sensors.py as workaround and reported the problem to Aldebaran. Until it's fixed, I suggest updating to the latest version of nao_driver (in SVN) and setting the parameter to False, or directly changing that line in your code.