Hi Kirk and Steve,

Kirk:  You can usually programme prefix codes to the readers so that you can 
identify the reader (if there are several connected).  If there is a “context” 
needed for the bar code scanning then we either use a card of custom bar codes, 
or there are “location" codes.  You can also get the scanner to provide info on 
what kind of code it is, which can help in 4D in decoding the context.  In the 
case of a warehouse there are custom barcodes for the shelves and boxes (to 
keep track of where things are).  I don’t use wedge input.

Steve:  The IP-based wireless scanners sound good!  Which ones are you using?

Cheers!

Tony

Tony Pollard
Another Dimension Ltd



> On 29 Aug 2018, at 2:09 am, Stephen J. Orth via 4D_Tech 
> <4d_tech@lists.4d.com> wrote:
> 
> Kirk & Tony,
> 
> We do lots of bar coding systems every year using wedge-readers (keyboard 
> input), RS-232 wireless, and IP-based wireless.  Going forward we are no 
> longer doing RS-232 scanners as it is simply too much work for both us and 
> our clients.
> 
> If a wedge-reader is the right tool, we use this first, otherwise all our 
> projects are now IP-based scanners which are basically browsers.  Our 
> communication is via web services, which are very, very fast to develop and 
> provide very fast network communication.  The scanner displays on these units 
> are small so generating HTML pages for this is really quite trivial.  We have 
> also done a number of IP-based tablets and all of what I said is also true 
> here.
> 
> Best,
> 
> 
> Steve
> 
> *********************************************
>  Stephen J. Orth                                                
>  The Aquila Group, Inc.         Office:  (608) 834-9213
>  P.O. Box 690                           Mobile:  (608) 347-6447
>  Sun Prairie, WI 53590
> 
>  E-Mail:  s.o...@the-aquila-group.com
> *********************************************
> -----Original Message-----
> From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Kirk Brooks 
> via 4D_Tech
> Sent: Tuesday, August 28, 2018 6:56 PM
> To: 4D iNug Technical <4d_tech@lists.4d.com>
> Cc: Kirk Brooks <lists.k...@gmail.com>
> Subject: Re: How to tie 4D to barcode readers?
> 
> Tony,
> How are you handling programming the barcode reader to include information
> about what the barcode belongs to? Or are you using it as an extended
> keyboard input?
> 
> On Tue, Aug 28, 2018 at 4:19 PM Tony Pollard via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
> 
>> If you want the bar code scanning to be independent of where the user is
>> on the UI, then there is usually a serial port emulation available on USB.
>> GET SERIAL PORT MAPPING is useful for this on Mac.  You can then run
>> serial comms in a separate process, which is handy if (for instance) the
>> bar code readers are RF and being used at a distance from the computer
>> (which also lets you run multiple scanners per computer).  Or I’d guess
>> that there must be some IP wifi based bar code scanners out there by now,
>> so you could (presumably) simply do a TCP_Open.
>> 
> -- 
> Kirk Brooks
> San Francisco, CA
> =======================
> 
> *We go vote - they go home*
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **********************************************************************
> 
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **********************************************************************

**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************

Reply via email to