User's Manual

ManualsBrandsEccel Technology ManualsElectronics10xRS485 Reader

1 | P a g e www.eccel.co.uk

FCC / ISED, PSE, CE approved

RS485 RFID reader

Eccel part: 000537

User manual

Manual version: v1.1

04/08/2022

Summary of content (67 pages)

PAGE 1
FCC / ISED, PSE, CE approved RS485 RFID reader Eccel part: 000537 User manual Manual version: v1.1 04/08/2022 1|Page www.eccel.co.
PAGE 2
Table of contents 1. Introduction ..........................................................................................................................................................5 2. Electrical specification ...........................................................................................................................................6 2.1 2.2 2.3 2.4 ABSOLUTE MAXIMUM RATINGS ............................................................................................................
PAGE 3
5.3.8 Transfer-Restore value (0x27) ............................................................................................................ 27 5.4 MIFARE ULTRALIGHT COMMANDS............................................................................................................................. 29 5.4.1 Read page (0x40) ............................................................................................................................... 29 5.4.2 Write page (0x41) ...........................
PAGE 4
5.6.6 5.6.7 5.6.8 5.6.9 5.6.10 5.6.11 5.6.12 5.6.13 5.6.14 5.6.15 5.6.16 5.6.17 5.6.18 5.6.19 5.6.20 5.6.21 5.6.22 5.6.23 5.6.24 5.6.25 5.6.26 5.6.27 5.6.28 5.6.29 Lock block (0x95)................................................................................................................................ 51 Write AFI (0x96) ................................................................................................................................. 52 Lock AFI (0x97) ................................
PAGE 5
1.
PAGE 6
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. Symbol TS TA VDDMAX Parameter Storage temperature Ambient temperature Supply voltage Min -40 -40 4.5 Max +125 +85 5.5 Unit °C °C V Table 2-1. Absolute maximum ratings 2.
PAGE 7
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. Figure 3-1. Connectors pinout. GPIO_XX corresponds to GPIO33 on the MCU GPIO_YY corresponds to GPIO21 on the MCU.
PAGE 8
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. The default baud rate is 115200 bps, and can be changed from 9600 up to 115200. Other protocol settings are:  data bits: 8,  parity: None,  Stop bits: 1,  flow control: None. 4.
PAGE 9
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, 0x8fd9, 0x9ff8, 0x6e17, 0x7e36,
PAGE 11
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. At power up, the Reader discovers nearby tags. 2. The Reader should read (header size) bytes from each discovered tag until it finds an address tag. Verify the header CRC. 3.
PAGE 12
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. This frame always contains 1-byte with command ID and optional arguments.
PAGE 13
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 0x0A - Error due to RF.
PAGE 14
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. If you want to perform a full inventory command for ICODE tag types please refer to ICODE_INVENTORY_xxx commands.
PAGE 15
0x0F - JCOP 0x10 – MIFARE Mini TAG parameter UID Example: 1 X N X 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 DSFID - byte for ICODE family tags UID bytes. Max length is 8.
PAGE 16
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. Argument Command ID Size 1 ACK Command ID Example: 1 1 Command description Value Description 0x05 HALT Response description 0x00 0x05 HALT HOST=>READER: 0x05 – HALT READER=>HOST: 0x00 - ACK byte 0x05 - related command code HALT 5.1.
PAGE 17
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. Argument Command ID Size 1 ACK Command ID Example: 1 1 Command description Value Description 0x07 SAVE_KEYS Response description 0x00 0x07 SAVE_KEYS HOST=>READER: 0x07 – SAVE_KEYS READER=>HOST: 0x00 - ACK byte 0x07 - related command code SAVE_KEYS 5.1.
PAGE 18
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
Bus address 1 X X Termination 1 Short name 4 X ACK Command ID Example: 1 1 0x00 0x0B HOST=>READER: 0x0B 0x05 0x81 0x01 0x31 Bus address byte. Default value is 0x80 0x00 – termination disabled 0x01 – termination enabled Four ASCII bytes with device description Response description SET_COMM_SETTINGS – SET_COMM_SETTINGS – baudrate 115200 – new RS485 module own address – termination 0x32 0x33 -x34 – Short name READER=>HOST: 0x00 – ACK byte 0x0B – related command code SET_COMM_SETTINGS 5.1.
PAGE 20
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. Argument Command ID Size 1 ACK Command ID Example: 1 1 Command description Value Description 0x0D FACTORY_RESET Response description 0x00 0x0D FACTORY_RESET HOST=>READER: 0x0D – FACTORY_RESET READER=>HOST: 0x00 – ACK byte 0x0D – related command code FACTORY_RESET 5.1.
PAGE 21
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. After this step, the device will not be able to boot the main application until it is uploaded again to the device.
PAGE 22
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). Argument Command ID Firmware bytes Size Value 1 0xF3 Max. 256 Command description Description FIRMWARE_FRAME Firmware bytes in chunks 256bytes long.
PAGE 23
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. The returned ACK answer contains data read from the specified tag memory.
PAGE 24
Argument Command ID Block number Number of blocks Key A/B parameter Key number Bytes to write ACK Command ID Example: HOST=>READER: Command description Size Value Description 1 0x21 MF_WRITE_BLOCK 1 X 1 Y X 0x0A – Key A should be selected from key storage 1 0x0B – Key B should be selected from key storage 1 0-4 Key number in key storage Bytes to write. Number of this bytes must be number of requested Y*16 XXX blocks multiplied by 16.
PAGE 25
Example: 5.3.4 HOST=>READER: 0x22 0x02 0x0A 0x00 – – – – MF_READ_VALUE block number 2 key A should be selected from key storage first key should be selected from key storage READER=>HOST: 0x00 0x22 0x00 0x01 – ACK byte – related command code MF_READ_BLOCK 0x00 0x00 0x01 – value – address byte Write value (0x23) This command should be used to write a value to the tag.
PAGE 26
Argument Command ID Block number Command description Value Description 0x24 MF_INCREMENT_VALUE X 0x0A – Key A should be selected from key storage X 0x0B – Key B should be selected from key storage 0-4 Key number in key storage X Signed 32-bit value (LSB first) 0x00 – Decrement by delta value X 0x01 – Increment by delta value Response description 0x00 0x24 MF_INCREMENT_VALUE Size 1 1 Key A/B parameter 1 Key number Delta value 1 4 Increment/Decrement 1 ACK Command ID Example: 1 1 HOST=>READER: 0x24
PAGE 27
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 0x02 0x03 0x0A 0x00 – – – – – MF_TRANSFER_RESTORE_VALUE source block number 2 destination block number 3 key A should be selected from key storage first key should be selected from key storage READER=>HOST: 0x00 – ACK byte 0x27 – related command code MF_TRANSFER_RESTORE_BLOCK 28 | P a g e www.eccel.co.
PAGE 29
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. The number of bytes of this data is MIFARE Ultralight page size (4) multiplied by the number of pages to be read.
PAGE 30
HOST=>READER: 0x41 0x02 0x02 0x31 – MFU_WRITE_PAGE – page number 2 – two pages to write 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. The returned ACK answer consists of 8-bytes containing the version information defined by the NXP standard. Please refer to the NXP documentation for more information.
PAGE 31
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.
PAGE 32
Argument Command ID Counter number ACK Command ID Counter value Example: Size 1 1 1 1 3 Command description Value Description 0x46 MFU_READ_COUNTER 0-2 Counter number Response description 0x00 0x46 MFU_READ_COUNTER X Unsigned 24-bit value, LSB first HOST=>READER: 0x46 – MFU_READ_COUNTER 0x01 – counter number READER=>HOST: 0x00 – ACK byte 0x46 – related command code MFU_READ_COUNTER 0x00 0x00 0x01 – value 5.4.
PAGE 33
ACK Command ID PACK Example: 1 1 2 0x00 0x48 X MFU_PASSWORD_AUTH Password acknowledge bytes 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. It takes as an argument one byte with the key number in the key storage.
PAGE 34
0x4A – related command code MFU_CHECKEVENT 0x01 – tearing event occurred 34 | P a g e www.eccel.co.
PAGE 35
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. Argument Command ID Size 1 ACK Command ID Read data Example: 1 1 28 5.5.
PAGE 36
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. Argument Command ID Size 1 ACK Command ID Application IDs Example: 1 1 X*3 5.5.4 Command description Value Description 0x62 MFDF_LIST_APP_IDS Response description 0x00 0x62 MFDF_LIST_APP_IDS X Bytes with applications IDs HOST=>READER: 0x62 – MFDF_LIST_APP_IDS READER=>HOST: 0x00 0x62 0x00 0xAA 0x55 ...
PAGE 37
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. This command can be used with DES and 2K3DES keys. Argument Command ID Key number in storage Key number on card ACK Command ID Example: 5.5.
PAGE 38
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. Argument Command ID Key number Size 1 1 ACK Command ID Example: 1 1 5.5.
PAGE 39
5.5.9 Delete application (0x68) This command tries to delete an application from the tag. It takes one argument with the application ID. Argument Command ID Application ID Size 1 3 ACK Command ID Example: 1 1 Command description Value Description 0x68 MFDF_DELETE_APP X Application ID bytes Response description 0x00 0x68 MFDF_DELETE_APP HOST=>READER: 0x68 – MFDF_DELETE_APP 0x01 0x02 0x03 – application ID READER=>HOST: 0x00 – ACK byte 0x68 – related command code MFDF_DELETE_APP 5.5.
PAGE 40
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.
PAGE 41
Access rights File size 2 3 X X Backup file 1 X ACK Command ID Example: 1 1 0x00 0x6C Please refer to the NXP documentation for more information file size, LSB first 0x00 – Standard file 0x01 – Backup file Response description MFDF_CREATE_DATA_FILE HOST=>READER: 0x6C 0x01 0xEE 0x40 0x01 – MFDF_CREATE_DATA_FILE – file number 0xEE – access rights 0x00 0x00 – file 64-bytes long – backup file READER=>HOST: 0x00 – ACK byte 0x6C – related command code MFDF_CREATE_DATA_FILE 5.5.
PAGE 42
Argument Command ID File number File offset Data length Size 1 1 3 3 ACK Command ID Example: 1 1 HOST=>READER: READER=>HOST: Command description Value Description 0x6E MFDF_READ_DATA X File number inside application X file offset, 3-bytes LSB value X Read data length, 3-bytes LSB value Response description 0x00 0x6E MFDF_READ_DATA 0x6E 0x01 0x00 0x07 0x00 0x6E 0x01 – MFDF_READ_DATA – file number 0x00 0x00 – zero offset 0x00 0x00 – seven bytes to read – ACK byte – related command code MFDF_READ_DATA 0
PAGE 43
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.
PAGE 44
Argument Command ID File number Credit value Size 1 1 4 ACK Command ID Example: 1 1 Command description Value Description 0x72 MFDF_LIMITED_CREDIT X File number inside application X 4 bytes signed value, LSB first Response description 0x00 0x72 MFDF_ LIMITED_CREDIT HOST=>READER: 0x72 – MFDF_ LIMITED_CREDIT 0x02 – file number 0x05 0x00 0x00 0x00 – 4 bytes signed value, LSB first READER=>HOST: 0x00 – ACK byte 0x72 – related command code MFDF_ LIMITED_CREDIT 5.5.
PAGE 45
Argument Command ID File number Access rights Record size Number of records Cyclic flag ACK Command ID Example: Size 1 1 2 2 2 1 1 1 Command description Value Description 0x74 MFDF_CREATE_RECORD_FILE X File number inside application X Please refer to the NXP documentation for more information X Record size, 16-bits LSB value X Number of records, 16-bits LSB value If cyclic file is full: X 0x00 - further writing is not possible unless it is cleared 0x01 - the new record overwrites oldest record Response
PAGE 46
Argument Command ID File number Record number Data length Size 1 1 2 2 ACK Command ID Example: 1 1 HOST=>READER: Command description Value Description 0x76 MFDF_READ_RECORD X File number inside application X Record number, 2-bytes LSB value X Read data length, 2-bytes LSB value Response description 0x00 0x76 MFDF_READ_RECORD 0x76 0x01 0x00 0x08 0x00 0x76 0x00 READER=>HOST: – MFDF_READ_RECORD – file number 0x01 – record number 0x00 – eighth bytes to read – ACK byte – related command code MFDF_READ_REC
PAGE 47
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. The available memory is returned as a 4 byte unsigned LSB value.
PAGE 48
Argument Command ID Size 1 ACK Command ID Example: 1 1 Command description Value Description 0x7B MFDF_COMMIT_TRANSACTION Response description 0x00 0x7B MFDF_COMMIT_TRANSACTION 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. No arguments are required.
PAGE 49
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. Please refer to the NXP documentation for more information.
PAGE 50
Argument Command ID AFI Size 1 1 ACK Command ID UID DSFID 1 1 8 1 More cards flag 1 Command description Value Description 0x91 ICODE_INVENTORY_NEXT X Application Family Identifier Response description 0x00 0x91 ICODE_INVENTORY_NEXT XXX Unique identifier Data Storage Format Identifier X 0x00 – no more cards in range of antenna X 0x01 – more cards in range of antenna Example: 5.6.
PAGE 51
Argument Command ID Block number Block count ACK Command ID Read data Example: 5.6.5 Size 1 1 1 1 1 4*N Command description Value Description 0x93 ICODE_READ_BLOCK X N Number of block to read Response description 0x00 0x93 ICODE_READ_BLOCK XXX Bytes read from the tag.
PAGE 52
Argument Command ID Block number Size 1 1 ACK Command ID Example: 5.6.7 1 1 Command description Value Description 0x95 ICODE_LOCK_BLOCK X Response description 0x00 0x95 ICODE_LOCK_BLOCK HOST=>READER: 0x95 – ICODE_LOCK_BLOCK 0x02 – block number 2 READER=>HOST: 0x00 – ACK byte 0x95 – related command code ICODE_LOCK_BLOCK Write AFI (0x96) This command performs a write to Application Family Identifier value inside the TAG memory. The command takes a one-byte argument representing the AFI value.
PAGE 53
Example: 5.6.9 HOST=>READER: 0x96 – ICODE_LOCK_AFI READER=>HOST: 0x00 – ACK byte 0x96 – related command code ICODE_LOCK_AFI 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.
PAGE 54
Argument Command ID ACK Command ID System information Example: Size 1 1 1 X Command description Value Description 0x9A ICODE_GET_SYSTEM_INFORMATION Response description 0x00 0x9A ICODE_GET_SYSTEM_INFORMATION XXX System information bytes HOST=>READER: 0x9A – ICODE_GET_SYSTEM_INFORMATION READER=>HOST: 0x9A 0x0F 0x16 0x00 – ACK byte – related command code ICODE_GET_SYSTEM_INFORMATION 0x04 0x8F 0x7F 0x0A 0x01 0x24 0xE0 0x00 0x00 0x33 0x03 0x02 – result bytes 5.6.
PAGE 55
Argument Command ID Size 1 ACK Command ID Example: 1 1 Command description Value Description 0x9C ICODE_PASSWORD_PROTECT_AFI Response description 0x00 0x9C ICODE_PASSWORD_PROTECT_AFI 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
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. This value should be used with ICODE_SET_PASSWORD command.
PAGE 57
XOR Password 4 X 1 1 0x00 0xA0 Response description ACK Command ID Example: ICODE_SET_PASSWORD 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. With this command, a new password is written into the related memory.
PAGE 58
Password Identifier ACK Command ID Example: 1 X 1 1 0x00 0xA2 0x01 – Read password 0x02 – Write password 0x04 – Privacy password 0x08 – Destroy password Response description ICODE_LOCK_PASSWORD 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
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.
PAGE 60
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
Response description ACK Command ID Example: 1 1 0x00 0xA8 ICODE_ENABLE_64BIT_PASSWORD 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. Please refer to the NXP documentation for more information.
PAGE 62
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. It takes three arguments: the option byte, the block number and the configuration bytes.
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.
PAGE 64
6. Compliance A. This module has been tested in accordance with FCC rule part 15.225 and ISED RSS-210 using the integrated coil antenna permanently fixed within the product. B. The host product manufacturer is responsible for compliance to any other FCC rules or ISED standards that apply to the host not covered by the modular transmitter certification. E.g.
PAGE 65
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. 3. The size of the label is 15mm x 15mm. 4. The label shall be placed as shown in Figure 7-1 below: Figure 7-1. Reader top side Figure 7-2. Label 65 | P a g e www.eccel.co.
PAGE 66
8. Mechanical dimensions All dimensions in millimetres. Figure 8-1. Mechanical dimensions 66 | P a g e www.eccel.co.
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 67 | P a g e www.eccel.co.