Valentina Gaggero
Valentina Gaggero
Thanks @AntonioConsilvio! We noticed the problem on the ergoCub2.0 joints, but in this case, the cause was a different number of motor poles that affected the index search algorithm. In...
> One thing we noticed is that if there is something wrong with one of the two wrists, then the entire calibration of the arm is delayed. This can cause...
[Here](https://icub-tech-iit.github.io/documentation/temperature_sensors/software/dataflow/#error-handling) the documentation that explains the raw values used as error code.
Hi @AntonioConsilvio, me and @andresoll we are aligned on this issue. Please contact us when you start working on it. cc @Fabrizio69
Hi @SimoneMic, did the error occur after or during the calibration? Thanks
Hi @S-Dafarra , we don't forget this issue, but we are involved in various activities related to ergocub s/n 001 and we are releasing a new FOC fw that will...
I saw the log today, I think that @MSECode was right, but, in any case, we need to investigate why the diagnostic says: `Time since last contact: 0 [ms]`.
I opened this issue for investigate further. https://github.com/robotology/icub-main/issues/937
Hi @sgiraz, in https://github.com/robotology/icub-main/issues/937, we fixed the diagnostic messages. We didn't take care of the problem on the robot. Now with the new release the diagnostic provides correct information when...
Remember to dump the data on a laptop! 😉