Unprotecting Subroutines - Scanlab RTC6 PCIe Board Installation And Operation Manual

• If using method 2, you should use it fully. If the
set_sub_pointer alone is executed, then the
subroutine is already callable by
index, but the subroutine remains unprotected
against overwriting. Protection is obtained only
after the subroutine is subsequently copied as an
indexed subroutine by
the protected RTC6 List Memory
• save_disk ignores all non-indexed subroutines,
even those subsequently protected in the
protected RTC6 List Memory
method 1. Be aware that they can be overwritten
there by load_disk.
save_disk/load_disk
• automatically replaces
unallowed commands (for example,,
set_end_of_list) with
• Indexed subroutines repeatedly indexed with
copy_dst_src are duplicated in the
Memory at a subsequent save_disk/load_disk.
This can result in a memory overflow in the
protected RTC6 List Memory
• Before executing load_disk, be sure the
protected RTC6 List Memory
sufficient size after configuration of "List 1" and
"List 2" (save_disk returns the number of stored
list commands). An indexed subroutine is not
load_disk
stored by if there is not sufficient
memory.
• Conversion of a subroutine by method 2 changes
the absolute memory address of the subroutine.
RTC6 boards
Doc. Rev. 1.0.21 en-US
6 Developing RTC6-User Programs
sub_call and its
save_disk/load_disk into
area "List 3".
area "List 3" by
list_nop commands.
RTC6 List
area "List 3".
area "List 3" is of

Unprotecting Subroutines

The protection of a subroutine stored in the
protected RTC6 List Memory
if it is assigned by config_list
Memory area "List 1" or "List 2".
The subroutine can then still be called using the same
parameters (index or absolute memory address). But
it no longer has protection against unintentional
overwriting.
area "List 3" is removed,
to one of the RTC6 List
117