-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ergoCub 1.3 S/N:002 β Issue on right ankle pitch temperature sensor #1986
Comments
Hi @S-Dafarra , |
We just updated to |
Then, do u have logged some data for the temperature. So we can check how data have been read and how they changed before the errors, to see if we are still reading badly. |
No, it was immediately after startup |
Ok, I would first check the cable, if it might be broken or detached. If that not the case I'll dig on the problem. |
For the time being, I will disable the sensor |
Hi @MSECode , |
If I recall correctly, on ergocub we only have motors with PT100 temperature sensors. Thus, the data shown on the logs are respectively the following temperatures in Celsius:
I would think that they are false positives. I'm just worried about 2 thing:
However, if the robot is still working fine and you started to read those values at a startup of the system, which was previously idle it cannot be a real problem of overtemperature. If, instead, the robot seemed to have problem during the calibration phase, that might be reasonable value but you should not be able to use the motor at its total power now (if it started to burn on the stator you should at least see worse performances on the joint ). Thus, in the case those are false positive, we need to check the cabling --> I would say that the most likely option is that we have the i2c extender or the tdb itself not well connected and so we see disturbed data.
For the latter two cases for sure we have encoder errors in the yri diagnostic, which can help in checking if we had issues on the encoders. |
Oh shoot, maybe they were not fake at all, see #1987. When I saw the values I thought they were already in Celsius. I thought they were fake cause it was happening right at startup and the joint was calibrating well. I wonder if instead, it was an issue of the board that is in short circuit. |
For sure I'll update the diagnostic message to give you both values (raw and converted) for clearance. |
In that case I would expected more errors (the negative values you can see here: https://icub-tech-iit.github.io/documentation/temperature_sensors/software/dataflow/#error-handling). However, if a resistor is damaged the output can be have an offset since you have not a balanced voltage divider anymore. But it is important that the resistor is just damaged. In the case of an open circuit you'll get an error. |
Hi @S-Dafarra , So, in other words, did you get it before the issue on #1987 or after? This is to understand the chronology. |
I am not sure either, but in any case I suppose that there is some issue on the right ankle 2foc. |
In the end, the motor was indeed burning. So I guess that the temperature sensor was working fine, and I got misled by the fact it was happening with the robot just turned on and by the raw value I assumed was in Celsius |
Hi! As can be seen in this comment, the motor was burnt out: So, closing this issue due this comment π: |
Robot Name π€
ergoCub 1.3 S/N:002
Request/Failure description
The joint goes in hardware fault because of clearly bogus readings
Detailed context
Here the error messages:
Additional context
This joint is using a i2c extender.
cc @maggia80 @valegagge @MSECode
How does it affect you?
No response
The text was updated successfully, but these errors were encountered: