Shell script to update flatfile DMRId.dat to MySQL Database

Add below crontab :-

20 3 * * * /usr/bin/curl --fail -o /tmp/DMRIds.dat -s http://www.pistar.uk/downloads/DMRIds.dat > /dev/null 2>&1

/path/update_newestdmrid_datfromtmp.sh :-

#!/bin/bash
/usr/bin/mysql --user=dbuser --password='password' -e "source /path/update_newestdmrid_datfromtmp.sql"

/path/update_newestdmrid_datfromtmp.sql :-

USE table;

CREATE TABLE IF NOT EXISTS temp_table SELECT ccs7, callsign, name FROM table LIMIT 0;

CREATE INDEX ccs7 on temp_table (ccs7) USING BTREE;
CREATE INDEX callsign on temp_table (callsign) USING BTREE;
CREATE INDEX name on temp_table (name) USING BTREE;

LOAD DATA LOCAL INFILE '/tmp/DMRIds.dat'
INTO TABLE temp_table
FIELDS TERMINATED BY '\t';

INSERT INTO table
(ccs7, callsign, name)
SELECT t1.ccs7, t1.callsign, t1.name FROM temp_table t1
WHERE NOT EXISTS(SELECT ccs7 FROM table t2
WHERE t2.ccs7 = t1.ccs7 and t2.callsign = t1.callsign);

DROP TABLE temp_table;

***remark your dbuser,password,table & temp_table to your db/user and table in MySQL database

Perl script to grab info from qrz.com or radioid.net

#!/usr/bin/perl

# Use the DBI module
#use strict;
use DBI;
#use warnings;
#use LWP::Simple;
use JSON::XS qw( decode_json );
use Data::Dumper;
use String::Util qw(trim);
use LWP::Simple qw(get);
use LWP::UserAgent;

#qrz api
use Ham::Reference::QRZ;
use Data::Dumper;


my $ua = LWP::UserAgent->new();
$ua->agent('Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36');
# PERL SQL Update Example
# my $callsign = uc("9W2LWK");
sub ucwords
{
my $str = shift;
$str = lc($str);
$str =~ s/\b(\w)/\u$1/g;
return $str;
}

print "Enter callsign please: ";
my $callsign = <STDIN>;
chomp $callsign;
$callsign = uc(trim($callsign));
print "\n";
print "Please enter first name first or last name first: (0=firstnamefirst/1=lastnamefirst): ";
my $flchoice = <STDIN>;
chomp $flchoice;
$flchoice = trim($flchoice);

#-------------------------------------
# qrz.com api
#-------------------------------------

my $qrz = Ham::Reference::QRZ->new(
callsign => $callsign,
username => '9w2lwk',
password => 'xxxxxxx'
);

my $listing = $qrz->get_listing;
my $dxcc = $qrz->get_dxcc;
my $session = $qrz->get_session;

$qrz->set_callsign('9W4GWK');
#debug
print "QRZ.com Surname and lastname\n";
#print Dumper($listing);
#print Dumper($dxcc);
#print Dumper($session);
#end-debug

print "Name: $listing->{name}\n";
print "Last Name: $listing->{fname}\n";

my $fname2 = $listing->{fname};
my $name2 = $listing->{name};
#--------------------------------------
# end of qrz.com api
#--------------------------------------

#my $url = 'http://www.radioid.net/api/dmr/user/?callsign=ON2RVQ';
my $url = 'https://radioid.net/api/dmr/user/?callsign='.$callsign;
my $response = $ua->get($url);
my $content = $response->content;
#my $content = get($url);
#print $content;
die "Couldn't get $url" unless defined $content;
my $json_array = decode_json($content);
my $dsn = 'DBI:mysql:database=databasename;host=localhost';
my $db_user_name = 'dbuser';
my $db_password = 'dbpassword';
my $password = "dbpassword";

print "\n";
print "This is the contents from radioio.net : -"."\n";
print "\n";

print $content;
print "\n";
print "\n";

my $fname = $json_array->{results}->[0]->{fname};
my $surname = $json_array->{results}->[0]->{surname};
my $country = $json_array->{results}->[0]->{country};
my $state = $json_array->{results}->[0]->{state};

print "fname count:-\n";
print $fname2 =~ s/[FT]//g;
print "\n";

if (!defined $fname2)
{
print "not change";
}
else
{
$fname = $fname2;
$surname = $name2;
}

if ($flchoice eq '0')
{
$fullname = ucwords(ucwords(lc($fname)) . " " . ucwords(lc($surname)));
#my $fullname = $fname . $surname;
print "First Name = " . $fname ."\n";
print "Surname = " . $surname ."\n";
print "Full Name = " . $fullname ."\n";
}
elsif ($flchoice eq '1')
{
$fullname = ucwords(ucwords(lc($surname)) . " " . ucwords(lc($fname)));
print "First Name = " . $fname ."\n";
print "Surname = " . $surname ."\n";
print "Full Name = " . $fullname ."\n";
}
else
{
$fullname = ucwords(ucwords(lc($fname)) . " " . ucwords(lc($surname)));
print "First Name = " . $fname ."\n";
print "Surname = " . $surname ."\n";
print "Full Name = " . $fullname ."\n";
}


#print Dumper($json_array);

# Connect to the database
# Note this connection can be used to
# execute more than one statement
# on any number of tables in the database
if ($callsign eq '')
{
print "Input cannot be blank"."\n";
}
else
{
my $dbh = DBI->connect($dsn, $db_user_name, $db_password) or die "Unable to connect: $DBI::errstr\n" ;
print "Select the record out first"."\n";
my $stmt2 = "SELECT * FROM dmrid where callsign = " . "'" . trim("$callsign") . "'";
print "\n";
print $stmt2."\n";
my $sth2 = $dbh->prepare($stmt2) or die "Unable to connect: $DBI::errstr\n" ;
$sth2->execute();

my ($count) = $sth2->fetchrow_array;
if ($count == 0) {
print "NO rows fetched!\n";
#$sth2->finish();
#$dbh->disconnect();
}
else
{
print "Record found!\n";
my $dbh = DBI->connect($dsn, $db_user_name, $db_password) or die "Unable to connect: $DBI::errstr\n" ;

# Create the statement.
#print $flchoice ."\n";
print "debug: Full Name = " . $fullname ."\n";

my $fullname_ = trim($fullname);
my $stmt = "UPDATE dmrid SET name = " . $dbh->quote("$fullname_") . "," . "country = " . $dbh->quote("$country") . "," . "state = " . $dbh->quote("$state") . " WHERE callsign = " . $dbh->quote("$callsign") ;
print "\n";
print "\n";
print $stmt."\n";
# Prepare and execute the SQL query

my $sth = $dbh->prepare($stmt) or die "Unable to connect: $DBI::errstr\n" ;

# Execute the statement
$sth->execute();

$sth->finish();
$dbh->disconnect();
}

}

table structure:-

dmrid.table

SMS functions via DMR

Original post and credit to : Ronald PE2KMV https://www.pe2kmv.nl/wp/en/dmr-en/sms-functions-via-dmr/

The Brandmeister network has some functions to request information via SMS messages. To access these functions specific keywords are to be sent to DMR ID 262993. Then the system responds as well via SMS on these requests. Below you’ll find an overview of these commands with some explanation. The commands are not case sensitive.

 

Furthermore it’s possible to route DMR messages into the DAPNet pager network. More information regarding DAPNet can be found at the website of Dutch Amateur Pagernetwork and  RWTH Aachen (Aachen University). Messages for DAPNet are to be sent to DMR ID 262994.

A pager message for DAPNet is to be sent in the format [callsign] [message], for instance PX0XXX This is a message from DMR to DAPNet . This sends a messagetext ‘This is a message from DMR to DAPNet’ to user PX0XXX . Prerequisite is that ‘PX0XXX’ is a registered DAPNet user.

Build a P25/DMR Cross-Mode Bridge

Quoted from https://blog.927.org/node/1, credit to the admin of the original page
This tutorial will serve as a BASIC guide to building your own cross-mode bridge from P25 to/from a Brandmeister DMR talk group. This tutorial is based on a Raspberry Pi 3B+ hardware, however it should be very similar on Ubuntu 18.04 or other current flavors of Linux. 

Software packages include: DVSwitch from N4IRS: https://github.com/DVSwitch and the P25 Client software from G4KLX at https://github.com/g4klx/P25Clients

If you’re not comfortable with compiling source code, setting file permissions, or modifying firewalls/port-forwarding – Google for these things! There is plenty of help available for your specific software and hardware…

Terminal commands are in Italics, and must be run one line at a time…

OVERVIEW

You'll be installing and configuring several software components that all play together to transcode a DMR data stream to P25 and vice-versa using DVSwitch The DVSwitch packages support other modes as well (NXDN, YaesuFusion, D-Star), and while this document does not cover them, they do not seem wildly different from what we're doing here.

So - let's get on with it!

ARCHITECTURE

P25Reflector<->P25Gateway<->AnalogBridgeP25<->AnalogBridgeDMR<->MMDVMHost<->BM Master

BUILD

We are going to build from the P25 side to the Brandmeister side. The first component is the P25 Reflector. First, download the P25Clients source code from G4KLX from https://github.com/g4klx/P25Client. 

BUILD THE REFLECTOR:

With the method of your choice, download and extract the client software to its default path (P25Clients-master) in /Downloads, and from there. Open a terminal window and.

cd /P25Clients-master/P25Reflector
ls -la


Confirm that you have source files, and they're in the right place: there should be a “P25Reflector.cpp” in this folder.

Copy the ini file to its new home:

sudo cp P25Reflector.ini /etc

Tweak the .ini file - Change “Daemon=1” to “Daemon=0”

sudo vi /etc/P25Reflector.ini

Save and Exit the editor.

Compile (Make sure you’re in ~/Downloads/P25Clients-master/P25Reflector)

make

Copy the compiled executable file and script to their new location: 

sudo cp p25Reflector /usr/local/bin/

sudo cp P25Reflector.sh /usr/local/bin/

sudo chmod +x /usr/local/bin/P25Reflector.sh

Test it!

cd /usr/local/bin
sudo ./P25Reflector.sh start /etc/P25Reflector.ini &


On first run, you should see something like this (ignore the DMRIds.data error)

P25R Start

Leave this terminal window open for now... it should show repeating "No Repeaters Linked" messages... 

BUILD THE P25GATEWAY:

P25Gateway creation is very similar to the P25Reflector. Open a new terminal window and:

cd /P25Clients-master/P25Gateway
ls -la


Confirm that you have source files, and they're in the right place: there should be a “P25Gateway.cpp” in this folder.

Copy the ini and P25Hosts file to their new home:

sudo cp P25Hosts.txt /etc

sudo cp P25Gateway.ini /etc

Compile:

make

Copy the P25Gateway to its new location: 

cp P25Gateway /opt/P25Gateway/

INSTALL DVSWITCH COMPONENTS:

Steve, N4IRS has made installing and configuring his tools very easy. Follow his instructions for adding the software repository and install the Analog Bridge and the MMDVM_Bridge using his instructions at https://dvswitch.groups.io/g/main/message/1224

The 'short version' from Steve's notes: 

cd /tmp
wget http://dvswitch.org/install-dvswitch-repo
chmod +x install-dvswitch-repo
./install-dvswitch-repo
 apt-get update


Install:

sudo apt-get install dvswitch

You should now have a P25Gateway, Analog_Bridge, md380-emu and MMDVM_Bridge folder in /opt - confirm that: 

ls -la /opt

Copy the MMDVM_Bridge.ini to /etc

cp /opt/MMDVM_Bridge.ini /etc

Understanding the next few steps are critical - you'll recall from the Architecture section that 2 instances of Analog_Bridge are needed. We are going to create those and their associated .ini files now.

cd /opt/Analog_Bridge
cp Analog_Bridge Analog_Bridge_p25
cp Analog_Bridge.ini /etc/Analog_Bridge_p25.ini
cp Analog_Bridge Analog_Bridge_DMR
cp Analog_Bridge.ini /etc/Analog_Bridge_DMR.ini


<STOP> TEST POINT B1

You should now have all of the software installed. Let's make sure the ini files that were copied to new folders have landed where we intended. The following files should be in your /etc folder (there will be others - including other .ini files...)

List the .ini files in /etc: 

ls -la /etc|grep .ini
  • P25Reflector.ini
  • P25Gateway.ini
  • Analog_Bridge_DMR.ini
  • Analog_Bridge_P25.ini
  • MMDVM_Bridge.ini
Should all be there... 

Likewise, the following FILES should be in these locations: 
  • /usr/local.bin/P25Reflector/P25Reflector.sh
  • /usr/local.bin/P25Reflector/P25Reflector
  • /opt/Analog_Bridge/Analog_Bridge_DMR
  • /opt/Analog_Bridge/Analog_Bridge_P25
  • /opt/MMDVM_Bridge/MMDVM_Bridge

CONFIGURE

There's no nice way to say this - the following section will require tedious, exacting, precise trial and error. :) The various components installed need to communicate with each other and do so via a collection of ports and everything needs to line up. It can be tricky. Remember we're working from P25 to DMR, and will 'follow the data' through each step. Thankfully, Steve N4IRS makes this as easy as possible - but it does require some very precise changes. You may have noticed during installation that we copied all of the .ini files to /etc - make sure you're editing these, and not the original files from /opt or /usr/local/bin. Worst case, if an edit goes bad you can always copy the default version back into /etc and start again. P25Reflector.ini needs very little tweaking, and we did that at install. (Changed Daemon from "1" to "0"). 

CREATE LOG DIRECTORIES

sudo mkdir /var/log/P25Gateway
sudo mkdir /var/log/P25Reflectorcp
sudo mkdir /var/log/mmdvm


P25GATEWAY

 sudo vi /etc/P25Gateway.ini

[General]
Callsign={Your callsign here}
RptAddress=127.0.0.1
RptPort=32010
LocalPort=42020
Announcements=1
Daemon=0 <--CHANGE "0"

[Id Lookup]
Name=DMRIds.dat
Time=24

[Log]
FilePath=/var/log/P25Gateway/
FileRoot=P25Gateway

[Network]
Port=42010
HostsFile1=/opt/P25Hosts.txt <--CHANGE to /etc/P25Hosts.txt
HostsFile2=./private/P25Hosts.txt
ReloadTime=60
ParrotAddress=127.0.0.1
ParrotPort=42011
Startup={Your P25 Reflector Talkgroup here}
InactivityTimeout=10
Debug=0

P25HOSTS

 sudo vi /etc/P25Hosts.txt

Determine what P25 Talkgroup you will use, and supply that in the P25Hosts.txt file in this format: TG(tab)127.0.0.1(tab)41000

P25Hosts

Save and exit. 

<STOP> TEST POINT C1

Lets test connectivity between the gateway and the reflector. You should still have the P25Reflector running in a terminal window, and it's probably reporting "No Repeaters Linked" every several seconds. We will start the P25Gateway and see if it connects to the P25Reflector:

cd /opt/P25Gateway
./P25Gateway /etc/P25Gateway.ini & 

You should see a process ID number - not an error message. Gateway Start 




Now - in the P25Reflector terminal session, you should see the connection after a few seconds ('P25GATEWAY is my 'Callsign' in the .ini)Reflector Start




"Can't get MMDVM user" error? I've heard reports that the Daemon setting in the P25Gateway file may actially need to be 0

ANALOG_BRIDGE_P25

 sudo vi /etc/Analog_Bridge_P25.ini

The Analog Bridge files only need a couple of modifications - only those lines are listed below: 

[GENERAL]
decoderFallBack = true     
useEmulator = false   

[AMBE_AUDIO]
server = 127.0.0.1
fromDMRPort = 34100 {IMPORTANT}
toDMRPort = 34103 {IMPORTANT}
ambeMode = P25 {IMPORTANT}
minTxTimeMS = 2000
gatewayDmrId = {YOUR DMR-ID+2-Digits. See MMDVM_Bridge notes}
repeaterID = {YOUR DMR-ID+2-Digits. See MMDVM_Bridge notes}
txTg = {YOUR P25 TALKGROUP from P25Hosts.txt HERE}
txTs = 1 
colorCode = 1

[USRP]
server = 127.0.0.1
toASLPort = 34001 {IMPORTANT}
fromASLPort = 32001 {IMPORTANT}
aslAudio = AUDIO_UNITY
agcGain = -20
dmrAudio = AUDIO_UNITY
dmrGain = 0.35

ANALOG_BRIDGE_DMR

 sudo vi /etc/Analog_Bridge_DMR.ini

[GENERAL]
decoderFallBack = true     
useEmulator = false   

[AMBE_AUDIO]
server = 127.0.0.1
fromDMRPort = 31100 {IMPORTANT}
toDMRPort = 31103 {IMPORTANT}
ambeMode = DMR {IMPORTANT}
minTxTimeMS = 2000
gatewayDmrId = {YOUR DMR-ID+2-Digits. See MMDVM_Bridge notes}
repeaterID = {YOUR DMR-ID+2-Digits. See MMDVM_Bridge notes}
txTg = {IMPORTANT - Brandmeister Talkgroup Number to link}
txTs = 1 
colorCode = 1

[USRP]
server = 127.0.0.1
toASLPort = 32001 {IMPORTANT - must match FROM port in P25.ini}
fromASLPort = 34001 {IMPORTANT -must match TO port in P25.ini}
aslAudio = AUDIO_UNITY
agcGain = -20
dmrAudio = AUDIO_UNITY
dmrGain = 0.35

MMDVM_BRIDGE

 sudo vi /etc/MMDVM_Bridge.ini

The MMDVM Bridge connects to the BrandMeister master server, and is essential a 'virtual' hotspot. What you configure here will appear in your BM Dashboard at brandmeister.network. A note about DMR-IDs: You do NOT need to register for a new DMR-ID for this hotspot. Simply append 2 digits to your existing ID, and BM will know what to do. Example: If my DMR-ID is 1234567, I can use anything from 123456701 through 123456799 for the MMDVM_Bridge ID, or any hotspot. 

MMDVM_BRIDGE is another large file - but only a few lines need to be tweaked from default. 

[General]
Callsign={YOUR CALL}
Id={YOUR DMR-ID+2-Digits}
Timeout=180
Duplex=0

[DMR]
Enable=1 {IMPORTANT}
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[P25]
Enable=1 {IMPORTANT}
NAC=927

[DMR Network]
Enable=1 {IMPORTANT}
Address=3101.repeater.net {IMPORTANT - Set your BM Master per your region!)
Port=62031
Jitter=750
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

[P25 Network]
Enable=1 {IMPORTANT}
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0

<STOP> TEST POINT C2

Confirm your MMDVM_Bridge connects to Brandmeister. 

cd /opt/MMDVM_Bridge

./MMDVM_Bridge /etc/MMDVM_Bridge.ini &

After a few seconds, you should see "MMDVM_Bridge is Running", followed by a successful connection to the BM master. Log onto your Brandmeister dashboard, and have a look in "My Hotspots" for your new 'hotspot'. 

If this fails - double check the MMDVM_Bridge.ini file....

BRANDMEISTER CONFIG

Once you've verified that the MMDVM_Bridge has connected to BrandMeister - you need to configure a static talk group for your hotspot. This will push the DMR traffic from BM to your hotspot... Use the same DMR talkgroup that you chose in the ANALOG_BRIDGE_DMR.ini file.... 

PI-STAR CONFIG

Optional step for setting up a hotspot running Pi-Star to connect to your bridged Talkgroup. You'll need the IP address or FQDN that Hotspots will use to access your reflector. 

SSH into your Pi-Star via the method of your choosing, and set the filesystem to read/write:

rpi-rw

Get permissions to modify files:

sudo su

Add your reflector to the P25Hosts file

sudo vi /root/P25Hosts.txt

Enter your information in the format: {TG#}tab{ReflectorIP}tab(41000) - there are also  instructions shown in the file.

Save and Exit.

Force Pi-star to re-load the P25Host file:

sudo pistar-update

When the update completes, exit the pi-star SSH session, and pull up the Dashboard. You should see the TG and IP domain in the "P25 Startup Host" on the Pi-Star configuration screen. You can set this as your startup now or not... 



RUN THIS BEAST!

OK - so here we are... let's run everything together! First - let's start clean. Reboot your device. 

Run each of these in it's own terminal window initially - this will help with troubleshooting. 
cd /usr/local/bin/
./P25Reflector.sh start /etc/P25Reflector.ini &


(new window)
cd /opt/P25Gateway
./P25Gateway /etc/P25Gateway.ini &


(new wind0w)
cd /opt/Analog_Bridge
./Analog_Bridge_DMR /etc/Analog_Bridge_DMR.ini &


(new wind0w)
cd /opt/Analog_Bridge
./Analog_Bridge_P25 /etc/Analog_Bridge_P25.ini &


(new window)
cd /opt/MMDVM_Bridge
./MMDVM_Bridge /etc/MMDVM_Bridge.ini &


(Pro-Tip: I have written a script to launch all of these. Once you've worked out any bugs in the setup and are running without issues, grab the bridge.sh script from here and place it in /opt. You can then start everything up with ./bridge.sh &) 

A note about 

HIT IT WITH SOME P25! 

This is the final step, get a P25 radio and make sure you’ve got the frequency, NAC and talkgroup programmed correctly, and transmit.

In the terminal windows, you should see messages indicating DMR and P25 TX/RX activity. Pay particular attention to the P25Reflector and MMDVM_Bridge info - those seem to convey the most in terms of where something may be going sideways. If that happens, check, and re-check, firewall and IP addresses, DMRIDs, ports and talk groups... and check out the DVSwitch groups.io board. for support! Thanks to everyone involved in creating and maintaining these software tools! 

DSTAR Peanut is linked to XLX522

Thanks to PA7LIM http://PA7lim.nl/peanut , we are now able to use computers (wind0ws), android phones (network-radio with android)  to link with DSTAR reflectors, which are linked, e.g. XLX522

in order to link to the reflector, you need an AMBE chip (USB) and running with AMBEServer application. you could either run it on a windows or a linux machine, for me i am running on a raspberry pi 3B+ as David, PA7LIM will connect to it via its server program, hence you should see PA7LIM-D always connected to XLX522 reflector.

Analog_bridge/MMDVM_Bridge and Allstarlink

Thanks to N4IRS , Now we can utilized the allstarlink’s asterisk USRP module to link to the Analog_bridge program/MMDVM_bridge and of course, the Software AMBE Transcoding MD380-emu.

The basic diagram of the implementation is as below:-

My analog radio Yaesu FT-7900 which connected to serial to windows Echolink (9W2LWK-R) <-> connected to Raspi3 allstarlink asterisk echolink module (9W2LWK-L) , which also connected to allstarlink node 47259 which is also connected to USRP private node 1999 (which internal link via udp port) <-> Analog_Bridge (which need to transcode the audio PCM/DMR via MD380-emu program) <-> MMDVM_Bridge <-> MY BM Master (TG50210) and back forward.

The procedures / process looks very complicated, but if you follow the step from N4IRS documents (at below link), you will get through the setup steps by steps.

Google Doc for setup Analog Bridge

The document above uses Rasbian/Debian type of linux distribution, where it utilized apt-get (Repository) to install all the dependencies, if you are someone that uses Archlinux like me, you can install the dependencies by using Pacman -S xxx command instead, and then download the individual binary version of Analog_Bridge, MMDVM_Bridge here at GitHub , the /bin directory should have the Analog_Bridge.amd64 , Analog_Bridge.armhfAnalog_Bridge.i386 | MMDVM_Bridge.amd64, MMDVM_Bridge.armhfMMDVM_Bridge.i386 accordingly depending on your Linux architecture.

The most difficult part is the MD380-emu, where you need to compile from source from the github if you are not using Rasbian/Debian based linux.

It is a tedious process, what i did was (for armv7h architecture) , i apt-get install md380-emu from my pi-star (Rasbian) then i copy the binary over the the Archlinux (it works perfectly)

For those amateur stations who want to play around with your audio in DMR/C4FM/DSTAR , they can firstly try out Analog-digital on analog radio simplex gateway @ 148.825Mhz CTCSS 177.3Hz hosted by 9W2LWK if you are in USJ/Puchong/Putra Jaya/Cyber Jaya/Shah Alam Area

If you are on android app and you wanted to try out DMR/C4FM/DSTAR , you can use echolink 9W2LWK-L/9W2LWK-R , and listen to your own audio in Broadcastify or Brandmeister Hoseline , of course this is also applied on Analog_bridge , on 148.825Mhz

Looking forward to see new stations try out your audio in C4FM/DMR/DSTAR before jumping to digital devices like FT70D (C4FM) , MD380/390 (DMR), FTM100DR (C4FM, WiresX), Icom ID-51E (DSTAR), Motorola XPR 7550 (DMR) etc. (See my YouTube video on my previous post on how to use SDR to decode DMR signal/RF)

YSF Reflector – to YSF2DMR bridge?

Recently someone asked me on how to bridge the BM TG from a YSF Reflector.

Previously you would need a BM operator to link up on Brandmeister level but since YSF2DMR is available from github, theoretically we can just use the existing MMDVM’s YSF2DMR module to plug into YSFReflector since both of them is listening to localhost UDP ports.

This is what i have done for the new YSFReflector bridge to BM TG525 by using YSF2DMR

https://ysf.lucifernet.com/

 

The configuration is as below:-

[Info]
RXFrequency=433550000
TXFrequency=433550000
Power=1
Latitude=2.xxxx
Longitude=10x.xx9
Height=1
Location=DBKL
Description=Multi-Mode Repeater
URL=http://www.qrz.com/db/9w2lwk

[YSF Network]
Callsign=9W2LWK
#Suffix=ND
Suffix=RPT
DstAddress=127.0.0.1
DstPort=42000
LocalAddress=127.0.0.1
LocalPort=42013
EnableWiresX=1
Daemon=1

[DMR Network]
#Need to put another suffix ’01’ behind your dmrid below
Id=502224101
#XLXFile=/etc/XLXHosts.txt
#XLXReflector=950
#XLXModule=D
StartupDstId=525
# For TG call: StartupPC=0
StartupPC=1
Address=211.60.41.188
Port=62031
Jitter=500
EnableUnlink=0
TGUnlink=4000
PCUnlink=0
# Local=62032
Password=passw0rd
# Options=
TGListFile=/etc/TGList.txt
Debug=0

 

by look at the log above, the YSF2DMR seems working successfully.

 

YSF Reflector download link – https://github.com/g4klx/YSFClients

YSF2DMR download link – https://github.com/juribeparada/YSF2DMR

 

** updated on 16-04-2018

The YSF2DMR on server works but not in an optimal condition whereby some of the DMR stations could not hear the station from YSF, hence a more stable and reliable connection would be operator connection directly from Brandmeister. I contacted 9W2POP (https://www.dmrnet.org) and have the TG525 linked to SINGAPORE YSF-V2

DMR, Pi-STAR and MMDVM

Digital communications for HAM has never been so phenomenon, thanks to the development of the MMDVM boards and pi-star software which let us use the MMDVM/pi-star as a hotspot/gateway to BRANDMEISTER network, hence connect to all over the world in talkgroup (TG) has never been so easy.

Digital mobile radio (DMR) is an open digital mobile radio standard defined in the European Telecommunications Standards Institute (ETSI) Standard TS 102 361 parts 1–4 and used in commercial products around the world, but in HAM world, we are making use of DMR on amateur radio band, mainly on UHF.

If you are on DMR but may want to contact Malaysia talkgroup, please join TG50210, where YSF/Wires-X/DMR are being bridged into one single “zone”, sometimes you may have some oversea stations that connect to the DMR brandmeister TG50210 from YSF or Wires-X Malaysia-Net room, if you are the lucky one. If you do not have a hotspot, you may also connect via 9M2RKL around KL or 9M4RMU by using wires-x on Yaesu digital devices.

There are several good to go options for HAMs which wanted to try out digital communication, especially there are very good reasonable HT around which can be purchased only, most famous HT which is TYT MD380 because it has good customized firmware which can be loaded into its firmware for HAM use (because the device is initially design for commercial use)

TYT MD2017 has dual band (V/U) which also a good choice but now lag of custom firmware (loading userdb is a function which loads all the DMR-ID /callsigns into the HT) and one of the picture above shows that Baofeng RD-5R also could be a nice purchase because up-to-now when writing this article, the firmware of RD-5R connects MMDVM with no problem at all, hence proven the new firmware can be compatible with the dual timeslots (TS) that use in DMR, which previous DM-5R could not support.

TG50210 Lastheard Dashboard: – https://pistar.lucifernet.com

Please register yourself a DMR-ID now, at this URL :- https://www.dmr-marc.net/cgi-bin/trbo-database/register.cgi , it is free

Note:

If anyone wants a good MMDVM board, please contact 9W2SVT, he made a good MMDVM board, he has a good blog over here: –

http://9w2svt.blogspot.com