Ok lets leave report printing alone (thatís too big scope, we need to do
something that is doable)
Goal: To print on demand ticket w/ temp username and password
Usage: Hospitality places: Café, Small Hotels
1) Print Ticket w/ Separate printer w/ I/O button
2) Tap in to POS system and use its printer
3) Use JetDirect to connect some printer as network printer
Now: #3 I think thatís to vulnerable, bidirectional support is not really
working in those print server, + u also need printserver. I would go w/ this
only if some one can show me Small Thermal Tiket printer that alredy has
Ethernet port build in and its cost is unde $400 + there is a prigamable
Other wise its either #1 or #2. I'm not an exper on POS inregration, but I
say if some one can show me how I can tap into POSes then it would be nice
and easy way out :)
Still POS idea makes me a bit cautious so I wanna stick with #1 as required
solution for tiket printing (Stand Alone Solution) and then have POS taping
as option if there is a POS that supports that.
As to the printers I have D-Link DSA-3100P which is OEM from APS-Printers.
And I thinking about ZyXel printer, but I donít know whos OEMing it. Any
other printers are fine w/ me if some one can name them.
From: Hillel Seltzer [mailto:hseltzer at larich dot com]
Sent: Tuesday, December 18, 2007 2:36 PM
To: Alex M
Subject: RE: [m0n0wall] Ticket Printer Project
For printing reports, it may be easiest to have m0n0wall
print to the existing store report printer. Trust me,
you do not want to be piling up more report printers.
Unless, of course, you want m0n0wall to replace the
network print server device for the store's report printer.
If the m0n0wall box is controlling the network and the
wireless access, you might not want to put it out on the
counter with the printer. Use a separate device for the
client machine with the printer. Then you can maintain
whatever OS you get to work with it without dealing with
changes to m0n0wall beyond your control. It is also not
smart to start serving regular network services like printing
with your network firewall.
I wrote and still maintain a point of sale application,
so I know what you are asking to do. I used to use my own
Unix-based thin clients and have now switch to IGEL Linux
thin clients. Most POS applications out there have generic
hooks for a OPOS device or for triggering a custom script
or application based on a line item or tender. Take a look
at how gift cards and private label credit work.
Do you have a specific printer with a button already in mind?
You may be able to find a button device that behaves to the
computer like a USB keyboard or an OPOS scanner. You might
actually want more than one button as other buttons could
trigger reports or other functions. Then you just react to
keys pressed on a keyboard. With USB, you can have multiple
keyboards, so adding a special device that acts like one
will not hurt anything else. KSI Keyboards is pretty
reasonable at getting small custom keyboards like that.
Take a look at http://www.ksikeyboards.com/custom_gallery.php
Some flavors of Linux made for thin clients will easily handle
multiple USB keyboard. MS Windows Embedded for POS (WEPOS)
would also do the trick with multiple OPOS devices.
My suggestion would be to put the m0n0wall device in the back room
with the telco equipment and just add a network service to provide
a new username and password for captive portal when requested.
Then build a small print server with a trigger button (like a
USB JetDirect) that would be attached to the little receipt printer
and perhaps serve the store's report printer while running your
network client to make requests from the m0n0wall box.
Ideally it would be best to be able to reprogram a JetDirect
or similar device that has a test button.
On Tue, 18 Dec 2007 12:42:01 -0500, Alex M wrote
> As to LDP Printer we can use it to print general reports and stats
> from nono on regular printer (that's what some one just asked me to
> do to :)
> And as to POS, yep that's nice idea to have POS request the username,
> the only problem is that POS is separate product and there
> 100000000 of different POS systems out there, we can do custom
> coding for each and every one of them. We can however try to work
> with Micros (the major POS for hospitality industry) but that is too
> much of a negotiation work. I'm currently talking to them about
> merging some other product but that's too hard, they are not like
> open source community; I have to do all the financial and legal
> things just to do the prototype.
> So, Ill say having one small printer on the counter is not a big
> deal, and then if u want we can add UPC barcode on the printer so
> the seller ony will have to scan the ticket to get the prce entered
> into POS. (Although in my company we give out internet for free to
> -----Original Message-----
> From: Hillel Seltzer [mailto:hseltzer at larich dot com]
> Sent: Tuesday, December 18, 2007 11:44 AM
> To: Monowall Support List
> Cc: Alex M
> Subject: RE: [m0n0wall] Ticket Printer Project
> Adding a LPD server with communication to a serial printer
> should be easy. However, you want a button on the printer
> to initiate communication back to the serial port - that is
> a lot harder.
> What is coming up with the new username and password?
> Can it be run on the point of sale terminal instead of the
> m0n0wall box? If the customer is being charged, then the
> cashier has to enter a sale for this anyway. Why not have
> the point of sale print the username and password on the
> receipt and then automatically communicate that somehow
> to the m0n0wall box? Alternatively, can the POS request the
> username and password from the m0n0wall box when printing the
> receipt for the sale? It could all be triggered automatically
> by selling the appropriate item, so the cashier would not
> even have to hit a button on another unit. You then also
> don't have to maintain another printer or walk over to a
> special box if they have POS terminals in multiple locations.