I must state here that I am not an expert in these matters, but the way it seems to work with our scanners is the scanner reads the barcode and automatically inserts a CR, indicating the EOL for that particular data field, and the program spits out the proper entry from the DB. I only point to that because I can manually enter the barcode number, but the program will not progress until I manually hit Enter, which indicates to me that the CR HAS to be inserted to tell the program that what was entered is the end of the input field.
Additionally, our barcodes are a standard 14-number format, which is programmable to different number combinations. It sounds like your pattern is different from ours because we only encode the 14 digits, and yours will probably have some sort of hex or ASCII code for encryption, assuming the cards are for security/identity, and the identifying info for the cardholder. I hope I've helped. If I haven't, just tell me to shut up! Jim Peterson On Wed, 2010-10-20 at 19:55 -0500, Paul Boniol wrote: > > Paul Boniol > > > > I've got it working, though I'm seeing what I'm guessing is more low > level information mixed in the data. It seems to follow the pattern: > > /(\x00|\xC0)\x02\xN/ where N is the number of bytes of data > following, up to 5 bytes. (The Card office encodes I believe 25 > characters in the stripe that I need to read + 1 CR.) It threw me for > a minute because the low ASCII characters aren't displayed on the > screen by cat, and the C0 just started after a reboot. > > Is this format normal/documented for raw /dev files? > > The input is terminated by a CR, so I have that as my > input-line-terminator. Thus I have no need for the pattern/number of > bytes. I could see if the CR was not there you would need to know > when one input was finished and where another would begin... > > Paul > > -- > You received this message because you are subscribed to the Google > Groups "NLUG" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to nlug-talk > [email protected] > For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en
