5. Configuration via TCP3 Config
will reboot in an attempt to reconnect to the printer. Users can change the ping interval and number of
retries as needed.
The Host and Printer watchdogs can be enabled or disabled via the checkboxes below. Additionally the
converter can be configured to continue pinging either interface without a reboot in the event of a network
failure by setting the number of retries to -1.
5.4. USB Configuration
Currently TCP3 is able to handle USB devices which communicate in HID Keyboard mode. This can
include RFID, magnetic stripe or optical barcode readers as well as numeric entry keypads.
5.4.1. Representation of Keyboard Newline
The user can choose which characters the converter will send to the server when it receives the terminating
character from the card reader or keypad or the timeout expires. In USB Keyboard mode, this terminating
character is always a Carriage Return (CR) 13 in decimal and 0x0D in hexadecimal.
The choices are Carriage Return (0x0D), Line Feed (0x0A) or both Carriage Return plus Line Feed (0x0D,
0x0A).
5.4.2. TCP/IP Configuration
The converter can be configured either as a server or as a client. The factory default setting is for the
converter to be a server of data to a network client. In this mode the Local Port for USB is default configured
to 7777. This is the port the converter will use to communicate with the Client. In Server mode the converter
will quietly wait for USB data to arrive. When data arrives it will inform the Solution Client which will then
poll the converter to retrieve the data. The server will typically continue to poll the converter for remaining
data and to keep the network port open.
In Server mode users have the option of sending card reader data either as plain text or more securely via
SSL card reader data is encrypted using the server's certificate.
Note that the converter supports 2 USB connections simultaneously on the same port number. Data from
either USB device will be sent to the same server location.
If the converter is configured as Client, when USB data arrives, TCP3 will open a network connection to
a solution server based on the Client Configuration settings. This is the most popular mode of operation
where the converter is configured to open a network connection, send card data to the server and to close
the connection. In this mode the network port is closed unless TCP3 has data to send. This operates in
the same way when either a keyboard or CDC mode reader is connected.
5.4.3. TCP Client Configuration
When the converter is configured for Client mode, users have the option of sending data either as plain
text or via SSL where the data will be encrypted on the converter and decrypted at the server. Client mode
uses one of the certificates configured on the Security tab which is only available on the TCP3 web page.
Refer to section 6.3 for more details.
When the converter is configured as a client, card reader data can be sent either using UDP or using web
services.
Page 22 of 61
Need help?
Do you have a question about the TCP3 3.0.3.1 and is the answer not in the manual?
Questions and answers