When we think about where we want to take the project, we have one thing that we keep in mind, kind of like our motto I guess and that is we want to be “open” but professional/commercial. What exactly does that mean? Well we want the project to be open meaning you can get it, change it, etc. We are going to make everything open source, even the hardware designs. At the same time, we want to make it so that the project could be installed in a remote location and be trusted to work as well or even better than any commercial repeater product.
With our background in hardware and software development, we have been making hardware and software that can handle the heavy use in live production environments. Our video switch controllers (h3j.com) are used daily on live broadcasts and large events and are reliable. We are putting this experience into the design of this project.
We have a lofty list of goals for this project. We know starting out we will not have all of the features but the list will remain a wish list until we get there.
- Easy to use graphical web interface
- Hybrid web interface for packet radio control
- Command line interface
- Usage statistics and graphs on the web interface
- One image to install for a repeater or just a simple hotspot
- Reporting ability to cloud reporting services
- Monitoring of power status (batteries, etc)
- Low power
- Small CPU (raspberry Pi, RiotBoard, BeagleBone Black, etc)
- Built in redundancy using multiple CPUs
- app_rpt (Most notably known for AllStar Link Network and WAN)
- Repeater Management (CTCSS, DTMF, Identification, Courtesy Tones, etc)
- Ability to work with a large number of transceivers
- LCD Status Display
- Physical User Interface
- 3 Timed Regular Identification / announcements that are configurable for content
- Regular Event Schedules and announcements (for example, if you have a traffic net every night at 7:30, you can have it sent out a notice 5 or 10 minutes early)