Table of Contents
Advertisement
Chapter 9. Diagnostics
9.6.1
DLB Operation
DLBs are created as components of a specific Target and are
separate from the application logic block components
associated with a target.
They are written in LD programming language and support
many of the same features, such as View Lock, Edit Lock, etc. as
other block types.
A target can have a maximum of 128 DLBs in a given PME
target. Each DLB can have associated published variable table
(PVT) and cam profile (used with Motion applications) files. Each
DLB can use up to 128K bytes of memory.
A DLB can be copied and pasted like other blocks. Regardless of
where a DLB is pasted, normal conflict handling is applied.
An active DLB can be dragged to the Toolchest, to folders under the Active Blocks node, or to
folders under the Program Blocks node. Note that only active blocks can be dragged. Downloading,
executing, or modifying a DLB does not affect the equality of the main logic program.
Suspend I/O Function and DLBs
The Suspend I/O (SUS_IO) function operates the same in a DLB as it does in application logic. Both
application logic and DLB logic execute in the CPU Sweep Logic window. Therefore, when a
SUSPEND_IO is executed by either the application or the DLB, outputs are held current during the
output scan that occurs immediately after the Logic window finishes its execution, and input
references will not be updated from inputs during the input scan that occurs immediately before the
Logic window is executed in the next CPU sweep.
Note that a SUSPEND_IO only affects normal I/O scans. It does not affect I/O scanning that is done as
the result of DO_IO or SCAN_SET_IO functions that execute in application or DLB logic. SUS_IO has
the same effect whether it is executed once in a sweep or multiple times in a sweep.
444
PACSystems* RX7i, RX3i and RSTi-EP CPU Programmer's Reference Manual
Figure 22: Diagnostic Logic Blocks
(DLBs) assigned to Target in MPE
GFK-2950C
Advertisement
Table of Contents
