I have an existing ATS system that predominantly uses mouse to control & select the next operation.
I have created a 'Command Line' text box and given it primary focus so that I can have a couple of pre-printed Barcode commands to perform the most common actions - e.g. Reset & Run another test. Detect the changed value, parse the content and perform the action. This seems to work quite well.
I also use it to effect a 'Done' or 'Continue' event on a boolean control, as if you set focus and then get a 'c/r' from the Keyboard emulation of a USB barcode reader, it's fine.
Code 39, standard Honeywell 1d barcode reader.
If my prompt barcode is
*CONTINUE*, *CONT*, *DONE-CONT* I don't seem to get any reaction - I hear the beep, but there is no action in Labview.
*RESET-RUN*, *DONE*, *0004* work, even *C-O-N-T-I-N-U-E* works.
Any ideas? Am I hitting a reserved sequence in Code 39 or is Labview messing me up?
All the codes come out fine if I try them in any Notepad type editor.
The attached end of test display gives an idea - this is the boolean button that refuses to switch with CONT or CONTINUE - I have removed all the sub-vi dependencies I can spot so this should run stand alone - or put it in a calling VI and try the different options specified in the help text.... If you run it stand alone, you'll have to set the hidden 'Action' string cointrol to 'Show' - probably make this default & save it - you might also like to stop it disapearing at the end of the run 🙂 set the second fp.open to True - or delete it..
Thanks, but I kind of proved that it wasn't the Barcode Reader itself, as I could get all the sequences I described to render correctly in several different notepad style applications..
Thanks, Ben, Key nav is set to 'None' - and like I say, I seem to get the same effect with a boolean as I do with the string control... These things are sent to try us..... 😞
I attach here the word file with sample barcodes I have been playing with
I have also tried pressing keys on the keyboard to see what will trigger the boolean - it looks like the letter T will do it, but no other (does this set the boolean =True?)
This behaviour must be documented somewhere - but I haven't found where yet!