Contents | Parent Topic | Previous Topic | Next Topic
The drivers for the following readers all have the same commands: Dumb Mouse, Dr Chip, Uniprog and Smart Mouse (under development) (These readers are called "dumb" because they do not implement a reader specific protocol).
Note: The Uniprog/Smart Mouse drivers are not tested on the actual device and therefore are not guaranteed to work.
Dr Chip note: : SCAM will not detect if the Dr Chip has a card inserted or not. The Dr Chip will give a pulse signal when the card is taken out. This can not be used in SCAM. The Dr Chip can act weird on 19200 baud, switching to 9600 baud and then back to 19200 usually solves this.
device
the serial device to which the reader is connected.
baud
the baud rate that should be used.
Note: Not every baudrate may be supported by the reader. This depends on the clocking frequency that the reader uses. The Dr Chip for example supports both 9600 and 19200 baud. However, not every smart card may support such high baudrates.
parity
the parity (odd/even/none/ignore/auto). When set to "auto" the parity that corresponds to the convention is used.
conv
the convention for byte encoding (direct/inverse).
wait_etu
the waiting time for input from the card in ETU.
wait_us
the waiting time for input from the card in microseconds.
Without any arguments, these commands return the current value.
baud [b]
parity [p]
conv [c]
wait_etu [e]
sets waiting time to e ETU
wait_us [u]
sets waiting time to u microseconds
All the general commands are valid as well.
Note: The Dr Chip reader can sometimes give an incorrect ATR if the card is inserted after the reader command.
Contents | Parent Topic | Previous Topic | Next Topic