Scanlab RTC 5 PC Interface Board Installation And Operation Manual page 530

Normal time_fix_f_off
List Command
Function stores in a buffer the current time and date of the RTC
date and time for use with
Call
time_fix_f_off( FirstDay, Offset )
Parameters
FirstDay
Offset
Comments • Before calling time_fix_f_off,
and PC time should be performed (at least once after each load_program_file) via
time_update.
• The complete time can be marked through multiple calls of
complete date through multiple calls of mark_date. The commands time_fix_f_off,
time_fix_f
that the to-be-marked time or date won't change during marking.
• If time_fix_f_off,
marking, then the last marked time will be marked again. If time_fix_f_off,
or time_fix
of January 1, 2000 will be marked.
• If Offset = 0, then the current date and current time are fixed. One practical use of
forward dating (Offset > 0) is for setting a date of expiry based on the current date.
Backdating (Offset < 0 ) isn't possible.
® ®
RTC 4 RTC 5 new command
Version info Last change with version DLL 524, OUT 526
References time_fix, time_fix_f, time_update, mark_time,
Ctrl Command time_update
Function sets the RTC
Call
time_update()
Comments • The RTC
command must be called after each
and calendar are to be calibrated.
• The base value for internal time counting is set to January 1, 2000, 00:00 by
load_program_file
counter is set to 0 via
the quartz-controlled 10 µs clock.
• Before marking with
time_fix_f_off
the current value of the internal seconds counter) and formatted.
® ®
RTC 4 RTC 5 unchanged
(the command was previously only available for the RTC
standalone version of the RTC
References time_fix, time_fix_f, time_fix_f_off, mark_date,
®
RTC 5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
mark_date
This parameter (an unsigned 32-bit value) defines the starting number for
determining the Julian calendar day from the current date of the RTC
calendar:
Counting proceeds from FirstDay to FirstDay + 364 (+1 for leap years).
forward dating in seconds (as an unsigned 32-bit value);
allowed range: [0 ... (2
time_fix_f
or time_fix must therefore be called before these marking commands so
time_fix_f or time_fix
aren't called at all after a load_program_file, then a time of 00:00 or a date
®
5's 24-hour clock and calendar to the current PC time.
®
5 board's clock doesn't contain a battery backup. Therefore, the time_update
whereas to the PC time by time_update. An internal seconds
load_program_file
mark_date or mark_time, you must call time_fix,
so that the current time can be captured (as sum of the base value and
®
4 board)
®
clock/calender or a forward-dated
and mark_time.
32 –
1)]
or time_fix, synchronization of the RTC
mark_time
are not called again before a time or date
mark_date
load_program_file if the RTC
or via time_update, but is always driven by
®
SCANalone Board, i.e. the
mark_time
®
®
5
and the
time_fix_f
®
5's 24-hour clock
time_fix_f or
530