8
Basic Programming
In this section we will review the basics of programming the unit via touch tone or via
local keypad.
Touch Tone programming the unit obviously requires the unit to be powered and connected to
a phone line that can be called. Even if the unit has a Modem installed, you are given a
brief opportunity to use touch tones. Simply wait for the unit to answer a call placed to
it. It will play a brief answered melody. You have about 6 seconds to send a touch tone
command before the Modem switches on. This allows you to latch or unlatch a gate control
or put the unit into programming mode. Any touch tone command will suspend the unit from
going into modem mode. Once the unit has answered, enter the code *2468 to enter
programming mode if desired.
On a residential dialer you may have to push the call button first for a simulated dial
tone. Then enter: *2468 command sequence to enter the programming mode. Units with
displays use the "*" key in the directory browser routines so the Call Button is required
first.
You will get a two tone sequence that is made every time you finish something correctly.
Programming commands fall into 3 categories.
Commands that start with a number follow a format much like our one button dialers.
Commands that start with a "#" key follow a format much like our residential dialers.
Commands that start with a "*" key are new and used to display or transmit data.
All commands that start with "*" are harmless. Do not use these commands via touch tone
programming because the data is almost worthless without a tone decoder. Also, you run the
risk of getting lost in the remote programming sequences.
All commands are entered as a sequence of digits that may include additional "*#" tones.
When the command is fully entered, use the "#" tone or key, to terminate the command.
If the command is understood you will hear that familiar two tone acknowledgment.
If the command was faulty, you may hear a long single tone that indicates an error was
made on your part in either format or function requested.
A typical function error will be generated if you try to load a number into a position
that doesn't exist, such as installing a card code to a database that is not enabled. In
this case it is a legal documented command that can't be performed.
A format error is produced by installing a 7 digit entry code when entry codes are
restricted to 6 digit lengths.
Refer to Page 1 for a quick summary of all generic commands.
Refer to the specific detailed pages for commands when the quick summary hasn't enough
detail to correctly enter your data. Also, many commands have subsets and variations that
allow more explicit abilities. For example a command may be used to drop a value into the
first empty position. But given there might be 8 available positions to place this value,
you might need to be more specific. So it's always a good idea to check the details on any
given command. You might even see that some commands have cool shortcuts that could save
time in loading data.
The "*" command is great for those with display units during keypad programming. All
variables and data can now be displayed and browsed through.
Also, from the keypad, if you think you might have messed up: Just hold down the "*" key
for 3 seconds. It will send you the dual ack-tones indicating the command was aborted.
Exit the programming mode with two "#" keys in sequence.
To Next Page
Loading...