ON3WOO — HAM radio

HAM-DMR: talkgroup 9 is unnecessary.

Fri, 20 May 2016 09:37:49 GMT

HAM-DMR

Human curiosity knows no bounds, and where there is a will, there is a way. This is often the starting point of amateur radio. Next to the hobbyist with a tall antenna mast and a big antenna in the garden, a different kind of radio amateur has emerged in recent years, curious about new technologies and communication techniques in the private and professional world. Radio amateurs have thus embraced digital DMR technology, in which conversations can be digitally encoded and sent over long distances via the worldwide Internet.

The world of talkgroups

The world currently has 3 large international DMR-based radio networks for radio amateurs: DMR-MARC as the first, mainly using Motorola equipment; DMR+ as the second network, which uses the cheaper radios of mainly Hytera; and the so-called BrandMeister network, where besides the professional brands there is also considerable room for home-built equipment and other flexible applications of DMR technology.

Each of those three networks has a similar set-up: through so-called talkgroups per part of the world, continent, language, country and region, radio amateurs can communicate with each other based on language, geographic location or interests. Depending on the national implementation of the network, a radio amateur can make international contacts simply by selecting a different talkgroup.

Those talkgroups are represented by numbers, and based on those numbers the administrators of the national networks and of the individual repeaters can decide whether a transmission on such a talkgroup is passed through on their repeaters. For example, there is a talkgroup with number “1” on DMR-MARC and DMR+ (91 on BrandMeister) that should be available worldwide. Each country also has a national group based on its country code (206 for Belgium, 204 for the Netherlands, 208 for France, …) and depending on the network, regional groups are available as well (2061 for the north of Belgium, 2081 to 2089 for 9 regional zones in France, …).

The interesting thing about these groups is that, even though you are not in France, you can still call a group such as 2083 and have a conversation with other people listening to this group, without the radio amateurs on this group actually being in that region of France. For example, talkgroup 2043 is intended for the South of the Netherlands, but a radio amateur who lives in Maastricht and is on the way to Amsterdam can choose to keep transmitting and listening on group 2043 in Amsterdam, and the local repeater in Amsterdam will pass on the conversations of group 2043 for as long as the radio amateur from Maastricht is active on that repeater.

Local

There are also talkgroups with numbers 8 and 9. These groups have a separate configuration. Talkgroup 9 is reserved on all three networks for so-called “local” conversations on the individual repeater. Conversations in that group are not routed to the rest of the network, but can only be heard on the repeater that receives the incoming communication. Talkgroup 8 is often set up so that conversations on this talkgroup are shared over only a limited number of repeaters, often based on region. A province may have 2 DMR repeaters, for example, where each repeater supports a talkgroup 9 that is not connected to the other repeaters, and a talkgroup 8 that is routed to the other repeater within the same province.

At first sight there is nothing wrong with this. People within range of the repeater can use talkgroup 9 to communicate with other radio amateurs, for example from the same club, on a single repeater, and people living in the same province can use talkgroup 8 to make contact with other residents of the same province.

The problem only arises when one of the participants in a conversation is, for example, mobile and gets out of range of the repeater. Because the conversations on group 8 are shared only to a limited extent, and on group 9 not shared over other repeaters at all, this radio amateur drives himself out of range of the ongoing conversation. In essence this is not desirable, certainly not in an international, worldwide network with worldwide available talkgroups.

Reflectors as a solution

A number of solutions were devised. Many radio amateurs interested in digital technology had already had the same experiences with D-STAR, a network technology from a particular manufacturer of radio equipment. That digital technology used so-called virtual “reflectors”: numbers that local repeaters could connect to, so that a conversation held locally was also available on this “reflector”. Another radio amateur on another repeater could then link his repeater to this reflector to follow, on his own repeater, the conversation that had started on another repeater.

The reflector technique was introduced in HAM-DMR in 2014, and many radio amateurs with D-STAR experience began to apply this technique so they could still hold their conversations beyond the range of their own repeater.

This technique does have gaps, however: when a radio amateur is about to drive out of range of his repeater, he has to find a free moment within an ongoing conversation to link the repeater to a reflector, and once out of range he also has to link the local group 9 of another repeater to that same reflector. That is a lot of actions for a mobile radio amateur. In addition, there is the risk that he does not manage to link the local group of the first repeater to the reflector in time, so that he actually drives out of range of his conversation.

Talkgroups as a solution

Of course it quickly became clear that this technique has its limits. For the classic radio amateur who finds it easier to regard 1 repeater as 1 local entity, the reflector technique is an extension of the familiar analogue logic, but DMR can do so much more, and once you as a radio amateur understand the use and concept of individual talkgroups in the network, you also understand the advantages of talkgroups more quickly.

That also explains the recent group of regional talkgroups in several countries, which are available internationally. Because they can be reached internationally, these talkgroups are often also easy to set up for “roaming” on radios that support this function (the radio automatically switches to the best reachable repeater, yet keeps the same talkgroup settings, so that a conversation continues in the same talkgroup but on another repeater, without any action from the radio amateur).

Away with group 9

With the rise of these regional talkgroups, the local talkgroups 8 and 9 on individual repeaters matter less and less, and maybe it is time to phase out these talkgroups. Because it still often happens that a few radio amateurs notice they are working on the same repeater and move to the local group 9, while listening radio amateurs are not in the same region and cannot switch to the repeater with talkgroup 9 where the conversation continues.

Conversations that currently take place on group 8 and 9, and that are not available to radio amateurs who cannot receive these repeaters directly, are best held on the respective regional talkgroups. These regional talkgroups are accessible to people who are active outside the region and want to follow the conversation.

At the end of the day, however, a sysop cannot block group 9. Group 9 is already not routed on the network, and the repeater will accept every radio amateur who starts transmitting on group 9, and transmit that signal on group 9. So it is up to the individual radio amateur to think about the impact when he or she says “come on, let’s go local on group 9”. Certainly in light of remarks that it is often quiet on the three networks.

So as a radio amateur, don’t shut yourself off: come out onto the regional or on-demand talkgroups and make the hobby more interesting for others too.

About Channel Busy and RX Lists

Wed, 17 Feb 2016 11:14:22 GMT

Even with all the scenarios from the previous presentation about Brandmeister and DMR, you may still run into problems on DMR now and then. I made a new presentation that explains a bit more about problems such as getting a Channel Busy, or hearing conversations while you are taking part in another conversation.

About Channel Busy and RX Lists (file no longer available)

BrandMeister, a practical guide with examples

Wed, 17 Feb 2016 11:08:35 GMT

The new features of the BrandMeister network are not always clear to every radio amateur. Where there used to seem to be only 2 talkgroups, their number has suddenly exploded, and how do you use them? How can you make connections abroad? And how do you reach someone who is in another region?

With the presentation below, I tried to explain all the scenarios through examples. So the next time you see ON7UZ transmitting in group 2067 on the Last Heard dashboard, you will know the how and why after going through this presentation.

Brandmeister in Belgium (file no longer available)

Theoretical reception of the HAM-DMR.BE BrandMeister network

Tue, 09 Feb 2016 15:31:06 GMT

This is currently the theoretical reach of all DMR repeaters connected to the Belgian BrandMeister network:

The following assumptions were made in generating this map:

All information on frequency, antenna height, metres above sea level, transmission power and antenna gain were taken from the UBA unmanned stations (link no longer available) list.
As a receiving device, I assumed the receiving antenna would be 1 metre above masl, and no antenna gain.

This simulation does not take in account possible reception of stations located outside of Belgium. However, some German, Dutch and French stations are available in Belgium.

HAM-DMR: code plugs, software and documentation

Fri, 05 Feb 2016 11:45:48 GMT

I’ve been active for a while now as an amateur radio ham operator on different HAM DMR networks.

Digital mobile radio (DMR) is an open digital mobile radio standard defined in the European Telecommunications Standards Institute (ETSI) and used in commercial products around the world. With these commercial products, HAM radio enthousiasts have developed international networks to communicate and extend the functions of these networks.

These commercial products, portable and mobile radio’s, are programmed to function within these HAM networks.

Over time, I have gathered the necessary software to program these devices (CPS), some documentation and have created my own “codeplugs”, the individual programmation per device.

You can find these files, as is, without documentation, here.

ON3WOO DMR software, codeplug and documentation repository (file no longer available)

DMR repeaters in Belgium

Mon, 01 Feb 2016 12:50:31 GMT

The original 2016 map of DMR repeaters is no longer available.

Update: Data from 2016-01-02 taken from the UBA website, together with a separation per network. For unclear reasons a number of sysops have decided to switch back to DMR+ and to remove themselves from the Belgian Brandmeister network. This means that currently none of the networks can offer full coverage across the country.

TETRA vs DMR Tier III

Fri, 06 Nov 2015 11:45:02 GMT

A good overview of the differences and uses of TETRA networks and DMR Tier 3 networks

Programming Radio Tour in an Albrecht AE69-2H or Uniden UBC69XLT

Mon, 03 Mar 2014 21:07:26 GMT

For people who have an Albrecht AE69-2H, a European Uniden UBC69XLT or similar, and who want to program the new frequencies 164.63125 MHz for Radio Tour Channel 1 and 160.10625 MHz for Radio Tour Channel 2:

Turn the radio off
Hold down key number 3 and turn the radio on. The radio is now configured with the correct ‘step’, i.e. 6.25 kHz
Turn the radio off again
Hold down the keys 2, 9 and Hold and turn the radio on again. All stored memory channels are erased. CLEAr appears on the display.
Press Hold and then press number 1. Then press Func and then Pgm. Channel number 1 appears.
Type in the first frequency, 164.6312, and the radio adds the last digit 5 itself.
Press E to store the frequency on the selected channel.
Press number 2. Then press Func and then Pgm. Channel number 2 appears.
Type in the second frequency, 160.1062, and the radio adds the last digit 5 itself.
Press E to store the frequency on the selected channel.

To scan between these frequencies, press Scan. To select a channel manually, press Hold and then the channel number (1 or 2).

If you manage to carry out steps 5 onwards and the radio takes the correct frequency, you can skip steps 1-4 if you want to keep your previous programming.

Note: a listening licence is required for these frequencies! Apply for a licence here and read the guidelines here.

Wire a Yaesu FTM-10 to a Sena SR10 bluetooth interface

Wed, 12 Dec 2012 12:48:29 GMT

So I ride a motorcyle. And I have a HAM license. And I have a bluetooth intercom system in my motorcycle helmet. And I’d like to do both, since riding is a lonely endeavour.

I had already bought the Sena SR10 bluetooth mono interface with telephone headset and 2-way-radio feature to be able to listen to my Garmin Zumo 660 satellite navigation system and GPS based speed trap alerter (although you can do without the SR10 if the Zumo is your only other mono sound interface next to your phone). I also used the SR10 connected to a PMR so I already had set up the PTT button to my left steering handle. The PMR is a Kenwood one, so I used the Sena compatible cable for Kenwood 2-way radio’s.

Then I bought the Yaesu FTM-10E.

It is a 50W 2 way waterproof radio with remote head, covering the VHF and UHF amateur frequencies. I set up a Diamond SGM-507 antenna on one of the handlebars of the passenger seat, put the radio under the top case and mounted the remote head with a RAM mount in between my handle bars.

Now, there are two options to connect this Yaesu FTM-10 to a bluetooth headset. One is as far as I know currently unproven scenario where you’d buy the FTM-10 with the optional bluetooth adapter and use bluetooth to connect to my bluetooth intercom headset. Theoretically it is possible, but I wonder how I’d manage to use PTT in this scenario because the Sena SMH10 bluetooth intercom I use does not have a PTT button included.

The other option is through the Sena SR10 bluetooth interface, which allows wired connections to bluetooth intercoms, and includes the necessary PTT button and is proven to work with other 2-way radio’s. In price, it’s also about the same as the bluetooth adapter in the FTM-10, but I already bought it for my Garmin Zumo 660 and GPS based speed trap alerter, so that part is already known territory to me.

So basically, you need:

Yaesu FTM-10E or FTM-10R. The connections on the FTM-10SE and FTM-10SR are different, so stop reading now if you have these 10W versions;
Sena SR10 bluetooth adapter
Sena SC-A0116 cable, which connects on one side to the SR10 and is open ended on the other side, for you to make your own cable. Which we are going to do.
Yaesu CT-M11, which connects to the back of the FTM-10 on one side and is also open ended on the other side, which we are going to connect to the Sena cable
2 390 kΩ resistors, which are needed to make the SR10 PTT buttons work with the Yaesu FTM-10
Soldering iron, tape, crimp tools, a steady hand, … anything to hook up some very tiny wires together. Realistically speaking, you are going to prefer soldering the resistors to the wires and then want to make everything waterproof by mounting the connections and resistors in a little box filling it with silicone sealant.

Once you have put in your orders, got your resistors through eBay and have waited 2 months to get your CT-M11 cable, you can get to work.

Download the Connection Yaesu FTM-10 Sena SR10 file, print it out and happy soldering!

Programming a Kenwood TK-3101 on a too quick machine

Mon, 12 Sep 2011 15:24:38 GMT

I have managed to get the typical Kenwood software KPG54D and KPG48D for their TK-3101 transceiver on one of the fastest Apple MacBook Pro‘s currently on the market, running OSX Lion, using VMWare Fusion (link no longer available), Windows XP and DOSBox. This might also work on any other virtualization environment, such as Parallels or VirtualBox, and even natively on other Windows versions.

For years now, I have had a Kenwood TK-3101 mobile radio which is tuned in to PMR446 frequencies. PMR446 is in Europe a way to use radio communication without the need for a license. If the weather is not to crazy and you are in the open, you should be able to receive PMR46-transmissions from up to 5 kilometer away.

I did not have much use for the radio until I started motorcycling. Riding along, PMR’s distance of a few kilometer apart is more interesting than the few meters you get out of bluetooth of the few dozens of meters out of a wireless helmet kit. Nice to talk to the person behind you on the buddy seat, but not enough to talk to a fellow rider riding in front or behind you.

My brother started riding too and I bought/won a few Kenwood TK-3101’s from eBay, intended to using them while riding. I also bought an aftermarket USB serial cable which the seller claimed would work with TK-3101’s.

Now, everyone on the internet claims 2 things:

You need a slow machine to run KPG48D or KPG54D, since newer, faster machines are too quick for the radio to respond in the same speed the software on your fast computer is expecting data;
KPG48D and KPG54D, both native DOS applications, need a pure connection to the serial COM port. USB won’t cut it.

Well, it turns out the above is only partial true.

VMWare Fusion, Windows XP

For starters, I needed something that could understand DOS. I had already VMWare Fusion installed, and set up a 32bit Windows XP Professional installation. Both come right out of the box, so you don’t have to modify anything here.

Serial Adapter

The USB to serial adapter I have turns out to be the popular Prolific PL-2030 USB to serial adapter, but in my case it ends in a mini- and microjack connector for Kenwood. Install the driver on the virtual Windows XP, connect the USB cable to your Mac and VMWare Fusion asks you to which machine it should connect the USB adapter. The obvious choice for us is the virtualized Windows XP.

The Kenwood software KPG48D and KPG54D only know of COM1 and COM2 so you need to make sure your USB serial adapter impersonates one of these two ports. Dive into the Windows XP Device Manager to disable one of two COM ports, and set the COM port your USB adapter impersonates to the COM port you just disabled.

The Prolific port will be set at 9500 bps, and this will work.

Installing DOSBox

After that, install DOXBox. It is a DOS emulator, which looks just like your regular DOS window, but it isn’t. For starters, it allows you to slow any program ran in it down on the go.

After installation, you should look in your Start menu to change the Options of DOSBox. This link will open the configuration file of DOSBox. Scroll down to [serial] and make sure that the COM-port you are going to use is set to ‘direct’.

In my case, I was using COM2 so modified the following line:

serial2=directserial realport:COM2

This instructs DOSBox to let any communication from or to the COM2 port in the DOSBox emulator straight to the COM2 port of Windows XP, which in our case is through a virtualized and physical USB port.

Making it all work

Right. Your virtual machine is in place, your COM-port defined and DOSBox installed.

Make sure you have the KPG54D and KPG48D software set up on a easy to reach folder on your Windows XP virtual machine, preferably something like C:\KENWOOD. The reason is that when you start DOSBox, it does not know anything about your C:-drive. You need to mount the directory you wish to use to the emulated C:-drive in the emulator.

mount c: c:\kenwood

Once you have done this, DOSBox will tell you drive C is mounted to the specified directory. Change to the C: drive and start up KPG54D.

KPG54D will show up. Use the Alt key to activate the menu, and use the arrow keys to navigate to Setup where you make sure you have selected the right COM port.

Now we can slow down the emulated version of DOS. Type in Ctrl+F11 to decrease and Ctrl+F12 to increase the Cpu speed cycles which are displayed in the Title bar of DOSBox. Once you reach about 190 cycles, you can navigate to the Program menu, hook up your Kenwood TK-3101, turn it on and read all channel information from your radio.

UPDATED: Even at 3000 cycles, I managed to read all data.

Troubleshooting

If for some reason you still get read errors, try to change the CPU cycles or COM port settings in Windows. It should work out of the box at 9500 bps and 3000 cpu cycles, but sometimes you need to power cycle the transceiver and change the speed of COM port or emulated DOS box to get it to work.

Thoughts

It’s probably possible to skip VMWare Fusion and Windows XP with the OSX version of DOSBox, but I will still have to look into that. At least I found a way that allows me to use 1999 technology with 2011 fastest consumer hardware.