Pelco C1553M-B - page 216

216 C1553M-B (4/05)

g. By seconds: If you want the scheduled action to execute every few seconds, click By Seconds. In the Every area, type in the number

of seconds you want to elapse before the action next executes, up to a maximum of 59 seconds. Fractional amounts will automatically

be rounded.

h. Once: If you want the scheduled action to execute once only on a predetermined day at a predetermined time, click Once. Type the

date in directly, or select it from the drop-down calendar. Use the left and right arrows to select the month in the drop-down calendar,

then select a date by clicking it. Today’s date is circled in red.

Specify the time of day for the action to execute. To set the time, select the hour, minutes, or seconds and click the up and down

arrows.

A schedule that is set to execute once is automatically deleted from the server conﬁguration once it has executed. To save a copy of

the schedule, make a copy of it before it executes using Copy and Paste. Refer to Pop-Up Menus in the Appendix for information on

making copies of objects.

5. Holidays: If you want prevent the scheduled action from executing on certain days of the year, click “Don’t run schedule on holidays.” Click

Set holidays to specify the days you do not want the action to execute. The Edit Holidays dialog box opens.

Figure 240. Edit Holidays Dialog Box

Click the down-arrow to the right of the date to open the drop-down calendar. Use the left and right arrows to select the month in the drop-

down calendar, then select a date by clicking it. Today’s date is circled in red. Click Add to add the date in the date box to the list of

holidays. To remove a date from the list, select the date and click Remove. Click OK once you have speciﬁed all the days you want to

prevent the action from executing.

6. Scheduled action: Click Edit to deﬁne the scheduled action. The Edit Script dialog box opens. Type the script actions directly into the

Action column, or use the script wizard to help you write the script. For more information on writing scripts, refer to Scripts and

Expressions.

A schedule’s script runs on the client of any operator speciﬁed in the schedule’s recipient group, provided the client is running and the

operator is logged in when the script executes. If the client is not running or the operator is not logged in, or if no recipients are speciﬁed in

the schedule, VMX300(-E) runs as much of the script as possible, namely, statements that do not require a recipient, such as a statement

that sets the value of a device property.

7. Priority: Enter the priority with which the schedule’s activities are to be treated by the server. VMX300(-E) uses priorities to resolve

situations in which two or more objects attempt to control a particular device at the same time. The object with the higher priority number

is given control of the device. The highest priority you can assign to an object is 99. The lowest is 1. System events have priority 100. Users,

schedules, and alarms and events all have a priority. The scripts associated with these objects inherit the object’s priority.

8. Recipients: Select the recipient group you want notiﬁed when the scheduled action executes. Recipients are only notiﬁed if they are

logged in to the client when the scheduled action executes.

Specifying recipients also determines which clients the schedule’s script runs on. A schedule’s script runs on the client of any operator

speciﬁed in the schedule’s recipient group, provided the client is running and the operator is logged in when the script executes. If the client

is not running or the operator is not logged in, or if no recipients are speciﬁed in the schedule, VMX300(-E) runs as much of the script as

possible, namely, statements that do not require a recipient, such as a statement that sets the value of a device property.