Hello everyone, After 6 weeks and many hours of work, I am pleased to share my first version of a DMR GPS packet decoder. The GPS/Data application will take the GPS information from packets sent by a radio and upload a position to APRS-IS. It is based on the "blank_app" and can attach to your setup as a peer. *Only tested with Anytone radios (D868, D878, D578) at this time.* Should work for radios sending NMEA sentences over the air (see https://wiki.brandmeister.network/index.php/NMEA_Location_Reporting ). Should also work with BTech DMR-6x2 as that will also send NMEA location sentences. *This will not work with Motorola, Hytera, or MD-380 like radios (not yet, at least).* I am hoping to add support for other radios in the future. I may need help testing when the time comes, if anyone is willing to help. The GPS/Data application will decode and assemble packets sent to its DMR ID (this is configurable) to extract coordinates. It then will match the sending DMR ID to the callsign of the user in the subscriber_ids file. Once the callsign is found, an APRS SSID of "-15" (this can be changed) is appended to the callsign and inserted into the APRS location packet before being uploaded to APRS-IS. This was done to keep the operation of the application simple and in a single file. I have also been able to decode DMR SMS messages with it, but have not developed any functions for this yet. *1.* Setup of the application is fairly simple. You first need to make a configuration file for the connection. It is easiest to copy hblink.cfg and configure a peer connection. You may also set it as a master as well. This is exactly the same as configuring playback.py for the echo function of HBLink. *2.* Open gps_data.py in your favorite text editor and change the settings to your liking (lines 75-85). The settings are as follows: *data_id* - This is the DMR ID where positions are sent. *call_type* - Data sent as a Unit (private) call or Group call. See below for note. *aprs_callsign* - Callsign used to log in to APRS-IS. *aprs_passcode* - Passcode for APRS-IS. *aprs_server* - APRS server *aprs_port* - APRS server port *user_ssid* - APRS SSID appended to callsign of users before upload to APRS-IS. *aprs_comment* - Text for the comment field of the APRS packet. *3.* Run gps_data.py with your configuration file. *4.* Configure user radio to send a position report to the data_id, as defined above, in a group or private call. That's it! You will now be able to see the position of the radio on https://aprs.fi. See https://www.m0pqa.com/2020/05/making-aprs-work-on-anytone-at-d878uv.html for details about configuring GPS on Anytone radios. There are a lot of other helpful articles and videos out there for setting up DMR APRS. In the future, I would like to add support for other radios. I am also hoping to do something useful with SMS functions. Lastly, I am hoping to add some code to allow for APRS packets to be sent via a TNC. These are just some ideas. *Group Calls* In order for group data calls to work, you will need to replace your bridge.py with the one from the GPS repository. This has to do with the routing of packets. *This application is "alpha quality", meaning that there are some bugs.* *Always make a backup of your setup before running this.* You can checkout my GitHub repository under the GPS branch to download. *See https://github.com/kf7eel/hblink3/tree/gps.*

I think I've finally gotten hbmonitor ported to Python 3. All are welcome to test it out, and use this message thread to question or comment. You can find the github repo here: https://github.com/kc1awv/hbmonitor3 A couple things to note: * Module is renamed to monitor.py * Log file is kept in the ./log directory - this was for ease of testing, you can put the log anywhere you want. Just change the line in the config file Right now, "it works for me, here." Hopefully I can get some feedback from others to see if it works there, too. I also tried to keep the style and formatting as close to the original HBmonitor as much as I could. Some changes made by me were for my own ease of readability. Steve KC1AWV

Okay, here we go. I've created a GitHub organization, named it "HBlink-org" and have added the repos that Cort made available to me in order to preserve maximum development history on the site. Cort's no longer on the mailing list, so I will just say that he's been awesome and really does care about the future of the project, just that he can't be the project lead any longer. He was kind enough to make his repos available to me to push into the new org for safekeeping. https://github.com/HBLink-org In that org, you will find all of the projects, named (I believe) the same way that they were named previously. These repos are full mirrors, so all branches (i.e. HB_Bridge and IPSC_Bridge for older HBLink and DMRlink repos) are there. I would strongly suggest that if you have tools that build things like Docker images or whatever, you should update those tools to pull from GitHub at these new repo locations. This will be where they are located, going forward. For those of you with clones of Cort's original repos, you should still be able to issue pull requests to these repos, I'm a bit more fuzzy on whether or not the commit ID's are the same (I think they are), so this whole rebasing of the repos might be a merge headache of epic proportions when time comes to actually attempt to merge pull requests. We'll just have to see, won't we... There will obviously be more details as we progress through this. I will be adding people to the org as members based on expressed interest and being able to identify their GitHub accounts. For the moment, I will be the only one who can commit to the repos until we further establish ground rules for development. In short, I'm taking care of the project until such time that someone better qualified and motivated steps up to manage it in a community-oriented manner. --R -- Randy Hall AA6RH (not K7AGE, quit asking) 😁