1. Manuals
  2. Brands
  3. Ubisys Manuals
  4. Other
  5. 7047
  6. Reference manual

Ubisys 7047 Reference Manual

13.56 mhz rfid usb reader
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
13.56 MHz RFID USB READER
REFERENCE MANUAL

Advertisement

Table of Contents
loading

Summary of Contents for Ubisys 7047

  • Page 1 13.56 MHz RFID USB READER REFERENCE MANUAL ...

  • Page 2: Overview

    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.

  • Page 3: Table Of Contents

    Operation ..............................19 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  www.ubisys.de...
  • Page 4 Memory Card Access Commands ....................29 7.5.4. Extended ISO15693 Information Commands ................30 7.5.5. ISO15693 Transparent mode ......................31 Firmware update ..............................33 ubisys RFID/Smart Card API ..........................40 9.1. Overview............................... 40 9.2. Basic RFID/Smart Card API ........................40 9.2.1.

  • Page 5: Features

    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)
  • Page 6 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).

  • Page 7: Supported Tags

    Generic ISO14443A-4 cards Application-layer protocol depends on the (e.g. NXP SmartMX) implemented application. read unique identifier (UID)  Supported read/write access Not supported, or not applicable read-only access  Available on request as a customer-specific feature transparent data exchange  www.ubisys.de...
  • Page 8 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.  www.ubisys.de...

  • Page 9: Cdc Firmware

    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 (support@ubisys.de). Notice that the “.inf” file is digitally signed however, and thus can be installed on all 64-bit versions of Microsoft Windows.

  • Page 10: Echo Control

    Example Request ATI Response UBISYS RFID 13.56 MHz (CDC) 1.05 Aug 18 2010 S/N 000000A003 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.

  • Page 11: Buzzer Control

    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)  www.ubisys.de...

  • Page 12: Inventory Scan (Without Anti-Collision)

    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.  www.ubisys.de...

  • Page 13: Get System Information

    (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 DFSID 00h, AFI 01h, 64 blocks of 4 bytes.  www.ubisys.de...

  • Page 14: Read Data Block

    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  www.ubisys.de...

  • Page 15: Lock Data Block

    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.  www.ubisys.de...
  • Page 16 (section 0) enabled Examples Request AT+w0,4 Writes 0x31 0x32 0x33 0x34 to 1234 memory block 0, option flag clear Response Request AT+l0 Permanently write-protects block 0 Response  www.ubisys.de...

  • Page 17: Enable/Disable Rf Field

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

  • Page 18: Automatic Scan Mode

    (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 (no indications generated anymore, you may use other commands again)  www.ubisys.de...

  • Page 19: Hid Firmware

    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.

  • Page 20: Ccid Firmware

    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.
  • Page 21 MUSCLE PC/SC Lite Test Program. Your ubisys reader should be listed. When prompted to enter the reader number, enter the number next to “ubisys 13.56 MHz RFID (CCID)”. You may then present a tag to the reader in order to see the tag’s ATR.

  • Page 22: Features And Tag Support

    For example, NXP Mifare DESFire cards belong to this class of tags. Libraries implementing the communication protocols are available on request to qualified customers. Please contact support@ubisys.de for details.

  • Page 23: Atr Strings

    Initial Header Category indicator Application identifier presence indicator Length 7..11 Registered Application Provider (PC/SC) A0 00 00 03 06 Standard 13..14 Card name NN NN 15..18 Reserved 00 00 00 00 (Check byte) Standard Standard ISO14443-3 ISO15693 (-3)  www.ubisys.de...

  • Page 24: Apdu Format

    (0 bytes), this field is absent. 256 bytes of expected response payload is encoded as 00h. 7.4.2. Response APDU Payload variable 1 byte 1 byte Optional Mandatory The payload field is optional, the status bytes SW1 and SW1 are always present.  www.ubisys.de...

  • Page 25: Apdu Definitions

    Wrong length requested, i.e. Le is less than the length of the UID/historical bytes. SW2 indicates the correct length. Function not supported. 7.5.2. Configuration commands Valid for: all standards, independent of active tag 7.5.2.1. Get Configuration Request Configuration item ignored Response Configuration value  www.ubisys.de...
  • Page 26 If the default configuration is read back and no default configuration was previously set, an empty response is returned. This configuration is used if the tag does not support the ISO15693 “Get System Information” command, which, among other information, returns the memory layout of the tag.  www.ubisys.de...
  • Page 27 Save the configuration to non-volatile memory. The current configuration will be preserved and reloaded on the next system start-up. Request ignored Response Response codes Meaning Command executed successfully. The configuration was saved. Failed to save configuration to non-volatile memory.  www.ubisys.de...
  • Page 28  www.ubisys.de...

  • Page 29: Memory Card Access Commands

    Function not supported. No memory card available or reader has entered transparent mode. File not found. The requested start address exceeds the memory capacity. 7.5.3.2. Update Binary Request Payload Address MSB Address LSB Amount of data to update (in bytes) Data to update (Lc bytes) Response  www.ubisys.de...

  • Page 30: Extended Iso15693 Information Commands

    2-byte values are encoded in little-endian byte order. Response Payload Response codes Meaning Command executed successfully and the requested information is contained in the payload. File not found. The tag did not submit the requested parameter. Wrong parameter P1-P2 submitted.  www.ubisys.de...

  • Page 31: Iso15693 Transparent Mode

    Command executed successfully. Transparent mode activated. Function not supported. Either, transparent mode is already activated or a non-ISO15693 tag is in the field. 7.5.5.2. Leave Transparent Mode Disables the transparent mode and returns to normal operation. Request ignored  www.ubisys.de...
  • Page 32 Command executed successfully. The response is delivered in the response payload field. Command executed successfully. The response is delivered in the response payload field. The response length was shorter than the specified Le. Wrong length, i.e. response buffer overflow. The submitted response length Le was too short.  www.ubisys.de...

  • Page 33: Firmware Update

    Firmware updates may be conducted on 32-bit and 64-bit Windows (requires RFID Control Center version 1.4 or above). Qualified customers needing firmware upgrade ability on other platforms should contact the ubisys RFID support team. The ubisys RFID Control Center software is available at http://www.ubisys.de/rfid/download-...
  • Page 34  www.ubisys.de...
  • Page 35 Step 1b (applies to CDC/CCID devices): If you are planning to update a CDC or CCID device, first use the connect command to click on the device, which you want to update. Then, click on the Update Firmware command.  www.ubisys.de...
  • Page 36 The card ATR will be printed for any card that enters reading range. Notice that the ATR does not comprise UID information, i.e. different cards of the same type will create the same ATR. You have to use the Get UID command in your applications to obtain the UID.  www.ubisys.de...
  • Page 37 Figure 4: Acknowledging the Warning Notice (Step 2) Step 2: Acknowledge the warning message.  www.ubisys.de...
  • Page 38 Step 3: Select the new firmware image. All common firmware images can be found in the installation folder of RFID Control Center (typically C:\Program Files\ubisys technologies\RFID Control\Firmware). Make sure that the USB connection is reliable while programming the firmware. Do not turn off intermediate hubs.
  • Page 39 Update” command. However, this should normally not be necessary. If you cannot use the Resume Update command successfully, detach the device from USB and reattach it. If the Resume Update Button does not appear after reattaching the device, it must be returned to the factory.  www.ubisys.de...

  • Page 40: Ubisys Rfid/Smart Card Api

    RFID/Smart Card API ubisys provides a C++ RFID/Smart Card API library, which provides an easy and convenient way of dealing with the Smart Card API. It can be used on Windows, MacOS X and Linux, as all operating systems use the same underlying Smart Card API.

  • Page 41: Csmartcard

    CSmartCard is destroyed/deleted. Internally calls SCardConnect(). The destructor will call SCardDisconnect() with the parameter dwDisposition to release the connection. The default parameters for dwShareMode, dwPrefProtocol and dwDisposition can be overridden, if necessary.  www.ubisys.de...

  • Page 42: Csmartcardtransaction

    CSmartCard::EndTransaction upon destruction. This class provides a convenient and exception-safe way to handle transactions. 9.2.4. CSmartCardStatusReceiver Provides a base class type for a status event receiver. An application must derive from this class to receive events in conjunction with CSmartCardStatusListener.  www.ubisys.de...

  • Page 43: Csmartcardstatuslistener

    SCARD_STATE_PRESENT cleared and again with SCARD_STATE_PRESENT. 9.2.5. CSmartCardStatusListener Provides an easy way to build an event-driven application which automatically reacts to tag/card events, e.g. availability/non-availability of tags (inserted/ejected cards), and the addition and removal of reader devices.  www.ubisys.de...

  • Page 44: Csmartcardexceptionhelper

    // A sharing violation occurred errorProtocolMismatch, // Protocol mismatch errorUnavailable // Reader or card/tag not available A sharing violation occurs if two applications try to open the same reader with incompatible settings, e.g. another application opened the reader in exclusive mode.  www.ubisys.de...

  • Page 45: Pre-Defined Exception Classes

    A pointer to the exception will be thrown. 9.2.7.1. Common Data Fields Both predefined exception classes contain the following public const data fields:  const unsigned int m_nErrorCause; Contains the cause of the error, encoded by using the enum defined in CSmartCardExceptionHelper.  www.ubisys.de...
  • Page 46 The MFC-based implementation overrides the GetErrorMessage() method:  virtual BOOL GetErrorMessage(LPTSTR lpszError, UINT nMaxError,  PUNIT pnHelpContext = NULL); The method returns a formatted error message, including the operation which failed, the API error code and the translated, human-readable error cause.  www.ubisys.de...

  • Page 47: Physical Dimensions

    10. Physical Dimensions Figure 7: USB Stick with on-board PCB antenna Figure 8: USB Stick with on-board PCB antenna (OEM, without case)  www.ubisys.de...
  • Page 48 Figure 9: USB Stick with SMA Connector for External Antenna Figure 10: USB Stick with SMA Connector (OEM, without case)  www.ubisys.de...
  • Page 49 Figure 11: Desktop Reader Pro Case (USB Micro-B Socket) Figure 12: Desktop Reader Case (USB B Socket)  www.ubisys.de...

  • Page 50: Ordering Information

    11. Ordering Information The following tables list the reader variants available. Use the specified order codes for your orders. Please contact ubisys support if you require any customization. 11.1. USB Stick Antenna Case Firmware variant Product Number Order Code U0201-010120-01...

  • Page 51: Desktop

    11.3. Desktop Case Firmware variant Product Number Order Code U0202-010210-01 7245 Light Grey U0202-010210-02 7252 (RAL 7035) CCID U0202-010210-03 7269  www.ubisys.de...

  • Page 52: Declaration Of Conformity

    We – ubisys technologies GmbH, Am Wehrhahn 45, 40211 Düsseldorf, Germany – declare under our sole responsibility that all orderable RFID products with product numbers and order codes as detailed in section 11 under the trade name “ubisys” to which this declaration relates are in conformity with the following directives and standards:...

  • Page 53: Document Revision History

    Updated tag compatibility matrix. Added lock block command documentation. Fixed an error in the documentation for transparent APDU exchange with ISO 15693 tags using the firmware CCID (the P1 parameter was documented incorrectly). 03/21/2016 Updated declaration of conformity 04/30/2016 Updated declaration of conformity  www.ubisys.de...

  • Page 54: Contact

    14. Contact UBISYS TECHNOLOGIES GMBH HARDWARE AND SOFTWARE DESIGN ENGINEERING AND CONSULTING AM WEHRHAHN 45 40211 DÜSSELDORF GERMANY T: +49 (211) 54 21 55 - 00 F: +49 (211) 54 21 55 - 99 www.ubisys.de info@ubisys.de support@ubisys.de  www.ubisys.de...

Table of Contents