I didn’t understand a word of that beyond “You might want to”, and it is quite ok because the power system seems robust enough to proceed with software configuration, unit testing, and learning ROS.
I’m considering keeping 10.0v as my “Warning - Battery Low” but raising the safety shutdown to 9.75v providing roughly 20-25 minutes of warning before the safety shutdown monitor pulls the plug on my playtime (which will announce “System Shutdown Scheduled In 2 Minutes” ).
With that level, I can safely issue a “sudo shutdown -c” and know that I can push everything up to git and then re-issue the shutdown.
**BUT as I discovered there is only 2 minutes between 9.15v and sudden death, so I’m going to see how many cycles I get with a 9.75v shutdown. Hopefully 700 cycles of 5 hours initially ending with 2.5 hours should last me more than a year, and would end up being $0.008/hour ($35/4375h).
Carl’s batteries cost out around $0.003/hour, but hey, it’ll be a ROSbot.
What I am trying to say is that as power requirements rise, wiring and connector losses become more significant, and as current draw increases, this turns into possibly significantly reduced playtime and undesirable connection heating.
In my entire power-electronics lifetime, I have personally seen only one battery fire/explosion1 compared to dozens if not hundreds of fires/damage instances caused by poor contact and underrated wiring.
That case was caused by my trying to solder leads to a 3v button cell while talking to my kid brother and being distracted by his little Yorkie who loves pets. It overheated and exploded.
There were certain desirable results:
My brother’s dog now knows better than to jump on my lap if I have a soldering iron out.
My brother now respects that “I need to concentrate” means that bothering me can cause undesirable things to happen.
Aside from scaring the poop out of both of them, nothing really serious happened.
I am sure I will revisit the “total playtime measurement” and “15 minute warning orange LED” once ROSbot gains the ability to start the LIDAR spinning and is wandering around in the resultant map. (Estimate 3-6 months to learn ROS and teach ROSbot to use it.)
Good to know “no dogs were hurt in this portrayal of real life”
There is a reason HP took away my screwdrivers when they switched my job description from mechanical engineer to software engineer forty-five years ago. My robots run on “Velcro”.
I remember seeing a picture of Pablo Picasso’s hands (in Life magazine?) many years ago and they were all wrinkled and mottled.
A picture of my hands looks more like the way the bottom of your feet feel after square-dancing on Lego bricks.
In my case, I’ve never been afraid to try things. Though one of the things in the top right-hand drawer of my workspace desk is ointment and Band-Aids.
I also keep a supply of 3-M “Command” velcro fasteners.
Tip:
Stores like Home Depot sell rolls of double-sided velcro plant-tie ribbon, (hooks on one side, loops on the other), that’s dirt cheap.
If you don’t mind the green color and the relatively narrow width, it’s excellent for strapping things together. (I’ve been using it to organize network cables for decades.)
You get several feet of it for a few dollars, as opposed to the “official” Velcro cable ties at Micro Center for dollars each.
Also! Avery “return address labels” are great when wrapped around a cable as a way to tag it.
Thanks. This is an area where I’m not nearly as concerned about the details as either of you. I’ll mess with it just enough to get by with what I need. I’m certainly leaving performance on the table by not exploring the boundaries of the hardware envelope, but there’s only so much time in the day. Besides - I can just ready your and @cyclicalobsessive 's posts to learn about that stuff
/K