-
Notifications
You must be signed in to change notification settings - Fork 9
30 Frequently Asked Questions
A free and open-source TETRA base station software stack for experimentation and research. See the Introduction for a full description, and the What works / Not functional sections there for the current feature status.
No. See the warning on the Home page.
At the time of writing this FAQ, only a specific fork supports connection to TETRAPack. Keep in mind you must be holder of a valid amateur radio license to join that network.
See the hardware compatibility table on the Requirements page. The short rule: only SDRs with reliable full-duplex hardware timestamping are supported.
No, not at this time. These devices lack reliable hardware timestamping, which is a hard requirement for base station operation. This may change in the future — see Requirements for details and a reference link.
No. The HackRF is half-duplex — it cannot transmit and receive at the same time, which a TETRA base station must do. This is a fundamental hardware limitation.
Yes — a Raspberry Pi 4 (2 GB) has been confirmed to work. See Requirements for minimum specs and configuration tips (real-time scheduling, SD card speed, etc.). You might be able to get away with lower-spec hardware, but as this software grows, expect the requirements to increase as well.
BlueStation officialy aims to support Pi5, so if in the future the compute loads turns out to be too heavy, Pi4 support might have to be dropped.
No. The software is evolving too fast for packaged images to stay useful. You need to build from source on a Debian-based system — see Dependencies and Building.
Use the main upstream repository for the most stable experience. Forks exist for experimental features (e.g. voice calls via Tetrapack/Brew). See Contributions, Forks and Issues for the full list of known forks and what they offer.
Not in the main branch, yet, expect this to change very soon.
Experimental voice support exists in the tetrapack-calls fork — see Contributions, Forks and Issues.
Copy the example config and follow the Configuration page. That page lists the minimum fields you must change and explains every parameter.
Transmitting requires authorization. You are solely responsible for compliance. See the Licensing and Regulatory Compliance section on the Requirements page.
Join the community Telegram group: [https://t.me/+WtWvrlb43NVkNjE0]
It's the best place for quick questions, setup help, and general discussion.
- Check the open issues to see if it's already reported.
- If not, open a new issue using the provided issue template in the repository and fill it out as completely as possible. Issues without enough detail are hard to act on and may be deferred.
See Contributions, Forks and Issues for more on the contribution and issue process.