Longtime lurker here, I have been flying both SP140 v2 and v2.5. I’ve always logged my flights using the “free & open-source forever” xcNav app and rely on its ADSB-in for the busy airspace that I fly in. Recently the developer added support for the SP140 v2.5 Bluetooth controller telemetry and I’ve been helping test on iOS (there is an Android version too). You can now see the realtime telemetry gauges for power, battery state of charge (SOC), and the differential cell-to-cell voltage. Power and SOC are logged along with flight data for those trying to understand the limits of their equipment.
Prior to this, I was using the ANT BMS app to monitor my differential cell-to-cell voltage (UnitVDiff) after my BMS cut power during flights (I have some bad cells in my v2.5 pack). I don’t have access to the OpenPPG app yet and suspect there is some overlap, but xcNav provided support for the critical telemetry I needed.
Anyway, this xcNav app has honestly improved my anxiety and awareness while flying.
xcNav 2.10.27, requires SP140 v2.5 with Bluetooth-enabled throttle with v8.0 firmware.
No, xcNav pulls the telemetry data from the v2.5 throttle controller via Bluetooth. A while ago we tried but could not directly connect to the BMS (v2.5 battery) using Bluetooth. However I see from the OpenPPG app demo that they can make a direct connection to BMS.
Either way I’ve noticed a flakey Bluetooth connection between the BMS and my phone mounted at the end of my swing arm. I used to use the ANT BMS (and ANT BMS V2) app and often couldn’t be certain if the data was refreshed or if the Bluetooth connection dropped. This made it impractical for critical data, like knowing when you were approaching UnitVDiff cutoff. Maybe the connection could improved with phone positioning to avoid your body obstructing the connection, perhaps mounted on your forearm.
