Revision C • 10/07
HARRIS CORPORATION
A-6
Appendix A VMCC
device or changing the parent on an existing edge
device does not automatically update the edge de-
vice location in the Explorer pane.
Edge device positions get updated when: a new
device is added to the community; when the com-
munity is reopened (
File,
Open Community
); when
the
Nest edge devices
selection is cycled (To cycle
the Nest selection, open the
Options
window,
uncheck
Nest edge devices
, then click
OK
to close
the options window. Reopen the
Options
window
and recheck
Nest edge devices
and click
OK
to
close the options window.). The edge devices will
then properly nest under their parent.
Inspection and Merge Devices Issues
Matching the Actual Community to an Existing
VMCC-created Community
Inspecting the actual devices, with the intent to
populate the null MAC addresses of a matching
VMCC-created community, brings up a
Merge
Devices
pane after inspection has completed. This
pane shows a list of all devices which match in
both IP address and physical card configuration
to those in the already existing VMCC-created com-
munity.
There is no distinction in this pane between de-
vices that match completely and devices that only
need their MAC address populated in VMCC. Click-
ing
Accept
will populate the MAC addresses in
those community members that matched. Even
though it appears no action is required (the pane
shows that all the devices match), if
Cancel
is
clicked, the MAC addresses are not filled in.
Merging a “Real Device” with a VMCC-Entered Device
Inspecting a community, with the intent to merge
an inspected real facility device with a VMCC-en-
tered device, only works if the inspected device
and the existing VMCC device match exactly in
regards to framesize and the types of cards in-
stalled and the card slot positions.
If the two devices do not match exactly, VMCC
only allows the inspected device to be added as a
new community member.
The differences between the VMCC device and
the inspected device are listed in the Inspect win-
dow. Make note of the differences, click
Cancel
and
update the VMCC device accordingly. Then, inspect
the community again. Once the inspected device
matches the VMCC device, VMCC will merge the
inspected device attributes into the existing VMCC
device.
Merge Devices List
If there is a changed device near the bottom of a
long device list in the Merge Devices pane, there
is no immediate indicator that decisions may be
required. Always scroll down through the device
list looking for devices with changes.
Merge Devices with Multiple Changes
If there are multiple devices with changes in the
Merge Devices pane, contiguous selections of
changed devices will display only the list of “Criti-
cal Issues” specific to the first changed device se-
lected. Selection of a device with no changes causes
the next changed device selected to display cor-
rectly.
GENERAL SESSION/MACRO FILE INFO
The SBC uses a memory-resident database to
maintain the file commands (the sections and their
entries) from the last session file loaded or macro
file taken on that console. To the SBC database,
handling a session or a macro file uses the same
procedure: clear the memory-resident database
cleared to make room for the new file, then load
the files contents.
Since clearing the database doesn’t affect the
control panel/hardware settings (the channels’
source and button status is maintained by the
hardware fader modules), the operation of the con-
To Next Page
Loading...
