Section 7. Quick Reference
7-23
CUSTOM STACK MEMORY REQUIREMENT WORKSHEET
As a general approximation the Custom Stack feature has a capacity of ten pager capcodes per
stack. If your application requires more than ten pages in a single series, then you can put the
capcode of another fixed stack in the last position and the next stack will follow the first
without interruption. However, because the actual capacity of the stack is controlled by
memory usage, there can be instances where the capacity of a fixed stack is more (or less!)
than ten capcodes, based on the size and number of capcodes actually entered. This worksheet
will help the installer determine whether or not all the pages desired can fit into a single stack.
The worksheet requires that you enter the number of digits required to enter each pager’s
capcode. This includes the leading digit that selects the format block. In the example shown,
the stack consists of five Two-Tone pages from a leading digit set up for a 1000-call code
plan (thus requiring three digit capcodes) and five DTMF pages from a leading digit set up for
five digit capcodes.
Pager
Position
Pager Capcode
Pager
Position
Pager Capcode
1
4 + 1 = 5
1
+ 1 =
2
4 + 1 = 5
2
+ 1 =
3
4 + 1 = 5
3
+ 1 =
4
4 + 1 = 5
4
+ 1 =
5
4 + 1 = 5
5
+ 1 =
6
6 + 1 = 7
6
+ 1 =
7
6 + 1 = 7
7
+ 1 =
8
6 + 1 = 7
8
+ 1 =
9
6 + 1 = 7
9
+ 1 =
10
6 + 1 = 7
10
+ 1 =
Total
60
Total
The maximum total allowed for a single fixed stack is 67. As the example on the left shows,
there is actually room in the stack memory for one more pager of either format.
Please remember
that when you enter a POCSAG pager capcode into the stack, you must
follow it with a message entry in the next capcode slot, and that this also consumes stack
memory resources. The position with a “NULL” message in it would be valued as “1 + 1”.
