Picture Perfect 4.6 User Manual - UTCFS Global Security Products

134
Picture Perfect 4.6
User Manual
Table 56. Micros form fields (continued)
Tab Field Description
Dial Host on
Schedule
Update
Specify whether the micro should dial the host whenever changes occur due to a micro
schedule.
• Always
The micro always dials the host for any schedule updates that affect it.
• Never
The micro does not dial the host for any schedule updates. Updates are made during
the next communications session.
eFlash
eFlash is a method of flashing your DirecDoor, PXNPlus, Micro/5-PX, Micro/5-PXN, M/PX-2000, and M/PXN-
2000 micros. It does not require the micro to be in maintenance mode while the flash code is being
downloaded. All communication is handled by the host.
The eFlash download program is installed as part of the base Picture Perfect product and can be run on
standalone systems, network subhosts, and on the primary host of a redundant system. On a networked
system, eFlash should not be run on the network host. It can run on all subhosts simultaneously and is
capable of flashing the micros connected to each subhost.
The eflash process requires an amount of free shared memory per each concurrent controller being flashed.
This amount is approximately 4 MB per concurrently flashed controller.
eFlash can be run either from the Micros form or from the UNIX command line.
Using an optional file, .eflashrc, you can define flashing requirements for the entire system once, and then
use part or all of the definition to flash or re-flash micros as needed. This file can be used for scheduling
unattended flashing.
Note:
Only one instance of eFlash can be run on a system. When eFlash begins, it creates a lock file:
/cas/log/eflash.pid
If the lock file exists, indicating that the program is running, when you attempt to launch eFlash, an
error message displays and the program exits.
Dynamic configuration
Micros (firmware 4.03 or later required) can be configured dynamically, meaning the Picture Perfect
system does not have to be restarted for the changes to take effect. However, there are some rules
that must be followed. If these rules are not met, an error message displays and none of the changes
are made until that rule is satisfied. The error message window remains open until you click OK.
Note:
All fields on the Micros form support dynamic configuration, except for Micro ID. Once a micro’s ID is set, it cannot
be changed.
Dynamic configuration rules:
1. Every micro must have a head (or upstream) micro.
2. Every micro must have a tail (or downstream) micro.
3. A micro can be upstream from at most one micro.
4. A micro can be downstream from at most one micro.
5. The primary port must be the same for a micro and its downstream micro.
6. The secondary port must be the same for a micro and its downstream micro.
7. An upstream micro must have a matching downstream micro.
8. A downstream micro must have a matching upstream micro.
9. The last micro in a bi-directional line must have a host downstream.
10. Two head micros cannot have the same primary port.
11. Two tail micros cannot have the same secondary port.