
2 Configuring PAD/ATPAD Ports
About Packet Assembler/Disassembler
About Packet Assembler/Disassembler
What is a PAD?
A Packet Assembler/Disassembler, or PAD for short, gives you network access and
ensures compatibility between different hosts and terminals and a packet switched
network. A PAD does this by packetizing data (Assembling), sent to the PAD from a
terminal device, and then routing that packetized data through a packet switching
node and onto the network.
A PAD can also ‘depacketize’ (Disassemble) data before it is sent to its intended
destination (host or terminal).
What Is a PAD
Port?
A PAD port lets you transmit asynchronous data. When setting the Port Type to PAD,
the remainder of the Port Record will contain only those parameters needed for
configuring the PAD port.
In this record, you can configure a PAD port for:
• Autocalling
• Autospeed
• Address blanking
What is an ATPAD
The ATPAD is an asynchronous port that lets you make and clear X.25 calls using a
restricted set of Hayes AT commands.
Features
PAD ports provide these features:
• A set of commands to make and clear calls
• A set of response codes that indicate the generation condition
• Other features such as configurable control characters, data forwarding
criteria, and answer mode for tailoring the ATPAD to your application
• Support for network parity, response delay, and DTR timeout
• Configurable Escape Sequence Timer
• Automatic or manual answer
• Four stored X.25 addresses (mnemonics) accessible by the ATDSn command
• Control signal or XON/XOFF flow control
• Configuration of operating parameters via the CTP