1. Manuals
  2. Brands
  3. Essel Manuals
  4. Scanner
  5. 000537
  6. Manual

Essel 000537 Manual

Fcc / ised, pse, ce approved rs485 rfid reader
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
FCC / ISED, PSE, CE approved
RS485 RFID reader
Eccel part: 000537
User manual
Manual version: v1.1
04/08/2022
1 |
P a g e
www.eccel.co.uk

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 000537 and is the answer not in the manual?

Questions and answers

Summary of Contents for Essel 000537

  • Page 1 FCC / ISED, PSE, CE approved RS485 RFID reader Eccel part: 000537 User manual Manual version: v1.1 04/08/2022 P a g e www.eccel.co.uk...

  • Page 2: Table Of Contents

    Table of contents Introduction ................................5 Electrical specification ............................6 2.1 A ............................ 6 BSOLUTE MAXIMUM RATINGS 2.2 O ............................. 6 PERATING CONDITIONS 2.3 DC = 5 V, T = 25 °C) ........................ 6 CHARACTERISTICS 2.4 C ) ..........................6 URRENT CONSUMPTION INPUT Installation ................................
  • Page 3 5.3.8 Transfer-Restore value (0x27) ......................27 5.4 MIFARE U ..........................29 LTRALIGHT COMMANDS 5.4.1 Read page (0x40) ..........................29 5.4.2 Write page (0x41) ..........................29 5.4.3 Get version (0x42) ..........................30 5.4.4 Read signature (0x43) ........................30 5.4.5 Write signature (0x44) ........................31 5.4.6 Lock signature (0x45) .........................
  • Page 4 5.6.6 Lock block (0x95) ..........................51 5.6.7 Write AFI (0x96) ..........................52 5.6.8 Lock AFI (0x97) ........................... 52 5.6.9 Write DSFID (0x98) ..........................53 5.6.10 Lock DSFID (0x99)..........................53 5.6.11 Get System Information (0x9A) ......................53 5.6.12 Get multiple BSS (0x9B) ........................54 5.6.13 Password protect AFI (0x9C) ......................

  • Page 5: Introduction

    1. Introduction Features  Low cost RFID Reader with MIFARE® Classic® in 1K, 4K memory, ICODE, MIFARE Ultralight®, MIFARE DESFire® EV1/EV2, MIFARE Plus® support  Over-the-Air lifetime updates  Command interface via RS485  Baud rate up to 115200 bps ...

  • Page 6: Electrical Specification

    2. Electrical specification 2.1 Absolute maximum ratings Stresses beyond the absolute maximum ratings listed in the table below may cause permanent damage to the device. These are stress ratings only, and do not refer to the functional operation of the device that should follow the recommended operating conditions.

  • Page 7: Installation

    3. Installation The RS485 RFID Reader must be connected to the RS485 bus using a dedicated cable. Pinout of the connectors is described below. The connector used on the Reader is 10 pin MOLEX 5015681007. Devices can be connected in a chain, so one device can be connected to another one. The maximum number of devices in a chain is four.

  • Page 8: Communication Interface

    4. Communication interface 4.1 Overview The RS485 RFID Reader can be controlled using a simple binary protocol available over RS485. This binary protocol was designed to be as simple as possible to implement on the host side whilst still providing robust communication.

  • Page 9: Crc Calculation

    4.3 CRC calculation CRC is a 16-bit CRC-CCITT with a polynomial equal to 0x1021. The initial value is set to 0xFFFF, the input data and the output CRC is not negated. In addition, no XOR is performed on the output value. Example C code is shown below.
  • Page 10 0x0691, 0x16b0, 0x6657, 0x7676, 0x4615, 0x5634, 0xd94c, 0xc96d, 0xf90e, 0xe92f, 0x99c8, 0x89e9, 0xb98a, 0xa9ab, 0x5844, 0x4865, 0x7806, 0x6827, 0x18c0, 0x08e1, 0x3882, 0x28a3, 0xcb7d, 0xdb5c, 0xeb3f, 0xfb1e, 0x8bf9, 0x9bd8, 0xabbb, 0xbb9a, 0x4a75, 0x5a54, 0x6a37, 0x7a16, 0x0af1, 0x1ad0, 0x2ab3, 0x3a92, 0xfd2e, 0xed0f, 0xdd6c, 0xcd4d, 0xbdaa, 0xad8b, 0x9de8, 0x8dc9, 0x7c26, 0x6c07, 0x5c64, 0x4c45, 0x3ca2, 0x2c83, 0x1ce0, 0x0cc1, 0xef1f, 0xff3e, 0xcf5d, 0xdf7c, 0xaf9b, 0xbfba,...

  • Page 11: Automatic Addressing

    4.4 Automatic addressing The device provides automatic addressing for boards connected together in the chain. The procedure requires modified tags with information containing the address and RS485 line termination information. It’s recommended to enable termination on the last reader in the chain. The procedure is as below: 1.

  • Page 12: Commands List

    5. Commands list Commands are exchanged with the module using the protocol described above. All frames contain a command byte and command arguments. Depending upon the command, arguments can be optional, so a command length can be in the range from 1-1024 bytes. 5.1 Generic commands 5.1.1 Acknowledge frame (0x00) This is the response message from the module to the host.

  • Page 13: Dummy Command (0X01)

    Error list: 0x01 - No reply received, e.g. PICC removal 0x02 - Wrong CRC or parity detected 0x03 - A collision occurred 0x04 - Attempt to write beyond buffer size 0x05 - Invalid frame format 0x06 - Received response violates protocol 0x07 - Authentication error 0x08 - A Read or Write error occurred in RAM/ROM or Flash 0x09 - The RC sensors signal over heating...

  • Page 14: Get Tag Count (0X02)

    5.1.4 Get tag count (0x02) The command send to the module to read how many TAGS are in range of the antenna no matter which technology of tag, so it returns the total amount present of all supported tag types. The maximum number for this standard discovery loop is 5.

  • Page 15: Activate Tag (0X04)

    0x0F - JCOP 0x10 – MIFARE Mini 0x21 – ICODE Sli 0x22 – ICODE Sli-S 0x23 – ICODE Sli-L 0x24 – ICODE Slix 0x25 – ICODE Slix-S 0x26 – ICODE Slix-X 0x27 – ICODE Slix2 0x28 – ICODE DNA SAK - byte for MIFARE family tags TAG parameter DSFID - byte for ICODE family tags UID bytes.

  • Page 16: Halt (0X05)

    5.1.7 Halt (0x05) The Halt command takes no arguments. It halts the tag and turns off the RF field. It must be executed at the end of each operation on a tag to disable the antenna and reduce the power consumption. Command description Argument Size...

  • Page 17: Save Keys (0X07)

    5.1.9 Save keys (0x07) This command should be called if the user wants to save keys changed using the SET_KEY command in the module non-volatile memory. Saved keys will be automatically loaded after power up or reboot. Command description Argument Size Value Description Command ID...

  • Page 18: Get Hardware Version (0X0A)

    Example: HOST=>READER: 0x09 – GET_VERSION READER=>HOST: 0x00 – ACK byte 0x09 – related command code GET_VERSION 0x31 0x2e 0x31 0x20 0x4a 0x61 0x6e 0x20 0x31 0x38 0x20 0x32 0x30 0x31 0x39 0x20 0x31 0x35 0x3a 0x33 0x35 0x3a 0x30 0x33 – version string bytes 5.1.12 Get hardware version (0x0A) This command requests a hardware version string from the device.

  • Page 19: Get Communication Settings (0X0C)

    Bus address Bus address byte. Default value is 0x80 0x00 – termination disabled Termination 0x01 – termination enabled Short name Four ASCII bytes with device description Response description 0x00 Command ID 0x0B SET_COMM_SETTINGS Example: HOST=>READER: 0x0B – SET_COMM_SETTINGS 0x05 – baudrate 115200 0x81 –...

  • Page 20: Reset To Factory Defaults (0X0D)

    5.1.15 Reset to factory defaults (0x0D) This command resets settings to factory default. The reader sends an ACK using the old settings, then reboots. The host application should wait at least 1000ms before sending another command. Command description Argument Size Value Description Command ID 0x0D...

  • Page 21: Firmware Commands

    5.2 Firmware commands The reader supports firmware upgrades. To perform a firmware upgrade, the user must execute the following commands. 5.2.1 Jump to bootloader (0xF1) This command should be executed as the first frame in a firmware upgrade sequence. When the device receives this command, it reboots and stays in the bootloader application.

  • Page 22: Firmware Frame (0Xf4)

    5.2.3 Firmware frame (0xF4) When the device is running the bootloader application and FIRMWARE START has already been executed, the host application can upload binary firmware file in chunks that are 256 bytes long (the last frame can be smaller). Command description Argument Size...

  • Page 23: Mifare Classics Commands

    5.3 MIFARE Classics commands This set of commands should be performed on MIFARE Classics tags. 5.3.1 Read block (0x20) The read block command should be used to read data from the tag. It takes as arguments the block number of the first block to read, the number of blocks to read, the key A or B parameter, and the key number in key storage.

  • Page 24: Read Value (0X22)

    Command description Argument Size Value Description Command ID 0x21 MF_WRITE_BLOCK Block number Number of blocks 0x0A – Key A should be selected from key storage Key A/B parameter 0x0B – Key B should be selected from key storage Key number Key number in key storage Bytes to write.

  • Page 25: Write Value (0X23)

    Example: HOST=>READER: 0x22 – MF_READ_VALUE 0x02 – block number 2 0x0A – key A should be selected from key storage 0x00 – first key should be selected from key storage READER=>HOST: 0x00 – ACK byte 0x22 – related command code MF_READ_BLOCK 0x00 0x00 0x00 0x01 –...

  • Page 26: Transfer Value (0X25)

    Command description Argument Size Value Description Command ID 0x24 MF_INCREMENT_VALUE Block number 0x0A – Key A should be selected from key storage Key A/B parameter 0x0B – Key B should be selected from key storage Key number Key number in key storage Delta value Signed 32-bit value (LSB first) 0x00 –...

  • Page 27: Restore Value (0X26)

    5.3.7 Restore value (0x26) This command should be used to restore a value to a volatile register on the tag from the block being addressed. It takes as arguments the block number where the value is stored, the key A or B parameter, key number in key storage.
  • Page 28 Example: HOST=>READER: 0x27 – MF_TRANSFER_RESTORE_VALUE 0x02 – source block number 2 0x03 – destination block number 3 0x0A – key A should be selected from key storage 0x00 – first key should be selected from key storage READER=>HOST: 0x00 – ACK byte 0x27 –...

  • Page 29: Mifare Ultralight Commands

    5.4 MIFARE Ultralight commands This set of commands should be performed on MIFARE Ultralight tags. 5.4.1 Read page (0x40) The read page command should be used to read data stored in tag pages. It takes as arguments the page number of the first page to be read, and the number of pages to be read. The returned ACK answer contains data read from the specified tag memory.

  • Page 30: Get Version (0X42)

    HOST=>READER: 0x41 – MFU_WRITE_PAGE 0x02 – page number 2 0x02 – two pages to write 0x31 0x35 0x3a 0x33 0x35 0x3a 0x30 0x33 – 32 bytes to write READER=>HOST: 0x00 – ACK byte 0x41 – related command code MFU_WRITE_PAGE 5.4.3 Get version (0x42) This command requests a version string from the TAG.

  • Page 31: Write Signature (0X44)

    5.4.5 Write signature (0x44) This command writes the signature information to the MIFARE Ultralight Nano TAG. It takes as arguments relative page location of the signature part to be written and four bytes of signature value to be written. Command description Argument Size Value Description...

  • Page 32: Increment Counter (0X47)

    Command description Argument Size Value Description Command ID 0x46 MFU_READ_COUNTER Counter number Counter number Response description 0x00 Command ID 0x46 MFU_READ_COUNTER Counter value Unsigned 24-bit value, LSB first Example: HOST=>READER: 0x46 – MFU_READ_COUNTER 0x01 – counter number READER=>HOST: 0x00 – ACK byte 0x46 –...

  • Page 33: Ultralight-C Authenticate (0X49)

    0x00 Command ID 0x48 MFU_PASSWORD_AUTH PACK Password acknowledge bytes Example: HOST=>READER: 0x48 – MFU_PASSWORD_AUTH 0x00 0x00 0x00 0x00 – password READER=>HOST: 0x00 – ACK byte 0x48 – related command code MFU_PASSWORD_AUTH 0x00 0x00 – password acknowledge bytes 5.4.10 Ultralight-C authenticate (0x49) This command tries to authenticate the MIFARE Ultralight-C tag using the password stored in the key storage.
  • Page 34 0x4A – related command code MFU_CHECKEVENT 0x01 – tearing event occurred 34 | P a g e www.eccel.co.uk...

  • Page 35: Mifare Desfire Commands

    5.5 MIFARE DESFire commands This set of commands should be performed on MIFARE DESFire tags. 5.5.1 Get version (0x60) This command requests version information from the tag. The returned ACK answer contains 28-bytes with version information. Command description Argument Size Value Description Command ID 0x60...

  • Page 36: List Application Ids (0X62)

    5.5.3 List application IDs (0x62) This command requests lists application IDs from the TAG. The returned ACK answer contains the bytes with application IDs. Every ID is 3-bytes long. Command description Argument Size Value Description Command ID 0x62 MFDF_LIST_APP_IDS Response description 0x00 Command ID 0x62...

  • Page 37: Authenticate (0X64)

    5.5.5 Authenticate (0x64) This command tries to authenticate the MIFARE DESFire using the password stored in the key storage. It takes as an argument one byte with the key number in the key storage, and one byte with the key number on the card.

  • Page 38: Authenticate Aes (0X66)

    5.5.7 Authenticate AES (0x66) This command tries to authenticate the MIFARE DESFire using the key stored in the key storage, and one byte with the key number on the card. It takes as an argument one byte with the key number in the key storage. This command can be used with AES128 keys.

  • Page 39: Delete Application (0X68)

    5.5.9 Delete application (0x68) This command tries to delete an application from the tag. It takes one argument with the application ID. Command description Argument Size Value Description Command ID 0x68 MFDF_DELETE_APP Application ID Application ID bytes Response description 0x00 Command ID 0x68 MFDF_DELETE_APP...

  • Page 40: Get Key Settings (0X6A)

    5.5.11 Get key settings (0x6A) This command gets the key settings bytes from the tag. This command does not require any arguments but an application must be selected and authorized. Command description Argument Size Value Description Command ID 0x6A MFDF_GET_KEY_SETTINGS Response description 0x00 Command ID...

  • Page 41: Write Data (0X6D)

    Access rights Please refer to the NXP documentation for more information File size file size, LSB first 0x00 – Standard file Backup file 0x01 – Backup file Response description 0x00 Command ID 0x6C MFDF_CREATE_DATA_FILE Example: HOST=>READER: 0x6C – MFDF_CREATE_DATA_FILE 0x01 – file number 0xEE 0xEE –...

  • Page 42: Create Value File (0X6F)

    Command description Argument Size Value Description Command ID 0x6E MFDF_READ_DATA File number File number inside application File offset file offset, 3-bytes LSB value Data length Read data length, 3-bytes LSB value Response description 0x00 Command ID 0x6E MFDF_READ_DATA Example: HOST=>READER: 0x6E –...

  • Page 43: Get Value (0X70)

    5.5.17 Get value (0x70) This command returns the value stored in a value file on the TAG. The returned ACK response contains 4 bytes of signed value, LSB-first. Command description Argument Size Value Description Command ID 0x70 MFDF_GET_VALUE File number File number inside application Response description 0x00...

  • Page 44: Debit File (0X73)

    Command description Argument Size Value Description Command ID 0x72 MFDF_LIMITED_CREDIT File number File number inside application Credit value 4 bytes signed value, LSB first Response description 0x00 Command ID 0x72 MFDF_ LIMITED_CREDIT Example: HOST=>READER: 0x72 – MFDF_ LIMITED_CREDIT 0x02 – file number 0x05 0x00 0x00 0x00 –...

  • Page 45: Write Record (0X75)

    Command description Argument Size Value Description Command ID 0x74 MFDF_CREATE_RECORD_FILE File number File number inside application Access rights Please refer to the NXP documentation for more information Record size Record size, 16-bits LSB value Number of records Number of records, 16-bits LSB value If cyclic file is full: Cyclic flag 0x00 - further writing is not possible unless it is cleared...

  • Page 46: Clear Records (0X77)

    Command description Argument Size Value Description Command ID 0x76 MFDF_READ_RECORD File number File number inside application Record number Record number, 2-bytes LSB value Data length Read data length, 2-bytes LSB value Response description 0x00 Command ID 0x76 MFDF_READ_RECORD Example: HOST=>READER: 0x76 –...

  • Page 47: Get Free Memory (0X79)

    Example: HOST=>READER: 0x78 – MFDF_DELETE_FILE 0x01 – file number READER=>HOST: 0x00 – ACK byte 0x78 – related command code MFDF_DELETE_FILE 5.5.26 Get free memory (0x79) This command returns a value corresponding to the amount of free memory available on the TAG. No arguments are required.

  • Page 48: Abort Transaction (0X7C)

    Command description Argument Size Value Description Command ID 0x7B MFDF_COMMIT_TRANSACTION Response description 0x00 Command ID 0x7B MFDF_COMMIT_TRANSACTION Example: HOST=>READER: 0x7B – MFDF_COMMIT_TRANSACTION READER=>HOST: 0x00 – ACK byte 0x7B – related command code MFDF_COMMIT_TRANSACTION 5.5.29 Abort transaction (0x7C) This command invalidates all previous write access on backup data files, value files and record files within one application.

  • Page 49: Icode (Iso15693) Commands

    5.6 ICODE (ISO15693) commands This set of commands should be performed on ICODE (ISO15693) TAGs. 5.6.1 Inventory start (0x90) This command starts the inventory procedure on ISO 15693 TAGs. It activates the first TAG detected during collision resolution. If no TAGs are detected, then an error with a timeout flag is returned. This command takes one argument AFI - Application Family Identifier.

  • Page 50: Stay Quiet (0X92)

    Command description Argument Size Value Description Command ID 0x91 ICODE_INVENTORY_NEXT Application Family Identifier Response description 0x00 Command ID 0x91 ICODE_INVENTORY_NEXT Unique identifier DSFID Data Storage Format Identifier 0x00 – no more cards in range of antenna More cards flag 0x01 – more cards in range of antenna Example: HOST=>READER: 0x91 –...

  • Page 51: Write Block (0X94)

    Command description Argument Size Value Description Command ID 0x93 ICODE_READ_BLOCK Block number Block count Number of block to read Response description 0x00 Command ID 0x93 ICODE_READ_BLOCK Read data Bytes read from the tag. Example: HOST=>READER: 0x93 – ICODE_READ_BLOCK 0x02 – block number 2 0x01 –...

  • Page 52: Write Afi (0X96)

    Command description Argument Size Value Description Command ID 0x95 ICODE_LOCK_BLOCK Block number Response description 0x00 Command ID 0x95 ICODE_LOCK_BLOCK Example: HOST=>READER: 0x95 – ICODE_LOCK_BLOCK 0x02 – block number 2 READER=>HOST: 0x00 – ACK byte 0x95 – related command code ICODE_LOCK_BLOCK 5.6.7 Write AFI (0x96) This command performs a write to Application Family Identifier value inside the TAG memory.

  • Page 53: Write Dsfid (0X98)

    Example: HOST=>READER: 0x96 – ICODE_LOCK_AFI READER=>HOST: 0x00 – ACK byte 0x96 – related command code ICODE_LOCK_AFI 5.6.9 Write DSFID (0x98) This command performs a write to Data Storage Format Identifier value inside the TAG memory. This command takes a one-byte argument representing the DSFID value. Command description Argument Size...

  • Page 54: Get Multiple Bss (0X9B)

    Command description Argument Size Value Description Command ID 0x9A ICODE_GET_SYSTEM_INFORMATION Response description 0x00 Command ID 0x9A ICODE_GET_SYSTEM_INFORMATION System information System information bytes Example: HOST=>READER: 0x9A – ICODE_GET_SYSTEM_INFORMATION READER=>HOST: 0x00 – ACK byte 0x9A – related command code ICODE_GET_SYSTEM_INFORMATION 0x0F 0x04 0x8F 0x7F 0x0A 0x01 0x24 0x16 0xE0 0x00 0x00 0x33 0x03 0x02 –...

  • Page 55: Read Epc (0X9D)

    Command description Argument Size Value Description Command ID 0x9C ICODE_PASSWORD_PROTECT_AFI Response description 0x00 Command ID 0x9C ICODE_PASSWORD_PROTECT_AFI Example: HOST=>READER: 0x9C – ICODE_PASSWORD_PROTECT_AFI READER=>HOST: 0x00 – ACK byte 0x9C – related command code ICODE_PASSWORD_PROTECT_AFI 5.6.14 Read EPC (0x9D) This command reads EPC data from the TAG. The ACK response contains 12-bytes of EPC data. Please refer to the NXP documentation for more information.

  • Page 56: Get Random Number (0X9F)

    Example: HOST=>READER: 0x9E – ICODE_GET_NXP_SYSTEM_INFORMATION READER=>HOST: 0x00 – ACK byte 0x9E – related command code ICODE_GET_NXP_SYSTEM_INFORMATION 0x0F 0x04 0x8F 0x7F 0x0A 0x01 0x24 0x16 0xE0 0x00 0x00 0x33 0x03 0x02 – result bytes 5.6.16 Get random number (0x9F) This command requests a random number from the ICODE TAG. No arguments are required. The ACK response contains a 16-bit random number.

  • Page 57: Write Password (0Xa1)

    XOR Password Response description 0x00 Command ID 0xA0 ICODE_SET_PASSWORD Example: HOST=>READER: 0xA0 – ICODE_SET_PASSWORD 0x02 – write password 0x34 0x76 0x39 0x64 – calculated XOR password READER=>HOST: 0x00 – ACK byte 0xA0 – related command code ICODE_SET_PASSWORD 5.6.18 Write password (0xA1) This command writes a new password to a selected identifier.

  • Page 58: Protect Page (0Xa3)

    0x01 – Read password 0x02 – Write password Password Identifier 0x04 – Privacy password 0x08 – Destroy password Response description 0x00 Command ID 0xA2 ICODE_LOCK_PASSWORD Example: HOST=>READER: 0xA2 – ICODE_LOCK_PASSWORD 0x02 – write password READER=>HOST: 0x00 – ACK byte 0xA2 – related command code ICODE_LOCK_PASSWORD 5.6.20 Protect page (0xA3) This command changes the protection status of a page.

  • Page 59: Lock Page Protection (0Xa4)

    READER=>HOST: 0x00 – ACK byte 0xA3 – related command code ICODE_PAGE_PROTECT 5.6.21 Lock page protection (0xA4) This command permanently locks the protection status of a page. Note that the related passwords have to be transmitted before with ref ICODE_SET_PASSWORD if the page is not public. Command description Argument Size...

  • Page 60: Destroy (0Xa6)

    5.6.23 Destroy (0xA6) This command permanently destroys the label (tag). The destroy password hasto be transmitted before with ICODE_SET_PASSWORD. This command is irreversible and the label will never respond to any command again. This command can take the XOR password argument for the ICODE products that requires this argument. The XOR password calculation method is described in the ICODE_SET_PASSWORD description.

  • Page 61: Read Signature (0Xa9)

    Response description 0x00 Command ID 0xA8 ICODE_ENABLE_64BIT_PASSWORD Example: HOST=>READER: 0xA8 – ICODE_ENABLE_64BIT_PASSWORD READER=>HOST: 0x00 – ACK byte 0xA8 – related command code ICODE_ENABLE_64BIT_PASSWORD 5.6.26 Read signature (0xA9) This command reads the signature bytes from the TAG. No arguments are required. The ACK response contains bytes containing the signature bytes.

  • Page 62: Write Config (0Xab)

    Example: HOST=>READER: 0xAA – ICODE_READ_CONFIG 0x00 – starting block number 0x02 – number of blocks to read READER=>HOST: 0x00 – ACK byte 0xAA – related command code ICODE_READ_CONFIG 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 – result bytes 5.6.28 Write config (0xAB) This command writes configuration bytes to addressed block data from the selected configuration block address.
  • Page 63 Example: HOST=>READER: 0xAB – ICODE_PICK_RANDOM_ID READER=>HOST: 0x00 – ACK byte 0xAB – related command code ICODE_PICK_RANDOM_ID 63 | P a g e www.eccel.co.uk...

  • Page 64: Compliance

    C. The Host device must be affixed with a permanent label that is clearly visible and states the following: “Contains FCC ID: 2ALHY-000537”. Contains IC: 22592-000537”. Please see FCC KDB 784748 D01 Labelling Part 15 &18 Guidelines v08 section 8 and RSP-100 Issue 11 section 3.2 for further details on labelling requirements.

  • Page 65: Labelling

    7. Labelling 1. The board will have silk screen printed on it at the top “10xGenomics RFID Reader v1.1”. 2. The label contains “FCC ID: 2ALHY-000537”, “IC: 22592-000537” and “HVIN: 1.1” text strings and FCC, PSE and CE Mark logos.

  • Page 66: Mechanical Dimensions

    8. Mechanical dimensions All dimensions in millimetres. Figure 8-1. Mechanical dimensions 66 | P a g e www.eccel.co.uk...
  • Page 67 MIFARE, MIFARE Ultralight, MIFARE Plus, MIFARE Classic, and MIFARE DESFire are trademarks of NXP B.V. No responsibility is taken for the method of integration or final use of the RS485 RFID readers More information about the RS485 RFID reader and other products can be found at the Internet site: http://www.eccel.co.uk or alternatively contact ECCEL Technology (IB Technology) by e-mail at: sales@eccel.co.uk...

Table of Contents