About The Native Sockets Interface; Converting Native Serial Applications To Native Sockets; Sending Device Ids To The Host - Intermec CN2B User Manual

Chapter 2 — Using the Intermec Gateway in a Native Environment

About the Native Sockets Interface

26
Note: If you are replacing a serially connected, legacy controller
with the Intermec Gateway on an Intermec Application Server,
you must have a 9F-25M RS-232 adapter (P/N 589182), since
the Intermec Application Server has a 9-pin serial port.
Native sockets are a subset of the Native async serial syntax. If
your host application was written to work with the Native
sockets interface, it should also work with the Intermec
Gateway.

Converting Native Serial Applications to Native Sockets

If your host application was written to work with WNAS or
legacy serially-connected controllers and are not communicating
with hosts through the Native sockets interface, you may need to
make some changes to your Native TE host applications to
connect them using Native sockets.
For help updating your Native applications, see the Native
Terminal Emulation Programmer's Guide.
Note: If your devices are communicating through Native
sockets, you must use a line feed (LF) as the delimiter. You
cannot use a carriage return (CR).
For example, if your host application was written to work with
the 6950 EGS, it should also work with the Intermec Gateway
as long as the host application separates packets using an LF
character. If you did not write your host application for the
6950 EGS using delimiters, you must add an LF after each
command. After you add the LFs, your host application will
work with both the 6950 EGS and the Intermec Gateway using
Native sockets.

Sending Device IDs to the Host

You can send the terminal session name and the terminal address
to the host. In the Add New Port page, check the Send Terminal
ID to Host check box. For more information on this feature, see
"Different Start-Up Packets" on page 46.
Intermec Gateway User's Guide