User's Manual

PICS POC User’s Manual 13 January 2003

following SQL script. This will create the database with the required tables and fields.

Make note of the physical location of the database to set in the configuration screen.

CREATE TABLE "PICS" (

USER_ID VARCHAR(64) NOT NULL,

USER_ID_LEN INTEGER,

PIC_KEY VARCHAR(512),

NAME VARCHAR(64),

PIC_ID VARCHAR(24),

PIC_KEY_LEN INTEGER,

DURESS_ID VARCHAR(64),

DURESS_LEN INTEGER,

CONSTRAINT "USER_ID" PRIMARY KEY ("USER_ID")

);

CREATE TABLE "PICS_UPDATE" (

USER_ID VARCHAR(64) NOT NULL,

PIC_ID VARCHAR(24) NOT NULL

);

CREATE ROLE Administrators;

CREATE ROLE Users;

GRANT ALL ON PICS TO Administrators;

GRANT ALL ON PICS_UPDATE TO Administrators;

GRANT SELECT,DELETE,INSERT,UPDATE ON PICS TO Users;

GRANT SELECT,DELETE,INSERT,UPDATE ON PICS_UPDATE TO Users;

3.3 Reader Operation

The PICS Reader contains an embedded PC running an embedded operating system. The

Reader software uses an initialization file called reader.ini, which is located in the root

directory. A keyboard and monitor may be attached to the Reader for troubleshooting

purposes and configuration management. In addition, the reader.ini file may be updated

via the File Transfer screen in the PICS Manager software (assuming the Ethernet

connection to the Reader has been established) or by placing a new file on a floppy in the

floppy drive during the first 30 seconds after the Reader software has started to run.

The Reader takes about 35 to 40 seconds to begin operating after power is applied. Once

the Reader has booted, the LED on the OPTO-22 module in position 5 should start to

blink. This is an indication that the Reader is operating normally. In addition, during the

first 30 seconds after starting, the LED on the OPTO-22 module in position 2 will blink,

indicating that the Reader is looking for new files in the floppy disk drive. Within that 30

second window, placing a floppy with a new reader.ini file in the drive will cause the

Reader to copy the new file to the hard disk. The Reader must then be rebooted in order

for the new file to take effect. If the new file loaded has incorrect settings, it is possible

that the Reader will not function correctly. In this case, it will be necessary to reload a

correct file. A sample listing of the reader.ini file is shown below.