User's Manual

Internal Encoding

RFI-148 & RFI-900 High Output Power Paging Transmitters User Manual Page 39 of 134

6.3 Protocols Supported

All protocols are accessible through either the rear serial port or the Ethernet port via TCP or UDP port 64250.

6.3.1 TNPP

The RFI PTX supports the ETE REQ and CAP PAGE block types. The TNPP station address is configurable.

6.3.2 PET

The RFI PTX supports the PG1 and PG3 page submission types. Note that the page “zone” for PG3 has no

effect on the RFI PTX and it only accepts this value for backwards compatibility. Also accepted is a password

up to length 6 characters. The password is not checked and also exists only for backwards compatibility.

There are several options available to allow for differences in PET implementations:

• Line Separator: The RFI PTX can print either a carriage return (<CR>) or a carriage return and line

feed (<CR><LF>) for line separation. Note that the RFI PTX only accepts lines separated by <CR>.

• Timeout: The timeout while expecting the next command string is configurable. The RFI PTX starts a

timer when it is expecting more data. If the timeout expires the RFI PTX PET parsing returns to either

the Idle or Logged In state.

• Baud Rate: Due to PET not having a way to submit baud rate with page messages, the baud rate must

be pre-configured. Standard POCSAG baud rates of 512, 1200, and 2400 are supported.

• Stay Logged In: This option allows the RFI PTX to remain in the Logged In state (ie, after the PG1

and password sequence) so messages can be submitted without having to handshake the connection

each time. This option can be used in conjunction with Implied Login to skip handshaking altogether.

• Implied Login: If the <STX> character (the start of a message submission) is sent to the RFI PTX this

option allows the RFI PTX to transition directly to message submission state and skip the login

handshaking.

• Detect Numeric Pages: Encode a paging message as numeric if all characters within the message fit

the numeric encoding scheme (ie, all characters are any of the following: '0', '1', '2', '3',

'4', '5', '6', '7', '8', '9', '!', 'U', ' ', '-', ']', '[').

6.3.3 TAP

The TAP protocol is treated the same as PET, however with some extensions:

• Group Code: The RFI PTX can be configured to accept a group code that trails the pager ID during a

message submission. The group code can be ‘A’, ‘B’, ‘C’, or ‘D’ when set for “Trailing Character”, or

‘1’, ‘2’, ‘3’, ‘4’ when set to “Trailing Digit”.

Paging Protocols -> Encoding Mode

Paging Protocols -> TNPP

Paging Protocols -> TAP/PET

Paging Protocols -> Page Datagram