RFC-1 Advanced Operation page 6.32
Looking at the Programming address table, the date/time triggers appear to be numbered backward. As the address
increases—the normal direction for programming—the number of the date/time trigger decreases. This is not a
mistake. The numbering is consistent as the date/time triggers transition into shared memory. This selection from
the Programming Address Table highlights the transition—notice the Alternate Use column. See section 6.7.4 for
more information on allocating memory for date/time triggers.
- Programming -
Addr Description Section Default Current Alternate Use / Notes
0248 Channel 62: telemetry units or status format - value 1 6.3.2 0 ____ Date/time 49: action sequence
0249 Channel 62: telemetry units or status format - value 2 6.3.2 3 ____ Date/time 49: month
0250 Channel 62: full scale and decimal point 6.3.4 2 ____ Date/time 49: date - value 1
0251 Channel 62: linear/log/indirect and auto relay 6.3.5 0 ____ Date/time 49: date - value 2
0252 Channel 63: telemetry units or status format - value 1 6.3.2 0 ____ Date/time 49: hour - value 1
0253 Channel 63: telemetry units or status format - value 2 6.3.2 3 ____ Date/time 49: hour - value 2
0254 Channel 63: full scale and decimal point 6.3.4 2 ____ Date/time 49: minute - value 1
0255 Channel 63: linear/log/indirect and auto relay 6.3.5 0 ____ Date/time 49: minute - value 2
0256 Date/time trigger 48: action sequence 6.7.4 0 ____ Alarm block 48: block indicator
0257 Date/time trigger 48: month 6.7.4 0 ____ Alarm block 48: alarm to block
0258 Date/time trigger 48: date—value 1 6.7.4 0 ____ Alarm block 48: month
0259 Date/time trigger 48: date—value 2 6.7.4 0 ____ Alarm block 48: day(s) of week
0260 Date/time trigger 48: hour—value 1 6.7.4 0 ____ Alarm block 48: start hour—V1
0261 Date/time trigger 48: hour—value 2 6.7.4 0 ____ Alarm block 48: start hour—V2
0262 Date/time trigger 48: minute—value 1 6.7.4 0 ____ Alarm block 48: end hour—V1
0263 Date/time trigger 48: minute—value 2 6.7.4 0 ____ Alarm block 48: end hour—V2
6.7.4 Programming a Timed Event
A timed event is a combination of two things: a date/time trigger and an action sequence. The date/time trigger
contains all data for when the event will occur but not what happens. The action sequence holds the instructions that
are executed but it contains no timing information whatsoever. This results in a system that is both flexible and
efficient.
• the first memory location identifies the action sequence to trigger
• the second memory location store the month in which to trigger
• the third and fourth memory locations store the date or day of week on which to trigger
• the fifth and sixth memory locations store the hour at which to trigger
• the seventh and eight memory locations store the minute at which to trigger
Program a single digit 1-8 for the number of the action sequence that the date/time should trigger.
Program a month from 1 to 12. It is okay to program a two-digit month in this location—enter both digits the press #
to write a month value larger than 9. Program the value 15 to have the trigger activate every month.
The date setting uses two memory locations. Program the first digit of the date in the first location (V1) and the
second digit of the date in the second location (V2). Use 0 for the first digit (V1) if the date is below 10. Program the
value 15 at both locations to trigger an event every day of a month.
The hour setting uses two memory locations. Program the first digit of the hour in the first location (V1) and the
second digit in the second location (V2). Use a 24-hour clock. Program a 0 for the first digit if the value is below 10.
Program the value 15 at both locations to trigger an event every hour of a day.
The minute setting uses two memory locations. Program the first digit of the minute in the first location (V1) and the
second digit in the second location (V2). Program a 0 for the first digit if the value is below 10.
Special codes that provide other triggering options are described below.
To Next Page
Loading...
Need help?
General
