bms-tools VS missing-semester

The code in question: bms-tools.

In my learning journey I have come to realize that BMSes do exist and my silly setup is both redundant and not very good at keeping the battery safe. I found a smart BMS by a company called JBD that has several 3rd party libraries written for it, including the one I'm using by a fellow redditor here called /u/MrSurly. Here's a link to his BMS library. The BMS library allows me to communicate with the BMS using the RPi, I get information such as the voltage of each cell, current output, and more information. It also automatically stops the discharging when the battery is about to die.

You can use the BMS Tools Python library, but I'm biased, as I wrote this.

So, I went down a rabbit hole of creating an open-source app for the somewhat popular JBD / XiaoXiang BMS. I was messing about with the features provided by the somewhat clunky official Windows app, and tried to do a firmware update on the BMS, and promptly bricked it.

Thank you! Yeah, I've tried a variety of edits to the function call, it's from the backend of a very professionally done python package with the reverse-engineered protocol for this pretty ubiquitous type of BMS; It is very cleanly written but also broken out into a ton of little stepwise functions many of which I don't understand... Enum types, lots of decorators (@staticmethod, @serial.setter, @property) and dunder enter/exit's... but I get the gist of it, every time I ask it it to read data it opens the port, constructs the bytes for the read command, sends them over the port, then collects the response byte-by-byte, verifies the final checksum byte, if ok then converts the payload to a dict otherwise raises an exception, and finally returns the data dict.

The serial protocol is now available here: https://gitlab.com/bms-tools/bms-tools/-/blob/master/JBD_REGISTER_MAP.md

Hey, here's the v1.1.0 release page -- should fix that issue.

The missing semester of your cs education

https://missing.csail.mit.edu/

You mentioned having issues with accessory concepts so perhaps this might help: https://missing.csail.mit.edu/. There's also a chapter on git

https://missing.csail.mit.edu/ is a good way to pass the Dec-Jan break if you want to prep for CS2030S + some more general stuff.

Reflecting a little bit more I don't think it was replit's fault, per-say. But that change should have been made together with a larger adjustment to the program. Like adding a class/unit in the style of [the missing semester](https://missing.csail.mit.edu/) to make sure people came away with a good range of intuitions.

From MJD's post: I think CS curricula should have a class that focuses specifically on these issues, on the matter of how do you actually write software?

But they never do.

FWIW, MIT's "The Missing Semester of Your CS Education" attempts to deal with this lack, though, even there, it's an unofficial course taught between terms, during MIT's IAP -- Independent Activities Period[1] -- and not an actual CS course.

[0] https://missing.csail.mit.edu/

[1] https://en.wikipedia.org/wiki/Traditions_and_student_activit...

Link to the "missing semester of your CS degree" course by MIT.

Rightly called The Missing Semester (of Your CS Education), this class from MIT will teach you how to use some of the tools that are fundamental to the software engineering ecosystem. From shell scripting to the fundamentals of information security—spanning around 12 lectures—you can add a bunch of practical skills to your toolbox.