I never claimed to be that sharp... Python

dogfuel · 10-04-2009, 01:18 AM

55 of you may notice I originally tried to solve this with evdev ... this was just me being ignorant ...

I have a barcode scanner that, like most, injects the scanned string and a lf as text from a keyboard. Rather than scan data into an application, I'd like to simply log the time of the scan and barcode data scanned to a file.

I'm so new to this I feel like an idiot but assume I can loop and use the device to distinguish between the "real" keyboard and the scanner (scanner is on /dev/input/event7). My question is how to detect the scan, grab the characters to a file and, if possible, stop the scanned barcode characters from getting to X.

So far:

PHP Code:


			
import time, codecs
scanner_location = '/dev/input/event7'  # get the correct one from HAL

while True:
    scanner_device = open(scanner_location,"r")
    # log stuff to file here - below line for testing/debugging
    print repr(scanner_device.readline())
    scanner_device.close()
    time.sleep(0.1)

This detects and captures what I need but not in a human readable form (a byte stream?) ... how to I convert the output (...'\xc8J\x88\xc1\x04\x00\x04\x00\x0...) to information I can use?

Thanks!

dogfuel · 10-06-2009, 10:35 PM

humor the ignorant ... what is the string ...'\xc8J\x88\xc1\x04\x00\x04\x00\x0... that is output by the code above? Is this an encoding issue?

Thanks!

Wim Sturkenboom · 10-07-2009, 01:31 AM

Quote:

I'm so new to this I feel like an idiot ...

Don't worry, happens to me all the time

My guess is that that's raw data (so indeed an encoding issue). How is the scanner connected? Parallel to the keyboard? Or USB? Or serial?

This question might fit better in the programming section. If you agree, you can report your post and ask it to be moved.

salasi · 10-07-2009, 05:42 AM

I know less than you but...you would expect a stream of digits. For this purpose it may be worth getting, eg, a pack of soap powder where they print the UPC or whatever they call it beneath the bar code so that you can compare the stream of electronic information with the printed UPC. Having 'the answer' in front of you will result in additional clues.

Quote:

'\xc8J\x88\xc1\x04\x00\x04\x00\x0..

I'd be guessing at ascii-hex 88, c1, 04, 00 ...but that raises a couple of interesting questions

-what about that single zero at the end...is that the representation of 00, or has a character fallen off at the end

-that c8J at the start, specifically the J. Maybe the J signifies a valid start sequence has been detected or something, because you wouldn't be expecting a j in a hex stream.

At some point, the manual for your reader has to be a help, and particularly when it comes to what the reader does with different encodings (maybe you get a code to tell you which encoding it is, maybe it is all 'transparent', I don't know and it probably depends on the reader)

dogfuel · 10-07-2009, 10:36 AM

Quote:

My guess is that that's raw data (so indeed an encoding issue). How is the scanner connected? Parallel to the keyboard? Or USB? Or serial?

The scanner is connected via usb - I do have a "keyboard wedge" that will make it appear as ps2 kb input but would prefer not to use this as the PCs I plan to use it with do not have ps2 ports.

Quote:

-what about that single zero at the end...is that the representation of 00, or has a character fallen off at the end

-that c8J at the start, specifically the J. Maybe the J signifies a valid start sequence has been detected or something, because you wouldn't be expecting a j in a hex stream.

I may have been unclear - the actual output per scan is much longer ... I pasted a snippet hopping it would be enough to guess at its form.

Thanks!

pixellany · 10-07-2009, 02:06 PM

Moved: This thread is more suitable in <Programming> and has been moved accordingly to help your thread/question get the exposure it deserves.

dogfuel · 10-09-2009, 09:21 AM

perhaps I should have clarified ... at the same time that I read the cryptic string from /dev/input/event*, the characters show up on the window with focus. To me this implies that it is a pure encoding issue as there is no software installed on the client to interpret the input.

If I scan an ISBM barcode with the python loop running in a terminal terminal session (A) and the focus on another terminal session (B), I see

In Terminal B

Quote:

9780596100940

which is correct and

and in Terminal A

Quote:

'\xc2K\xcfJD\xc3\x02\x00\x04\x00\x04\x00&\x00\x07\x00\xc2K\xcfJL\xc3\x02\x00\x01\x00\n'
"\xc2K\xcfJ\xafx\x04\x00\x04\x00\x04\x00\x1e\x00\x07\x00\xc2K\xcfJ\xb5x\x04\x00\x01\x00\x02\x00\x01\ x00\x00\x00\xc2K\xcfJ\xb7x\x04\x00\x00\x00\x00\x00\x00\x00\x00\x00\xc2K\xcfJ\xee\x97\x04\x00\x04\x00 \x04\x00\x1e\x00\x07\x00\xc2K\xcfJ\xf5\x97\x04\x00\x01\x00\x02\x00\x00\x00\x00\x00\xc2K\xcfJ\xf6\x97 \x04\x00\x00\x00\x00\x00\x00\x00\x00\x00\xc2K\xcfJ$\xb7\x04\x00\x04\x00\x04\x00'\x00\x07\x00\xc2K\xc fJ*\xb7\x04\x00\x01\x00\x0b\x00\x01\x00\x00\x00\xc2K\xcfJ*\xb7\x04\x00\x00\x00\x00\x00\x00\x00\x00\x 00\xc2K\xcfJf\xd6\x04\x00\x04\x00\x04\x00'\x00\x07\x00\xc2K\xcfJn\xd6\x04\x00\x01\x00\x0b\x00\x00\x0 0\x00\x00\xc2K\xcfJo\xd6\x04\x00\x00\x00\x00\x00\x00\x00\x00\x00\xc2K\xcfJ\x98\xf5\x04\x00\x04\x00\x 04\x00'\x00\x07\x00\xc2K\xcfJ\x9d\xf5\x04\x00\x01\x00\x0b\x00\x01\x00\x00\x00\xc2K\xcfJ\x9e\xf5\x04\ x00\x00\x00\x00\x00\x00\x00\x00\x00\xc2K\xcfJ\xe6\x14\x05\x00\x04\x00\x04\x00'\x00\x07\x00\xc2K\xcfJ \xed\x14\x05\x00\x01\x00\x0b\x00\x00\x00\x00\x00\xc2K\xcfJ\xee\x14\x05\x00\x00\x00\x00\x00\x00\x00\x 00\x00\xc2K\xcfJ\x154\x05\x00\x04\x00\x04\x00&\x00\x07\x00\xc2K\xcfJ\x1a4\x05\x00\x01\x00\n"

how would I start to determine the encoding? The manual and manufacturer of the scanner have been no help and keep asking why I do not just scan directly into a text box.

Thanks,
joe

dogfuel · 10-09-2009, 11:12 AM

I tried the chardet module to deduce encoding with no luck ... I then tried all standard encodings without being able to interpret the line.

This has me really lost - it may be obvious to someone who knows what they're doing but I am stumped!

Thanks,
Joe