Ubisys 7047 User manual


13.56 MHz RFID USB READER
REFERENCE MANUAL

2 www.ubisys.de

1. Overview
Welcome to your ubisys RFID reader solution!
This reference manual provides operating and maintenance instructions, command references, a tag
compliance matrix, and other detailed product information. If you have any questions or need additional
support, drivers, software, libraries or source code samples, please visit our RFID support pages.
http://www.ubisys.de/rfid/support.html

3 www.ubisys.de

2. Contents
1. Overview ................................................................................................................................................................. 2
2. Contents.................................................................................................................................................................. 3
3. Features ................................................................................................................................................................... 5
4. Supported TAGs ................................................................................................................................................... 7
5. CDC Firmware ....................................................................................................................................................... 9
5.1. Features .......................................................................................................................................................... 9
5.2. CDC/ACM AT Command set ................................................................................................................... 9
5.2.1. Port Settings ......................................................................................................................................... 9
5.2.2. General Frame Format........................................................................................................................ 9
5.2.3. Device Information ............................................................................................................................... 9
5.2.4. Echo Control ....................................................................................................................................... 10
5.2.5. Light-Emitting Diode Control .......................................................................................................... 10
5.2.6. Buzzer Control .................................................................................................................................... 11
5.2.7. Inventory Scan .................................................................................................................................... 11
5.2.8. Inventory Scan (without Anti-Collision) ........................................................................................ 12
5.2.9. Select Tag ........................................................................................................................................... 12
5.2.10. Get System Information ............................................................................................................... 13
5.2.11. Read Data Block ........................................................................................................................... 14
5.2.12. Write Data Block ........................................................................................................................... 14
5.2.13. Lock Data Block ............................................................................................................................ 15
5.2.14. Enable/Disable RF field ............................................................................................................... 17
5.2.15. Query RF field status .................................................................................................................... 17
5.2.16. Automatic Scan Mode ................................................................................................................. 18
6. HID Firmware ....................................................................................................................................................... 19
6.1. Features ........................................................................................................................................................ 19
6.2. Operation ..................................................................................................................................................... 19
7. CCID Firmware .................................................................................................................................................... 20
7.1. Driver Installation ........................................................................................................................................ 20
7.2. Features and Tag Support ....................................................................................................................... 22
7.3. ATR Strings ................................................................................................................................................. 23
7.3.1. ATR for ISO14443-4 ....................................................................................................................... 23
7.3.2. ATR for Memory Cards (ISO15693, ISO14443-3 Type A).................................................... 23

4 www.ubisys.de

7.4. APDU Format .............................................................................................................................................. 24
7.4.1. Request APDU ................................................................................................................................... 24
7.4.2. Response APDU ................................................................................................................................ 24
7.5. APDU Definitions........................................................................................................................................ 25
7.5.1. Tag Identification Commands ......................................................................................................... 25
7.5.2. Configuration commands ................................................................................................................ 25
7.5.3. Memory Card Access Commands ................................................................................................ 29
7.5.4. Extended ISO15693 Information Commands ............................................................................ 30
7.5.5. ISO15693 Transparent mode ........................................................................................................ 31
8. Firmware update .................................................................................................................................................. 33
9. ubisys RFID/Smart Card API ............................................................................................................................ 40
9.1. Overview....................................................................................................................................................... 40
9.2. Basic RFID/Smart Card API .................................................................................................................... 40
9.2.1. CSmartCardContext ......................................................................................................................... 40
9.2.2. CSmartCard ....................................................................................................................................... 41
9.2.3. CSmartCardTransaction .................................................................................................................. 42
9.2.4. CSmartCardStatusReceiver ........................................................................................................... 42
9.2.5. CSmartCardStatusListener ............................................................................................................. 43
9.2.6. CSmartCardExceptionHelper ......................................................................................................... 44
9.2.7. Pre-defined Exception Classes ...................................................................................................... 45
10. Physical Dimensions ...................................................................................................................................... 47
11. Ordering Information ...................................................................................................................................... 50
11.1. USB Stick ................................................................................................................................................ 50
11.2. Desktop Pro ............................................................................................................................................ 50
11.3. Desktop .................................................................................................................................................... 51
12. Declaration of Conformity ............................................................................................................................. 52
13. Document revision history ............................................................................................................................ 53
14. Contact ............................................................................................................................................................. 54

5 www.ubisys.de

3. Features
- Versatile reader supporting three USB modes of operation: CCID = smart card reader, HID = keyboard
emulation, CDC/ACM = virtual serial port. Features out-of-the box OS support, i.e. no driver installation
on Microsoft Windows, Apple MacOS X and Linux – except for CDC/ACM mode, which requires a
driver information file on Windows (32- and 64-bit drivers available)
- 13.56 MHz HF RFID, supports all ISO 14443A and ISO 15693 tags,
with ISO 14443B and ISO 18000-3 available upon request
- Supported tags include Texas Instruments Tag-It HF-I, NXP i-code SLI, NXP Mifare Ultralight, NXP
Mifare DESFire, NXP Mifare DESFire EV1
- Extensible and future-proof design: Firmware updates via USB
- USB 2.0 full-speed device, bus-powered, 90mA in active mode, 30mA in stand-by. Thus, can be
plugged into any USB port, even into passive hub ports, such as those integrated into keyboards. Less
than 100mA when both LEDs are on (Desktop Reader Pro only), and additional 100mA for a total of
200mA when sound output is active (Desktop Reader Pro only)
- 70mW output power, approximately 10cm reading range with typical antenna/tag combinations
- Supported by ubisys® RFID Control Center, a sophisticated graphical user interface application for
evaluation, testing and firmware updates (Windows only)
- Three device classes available: USB stick, Desktop Reader Pro with two LEDs (red, green) and a buzzer
in premium design, and a classic desktop reader case
- Flexible antenna configurations:
o 50 Ohm SMA connector for industrial and commercial environments
o Standard printed circuit-board antenna coils available matched to 50 Ohm at 13.56 MHz
- Customizable OEM versions available, including customer-specific antenna coil designs
- Industrial temperature range: -40 °C ... +85 °C (Desktop Pro: -40°C ... +60°C)
- Different firmware types are available, can be used and exchanged depending on customer requirements
o CDC/ACM – Virtual Serial Port
The reader appears as a virtual serial port (COM port) by implementing the USB
Communications Device Class, Abstract Control Model (CDC/ACM) specification. All major
operating systems, including Windows, MacOS X and Linux support such devices out-of-the-
box – without the need for special device drivers. An “AT”-like command set is provided to
inventory tags and to access them. CDC/ACM was designed for industrial grade applications.
The firmware includes support for anti-collision inventory scan (bulk mode) and link-quality
assessment based on received signal strength indications.
o HID – Virtual USB Keyboard
The device appears as a keyboard by implementing the USB Human Interface Device Class
(HID) specification with the keyboard usage page. All major operating systems, including
Windows, MacOS X and Linux support such devices out-of-the-box – without the need for
special device drivers.
Whenever a tag is identified, it automatically “types” the unique identification number as a
hexadecimal number, followed by return. Customized versions, which type additional or
customized data (e.g. reader serial number combined with UID, memory content, encryption,
certificates etc.) are available upon request.
HID mode perfectly suited for web applications in heterogeneous IT environments (“cloud”)
o CCID – Smart Card reader
The device appears as a Smart Card reader (Chip Card Interface Device, CCID) with one virtual
slot. Standard CCID device drivers, provided with all major operating systems, will be used.
Supports access to ISO15693 memory cards, identification of ISO15693 non-memory cards,
identification of cards according to ISO14443A-3 (Mifare Classic/Mini/Ultralight) and full
access to cards according to ISO14443-4 (Mifare DESFire, NXP SmartMX etc.).
Compatible with many desktop virtualization solutions (including Microsoft and Citrix products)

6 www.ubisys.de

Reader devices can be ordered with the firmware of choice (CDC/ACM, HID or CCID) and can later be
updated to newer firmware releases as well as to other firmware types, by using the ubisys RFID Control
Center (see section 8).

7 www.ubisys.de

4. Supported TAGs
CDC
HID
CCID
Remarks
UID
R/W
UID
R
UID
R/W
D/E
ISO15693
ICODE SLI       
ICODE SLI-L       
ICODE SLI-S       
ICODE SLI-SY       
ICODE UID       
ICODE UID-OPT       
ICODE EPC       
ICODE 1 - - - - - - -
ICODE HC       
TAG it HF-I       
TAG it HF-I Pro       
TAG it HF-I Plus       
Legic Advant MV  -  -  - -
STM LRI64        LRI64 tags require 10% modulation depth, 1-
out-of-4 coding, single subcarrier setting and
high data rate.
The CCID firmware can be configured for these
parameters. CDC does not currently support
configuration. A modified firmware can be
provided on request.
STM LRI2K       
STM LRIS2K       
Fujitsu MB89R118       
Requires CDC Version 1.16 or above, CCID
Version 1.02 or above
ISO14443A storage cards
Mifare Classic  -  -  - -
Mifare Ultralight       -
Mifare Plus       -
Mifare Mini       -
ISO14443A-4 processor cards
Mifare DESFire
Mifare DESFire EV1
 -  -  -  No direct read/write access. Library
implementing the application-layer cryptographic
protocol to allow reading/writing data is available
upon request
Generic ISO14443A-4 cards
(e.g. NXP SmartMX)
 -  -  -  Application-layer protocol depends on the
implemented application.
 Supported
- Not supported, or not applicable
 Available on request as a customer-specific feature
UID read unique identifier (UID)
R/W read/write access
R read-only access
D/E transparent data exchange

8 www.ubisys.de

Remarks:
Mifare DESFire cards utilize a complex but flexible cryptographic protocol and require authentication,
session setup etc. and offer optional data encryption or message integrity checking. The protocol is not
implemented in the reader itself, but a library is available on request, which implements the protocol
and allows read/write access via the CCID firmware using the transparent data exchange.
Transparent data exchange for ISO15693 tags allows implementing features exceeding the reader-
supported read/write access in the host software. A library implementing further features is available
upon request.
Notice that ISO 15693 tags with eight-byte data blocks (e.g. Fujitsu MB89R118) require at least CDC
version 1.16 or CCID version 1.02 to read data blocks. Previous firmware versions were affected by a
bug. The bug did not affect writing.

9 www.ubisys.de

5. CDC Firmware
The device appears as a virtual serial port (COM port) by implementing the USB Communications
Device Class, Abstract Control Model (CDC/ACM) specification. All major operating systems,
including Windows (see below), Linux, and MacOS support such devices out-of-the-box.
Microsoft Windows requires an “.inf” file to recognize the device, which installs the built-in Windows
driver. This “.inf” file is (currently) not WHQL certified. Therefore, Microsoft Windows displays a
warning. If you need WHQL certified drivers for Microsoft Windows please file a feature request
([email protected]e). Notice that the “.inf” file is digitally signed however, and thus can be installed on
all 64-bit versions of Microsoft Windows.
A simple AT command set is provided to inventory tags and to access them.
5.1. Features
- The virtual serial port allows easy interfacing to customer-specific applications
- Supports ISO15693 (13.56 MHz) tags, e.g. TI Tag-It HF, NXP i-code SLI etc.
- Features a simple to use, “AT-like” command set that allows scanning for tags, reading and writing
on-tag memories, modifying physical layer parameters, etc.
- Thin abstraction layer over the ISO15693 protocol layer.
5.2. CDC/ACM AT Command set
5.2.1. Port Settings
The device represents itself as a virtual COM port. As such, port settings, like communication speed,
parity or stop bit settings will be ignored. No specific configuration is necessary and the port can be
operated at any settings (without influencing the communication speed).
5.2.2. General Frame Format
Request frames are terminated with a carriage-return character (ASCII code 13 decimal; 0x0d
hexadecimal; “\r” as C string literal). The device terminates response frames with carriage-return
followed by line-feed (ASCII codes 13, 10 decimal; 0x0d, 0x0a hexadecimal, “\r\n” as C string literal).
Do not add any white space (space, back-space, tab, carriage-return, line-feed, etc.), it will not be
removed by the command-line parser and thus leads to “ERROR” responses.
5.2.3. Device Information
This command queries the product information and firmware version of the device.

10 www.ubisys.de

Syntax
Request ATI
Response <product description>
S/N <serial number>
OK
Example
Request ATI
Response UBISYS RFID 13.56 MHz (CDC) 1.05 Aug 18 2010
S/N 000000A003
OK
5.2.4. Echo Control
This command enables or disables the echo of typed (received) characters. Enabling the echo is mainly
useful for debugging and for manual testing.
Syntax
Request ATE0 Disable echo
ATE1 Enable echo. All received characters will be echoed
back.
Response OK
5.2.5. Light-Emitting Diode Control
This command controls the state of the light-emitting diodes (LEDs). Notice that not all hardware
variants feature LEDs. Requires CDC/ACM firmware version 1.12 or above.
Syntax
Request AT+D<led no>=[0|1|2] Changes the state of the specified LED to
0 = off, 1 = on, or 2 = blinking. If no
state is specified, the application
relinquishes control to the firmware.
Response OK
Example
Request AT+D1=1 Turns LED number 1 on.
Response OK
Request AT+D2=0 Turns LED number 2 off.
Response OK
Request AT+D3=2 Makes LED number 3 blink.
Response OK
Request AT+D3= Returns control of LED3 to the firmware.

11 www.ubisys.de

Response OK
5.2.6. Buzzer Control
This command controls the operating mode of the on-board buzzer. Notice that not all hardware
variants feature a buzzer. Requires CDC/ACM firmware version 1.13 or above.
Syntax
Request AT+B=[0|1] Changes the operating mode of the buzzer
to 0 = off, or 1 = on. If no operating
mode is specified, the application
relinquishes control to the firmware (a
short beep whenever a transponder is
detected).
Response OK
Example
Request AT+B=1 Turns buzzer on.
Response OK
Request AT+B=0 Turns buzzer off.
Response OK
Request AT+B= Returns control of the buzzer to the
firmware.
Response OK
5.2.7. Inventory Scan
Requests an inventory scan. Returns a list of 64-bit unique identifiers and the received signal strength
indicators, as reported by main and auxiliary receivers. If no tags were found, the response is OK (no
UIDs).
ISO 15693 command: 01h (mandatory, supported by all tags)

12 www.ubisys.de

Syntax
Request AT+I
Response +UID=<uid>,+RSSI=<main>/<aux> [possibly repeated or absent]
OK
ERROR automatic scan mode (section 0) enabled
Example
Request AT+I
Response +UID=E00402000058913D,+RSSI=6/6
+UID=E00402000023F23C,+RSSI=3/2
OK
5.2.8. Inventory Scan (without Anti-Collision)
Requests an inventory scan without anti-collision. Returns the 64-bit unique identifier of the identified
tag and the received signal strength indicators, as reported by main and auxiliary receivers. If no tag
was found, the response is OK (no UID).
ISO 15693 command: 01h (mandatory, supported by all tags)
Requires CDC/ACM firmware version 1.09 or above.
Syntax
Request AT+i
Response +UID=<uid>,+RSSI=<main>/<aux> [may be absent]
OK
ERROR automatic scan mode (section 0) enabled
Example
Request AT+i
Response +UID=E00402000058913D,+RSSI=6/6
OK
5.2.9. Select Tag
Select a single tag for further processing. The tag access commands (get system information, read
data block, write data block) can either address all tags in the field or only a single tag. If it is known or
expected that more than one tag is in the field, a single tag should be selected.
Requires CDC/ACM firmware version 1.09 or above.

13 www.ubisys.de

Syntax
Request AT+SELECT=<uid> Select the specified tag for further processing.
AT+SELECT= Deselect tag. Address all tags in the field from
now on.
Response OK
Example
Request AT+SELECT=E00402000058913D
Response OK
(tag access commands address the specified tag)
Request AT+SELECT=
Response OK
(tag access commands address all tags in the field)
5.2.10. Get System Information
Obtain the tag’s system information. Returns 64-bit unique identifier, data storage format identifier
(DSFID), application family identifier (AFI), memory block count (BC) and size (BS), and IC
manufacturer defined data (IC). Notice that not all tags support this command and not all tags support
all items. DSFID, AFI and IC are displayed in hexadecimal format, BC and BS in decimal format.
ISO 15693 command: 2Bh (optional, supported by most tags, including NXP i-code SL-2, TI Tag-It
HF-I)
Syntax
Request AT+S
Response +UID=<uid>,DSFID=<dfsid>,AFI=<afi>,BC=<bc>,BS=<bs>,IC=<ic>
OK
ERROR tag reported an error, did not respond or automatic scan
mode (section 0) enabled
Please note that the presence of the DFSID, AFI, BC, BS and IC fields depends on what the tag
supports.
Examples
Request AT+S
Response +UID=E00402000058913D,DSFID=00,AFI=01,BC=40,BS=4,IC=02
OK
DFSID 00h, AFI 01h, 64 blocks of 4 bytes.

14 www.ubisys.de

Request AT+S
Response +UID=E00402000058913D,BC=100,BS=1
OK
No DFSID, no AFI, 256 blocks of 1 bytes.
Request AT+S
Response +UID=E00402000058913D
OK
No memory-related capabilities reported.
5.2.11. Read Data Block
Read data block from tag memory. The block number must be within the range supported by the tag,
i.e. the within range returned by the “Get System Information” request (BC, if command is supported).
Returns the length of the data block, followed by the actual data in binary format (separated by a
colon).
ISO 15693 command: 20h (optional, supported by most tags with on-chip memory, including NXP i-
code SL-2, TI Tag-It HF-I)
Syntax
Request AT+R<block number>
Response +DATA <number of raw bytes>:<raw data bytes>
OK
ERROR tag reported an error or did not respond, or automatic scan
mode (section 0) enabled
Example
Request AT+R0
Response +DATA 4:1234
OK
Request AT+R88
Response ERROR (e.g. if address is out of range)
5.2.12. Write Data Block
Write data block to tag memory. The block number must be within the range supported by the tag, i.e.
within the range returned by the “Get System Information” request (BC, if command is supported). The
Length must match the size of a data block as returned in the BS parameter.
ISO 15693 command: 21 (write single block, optional)
Notice: There are two variants of the write single block command. The first variant (lower-case “w”) has

15 www.ubisys.de

the option request flag clear, the second variant (upper-case “W”) has the option request flag set. It
depends on the tag, which command variant is supported. If you encounter errors or the memory block
content does not change, try the alternate option flag setting.
The data portion is in raw binary format, i.e. all values in the range 0-255 are allowed and written to the
tag without modification.
Syntax
Request AT+w<block number>, <size> without option flag
<data>
Request AT+W<block number>, <size>  with option flag
<data>
Response OK
ERROR tag reported an error or did not respond,
or automatic scan mode (section 0) enabled
Examples
Request AT+w0,4 Writes 0x31 0x32 0x33 0x34 to
1234 memory block 0, option flag clear
Response OK
Request AT+W23,4 Writes 0x54 0x65 0x78 0x74 to
Text memory block 23, option flag set
Response OK
5.2.13. Lock Data Block
Lock data block in tag memory. Requires CDC/ACM firmware version 1.15 or above. The block
number must be within the range supported by the tag, i.e. the within range returned by the “Get
System Information” request (BC, if command is supported).
ISO 15693 command: 22h (optional, supported by most tags with on-chip memory, including NXP i-
code SL-2, TI Tag-It HF-I)
Notice: There are two variants of the lock block command. The first variant (lower-case “l”) has the
option request flag clear, the second variant (upper-case “L”) has the option request flag set. It
depends on the tag, which command variant is supported. If you encounter errors, try the alternate
option flag setting.
ATTENTION: Once a block has been locked, it cannot be unlocked any more. The contents of the
block will be permanently write-protected, i.e. subsequent write attempts to the same block will fail.
Other blocks are not affected.

16 www.ubisys.de

Syntax
Request AT+l<block number> without option flag
Request AT+L<block number> with option flag
Response OK
ERROR tag reported an error or did not respond, or automatic scan
mode (section 0) enabled
Examples
Request AT+w0,4 Writes 0x31 0x32 0x33 0x34 to
1234 memory block 0, option flag clear
Response OK
Request AT+l0 Permanently write-protects block 0
Response OK

17 www.ubisys.de

5.2.14. Enable/Disable RF field
Syntax
Request AT+RF=<0|1>
Response OK
Example
Request AT+RF=0 Disable RF field
Response OK
Request AT+RF=1 Enable RF field
Response OK
5.2.15. Query RF field status
Syntax
Request AT+RF?
Response +RF=<0|1>
OK
Example
Request AT+RF?
Response +RF=1
OK

18 www.ubisys.de

5.2.16. Automatic Scan Mode
Enable or disable the automatic scan mode. In the automatic scan mode, indications are created
automatically whenever a tag enters or leaves the field.
NOTICE: While in any of the scan modes, all other commands are not available. You need to quit scan
mode first, using AT+SCAN0.
Syntax
Request AT+SCAN<0|1|2> 0 disable automatic scan mode
1 enable automatic scan mode
2 enable automatic scan mode with extended
scan indications (including RSSI)
Response OK
Indications SCAN:+UID=<uid> Tag found (new tag)
SCAN:-UID=<uid> Tag lost
Mode 2 only: SCAN:+UID=<uid>,+RSSI=<main>/<aux> New tag or RSSI changed
Example
Request AT+SCAN1 Enable scan mode 1
Response OK
(from this point forward the reader only accepts AT+SCAN commands, in particular AT+SCAN0
to leave scan mode)
Indications SCAN:+UID=E00402000058913D Tag found
SCAN:-UID=E00402000058913D Tag lost
Request AT+SCAN2 Enable scan mode 2
Response OK
(from this point forward the reader only accepts AT+SCAN commands, in particular AT+SCAN0
to leave scan mode)
Indications SCAN:+UID=E00402000058913D,RSSI=7/7 Tag found
SCAN:+UID=E00402000058913D,RSSI=6/5 RSSI changed
SCAN:-UID=E00402000058913D Tag lost
Request AT+SCAN0 Scan mode disabled
Response OK
(no indications generated anymore, you may use other commands again)

19 www.ubisys.de

6. HID Firmware
The HID firmware acts as a USB HID keyboard and “types” the UID of a found tag by using virtual
keystrokes. As such, it is possible to use the reader in conjunction with any application, without
modifications.
6.1. Features
- No dedicated device driver required. All major operating systems (Microsoft Windows, Mac OS X,
Linux) ship with a driver, which will be used.
- Whenever a tag is identified, it automatically “types” the unique identification number as a
hexadecimal number, followed by return.
- Supported standards are ISO15693 and ISO14443A (integrated “multi-ISO” firmware and
dedicated firmware images for each standard)
- Extended firmware versions available that type the reader’s serial number in front of the tag’s UID.
This version allows you to know with which reader (i.e. where) the tag has been scanned.
- Custom configurations can be provided, which output tag memory contents or enter customer-
defined prolog/epilog key sequences. Please contact ubisys® support for details.
6.2. Operation
Whenever a tag is detected first, its UID is typed via emulated keystrokes. As long as the tag is in the
field, no further action is taken. If the tag leaves the field and enters it again, the UID is typed again.

20 www.ubisys.de

7. CCID Firmware
With the CCID Firmware, the device appears to the host operating system as a single-slot Smart Card
Reader. If a tag is in the RF field of the reader, the reader reports an ”inserted card”. If there is no tag in
the field, this is reported as “card ejected”.
The device itself complies with the USB 2.0 CCID 1.1 specification (chip card interface device) to
allow the host computer to use a standard device driver, shipped with all major operating systems.
Applications use the operating-system-provided Smart Card API to access the reader and the tags. A
native Smart Card API is available on Microsoft Windows 2000 and above. The same API has been
adopted on MacOS X and Linux (pcsc-lite).
The reader emulates the T=1 APDU protocol exchange, allowing the host computer to exchange
commands and data with the reader and/or tag by sending and receiving APDUs.
For ISO 14443-4, which is based on APDUs natively, the reader establishes a transparent channel and
forwards APDUs between host and tag.
For memory cards (ISO15693), an APDU emulation layer is provided, which translates certain
predefined APDUs to appropriate ISO 15693 commands. Besides the APDU emulation layer, a
transparent mode can be enabled for ISO 15693, allowing the host application to communicate
directly with the tag. This feature allows customers to operate any tag that complies with the ISO
15693 standard. In particular, application software may use any manufacturer-specific “custom
command” codes.
A set of APDUs is defined to read the UID of the tag in the field and to configure the reader. These
APDUs will always be processed by the reader itself.
7.1. Driver Installation
On Microsoft Windows systems, the driver will be installed automatically. On Windows versions that
originally shipped without native CCID support, like Windows 2000 and Windows XP, you might need
to allow Windows Update to be searched for a suitable device driver. If you are using Windows 2000,
make sure that Service Pack 3 is installed.
Linux support requires that the packages pcsc-lite and libccid are installed.1
MacOS X Leopard, Snow Leopard and Lion also include versions of pcsc-lite.
Your ubisys product is automatically supported on systems with libccid version 1.4.5 as of October 11,
2011 and above. Depending on your OS type and version, the ubisys USB product and vendor ID
(0x19a6:0x0009) might not be included in shipped configurations yet and must be entered in a
configuration file belonging to PC/SC Lite in this case. Under MacOS X, the file is
/usr/libexec/SmartCardServices/drivers/ifd-ccid.bundle/Contents/Info.plist
1 The exact package names depend on the distribution used.