I'm reporting here issues that impact this feature but are already identified as being originated in other components (dynamic library, simulation environment/tool).
[ ] method getMotorEncoderAccelerations() from the IMotorEncoders interface returns always zero motor accelerations. Current workaround reads joint accelerations instead multiplied by the coupling matrix.
I'm reporting here issues that impact this feature but are already identified as being originated in other components (dynamic library, simulation environment/tool).
getMotorEncoderAccelerations()from theIMotorEncodersinterface returns always zero motor accelerations. Current workaround reads joint accelerations instead multiplied by the coupling matrix.