For all Libre Solar devices we are currently using ThingSet for monitoring and control as well as triggering firmware upgrades. This will also be the primary method for the BMS.
The predefined battery resource from OCF only exposes very high-level information about a battery. With ThingSet we are more flexible and can expose the data in any detail we want.
However, if the AirLink development you are working on will be available as a Zephyr module, it should be fairly easy to integrate it into the BMS aswell and we could leverage it. I’ve seen that Angaza developed some example Zephyr code for nexus already: https://github.com/angaza/nexus-embedded/tree/master/nexus/examples
What are your plans regarding implementation of the device side for AirLink? Are you using Zephyr or Nordic Connect SDK as a basis?
Hi Martin, We’re using Nordic’s SDK internally but intend Airlink to be agnostic to our current implementation which is just the first prototype (we’d also like to look at non-Nordic for cost purposes).
Ah, ok, so that’s the “old” SDK from Nordic, I guess. The new Nordic Connect SDK is Zephyr-based, so it would be very easy to switch to other MCUs like ESP32.
In general it sounds good to make Airlink agnostic to the underlying SDK / RTOS.
Hi everyone. We have started working on this project. You can find a dedicated thread to collect requirements and feedback here: Libre Solar BMS Development
