Radio Management: A quick guide with links

Introduction

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:


OTAP

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 192.168.10.0/24 and 12.0.0.0/8 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:


Modes

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


Addendum

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

15 comments:

  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?

    ReplyDelete
    Replies
    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.

      Delete
  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

    ReplyDelete
  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?

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

      Delete
    2. Hi guys,
      Mr. Stuart, did you solved this issue?
      I am facing the same problem. I need to upgrade a fleet, in the first group of radios (97 portables), I select Manage Template->UpgradeFirmware.. Only one is available to upgrade! All the radios, same model, same templat, exactly the same.
      With other groups, some of them "No radios to upgrade", in some of them just some units...
      Thanks for your support!

      Delete
    3. I could not find find a solution. The only way we could upgrade the firmware on those radios was manually through CPS (not RM). Then read the radio through RM and apply the new template... A lot more hassle than it should be and I have spoken to others who have come across this same issue.

      Delete
  4. hey wayne i have an issue with getting my OTAP to work. I have my OTAP keys set up in my control radio and radio on which i wish to program. Question is there option or steps taken to program the control radio?

    ReplyDelete
    Replies
    1. Have a look at https://cwh050.blogspot.de/2015/08/radio-network-parameters-in-cps.html.

      Confirm whether Device programmer is installed and running.
      Check the configuration of Device Programmer and Job Processor.
      Make sure that the target radios is online and preferably sending ARS.
      In the settings page of Device Programmer and Job Processor, press the Test Connection button.
      Try pinging the Control Station on the 192 and 12 subnets and check that there is a static route between these two subnets for the Control Station.
      If Device Programmer and Job Processor are on different machines, trying pinging from both ends.
      Try pinging a target radio from the Device Programmer host - at the same time check that the Control Station is transmitting short bursts.

      If you still need help, check https://cwh050.blogspot.de/p/support.html

      Delete
  5. Hi Wayne, We have a TRBOnet dispatcher/Watcher solution running on a server and the Swift/Control station for Audio Paths etc. Now the system is running great however I am now trying to get our LCP system to do Radio Management. I have a separate workstation with the dispatcher and watcher client which is also the CPS programming station and has RM and DDMS installed. Anyway I have searched forums high and low and before I throw this at my dealer I thought I'd ask the Guru Wayne. When I start the RM Monitor app and configure it (like your video) even after successful configuring it is still saying across the top of the screen "RM Device Monitor(2.8.14.0) Repeater IP Programming Status There is no system available to be connected". I have my TRBONet watcher on in the background so I can see what is transmitting to whom etc, but the Rm will not work OTA (OK on USB) I have read the System Planner, Your OTAP 1-5 and every forum or instruction I can find including all the documentation by the 3rd party application manufacturers and I still get nothing. I am a little disappointing by the lack of documentation for the RM and the poor design of the app. Especially trying to clean it all up and start again. You can't even uninstalling it - it does not clean uninstall and therefore retains all all old jobs used to try and test it (which failed). I am having to completely re-image the computer to get a fresh start.
    Have you any idea what can be the problem with the error above and where I can get better documentation from Motorola regarding the RM setup and how it works to understand the fault. It would also be better to use the Swift control station as the control radio for the RM too. But as you can guess, there is very little documentation.

    ReplyDelete
    Replies
    1. There is unfortunately no Installation Guide for Radio Management. There is however a fair bit of training material. The difficulty with creating an installation guide is that there are endless possible configurations for Radio Management and it would be near impossible to describe how to set up each one of them. None the less, it's something I'll take up with our documentation team (I have to be careful as suggesting stuff sometimes gets me volunteered/seconded :-))

      The uninstall for Radio Management is a little quirky. You have to uninstall each component; completely uninstall Microsoft SQL then, to be safe, I find that cleaning the registry is also a good idea. No Windows redo needed.

      A quick check to determine the root cause of OTAP failing, is to ping the radio IP. There is a post coming up on this topic but each Radio has an IP address made up of the CAI number and Radio ID. For example, Radio ID 1 will (by default) have an IP address of 12.0.0.1 and Radio 5320 will have an IP address of 12.0.20.200. The rule is, if you can ping the radio from the Device Programmer PC, you can OTAP it. If you cannot ping the radio, try pinging the MNIS tunnel IP which should be 192.168.10.1 (I think) or the Control Station radio which should be at the same address.

      If you're using a Control Station, make sure you can call it using an individual call from another radio.
      If you're using MNIS, you should be able to send it a radio check (not sure on this point).
      Another thing to check, is to make sure there's a static persistent route between the 192 and 12 subnets. MNIS (and the ping test) needs this. There are a number of howto's on this point, just Google "static persistent route windows".

      That's all I can think of for now...

      Delete
  6. Good day Wayne, I keep getting a SQL error on the installation, how do I get around this?

    ReplyDelete
    Replies
    1. Which operating system?
      If it’s Windows 10, have all the updates been applied?
      Do you have admin rights on the machine as well as full access to the C:\Users\%username%\Appdata folder?
      Try also stopping the Antivirus and Windows Defender temporarily.

      Delete
    2. Windows 10, yes its updated daily, but will confirm with IT on the matter. I have access to the stated folder and also admin rights but will double confirm with the IT department.

      Delete
    3. Windows 10, yes its updated daily, but will confirm with IT on the matter. I have access to the stated folder and also admin rights but will double confirm with the IT department.

      Delete

Powered by Blogger.