On Sun, 2002-07-14 at 17:13, Michael Van Wesenbeeck wrote: > Thanks for the reply, Anselm. > > > > Subject: [Ltsp-discuss] Point of Sale , accessing peripherals > > > > > Could anyone give me some tips on accessing peripherals on the > workstations? > > > I would like to read an iButton (small memory device, www.ibutton.com, > > > accessed via the serial port) in my point of sale app as some sort of > credit > > > card (members only). > > > > I just visited their website, and I'm truly impressed. One day I will > > get that system to computerize my home's door opener :-) > > > > I don't really understand what you do. Describe more precise... > See below... > > > > There seems to be something like a Java API for the iButton devices, with > > Linux support announced. Try to get your apps run with that, with the > > iButton reader device hanging at the server serial port (should be > > easy, as well documented). Then get the reader device > > moved to the workstation by having the WS running a modemserver (or so) > > and map /dev/ttyX1 to the network exported modem device > > - if you got that far, ask again. > > > > Another solution attempt: If you have (as I understood) a Windows > > computer (your "server") having the iButton, and windows-client > > machines only (as active* is MSIE only, AFAIK!?), you can mount a > > linux-exported serial port under windows too! That could cost you some > > dozen bucks (I would have to look it up, don't even remember the > > program's name for now), but it could work. But I don't see the point: > > Why attach an iButton reader to a LTSP client when it cannot run the > > software to access iButton? Or do you use vmware|Win4Lin|wine|...? > > > > I wonder if the iButton manufacturers would like to support > > ltsp-iButton project... Imagine an iButton > > based internet cafe (LTSP workstations) > > As in your example above -which really sounds interesting- one could have 1 > unique key per WS to get access to that specific WS. In my case however, my > plan is to use the iButtons to identify the different waiters (or > bartenders) or clients in our club (actually a riding school) so they can > put in orders on whatever WS or make payments (small cash transaction) on > whatever WS. > > Now that I read your comments, I think I want to try another approach to > this. On the same site they have info on TINI (Tiny InterNet > Interface --www.ibutton.com/tini) wich does all the propietary iButton stuff > and gets this info on the network. If I can get my server to read or track > this info, I can access it with my WS's. > > Let's say I wanted to use the serial port for something else. A simple LCD > display, showing the price the client has to pay. this can be different per > WS. How to set this up (Hardware/Software) ?
For most LCD displays, its simply "echo message > /dev/device". I print to stuff to them :). Setup a small LPD server on the workstation, and run 'echo "Hi there" | rlpr -P/dev/ttyS1@ws123' on the server. It could be simpler: simply run 'nc > /dev/ttyS1' in inetd on the workstation, and run 'echo "Hi there" | nc ws123 <port>' on the server. nc will get you messages back, too. I hope this info is some use to you. > > Info for your door-lock can be found @ > http://www.ibuttonlock.com/mylocksmith_pc/index.htm > > Michael. -- Berend De Schouwer ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
