Instruction manual

Troubleshooting and Repair
025-9416 133
Example Valid Entries Description
N N = numeric
A = alphanumeric
B = beep (tone-only)
Page class
A A = 1 B = 2
C = 3 D = 4
RF channel designator
@
A = 1 B = 2
C = 3 D = 4
RF zone designator (same as channel designator)
C 1 - F Page function code - 1 hex digit
00400672 5 - 7 digit capcode with leading
zeros (hex F indicates 5/6-tone)
Pager capcode - always 8 ASCII characters
replaces
capcode
20 - FE hex Identifier - customer ID, always 10 ASCII characters
98888005 depends on pager type Message - variable length
♥
constant value
ASCII value 03 or ^C
End of text (ETX) character
Traffic Command
The traffic command provides another way to troubleshoot individual TNPP pages. The
command is available from the plus prompt (+) and identifies the status of each page sent and
received by the Model 640.
Table 26 shows the TNPP packet responses provided by the traffic command, what they mean,
and some solutions to failed pages.
Table 26. Outbound TNPP Page Responses
TNPP
Response Description Solution
ACK Acknowledge - the packet was received
by the destination node.
The page was successful.
No solution required.
CAN Cannot acknowledge - the destination
node did not recognize the node ID or
did not like something about the page.
The page failed.
Double check the destination node ID.
Ensure that the information in the TNPP
packet is valid: capcode or pager ID, page
class, page type, etc.
NAK No acknowledge - the page was not
properly received by the destination
node.
The page failed.
Check the RF link for excessive noise and
proper configuration and connections.
Ensure that the information in the TNPP
packet is valid: capcode or pager ID, page
class, page type, etc.