Extended instructions
8.4 Interrupts
S7-1200 Programmable controller
338 System Manual, 03/2014, A5E02486680-AG
Table 8- 96 Data types for the parameters
OB number (accepts symbolic name)
SDT IN DTL Start date and time: Seconds and milliseconds are ignored and can be
LOCAL IN Bool 0 = Use system time
1 = Use local time (if the CPU is configured for local time, otherwise
PERIOD IN Word The period from the starting date and time for recurring interrupt event.
• W#16#0000 = Once
• W#16#0201 = Every minute
• W#16#0401 = Every hour
• W#16#1001 = Daily
• W#16#1201 = Weekly
• W#16#1401 = Monthly
• W#16#1801 = yearly
• W#16#2001 = End of month
ACTIVATE IN Bool 0 = ACT_TINT must be executed to activate the interrupt event.
1 = The interrupt event is activated.
Your program can use SET_TINTL to set a date and time of day interrupt event that will
execute the assigned interrupt OB. The start date and time is set by parameter SDT and the
time period for recurring interrupts (for example, daily or weekly) is set by parameter
PERIOD. If you set the repetition period to monthly, then you must set the start date to a day
from 1 to 28. The days 29 to 31 may not be used because they do not occur in February. If
you want an interrupt event at the end of each month, then use end of month for parameter
PERIOD.
The DTL data weekday value in parameter SDT is ignored. Set a CPU's current date and
time using the "Set time of day" function in the "Online & diagnostics" view of an online CPU.
You must set the month, day of month, and year. STEP 7 calculates the interrupt period
based on the CPU date and time clock.
Note
The first hour of the day does not exist when changing from summer to winter (daylight
saving time). Use a start time within the second hour or use an additional time delay interrupt
within the first hour.
To Next Page
Loading...
