Add direct BullTron BLE connect option
This commit is contained in:
@@ -98,6 +98,16 @@ permission issue rather than a protocol issue:
|
||||
sudo .venv/bin/python bulltron_gui.py
|
||||
```
|
||||
|
||||
The scan list shows every BLE device returned by the OS; BullTron-looking
|
||||
devices are only sorted first and marked with `*`. If the battery is not shown
|
||||
at all, close the Android BullTron app so it is not holding the GATT connection,
|
||||
increase the GUI scan duration, and try the `Direct connect` field with the
|
||||
address observed in the HCI capture:
|
||||
|
||||
```text
|
||||
7C:3E:82:1C:7A:86
|
||||
```
|
||||
|
||||
### Windows 11
|
||||
|
||||
Install Python 3.11 or newer from <https://www.python.org/downloads/windows/>
|
||||
@@ -127,6 +137,12 @@ Windows Settings and that the BullTron battery is nearby and not already held by
|
||||
the Android app. Pairing in Windows should not be required for normal telemetry;
|
||||
the original Android flow also reads telemetry without bonding.
|
||||
|
||||
If the Windows scan does not list the battery, first close the Android app and
|
||||
use the GUI's longer scan duration. If the PC can still not discover it, use the
|
||||
`Direct connect` field with the captured address `7C:3E:82:1C:7A:86`. Some
|
||||
Windows Bluetooth adapters will only connect to an address after they have seen
|
||||
at least one advertisement from that peripheral in the current session.
|
||||
|
||||
The GUI shows:
|
||||
|
||||
- live pack voltage, current, discharge watts, SOC, remaining Ah, cell max/min,
|
||||
|
||||
Reference in New Issue
Block a user