MOTOROLA SOLUTIONS MN010257A01 Over The Air Programming Using Radio Management User Guide
Intellectual Property and Regulatory Notices
Copyrights
The Motorola Solutions products described in this document may include copyrighted Motorola Solutions computer programs. Laws in the United States and other countries preserve for Motorola Solutions
certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted Motorola Solutions computer programs contained in the Motorola Solutions products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola Solutions.
No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without the prior written permission of Motorola Solutions, Inc.
Trademarks
MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the property of their respective owners.
License Rights
The purchase of Motorola Solutions products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola Solutions, except for the normal nonexclusive, royalty-free license to use that arises by operation of law in the sale of a product.
Open Source Content
This product may contain Open Source software used under license. Refer to the product installation media for full Open Source Legal Notices and Attribution content.
European Union (EU) and United Kingdom (UK) Waste of Electrical and Electronic Equipment (WEEE) Directive
The European Union’s WEEE directive and the UK’s WEEE regulation require that products sold into EU countries and the UK must have the crossed-out wheelie bin label on the product (or the package in some cases). As defined by the WEEE directive, this crossed-out wheelie bin label means that customers and end users in EU and UK countries should not dispose of electronic and electrical equipment or accessories in household waste.
Customers or end users in EU and UK countries should contact their local equipment supplier representative or service center for information about the waste collection system in their country.
Disclaimer
Please note that certain features, facilities, and capabilities described in this document may not be applicable to or licensed for use on a specific system, or may be dependent upon the characteristics of a specific mobile subscriber unit or configuration of certain parameters. Please refer to your Motorola Solutions contact for further information.
© 2024 Motorola Solutions, Inc. All Rights Reserved
Contact Us
The Centralized Managed Support Operations (CMSO) is the primary contact for technical support included in your organization’s service agreement with Motorola Solutions. To enable faster response time to customer issues, Motorola Solutions provides support from multiple countries around the world.
Service agreement customers should be sure to call the CMSO in all situations listed under Customer Responsibilities in their agreement, such as:
- To confirm troubleshooting results and analysis before taking action
Your organization received support phone numbers and other contact information appropriate for your geographic region and service agreement. Use that contact information for the most efficient response. However, if needed, you can also find general support contact information on the Motorola Solutions website, by following these steps:
- Enter motorolasolutions.com in your browser
- Ensure that your organization’s country or region is displayed on the Clicking or tapping the name of the region provides a way to change it.
- Select “Support” on the motorolasolutions.com page.
Comments
Send questions and comments regarding user documentation to documentation@motorolasolutions.com. Provide the following information when reporting a documentation error:
- The document title and part number
- The page number or title of the section with the error
- A description of the error
Motorola Solutions offers various courses designed to assist in learning about the system. For information, go to https://learning.motorolasolutions.com to view the current course offerings and technology paths.
Document History
| Version | Description | Date |
| MN010257A01-AA | Initial converted edition. | April 2024 |
About This Manual
The Vehicular Repeater (VR) mentioned in this manual applies to any of the following products: DVR, DVR-LX®, and VRX1000.
The VR is designed to interface seamlessly to the following MSU:
- Remote Mount APX Series MSU with or without Control Head
When the VR is interfaced to a Remote Mount Motorola Solutions APX Mobile Radio, the complete equipment package is referred to as Digital Vehicular Repeater System (DVRS).
For requirements on compatible Mobile and Portable radios, refer to the Compatibility Charts.
For details on the APX series Mobile or Portable Radios operation, refer to the applicable Manuals available from Motorola Solutions Learning eXperience Portal (LXP) website.
For details on how to operate a VR, refer to the Vehicular Repeater User Guide.
Notations Used in This Manual
This guide is designed to give you more visual cues.
The following graphic icons are used throughout the user guide.
DANGER: The signal word DANGER with the associated safety icon implies information that, if disregarded, will result in death or serious injury.
WARNING: The signal word WARNING with the associated safety icon implies information that, if disregarded, could result in death or serious injury, or serious product damage.
CAUTION: The signal word CAUTION with the associated safety icon implies information that, if disregarded, may result in minor or moderate injury, or serious product damage.
CAUTION: The signal word CAUTION without the associated safety icon implies potential damage to non-MSI equipment, software or data, or injury that is not related to the MSI product.
IMPORTANT: IMPORTANT statements contain information that is crucial to the discussion at hand, but is not a CAUTION or WARNING. There is no warning level associated with the IMPORTANT statement.
NOTE: NOTE contains information more important than the surrounding text, such as exceptions or preconditions. They also refer the reader elsewhere for additional information, remind the reader how to complete an action (when it is not part of the current procedure, for instance), or tell the reader where something is on the screen. There is no warning level associated with a notice.
bTIP contains information that provides the reader a different or quicker method in accomplishing the same task. At times, they also give the reader the best way to proceed or handle the task.
The following special notations highlight certain information:
Table 1: Special Notations
| Example | Description |
| Menu key or PTT button | Bold words indicate a name of a key, button, soft menu item, or programming menu item. |
| Ordering Guide | Italic word indicates title of a bibliographic resource. |
| Powering Off | Typewriter words indicate the Human Machine Interface (HMI) strings or messages displayed on your display |
| File → Templates (DCD Files) → Load DCD Template | Bold words with the arrow between indicate the navigation structure in the menu items. |
User Guides
| Part Number | Description |
| MN010246A01 | Vehicular Repeater Functional Description Manual |
| MN010256A01c | Vehicular Repeater User Guide |
| Programming Guides | |
| MN003621A01 | APX™ CPS Radio Management User Guide |
| MN010245A01 | Vehicular Repeater Programming Guide |
| Data Sheets Data sheets can be retrieved from the Futurecom website. Go to Support → Documentation and Software → DVR-LX/VRX1000 → Datasheets. | |
| Model | Data sheets |
| DVR-LX® |
|
| VRX1000 |
|
| Others | |
| Combability Chart | Includes software compability, compatible APX mobile radios, and XTS/APX portable radios. See Compatibility Chart from Futurecom website: Support → Documentation and Software → DVR-LX/VRX1000 → Compatibility Chart |
| Ordering Guides | Include the following guides:
|
Overview
Over-The-Air-Programming using Radio Management (RM-OTAP) provides radio technicians the ability to
program or upgrade the firmware or features of a DVR-LX® , DVR, or VRX1000 without physically connecting the devices to a computer.
Figure 1: No Physical Connection to VR
The RM-OTAP feature leverages off the APX™ Radio Management application. Firmware and configuration files are pushed to the VR using the Mobile Subscriber Unit (MSU) through any of the following mediums:
- Wi-Fi
- P25 (LMR)
- USB (or USB connected to LTE device/modem)
Figure 2: Delivery Methods for RM-OTAP
RM-OTAP is a licensed feature and can be purchased at either time of order for the VR or purchased as a field upgrade. Refer to the Ordering Guides.
Feature Requirements
Vehicular Repeater (VR)
DVR-LX®, DVR, and VRX1000
VR Configuration Tool
- Tweaker 05 or later
- Futurecom Repeater Configurator 0 or later
Radio Management (RM)
R21.00.01 or later
VR Firmware
1.60 or later
Mobile Firmware
R21.00.01 or later
VR Feature License
RM-OTAP
Mobile Feature License
DVRS MSU Operation
To verify which mobile models support firmware or configuration updates, see RM-OTAP File Type Support on page 29.
TIP:
- When using RM-OTAP for firmware updates, note that firmware compatibility is always
Compatible MSU and VR firmware versions are bundled together in the MSU firmware. If the MSU is updated with a specific firmware, compatible (bundled) VR firmware is applied to the attached VR. For a list of VR-MSU firmware version bundles, refer to the Compatibility Charts.
- Do not mix RM-OTAP configuration with FRC configuration. RM-OTAP and FRC do not communicate and tracking configurations will be Only one method must be selected.
- After the initial launch of RM-OTAP support for the VR, there have been subsequent enhancements to improve the user experience. See Table 2: Radio Management Enhancement on page 14 for details on the capabilities introduced and respective release dates.
Table 2: Radio Management Enhancement
| RM Version | Description |
| R21.00.01 (Initial Launch) | Linking a DCD file with a mobile radio template is always requried when using RM.
|
| R21.40.00 | Linking a DCD file is when working with mobile firmware is no longer needed prior to R21.00.01. Manage → Templates → DVRS Files field, select None. See Linking the Imported DCD File to an MSU Template on page 26 |
| R23.00.00 | VR without an RM-OTAP feature license (regardless of mobile firmware) no longer needs to link a DCD file. Manage → Templates → DVRS Files field, select None. See Linking the Imported DCD File to an MSU Template on page 26 |
| R23.00.00 | Application for an RM-OTAP license to a VR using RM is supported. |
| R26.00.00 | Support added for VR ID only change in SR2021.4 |
VR Firmware Update
When updating the MSU firmware, there is no user action required to update the Vehicular Repeater (VR) firmware. The VR firmware update software (DFB) is bundled with the MSU firmware and automatically updates the VR firmware during an MSU firmware update. Refer to Motorola Solutions Radio Management Training if you have questions regarding an MSU update.
For Motorola Solutions training materials and documentation, go to Motorola Solutions Learning eXperience Portal (LXP) website.
Updating VR Configuration
A Vehicular Repeater (VR) configuration update using RM-OTAP involves the following procedures.
Procedure:
- Creating a DCD file from Tweaker or Futurecom Repeater Configurator (FRC).
- Importing DCD file in the RM server.
- Linking the imported DCD file to an Mobile Subscriber Unit (MSU) template.
- Selecting the template to write to MSU.
DCD File Creation
There are two ways of creating a DCD file, creating a new file, or modifying an existing file.
NOTE: Ensure the Mobile Subscriber Unit (MSU) and Vehicular Repeater (VR) are synchronized. See VR Communication Setup in the manual Vehicular Repeater Programming Guide.
TIP: It is always recommended to save each DCD file to enable future configuration changes for a particular VR.
Creating a New File
Procedure:
- Establish communications with the Vehicular Repeater (VR).
- To read the VR, do one of the following:
- On the FRC, select Repeater → Load Data from Repeater.
- Press shortcut key F2.
A progress dialog pops up.
- Make the required configuration changes to the downloaded data.
- To save the data as a DCD file, select File → Templates (DCD Files) → Save DCD Template.
- In the Save As dialog, navigate to the desired location and enter a filename. Click Save.
- In the DCD Options window, fill in the following fields and click OK.
Configuration Data Name
Filename displayed after importing into Radio Management. (The maximum is 23 alphanumeric characters.)
Description
Additional text to clarify the content. Displayed in Preview File Header section on the Open File window. (The maximum is 1024 alphanumeric characters.) Load TXT File Command button that loads and external file that contains a list if the serial numbers. All data imported is placed into the List of Serial Numbers field.
List of Serial Numbers
List of serial numbers of the repeater that this DCD file should apply to. If left BLANK, this DCD file is applicable to all repeaters. (The maximum is 65000 alphanumeric characters.) Applicable when delivered to repeater using FRC or RM-OTAP.
Encryption
Option to encrypt codeplug file. Select between Default and Custom encryption. If Custom is selected, specify a password in the Password field and reconfirm the password in the Confirm field.
Bundle License File
Command button that selects a License File to be bundled to the DCD file. The text file next to the button displays the License Files to be bundled.
Result: The DCD file is successfully saved.
Modifying an Existing File
NOTE: DPD files are not meant to be used for this purpose. Only DCD files may be modified to create
another DCD file.
Procedure:
- Select File → Templates (DCD Files) → Load DCD Template. Load DCD file caution dialog pops up.
- Click Continue.
- In the Open File window, navigate to the DCD file and click Open.
NOTE: If the saved DCD file was previously saved with a description, the details are displayed in
the Preview File Header section.
- Unselect the undesired options and click OK.
- Make the required configuration changes to the data.
- To save as a DCD file, select File → Templates (DCD Files) → Save DCD Template.
- In the Save dialog, navigate to the desired location and enter a filename. Click Save.
- In the DCD Options window, fill in the following fields and click OK.
Configuration Data Name
Filename displayed after importing into Radio Management. (The maximum is 23 alphanumeric characters.)
Description
Additional text to clarify the content. Displayed in Preview File Header section on the Open File window. (The maximum is 1024 alphanumeric characters.)
Load TXT File
Command button that loads and external file that contains a list if the serial numbers. All data imported is placed into the List of Serial Numbers field.
List of Serial Numbers
List of serial numbers of the repeater that this DCD file should apply to. If left BLANK, this DCD file is applicable to all repeaters. (The maximum is 65000 alphanumeric characters.) Applicable when delivered to repeater using FRC or RM-OTAP.
BOption to encrypt codeplug file. Select between Default and Custom encryption. If Custom is selected, specify a password in the Password field and reconfirm the password in the Confirm field.
Bundle License File
Command button that selects a License File to be bundled to the DCD file. The text file next to the button displays the License Files to be bundled.
License File Application
All feature license files, including the RM-OTAP license file, may be sent using RM-OTAP by bundling with a DCD file.
A license file is bundled in as part of the creation or modification of a DCD file. Note the Bundle License File button in the DCD Options window.
NOTE : Outdated versions of Tweaker or FRC have a separate option for saving DCD files with license.
Select File → DCD Files → Save DCD File with License.
Bundle License File to Template File
You can bundle a license file to a template file. This can be delivered to a single repeater or fleet of repeaters using Radio Manager. The serial number of any repeater that matches a serial number in the bundled license file will have that feature enabled and take in the configurations in the corresponding template file.
Previewing License Information Bundled to Template File
You can bundle a license file to a DCD file for deployment using Radio Management. FRC shows a preview of information prior to loading the DCD file.
Procedure:
- Select File → Templates (DCD Files) → Load DCD Template.
Load DCD file caution dialog pops up.
- Click Continue.
- In the Open File window, navigate to the DCD file and enable Preview File Header.
Result: Enabled license and corresponding serial numbers are shown.
Applying License to Repeater Using Radio Manager
A repeater must have an RM-OTAP license already enabled for it to support DCD updates from Radio Management (RM). One exception is that users can enable RM-OTAP license when using a bundled license file together with a DCD file update.
NOTE: RM-OTAP license must be already enabled or included in the bundled license file before using RM to update another feature license.
Procedure:
- Create a DCD file on the FRC with a bundled license
NOTE: See Creating a New File on page 17 or Modifying an Existing File on page 19 for detailed procedures.
a. Select File → Templates (DCD Files) → Save DCD Template.
b. Follow the prompts and specify the DCD filename.
c. In the DCD Options window, enter specifics about the DCD file.
d. Click Bundle License File to pick up the appropriate .upf file.
e. Click OK to save the DCD file. - Import the newly created DCD file into the Radio
- Link the DCD file to the corresponding Template of the mobile
- Schedule a Write job on RM for the mobile radio to push the
Result: The MSU and Repeater process the DCD update. Feature licenses specified in the bundled license file will be applied.
Importing DCD File in RM Server
Prerequisites: Launch Radio Management.
TIP:
- It is always recommended to use a new DCD filename. When reusing an existing DCD filename, delete the existing DCD file from DVRS Files window in RM to ensure the new DCD file will be properly imported.
- Note that a DCD file created prior to FRC 1.18 cannot be used.
- For more information on the Radio Management, see APX™ CPS Radio Management User Guide
Procedure:
- From Radio Management Client-Radio View, select
Actions → Manage → DVRS Files. - In the new window, select
Import. - Navigate to the previously saved DCD file from Tweaker or FRC, and click Open.
- In Radio Management Server-Job View, confirm that the DCD file has been imported successfully.
Linking the Imported DCD File to an MSU Template
- To open the Template View window, in Radio Management Client-Radio View, select Actions → Manage → Templates.
- To associate the DCD file with a specific MSU connected to the VR, under the desired template, scroll to the right to find the DVRS File column and select the DCD file from the drop-down menu.
TIP:
- If the DCD file does not appear as expected in the DVRS File drop-down menu, export mobile xml to FRC, save DCD, and import DCD into RM again.
- For more information on the Radio Management, see APX™ CPS Radio Management User Guide.
Selecting the Template to Write to MSU
Prerequisites: In the Radio View window, ensure that the VR ID is correct in the VR ID column.
NOTE:
- The purpose of having the VR ID as a separate column for each radio is that the DCD is a template to be used for multiple radios and does not contain the VR ID.
- The VR ID is displayed in Hexadecimal format. If you enter VR ID in decimal format, it will automatically convert to hexadecimal format.
- VR ID Change Only: To change the VR ID only, a DCD must still be attached to the job even if there are no configuration changes. An attempt to change the VR ID without an attached DCD will have no effect. If NONE is selected, RM blocks the change with a pop-up error message and revert the VR ID
Procedure:
- Right-click on the row and schedule a write job to complete the configuration update on the VR.
- Navigate to Job View to see the status of the configuration update.
Result: When update is complete, the completion status is shown in the job status column. The MSU control head displays Updating DVRS and restarts.
Initiating Automatic Update for a Replacement VR
Prerequisites: Ensure that RM-OTAP have been successfully used to send firmware and configuration to the VR being replaced. If this is not met, refer to Selecting the Template to Write to MSU on page 26 .
Procedure:
- Remove the previous VR from
- Prepare the new VR by installing RM-OTAP license using See License File Application on page 22 for more information.
- Connect the new VR to original
- Power up original MSU and the new
- Observe the DVRS
The following details are displayed:
- Firmware version bundled inside MSU is pushed to the
- If the MSU has a previously saved configuration, the saved configuration is pushed to the VR as
- VR ID is
Result : Once the update is completed, the MSU will reset.
Overwriting a Temporary Configuration or Firmware Update for a VR
Prerequisites:
- Ensure that RM-OTAP have been successfully used to send firmware and configuration to the VR being replaced. If this is not met, refer to Selecting the Template to Write to MSU on page 26 .
- Firmware, and/or configuration, and/or VR ID have been updated using FRC after RM-OTAP was last
Procedure:
- Restore the VR to the last configuration and firmware sent using RM-
a. Connect your laptop to the new VR using a USB programming cable.
b. Launch FRC.
c. Load the data from the VR.
d. In the FRC navigation tree, click on Update Info.
e. In the Update Info window, do the following:- Click Reload OTAP Configuration from MSU.
- Click Reload OTAP Firmware from MSU.
- Power down the VR.
- Power up the MSU and VR.
- Observe the DVRS update. The following details are displayed:
- Firmware version bundled inside MSU is pushed to the VR.
- If the MSU has a previously saved configuration, the saved configuration is pushed to the VR as well.
- VR ID is updated.
Licensed Feature Upgrade
If you purchased a feature (for example, Authentication), a license file is provided. To bundle this file with a DCD, see License File Application on page 22.
RM-OTAP File Type Support
VR Configuration and License Files
Table 3: VR Remote Configuration and License File Updates (RM R21.00.00)
| MSU Models (AN/BN) | Transport Method (RM to MSU) | ||
| USB | Wi-Fi | P25 (LMR) | |
| APX 7500AN APX 6500AN APX 4500AN APX 2500AN | Supported | Not Supported | Supported |
| APX 8500 APX 6500BN APX 4500BN APX 2500BN | Supported | Supported | Supported |
Table 4: VR Remote Firmware Update (RM R21.00.00)
| MSU Models (AN/BN) | Transport Method (RM to MSU) | ||
| USB | Wi-Fi | P25 (LMR) | |
| APX 7500AN APX 6500AN APX 4500AN APX 2500AN | Supported | Not Supported | Supported |
| APX 8500 APX 6500BN APX 4500BN APX 2500BN | Supported | Supported | Supported |
NOTE: Not all model pairings are offered in all region.
Documents / Resources
 |
MOTOROLA SOLUTIONS MN010257A01 Over The Air Programming Using Radio Management [pdf] User Guide MN010257A01, MN010257A01-AA, MN010257A01 Over The Air Programming Using Radio Management, MN010257A01, Over The Air Programming Using Radio Management, Air Programming Using Radio Management, Programming Using Radio Management, Using Radio Management, Radio Management, Management |
