User's Manual

ManualsBrandsEccel Technology ManualsElectronicsRS485 connected RFID reader

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

User Manual- RS485 RFID Reader

1 Installation

Essential Instructions and Requirements for Users of this

Product and Host Equipment Containing This Product

This product has been approved by the Federal Communications Commission (FCC) and Industry Canada

(IC). It is accredited Limited Modular Approval for radio modules under regulations detailed in 47 CFR

15.225 and RSS-210 issue 10 Annex B6.

The product is only for use with a 5V dc (+/- 5%) power supply to it via the J1 connector shown in Picture

1 below.

The host power supply to the product should be rated to be able to deliver up to 300 milliamps of in rush

current for up to 100 milliseconds and supply a constant current of up to 150 milliamps.

This product is only authorised for operation using the integral trace antenna contained on the product.

It is not authorised for use with any other antenna.

RF exposure calculation has been provided with the module certification utilising a worst case 5mm

distance to users, RF exposure in the host equipment may need to be re-evaluated.

Host equipment incorporating this product must have clearly affixed to it a permanent label stating,

“Contains FCC ID: 2ALHY1356NFC-ICC-IC and Contains IC ID: 22592-RS485IC470”.

The host equipment containing this product must itself be tested and verified that it does not exceed the

FCC rules in 47 CFR part 15.225 or RSS-210 Annex B6 including if the host equipment is powered by a

mains AC supply, that it does not exceed the AC powerline conducted emissions limits specified in the

FCC / RSS-GEN test specifications. A host manufacturer has three options available, either:

1) A Class II permissive change (FCC) or a Class IV permissive change (ISED) must be requested

through Eccel Technology Ltd in order to add the host equipment test evaluation data to the

existing certification.

2) The host manufacturer can perform a change in ID followed by a class II permissive change.

3) The host manufacturer can apply for a new FCC ID or IC ID.

This product is only authorised for the following rule: Part 47 CFR 15.225 as listed in the Grant of

Equipment Authorisation and RSS-210 Annex B6 as listed in the Technical Acceptance Certificate.

The host product manufacturer is responsible for compliance to any other FCC and IC rules that apply to

the host not covered by the modular transmitter Grant of Certification/ acceptance certificate.

Summary of content (62 pages)

PAGE 1
User Manual- RS485 RFID Reader 1 Installation Essential Instructions and Requirements for Users of this Product and Host Equipment Containing This Product This product has been approved by the Federal Communications Commission (FCC) and Industry Canada (IC). It is accredited Limited Modular Approval for radio modules under regulations detailed in 47 CFR 15.225 and RSS-210 issue 10 Annex B6. The product is only for use with a 5V dc (+/- 5%) power supply to it via the J1 connector shown in Picture 1 below.
PAGE 2
The RS485 RFID Reader v1 must be connected to the RS485 bus using standard CAT5 (not crossed) LAN cable. Pinout of the RJ45 connecter is describe below. Devices can be connected in a chain, so one device can be connected to another one. Picture 1. RJ45 connector pinout. 2|Page www.eccel.co.
PAGE 3
2 Communication interface 2.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 115200bps, and can be changed from 9600 up to 115200. Other protocol settings are: data bits: 8, parity: None, Stop bits: 1, flow control: None. 2.2 Frame structure Communication with the module is symmetric.
PAGE 4
2.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 5
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 6
3 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. 3.1 Generic commands 3.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 7
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 8
3.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 9
0x10 – Mifare Mini TAG parameter 1 X UID 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 10
Argument Command ID Size 1 ACK Command ID 1 1 Command description Value Description 0x05 HALT Response description 0x00 0x05 HALT Example: HOST=>READER: 0x05 – HALT READER=>HOST: 0x00 - ACK byte 0x05 - related command code HALT 3.1.8 Set key (0x06) This command sets a KEY in Key Storage Memory on a selected slot. Set key can be used for all RFID functions needing authorization like e.g. READ/WRITE memory on the TAG etc.
PAGE 11
3.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 1 1 Command description Value Description 0x07 SAVE_KEYS Response description 0x00 0x07 SAVE_KEYS Example: HOST=>READER: 0x07 – SAVE_KEYS READER=>HOST: 0x00 - ACK byte 0x07 - related command code SAVE_KEYS 3.1.
PAGE 12
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 3.1.12 Get hardware version (0x0A) This command requests a hardware version string from the device.
PAGE 13
Response description ACK Command ID 1 1 0x00 0x0B SET_COMM_SETTINGS Example: HOST=>READER: 0x0B 0x05 0x81 0x01 0x31 – 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 3.1.14 Get communication settings (0x0C) This command gets communication settings.
PAGE 14
Response description ACK Command ID 1 1 0x00 0x0D FACTORY_RESET Example: HOST=>READER: 0x0D – FACTORY_RESET READER=>HOST: 0x00 – ACK byte 0x0D – related command code FACTORY_RESET 3.1.16 Set LED (0x0E) This command turns on/off the external LED. If the On/Off flag is set to 2, then the host must provide a timeout for the LED (two bytes LSB). The device turns on the LED for the specified timeout and then turns it off.
PAGE 15
3.2 Firmware commands The reader supports firmware upgrades. To perform a firmware upgrade, the user must execute the following commands. 3.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 16
3.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 17
3.3 Mifare Classics commands This set of commands should be performed on Mifare Classics tags. 3.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 18
Argument Command ID Block number Number of blocks Command description Value Description 0x21 MF_WRITE_BLOCK X 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 Y*16 XXX requested blocks multiplied by 16.
PAGE 19
Response description ACK Command ID Value Address 1 1 4 1 0x00 0x22 X X MF_READ_VALUE Signed 32-bit value (LSB first) Address byte Example: 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 3.3.4 Write value (0x23) This command should be used to write a value to the tag.
PAGE 20
3.3.5 Increment/decrement value (0x24) This command should be used to increment or decrement a value stored in the tag memory. It takes as arguments the block number where the value is stored, the key A or B parameter, the key number in key storage, value (signed 32-bit LSB first) as 4 bytes to increment or decrement, and the increment/decrement flag.
PAGE 21
HOST=>READER: 0x25 0x02 0x0A 0x00 – – – – MF_TRANSFER_VALUE block number 2 key A should be selected from key storage first key should be selected from key storage READER=>HOST: 0x00 – ACK byte 0x25 – related command code MF_TRANSFER_BLOCK 3.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 22
Key A/B parameter 1 X Key number 1 0-4 ACK Command ID 1 1 0x00 0x27 0x0A – Key A should be selected from key storage 0x0B – Key B should be selected from key storage Key number in key storage Response description MF_ TRANSFER_RESTORE _VALUE 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 –
PAGE 23
3.4 Mifare Ultralight commands This set of commands should be performed on Mifare Ultralight tags. 3.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 24
Example: HOST=>READER: 0x41 0x02 0x02 0x31 write – MFU_WRITE_PAGE – page number 2 – two pages to write 0x35 0x3a 0x33 0x35 0x3a 0x30 0x33 – 32 bytes to READER=>HOST: 0x00 – ACK byte 0x41 – related command code MFU_WRITE_PAGE 3.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 25
Example: HOST=>READER: 0x43 – MFU_READ_SIGNATURE READER=>HOST: 0x00 0x43 0x01 0x31 0x81 0x31 – ACK byte – related command code MFU_READ_SIGNATURE 0x2e 0x41 0x22 0x43 0x11 0x8e 0x20 0x38 0x20 0x32 0x30 0x31 0x39 0x41 0x23 0x42 0x28 0x33 0x01 0x8e 0x72 0x35 0x3a 0x33 0x35 0x3a 0x30 0x33 – signature bytes 3.4.5 Write signature (0x44) This command writes the signature information to the Mifare Ultralight Nano TAG.
PAGE 26
HOST=>READER: 0x45 – MFU_LOCK_SIGNATURE 0x02 – permanent lock READER=>HOST: 0x00 – ACK byte 0x45 – related command code MFU_LOCK_SIGNATURE 3.4.7 Read counter (0x46) This command should be used to read a counter from the TAG. It takes as arguments the counter number. The returned ACK response contains a value as a signed 24-bit value (LSB first).
PAGE 27
3.4.9 Password auth (0x48) This command tries to authenticate the tag using the chosen password. It takes as an argument a password as four bytes. The returned ACK response contains two bytes of password acknowledge (PACK).
PAGE 28
Example: HOST=>READER: 0x49 – MFUC_AUTHENTICATE 0x00 – key number READER=>HOST: 0x00 – ACK byte 0x49 – related command code MFUC_AUTHENTICATE 3.4.11 Check Tearing Event (0x4A) The Check Tearing Event command takes as arguments one byte with the counter number. This command checks whether there was a tearing event in the counter. The returned ACK response contains result byte. The value ‘0x00’ is returned if there has been no tearing event, and ‘0x01’ is returned if a tearing event occurred.
PAGE 29
3.5 Mifare Desfire commands This set of commands should be performed on Mifare Desfire tags. 3.5.1 Get version (0x60) This command requests version information from the tag. The returned ACK answer contains 28-bytes with version information.
PAGE 30
3.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.
PAGE 31
3.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.
PAGE 32
READER=>HOST: 0x00 – ACK byte 0x65 – related command code MFDF_AUTHENTICATE_ISO 3.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 33
0x01 0x02 0x03 – application ID 0xED 0x84 – key settings bytes READER=>HOST: 0x00 – ACK byte 0x67 – related command code MFDF_CREATE_APP 3.5.9 Delete application (0x68) This command tries to delete an application from the tag. It takes one argument with the application ID.
PAGE 34
READER=>HOST: 0x00 – ACK byte 0x69 – related command code MFDF_CHANGE_APP 3.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 35
Command description Argument Size Value Description Command ID 1 0x6C MFDF_CREATE_DATA_FILE File number 1 X File number inside application Access rights 2 X Please refer to the NXP documentation for more information File size 3 X file size, LSB first Backup file 1 X ACK 1 0x00 Command ID 1 0x6B 0x00 – Standard file 0x01 – Backup file Response description MFDF_CREATE_DATA_FILE Example: HOST=>READER: 0x6C – MFDF_CREATE_DATA_FILE 0x01 – file number 0xEE 0xEE – access rights 0x40 0
PAGE 36
READER=>HOST: 0x00 – ACK byte 0x6D – related command code MFDF_WRITE_DATA 3.5.15 Read data (0x6E) This command reads data from standard data files or backup data files. It takes three arguments: the file number, the offset in the file where data is stored, and the number of bytes to be read. The returned ACK response contains the data that has been read.
PAGE 37
Limit credited 1 X Please refer to the NXP documentation for more information Response description ACK 1 0x00 Command ID 1 0x6F MFDF_CREATE_VALUE_FILE Example: HOST=>READER: 0x6F – MFDF_CREATE_VALUE_FILE 0x02 – file number 0xEE 0xEE – access rights 0x00 0x00 0x00 0x00 – low limit 0x80 0x00 0x00 0x00 – up limit 0x00 0x00 0x00 0x00 – initial value 0x01 – get free enabled 0x01 – limited credit READER=>HOST: 0x00 – ACK byte 0x6F – related command code MFDF_CREATE_VALUE_FILE 3.5.
PAGE 38
Argument Size Value Description Command ID 1 0x71 MFDF_CREDIT File number 1 X File number inside application Credit value 4 X 4 bytes signed value, LSB first Response description ACK 1 0x00 Command ID 1 0x71 MFDF_CREDIT Example: HOST=>READER: 0x71 – MFDF_CREDIT 0x02 – file number 0x05 0x00 0x00 0x00 – 4 bytes signed value, LSB first READER=>HOST: 0x00 – ACK byte 0x71 – related command code MFDF_CREDIT 3.5.
PAGE 39
Command ID 1 0x73 MFDF_DEBIT File number 1 X File number inside application Credit value 4 X 4 bytes signed value, LSB first Response description ACK 1 0x00 Command ID 1 0x73 MFDF_DEBIT Example: HOST=>READER: 0x73 – MFDF_DEBIT 0x02 – file number 0x05 0x00 0x00 0x00 – 4 bytes signed value, LSB first READER=>HOST: 0x00 – ACK byte 0x73 – related command code MFDF_DEBIT 3.5.
PAGE 40
READER=>HOST: 0x00 – ACK byte 0x74 – related command code MFDF_CREATE_VALUE_FILE 3.5.22 Write record (0x75) This command writes data to a record file. It takes two arguments: the file number and the data bytes to be written. To store data on the TAG, a commit transaction command is required.
PAGE 41
0x00 0x01 – record number 0x08 0x00 – eighth bytes to read READER=>HOST: 0x00 – ACK byte 0x76 – related command code MFDF_READ_RECORD 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07 - data 3.5.24 Clear records (0x77) This command resets cyclic or lineal record files. It takes as an argument the file number.
PAGE 42
READER=>HOST: 0x00 – ACK byte 0x78 – related command code MFDF_DELETE_FILE 3.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 43
Command description Argument Command ID Size Value Description 1 0x7B MFDF_COMMIT_TRANSACTION Response description ACK 1 0x00 Command ID 1 0x7B MFDF_COMMIT_TRANSACTION Example: HOST=>READER: 0x7B – MFDF_COMMIT_TRANSACTION READER=>HOST: 0x00 – ACK byte 0x7B – related command code MFDF_COMMIT_TRANSACTION 3.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 44
3.6 ICODE (ISO15693) commands This set of commands should be performed on ICODE (ISO15693) TAGs. 3.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 45
Command description Argument Size Value Description Command ID 1 0x91 ICODE_INVENTORY_NEXT AFI 1 X Application Family Identifier Response description ACK 1 0x00 Command ID 1 0x91 ICODE_INVENTORY_NEXT UID 8 XXX Unique identifier DSFID 1 X Data Storage Format Identifier More cards flag 1 X 0x00 – no more cards in range of antenna 0x01 – more cards in range of antenna Example: HOST=>READER: 0x91 – ICODE_INVENTORY_NEXT 0x00 – Application Family Identifier READER=>HOST: 0x00 – ACK
PAGE 46
contains data read from the specified tag memory. The number of bytes of this data is ICODE block size (4) multiplied by the number of blocks to be read. Command description Argument Size Value Description Command ID 1 0x93 ICODE_READ_BLOCK Block number 1 X Block count 1 N Number of block to read Response description ACK 1 0x00 Command ID 1 0x93 ICODE_READ_BLOCK 4*N XXX Bytes read from the tag.
PAGE 47
HOST=>READER: 0x94 – ICODE_WRITE_BLOCK 0x02 – block number 2 0x01 – block count 1 0x35 0x3a 0x30 0x33 – 4 bytes to write READER=>HOST: 0x00 – ACK byte 0x94 – related command code ICODE_WRITE_BLOCK 3.6.6 Lock block (0x95) This command performs a lock block command. Once it receives the lock block command, the TAG permanently locks the requested block. The command takes a one-byte argument representing the block number to be locked.
PAGE 48
HOST=>READER: 0x96 – ICODE_WRITE_AFI 0xAA – new Application Family Identifier value READER=>HOST: 0x00 – ACK byte 0x96 – related command code ICODE_WRITE_AFI 3.6.8 Lock AFI (0x97) This command performs a Lock AFI command on the TAG. When it receives the lock AFI request, the TAG locks the AFI value permanently into its memory.
PAGE 49
Command description Argument Command ID Size Value Description 1 0x99 ICODE_LOCK_DSFID Response description ACK 1 0x00 Command ID 1 0x99 ICODE_LOCK_DSFID Example: HOST=>READER: 0x99 – ICODE_LOCK_DSFID READER=>HOST: 0x00 – ACK byte 0x99 – related command code ICODE_LOCK_DSFID 3.6.11 Get System Information (0x9A) This command performs get system information command on the TAG. No arguments are required. The ACK response contains bytes with system information.
PAGE 50
Command description Argument Size Value Description Command ID 1 0x9B ICODE_GET_MULTIPLE_BSS First block number 1 X Number of blocks 1 N Response description ACK 1 0x00 Command ID 1 0x9B BSS information N X ICODE_GET_MULTIPLE_BSS Blocks security status information Example: HOST=>READER: 0x9B – ICODE_GET_MULTIPLE_BSS 0x00 – starting block number 0x08 – number of BSS to read READER=>HOST: 0x00 – ACK byte 0x9B – related command code ICODE_GET_MULTIPLE_BSS 0x00 0x00 0x00 0x00 0x00 0x00 0
PAGE 51
Command description Argument Size Value Description 1 0x9D ICODE_READ_EPC Command ID Response description ACK 1 0x00 Command ID 1 0x9D EPC information 12 X ICODE_READ_EPC Please refer to the NXP documentation for more information. Example: HOST=>READER: 0x9D – ICODE_READ_EPC READER=>HOST: 0x00 – ACK byte 0x9D – related command code ICODE_READ_EPC 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 – result bytes 3.6.
PAGE 52
3.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 53
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 3.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. Note that the old password has to be transmitted before with ICODE_SET_PASSWORD.
PAGE 54
0x02 – Write password 0x04 – Privacy password 0x08 – Destroy password Response description ACK 1 0x00 Command ID 1 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 3.6.20 Protect page (0xA3) This command changes the protection status of a page. Note that the related passwords have to be transmitted before with ICODE_SET_PASSWORD if the page is not public.
PAGE 55
Command ID 1 0xA2 ICODE_PAGE_PROTECT Example: HOST=>READER: 0xA3 – ICODE_PAGE_PROTECT 0x02 – second block selected 0x01 - ICODE_PROTECT_PAGE_READ_LOW flag selected READER=>HOST: 0x00 – ACK byte 0xA3 – related command code ICODE_PAGE_PROTECT 3.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 56
BSS information N X Blocks protection status information Example: HOST=>READER: 0xA5 – ICODE_GET_MULTIPLE_BPS 0x00 – starting block number 0x08 – number of BSS to read READER=>HOST: 0x00 – ACK byte 0xA5 – related command code ICODE_GET_MULTIPLE_BPS 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 – result bytes 3.6.23 Destroy (0xA6) This command permanently destroys the label (tag). The destroy password hasto be transmitted before with ICODE_SET_PASSWORD.
PAGE 57
ACK 1 0x00 Command ID 1 0xA7 ICODE_ENABLE_PRIVACY Example: HOST=>READER: 0xA7 – ICODE_ENABLE_PRIVACY READER=>HOST: 0x00 – ACK byte 0xA7 – related command code ICODE_ENABLE_PRIVACY 3.6.25 Enable 64-bit password (0xA8) This instructs the label that both Read and Write passwords are required for protected access. Note that both the Read and Write passwords have to be transmitted before with ICODE_SET_PASSWORD.
PAGE 58
Example: HOST=>READER: 0xA9 – ICODE_READ_SIGNATURE READER=>HOST: 0x00 – ACK 0xA9 – related 0x0F 0x04 0x8F 0x16 0xE0 0x00 byte command code ICODE_READ_SIGNATURE 0x7F 0x0A 0x01 0x24 0x00 0x33 0x03 0x02 – result bytes 3.6.27 Read config (0xAA) This command reads multiple 4-byte data chunks from the selected configuration block address. It takes two arguments, the first block number and the number of blocks to read the configuration data.
PAGE 59
Configuration bytes 4 X Response description ACK 1 0x00 Command ID 1 0xAB ICODE_WRITE_CONFIG Example: HOST=>READER: 0xAB – ICODE_WRITE_CONFIG 0x01 – option byte 0x00 – block number 0x00 0x00 0x00 0x00 – config bytes READER=>HOST: 0x00 – ACK byte 0xAB – related command code ICODE_WRITE_CONFIG 3.6.29 Pick random ID (0xAC) This command enables the random ID generation in the tag. This interface is used to instruct the tag to generate a random number in privacy mode.
PAGE 60
4 Compliance A. The user and host equipment that incorporates this RFID reader module must follow all instructions listed in section 1 of this User Manual. B. Changes or modifications to this product not expressly approved by Eccel Technology Ltd could void the user's authority to operate the equipment. C. This device complies with Part 15 of the FCC Rules.
PAGE 61
5 Marking and Labelling of the Product by Eccel Technology Ltd 1. The product shall contain as silkscreen printing the following information, all in capital letters (Picture 55):    The name ‘RS485 RFID READER v3.1’. The FCC ID The ISED number 2. The Serial Number contained on the label affixed to the product shall be formatted as a six-digit number starting from 000001. 3.
PAGE 62
Picture 5-5 62 | P a g e www.eccel.co.