EasyManua.ls Logo

Futurecom VR - Remote Mode Change of VR by Dispatcher; System PSU

Default Icon
144 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
8G093X01 R5
VR Programming Guide
August 2022 Page 78 of 144
Remote Mode change of VR by Dispatcher / System PSU
Dispatcher / System PSU can send a call alert (page) to a specific MSU ID, which in turn causes
VR mode change in the following order: OFF-SYS-LOC-OFF.
The MSU can be programmed to support one of the following configurations:
Call Alert / Remote Activation Disabled the MSU does not respond to any Call Alert
requests
Call Alert Enabled the MSU responds to Call Alerts addressed to its ID and does NOT
initiate VR mode change
Remote Activation Enabled the MSU will acknowledge Call Alerts addressed to its ID
and will initiate VR mode change provided the source ID of the Call Alert is programmed
in the “VR Remote Activation IDs” table.
When MSU is involved in any one of MSU features (emergency call, private call, status,
etc.) MSU will not accept the call alert from FNE.
VR Remote Activation: via Call Alert” feature is blocked by the MSU.
If “Generate Status on DVRS Mode Change” is enabled for a given DVRS Profile (in the APX
MSU), the MSU will send back a mode change status to indicate the current VR mode (OFF,
SYSTEM, LOCAL). Only the dispatcher console can interpret those status messages:
DVR MODE
STATUS VALUE
OFF
1
LOCAL
2
SYSTEM
3
Dispatcher can’t force a non-primary VR to become a primary and can’t activate a VR when a ‘VR
Disabled’ mode is selected on the control head.

Table of Contents