5-10
RLC-4 V1.79 Copyright © 1998 Link Communications Inc. 9/18/98
Blocking Execution from Certain Ports
Purpose of these commands:
The following three commands allow you to mark certain commands so that they can not be
executed from certain ports. You might want to use this command to make it so your autopatch
can not be accessed from the link ports. If you are using one of the ports as a control port, you
could make all of the commands in the controller so they could only be executed from that control
port. This adds a lot of security to your controller.
Caution:
Because these commands can keep you from executing commands, they can lock you out of your
own controller. If you have a terminal or computer hooked up to the serial port, these commands
can not lock you out, so you don't have to worry about it. Also, you can always re-initialize the
controller (see Appendix D), but that erases all of your programming and you have to be at the site
to do it. In other words, be careful what commands you block and what ports you block their
execution from. If you don't want to use these functions and you want to erase their names so that
they can not be entered accidently, enter the following commands:
010 130 <unkey>
010 131 <unkey>
010 132 <unkey>
These commands erase the names of command numbers 130, 131 and 132 so that they can not be
executed without renaming them to a valid name.
If you think you have locked yourself out, execute the following sequence of commands from every
port you can get touch tones to, or from the serial port. If they are executed they will allow access
to every command from every port.
131 1 000 249 <unkey>
131 2 000 249 <unkey>
131 3 000 249 <unkey>
131 4 000 249 <unkey>
To Next Page
Loading...
Need help?
General
