Download Getting Started With Your UID Compliance Verifier

Appendix
F
Data File Formats for UIDChecker Software
•
HTML files containing the results for a single read. These files contain the
text and image data, allowing for simple viewing in a web browser. HTML
offers a more secure file structure than a typical text file. Editing or changing
data results is more difficult for a novice PC user. HTML file names are the
unique hex number prefixed by “Result_” and suffixed by “.html”.
•
Image files are the bitmap image used for the read. Saving image data is a
user-defined option. Image file names are the unique hex number prefixed
by “Image_” and suffixed by “.bmp”.
•
The cumulative log file gets appended with the text for each result that is
saved. The log file name is “UIDDataLog.dat”. This file contains the raw
text data in comma-delimited fields. Customers who wish to automate their
UID Mark Reading results using perhaps a database scheme will be able to
use this log file.
Each saved result places a single line of data into the cumulative log file.
The data is comma delimited in the following order:
F-2
–
Path and Name of Image, if image saving is enabled
Or
Result Number and “:No Image Saved”, if image saving is disabled
–
Month and Day (e.g., November 4)
–
Year and Time of Result (e.g., “2004 13:24:34”)
–
Software Version (e.g., “1.0.0”)
–
The string “UII:” followed by the decoded UID string
(e.g., “UII: UN077991289420243510936”)
Or
The string “UII: Not a valid UID Data Matrix” if the mark is invalid
–
“PASS”, if UID Compliant
Or
“FAIL”, if not UID Compliant
–
“FORMAT INVALID”, if raw data is not a UII format string
Or
UID Construct (e.g., “# 1”), if raw data is a UII format string
–
“RAW DATA:” followed by raw data, if raw data is not a UID format
string
Getting Started With Your UID Compliance Verifier
v2.3.1, Dec 2008