Over The Air Programming Via Radio Manager RM Otap User Guide
Over The Air Programming Via Radio Manager RM Otap User Guide
for DVR-LX®/DVR/VRX1000
Document: 8K083X64
Revision: R4.1
Date: May 2022
8K083X64 R4.1
RM-OTAP User Guide
Document Revisions
Rev Date Notes & References
0 2020-07-27 Initial Release
1 2020-08-07 Added DVR-LX®, RM-OTAP File Type Support
2 2020-10-14 Added Helpful Hints
2.1 2020-11-20 Updated DVR reference to VR, Updated support for FW-LMR
3 2020-02-24 Added Helpful Hints: FW Compatibility, Enhancements
Clarification of license type support- now included RM-OTAP license
3.1 2020-08-18 Updated information about saving DCD files and bundling license
3.2 2021-10-13 Addition of How to Update VR ID, Replacing a VR, Overwriting
Temporary Config/FW Update
4.1 2022-01-27 Feature License Notes information added
Proprietary Statement
Table of Contents
The RM-OTAP feature leverages off the APX™ Radio Management application.
Firmware & configuration files are pushed to the VR via Mobile Subscriber Unit (MSU)
through any of the following mediums:
1. Wi-Fi
2. P25 (LMR)
3. USB (or USB connected to LTE device/modem)
RM-OTAP is a licensed feature and can be purchased at either time of order for the VR
or purchased as a field upgrade. Please reference the Futurecom Ordering Guide by
visiting Futurecom > Support > Documentation-Software > DVRS-VRX1000
2. Feature Requirements
Vehicular Repeater (VR): DVR-LX®, DVR and VRX1000
HELPFUL HINT
When using RM-OTAP for firmware updates, please note that firmware
compatibility is always enforced. Compatible MSU and VR firmware versions are
bundled together in the MSU firmware. If MSU is updated with a specific
firmware, compatible (bundled) VR firmware will be applied to the attached VR.
For a list of VR-MSU firmware version bundles, please reference the Futurecom
Compatibility Charts by visiting Futurecom > Support > Documentation-Software
> DVRS-VRX1000
HELPFUL HINT
Do not mix RM-OTAP configuration with FRC configuration. RM-OTAP and FRC
do not communicate and tracking configurations will be confusing. One method
must be selected.
HELPFUL HINT
After the initial launch of RM-OTAP support for the VR, there have been
subsequent enhancements to improve the user experience. Please see below
to determine what capability was introduced and when.
RM VERSION DESCRIPTION
R21.00.01 User is always required to link a dcd file with a mobile radio template
(Initial Launch) when using Radio Management.
a. With RM-OTAP feature license- linked dcd file is applied to the
VR.
b. Without RM-OTAP feature license- linked dcd file is not applied
to the VR.
R21.40.00 User no longer needs to link a dcd file when working with mobile
firmware prior to R21.00.01.
Manage->Templates->DVRS Files field, select “None” (see Section 4.3)
R23.00.00 User no longer needs to link a dcd file when they do not have RM-
OTAP feature license for VR (regardless of mobile firmware).
Manage->Templates->DVRS Files field, select “None” (see Section 4.3)
R23.00.00 User can apply an RM-OTAP license to a VR using RM.
R26.00.00 Support added for VR ID only change in SR2021.4
3. VR Firmware Update
When updating the MSU firmware, there is no user action required to update the VR
firmware. The VR firmware update software (DFB) is bundled with the MSU firmware and
will automatically update the VR firmware during an MSU firmware update. Please refer
to Motorola Radio Management Training if you have questions regarding an MSU update.
https://learning.motorolasolutions.com/
4. VR Configuration Update
A VR configuration update using RM-OTAP is a four-step procedure:
HELPFUL HINT
It is always recommended to save each DCD file to enable future configuration
changes for a particular VR(s).
2. Click Continue.
3. Specify the DCD file location and name then click Open.
NOTE: If original DCD file was saved with a description, it will be displayed in the
Preview File Header section.
4. Unselect any screens with data that is not desired to be loaded and then click OK.
HELPFUL HINT
Older versions of Tweaker/FRC have a separate menu option for saving
DCD files with license: select File → DCD Files → Save DCD File with
License
User can bundle a license file to template file. This can be delivered to a single repeater
or fleet of repeaters via Radio Manager. Any repeater's S/N that matches a S/N in the
bundled license file will have that feature enabled and take in the configurations in the
corresponding template file.
User can bundle a license file to DCD file for deployment via Radio Management. FRC
shows preview of info prior to loading the DCD file
Procedures:
2. Enable checkbox Preview File Header in the Open File dialog window
3. License enabled & corresponding S/N are shown (see purple box above)
In general, repeater must have RM-OTAP license already enabled for it to support DCD
updates from Radio Manager. One exception is that user can enable RM-OTAP license
when using a bundled license file together with a DCD file update.
Note: cannot update another feature license via RM without RM-OTAP license
already enabled or included in the bundled license file
Procedures:
2. From the DVRS Files screen, click Import (icon with three dots inside circle).
3. Select the DCD file previously saved from Tweaker/FRC and click open.
4. In the Job View, confirm the DCD file has imported successfully.
HELPFUL HINTS
It is always recommended to use a new DCD file name. When reusing an
existing DCD file name, delete first from DVRS Files view in Radio
Management (pictured above) to ensure it will be properly imported.
Also note that a DCD created prior to FRC 1.18 cannot be used.
1. To associate the DCD file with a specific MSU connected to the VR, navigate to
Settings->Manage->Templates.
2. Select the MSU template and scroll to the right and locate the "DVRS File"
column and select the DCD file from the drop-down menu.
HELPFUL HINT
If DCD file does not appear as expected in the DVRS File drop down menu,
one possible solution is to export mobile xml to FRC, save DCD, and import
DCD into RM again.
1. Before scheduling the job, in the Radio View, confirm 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.
HELPFUL HINT
VR ID- displayed in Hex- if you enter VR ID as decimal, it will automatically
convert to hex.
HELPFUL HINT
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 will block with a pop-up error message and revert the VR ID.
2. Right click on the row and schedule a write job to complete the configuration
update on the VR.
3. Proceed to Job View to see the status of the configuration update. Once it is
shown as complete in the job status column, the MSU control head will display
"Updating DVRS" and restart.
*If prerequisite is not met, refer to Section 4.5 Error! Reference source not
found..
VR Firmware
VR Remote Firmware Update (RM R21.00.00)
7. Contact Information
Subscribe to our newsletter if you want to be informed about new releases and updates.
Please visit http://futurecom.com/support/newsletter/