Radio Management: A quick guide with links


I've had a few questions over the last few months about Radio Management and OTAP - and although I've written a few posts on this topic, there still seems to be some unanswered questions.

Here's a short summary of what you should know with links to other information sources. If anything needs to be added once the publish button has been pressed, I'll do that at the bottom of this post or in blue.

Radio Management

MOTOTRBO Radio Management provides an efficient and simple means to manage multiple device configurations across - potentially - many radio networks.

Radio Management runs on Microsoft Windows (Windows 7 or later). The Radio Management server should have ample disk space, as the database will grow as you make changes and add radios.

There are five major components to a Radio Management setup:

  • The Radio Management Database - This stores all the data about the managed devices. Usually abbreviated to RM. It uses Microsoft SQL Server Express as a basis for managing relational data.
  • Job Processor - This gathers the required information from the RM Database and sends it on to the Device Programmer. If the PC which hosts the Job Processor has more Processor Cores, it will be able to handle more concurrent jobs.You can have a single or multiple Job Processor PCs connected to a server.
  • The Device Programmer - this takes the information sent from the Job Processor and sends it out to a device. You can have a single or multiple Device Programmer PCs connected to a server. You can also allocate a certain number of radios to be OTAPed (or programmed) from a specific Device Programmer PC.
  • On non-Capacity Max systems, you would also use Device Discovery and Mobility Service (abbr. DDMS) to process ARS messages from radios, and send this information on to the Device Programmer. DDMS would also only really be used when you use OTAP since it helps Radio Management to figure out which radio is on or not.
  • MNIS would be used on systems that don't use a Control Station (read further) but instead use NAI (or VRC on Capacity Max).

The above components can be installed on the same PC or installed on different PCs - if the latter is used, there needs to be IP connectivity between all of these. There are a multitude of possible combinations.

For more details, have a look at the following posts:


There are two ways to send configuration updates to a radio:
  • Via the radio channel (trunked or conventional).
  • Via WiFi - if the target radios has WiFi enabled.

There are two ways to access the radio channel to handle OTAP:
  • Using a Control Station.
  • Using MNIS and NAI.
A Control Station is essentially a MOTOTRBO radio connected to the PC that hosts the Device Programmer. The radio would be connected to the PC via a USB cable (the programming cable).
In a Capacity Max system you would not (want to) be using a Control Station since it would not be very efficient for networks of this size.

If only one Control Station is connected to the PC, Windows will use the RNDIS driver, included with the MOTOTRBO CPS. If multiple Control Stations are used, the Multi Channel Device Driver must be used and each Control Station must have a different Radio IP. If using a Control Station, you will need to set up a static-persistant route between the and subnets.

MNIS is a middleware application that routes data between the physical IP network and RF Air Interface. It resides on the PC hosting the Device Programmer (or application) and runs as a Service. From the radio network it is seen as a "virtual radio" with a DMR Radio ID. From the IP network (or PC).

For more details, have a look at the following posts:


There are two "ways" to use Radio Management: this is referred to as modes. There is what is known as Template Mode and there is Configuration Mode.

In Template Mode, you would access Radio Management via the CPS. You would also have a list of radios to which you would apply (a) common template(s). The template(s) would essentially be a generic codeplug containing the settings sshared between radios. Radio Management would pull the settings from the template and use the Radio ID shown in the list.

In Configuration Mode, you would access Radio Management via Radio Management Client (a seperate application). You would still have a list of radios but their settings would be made up of both Configurations and Sets.

Information Sources


After hitting publish, anything extra will be added here:-


  1. Hello Waynes,

    I installed the RM 2.0 version. I do not manage to connect to the "RM SERVER" since the RM Configurator client since the port 443. I nevertheless opened ports on the router and to authorize the access in the firewall.

    I met Alain during a conference Motorola and he told me that actually there were problems recurring of connection between the RM SERVER and the RM Remote devises.

    Have you an idea of the problem?

    1. The only problem I’m aware of is a conflict between Skype and RM Client. If both are running there are some login errors. The fix is to shut down Skype or uninstall it completely.

  2. Hello Wayne,

    I managed to connect the CLIENT RM to the SERVER RM in my local area network with no problem at all but always not in WAN. Certainly the port 443 which is not correctly managed … I am going to verify the routing.

    Thank you

  3. Hi Wayne,

    I have just installed CPS 15.5 and trying to update about 80 DP4801 to new firmware. The problem I'm facing is once I upgrade firmware on the template I am unable to apply the template with updated fw to all the radios that the template was previously applied to, it only lists about half of the radios to apply the new template to. And after I updated all those radios it lists if I try again it says "no available radio to upgrade" even though the template is clearly showing as in use by the remaining radios. There is no difference between the radios that work and the ones that don't, all same model, running same fw with exact same template. Any ideas?

    1. Sorry, I've not seen this before.
      Looks like something your dealer needs to help you with...


Powered by Blogger.