How do I install an LPR printer within RetailVista?

This document describes the installation of an LPR Printer in RetailVista. LPR stands for 'Line Printer Request' and originates from the Unix world to be able to print to printers.

Introduction

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 the Retail3000 backoffice environment prints directly to an IP address. In this case, RetailVista is the LPR, and the printer itself 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

As previously mentioned, in order to print, an LPD must be available. This LPD has an IP address and works with TCP port 515 by default. 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 enabled 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, for a thermal printer, it must be indicated that the destination is TCPIP. Use the name of the print queue as the queue name, usually raw1. The TCP port number is almost always 515.  

From this point on, printing via TCPIP is possible. Windows In some situations, it can be useful to have a Windows PC or server perform the LPD function. An LPD print server or LPD network printer is not necessary in this case, as Windows takes over the LPD function. LPD is part of the optional "TCPIP servers" that can be added through Windows configuration.

By sharing a printer, the printer will be accessible via LPD. The name of the LPD queue will be the same as the share name of the printer.  In the example below, this Windows printer is shared and has the share name 'Epson'. The fact that the printer is shared can also be seen from the 'sharing' icon in the image above 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 (where 1.2.3.4 is the IP address of the LPD server). This should result in a connection through a 'black' screen, indicating 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 of a printer on an LPD server. The LPQ.EXE program becomes available after installing the TCP services (or LPD Print services, depending on the Windows version) in Windows. The syntax of LPD is as follows:

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

The queue name is the name of the printer on the LPD server for which the tasks should be displayed. If Windows is the LPD server, then the queue name is the share name of the shared Windows printer.

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