[aprssig] Bar Code Formats for APRS

['Scott Miller']

One issue with an embedded barcode device is that you might need to handle
retries.  If you just send a raw string to the TNC, you get one packet.  If
you want reliable delivery, you need to be able to retry or at least repeat
the packet.  If you're scanning a bunch of cards one after another, it
becomes a memory issue trying to keep track of everything that needs a
retry.

For the OpenTracker, I could set it up so that a scanned ID results in the
tracker sending a pre-programmed position with that ID a certain number of
times, unless it's interrupted by another ID being scanned.  Might not be
the best option, though, since you'd get a pile of icons in the same place.
Positional ambiguity also might not be what you want on something like a
race course, since it's 2-dimensional.

It'd be really easy to set up a command on the Tracker2 to send a message to
a pre-programmed destination, so you wouldn't have to include the
destination in the barcode.  Just barcode each card with the ID, and you'd
get a message with that text at the destination, tagged with the source call
of the scanning station.  At the very least that'd let you manually update a
tracking board, and it'll handle retries for a single buffered message
as-is.

Scott
N1VG 

> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org 
> [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Robert Bruninga
> Sent: Tuesday, February 27, 2007 11:45 AM
> To: 'TAPR APRS Mailing List'
> Subject: [aprssig] Bar Code Formats for APRS
> 
> I think a BarCode Application is ideal for APRS.
> 
> > IF the entrant's scorecards could be barcoded, they 
> > could be scanned on the way IN to a stage and on the 
> > way OUT of a stage.
> 
> I hope we can integrate the Barcodes into APRS in a seamless way
> so that they can be tabulated even on existing machines.  Here
> are some options:
> 
> >STATUS Packet...   
> :BLN1SCAN :A bulletin to all
> :DATABASEx:A message to "databaseX callsign"
> =POSIT/position comment text
> 
> MESSAGE FORMAT:  A message to s specific applications callsign
> wouild be great for generic applications.  They will be captured
> by all APRS clients and can be captured in FINDU etc.
> 
> 
> POSIT FORMAT:  The POSIT format is good for an application where
> the person with the wand is moving about.  Such as moving
> through a building or something (or a cave) and whenever they
> see a barcode on the wall, they scan it and their wand sends the
> LAT/LONG position AND any other data that is on the bar code.
> 
> Can anyone see any application that cannot be fit into either of
> these formats?
> 
> Bob, WB4APR
> 
> 
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 
>