MOTOTRBO Radio Management: Part 1 Getting Started

As mentioned before in my posts about OTAP, there are several possible topologies for Radio Management (RM).
Within RM, there are essentially five major components: the RM Client (the CPS); the RM Server (the SQL backend et al.); the Device Programmer (the interface between the server and radio); Job Processor (the interface between these all) and MNIS (the server which tells the server where a radio is and if it's switched on).
All of these can be on one PC or on multiple PCs. There can only be one RM Server per system but there can be multiple Clients and multiple Device Programmers.

For the sake of simplicity I'm only going to consider two of these: everything on one and client-server. In my client server scenario the Control Station will be connected to the server via a USB cable. This obviously assumes that the server is within coverage of the system (if not you need another PC with the device programmer installed on it separately and connected to a control station).

So what is a Control Station (a.k.a. Donor Radio)? This is just a standard MOTOTRBO radio, programmed to transmit and receive on the system and connected to an antenna, just like a base station radio. This radio would typically not be a member of any groups so as to allow it to sit silently and fire out configuration changes when needed...

Another possibility is to use the Network Application Interface (NAI) feature, available in release 2.2! This essentially eliminates the need for a Control Station and makes the repeater act as the RF interface for OTAP. This of course requires that NAI licences are loaded into all the repeaters which make up the system.

I have not used the most ideal hardware for my setup: I have an old Dell 260 desktop running Windows XP - this will be my Radio Management server. This PC (I'm on at the moment) will be the RM Client. I have already installed the CPS on it and both PCs are on the WAN at my office.
I have a DM3400 connected to the server PC; this is on 430,3000MHz and has been turned down to 1W (sodass ich keine QRM verursachen).

PC (Client); Device Programmer and Server Operating System Requirements

The supported Operating Systems, for: MOTOTRBO CPS (Radio Management Client); Radio Management Server and Radio Management Device Programmer, are:

  • Windows 8, 32-bit and 64-bit.
  • Windows 7 Home Premium or Professional (SP 2 or higher) 32-bit and 64-bit
  • Windows Server 2008 R2 SP1 32-bit and 64-bit
Windows XP is not supported. 


PC (Client); Device Programmer and Server Hardware Requirements.

For smaller systems with less than 5000 radios, the suggested RM Server hardware is:

  • Intel Xeon® E5‐2400 processor or equivalent
  • At least 8GB RAM
  • 7.2K RPM SATA 3Gbps HDD
  • Gigabit Ethernet

For medium sized systems with between 5000 and 15000 radios, the suggested RM Server hardware is:

  • Intel Xeon® E5‐2600 processor or equivalent
  • At least 16GB RAM
  • 10K RPM SAS 6Gbps HDD
  • Gigabit Ethernet

For larger systems with more than 15000 radios, the suggested RM Server hardware is:

  • Intel Xeon® E5‐4600
  • At least 16GB RAM
  • 15K RPM SAS 6Gbps HDD
  • Gigabit Ethernet

SCSI disk drives are preferred since they provide higher reliability over longer periods of high activity.

The Device Programmer PC  requires a Control Station and Programming Cable or an IP connection to the Radio System (repeaters) which have the Data NAI licences loaded. If an IP connection is used, then this PC also requires MNIS to be installed.

Software Requirements

GMVN5141 DVD (currently GMVN5141AD).

General Requirements

You will need to have a good understanding of Microsoft Windows.
You will need administrative rights on the PC/Server on to which RM will be installed.




Next: installing Radio Management.

Powered by Blogger.