-
Notifications
You must be signed in to change notification settings - Fork 24
Data Gateway
The data gateway can be used with FreeDMR or HBLink. You don't need to switch to HBNet to use the data gateway. The HBNet web service also functions as a dashboard.
In an attempt to make DMR SMS more useful, the data gateway contains several unique features. Time will tell if they are useful or not.
Bulletin Board - The bulletin board started as a way for users to see if the gateway could decode SMS messages from their radios. Essentially, the Bulletin Board will display whatever you send to it.
Social Status - Social Status is an attempt to create a social media like service that can be used via SMS. Users can post to Social Status. Posts can be viewed on the dashboard, or retrieved via SMS.
Tiny Pages - Tiny Pages are statically retrievable pieces of information. A tiny page can be created by a user in the web service. A tiny page can be retrieved via SMS with a simple command. Potential uses include help messages, net schedule messages, or whatever you can think of.
Hashtags - Anytime an SMS, Social Status post, or Bulletin Board entry contain a hashtag (#), it will be listed on this page. Yet another social media like feature.
Actually tested
| Radio | GPS | SMS Decode | SMS Encode |
|---|---|---|---|
| Anytone D878 | YES | YES | YES |
| Anytone D578 | YES | YES | Most Likely |
| Anytone D868 | Most liely | YES | Most Likely |
| BTech DMR-6x2 | YES | Most likely | Not Tested |
| MD-380 (MD380tools, no GPS) | - | YES | YES |
| MD-380 (stock firmware, GPS) | YES | Most likely | Most likely |
| MD-390 (stock firmware) | YES | YES | Most likely |
| Retevis RT73* | YES | YES | Not Tested |
| Ailunce HD1 | YES | YES | Not Tested |
| Radioddity GD-73e | Unknown | Most likely | YES |
*RT73 must have unconfirmed data setting enabled.
Not tested yet, but will most likely work.
| Radio | GPS | SMS Decode | SMS Encode |
|---|---|---|---|
| TYT MD-2017 | Most likely | Likely | Unknown |
| TYT MD-9600 | Most likely | Likely | Unknown |
| Retevis RT8 | Most likely | Likely | Unknown |
Tested, but with bugs present.
| Radio | GPS | SMS Decode | SMS Encode |
|---|---|---|---|
| Alinco DJ-MD5TGP | WIP | Most likely | Not Tested |
| Motorola DP3601 | WIP | WIP | Not Tested |
Connect Systems GPS enabled radios
When configured, the HBNet core (hbnet.py) will send a list of PEERs to a data gateway that are connected to a MASTER or PROXY where STAT_APRS_POSITIONS are enabled. Positions for the connected hotspots or repeaters are generated and uploaded on the same timer as IGATE_BEACON_TIME in the configuration.
The hotspot Description field becomes the APRS comment, and an SSID containing a letter is assigned based on the last 2 digits of the hotspot's DMR ID, if it is over 7 digits long. The last to digits correspond to a letter of the alphabet. For example, a hotspot connected with a DMR ID of __1234567__01 will have an ending digit of 01, which corresponds to the letter A. An ending in 02 would be B, and so on.
In December of 2020, the project was granted a TOCALL of APHBLx by Bob Bruniga (WB4APR), founder of APRS. The TOCALL field in APRS is used to identify the hardware of software of the sending station. See the official list at http://www.aprs.org/aprs11/tocalls.txt.
The following designate where GPS positions originated from.
APHBL3 - Originating form an HBLink or HBNet network.
APHBLD - Originating via DMRLink (now defunct, see [https://github.com/kf7eel/DMRlink](https://github.com/kf7eel/DMRlink