Elatec TCP3 3.0.3.1 User manual

TCP3 3.0.3.1
Technical Manual
DocRev4, September 2, 2021
Elatec GmbH

Contents
Contents
1. Introduction.............................................. 5
1.1. Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2. Important Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Network Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1. IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2. Static IP Host Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3. DHCP Host Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Hardware Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1. Hardware Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2. Network cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3. USB Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.4. Connect the Network Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5. Power up TCP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.6. External Input and Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.7. Input Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4. Discovering TCP3 Devices on the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1. Prerequirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.2. Start TCP3 Config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3. Cross Subnet Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4. TCP3 Display List Sort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5. Configuration via TCP3 Config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.1. TCP3 Config Home Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.2. Backwards Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3. Network Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3.1. Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.3.1.1. Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.3.1.2. IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4. USB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4.1. Representation of Keyboard Newline . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4.2. TCP/IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4.3. TCP Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4.3.1. Web Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.4.3.2. Connect on any character . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.4.3.3. Connect on this character . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.4.3.4. Disconnect on this character . . . . . . . . . . . . . . . . . . . . . . . . 25
5.4.3.5. Disconnect timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.5. System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.5.0.1. Send Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.5.0.2. System Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.6. Password Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.6.1. Custom Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.7. Sending the Configuration to converters . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.8. Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.9. Saving Configuration to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Page 2of 61

Contents
5.10. Read Configuration from a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.10.1. Reset to Factory Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.11. Remote Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.12. Remote TWN4 Firmware or Configuration Update . . . . . . . . . . . . . . . . . . . . . . 30
6. Configuration via Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.1. Open the Homepage of a selected TCP3 . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.2. Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.2.1. Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.2.2. Printer: IP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.2.3. IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.3. Security ............................................ 36
6.3.1. Server Certificate Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.3.1.1. Create a Certificate Signing Request (CSR) Or Create an internal certificate 36
6.3.2. Client Certificate Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.4. USB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.4.1. Representation of Keyboard Newline . . . . . . . . . . . . . . . . . . . . . . . . 38
6.4.2. TCP/IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.4.2.1. TCP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.4.2.2. TCP Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.4.2.3. TCP Client Connection Features . . . . . . . . . . . . . . . . . . . . . . 40
6.5. Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.6. System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.6.1. Logging Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.6.1.1. Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.6.1.2. Send Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.6.2. System Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.6.3. Upgrade Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.6.3.1. Upgrade TCP3 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.6.3.2. Upgrade TWN4 Card Reader Configuration . . . . . . . . . . . . . . . . 45
6.7. Status ............................................. 46
7. Refresh the Firmware on TCP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.1. Local Firmware Update steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
8. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8.1. Basic Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8.2. TCP3 Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8.3. Network Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8.4. Printer ............................................. 51
8.5. Can the TCP3 be discovered by the TCP3 Config Tool? . . . . . . . . . . . . . . . . . . 52
8.5.1. Different Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.5.2. TCP3 is on Static IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.5.3. Can you open the homepage of the connected printer? . . . . . . . . . . . . . . 53
8.5.3.1. DHCP Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.5.3.2. Incorrect Static Address . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.6. Is the card swipe not being recognized by the authentication server? . . . . . . . . . . . 53
8.7. DHCP Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
9. Security................................................ 55
9.1. Network Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
9.2. USB Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
10. History of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
10.1. TCP3 Converter Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
10.1.1. Firmware STD3.0.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Page 3of 61

Contents
10.1.2. Firmware STD3.0.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
10.1.3. Firmware STD3.0.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
10.1.4. Firmware STD3.0.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
10.1.5. Firmware STD3.0.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
10.2. TCP3 Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
10.2.1. TCP3 Config V3.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
10.2.2. TCP3 Config V3.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
10.2.3. TCP3 Config V3.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
10.2.4. TCP3 Config V3.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
A. FCCNotice.............................................. 59
B. ICNotice ............................................... 60
C. Disclaimer .............................................. 61
Page 4of 61

1. Introduction
1. Introduction
The Primary use of TCP3 Converter is to provide an on-ramp for USB data to reach a network Server
which implements Authentication and optionally a Pull Printing feature. TCP3 can be configured as a 2
port network router which is designed to be connected between a network printer and a print server. TCP3
is equipped with two USB 3.0 ports. A card reader or keypad can be connected to either or both of these
two ports and can be used to send data to the authentication server. This is typically used to enable card
based authentication and to release print jobs from the print server to the attached network printer.
TCP3 can also be used in an industrial setting to enable card based authentication for industrial robots
or other manufacturing equipment. Via web services, an authentication host can directly control the two
outputs and one input to enable power to equipment or to indicate operational status.
1.1. Typical Scenario
A typical application is to extend the feature set of a network device (i.e. a network printer), by enabling
connection of a local peripheral device such as a card reader or keypad.
Figure 1.1.: Typical Connection with TCP3 Converter, reader and printer
1.2. Important Features
• TCP3’s IP address may be obtained by DHCP or may be assigned statically.
• TCP3 consumes only one IP address from the building’s DHCP server. This is important to cus-
tomers whose IT department charges based on the number of addresses in use.
• A card reader or keypad can be connected to either USB port. An additional device can be connected
to the second USB port. Both can be active at the same time.
• The USB ports do not follow the standard USB power specification but instead share a fixed amount
of power between the two ports.
• Supports both Client and Server modes of communication. In client mode the converter will send
data whenever a card is swiped, in Server mode the converter must be polled to receive the data.
Page 5of 61

1. Introduction
• Supports OAuth authentication in client mode
• Supports sending data in client mode via SSL TLS1.2 or HTTPS using a self signed certificate or via
customer certificate
• Can be configured over the network via its web browser interface
• Supports Syslog which enables remote monitoring of its health and status
• Supports printing a summary of its configuration settings to an attached printer
• Each Ethernet port is default configured to auto-negotiate 10/100/1000 Mbps full-duplex.
• The supplied TC3Config.exe tool provides a means for finding all TCP3 devices on a network.
• TCP3 Converter firmware can be upgraded over the network via its web browser interface
• The configuration of an attached TWN4 card reader can be upgraded over the network via its web
browser interface
• With the inclusion of an external specification file, TC3Config.exe can discover devices on other
subnets.
• Can be configured directly from the TC3Config tool
• TCP3 firmware can be upgraded over the network via the TC3Config tool.
• The configuration of an attached TWN4 card reader can be updated over the network via the
TC3Config tool.
• Power over Ethernet is an available option for powering TCP3.
• Compliant with California password law SB327.
The main feature of TCP3 is that it can enable any printer to participate in card based authentication along
with the Pull Printing function. Single function printers or older MFPs which do not support the direct
connection of a USB card reader can now be enabled by connecting those devices to TCP3.
TCP3 presents only one MAC address to the building’s network infrastructure and requests only one IP
address from the DHCP server. TCP3 behaves similar to a router where the printer connected to TCP3
has its own IP address but to the outside world it appears to use the IP address of TCP3. This means
TCP3 can be easily integrated into existing network environments, without managing extra IP addresses
or paying for extra IT support costs associated with additional IP addresses.
Other than the few ports necessary to configure and operate TCP3, communication is transparent between
the printer and the local network. This makes it convenient to configure the connected printer as if TCP3
was not connected in between.
Page 6of 61

2. Network Addressing
2. Network Addressing
2.1. IP Addressing
The TCP3 Converter has two network connections. The host connection can be configured to use either
DHCP or Static IP addresses to the building’s network. The Printer connection is always configured for
DHCP but users can configure the exact IP address provided so it can match a printer configured with a
static IP address.
2.2. Static IP Host Addressing
In this discussion we will assume that a network printer which was already operating on the network
with a static IP address of 192.168.1.10 as shown in Figure 2.1. That printer will now be connected to
TCP3.
Figure 2.1.: Network configuration before introduction of TCP3
A TCP3 Converter will be installed between the switch and the printer. When installing TCP3 we often
need to maintain the network relationship between the existing printer and the print driver installed on
the user’s workstation. As a result TCP3 should be configured to use the printer’s original IP address
192.168.1.10.
The printer must now be configured with a different IP address. TCP3 is configured to provide the printer
its address using DHCP. It is further configured to always issue the printer an IP of 192.168.50.100. If the
printer is configured for DHCP it will receive this address at each power up and at each DHCP renewal. If
the printer is not capable of DHCP and is configured with a static IP address, that exact address will need
to be entered on the TCP3 Network page.
Note if TCP3 is placed on a 192.168.50.xx host network, the converter will automatically change the default
printer address assigned via DHCP to 192.168.60.100.
2.3. DHCP Host Addressing
In this example the printer is configured for DHCP and has a MAC based IP address reservation on the
DHCP server so it always receives the same IP address. When the printer reaches out to the building
router, its DHCP controller issues the printer an IP address 192.168.1.10.
As with the preceding static IP address discussion, when installing TCP3 we often need to maintain the
existing network relationship between the printer and the print driver installed on the user’s workstation.
Page 7of 61

2. Network Addressing
Figure 2.2.: Network Settings for TCP3 and Printer. Note that TCP3 takes the IP address that the Printer
had.
When TCP3 is inserted between the printer and building router, the router’s DHCP reservation for the
printer should be reassigned to the MAC address of TCP3. That host MAC address is printed on the back
of the converter enclosure. TCP3 will then communicate with the DHCP server and will receive the printer’s
original IP address.
Any print driver previously configured to send jobs to the printer will now communicate with TCP3 which
will seamlessly forward those print jobs directly to the attached printer. As a result the printer will appear
on the network as it did before TCP3 was installed. The customer benefit is that this was accomplished
using one network port with only one IP address from the customer environment.
To reach the printer’s home web page simply enter the IP address of the TCP3 device into your favorite
web browser. TCP3 will pass that request directly to the printer and the printer’s web page will open.
To reach the TCP3 home web page simply enter the IP address of the TCP3 device followed by :81 into the
web browser for example: 192.168.1.10:81. TCP3 broadcasts its web page on port 81 while all traffic to the
standard http port 80 traffic is redirected to the printer and its home page. Note if HTTPS is enabled instead
of using port 81 TCP3 broadcasts its secure web page on port 442 for example: https://192.168.1.10:442.
All secure web traffic destined for the connected printer will use the standard port for HTTPS (443) which
will pass through TCP3 unaltered.
Page 8of 61

3. Hardware Setup
3. Hardware Setup
Figure 3.1.: Connection Diagram
3.1. Hardware Mounting
TCP3 is shipped with rubber mounting feet such that it can be positioned upon a horizontal surface. In
most instances the preferred mounting will be to attach it vertically to the back of the printer using the
Velcro tabs provided. That will make the converter less visually obtrusive.
3.2. Network cables
Refer to Figure 3.1 Connection Diagram which shows all of the possible peripherals and their connection
points. There are two Ethernet ports on TCP3, the Host port is used to connect TCP3 to the local network
and the Printer port is used to connect a printer to TCP3.
3.3. USB Cables
Users can connect a USB card reader to either of the 2 USB ports on TCP3. Up to two readers can
be connected simultaneously. Currently USB Human Interface Device also known as keyboard mode is
supported.
TCP3 can provide up to 1.5A current shared between the two USB ports. This means if the peripheral
connected to one port is drawing 1.0A, the second peripheral can draw up to 0.5A before both ports will
be turned off by the over current protection circuit. Removing the second USB peripheral will enable the
port to self reset.
Page 9of 61

3. Hardware Setup
Note that only tested and approved USB devices will be allowed to operate on TCP3. This will enable
Elatec to provide support for only those devices for which our support team has been trained. Following is
the current list of tested and approved devices.
Table 3.1.: Supported USB Devices.
Manufacturer Device USB VID USB PID
Elatec TWN3 RFID Reader 0x09D8 0x0310
Elatec TWN4 RFID Reader 0x09D8 0x0410
Elatec TWN4 SafeCom Reader 0x09D8 0x0206
ID Tech MiniMag II™ MagStripe reader 0x0ACD 0x0001
ID Tech Barcode Reader 0x0ACD 0x2420
MagTek Dynamag Reader 0x0801 0x0520
MagTek MagStripe reader 0x0801 0x0001
Honeywell Model 3800 Barcode Reader 0x0536 0x02E1
Honeywell Model 3800 Barcode Reader 0x0C2E 0x0B01
Honeywell Model 1250G Barcode Reader 0x0C2E 0x0B41
Symcode Barcode reader 0x0483 0x0011
Motorola Model DS9208 2D Barcode Reader 0x05E0 0x1200
Perixx Peripad-201 Plus PIN pad 0x2A7F 0x5740
Perixx Peripad-201 PIN pad 0x1C4F 0x0043
Perixx Peripad-202 PIN pad 0x04D9 0xA02A
HCT Numeric PIN Pad 0x1C4F 0x0002
Valley Enterprises USB to RS232 converter 0x0403 0x6001
Manhattan 28 port USB hub 0x2109 0x2811
NT-Ware TWN4 for NT-Ware 0x171B 0x2001
Lenovo KU-9880 USB numeric Pin Pad 0x04F2 0x3009
Targus AKP10-A USB numeric Pin Pad 0x05A4 0x9840
Targus AKP10-A USB numeric Pin Pad 0x05A4 0x9846
3.4. Connect the Network Printer
Connect the network printer as shown in Figure 3.1. Leave the printer powered off until TCP3 has been
configured.
3.5. Power up TCP3
TCP3 is offered with either a 5 volt wall power supply or Power over Ethernet (PoE).
• If using a 5V supply, connect the power supply as shown in Figure 3.1.
• If using PoE, connect the Host Ethernet cable to a 802.3af compliant PoE enabled network switch
which outputs 44-56 volts. Note that the converter will not likely operate using a PoE injector. Most
injectors are passive meaning the power is on all of the time. Power is not negotiated per 802.3af
and they typically output only 24 volts which by design is ignored by TCP3. Note that although TCP3
was designed to be 802.3af compliant, it will also operate on a 802.3at or 802.3bt compliant switch.
As TCP3 powers up, its operating status can be determined through the LED panel located on the face
of the unit. The converter typically takes 45 seconds to boot up. This time will be extended by up to two
Page 10 of 61

3. Hardware Setup
additional minutes if there is no host network connection as the converter continually attempts to reach the
DHCP server.
There are 4 LEDs on the device and the operation mode of the device can be determined based on a
combination of LED signals. Here are a few of the possible states.
• Power LED displays Green when power supply is connected and orange if there is a power fault.
• Ready LED displays Green in normal operation. It will turn off during certain conditions described
later in this document.
• Busy LED displays Red when the device is initializing. It will blink during a software upgrade or when
the input button is pressed. It is off at other times.
• The Status LED displays Green when all conditions are normal. I will display red if there is a loss of
the host network and orange if it is not able to communicate with the printer.
3.6. External Input and Outputs
TCP3 is equipped with 2 optically isolated outputs and one optically isolated input. These can be used to
control copiers equipped with a 3 wire Foreign Device Interface. These signals are available via an 8 pin
ribbon cable connector on J7 as shown in Figure 3.2. The mating connector is a CviLux CI018SDOL1.
Prototyping cable are available from Elatec. The article number is CAB-J7.
Figure 3.2.: External I/O Connector Pinout
The outputs are polarity insensitive and capable of sinking up to 75ma and provide 1,500V isolation The
input is polarity sensitive and requires a minimum of 1.6ma for recognition of an input while providing
5,000V isolation.
These outputs can be controlled via a web service response response to a card swipe. The API for this web
response is presented in the TCP3 Config folder of the AdminPack. Its file name is “card_service_to_server.json”.
A hidden web page as shown in Figure 3.3 is available which can be used to for development purposes. A
link to this page is presented at the bottom of the System page as shown in Figure 6.9. In addition Foreign
Device Interface stub cables are available for prototype purposes. The Elatec part number for the cable
assembly is CAB-J7.
In an industrial setting, the authentication server can respond to the web service call with instructions to
enable or disable outputs or to time enable them. It can also monitor the input sensor line to gain status.
This could be used to enable a CNC machine for an authenticated user.
Page 11 of 61

3. Hardware Setup
Figure 3.3.: Hardware Status
3.7. Input Button
TCP3 is equipped with an input button which is located next to the USB ports. This button can be used
to activate additional functions. When the input button is held, the Busy LED will blink at a rate of once
per second. Hold the button and release it after a particular number of blinks to activate the associated
function
• 3 blinks will print a TCP3 configuration page to the attached printer.
• 8 blinks will reset the TCP3 configuration to factory defaults and will force a reboot. Note this will not
reset the password. That can only be done by reloading firmware.
Page 12 of 61

4. Discovering TCP3 Devices on the network
4. Discovering TCP3 Devices on the network
4.1. Prerequirements
1. Download the TCP3 AdminPack from the Elatec website Download Center. The contents of the
AdminPack are shown in Figure 4.1. It contains the TCP3 firmware, this Technical Manual, the
installer for the TC3 Configuration application and several sample subnet search files.
http://www.elatec.com/support-center/downloads/.
Figure 4.1.: Admin Pack Contents
2. Unzip the AdminPack then run the TCP3 Config installer by double clicking on Setup.exe. This will
install the TCP3 Config tool on a PC.
3. Devices must be on the same subnet as the PC operating the TCP3 Config discovery tool. Devices
on a different subnet can be discovered with additional steps addressed in section 4.3 which follows.
4.2. Start TCP3 Config
TCP3 Config is a tool which can be utilized to discover all of the TCP3 devices connected to the network.
It can also read the configuration of the selected converter, enable editing of that configuration and can
Page 13 of 61

4. Discovering TCP3 Devices on the network
send that updated configuration back to the same converter to multiple converters.
Double click on the TCP3 Config application which will then start and the window shown below will
open.
Figure 4.2.: TCP3 Config Home Screen and Button Functions
Once the TCP3 Config tool is started, it will immediately begin to broadcast a discovery message to each
specific IP address on the same subnet as the workstation on which TCP3 Config is running. It will only
send one message to each address and will then listen for a response to that message from each device.
All of the TCP3’s connected to the local subnet, will appear once discovered. They will be presented in
the order they respond to the discovery message sent from the TCP3 Config tool. This can take up to 60
seconds. If the host PC on which TCP3Config is running is connected to multiple networks for example
a wired and a wireless connection, TCP3Config will search both networks for converters. This will extend
the search time if each connection is on a different subnet.
Figure 4.3.: Repeat Search For Converters
Any additional devices connected to the network after TCP3 Config completes its search will not be auto-
matically discovered. The ”Search for Devices” button in the upper right corner of Figure 4.3 will need to
be selected again to repeat the search process.
4.3. Cross Subnet Discovery
TCP3 Config can be enabled to discover TCP3 units on subnets other than the one to which the user’s
workstation is connected. The network routers and switches must be enabled to allow web service traf-
Page 14 of 61

4. Discovering TCP3 Devices on the network
fic.
As shown in Figure 4.4 which follows, in the upper left corner of the TCP3 Config display window, select
“File” then “Load Network Search File”. This will enable the user to upload a file which describes the
various subnets which are to be searched. Selecting “Unload Network Search File” disables the file and
returns to search only the local subnet.
Figure 4.4.: Import subnet Search file
A window will open which will enable the user to navigate to the file which contains their search criteria.
Three sample configuration files are supplied with the TPConfig software and shown as follows. Select the
file then select “Start Discovery” and a new search will begin using the criteria specified in the configuration
file.
TCP3 Config will send a packet to each host address specified in the Subnet Search file and will populate
the discovered device window with each TCP3 which responds to that query. Note that the search file
could describe the same subnet as the searching PC.
Each time “Start Discovery” is selected the converter will execute just one pass of the parameters specified
in the search file.
The sample search files present several different approaches to subnet exploration: specific addresses,
address ranges and using CIDR or slash notation.
Figure 4.5.: Sample configuration file Using Explicit IP Addresses
If the addresses of each converter is known, a text file can be built as shown in Figure 4.5. Once that file
is loaded, the TCP3 Config main window will be populated with the list of addresses from the file. Upon
Page 15 of 61

4. Discovering TCP3 Devices on the network
selecting “Start Discovery” a new search will begin as queries are sent to each IP address on the list.
As the various converters respond, their information will populate the various TCP3 Config fields. This
method is useful for checking the status of a known installed population of devices. Converters which fail
to respond indicate that attention may be needed.
Figure 4.6.: Sample configuration file Using CIDR Notation
If the addresses of the converters are not known and only the subnet is known, a text file can be built
as shown in Figure 4.6. With CIDR also known as slash notation, the address is supplied along with the
netmask. Once that file is loaded, the TCP3 Config main window will initially be populated with the list of
subnets to be searched.
Figure 4.6 file presents two different subnets to be explored. 192.168.8.0/24 will use a subnet mask of
255.255.255.0 and will search IP addresses in the range 192.168.8.0 - 192.168.8.255 for a total of 256
addresses.
Note CIDR search is restricted to /24. Any number smaller than /24 could cause a very large search which
could take a long time and could take the customer’s network down. It might be interpreted as a denial of
service attack. As a result any number other than /24 will be ignored. For an efficient search, select many
individual subnets.
Figure 4.7.: Sample configuration file Using IP Ranges
If the addresses of the converters are not explicitly known but you have a rough idea where they reside a
search can be constructed to explore a limited number of addresses with a range specification. A text file
can be built as shown in Figure 4.7. Once that file is loaded, the TCP3 Config main window will initially be
populated with the range of IP addresses to be searched.
Upon selecting “Start Discovery”, the range notation will be replaced and updated with a list of IP addresses
of the converters which have responded.
Additionally each of these search techniques can be combined into one search file.
Page 16 of 61

4. Discovering TCP3 Devices on the network
4.4. TCP3 Display List Sort
The contents of the display window can be sorted by each of the table headings. Selecting a column
heading once will sort in ascending order. Selecting the heading a second time will reverse the sort
order.
Once the converter or converters are discovered, one at a time they can be selected and configured. If the
printer attached to the selected TCP3 has a web front-end on port 80, it can be accessed by clicking the
button “Open the Homepage of the Printer” as shown in Figure 4.8.
The web page view of the converter can be reached by selecting the converter followed by selecting “Open
the Homepage of the Converter”. This will open the homepage of the selected TCP3 using the default web
browser.
Figure 4.8.: Opening the Homepage of the printer
Page 17 of 61

5. Configuration via TCP3 Config
5. Configuration via TCP3 Config
5.1. TCP3 Config Home Screen
When TCP3Config opens it will immediately start to discover all of the TCP3 devices on the local subnet. It
will also determine if the devices are able to communicate via HTTPS or only via HTTP. If any of the TCP3
devices are reconfigured from HTTP to HTTPS be sure to select the search button again so TCP3Config
can relearn the capabilities of each device. If any converter is capable of communicating via HTTPS,
TCP3Config will use that protocol while still communicating with other devices via HTTP. That capability
will also be indicated with a check mark in the SSL column next to the device IP address as shown in
Figure 5.1.
From the TCP3 Config screen select one of the TCP3 devices then double click on it. TCP3 Config will
contact the selected converter using the default password to obtain the configuration. If the TCP3 uses a
password which differs from the default, please refer to section 5.6.1 for instructions to change the default
TCP3 Config password.
Beginning with firmware version 3.0.1.0 TCP3 will be compliant with California law SB327 which requires
each TCP3 to be factory programmed with a unique power on password. The default password is the last
8 characters in the Host MAC address which is printed on the back of TCP3. For example if the Host MAC
address is 20:1D:03:01:7E:1C, simply enter 03017E1C as the password. Note that the password is case
sensitive and must be entered as upper case. Once the password has been entered a user may change
the factory password to something easier to remember. There are currently no constraints on minimum
password length or password complexity
5.2. Backwards Compatibility
Elatec typically offers a new version of TCP3 firmware every 6-9 months. Each of these versions has new
features which must also be incorporated into the TCP3 Config management tool. As a result it is difficult
to support older versions of TCP3 with any given version of TCP3 Config. A version of TCP3 Config is only
guaranteed to work with the current release of TCP3 and the previous version of TCP3. The best practice
is to upgrade older TCP3 devices to the latest firmware to take advantage of the newer features. The latest
TCP3 Admin Pack is always available on Elatec.com.
5.3. Network Configuration Window
A configuration window will open which defaults to the current network configuration for the selected con-
verter. The window has 4 different tabs which present Network, USB, System and Password. These
present the same information presented in the web page view but the connection to the converter is via an
API instead of via a web browser.
At the bottom of each view are three buttons called “Apply”, “Save” and “Cancel”.
Page 18 of 61

5. Configuration via TCP3 Config
Figure 5.1.: TCP3 Config Home Screen and Button Functions
Apply Button When Apply is selected TCP3 Config will send the configuration settings directly to the
selected converter via the API. All configuration settings will be packaged into a file and sent regardless
of whether any changes were made or not. Once the converter responds that the changes have been
accepted or rejected, the window will close and the converter will reboot. The Log window on the TCP3
Config home screen will indicate whether the changes were accepted or rejected.
Save Button When Save is selected, TCP3 Config will save all settings to internal memory used by the
TCP3 Config program. The window will close and no changes will be made to the converter which is
selected. Because these changes have been saved to the TCP3 Config program they can now be applied
to other converters or saved to a file. See section 5.9 and 5.10 for details on this feature.
Cancel Button When Cancel is selected, TCP3 Config will close the window and any changes will be
lost.
5.3.1. Network Configuration
5.3.1.1. Name Resolution
TCP3 Config offers the ability to send the same configuration to multiple converters. While this is a really
useful feature, we need to be careful sending the same hostname or static IP address to multiple convert-
ers. As a result in order to change the hostname you must overtly select the Change Hostname checkbox
Page 19 of 61

5. Configuration via TCP3 Config
Figure 5.2.: Network Configuration Screen
in the event you wish to actually change the hostname.
This requirement is in place for both the Apply button which would change the hostname immediately or
to the Save button which would place the new hostname in the file which would be sent to other convert-
ers.
Name This is the name assigned to each individual TCP3 unit. Normally each converter is given a
name which is easy to associate with the connected printer. Often this name is geographically inspired
for example a device attached to a Brother printer on the 3rd floor near column G7 might be named:
Brother3-G7.
Hostnames are composed of series of labels concatenated with dots, as are all domain names. For
example, “tcp3.local” is a hostname. Each label must be between 1 and 63 characters long, and the entire
hostname (including the delimiting dots) has a maximum of 255 characters.
The Internet standards RFC (Request for Comments) for protocols mandate that component hostname
labels may contain only the ASCII letters ’a’ through ’z’ (in a case insensitive manner), the digits ’0’ through
’9’, and the hyphen (’-’). (RFC 1123) permitted hostname labels to start with digits. No other symbols, punc-
tuation characters, or white space are permitted. Please make sure a valid hostname is given, otherwise
Page 20 of 61