EasyManua.ls Logo

GSE 574 - Page 161

Default Icon
339 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Model 574 Programmable Counting System (PCS)
142 - GSE Scale Systems
Macro Call Commands.
If a setpoint invokes a macro while another macro is in
process, the newly invoked macro is "pushed" onto a
macro stack (ie the fact that it needs to be executed is
noted). When the currently executing macro is
completed then the "pushed" macro is executed. The
macro stack allows for up to 16 macros which are
awaiting execution to be tracked by the 574. If more
than 16 macros are invoked the message "Macro Error"
will be displayed. All macros awaiting execution and the
currently executing macro will be canceled.
When one macro "calls" another macro, the calling
macro's next command is "pushed" onto the macro stack.
This is how the place where execution is to resume is
noted by the macro. However it is necessary to not use
multiple "nested" macro "calls" (in excess of 15) in order
to prevent overflowing the macro stack.
A macro invoked by an alarm or a setpoint while another
macro is in progress is noted and that macro will be
executed once the macro(s) in progress are completed. A
macro being invoked by a remote key will be ignored if
another macro is running. If the currently running macro
attempts to accept operator (using one of the designated
commands) then the remote key input will be ignored
and discarded. However if the running macro completes
execution without checking for operator input, then the
remote key will be processed at that time. Any macro
can be invoked when any setpoint is activated and / or
deactivated. he "menu" option allows any macro that has
been named to be invoked through a menu using the
<ID> key.
Naming Macros and the Macro Menu
Macros may be named. If a macro is named, that macro
can appear in a menu which allows an operator to invoke
one of the named macros through the unit's front panel, if
setup parameter P720 is set to "Menu".
Macros are named starting at P850 for macro 0 and
continuing through P866 for macro 16. The method of
naming is exactly the same as that for naming the IDs, ie
P701 - P711.
To make use of this feature, first name all of the macros
which will need to be invoked by the operator. Use a
name that will be meaningful to the operator of the unit
and that will look good on the two line by five character
display. If an entry is expected of the operator at the
time that the macro is invoked, make sure the name
suggests that an entry be made. Also make sure that P720
is set to "Menu".
Then, when the operator is using the scale, press the
<ID> key to display the name of the first named macro.
Then, if necessary, press the <SELECT> key to advance
the menu selection to the next named macro. When the
required selection is displayed, press the <ENTER> key
to invoke that macro or if the macro is written to accept
an entry, key in the data prompted for and then press
<ENTER>.
In order for a macro to accept operator input when it is
invoked, it must be written appropriately. Keying in
some data and pressing <ENTER> at the macro merely
causes the data to be placed in the unit's entry buffer.
Then the first command in the macro will simply act
upon the information in the entry buffer. For instance if
the macro started out with "80%s" to select var #0 and
the operator had pressed "123 <ENTER>" to invoke the
macro from the menu, then the 574 would attempt to
execute "12380 <SELECT>". This would bring up the
"Setup Keyin Code" prompt as the 574 attempted to
access the setup mode. This is not at all what was
intended!
If the macro does not require operator input when it is
invoked, it is recommended that the entry buffer be
cleared in some manner at the very beginning of the
macro. This will prevent a macro from executing
erroneously if an operator does make an entry.
Example 1: (used as the very first entry in a macro
named "Keyin Targt"):
;80%C Copy entry into Var #0. If no entry is
made, Var #0 is cleared.
Example 2: (same as above except requires
operator input):
%\ IF NO ENTRY
Keyin Targt%G Re-prompt operator.
0%^ Re-start this macro (macro 0)
%E END IF
;80%C Store entry in Var #0.
Example 3: (when operator input is not required):
1%c Start an entry (in case entry not in
progress), then clear entry.
16.3 Methods of Aborting Macros
In the event that a macro is aborted by the user pressing
<CLR> + <SELECT> simultaneously, sometimes it is

Table of Contents