A blog about MOTOTRBO and other things.

22 August 2015

Radio network parameters in the CPS

In all MOTOTRBO radios, the Network page contains settings relating to the radios connectivity with external devices and services.

If the radio has Bluetooth(TM) functionality (in this example a DM4601) then it will have three IP network connections: the Bluetooth data connection and the USB connection. The third IP connection is the RF air interface (i.e. DMR transmitter and receiver).

Radio IP sets the USB and Bluetooth IP address. The default value is 192.168.10.1. The Bluetooth IP is automatically one subnet up: 192.168.11.1.

When you connect a PC to the radio, Windows will setup a network connection with an IP address of 192.168.10.2 (i.e. radio IP + 1)
Any Bluetooth data device connecting will get 192.168.11.2.


The RF air interface IP address is defined by the Radio IP plus the CAI Network setting. The CAI Network defines the first octet of the IP address - in this case 12. The remaining three octets of of the (IPv4) IP address are defined by the Radio ID.

I strongly recommend that you leave the CAI Network setting at 12!

The first octet of the destination IP address for a Group call is defined by the CAI Group Network. So if Radio 1 sends a data message to any radios in group 1 the source and destination addresses would be 12.0.0.1 and 225.0.0.1.

 I strongly recommend that you leave the CAI Group Network setting at 225!!

The Maximum TX Packet Data Unit Size sets the maximum number of bytes that will be transmitted per packet. For data intensive applications the PDU size can be increased. In systems where there is interference or a high number of retries, the PDU size should be decreased.

The Telemetry UDP port sets the source and destination port for telemetry messages. I highly recommend leaving this at 4008.

Any data arriving at the radio within the 13.x.x.x IP address space is generally intended for an externally connected device or application. There are three ways for the radio to handle this data:

- Do nothing - Disabled.
- USB - send it to a PC (or device) connected via USB.
- Bluetooth - send it to a paired Bluetooth PC or device.
- Non-IP Peripheral - send it to an external device which doesn't use RNDIS or IP.


The ARS Radio ID is the Radio ID to which this radio will send Presence Notification and Location (GPS) messages. This in turn sets the ARS IP to 13.x.x.x - where x is the ARS radio ID. If this radio is the ARS radio then it will be connected to the application server and Forward to PC will need to be set to USB (or Bluetooth).

The ARS UDP Port defines the UDP port to be used for Presence Notification (Automatic Registration Service) messages. This should be left as is: 4005.

The TMS Radio ID is the Radio ID to which a radio user could send text messages. This in turn sets the TMS IP to 13.x.x.x - where x is the Radio ID in the Contact List and One Touch Access.

There are three user defined ports as well as a XCMP Server ID. These are all used for 3rd Party Applications from Motorola's Application Development Partner Programme. 
MOTOTRBO radios use XCMP to send commands between the option board; radio and external hardware. The user defined ports can be used to direct certain data to the option board or to an external device.


The settings under Control station only apply if the radio is connected to an application server - hence the name Control Station.

If this radio is connected to an application server, it could be used for voice only (i.e. when the dispatcher presses the PTT, this radio starts transmitting) or voice and data or just data only.  If this radio is connected to an application server and is used for voice dispatch only then Voice Only can be ticked.

If this radio will be connected to an application server and will be used for data only, then Voice Only should be un-ticked and Data Modem should be set to either Conventional or Capacity Plus. This setting, together with Voice Only, allows multiple Control Stations (radios connected to the Application Server) to share the same Radio ID.

The Data Modem Window Size sets the window size for scheduled data and works in conjunction with Enhanced GPS.

Repeater Latitude and Longitude allows you to set the coordinates of the repeater which the Control Station radio is monitoring.**

The ARS Monitoring ID is the ID of the radio, that is connected to the ARS server, that the fielded radios will communicate with OTAP services. When a radio powers up, it announces its presence by communicating with the ARS server. The Monitoring ID must not be the same ID as the ARS Radio ID in Network.

The Location Server UDP port is the port number used for inbound ARS and GPS messages. The XCMP Server UDP Port is used by 3rd party applications. The Battery Management Server UDP Port is the port number used by IMPRES Fleet Management.**


On models which support Bluetooth, the below parameters will be visible. The Country Code Channel sets the number of channels available for connectivity. In some countries, only 23 channels are permitted.

Reconnect TOT sets the duration that the radio waits while attempting to reconnect to the same device after it was disconnected, perhaps due to out or range or the radio switching off. If this timer expires and the Bluetooth device comes back into range then it will have to be re-paired.

Off-Hook defines how the Bluetooth audio device and radio should operate if it is taken off hook.

If Device Database Erase On Power Up is ticked, the radio will delete all known BLuetooth devices when switching on.

Bluetooth Serial Port Profile Data Routing defines how a Bluetooth data device should be handled by the radio.

USB HID Data Routing defines how data from a Human Input Device (e.g. a barcode reader) should be handled by the radio.




** More about this in a future post.

16 August 2015

R2.4B on the SL1600


On 20 July, Motorola released R2.4B firmware which introduces a few noteworthy features. Some of these features are detailed here and in my other posts (see below).

In General


  • Home Channel Reminder. Radio alerts user when they have left their primary home channel for a predetermined period of time.
  • Adaptive Rest Channel RDAC Alarm: Repeater generates an RDAC alarm when the “Adaptive Forced Rest Channel Rotation” feature rotates the Rest channel.
  • Improved RSSI Indication: Radios provide a more precise signal strength indication for the user.
  • SLR 5500 Repeater support.
  • Hebrew Keypad models. Addition of Hebrew language capability and a number of Hebrew
  • language keypad on some portable models.


On the SL1600


  • Ability to support radio names up to 12 characters in length.
  • Ability  to support the Alveolar Trill (i.e. rolling “r”) enhancement option.
  • Ability for the radio to support the OTA Battery Management registration feature.
  • The maximum “Digital TX High Power” setting can be tuned for 2,5W or 3W without impacting the other “Digital TX High Power” settings (i.e. 2W and 1W). In a number of European countries the legal limit is 2,5W.


New in R2.4B: Roaming RSSI per site

On 20 July, Motorola released R2.4B firmware for the second generation MOTORBO radios. In this system release, there are some important enhancements which I will detail here.

It is now possible to define a Roaming RSSI threshold per site, in IPSC and LCP. Previously only one Roaming RSSI level could be defined.
This is particularly useful if there are significant differences between the relative signal strengths from multiple sites in a system: the site with the best coverage and strongest signal could have a higher Roaming RSSI threshold thus preventing all the radios roaming to it.

In IPSC

Roaming Per-Site RSSI Threshold in IPSC.
Ticking the Use Per-Site RSSI Threshold in the Roam List un-greys the RSSI Threshold spinbox in the channel. Note that the channel should preferably be in the Channel Pool and IP Site needs to be ticked. The channel also needs to be in one of the roam lists.
These videos describe how to set up IPSC in the radios and repeaters.

In LCP

Roaming Per-Site RSSI Threshold in LCP (Click to enlarge)
In LCP, ticking the Use Per-Site RSSI Threshold in the Site List un-greys the RSSI Threshold column in the site table.
These videos describe how to set up LCP.

Emergency enhancements in R2.4B

On 20 July (while I was traveling and was on holiday), Motorola released R2.4B firmware for the second generation MOTORBO radios. In this system release, there are some important enhancements which I will detail here.

Emergency Search Tone and LED

When the radio enters emergency mode, it be configured to also sound a a loud tone through the speaker. This helps rescue personnel locate the exact position of the radio (and the user thereof) in darkness or when there is no visibility. At the same time, the emergency alert LED can be configured to continue to flash while idle and in emergency.

Emergency Contact

Addition of a contact field in the (Conventional) Digital Emergency System to enable the Revert Channel and Contact to be independently configured in the CPS.

Other Enhancements


  • The radio user can now configure the duration of the emergency alert tone.
  • An Emergency Vibrate option has been added to the SL4000 series.
  • When the radio is in emergency mode, the user can manually transmit during an emergency hot-mic session.
  • The radio can now flash the red LED and sound a periodic tone while receiving emergency voice.


The Author

Please Note

The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of my employer, Motorola Solutions.

Translate this page

Popular Posts