Interpage Z-500 Series, Manual

Page: 31 / 57

The Operational Modes available for paging using the TAP Paging Protocol include:

System Identification Command

Paging Session Login

Paging Operation

Paging Session Logout
SYSTEM IDENTIFICATION COMMAND
The System Identification command allows installation programs and other software applications to poll serial ports for the
existence of an
InterPage Z-500 Series Paging Encoders using the Standard ATI Command. This can be used for a
supervised process (also called keep-alive) where the host system periodically polls the paging system for a response.
When the InterPage paging transmitter recognizes a command formatted as
ATI<CR> , the transmitter responds with the
following message:
InterPage Paging Encoder v8.01<CR>
(The firmware version number is subject to change)
PAGING SESSION LOGIN
The Z-500 Series Paging Session Login mode allows a Host Device , sometimes called a Remote Entry Device, to initiate
communications with the paging system. With the InterPage Z-500 Series Paging Systems , the Login process is optional.
The InterPage Z-500 Series Paging Systems will automatically login a Host Device and process the paging message if it
recognizes a properly formatted TAP message block at any point in its operation.
The Host Device initiates the Login process by transmitting a carriage return <CR> character every two seconds until the
paging system properly responds or until the Host Device times out and notifies the operator of a bad connection. The
paging system will respond with
“ID=<CR>” (Note: the quotation characters are used here only for reference and are not
included in the transactions). The “ID=<CR>” will not be repeated or timed out by the paging system.
The Host Device should respond to the paging system with:
<ESC>PG1<CR> or <ESC>pg1<CR>
The InterPage Z-500 Series Paging Systems will then respond with:
110 1.8<CR>InterPage Paging Encoder v8.01<CR><ACK><CR>
The “110 1.8” message indicates that the system conforms to TAP specification version 1.8 and should be backward
compatible with earlier TAP implementations. The paging system then notifies the Host Device that it is ready to accept
messages as follows:
<ESC>[p<CR>
This completes the Login process.
Tap Interface Specifications Continued on next page…