Pelco C1553M-B Benutzerhandbuch
C1553M-B (4/05)
221
ACCESS ALARMS AND EVENTS DEFINED ON ANOTHER SERVER
You can access alarms and events defined on another server using the remote server driver feature. Remote server drivers appear as device
drivers in the Object Browser, and are added, edited, and deleted the same way device drivers are. There is a remote server driver for every
server that is running. Refer to Device Drivers for instructions on adding a remote server driver.
drivers in the Object Browser, and are added, edited, and deleted the same way device drivers are. There is a remote server driver for every
server that is running. Refer to Device Drivers for instructions on adding a remote server driver.
Script tags for remote servers are made up of the remote server name that appears in the Object Browser appended with “_Server”. Script tags
for remote devices are made up of the device name that appears in the Object Browser under Sources appended with “_RS”, for “Remote
Server”. Script tags for remote alarms and events appear in the Object Browser as read properties.
for remote devices are made up of the device name that appears in the Object Browser under Sources appended with “_RS”, for “Remote
Server”. Script tags for remote alarms and events appear in the Object Browser as read properties.
The remote server driver for a particular server provides a list of alarms and events defined on that server. Each alarm or event is presented as a
read property of the remote server. The read property has value True when the remote alarm/event’s expression is true. The read property has
value False when the remote alarm/event’s expression is false. The remote server driver does not provide you with access to the alarm/event
definition. You cannot edit the alarm or event, nor can you delete it from the server it is defined on.
read property of the remote server. The read property has value True when the remote alarm/event’s expression is true. The read property has
value False when the remote alarm/event’s expression is false. The remote server driver does not provide you with access to the alarm/event
definition. You cannot edit the alarm or event, nor can you delete it from the server it is defined on.
Figure 242. Accessing Alarms and Events on Another Server
To work with a remotely defined alarm or event, create an alarm or event on your server whose expression tests the remote server’s read
property.
property.
For example, suppose you have added the remote server driver for a server called EMO-3. Suppose EMO-3 has an external door alarm that
triggers an alarm, Door Alarm, that directs Camera1 at the door. On your server, create an alarm that loads live video from Camera1 into a custom
window configured on your server, Window1, when the Door_Alarm read property becomes true. The expression for the alarm is:
triggers an alarm, Door Alarm, that directs Camera1 at the door. On your server, create an alarm that loads live video from Camera1 into a custom
window configured on your server, Window1, when the Door_Alarm read property becomes true. The expression for the alarm is:
EMO-3_Server.Door_Alarm = EMO-3_Server.True.
The alarm’s On Event action is:
SET Window1.LiveSource = Camera1_RS.Output.
TIP: Use context-sensitive help or the script wizard to write scripts involving remote servers. VMX300(-E) will provide you with a pop-up
list of script tags referring to remote servers and their alarms and events, in context. Refer to Scripts and Expressions - Mechanics of
Editing Scripts and Expressions for more information.
list of script tags referring to remote servers and their alarms and events, in context. Refer to Scripts and Expressions - Mechanics of
Editing Scripts and Expressions for more information.