[50]
EXAMPLE 1:
AN0046180DThis is a test<CR>
This sends the message “This is a test” at 512 bps to an alphanumeric pager with Cap Code 0046180.
(
Note:
The POCSAG alphanumeric character set is the entire ASCII 7 bit character set
.)
EXAMPLE 2:
NN0765155B412-3433<CR>
Will send the message “412-3433” at 512 bps to a numeric pager with Cap Code 0765155.
(
Note:
The POCSAG numeric character set allows Hyphen ( - ), space, left bracket ( [ ), and right bracket ( ] )
.)
EXAMPLE 3:
AF0145678C<CR>
Will send a three beep tone only message at 1200 bps to a pager with Cap Code 0145678 and multiple tone
cadence capability. Certain paging receivers aren’t designed to respond to multiple tone cadence messages.
RESPONSE TO ALL COMMANDS
RESPONSES TO PAGING MESSAGE COMMANDS COME IN THE FOLLOWING FORMATS:
Page Queued Okay<CR><LF>
The Page Queued Okay response is sent by the paging encoder to the host system immediately following a
command if the command was understood by the paging encoder.
FOLLOWING ARE SOME EXAMPLE ERROR MESSAGES OUTPUT WITH SCOPE PROTOCOL:
•
Error – Invalid Pager ID<CR><LF>
•
Error – Invalid pager type. Expected A or N<CR><NAK><CR><LF>
•
Error – Beep code invalid. Expected A,B,C,D<CR><NAK><CR><LF>
NEGATIVE ACKNOWLEDGEMENT
<NAK> | 21 – indicates the refusal of a host device command
due to errors or bad formatting.
