33
Detail Programming Macro Commands Continued
Each Event uses two lines of the display to view. The left side is a short description of
the event and each top line is labled N1 N2 N3 N4 N5 N6 N7 N8 N9 N0 (N0 is actually N10).
Of course you can't see all the numbered commands in one view so scroll across using the
"0" key. It will wrap back to start after the last number is shown. Directly under the "N"
is the actual Macro Command and should initially all be set to "00" as the Resume Command.
To Set a Macro Function
using command
#5
:
#5 01*11*22*33#
Set Event Line-01 with commands 11,22,33, terminate.
#5 01#
Clear Event Line-01 by setting whole line to "00"s.
Here is a sample for setting up a two code function being required to Grant Access:
Program:
1) On Entry Code validated: <Set Switch 1 On><Set 4 Seconds on Timer><Discontinue>.
2) On Special-1: <And Switch 1 On><And Timer Clear><Clear Switch 1><Resume>.
3) On Card-1 Valid: <And Switch 1 is Off><Discontinue>.
Explanation:
1: Sets Switch-1 for a valid Entry Code, starts a Timer, but stops short of Entry Granted.
2: Is always checking Switch 1 and clears it anytime that the Timer expires. (clean up)
3: If Card-1 is Access Valid but Switch 1 was off then the Card-1 Valid is cleared only.
Thus a valid Card-1 Access can only be processed within 4 seconds of a valid Entry Code.
Ok.. you want a simple example? Here goes:
1) On Ajar-1 Input Active (Event number 4): <Cycle Relay-1> (Macro command 15)
Thus a simple contact closure on Ajar-1 input will Gate Cycle the Relay-1.
Programming example of the simple sample above:
Good and simple, this command does the basic job:
#5 04*15#
Better yet simple, this command includes a Audio Request to Enter but leaves the audio on:
#5 04*15*85*48#
Best, same as above, but cleans up after itself after the message has played.
#5 04*15*85*48*03*07#
Note: This procedure method just above doesn't activate until the Ajar-1 event concludes.
A work-around would be more complex and use Event-24 starting with Command-62 but the
following commands would have to form a procedure to stop the message from restarting the
whole time while the Ajar-1 input is active.
Note: The above sample may appear to provide a method for gate access but be aware that
the system doesn't know why you did this. Was it for Access or a Camera Enable? Thus the
access event isn't placed in the Audit Log. We have not provided you with the ability to
force a logged entry because a mistake in programming could fill up the log memory real
fast. The commands we do allowed you to have can't harm the system. They might tie it into
programming knots and loops but they can't harm it.
Note: Don't do this "#5 24*07#". This Macro sequence could normally lock up part of the
system. However, we do trap for high frequency reset commands (07) to reduce such risks.
Summary of Contents for Uni-2010
Page 38: ......