Go to file
2020-12-26 13:43:19 -08:00
.gitattributes Update to sync dev system 2020-03-14 10:56:16 -05:00
.gitignore non-programatic updates 2019-03-01 11:30:45 -06:00
bridge_all.py Changed initial state values for some reporting variables. Cosmetic, but avoids unecessary tracabacks. 2020-01-13 14:45:17 +00:00
bridge.py fix another bug 2020-11-26 17:44:19 -08:00
config.py add APRS beacon script for gps_data 2020-12-11 12:47:43 -08:00
const.py Add necessary pieces for Talker Alias DMRA 2020-10-15 16:23:55 -05:00
gps_data_igate_beacon.py fix beacon time to minutes 2020-12-11 13:05:59 -08:00
gps_data-SAMPLE.cfg add APRS beacon script for gps_data 2020-12-11 12:47:43 -08:00
gps_data.py add UDT UAB criteria to reduce inaccurate packets 2020-12-26 13:43:19 -08:00
gps_functions.py update readme, sample, and functions 2020-11-26 19:40:43 -08:00
hblink-SAMPLE.cfg Re-add needed code removed when diffing to restore XLX 2020-10-24 21:14:06 -04:00
HBlink.png Adding Official Logo Images 2020-03-06 07:31:12 -06:00
hblink.py remove code from accidental commit 2020-12-24 13:53:44 -08:00
HBlink.svg Adding Official Logo Images 2020-03-06 07:31:12 -06:00
LICENSE.txt non-programatic updates 2019-03-01 11:30:45 -06:00
log.py non-programatic updates 2019-03-01 11:30:45 -06:00
mk_voice.py non-programatic updates 2019-03-01 11:30:45 -06:00
play_ambe.py update copyrights 2019-03-05 19:01:07 -06:00
playback.py Cleaned up Processing and logging 2019-09-30 14:10:40 -05:00
README.md Update README.md 2020-12-23 22:59:52 -08:00
reporting_const.py Mostly kinda works now 2019-01-04 15:32:13 -06:00
requirements.txt Add packet generation for XLX master module selection 2019-06-19 12:15:21 +00:00
rules_SAMPLE.py update readme, sample, and functions 2020-11-26 19:40:43 -08:00
voice_lib.py Update to sync dev system 2020-03-14 10:56:16 -05:00

GPS/Data Application

This repository contains everything needed to decode DMR GPS packets and SMS for HBLink3. This application can act as a master or peer and receive data as a group call or private call. It is designed to work in a multi system/user network.

Files modified from original master branch of HBLink3:

  • bridge.py
  • config.py

Required modules

  • pynmea2
  • aprslib
  • maidenhead

This should work for DMR radios that send location data as a UTF-8 NMEA sentence. I am hopping to add support for more radios in the future.

Differences in branches

  • GPS: Contains the GPS/Data Application.
  • aprs_features: Contains the GPS/Data Application and a modified version of the APRS implementation for repeaters and hotspots by IU7IGU. (See https://github.com/iu7igu/hblink3-aprs for his work). I combined these for convenience.

Confirmed working:

Actually tested

Radio GPS SMS
Anytone D878 YES YES
Anytone D578 YES YES
MD-380 (MD380tools, no GPS) - YES

Highly suspected to work:

Not tested yet, but will most likely work.

Radio GPS SMS
Anytone D868 Most likely Most likely
BTech DMR-6x2 Most likely Most likely
Alinco DJ-MD5TGP Most likely Most likely
TYT MD-380 Most likely Likely
TYT MD-390 Most likely Likely
TYT MD-2017 Most likely Likely
Retevis RT8 Most likely Likely

Would like to test:

  • Ailunce HD1

Features

  • Decode GPS locations and upload APRS position packets
  • Each user/DMR ID can customize APRS position
  • Ability to receive data as a private call or group call
  • Trigger a command or script via DMR SMS

How it works

A user should configure their radio for the DMR ID of the application and private or group call. When a position is received by the application, it will extract the coordinates and create an APRS position packet. The application will find the callsign of the user based on the sending radio's DMR ID. It is essential to have an up to date subscriber_ids file for this to work. A predefined APRS SSID is appended to the callsign. The APRS location packet is then uploaded to APRS-IS. No setup is required beforehand on the part of the user. This is pretty much "plug and play."

For example, N0CALL has a DMR ID of 1234567. N0CALL's radio sends a position to the application. The application will query the subscriber_ids file for DMR ID 1234567. The result will be N0CALL. An APRS location pack is created and uploaded to APRS-IS.

Individual user/DMR ID APRS settings

By default, all APRS positions will have an SSID of 15, a default comment, and the callsign of the DMR user. These default settings can be changed.

The comment, SSID, and icon can be set for each individual user/DMR ID the application sees. The application stores all the setting in a file. You may have different SSIDs, icons, and comments for different DMR IDs. This is done via DMR SMS using the following commands:

Command Description Example
@SSID Change SSID of user callsign. @SSID 7
@ICON Change the icon of the APRS position. *See http://aprs.net/vm/DOS/SYMBOLS.HTM for icon list. @icon /p
@COM Change the comment of the APRS. @COM This is a test comment.
@MH Set you location by maidenhead grid square. Designed for radios with no GPS or that are not compatable yet. @MH DN97uk

Send a DMR SMS to the configured dmr_data_id in the application with the desired command followed by the value. For example, to change your icon to a dog, the command would be @ICON /p (see the icon table for values). Changing your SSID is as simple as @SSID 7, and @COM Testing 123 will change the comment.

To remove any of the stored values, just send the appropriate command without any input. @COM will remove the stored comment, @ICON will remove the stored icon, and @COM will remove the strored comment. Any position now reports sent will have the default settings.

Configuration

See hblink_SAMPLE.cfg, rules_SAMPLE.py, and gps_data_SAMPLE.cfg for examples.

Special thanks to:

N0MJS - For creating HBLink and dmr_utils. This project not possible without him.

IU7IGU - For creating APRS position beaconing for PEER connections.

IV3JDV - For helping debug SMS in Anytone radios.

KD7LMN - For pointing out a critical bug.

KB5PBM - For helping implement support for MD-380 type radios.

EI7IG - For writing the page explaining MD-380 type GPS packets.

Resources for DMR data

I spent many hours looking at the following for this project. You may find these links useful.

https://github.com/travisgoodspeed/md380tools/issues/160

https://jpronans.github.io/ei7ig/dmr.html

http://cloud.dstar.su/files/G4KLX/MMDVM/MMDVM%20Specification%2020150922.pdf

https://wiki.brandmeister.network/index.php/NMEA_Location_Reporting

https://forums.radioreference.com/threads/motorola-lrrp-protocol.370081/

https://forums.radioreference.com/threads/lrrp-decoding.359575/

https://github.com/polkabana/go-dmr

https://github.com/nonoo/dmrshark

https://wiki.brandmeister.network/index.php/Compressed_Location_Reporting

All of the ETSI DMR documents (ETSI 102 361-1 through 361-4).

The Shark RF forums.


FOR SUPPORT, DISCUSSION, GETTING INVOLVED

Please join the DVSwitch group at groups.io for online forum support, discussion, and to become part of the development team.

DVSwitch@groups.io

A voluntary registrty for HBlink systems with public access has been created at http://hblink-register.com.es Please consider listing your system if you allow open access.


PROJECT: Open Source HomeBrew Repeater Proctol Client/Master.

UPDATES:

PURPOSE: Thanks to the work of Jonathan Naylor, G4KLX; Hans Barthen, DL5DI; Torsten Shultze, DG1HT we have an open protocol for internetworking DMR repeaters. Unfortunately, there's no generic client and/or master stacks. This project is to build an open-source, python-based implementation. You are free to use this software however you want, however we ask that you provide attribution in some public venue (such as project, club, organization web site). This helps us see where the software is in use and track how it is used.

For those who will ask: This is a piece of software that implements an open-source, amateur radio networking protocol. It is not a network. It is not intended to be a network. It is not intended to replace or circumvent a network. People do those things, code doesn't.

PROPERTY:
This work represents the author's interpretation of the HomeBrew Repeater Protocol, based on the 2015-07-26 documents from DMRplus, "IPSC Protocol Specs for homebrew DMR repeater" as written by Jonathan Naylor, G4KLX; Hans Barthen, DL5DI; Torsten Shultze, DG1HT, also licenced under Creative Commons BY-NC-SA license.

WARRANTY None. The owners of this work make absolutely no warranty, express or implied. Use this software at your own risk.

PRE-REQUISITE KNOWLEDGE:
This document assumes the reader is familiar with Linux/UNIX, the Python programming language and DMR.

Using docker version

To work with provided docker setup you will need:

  • A private repository with your configuration files (all .cfg files in repo will be copyed to the application root directory on start up)
  • A service user able to read your private repository (or be brave and publish your configuration, or be really brave and give your username and password to the docker)
  • A server with docker installed
  • Follow this simple steps:

Build your own image from source


docker build . -t millaguie/hblink:3.0.0

Or user a prebuilt one in docker hub: millaguie/hblink:3.0.0

Wake up your container

touch /var/log/hblink.log
chown 65000  /var/log/hblink.log
 run -v /var/log/hblink.log:/var/log/hblink.log -e GIT_USER=$USER -e GIT_PASSWORD=$PASSWORD -e GIT_REPO=$URL_TO_REPO_WITHOUT_HTTPS://  -p 54000:54000  millaguie/hblink:3.0.0

MORE DOCUMENTATION TO COME

0x49 DE N0MJS

Copyright (C) 2016-2020 Cortney T. Buffington, N0MJS n0mjs@me.com

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA