Hi Tony,
The great thing about TestStand is you can make it do pretty much
whatever you want. Since TestStand can call code modules from just
about any programming
language, if you can write a program to do what you want, TestStand can
use it. It's just a matter of determining where in the Process Model /
Test Sequence to insert your code module.
In my experience people have used bar codes as a serial number entry
method. Serial number entry is handled by the Process Model,
specifically in the Pre UUT portion. You could use the Pre UUT callback
in your sequence file to call a code module that does all the work
involving your barcode entry, then pass it on to the Serial Number
variable within TestStand that gets used in your report.
Hope this helps Tony, have a great weekend!
Dan Weiland
Applications Engineer
National Instruments`
Dan Weiland