mirror of
https://github.com/torlando-tech/pyxis.git
synced 2026-06-28 10:22:00 +00:00
torlando-tech
76ffd29b01
Pre-this the 10s heartbeat reported running/scanning/connected/peers state but nothing about whether data was actually flowing. With the counters added to BLEInterface and threaded into the heartbeat snprintf, the line now also surfaces: tx_pkt — outbound RNS packets attempted tx_frag — BLE fragments actually written/notified tx_b — total bytes written tx_fail — platform write/notify returned false rx_frag — BLE fragments handed to the reassembler rx_b — total bytes received That was enough to root-cause the Columba-side stalls observed during the BLE end-to-end testing session: pyxis showed connected=1 but tx_pkt frozen, surfacing that the keepalive loop wasn't firing for a peer whose handshake had completed but identity recording raced. Cumulative-since-start, no reset; cheap to keep on always.
Pyxis
An LXMF and LXST client firmware for T-Deck, built on a highly modified fork of microReticulum
Very much WIP, don't expect stability :)
Features
Reticulum transport over:
- RNode-compatible LoRa
- AutoInterface (local wifi)
- TCP Client
- BLE Interface (barely working if at all)
Other features:
- GPS-synced time
- One really annoying beep when you get a new message (user toggle)
- View the announce stream
- Choose a propagation node (and sync with it) (fixed in v0.2.1)
- Set auto announce timer
- Light up keyboard (user toggle)
Will crash in about 5 minutes of normal use (sorry)I had 5d uptime on v0.2.0 with BLE disabled- Make LXST voice calls (codec2 only, quality sounds horrible coming out the other end in Columba, needs work)
Why "Pyxis"
Pyxis, latin for "compass," is a constellation in the southern sky depicting a mariner's compass. Small but essential, the compass ensures every message finds its destination - even when the path is uncertain.