-
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.0 S/N:000 β The robot sometimes completely blacks out when in battery mode #1688
Comments
Hello! Something really similar happened to The differences that were present, albeit really similiar, with the original post were:
@AntonioAzocar @AntonioConsilvio were present, maybe thay can add some details that I've missed |
It happened again today. It seems like the BAT rebooted for some reason. May it be a FW issue on the BAT side? @maggia80 @valegagge @MSECode |
oks, |
Only battery.
I am afraid not π’
For this, I am tagging @carloscp3009 and @GiulioRomualdi, but I am not sure we were logging the data. I think the battery device was active though since we the YRI throws errors about it (something like that it detected that some boards are not streaming).
The reason why I am thinking about this is because it is happening on three different robots in very similar conditions, while it never happened on iCub3 (at least before it got π mounted on it). The probability that three battery packs are faulted in the same way seems low, and iCub3 had the same BMS. The only difference is the BAT, which is common between ergoCubs. |
Oks, the errors related to the fact that the boards are not streaming happens when a device is enabled in the xml configuration files but it's not streaming anything on CAN. It's generated by the 'can monitor', which is pinging the CAN boards every 1s.
Yeh, that's reasonable. I'll dig into that to see if there's something wrong in the fw. |
Makes sense! Just to be sure, which data are you interested in? |
I checked with them and we inadvertently deleted all the logs because we ran out of HD. We did not think of keeping that one. |
Remember to dump the data on a laptop! π |
We need the output of the battery devices (both for BAT and BMS), but @MSECode can add more details and ideas. |
Exactly, |
Unfortunately, it was the laptop to be full. We were focused on an experiment and we were logging a lot of data, and to continue with the experiment we decided to delete the past logs.
Yeah, I think that at the moment that data is not logged |
Hi all, soon we are going to have a demo on a stage without any cable. Do you think there is something that is possible to do in order to reduce the likelihood of this happening? Can this be related to robotology/icub-firmware#421 since it started happening afterward? |
Hi @S-Dafarra, today we gonna check if those changes caused the issue. In the meantime, did you dump some data? cc @MSECode |
I could not since I was busy all week in Washington for a demo. Moreover, to the best of my knowledge, it did not appear again lately. |
Hi @S-Dafarra, I checked out the code but it seems all fine to me. The changes done in that PR should be fine. I do not notice anything strange. Anyways, is the latest version of the BAT, i.e. 1.3.4 flashed on all the robot you are using? And I'll keep this issue monitored eventually. |
Today it happened again (on the SN000). We operated the robot in battery for a while, then we plugged back the power supply and the battery charger. After about 20 minutes, we switched off the battery charger, we switched off the power supply, and about 10 seconds later, the robot completely blacked out. The display was off and I had to power cycle also the BMS. I was reading the output of the BMS, here the last lines (FYI the period is 1s, see https://github.com/icub-tech-iit/robots-configuration/blob/0f5e570b4aaeb283d588fdb0cbb5c5b231714ccf/ergoCubSN000/wrappers/battery/battery_bms.xml#L4)
|
It does not seem to be an overheating issue, since the temperature was 34 deg. |
During Humanoids, it seemed to happen also with the 001, when the battery was at 30%. The ambient temperature was also very cold. |
Robot Name π€
ergoCub 1.0 S/N:000
Request/Failure description
It happened that during two demos, the robot suddenly shuts down completely when in battery power.
Detailed context
This happened twice in similar conditions. The robot starts in the following state:
Then, we remove the battery charger and the power supply. After 30s or so, the robot falls down and the robot is completely off, as well as the display.
It is then necessary to power cycle the battery to have the robot functional again, and the battery is still charged.
Additional context
An educated guess is that the battery BMS goes into protection. We suspect that there is an overheating issue. Indeed, the second time the robot was quite hot, but the first time we were with the robot "outside" and the weather was quite fresh.
How does it affect you?
No response
The text was updated successfully, but these errors were encountered: