113 réponses à ce sujet
#65
Mike118
-
- Administrateur
-
- 12 873 messages
Staff Robot Maker
- Gender:Male
- Location:Anglet
- Interests:Robotique, Entrepreneuriat, Innovation, Programmation, Résolution de problème, Recherche de solutions, Mécanique, Electronique, Créer, Concevoir
Posté 01 février 2026 - 14:09
I need to have the new minus kits ready to be ordered by then ! 
Si mon commentaire vous a plus laissez nous un avis ! 
Nouveau sur Robot Maker ?
Jetez un oeil aux blogs, aux tutoriels, aux ouvrages, au robotscope aux articles, à la boutique et aux différents services disponible !
En attendant qu'une bibliothèque de fichiers 3D soit mise en place n'hésitez pas à demander si vous avez besoin du fichier 3D d'un des produits de la boutique... On l'a peut être !
Si vous souhaitez un robot pilotable par internet n'hésitez pas à visiter www.vigibot.com et à lire le sous forum dédié à vigibot!
#73
derpflanzer
-
- Membres
- 1 messages
Nouveau membre
Posté 26 février 2026 - 08:36
On the Botkins Github Parts List, there's a workaround described if you try the Waveshare UPS hat (D). In the workaround, there's a change to /usr/local/vigibot/clientrobotpi.js mentioned, and the caveat that this might break future automatic upgrades. As I have zero experience with Botkins and Vigibot, it's unclear to me what the impact of this is. How often do these upgrades happen, and how critical is it to apply them? Can you help me understand what the impact is?
I'm referring to "*Hinweise zu Alternativen:" on this page: https://github.com/e...file#teileliste
I'm referring to "*Hinweise zu Alternativen:" on this page: https://github.com/e...file#teileliste
#74
firened
-
- Membres
-
- 2 124 messages
Pilier du forum
- Gender:Male
Posté 26 février 2026 - 08:41
We must've been writing at the same time ^^
I'll copy my answer here for completion's sake:
Yeah good question.
If i had to guess:
- only few small updates in the last 3 years.
- about 5 years ago, there were many regular updates happening, including a required one, which broke non-updated clients.
Many UPS, like the geekworm UPS HAT3, that we used a lot, do not have any current sensing at all.
None of my 9 robots have it.
In my opinion, the voltage is the more important measure, which will give an approximate battery charge level.
(On that note, we could consider writing the inaccurate battery % instead of the voltage, as voltage is probably difficult to understand for patients.)
For voltage only, no change to the clientrobotpi.js code is necessary. So that would be my recommendation.
I'll copy my answer here for completion's sake:
Yeah good question.
If i had to guess:
- only few small updates in the last 3 years.
- about 5 years ago, there were many regular updates happening, including a required one, which broke non-updated clients.
Many UPS, like the geekworm UPS HAT3, that we used a lot, do not have any current sensing at all.
None of my 9 robots have it.
In my opinion, the voltage is the more important measure, which will give an approximate battery charge level.
(On that note, we could consider writing the inaccurate battery % instead of the voltage, as voltage is probably difficult to understand for patients.)
For voltage only, no change to the clientrobotpi.js code is necessary. So that would be my recommendation.
Répondre à ce sujet
0 utilisateur(s) li(sen)t ce sujet
0 members, 0 guests, 0 anonymous users
