RTC
®
5 PC Interface Board
Rev. 1.9 e
6 Developing User Applications
81
Other than that, the same rules as for indexed
subroutines are applicable (see "Indexed Subrou-
tines", page 76 and "Subsequent Protection and
Conversion of Non-Indexed Subroutines", page 78).
Notes
•The set_char_table command is synonymous
with the set_text_table_pointer command.
Calling Indexed Text Strings
Indexed text strings can be called for marking times,
dates and serial numbers via the commands
mark_time, mark_date and mark_serial (or the
“AbsCall” commands mark_time_abs,
mark_date_abs and mark_serial_abs) (see "Marking
Dates, Times and Serial Numbers" on page 150).
Management of Indexed Characters and Text
Strings
The RTC
®
5’s management of indexed characters
together with the management of indexed text
strings occurs via one internal management table
maintained separately from the internal index
management of indexed subroutines.
Index management by the user (renumbering,
copying, …) resembles index management of
indexed subroutines (see "Index Management and
Defragmentation" on page 79) using the commands
copy_dst_src, load_char, load_text_table,
get_char_pointer, get_text_table_pointer and
save_disk/load_disk. Defragmentation of the
protected buffer area also includes indexed char-
acters and text strings.
6.5.3 Jumps
The list_jump_pos (see page 319) (synonymous with
set_list_jump) and list_jump_rel (see page 321)
commands allow the definition of runtime jumps by
the RTC
®
5 to a specified address.
With the list_jump_pos command, an absolute
memory address within the configured list area
(“List 1” and “List 2”) can be specified. Jumps within
or out from the protected buffer area (“List 3”) are
not allowed with these commands. Any
list_jump_pos command having such an unallowed
jump address will be ignored during execution.
With list_jump_rel, jump widths (i.e. relative
memory addresses) can be specified. This command
can be used in all memory areas, even the protected
buffer area (“List 3”). Nevertheless, when specifying
jump addresses, you should be sure the jump does
not exceed the boundary of the corresponding
memory area. Otherwise, the RTC
®
5 will ignore the
command during execution. If the command is used
in an indexed subroutine, you must further ensure
the jump does not exceed the subroutine’s bound-
aries. During processing of indexed subroutines,
relative jumps that exceed a subroutine’s boundaries
will be ignored by the RTC
®
5.
Notes
• Reconfiguration of the list memory or conversion
of a subroutine can result in an originally-valid
jump address becoming invalid due to new list
boundaries or an altered subroutine position in
the memory. In this case, the RTC
®
5 ignores the
corresponding jump command – hence, the
program will probably no longer function as
intended. Therefore, exercise care when
programming jump commands.
• When conditional jump commands are used,
execution of a jump is dependent on an external
control signal (see "Conditional Command
Execution", page 213).
• Jump commands initiating a jump to themselves
as
list_jump_rel( 0 )
will be ignored at runtime
to prevent an infinite loop that excludes further
activities.
On the other hand, conditional jump commands
as
list_jump_rel_cond( Mask1, Mask0, 0 )
are
allowed, e.g. to wait for confirmation of a signal.
To Next Page
Loading...