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 184.108.40.206 and 220.127.116.11.
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.