Hello all,
We are still in the midst of implementation and I am trying to determine if our existing BOCA printers (which are largely older units without built in ethernet or usb ports) can be made to work using our existing setup which includes Lantronix print servers.
Does anybody out there use Lantronix servers? I can't seem to get Tessitura to recognize any ticket printers I've tried to install via the Lantronix devices...
Thanks in advance for any tips!
Steven
Are the LANTRONIXs devices the networked serial devices? If they are, I don't think we had much luck with them and ended up going with parallel via a HP Jet Direct 170X. We had to buy a new interface for the BOCAs and fit them ourselves (10/15 mins per printer and 2/3 screws)
Hi Wayne,
Our BOCAs have both serial and parallel connectivity, and we are using the parallel ports. It seems though as the Lantronix devices have multiple ports (2 x serial & 2 x parallel) that there has to be some kind of logic to define the correct port.
Lantronix seems to suggest setting up LPR queues. I've done this but the printers don't show up in Tessitura. I've also tried creating a dummy local device on LPT1 with the generic text driver, and Tessitura fails to offer that in the Ticket Printer pulldown list.
I've followed the documentation on adding a ticket printer, but so far no joy. I'm going to try relocating a BOCA shortly to see if plugging it in locally to a PC works or not before I get too much further along.
I'm not sure how much this will help (I haven't touched printers in so long - I'm a bit rusty). I believe Tessitura looks for any printer setup on your machine with the Generic Text driver. (Just re-read and see you've done this already - please disregard the next para)
You could try setting up a local (fake) boca and assign it to LPT1 to see if it shows in Tess. Close tess and change the port on the printer properties -> port tab to point at the LPR queue and open Tess again to see if it shows and prints
OR, if you have a (windows) print server, share all these via that print server, so Tess is printing to a networked printer & not aware of any oddness.
Our snipped .vbs script for adding these boca looks like:
on error resume next
Set objNetwork = CreateObject("WScript.Network")
' New Print server RSCTOVF03
objNetwork.AddWindowsPrinterConnection "\\RSCTOVF03\COURTYARD-Foyer1"
objNetwork.AddWindowsPrinterConnection "\\RSCTOVF03\COURTYARD-Foyer2"
objNetwork.AddWindowsPrinterConnection "\\RSCTOVF03\COURTYARD-Office-Batch1"
objNetwork.AddWindowsPrinterConnection "\\RSCTOVF03\COURTYARD-Office-Supervisor1"
Dim WSHShell, RegLocate
'In the group policy registry editing is switched off. This is the only way I have found to get
'registry info into the local user key.
Set WSHShell = WScript.CreateObject("WScript.Shell")
RegLocate = "HKEY_CURRENT_USER\Printers\Settings\EnableBalloonNotificationsRemote"
WSHShell.RegWrite RegLocate,"00000000","REG_DWORD"
WScript.Quit ' Tells the script to stop and exit.
Hope it's of some use and not telling you what you already know
--Wayne
I see you've already tried the local boca already - sorry didn't read properly.
I've looked up the website and it was these we couldn't get working - was model UDS-10
I believe you have to change the port number to one digit higher for the next id. Normally the parallel port is 9100. I think you'd put 9101 to output to the second Parallel. There is/was a website or software configurator for the UDS-10, so I assume its similar for other models. You loaded a client on the PC and it gave you the option to configure the device from your PC.
Hope you get somewhere with this.
Thanks
Thanks a lot for all of this - I will try some of your suggestions.
Also, I've reached out to our implementation team, and showed them the issue(s), and they are going to open a ticket with RAMP on this as it seems even the basic local test should have at least displayed as an option in the pull-down.
I think there is an issue either way - I'll update this thread when I learn more.