Section 5. Programming
5-34
When a fixed stack page is executed, the encoder starts at the beginning of the string and
reads the characters as though they were being entered from the keypad. If the format
programmed for a particular leading digit requires more digits than you supplied when you
programmed that position in the stack, then the Model 15P will “borrow” the necessary digits
from the next capcode in the stack. This will result in several possible failure modes for this
stack page:
x
The page that was short a digit or two will still go out, however, it will not call the
decoder you intended it for because the final digits came from the next capcode position.
At a minimum this page in the stack is wasted.
x
The encoder moves on to the stack position that follows the “short” capcode. If the “new”
leading digit (the next digit after the ones that were borrowed) does not point to a
programmed format, then the encoder treats it as a bad entry and moves on to the next
digit and tries it as a leading digit, and so on. That means that this page in the stack is lost
as well.
x
If the “new” leading digit does point to a programmed format, then the encoder will look
for enough digits to make a page. This page will also be a waste, since it isn’t for any of
the pagers you intended. Worse yet, if it requires more digits than remain in this capcode
position, it too will borrow from the next position, passing the failure on down the stack.
Just how much damage a bad capcode entry can do to a stack page is determined in part by
where it occurs in the stack. If it occurs in the last position, the single page is lost. If it occurs
a few pages from the end, then you can lose everything from there to the end. If it occurs
early in the stack, it can possibly sabotage the entire stack.
It should be obvious at this point that there are some precautions you should take whenever
you are going to be programming fixed stack pages under the Custom Stacks format. In order
of importance they are:
1. D
O ALL OF THE PROGRAMMING TO SET UP THE INDIVIDUAL PAGING FORMATS FIRST
.
This is necessary to define exactly what the valid capcode entry is for each of the pagers
or decoders being used. If possible, try each of the pages manually and record the leading
digit + capcode string necessary to set off each unit.
2. S
TRAP CAPCODE DIGITS AND FUNCTION CODES
.
Whenever possible in the programming of individual formats, strap as many of the
capcode digits as the format will allow. This includes function codes as well. (If an
operator would have to key in the function code when making a manual page, then the
programmer must do so when entering the same capcode into a stack.) This provides two
benefits. It makes manual entry of individual pagers easier by reducing the number the
operator must key in. It also increases the number of pagers that can be programmed into
a single stack by reducing the digits added to the fixed stack string.
3. A
LWAYS SUPPLY A MESSAGE
(
OR TURN THEM OFF
).
If the stack you are programming includes capcodes for one of the display paging