Installing LPR/LPD printer in RetailVista

This document describes how printing to an LPD printer works from RetailVista.

Introduction

LPR stands for 'Line Printer Request' and originates from the Unix world to be able to print to printers. From Unix, there was no other option than to print via the IP (TCP) protocol. From RetailVista, it is now possible to specify that the destination for a thermal printer is not 'LocalServices' but instead 'TCPIP'. LocalServices is then completely bypassed, and printing is done directly to an IP address from the Retail3000 backoffice environment.

In this case, RetailVista acts as the LPR, and the printer is the LPD (Line Printer Daemon).

In order to print via TCPIP, the printer must support LPD. This can be done through a print server or a printer with a network interface. Note: Some cheap print servers and Ethernet printer interfaces only work with the host-printer protocol. This is different from LPR/LPD and will not work. Therefore, when purchasing, make sure that the printer supports LPR/LPD. An example of an external print server that supports LPR/LPD is the HP J4102/170x.

Installation

In order to print, as mentioned earlier, an LPD must be available. It has an IP address and by default works with TCP port 515. Each port of a print server has its own queue name. Usually, this is raw or raw1, raw2, etc. This is especially the case with print servers that have multiple LPT ports.

If printing from outside the network to this LPD is desired, port forwarding must be activated on a router, for example, TCP port 515 to the internal IP address of the print server. If multiple print servers are desired, other ports such as 516, 517, etc. can also be opened. On the router, all these ports must be forwarded internally to an IP address with TCP port 515.

In RetailVista, it must be indicated that the destination for a thermal printer is TCPIP.

From this moment on, printing via TCPIP is possible.

Windows

In some situations, it can be useful to have a Windows PC or server perform the function of LPD. LPD is part of the optional 'TCPIP servers' that can be added through the Windows configuration.

By sharing a printer, the printer will be accessible via LPD. The name of the LPD queue is then equal to the share name of the printer.

Debugging

To check if the LPD server is available, it can be tested in a number of ways:

1. Use Telnet to open a session to the IP address and TCP port.

Example: Telnet.exe 1.2.3.4 515

This should result in a connection through a 'black' screen. This indicates that the

device at IP address 1.2.3.4 is at least responding on port 515.

2. Use LPQ.EXE to get an overview of all tasks in the queue on the LPD server. The LPQ.EXE program becomes available after installing the TCP services in Windows. The syntax of LPD is as follows:

LPD.EXE -S<ip address> -P <queue name>

Note: Not every print server supports extensive feedback of the tasks in the queue. It is possible that only very limited response comes without information about tasks.