Home › Help Centre › Realtime › Visitor management
Home › Help Centre › Realtime › Visitor management
Realtime help
Set up a visitor sign-in tablet with Realtime and print visitor passes on a DYMO label printer.
Connect a visitor tablet to Realtime and print visitor passes on a DYMO LabelWriter 550 attached to a local PC near the tablet.
RTConfig.ini file configured and saved in the Realtime folder (example below).This file holds the port you want to use internally on your network and the name of the printer. The printer name must be spelt exactly as Windows shows it. The easiest way to get it right is to print once from Realtime first (see Step 3), which saves the chosen printer name to the registry, then copy that exact name in. There is more on this in the advanced troubleshooting guide below.
If the visitor appears, the tablet is talking to Realtime correctly and you can move on to printing. If not, recheck the IP address and port from Step 1 before going any further.
The printer must be plugged into the local PC near the tablet, and the visitor print service must be running on that PC with the RTConfig.ini file in place.
RTConfig.ini is in the same place as the service.Still stuck? The advanced troubleshooting guide below walks through testing the port and the print service directly with PowerShell.
If a pass will not print, these checks isolate whether it is the printer driver, the port, the firewall or the print service. They are aimed at IT or installers.
LabelPrinter.For the network tests, the IP is the client PC that has the printer service installed, and the port can be any port that will not clash internally. These two settings go into the app under Printer Server IP and Port.
Run this in PowerShell on the PC with the service, using 127.0.0.1 and the port from your config. A result of True means the port is listening.
Run the same test from a different PC, using the IP address of the PC running the service.
If Test 1 is True but Test 2 is False, the firewall is blocking the port, and the app will hit the same problem. Open the port on the service PC's firewall.
Best run from a different PC. Use the IP address of the PC running the service (or 127.0.0.1 if testing locally). If the service is working, a label prints.