Over the past few months, the default password “passw0rd” used for MMDVM, Homebrew, and Kairos connections has been progressively removed from BrandMeister DMR Master Servers. This process will be completed by October 1st 2021.
Below are the details of which devices will be affected with this change, and how to address it.
If you have not yet specified a hotspot password in your BrandMeister Selfcare, please do so by following the steps in this article. You will also find explanations on configuring your personalized password for the Openspot, Pi-Star and BlueDV.
MMDVM, Homebrew Repeaters Owners
If you are running a repeater using a 6-digit DMR ID and connected to a BrandMeister Master, and you have not set a password yet, please login to your repeater page and scroll to the bottom of the screen where you will find the “Device Password” field:
Once saved, configure your repeater to use this password when connecting to any BrandMeister Master server.
Dual time-slot MMDVM devices
If you are running a dual-timeslot MMDVM with a 7-digit DMR ID, please follow the steps described in the hotspot section above.
One of the main distinguishing feature of BrandMeister DMR is that the network is accessible from any master. Therefore you have a choice of 40+ master servers to connect your repeater or hotspot. How to choose?
The best performance will not always be with the master server that is closest to you geographically. Rather, it depends on your internet service provider’s capacity/peerings and the one of the master server.
The key factors for best DMR performance are jitter, then latency. Below is the most simple method to find the best master for you, without any special software.
Step 1: Go to the Brandmeister DMR Master Servers list, and select which master(s) you want to consider. Click on the “Status” button and grab the IP address for the master in your browser’s address bar.
Step 2: From the same network as your repeater or hotspot, run a “ping” command for 1 to 2 minutes to each master you are considering. Perform this test during the time of the day where your typically have the most traffic.
Step 3: Check that the round-trip delay provided by each ping (called latency) stays consistent, without any major variations (called jitter). See the examples below:
Good (No Jitter):
~ ping -t 18.104.22.168
Pinging 22.214.171.124 with 32 bytes of data: Reply from 126.96.36.199: bytes=32 time=71ms TTL=54 Reply from 188.8.131.52: bytes=32 time=73ms TTL=54 Reply from 184.108.40.206: bytes=32 time=69ms TTL=54 Reply from 220.127.116.11: bytes=32 time=68ms TTL=54 Reply from 18.104.22.168: bytes=32 time=71ms TTL=54 Reply from 22.214.171.124: bytes=32 time=74ms TTL=54 Reply from 126.96.36.199: bytes=32 time=70ms TTL=54 Reply from 188.8.131.52: bytes=32 time=69ms TTL=54 Reply from 184.108.40.206: bytes=32 time=69ms TTL=54 Reply from 220.127.116.11: bytes=32 time=68ms TTL=54 Reply from 18.104.22.168: bytes=32 time=69ms TTL=54 Reply from 22.214.171.124: bytes=32 time=69ms TTL=54 Reply from 126.96.36.199: bytes=32 time=70ms TTL=54 Reply from 188.8.131.52: bytes=32 time=72ms TTL=54 Reply from 184.108.40.206: bytes=32 time=70ms TTL=54
You can see that there are no major latency variations.
~ ping -t 220.127.116.11
Pinging 18.104.22.168 with 32 bytes of data: Reply from 22.214.171.124: bytes=32 time=71ms TTL=54 Reply from 126.96.36.199: bytes=32 time=73ms TTL=54 Reply from 188.8.131.52: bytes=32 time=354ms TTL=54 Reply from 184.108.40.206: bytes=32 time=366ms TTL=54 Reply from 220.127.116.11: bytes=32 time=219ms TTL=54 Reply from 18.104.22.168: bytes=32 time=72ms TTL=54 Reply from 22.214.171.124: bytes=32 time=70ms TTL=54 Reply from 126.96.36.199: bytes=32 time=77ms TTL=54 Reply from 188.8.131.52: bytes=32 time=983ms TTL=54 Reply from 184.108.40.206: bytes=32 time=875ms TTL=54 Reply from 220.127.116.11: bytes=32 time=917ms TTL=54 Reply from 18.104.22.168: bytes=32 time=75ms TTL=54 Reply from 22.214.171.124: bytes=32 time=72ms TTL=54 Reply from 126.96.36.199: bytes=32 time=819ms TTL=54 Reply from 188.8.131.52: bytes=32 time=668ms TTL=54
You can observe here the big variances in latency, indicating jitter. Symptoms of jitter include choppy/garbled audio and delayed/dropped transmissions.
Once you have found some masters with no jitter, pick the one offering the lowest latency (smallest ping time).
The support team noticed a lot of questions are being sent regarding the use of IDs in radios, hotspots and repeater. Here is how BrandMeister recommends to use DMR IDs based on the different use case.
Accessing BrandMeister DMR with your radio and a public repeater or hotspot
All you have to worry about is the codeplug of your radio. In the configuration, you will use the 7-digit DMR ID your call-sign has been assigned (for example: 2060945) and the proper TX/RX frequencies.
Accessing BrandMeister DMR using your radio and personal hotspot
In your radio’s codeplug, configure your 7-digit personal DMR ID as assigned by HamDigital or RadioID. (For example: 2060945).
In your hotspot configuration, use your 7-digit personal DMR ID followed by “01”, for a total of 9-digits. (For example: 206094501). If you have more than one hotspot, use the suffix 02, 03, etc. Always make sure that all your hotspots are using different frequencies.
Do not add only “1”, “2”, etc. for a total of 8 digits, as this won’t work.
You do not need to request a 6-digit repeater ID for a hotspot, even if more than one person is using it, and even if it is dual-timeslot. The 6-digit repeater IDs are designed for large-coverage repeaters.
Providing a BrandMeister DMR repeater for the general public
If you would like to setup a repeater to allow a larger audience to access the BrandMeister DMR network, you will have to apply for a repeater ID with HamDigital.org or RadioID.net depending on your geographical location. Use this ID as-is in your repeater codeplug configuration and you are done.
If you are planning to deploy more than one repeater you will need to request a new 6-digit repeater ID for each repeater. Do not add “01”, “02” suffixes in each repeater configuration.
BrandMeister Repeater Sysops : How to create a “local talkgroup” for
your repeater ?
Repeater owners like to offer a talkgroup dedicated for hams within the coverage area of the repeater and refer to it as the “local talkgroup”. This can be achieved two ways, depending if you want a talkgroup:
1) that only local users within the repeater coverage can use
As you know, all valid talkgroups numbers are routed between BrandMeister master servers. There is however an exception for talkgroups 1 through 90. QSOs on these talkgroup numbers will never route past the repeater.
Considering that single-digit talkgroup
numbers are usually used for clusters, using a talkgroup number between 10 and
90 for your local-only talkgroup(s) is a good choice.
One might think that Talkgroup 9
on Timeslot 2 is an option because traffic doesn’t seem to route. However it is
not a good idea because TG9/TS2 is dedicated for reflector usage. As soon as
someone connects a reflector on the repeater: all the traffic that users think
is local on TG9/TS2 is now broadcasted on the matching talkgroup on the worldwide
BrandMeister without them knowing! (unless
the connected master is configured to disable reflectors, but better be safe
2) that is dedicated to the local community of the repeater users but also available outside of the coverage area if someone travels and want to use a different repeater or hotspot to talk to hams at home
What is recommended in this case
is to simply use a talkgroup number that matches the 6-digit DMR ID of the
repeater. This avoid any possible collision if choosing an arbitrary talkgroup
number, since all repeaters have a unique ID on the BrandMeister network. 4-digit
and 5-digit talkgroups are usually dedicated to regional talkgroups. There no
need to make this talkgroup static since it is for the repeater’s local users.
As you may know, hotspots connecting to a BrandMeister master server using homebrew or MMDVM protocol require a password to connect. Currently most of you use the “master server password” which is typically published on the corresponding country’s BrandMeister wiki page. Some software packages include those default passwords, relieving the users from needing to research and input this password.
It is also possible, and now strongly recommended for each user to setup their own personalized password from within the BrandMeister Selfcare.
Why setting up a personalized hotspot password for your own callsign ?
If you did not setup a personalized password for your hotspot, anyone can configure their hotspot with your personal DMR ID and connect with the master’s publicly documented default password, and start using the hotspot with your callsign !
Unfortunately this is happening more and more, thus our recommendation for everyone to setup a personalized password. By creating your own password, you ensure that you are the only one able to use your DMR ID to setup a hotspot.
Also setting up your own password will prevent your hotspot connection to stop working when the password is changed on the master you are connecting to.
How to proceed ?
First, create a personalized password in your BrandMeister selfcare.