| all | frequencies |
|
|
|
|
exhibits | applications |
|---|---|---|---|---|---|---|---|
| manuals | |||||||
| app s | submitted / available | |||||||
|---|---|---|---|---|---|---|---|---|
| 1 |
|
User Manual 1 | Users Manual | 472.19 KiB | ||||
| 1 |
|
User Manual 2 | Users Manual | 473.02 KiB | ||||
| 1 |
|
User Manual 3 | Users Manual | 283.57 KiB | ||||
| 1 |
|
User Manual 4 | Users Manual | 1.72 MiB | ||||
| 1 | Operational Description | |||||||
| 1 | Cover Letter(s) | |||||||
| 1 | External Photos | |||||||
| 1 | Internal Photos | |||||||
| 1 | ID Label/Location Info | |||||||
| 1 | ID Label/Location Info | |||||||
| 1 | Test Report | |||||||
| 1 | Test Setup Photos |
| 1 | User Manual 1 | Users Manual | 472.19 KiB |
Technical Information Manual Revision n. 2 2 April 2008 Mod. A528 OEM UHF MULTIREGIONAL COMPACT READER NPO:
00101/07:A528X.MUTx/02 Federal Communications Commission (FCC) Notice (Preliminary) This device was tested and found to comply with the limits set forth in Part 15 of the FCC Rules. Operation is subject to the following conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received including interference that may cause undesired operation. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This device generates, uses, and can radiate radio frequency energy. If not installed and used in accordance with the instruction manual, the product may cause harmful interference to radio communications. Operation of this product in a residential area is likely to cause harmful interference, in which case, the user is required to correct the interference at their own expense. The authority to operate this product is conditioned by the requirements that no modifications be made to the equipment unless the changes or modifications are expressly approved by CAEN RFID. CAEN RFID srl 2008 Disclaimer No part of this manual may be reproduced in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of CAEN RFID. Preliminary Product Information: This document contains information for a new product. CAEN RFID reserves the right to modify this product without notice. Preliminary product information describes products that are ready for production, but for which full characterization data is not yet available. CAEN RFID believes that the information contained in this document is accurate and reliable. However, the information is subject to change without notice and is provided AS IS without warranty of any kind
(Express or implied). You are advised to obtain the latest version of relevant information to verify, before placing orders, that information being relied on is current and complete. All products are sold subject to the terms and conditions of sale supplied at the time of order acknowledgement, including those pertaining to warranty, patent infringement, and limitation of liability. No responsibility is assumed by CAEN RFID for the use of this information, including use of this information as the basis for manufacture or sale of any items, or for infringement of patents or other rights of third parties. NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
2 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 INDEX 1. INTRODUCTION..................................................................................................................................................5 2. MOD. A528 TECHNICAL SPECIFICATIONS .................................................................................................6 2.1. MOD. A528 TECHNICAL SPECIFICATIONS TABLE..............................................................................................6 2.2. EXTERNAL CONNECTIONS..................................................................................................................................7 2.2.1. A528 Main connector pinout...................................................................................................................8 2.2.2. A528 MAIN connector electrical characteristics .....................................................................................9 2.2.3. Power supply connection........................................................................................................................10 2.2.4. General purpose I/O connections...........................................................................................................10 2.2.5. External reset..........................................................................................................................................11 2.2.6. UART connection....................................................................................................................................12 A528 recovery.........................................................................................................................................12 2.2.7. 2.2.8. A528 USB connector pinout ..................................................................................................................13 2.2.9. USB connector pinout electrical characteristics...................................................................................14 2.2.10. Antenna port specifications ....................................................................................................................14 2.3. READER TAG LINK PROFILES ........................................................................................................................15 2.4. HOST COMMUNICATION INTERFACES...............................................................................................................15 2.5. A528 FIRMWARE UPGRADE ............................................................................................................................16 A528 USB Recovery/FW upgrade ..........................................................................................................17 A528 RS232 FW upgrade.......................................................................................................................18 Regulatory Compliance (FCC)...............................................................................................................19 2.5.1. 2.5.2. 2.5.3. LIST OF FIGURES FIG. 1-1: MOD. A528 OEM UHF MULTIREGIONAL COMPACT READER.....................................................................5 FIG. 2-1: MOD. A528 TECHNICAL DRAWINGS............................................................................................................7 FIG. 2-2: MOD. A528 POWER SUPPLY CONNECTION.................................................................................................10 FIG. 2-3: MOD. A528 GPIO CONNECTION EXAMPLE ...............................................................................................11 FIG. 2-4: MOD. A528 EXTERNAL RESET...................................................................................................................11 FIG. 2-5: MOD. A528 RS232 CONNECTION .............................................................................................................12 FIG. 2-6: MOD. A528 TST-RECOVERY CONNECTION...............................................................................................13 FIG. 2-7: MOD. A528 USB INTERFACE CONNECTION ..............................................................................................13 FIG. 2-8: MOD. A528 DEBUG SHELL WINDOW .........................................................................................................18 NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
3 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 LIST OF TABLES TABLE 2.1: MOD. A528 TECHNICAL SPECIFICATIONS ...............................................................................................6 TABLE 2: A528 MAIN CONNECTOR PINOUT..............................................................................................................8 TABLE 2.3: A528 MAIN CONNECTOR ELECTRICAL CHARACTERISTICS .......................................................................9 TABLE 2.4: USB CONNECTOR ELECTRICAL SPECIFICATIONS ...................................................................................13 TABLE 2.5: A528 USB CONNECTOR ELECTRICAL CHARACTERISTICS ......................................................................14 TABLE 2.6: RF PORT PINOUT ...................................................................................................................................14 TABLE 2.7: RF PORT ELECTRICAL CHARACTERISTICS..............................................................................................15 TABLE 2.8: A528 READER - TAG LINK PROFILES......................................................................................................15 NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
4 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 1. Introduction The A528 is an OEM UHF multiregional compact reader for integration into label printers, label applicators, handheld devices and in general any fixed or mobile short and medium range device requiring UHF tag programming and reading. The A528 can operate in both European (ETSI EN 302 208) and US (FCC part 15) regulatory environments and is fully programmable up to 500 mW conducted power. The reader supports EPC Class1 Gen2 protocol. The module uses the Intel UHF RFID Transceiver R1000 and features a Gen2 Dense Reader Mode capability. Due to its multiregional capabilities the A528 is ideal for integration in devices requiring compliance to different geographic regions. A service board (Mod. A528ADAT), which allows to manage the A528 via USB and RS232, is available. Fig. 1-1: Mod. A528 OEM UHF Multiregional compact reader NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
5 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 2. Mod. A528 Technical Specifications 2.1. Mod. A528 Technical Specifications Table Table 2.1: Mod. A528 Technical Specifications Frequency band Output Power Level Output power accuracy Antenna VSWR requirement Antenna Connector Frequency Tolerance Number of Channels Standard Compliance Digital I/O UART Serial Port 902928 MHz (FCC part 15) 865.600867.600 MHz (ETSI EN 302 208) Programmable in 8 steps1 up to 500 mW @ 5 V (27 dBm)
+/- 1dB 2:1 or better for optimum performances Nr. 1 MMCX type 10 ppm over the entire temperature range 10 channels (compliant to ETSI EN 302 208) 50 hopping channels (compliant to FCC part 15) EPC C1G2 Four I/O lines 3.3V out @ 3mA, 5V tolerant Baudrate: 115200 Databits: 8 Stopbits: 1 Parity: none Flow control: none 3.3 V out, 5 V tolerant 9.6115 kbit/s data rate (settable) USB Device Port Dimensions One USB 2.0 Full Speed (12 Mbits per second) device port. 42 x 60 x 6.3 mm3 (1.65 x 2.36 x 0.25 inches3) Supply voltage requirements Electrical Power Operating Temperature MTBF Weight 4.75V 5.25V; ripple and noise < 100mVpp; ripple frequency >
100kHz 1A max @ 5 V (TX/RX mode)2, 230 mA @ 5 V (idle mode)
-20 C to 60 C
> 200'000 hours 16 g 1 Output power levels are the following: 10mW; 25mW; 50mW; 100mW; 200mW; 300mW; 400mW and 500mW 2 Typical supply current values @ 5V in TX/RX mode are the following: 0.50A @ Pout=50mW; 0.68A @ Pout=200mW; 0.80A
@ Pout=500mW NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
6 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 2.2. External connections The location of the connectors is shown in Fig. 2.1. Their mechanical specifications are listed here below:
Antenna Port: RF Coax Connector Huber+Suhner type 82MMCX-S50-0-2/111_K (to be used with Huber+Suhner type 11MMCX-50-1-1/111_O) MOLEX Connector: PCB Headers Molex type 53261-1290
(to be used with Molex Type 51021-1200 + 12pcs crimp terminal type 50058-8100) MOLEX Connector: PCB Headers Molex type 53261-0290
(to be used with Molex Type 51021-0200 + 2pcs crimp terminal type 50058-8100) 0 2 2
. 24.55 25.15 5.20 4.00 12.25 12.85 0 6 1
. 2 4 7
. 4.72 31.80 5.48 8 5 2
. O 2.70 2.58 0 9 5
. 0 9 2
. 36.84 42.00 O 2.70
. 2 4 7 2
. 0 0 0 6 O 2.70
. 2 4 7 2 2.58 8 5 2
. 0 3 6
. Fig. 2-1: Mod. A528 technical drawings NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
7 t r o p a n n e n A t Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 2.2.1. A528 Main connector pinout Compact reader A528 MAIN external connector is a Molex SMD, 12 poles, 1.27 pitch connector whose pinout is shown in table below. Table 2: A528 MAIN connector pinout Pin Function Power Line (+5V) 1 2
/RESET 3 GPIO0 4 GPIO1 5 GPIO2 6 GPIO3 7 8 USB PUP 9 RXD 10 TXD 11 GND 12 GND TST_RECOVERY Direction
IN IN/OUT IN/OUT IN/OUT IN/OUT IN IN IN OUT
The GPIO0-GPIO3 pin are 4 general purpose bidirectional pins, their default direction (or after a Reset) is OUT. TST_RECOVERY pin is reserved and shall be used only to perform the microcontroller recovery procedure during which it must be forced at high level (3.3V or 5V). The RXD/TXD pins are used to communicate with the A528 board via UART port; to establish a link with the device you must configure your COM port as follows3:
1. Baud rate : 115200 2. Parity 3. Data bits 4. Stop bits 5. Flow Control: none
: None
: 8
: 1 3 Since A528 RX/TX are TTL level signals, in order to connect it with a PC, a TTL/RS232 translator shall be used. A528 service board (A528ADAT) hosts both RS232 and USB full interfaces. NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
8 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 2.2.2. A528 MAIN connector electrical characteristics Table 2.3: A528 main connector electrical characteristics Pin name Pin No. Parameter Min. Typ. Max. Unit Supply DC voltage 4.75 5.00 5.25 V
+5V 1
/RESET 2 Power supply requirements Ripple Voltage Power supply requirements - Ripple Frequency Supply DC current VIL VIH Internal pull-up resistance GPIO[0:3]
3, 4, 5, 6 TST-
Recovery USB PUP RXD 7 8 9 TXD 10 GND 11,12 Pulse width VOL VOH Output current VIL VIH Input current VIH VIH VIL VIH Input current VOL VOH Output current 100 0.23
-0.3 2.4 10 1 0 2.0
-0.3 2.0 2.0 2.0
-0.3 2.0 0 2.4 20 100 mVpp kHz 1.0 1.0 3.6 0.4 3.3 3.0 0.8 5.5 1 5.5 5.5 0.8 5.5 1 0.4 3.3 1.5 A V V k s V V mA V V A V V V V A V V mA NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
9 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 2.2.3. Power supply connection In the following schematic suggested A528 power supply connection is shown. The use of fuse F1 is recommended since A528 doesn't provide internal current limitation protection. Diode D1 avoid damage to the reader in case of reverse polarity connection. The use of optional LC filter improves reader immunity in presence of noisy power supply. In order to ensure the correct operation of the reader the power supply shall not enter in burst mode (switching frequency less than 100kHz) when A528 reader is in idle mode
(supply current less than 0.2A). As a rule of thumb the power adapter shall have a maximum current rating from 1A to 1.5A. Fig. 2-2: Mod. A528 power supply connection 2.2.4. General purpose I/O connections The GPIO0-GPIO3 pins are 4 general-purpose bidirectional pins. Their default direction after a power on reset or a general reset is set to Output. GPIO, when configured as Outputs, can be used to drive indicators as leds or buzzers or to send trigger signal to others equipments. GPIO, when configured as Inputs, can accept control signals from other equipments or trigger signals from sensors (i.e. photocells). In the following schematic an example of application of GPIO is shown. NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
10 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 Fig. 2-3: Mod. A528 GPIO connection example 2.2.5. External reset A528 manual reset can be performed by forcing at low level /RESET pin for 1S at least.
/RESET pin is pulled-up by an internal resistor. Fig. 2-4: Mod. A528 external reset NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
11 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 2.2.6. UART connection The RXD/TXD pins are used to communicate with the A528 board via UART port. Since A528 RX/TX are TTL level signals, in order to connect it with a PC, a TTL/RS232 translator shall be used (please refer to the diagram below)4. To establish a link with the device host COM port shall be configured as follows:
1. Baud rate: 115200 2. Parity: None 3. Data bits: 8 4. Stop bits: 1 5. Flow Control: none Fig. 2-5: Mod. A528 RS232 connection 2.2.7. A528 recovery TST_RECOVERY pin is reserved and shall be used only to perform the microcontroller recovery procedure during which it must be forced at high level (3.3V or 5V). In the following diagram a manual recovery mechanism is shown: in order to perform the A528 boot recovery the jumper JP1 shall be inserted, then A528 shall be switched on by applying 5V supply voltage for 5s at least. After that the reader shall be switched off and the jumper removed: at the next switch on the reader will execute the boot recovery program. For further details please see 2.5. 4 A528 service board (A528ADAT) hosts both RS232 and USB full interfaces. NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
12 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 Fig. 2-6: Mod. A528 TST-recovery connection 2.2.8. A528 USB connector pinout A528 USB interface connector is a Molex SMD, 2 poles, 1.27 pitch connector whose pinout is shown in table below. Table 2.4: USB connector electrical specifications Pin Function 1 DDM 2 DDP Direction Description IN/OUT USB data -
IN/OUT USB data +
A528 board provides only the USB data signals; in order to implement a full USB interface some external components shall be used. The external circuit necessary for A528 USB operation is shown in the schematic below. Fig. 2-7: Mod. A528 USB interface connection NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
13 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 2.2.9. USB connector pinout electrical characteristics Pin name Pin No. Parameter Min. Typ. Max. Unit DDM DDP 1 2 VIL VIH VOL VOH Recommended external series resistor VIL VIH VOL VOH 2 0 2.8 2 0 2.8 0.8 0.3 3.3 27 0.8 0.3 3.3 Recommended external series resistor 27 Table 2.5: A528 USB connector electrical characteristics 2.2.10. Antenna port specifications V V V V V V V V In the following table the pinout of A528 antenna is shown. Pin INNER OUTER Function RF OUT GND Direction OUT
Description RF output Ground Table 2.6: RF port pinout NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
14 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 Parameter RF output power Output power vs. power setting accuracy RF port impedance Recommended antenna VSWR Min. 10 10 Typ. 50 Max. 500 27 1 2:1 Unit mW dBm dB
Table 2.7: RF port electrical characteristics 2.3. Reader Tag link profiles A528 reader supports different modulation and return link profiles according to EPC Class1 Gen2 protocol. In the following table are reported all profiles that have been tested for the compliance with ETSI and FCC regulations. Link profile #
0 1 2 3 4 5 Regulation ETSI - FCC ETSI ETSI - FCC ETSI FCC FCC Modulation DSBASK; f=40kHz DSBASK; f=40kHz PR-ASK; f=40kHz PR-ASK; f=40kHz DSB-ASK; f=160kHz PR-ASK; f=40kHz Return Link FM0; f = 40kHz Miller (M=2); f = 160kHz Miller (M=4); f = 250kHz Miller (M=4); f = 300kHz FM0; f = 400kHz Miller (M=2); f = 250kHz Table 2.8: A528 reader - tag link profiles 2.4. Host communication interfaces A528 reader allows the user to manage host communication through two different protocols5:
1. CAEN communication protocol. In this case the host-reader interface is serial and A528 is fully compatible with all the CAEN Demos and libraries included in the Easy2Read SDK. Intel communication protocol. In this case the host-reader interface is USB and A528 is fully compatible with 2. 5 Serial / CAEN procotol is implemented starting from FW release 1.1.5. NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
15 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 Intel RFID Tracer and libraries included in the Intel SDK. Using Intel protocol, serial interface has debug purpose only. The default setting of the A528 reader is the Serial/CAEN choice, in order to switch to the INTEL protocol on USB interface you shall follow the steps described below:
1. Connect to the reader, using a RS232 cable6, with the Hyperterminal (or with any other terminal emulation application) with the following settings:
- baud rate:
- data bits:
- parity:
- stop bits:
- Flow control:
115200 8 none 1 None 2. Type quickly the word "CAEN" (in capital letters) in theHyperterminal window. 3. Type "chgprot" in the hyperterminal window 4. Select the "USB interface" and "INTEL protocol" options when prompted. After a reset the reader will reply to the INTEL commands. In order to switch from Serial/CAEN protocol to the INTEL protocol on USB interface you shall follow the steps described below:
1. Connect to the reader, using a RS232 cable7, with the Hyperterminal (or with any other terminal emulation application) with the following settings:
- baud rate:
- data bits:
- parity:
- stop bits:
- Flow control:
115200 8 none 1 None 2. Stop the boot process pressing the spacebar within 6 seconds from the power on. 3. Type "chgprot" in the hyperterminal window. 4. Select the "Serial interface" and "CAEN protocol" options when prompted. After a reset the reader will reply to the CAEN commands. 2.5. A528 Firmware Upgrade The A528 reader firmware upgrade can be performed via USB or RS2328 interface. 6 7 8 Assuming to use A528 adapter board and a PC as host Assuming to use A528 adapter board and a PC as host Assuming to use A528 adapter board and a PC as host NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
16 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 2.5.1. A528 USB Recovery/FW upgrade USB upgrade is based on Atmel Smart Arm Microcontroller Boot Assistant (hence forth referred to as SAM-BA). The SAM-BA tools is distributed by Atmel via http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3883
(download and install AT91-ISP.exe file). USB upgrade requires the following steps:
1. With power supply disconnected, connect with a short circuit J1 pin 4 (GPIO4) and TP1 pad. 2. With short circuit inserted connect the power supply to the board and wait for 5 seconds at least. 3. Disconnect the power supply. 4. Remove the short circuit between pin 4 of J1 and TP1. 5. Connect the power supply and the USB cable to A528ADAT. 6. At this point, Windows XP will detect the platform (in SAM-BA mode) and display the Found New Hardware Wizard. 7. The first screen asks if Windows can connect to Windows Update to search for the software, select: No, not this time and then click the NEXT button. 8. On the next wizard screen, select: Install the software automatically, then click the NEXT button. 9. A dialog will popup indicating that the driver has not passed Windows Logo Testing, click the CONTINUE ANYWAY button. 10. When the last screen appears, click the Finish button to dismiss the New Hardware Wizard 11. Reboot PC when prompted. 12. Run the SAM-BA v2.6 application on the WinXP host machine 13. When a dialog box appears, ensure AT91SAM7S256-EK is selected in the drop down list then click on the "USB connection" button. Note that a number of the names in the dropdown list are similar so ensure you select the correct one. 14. Ensure the "FLASH" tab is selected. 15. Enter the path in the "Send File Name:" or use the corresponding "Browse" button to find and select the file containing the new firmware. Latest release can be downloaded from CAEN RFID website (http://www.caen.it/rfid) 16. Click the "Send File" button. 17. Click "Yes" in response to "Do you want to unlock involved lock region(s)". Click
"No" in response to "Do you want to lock involved lock region(s)". Finally - confirm the programming by clicking the "Compare sent file with memory" button. When SAM-BA reports that the files are identical click the OK button. 18. Exit the SAM-BA application via the File -> Quit option. 19. To ensure correct behaviour of Windows XP, click the Safely Remove Hardware icon in the Windows system tray, and Stop the Atmel Test Board entry and power DOWN your A528ADAT (disconnect power supply) NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
17 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 2.5.2. A528 RS232 FW upgrade To perform the FW upgrade via RS-232 interface these steps shall be followed:
1. Turn off the reader 2. Connect the reader with the RS232 serial cable to your PC using the adapter board A528ADAT. 3. Setup a serial terminal (such hyperterminal available on all windows OS) with the following settings:
- baud rate:
- data bits:
- parity:
- stop bits:
- Flow control:
4. Turn on the reader. 115200 8 none 1 None If A528 is configured to use INTEL protocol a boot message (see Fig. 2-8 ) will appear press the space bar within 6 seconds from boot. Fig. 2-8: Mod. A528 debug shell window If A528 is configured to use CAEN protocol no boot message will appear: in this case you shall type quickly and in capital letters the word CAEN. 5. After that in both cases a prompt ">" should be displayed. The reader is waiting for commands to be sent over the serial port. 6. Type "upgrade", press return and disconnect the serial port NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
18 Document type:
User's Manual (MUT) Title:
Mod. A528 OEM UHF Multiregional compact reader Revision date:
02/04/2008 Revision:
2 7. Launch the upgrade tool (AT91SAM7SERIALBOOT.exe) provided into CAEN SDK CD-ROM on your PC. 8. Select the COM port you are using (typically is COM1) with the radio button on the left of the main window and press the connect button. 9. Click the Open button and Browse until you find the .bin firmware upgrade image 10. Press the Download button. If, for any reason, the upgrade procedure fails, do not power off the reader but press the download button again. 11. At the end power off the reader and power it on again. Firmware upgrade has been completed. If some problems occur in this procedure the recovery of module operation can be obtained by performing the procedure described in 2.5.1. 2.5.3. Regulatory Compliance (FCC) This equipment has been tested and found to comply with Part 15 of the FCC Rules. NOTE:
(a) Any changes or modification not approved by CAEN RFID could void the users authority to operate the equipment.
(b) The A528 Module, which is rated at 500 mW output, are approved for operation with the CAENRFID antenna Mod. WANTENNAX010 (Linear polarized 3dBi gain 915 MHz PIFA antenna). Use of other than the approved antenna with this unit may result in harmful interference with other users, and cause the unit to fail to meet regulatory requirements. Professional installation is required for A528 Module. NPO:
00101/07:A528X.MUTx/02 Filename:
A528_REV02.DOC Number of pages:
19 Page:
19
| 1 | User Manual 2 | Users Manual | 473.02 KiB |
NPO:
00117/03:PROTx.MUTx/05 Technical Information Manual Revision n. 5 02 April 2008 CAEN RFID UHF READERS COMMUNICATION PROTOCOL Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 INDEX 1. INTRODUCTION..................................................................................................................................................3 1.1. CAEN RFID UHF RFID READER NAMING CONVENTIONS...............................................................................3 2. PROTOCOL SPECIFICATION ..........................................................................................................................4 3. ASYNCHRONOUS NOTIFICATION: PROTOCOL SPECIFICATION .....................................................28 4. DEFAULT CONFIGURATION .........................................................................................................................29 5. SAMPLES.............................................................................................................................................................31 6. REFERENCES .....................................................................................................................................................32 LIST OF TABLES TABLE 1.1: CAEN RFID NAME ABBREVIATION ........................................................................................................3 TABLE 2.1: ATTRIBUTE TYPES...................................................................................................................................5 TABLE 2.2: COMMAND CODES.................................................................................................................................11 TABLE 3.1: ATTRIBUTE TYPES: NOTIFICATION AVP LIST. .....................................................................................28 TABLE 4.1: A928 AND A948 CONFIGURATION PARAMETERS DEFAULT VALUES......................................................29 TABLE 4.2: A928 AND A948 DEFAULT COMPOSITION OF SOURCES .........................................................................29 TABLE 4.3: A828, A829, A829, A946 AND A949 CONFIGURATION PARAMETERS DEFAULT VALUES.....................30 TABLE 4.4: A828, A829, A946 AND A949 DEFAULT COMPOSITION OF SOURCES...................................................30 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
2 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 1. Introduction This document describes the message format of the communication protocol used by the host and the reader in order to issuing commands and reply with responses. The protocol is based on the Attribute Value Pair (AVP) schema and foresees a message header in order to identify the message scope. The command set and the firmware architecture draw inspiration from the Reader Protocol 1.0 specification draft from EPCGlobal but, at now, this protocol is not fully compatible with the same last specifications. Message fields are described left to right, with the most significant byte on the left and the least on the right. 1.1. CAEN RFID UHF RFID Reader Naming conventions The following table describes CAEN RFID reader name abbreviation used in the following paragraph Table 1.1: CAEN RFID name abbreviation Name Abbreviation CAEN RFID Reader A528 A828 A528 - OEM UHF multiregional Compact Reader A828EU - OEM UHF compact reader (ETSI EN 300 220) A828US - OEM UHF compact reader (FCC Part 15) A828AEU - OEM UHF enhanced compact reader (ETSI EN 300 220) A829EU - Fully integrated UHF compact reader (ETSI EN 300 220) A829US - Fully integrated UHF compact reader (FCC Part 15) A941MEI - IP65 UHF stand alone reader (ETSI EN 302 208) A941MEO - OEM UHF stand alone reader (ETSI EN 302 208) A941MUI - IP65 UHF stand alone reader (FCC Part 15) A941MUO - OEM UHF stand alone reader (FCC Part 15) A949EU - IP65 UHF stand alone reader (ETSI EN 302 208) A946EU - OEM UHF stand alone reader (ETSI EN 302 208) A928EU - UHF long range reader (ETSI EN 300 220) A948EU - UHF long range reader (ETSI EN 302 208) A948EU - UHF long range reader DRM (ETSI EN 302 208) A948US - UHF long range reader (FCC part 15) A948EU - UHF long range reader HS (ETSI EN 302 208) A828A A829 A941 A949 A946 A928 A948 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
3 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 2. Protocol specification CAEN RFID UHF RFID Reader protocol uses two logical communication channels: one for synchronous commands and one for asynchronous notifications. Command channel is mandatory and, at now, it is implemented on top of a TCP/IP socket (port 1000) and on RS232 while notification channels are implemented only with sockets. All the messages (commands, responses and notifications) are composed by a header and a body. In all cases the body of the message is a list of attribute-value pairs. Responses always echo the Command AVP sent by the host. All the packets for the control and notification channel share a common header format:
1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
| FIXED | Message ID |
| Vendor ID |
| Length |
FIXED: Must be 0x8001 for commands and 0x0001 for responses. Message ID: Id of the message. It is a sequence number used to map requests to its responses: a request and its corresponding response have the same message ID (the id is local to the channel). Vendor ID: Must be 21336: the IANA SMI Network Management Private Enterprise Code assigned to CAEN SpA. Length: Encodes the length of the message (in bytes) including the header. The header is followed by a list of AVPs the number of which depends on the command. Each AVP have the following format:
1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
| RESERVED | Length |
| Attribute Type | Attribute Value |
| [ until length is reached ] |
RESERVED: The first 16 bits are reserved for future extensions. All reserved bits must be set to 0 on outgoing messages and ignored on incoming messages. Length: Encodes the length of the AVP packet including the length and the reserved fields. Attribute type: A 2 byte code identifying the attribute type. Attribute value: The actual attribute value according to the type. It follows immediately after the Attribute Type field and runs for the remaining bytes indicated in the Length (i.e. Length minus 6 bytes of header). NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
4 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Table 2.1: Attribute types Description CommandName: the command to be executed. All the commands are specified in the relevant table. Attribute value is 2 bytes long. ResultCode: a code representing an indication on the result of the command. All the commands are specified in the relevant table. Attribute value is 2 bytes long. EventType: the type of the notified event. Attribute value is 4 bytes long and can assume the following values:
0x00 = Unknown Event 0x01 = Tag glimpsed 0x02 = Tag New 0x03 = Tag Observed 0x04 = Tag Lost 0x05 = Tag Purged TagIDLen: the length of the tag ID. Attribute value is 2 bytes long. TimeStamp: an indication of the time. Attribute is 8 bytes long and must be interpreted as follow:
the 4 least significant bytes are the seconds elapsed from the 1 January 1970. the 4 most significant bytes are the micro-seconds. TagID: the ID read from the tag. Attribute value has a maximum length of 12 bytes. For ISO18000 tags only the first 8 bytes are significant while for EPC tags all the 12 bytes are significant. ChannelName: the name of the notification channel. Attribute value has a maximum length of 30 bytes. ChannelAddress: the address of the notification channel. Attribute value has a maximum length of 30 bytes. TriggerName: the name of the trigger. Attribute value has a maximum length of 30 bytes. TriggerType: the type of the trigger. Attribute value has a maximum length of 30 bytes. Code 0x01 0x02 0x0E 0x0F 0x10 0x11 0x1E 0x1F 0x20 0x21 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
5 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code 0x22 0x4D 0x4E 0x4F 0x50 0x51 0x52 0x53 0x54 0x56 Description ReadPointName: a string representing the name of the read point. Attribute value has a maximum length of 5 bytes and can assume the following values:
Ant0, Ant1, Ant2, Ant3 TagValue: data read from the tag memory (when applicable). Attribute value has a maximum length of 128 bytes. TagAddress: the memory location address of the tag where read or write data (when applicable). Attribute value is 2 bytes long. RESERVED. Length: a value representing the length of a parameter. Attribute value is 2 bytes long. BitRate: a value representing the RF BitRate. Attribute value is 2 bytes long and can assume the following values:
0x0 Transmit = 10kbit, Receive = 10kbit 0x1 Transmit = 10kbit, Receive = 40kbit 0x2 Transmit = 40kbit, Receive = 40kbit 0x3 Transmit = 40kbit, Receive = 160kbit PowerGet: a value representing the RF power. Attribute value is 4 bytes long. (used for read the current setting) RESERVED. Protocol: a value representing the air protocol. Attribute value is 4 bytes long and can assume the following values:
0x00 = ISO18000-6B 0x01 = EPCC1G1 0x02 = ISO18000-6A 0x03 = EPCC1G2 ReadPointStatus: a value representing the antennas status. Attribute value is 4 bytes long and can assume the following values:
0x00 = Bad: antenna is not connected or broken. 0x01 = Poor: antenna has a low quality connection. 0x02 = Good: antenna is well connected. NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
6 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code 0x57 0x58 0x59 0x5A 0x5B 0x5C 0x5D 0x5E 0x5F 0x60 Description Boolean: a value representing a boolean data. Attribute value is 2 bytes long and can assume the following values:
0x00 = FALSE. Not 0x00 = TRUE. IPAddress: a string representing an IP address formatted with the standard IP dotted decimal format. Attribute value has a maximum length of 30 bytes. IPNetMask: a string representing an IP netmask formatted with the standard IP dotted decimal format. Attribute value has a maximum length of 30 bytes. IPGateway: a string representing an IP address formatted with the standard IP dotted decimal format. Attribute value has a maximum length of 30 bytes. DESBEnable: used to enable/disable the Data Exchange Status Bit handling for ISO18000-6b and EPC 1.19 anti-collision algorithm. Attribute value is 2 bytes long and can assume the following values:
0x00 = Disable the DESB handling. Not 0x00 = Enable the DESB handling. FWRelease: a string representing the devices firmware revision. Attribute value has a maximum length of 200 bytes. DESBStatus: used to check the Data Exchange Status Bit handling for ISO18000-6b and EPC 1.19 anti-collision algorithm. Attribute value is 2 bytes long and can assume the following values:
0x00 = DESB handling is not enabled. Not 0x00 = DESB handling is enabled. EPCPWD: a value representing an EPC tag password. Attribute value is 2 bytes long. RFOnOff: used to start the generation of a continuous wave for test purposes. Attribute value is 2 bytes long and can assume the following vaules:
0x00 = Stop the wave generation. Not 0x00 = Start the wave generation. BaudRate: a value representing the baudrate setting of serial port. Attribute value is 4 bytes long. NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
7 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code 0x61 0x62 0x63 0x64 0x65 0x66 0x67 0x68 Description DataBits: a value representing the databits setting of serial port. Attribute value is 4 bytes long. StopBits: a value representing the stopbits setting of serial port. Attribute value is 4 bytes long. Parity: a value representing the parity setting of serial port. Attribute value is 4 bytes long and can assume the following values:
0x00 = No parity 0x01 = Odd parity 0x02 = Even parity FlowCtrl: a value representing the flow control setting of serial port. Attribute value is 4 bytes long and can assume the following values:
0x00 = No flow control 0x01 = Hardware flow control 0x02 = Software flow control (not yet implemented) DateTime: a value representing a date and time. Attribute value has a maximum length of 30 bytes. The data format is:
YYYYMMDD HH:MM:SS SelUnselOp: a value representing the tag selection operation defined by the ISO18000-6B protocol. Attribute value is 2 bytes long and can assume the following values:
0x00 = select equal 0x01 = select not equal 0x02 = select greater than 0x03 = select lower than 0x04 = unselect equal 0x05 = unselect not equal 0x06 = unselect greater than 0x07 = unselect lower than Bitmask: a value representing the bitmask parameter of tag selection operations defined by the ISO18000-6B protocol. Attribute value is 2 bytes long (only 8 least significant bits are used). REESERVED. NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
8 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code 0x69 0x6A 0x6B 0x6C 0x6D 0x6E 0x6F 0x70 Description IORegister: a value representing the status of the I/O lines of the reader. Where input lines are separated from output ones, input lines are mapped on the less significant bits while outputs are mapped on the most significant. Attribute value is 4 bytes long (effective used bits depend on the reader model). ConfigParameter: a value representing a configuration parameter. Attribute value is 4 bytes long and can assume the following values:
0x00 = ReadCycle configuration 0x01 = Observed Threshold configuation 0x02 = Lost Threshold configuration ConfigValue: a value for the configuration parameter. Attribute value is 4 bytes long. NoOfTriggers: a value representing the number of triggers. Attribute value is 2 bytes long. NoOfChannels: a value representing the number of channels. Attribute value is 2 bytes long. EventMode: a value representing the event handling mode. Attribute value is 2 bytes long and can assume the following values:
0x00 = ReadCycle mode 0x01 = Time Mode 0x02 = No Event Mode UpgradeType: a value representing the type of upgrade to perform. Attribute value is 2 bytes long and can assume the following values:
0x01 = TFTP firmware upgrade. UpgradeArgument: a value representing the argument for the requested upgrade. Attribute value has a maximum length of 255 bytes. For TFTP upgrade string has
<tftpserverip>:<filename>.
(code 0x01) form:
the the NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
9 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code 0x71 0x72 0x73 0x74 0x75 0x76 0x77 0x78 0x96 Description MemoryBank: a value representing the memory bank of a EPC Class 1 Generation 2 tag. Attribute value is 2 bytes long and can assume the following values:
0x00 = Reserved Memory Bank 0x01 = EPC Memory Bank 0x02 = TID Memory Bank 0x03 = User Memory Bank Payload: a value representing the payload parameter for the EPC Class 1 Gen 2 lock command (see the EPC Gen2 specification for details). Attribute value is 4 bytes long. G2Password: a value representing the password parameter for the EPC Class 1 Gen 2 kill command (see the EPC Gen2 specification for details). Attribute value is 4 bytes long. G2NSI: a value representing the numbering system identifier for the EPC Class 1 Gen 2 tags id (see the EPC Gen2 specification for details). Attribute value is 2 bytes long. QParameter: a value representing the initial value for the Q parameter involved in the EPC Class 1 Gen 2 anticollision algorithm (see the EPC Gen2 specification for details). Attribute value is 2 bytes long. ReaderInfo: a string indicating the model and the serial number of the reader. RFRegulation: a value representing the RF regulation to use. Attribute value is 2 bytes long and can assume the following values:
0x00 = ETSI EN 302 208 0x01 = ETSI EN 300 220 RFChannel: a value representing the RF channel to use. Attribute value is 2 bytes long and can assume values in the range 0 9. Channels are referred to the ETSI EN 302 208 regulation. PowerSet: a value representing the RF power emitted during the communication with tags. Attribute value is 4 bytes long. (used to set a new current value). NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
10 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code 0xFB Description SourceName: a string representing the name of the data source. Attribute value has a maximum length of 30 bytes and can assume the following values:
Source_0, Source_1, Source_2, Source_3 Table 2.2: Command codes Code Description RawReadIDs: permits to get all the tags Ids that are under the RF field of the selected source. Parameters:
SourceNameIn: [in] the name of the source to use. SourceNameOut: [out] the name of the source used. ReadPointName: [out] the name of the readpoint. TimeStamp: [out] the time at which the tags are detected. TagIDLen: [out] the ID length of the tags detected. ListOfIDs: [out] the list of Ids detected from the source. ResultCode: [out] the result code. Note: out parameters are repeated for each readpoint in the source. AddReadTrigger: permits to add a trigger to a source. Parameters:
SourceName: [in] the name of the source. TriggerName: [in] the name of the trigger. ResultCode: [out] the result code. AddNotifyTrigger: permits to add a trigger to a notification channel. Parameters:
ChannelName: [in] the name of the channel. TriggerName: [in] the name of the trigger. ResultCode: [out] the result code. RemoveReadTrigger: permits to remove a trigger from a source. Parameters:
SourceName: [in] the name of the source. TriggerName: [in] the name of the trigger. ResultCode: [out] the result code. 0x12 0x3F 0x40 0x41 Comp. A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A928 A948 A928 A948 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
11 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Comp. Code 0x42 0x49 0x4A 0x53 0x54 0x5D Description RemoveNotifyTrigger: permits to remove a trigger from a notification channel. Parameters:
ChannelName: [in] the name of the channel. TriggerName: [in] the name of the trigger. ResultCode: [out] the result code. AllocateTrigger: permits to create a new trigger. Parameters:
TriggerName: [in] the name of the trigger. TriggerType: [in] the type of the trigger. ResultCode: [out] the result code. DeallocateTrigger: permits to destroy an existing trigger. Parameters:
TriggerName: [in] the name of the trigger. ResultCode: [out] the result code. AllocateChannel: permits to create a notification channel. Parameters:
ChannelName: [in] the name of the channel. ChannelAddress: [in] the address of the channel. ResultCode: [out] the result code. DeallocateChannel: permits to destroy a notification channel. Parameters:
ChannelName: [in] the name of the channel. ResultCode: [out] the result code. AddSourceToChannel: permits to add a source to a notification channel. Parameters:
SourceName: [in] the name of the source. ChannelName: [in] the name of the channel. ResultCode: [out] the result code. A928 A948 A928 A948 A928 A948 A928 A948 A928 A948 A928 A948 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
12 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code 0x5E 0x5F 0x60 0x64 0x6E Description RemoveSourceFromChannel: permits to remove a source from a notification channel. Parameters:
SourceName: [in] the name of the source. ChannelName: [in] the name of the channel. ResultCode: [out] the result code. AddReadPointToSource: permits to add a readpoint to a source. Parameters:
SourceName: [in] the name of the source. ReadPointName: [in] the name of the readpoint. ResultCode: [out] the result code. RemoveReadPointFromSource: permits to remove a readpoint from a source. Parameters:
SourceName: [in] the name of the source. ReadPointName: [in] the name of the readpoint. ResultCode: [out] the result code. SetPower: permits to set the RF power level. Parameters:
PowerSet: [in] the power level to set. ResultCode: [out] the result code. ReadTagData: permits to read data from the tag memory. Parameters:
SourceName: [in] the name of the source to use. TagIDLen: [in] the ID length of the tag. TagID: [in] the ID of the tag. TagAddress: [in] the address from which read the data. Length: [in] the number of bytes to read. TagValue: [out] the data read from the tag memory. ResultCode: [out] the result code. Comp. A928 A948 A928 A948 A928 A948 A928 A948 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
13 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code Description WriteTagData: permits to write data to the tag memory. Parameters:
SourceName: [in] the name of the source to use. TagIDLen: [in] the ID length of the tag. TagID: [in] the ID of the tag. TagAddress: [in] the address where to write the data. Length: [in] the number of bytes to write. TagValue: [in] the data to write to the tag memory. ResultCode: [out] the result code. LockTag: permits to lock data into the tag memory. Parameters:
SourceName: [in] the name of the source to use. TagIDLen: [in] the ID length of the tag. TagID: [in] the ID of the tag. TagAddress: [in] the address where to write the data. ResultCode: [out] the result code. RESERVED SetBitRate: permits to set the BitRate to use. Parameters:
BitRate: [in] the BitRate to set. ResultCode: [out] the result code. 0x6F 0x70 0x71 0x72 GetPower: permits to get the current RF power level. Parameters:
PowerGet: [out] the current power level. ResultCode: [out] the result code. 0x73 Comp. A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A941 A946 A949 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
14 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code Description SetProtocol: permits to set the protocol to use. Parameters:
Protocol: [in] the protocol to use. ResultCode: [out] the result code. 0x74 0x75 0x76 0x77 0x78 RESERVED CheckReadPointStatus: permits to check the quality of the antenna connection. Parameters:
ReadPointName: [in] the name of the readpoint. ReadPointStatus: [out] the quality of the connection. ResultCode: [out] the result code. CheckSourceInChannel: permits to verify if a source is assigned to a notify channel. Parameters:
SourceName: [in] the name of the source. ChannelName: [in] the name of the channel. Value: [out] a Boolean value meaning the belonging to the source. ResultCode: [out] the result code. CheckReadPointInSource: permits to verify if a readpoint belongs to a givens source. Parameters:
ReadPointName: [in] the name of the readpoint. SourceName: [in] the name of the source. Value: [out] a Boolean value meaning the belonging to the source. ResultCode: [out] the result code. Comp. A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A941 A946 A949 A928 A948 A928 A948 A941 A946 A949 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
15 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code Description GetProtocol: permits to get the protocol in use. Parameters:
Protocol: [out] the protocol in use. ResultCode: [out] the result code. 0x79 0x7A 0x7B 0x7C SetNetwork: permits to set up the network configuration. Parameters:
IPAddress: [in] the IP address to set. IPNetMask: [in] the IP netmask to set. IPGateway: [in] the IP gateway to set. ResultCode: [out] the result code. SetDESB: permits to enable or disable the Data Exchange Status Bit handling during the anti-collision algorithm when ISO 18000-6b air protocol is in use. Parameters:
DESBEnable: [in] enable/disable value. ResultCode: [out] the result code. GetFirmwareRelease: permits to get the firmware revision. Parameters:
FWRelease: [in] the firmware release. ResultCode: [out] the result code. Comp. A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
16 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code Description Comp. GetDESB: permits to get the current setting of the Data Exchange Status Bit handling. Parameters:
DESBStatus: [in] enabled/disabled value. ResultCode: [out] the result code. A928 A948 A528 A828 A828A 0x7D ProgramID: permits to program the ID in the EPC Class 1 Gen 1 tags. Parameters:
SourceName: [in] the name of the source. TagIDLen: [in] the ID length of the tag. TagID: [in] the ID of the tag. EPCPWD: [in] the EPC password to set. Lock: [in] a Boolean value; TRUE = lock the ID. FALSE = do not lock. ResultCode: [out] the result code. KillTag: permits to kill a EPC Class 1 Gen 1 tag. Parameters:
SourceName: [in] the name of the source. TagIDLen: [in] the ID length of the tag. TagID: [in] the ID of the tag. EPCPWD: [in] the EPC password. ResultCode: [out] the result code. RFOnOff: permits to start/stop the generation of a continuous wave. Used only for test and measurements purposes. Parameters:
RFOnOff: [in] = 0 stop; != 0 start ResultCode: [out] the result code. 0x7E 0x7F 0x80 A829 A941 A946 A949 A928 A948 A928 A948 A928 A948 A528 A828 A828A A829 A941 A946 A949 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
17 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code Description GetBitRate: permits to get the BitRate in use. Parameters:
BitRate: [out] the BitRate in. ResultCode: [out] the result code. 0x81 0x82 0x83 BlockWriteTag: permits to write data to the tag memory. This function uses the ISO18000-6b Write4Byte command to speed up the writing of large amount of data at one time. Parameters:
SourceName: [in] the name of the source to use. TagIDLen: [in] the ID length of the tag. TagID: [in] the ID of the tag. TagAddress: [in] the address where to write the data. Length: [in] the number of bytes to write. TagValue: [in] the data to write to the tag memory. ResultCode: [out] the result code. SetRS232: permits to modify the settings of the serial port. Parameters:
Baudrate: [in] the baud rate value. Databits: [in] the data bits setting. Stopbits: [in] the stop bits setting. Parity: [in] the parity setting. Flowctrl: [in] the flow control setting. ResultCode: [out] the result code. Comp. A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
18 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code Description SetDateTime: permits to modify date and time. Parameters:
Datetime: [in] the date and time to set up. ResultCode: [out] the result code. 0x84 0x85 0x86 GroupSelectUnselect: permits to execute the tag selection commands defined by the ISO18000-6B protocol. Parameters:
SourceName: [in, optional] the name of the source to use. Operation: [in] the tag selection operation. Bytemask: [in] the byte mask as defined by the protocol. TagAddress: [in] the address where to compare the data. TagValue: [in] the data to compare with the tag memory. TagID: [out] the ID of the tag. ResultCode: [out] the result code. GetIO: permits to read the current status of the I/O lines. Parameters:
IORegister: [out] the status of the I/O lines. ResultCode: [out] the result code. Comp. A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
19 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code Description SetIO: permits to set the level of the output lines. Parameters:
IORegister: [in] the value to set to the output lines. ResultCode: [out] the result code. 0x87 0x88 0x89 0x8A SetIODirection: permits to define the direction of the I/O lines.
(0 = input; 1 = output) Parameters:
IORegister: [in] the direction to set to the I/O lines. ResultCode: [out] the result code. GetIODirection: permits to read the current status of the I/O lines. (0 =
input; 1 = output) Parameters:
IORegister: [out] the direction of the I/O lines. ResultCode: [out] the result code. SetSourceConfig: permits to set a configure parameter for a logical source. Parameters:
SourceName: [in] the name of the source to configure. ConfigParameter: [in] the code of the parameter. ConfigValue: [in] the value for the parameter. ResultCode: [out] the result code. Comp. A928 A948 A528 A828 A828A A829 A941 A946 A949 A528 A828 A828A A829 A941 A946 A949 A528 A828 A828A A829 A941 A946 A949 A928 A948 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
20 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Comp. Code 0x8B 0x8C 0x8D 0x8E 0x8F Description GetSourceConfig: permits to read a configure parameter for a logical source. Parameters:
SourceName: [in] the name of the source to configure. ConfigParameter: [in] the code of the parameter. ConfigValue: [out] the value for the parameter. ResultCode: [out] the result code. GetTriggers: permits to read the names of the allocated triggers. Parameters:
NoOfTriggers: [out] the number of allocated triggers. ListOfTriggerNames: [in] a list containing the names of the allocated triggers. ResultCode: [out] the result code. GetChannels: permits to read the names of the allocated notification channels. Parameters:
NoOfChannels: [out] the number of allocated channels. ListOfChannelNames: [in] a list containing the names of the allocated channels. ResultCode: [out] the result code. CheckSourceInTrigger: permits to verify if the specified logical source is associated to the specified trigger. Parameters:
SourceName: [in] the name of the source. TriggerName: [in] the name of the trigger. Boolean: [out] 0 if they are associated, 0 if not. ResultCode: [out] the result code. CheckTriggerInChannel: permits to verify if the specified trigger is associated to the specified channel. Parameters:
ChannelName: [in] the name of the source. TriggerName: [in] the name of the trigger. Boolean: [out] 0 if they are associated, 0 if not. ResultCode: [out] the result code. A928 A948 A928 A948 A928 A948 A928 A948 A928 A948 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
21 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code 0x90 0x91 0x92 0x93 0x94 Description CheckChannelInTrigger: permits to verify if the specified channel is associated to the specified trigger. Parameters:
ChannelName: [in] the name of the source. TriggerName: [in] the name of the trigger. Boolean: [out] 0 if they are associated, 0 if not. ResultCode: [out] the result code. SetEventMode: permits to set the event generation mode for the reader notification channels. Parameters:
EventMode: [in] the event mode. ResultCode: [out] the result code. GetEventMode: permits to read the event generation mode for the reader notification channels. Parameters:
EventMode: [out] the event mode. ResultCode: [out] the result code. FirmwareUpgrade: permits to upgrade the reader firmware. Parameters:
UpgradeType: [in] the type of the upgrade. UpgradeArg: [in] the argument needed by the upgrade procedure. ResultCode: [out] the result code. E119ProgramID: permits to write the EPC into a EPC1.19 tag. Parameters:
SourceName: [in] the name of the source to use. TagID: [in] the old EPC of the tag. TagValue: [in] the EPC to write into the tag memory. ResultCode: [out] the result code. Comp. A928 A948 A928 A948 A928 A948 A928 A948 A928 A948 A528 A828 A828A A829 A941 A946 A949 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
22 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code Description 0x95 0x96 0x97 G2ProgramID: permits to write the EPC in a Class 1 Gen 2 tag. Parameters:
SourceName: [in] the name of the source to use. TagIDLen: [in] the ID length of the tag (must be an even number). TagID: [in] the EPC to write into the tag memory. G2NSI: [in] the EPC numbering system. ResultCode: [out] the result code. G2Read: permits to read data from anyone of the Gen2 tag memory banks. Parameters:
SourceName: [in, optional] the name of the source to use. TagIDLen: [in] the ID length of the tag. TagID: [in] the ID of the tag. MemoryBank: [in] the memory bank. TagAddress: [in] the address where to read the data. Length: [in] the number of bytes to read (must be an even number). TagValue: [out] the data read from the tag memory. ResultCode: [out] the result code. G2Write: permits to write data into anyone of the Gen2 tag memory banks. Parameters:
SourceName: [in, optional] the name of the source to use. TagIDLen: [in] the ID length of the tag. TagID: [in] the ID of the tag. MemoryBank: [in] the memory bank. TagAddress: [in] the address where to write the data. Length: [in] the number of bytes to write (must be an even number). TagValue: [in] the data to write to the tag memory. ResultCode: [out] the result code. Comp. A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
23 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code Description G2Lock: permits to execute the tag lock command defined by the EPC Class 1 Gen 2 protocol. Parameters:
SourceName: [in, optional] the name of the source to use. TagIDLen: [in] the ID length of the tag. TagID: [in] the ID of the tag. G2Payload: [in] the lock payload. ResultCode: [out] the result code. G2Kill: permits to execute the tag kill command defined by the EPC Class 1 Gen 2 protocol. Parameters:
SourceName: [in, optional] the name of the source to use. TagIDLen: [in] the ID length of the tag. TagID: [in] the ID of the tag. G2Password: [in] the kill password. ResultCode: [out] the result code.
(0x00) G2Query: permits to execute the tag query command defined by the EPC Class 1 Gen 2 protocol. If a tag is in the field result code is ERROR_SUCCESS is ERROR_TAGNOTPRESENT (0xCA). Parameters:
SourceName: [in] the name of the source to use. ResultCode: [out] the result code. result code else 0x98 0x99 0x9A Comp. A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
24 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code Description Comp. G2SetQ: permits to change the initial value of the Q parameter used in the Gen2 anticollision algorithm. Parameters:
QParameter: [in] the value of the Q parameter. ResultCode: [out] the result code. A928 A948 A528 A828 A828A 0x9B G2GetQ: permits to read the initial value of the Q parameter used in the Gen2 anticollision algorithm. Parameters:
QParameter: [out] the value of the Q parameter. ResultCode: [out] the result code. 0x9C 0x9D in the stored G2QueryAck: permits to execute the tag query and ack command defined by the EPC Class 1 Gen 2 protocol. If a tag is in the field result code is ERROR_SUCCESS (0x00) and the command returns the EPC code is ERROR_TAGNOTPRESENT (0xCA). Parameters:
SourceName: [in] the name of the source to use. TagID: [out] the ID of the tag. ResultCode: [out] the result code. result code else tag the A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 A928 A948 A528 A828 A828A A829 A941 A946 A949 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
25 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code Description Comp. GetReaderInfo: permits to read some information about the reader itself. Parameters:
ReaderInfo: [out] a string with information about the reader. ResultCode: [out] the result code. A928 A948 A528 A828 A828A SetLBTMode: permits to enable or disable the Listen Before Talk capability on ETSI EN 302 208 compatible readers. Parameters:
Boolean: [in] 0 to disable LBT and 0 to enable LBT. ResultCode: [out] the result code. GetLBTMode: permits to read the current setting for the Listen Before Talk capability on ETSI EN 302 208 compatible readers. Parameters:
Boolean: [out] 0 if LBT is disabled, 0 if LBT is enabled. ResultCode: [out] the result code. SetRFRegulation: permits to change the RF regulation used by the reader. Parameters:
RFRegulation: [in] the desired RF regulation. ResultCode: [out] the result code. GetRFRegulation: permits to read the RF regulation used by the reader. Parameters:
RFRegulation: [out] the desired RF regulation. ResultCode: [out] the result code. SetRFChannel: permits to set the RF channel where the reader emits the RF field. Parameters:
RFChannel: [in] the RF channel. ResultCode: [out] the result code. A829 A941 A946 A949 A941 A946 A948 A949 A941 A946 A948 A949 A941 A946 A948 A949 A941 A946 A948 A949 A941 A946 A948 A949 0x9E 0x9F 0xA0 0xA1 0xA2 0xA3 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
26 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Code 0xA4 Description GetRFChannel: permits to read the RF channel currently in use. Parameters:
RFChannel: [out] the RF channel. ResultCode: [out] the result code. 0xFFFF RESERVED Comp. A941 A946 A948 A949 NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
27 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 3. Asynchronous Notification: Protocol specification The notification channels are implemented only with sockets. All the messages notifications are composed by a header and a body. In all cases the body of the message is a list of attribute-value pairs. The first AVP of the body is fixed and called NotifyMessage. All the packets for notification channel share the same header format of other packet as described at 3. The first AVP (NotifyMessage) is followed by a list of AVPs, the number of which depends on how many tags should be notified. Each AVP has the same format of the AVP described in 3. The NotifyMessage has the following fixed format:
1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
| RESERVED | 8 |
| CommandName
After the NotifyMessage AVP we can receive:
| ReportBuffer a) a list of AVPs (as described in table 3) followed by an AVP with Attribute Type ResultCode b) a single AVP called KillMessage with the following fixed format:
1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
| RESERVED | 8 |
| KillCommand
| KillCommand Table 3.1: Attribute types: Notification AVP List. Description TimeStamp: the timestamp of the notification TagIDLen: the ID length of the tag. TagID: the ID of the tag. SourceName: the name of the source to use. EventType: the type of the notified event NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
28 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 4. Default configuration CAEN A928 and A948E UHF RFID Reader protocol has various configuration parameters; in the following table are summarized the default values. Table 4.1: A928 and A948 Configuration parameters default values Parameter IP Address IP Netmask IP Gateway Sources Readpoints Baud Rate Data Bits Stop Bits Parity Flow Control Default value 192.168.0.125 255.255.255.0 192.168.0.1 Source_0, Source_1, Source_2, Source_3 Ant0, Ant1, Ant2, Ant3 115200 8 1 None None The default composition of sources for A928E and A948 reader is the following:
Table 4.2: A928 and A948 Default composition of sources Readpoints Source Source_0 Source_1 Source_2 Source_3 Ant0 Ant1 Ant2 Ant3 CAEN A828, A829, A946 and A949 UHF RFID Reader protocol has various configuration parameters; in the following table are summarized the default values. NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
29 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 Table 4.3: A828, A829, A829, A946 and A949 Configuration parameters default values Default value Parameter Sources Readpoints Baud Rate Data Bits Stop Bits Parity Flow Control Source_0 Ant0 115200 8 1 None None The default composition of sources for the A828, A829, A946 and A949 reader is the following:
Table 4.4: A828, A829, A946 and A949 Default composition of sources Source Source_0 Ant0 Readpoints NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
30 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 5. Samples
(Fixed)
(Message ID)
(AVP Value)
(Vendor ID = CAEN SpA)
(Message Length)
(Reserved)
(AVP Length)
(AVP Type = CommandName)
(AVP Value = RawReadIDs)
(Reserved)
(AVP Length)
(AVP Type = SourceName) In the following sample a RawReadIDs command is examined together with the response coming from the reader. Command sent:
0x8001 0x0000 0x00005358 0x0021 0x0000 0x0008 0x0001 0x0012 0x0000 0x000F 0x00FB Source_0 Response received:
0x0001 0x0000 0x00005358 0x0066 0x0000 0x0008 0x0001 0x0012 0x0000 0x000F 0x00FB Source_0 0x0000 0x000B 0x0022 Ant0 0x0000 0x000E 0x0010 0x00000578 0x00000000 0x0000 0x0008 0x000F 0x0008 0x0000 0x000E 0x0011 0x05629FFF 0xC0113001 0x0000 0x000E 0x0011 0xE0040F0E 0x06010000 0x0000 0x0008 0x0002 0x0000
(Fixed)
(Message ID)
(Vendor ID = CAEN SpA)
(Message Length)
(Reserved)
(AVP Length)
(AVP Type = CommandName)
(AVP Value = RawReadIDs)
(Reserved)
(AVP Length)
(AVP Type = SourceName)
(AVP Value)
(Reserved)
(AVP Length)
(AVP Type = ReadPointName)
(AVP Value)
(Reserved)
(AVP Length)
(AVP Type = TimeStamp)
(AVP Value)
(Reserved)
(AVP Length)
(AVP Type = TagIDLen)
(Reserved)
(AVP Length)
(AVP Type = TagID)
(AVP Value)
(AVP Value)
(Reserved)
(AVP Length)
(AVP Type = TagID)
(AVP Value)
(AVP Value)
(Reserved)
(AVP Length)
(AVP Type = ResultCode)
(AVP Value = Thu Jan 1 01:23:20 1970)
(AVP Value = Success)
(AVP Value) NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
31 Document type:
User's Manual (MUT) Title:
CAEN UHF RFID Readers Communication Protocol Revision date:
02/04/2008 Revision:
5 6. References Reader Protocol 1.0 Working Draft Version of 25 August 2004 Document revision 33 - EPCGlobal EPC Radio Frequency Identity Protocols Class-1 Generation-2 UHF RFID Protocol for Communications at 860MHz 960MHz Version 1.0.9 EPCGlobal ISO/IEC FDIS 18000-6:2003(E) Information technology automatic identification and data capture techniques Radio frequency identification for item management air interface Part 6: Parameters for air interface communication at 860-960 MHz NPO:
00117/03:PROTx.MUTx/05 Filename:
EASY2READ_PROTOCOL_REV5.DOC Number of pages:
32 Page:
32
| 1 | User Manual 3 | Users Manual | 283.57 KiB |
Technical Information Manual Revision n. 2 17 January 2007 CAENRFIDLib ANSI C FUNCTIONS LIBRARY NPO:
00117/03:RFLIB.MUTx/02 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 INDEX 1. INTRODUCTION................................................................................................................................................4 1.2.1. 1.1. CAENRFIDLIB INTRODUCTION......................................................................................................................4 1.2. CAENRFIDLIB DESCRIPTION ........................................................................................................................4 CAENRFIDTypes.h ................................................................................................................................4 1.3. CAENRFIDLIB FUNCTIONS DESCRIPTION .....................................................................................................7 CAENRFID_Init .....................................................................................................................................7 1.3.1. CAENRFID_ End ...................................................................................................................................7 1.3.2. CAENRFID_GetSWRelease ...................................................................................................................7 1.3.3. CAENRFID_GetFWRelease...................................................................................................................8 1.3.4. CAENRFID_Inventory ...........................................................................................................................8 1.3.5. CAENRFID_SetPower ...........................................................................................................................8 1.3.6. CAENRFID_Read...................................................................................................................................9 1.3.7. CAENRFID_Write..................................................................................................................................9 1.3.8. 1.3.9. CAENRFID_Lock...................................................................................................................................9 1.3.10. CAENRFID_TestMode.........................................................................................................................10 1.3.11. CAENRFID_SetModulation .................................................................................................................10 1.3.12. CAENRFID_GetModulation ................................................................................................................10 1.3.13. CAENRFID_AllocateChannel..............................................................................................................11 1.3.14. CAENRFID_DeallocateChannel..........................................................................................................11 1.3.15. CAENRFID_AddSourceToChannel......................................................................................................11 1.3.16. CAENRFID_RemoveSourceFromChannel...........................................................................................11 1.3.17. CAENRFID_AddReadPoint .................................................................................................................12 1.3.18. CAENRFID_RemoveReadPoint ...........................................................................................................12 1.3.19. CAENRFID_AllocateTrigger ...............................................................................................................12 1.3.20. CAENRFID_DeallocateTrigger ...........................................................................................................13 1.3.21. CAENRFID_AddReadTrigger..............................................................................................................13 1.3.22. CAENRFID_RemoveReadTrigger........................................................................................................13 1.3.23. CAENRFID_AddNotifyTrigger ............................................................................................................13 1.3.24. CAENRFID_RemoveNotifyTrigger ......................................................................................................14 1.3.25. CAENRFID_GetNotification................................................................................................................14 1.3.26. CAENRFID_GetPower.........................................................................................................................14 1.3.27. CAENRFID_SetProtocol......................................................................................................................15 1.3.28. CAENRFID_GetProtocol .....................................................................................................................15 1.3.29. CAENRFID_GetReadPointStatus ........................................................................................................15 NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
2 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 1.3.30. CAENRFID_GetSourceInChannel .......................................................................................................15 1.3.31. CAENRFID_GetSourceInTrigger ........................................................................................................16 1.3.32. CAENRFID_GetTriggerInChannel......................................................................................................16 1.3.33. CAENRFID_GetChannelInTrigger......................................................................................................16 1.3.34. CAENRFID_GetReadPointInSource....................................................................................................17 1.3.35. CAENRFID_SetNetwork ......................................................................................................................17 1.3.36. CAENRFID_SetDE_SB ........................................................................................................................18 1.3.37. CAENRFID_GetDE_SB .......................................................................................................................18 1.3.38. CAENRFID_ProgramID ......................................................................................................................18 1.3.39. CAENRFID_KillTag.............................................................................................................................18 1.3.40. CAENRFID_BlockWrite.......................................................................................................................19 1.3.41. CAENRFID_SetRS232 .........................................................................................................................19 1.3.42. CAENRFID_SetDateTime ....................................................................................................................20 1.3.43. CAENRFID_GetIO...............................................................................................................................20 1.3.44. CAENRFID_SetIO................................................................................................................................20 1.3.45. CAENRFID_SetSourceConfiguration ..................................................................................................20 1.3.46. CAENRFID_GetSourceConfiguration .................................................................................................21 1.3.47. CAENRFID_GetAllocatedTriggers......................................................................................................21 1.3.48. CAENRFID_GetAllocatedChannels.....................................................................................................21 1.3.49. CAENRFID_SetEventMode..................................................................................................................22 1.3.50. CAENRFID_GetEventMode.................................................................................................................22 1.3.51. CAENRFID_FirmwareUpgrade...........................................................................................................22 1.3.52. CAENRFID_Lock_C1G2 .....................................................................................................................22 1.3.53. CAENRFID_KillTag_C1G2 .................................................................................................................23 1.3.54. CAENRFID_KillTag_C1G2 .................................................................................................................23 1.3.55. CAENRFID_ProgramID_EPC119.......................................................................................................23 1.3.56. CAENRFID_ProgramID_C1G2...........................................................................................................24 1.3.57. CAENRFID_Read_C1G2.....................................................................................................................24 1.3.58. CAENRFID_Write_C1G2 ....................................................................................................................24 1.3.59. CAENRFID_QueryTag_C1G2 .............................................................................................................25 1.3.60. CAENRFID_SetQ_C1G2 .....................................................................................................................25 1.3.61. CAENRFID_GetQ_C1G2.....................................................................................................................25 1.3.62. CAENRFID_GetReaderInfo .................................................................................................................25 1.3.63. CAENRFID_FreeTagsMemory ............................................................................................................26 NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
3 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library 1. Introduction Revision date:
17/01/2007 Revision:
2 The CAEN Long Range UHF Readers are developed in Europe and in compliance with European and US telecommunication regulations, are a step forward in UHF RFID readers. Capable of long distance reading using extremely low RF energy, the CAEN Long Range UHF Readers are optimized to increase receiver sensibility and reduce transmitter noise. The CAEN Long Range UHF Readers open architecture uses a multi-protocol technology. The tag protocol interface was developed using a field programmable gate array, which allows easy modification of the tag protocol definition. On the host side, a powerful 32bit micro-controller enables for maximum upgradeability to future generations of the EPC specification. Easily integrated with most popular database software and fully compliant with ISO 18000-6B and EPC Class 1 Generation 1 protocol, Philips UCODE EPC 1.19, the CAEN Long Range UHF Readers can be used in conjunction with any passive or active tag that conforms to the same standards; moreover, it can be easily upgraded for compliancy with other protocols1. With their extended read range, the CAEN Long Range UHF Readers are well suited to asset management and logistics applications that require the simultaneous reading of a large number of tags from a great distance. firmware updating fast 1.1. CAENRFIDLib introduction This section describes the CAENRFIDLib library and its implemented functions. CAENRFIDLib is a set of ANSI C functions which permits an user program the use and the configuration of the CAEN Long Range UHF Readers. The present description refers to CAENRFIDLib, available in the following formats:
Win32 DLL (CAEN provides the CAENRFIDLib.lib stub for Microsoft Visual C++ 6.0) CAENRFIDLib is logically located between an application like the samples provided and the lower layer software libraries. 1.2. CAENRFIDLib description 1.2.1. CAENRFIDTypes.h
#define MAX_ID_LENGTH 12 typedef int CAENRFIDHandle;
Error codes
typedef enum {
CAENRFID_StatusOK = 0, // Operation completed successfully CAENRFID_PortError = -1, // Error on selected port CAENRFID_ParityError = -2, // Parity error CAENRFID_InitError = -3, // Error on init CAENRFID_StatusByteError = -4, // Error on status byte 1 Software upgrades will be available at: http://www.caen.it/rfid/
NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
4 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 CAENRFID_InvalidParam = -5, // Invalid parameter error CAENRFID_TimeOutError = -6, // Time out error CAENRFID_Max4Byte = -7, // Data length greater than 4
= -9, // Antenna not connected
= -10, // Generic error
= -11 // Invelid Handle CAENRFID_PowerOutRange = -8, // Power out of range CAENRFID_BadAntenna CAENRFID_GenericError CAENRFID_InvalidHandle
} CAENRFIDErrorCodes;
ID length enum
typedef enum {
L64bit = 8, L96bit = 12
} CAENRFIDLenghtID;
Communication ports enum
typedef enum {
RS232 = 0, RS485 = 1, TCP = 2, USB = 3
} CAENRFIDPort;
Antenna select enum
typedef enum {
NOANT = 0, ANT1 = 1, ANT2 = 2, ANT3 = 3, ANT4 = 4
} CAENRFIDAntenna;
Tag identification struct: for each tag it contains the ID, the length of the ID and the antenna used to identify the tag.
typedef struct {
byte ID[MAX_ID_LENGTH];
int Length;
CAENRFIDAntenna Antenna;
} CAENRFIDTag;
General purpose outputs masks
typedef enum {
GPO0 = 0x01, NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
5 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 GPO1 = 0x02, GPO2 = 0x04, GPO3 = 0x08,
} CAENRFIDGpo;
Bit rate modulation control enum
typedef enum {
TX10RX10 = 0, TX10RX40 = 1, TX40RX40 = 2, TX40RX160 = 3
} CAENRFIDTxRxConf;
#ifndef CAENRFID_ODL
RF field control enum
typedef enum {
CARRIER_OFF = 0, CARRIER_ON = 1
} CAENRFIDControl;
typedef enum {
STANDBY = 0, ACTIVE = 1
} CAENRFIDPas;
Command mode control enum
typedef enum {
SINGLE = 0, START_SEQ = 1, END_SEQ = 2, SUSTAINED = 3
} CAENRFIDSetCMD;
#endif NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
6 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 1.3. CAENRFIDLib Functions description 1.3.1. CAENRFID_Init Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_Init A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function generates an opaque handle to identify a module attached to the PC.
[in] Port: Communication port (see CAENRFIDPort enum).
[in] Address: Communication address (i.e.: "COM1" for RS232,
"USB0" for USB of IP address for TCP/IP etc.)
[out] Handle: The handle that identifies the device. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_Init (CAENRFIDPort Port, char *Address, CAENRFIDHandle *Handle, CAENRFIDProtocol *Protocol);
1.3.2. CAENRFID_ End Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_End A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU Notifies the library the end of work and free the allocated resources
[in] Handle: The handle that identifies the device An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_End(CAENRFIDHandle Handle);
1.3.3. CAENRFID_GetSWRelease Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetSWRelease A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU Permits to read the software release of the library.
[out] SwRel: Returns the software release of the library An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetSWRelease(char *SwRel);
NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
7 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library 1.3.4. CAENRFID_GetFWRelease Revision date:
17/01/2007 Revision:
2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetFWRelease A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU Permits to read the firmware release loaded into the device
[in] Handle: The handle that identifies the device.
[out] FWRel: Returns the firmware release of the device An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetFWRelease(CAENRFIDHandle Handle, char
*FWRel);
1.3.5. CAENRFID_Inventory Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_Inventory A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function returns all the IDs of the tags under the reader fieldusing all the available antennae. The Tags array contains The IDs together with other information related to the single ID such as the antenna under which is the ID and the format of the ID itself (see CAENRFIDTag struct for the details).
[in] Handle: The handle that identifies the device.
[in] LogicalSourceName: The name that identify the Logical Source
[out] Tags: Returns an array containing the tags read.
[out] TagsNo: Returns the number of tags in the array. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_Inventory(CAENRFIDHandle Handle, char
*LogicalSourceName, CAENRFIDTag **Tags, int *TagsNo);
1.3.6. CAENRFID_SetPower Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_Inventory A928EU, A948EU The function permits to set the RF field power relative to the antenna socket
[in] Handle: The handle that identifies the device.
[in] Power: RF field power expressed in mW. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_SetPower(CAENRFIDHandle Handle, unsigned int Power);
NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
8 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library 1.3.7. CAENRFID_Read Revision date:
17/01/2007 Revision:
2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_Read A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU This function allows to read Length bytes from the memory of a specific tag identified by the ID (regardless of its status) at the address specified by Address.
[in] Handle: The handle that identifies the device.
[in] ID: The tag ID.
[in] Address: The address of the memory to read.
[in] Length: The number of bytes to read.
[out] Data: The data read from the tag's memory. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_Read(CAENRFIDHandle Handle, CAENRFIDTag
*ID, int Address, int Length, void *Data);
1.3.8. CAENRFID_Write Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_Write A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU This function allows to write Length bytes to the memory of a specific tag identified by the ID (regardless of its status) at the address specified by Address.
[in] Handle: The handle that identifies the device.
[in] ID: The tag ID.
[in] Address: The address of the memory to write.
[in] Length: The number of bytes to write.
[in] Data: The data to write in the tag's memory. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_Write(CAENRFIDHandle Handle, CAENRFIDTag
*ID, int Address, int Length, void *Data);
1.3.9. CAENRFID_Lock Name:
Reader:
Description:
Parameters:
CAENRFID_Lock A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU This function allows to lockthe memory of a specific tag identified by the ID at the address specified by Address.
[in] Handle: The handle that identifies the device.
[in] ID: The tag ID.
[in] Address: The address of the memory to write. NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
9 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 Returns:
Syntax:
An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_Lock(CAENRFIDHandle Handle, CAENRFIDTag
*ID, int Address);
1.3.10. CAENRFID_TestMode Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_TestMode A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function permits to enable/disable te TestMode.
[in] Handle: The handle that identifies the device.
[in] TestMode: 0 Disable TestMode >0 Enable An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_TestMode(CAENRFIDHandle handle, unsigned int TestMode);
1.3.11. CAENRFID_SetModulation Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_SetModulation A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function permits to control to choose the modulation (the bit rate of the transmission and receive)
[in] Handle: The handle that identifies the device.
[in] TxRxCfg: Modulation setting. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_SetModulation(CAENRFIDHandle Handle, unsigned short TxRxCfg);
1.3.12. CAENRFID_GetModulation Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetModulation A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function permits to retrieve the modulation (the bit rate of the transmission and receive).
[in] Handle: The handle that identifies the device.
[out] TxRxCfg: Modulation setting An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetModulation(CAENRFIDHandle handle, unsigned short *TxRx);
NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
10 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 1.3.13. CAENRFID_AllocateChannel Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_AllocateChannel A928EU, A948EU The function permits to allocate a notification Channel
[in] Handle: The handle that identifies the device.
[in] ChannelName: The Name of the Channel.
[in] ChannelAddress: The Address of the Channel in the form
[TCP|USB|RS232]://[ip address:port]
An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_AllocateChannel(CAENRFIDHandle handle, char
*ChannelName, char *ChannelAddress);
1.3.14. CAENRFID_DeallocateChannel Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_DeallocateChannel A928EU, A948EU The function permits to Deallocate a Channel.
[in] Handle: The handle that identifies the device.
[in] ChannelName: The Name of the Channel. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_DeallocateChannel(CAENRFIDHandle handle, char
*ChannelName);
1.3.15. CAENRFID_AddSourceToChannel Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_AddSourceToChannel A928EU, A948EU The function permits to add a LogicalSource to a notification Channel.
[in] Handle: The handle that identifies the device.
[in] SourceName: The Name of the Logical Source.
[in] ChannelName: The Address of the Channel. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_AddSourceToChannel(CAENRFIDHandle char *SourceName, char *ChannelName);
handle, 1.3.16. CAENRFID_RemoveSourceFromChannel Name:
Reader:
Description:
CAENRFID_RemoveSourceFromChannel A928EU, A948EU The function permits to remove a LogicalSource from a NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
11 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 Parameters:
Returns:
Syntax:
notification Channel
[in] Handle: The handle that identifies the device.
[in] SourceName: The Name of the Logical Source.
[in] ChannelName: The Address of the Channel. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_RemoveSourceFromChannel(CAENRFIDHandle handle, char *SourceName, char *ChannelName);
1.3.17. CAENRFID_AddReadPoint Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_AddReadPoint A928EU, A948EU The function permits to add a read point (antenna) to a logical source
[in] Handle: The handle that identifies the device.
[in] SourceName: The name of the Logical Source.
[in] ReadPoint: The name of the Read Point. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_AddReadPoint(CAENRFIDHandle
*SourceName, char *ReadPoint);
handle, char 1.3.18. CAENRFID_RemoveReadPoint Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_RemoveReadPoint A928EU, A948EU The function permits to remove a read point (antenna) frpm a logical source
[in] Handle: The handle that identifies the device.
[in] SourceName: The name of the Logical Source.
[in] ReadPoint: The name of the Read Point. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_RemoveReadPoint(CAENRFIDHandle handle, char
*SourceName, char *ReadPoint);
1.3.19. CAENRFID_AllocateTrigger Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_AllocateTrigger A928EU, A948EU The function permits to create a trigger of the specified type
[in] Handle: The handle that identifies the device.
[in] TriggerName: The name of the trigger.
[in] TriggerType: The type of the trigger. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
12 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 CAENRFID_AllocateTrigger(CAENRFIDHandle handle,
*TriggerName, char *TriggerType);
char 1.3.20. CAENRFID_DeallocateTrigger Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_DeallocateTrigger A928EU, A948EU The function permits to destroy a trigger
[in] Handle: The handle that identifies the device.
[in] TriggerName: The name of the trigger An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_DeallocateTrigger(CAENRFIDHandle handle, char
*TriggerName);
1.3.21. CAENRFID_AddReadTrigger Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_AddReadTrigger A928EU, A948EU The function permits to associate a trigger to a source in order to start a read cycle
[in] Handle: The handle that identifies the device.
[in] SourceName: The name of the Logical Source.
[in] TriggerName: The name of the trigger An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_AllocateTrigger(CAENRFIDHandle handle,
*TriggerName, char *TriggerType);
char 1.3.22. CAENRFID_RemoveReadTrigger Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_RemoveReadTrigger A928EU, A948EU The function permits to remove the read trigger from the logical source
[in] Handle: The handle that identifies the device.
[in] SourceName: The name of the Logical Source.
[in] TriggerName: The name of the trigger An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_RemoveReadTrigger(CAENRFIDHandle handle, char *SourceName, char *TriggerName);
1.3.23. CAENRFID_AddNotifyTrigger Name:
Reader:
Description:
CAENRFID_AddNotifyTrigger A928EU, A948EU The function permits to associate a trigger to a channel in order NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
13 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 Parameters:
Returns:
Syntax:
to start a notification.
[in] Handle: The handle that identifies the device.
[in] ChannelName: The Address of the Channel.
[in] TriggerName: The name of the trigger. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_AddNotifyTrigger(CAENRFIDHandle handle, char
*ChannelName, char *TriggerName);
1.3.24. CAENRFID_RemoveNotifyTrigger Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_RemoveNotifyTrigger A928EU, A948EU The function permits to remove the notification trigger from a channel.
[in] Handle: The handle that identifies the device.
[in] ChannelName: The Address of the Channel.
[in] TriggerName: The name of the trigger. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_RemoveNotifyTrigger(CAENRFIDHandle char *ChannelName, char *TriggerName);
handle, 1.3.25. CAENRFID_GetNotification Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_RemoveNotifyTrigger A928EU, A948EU The function permits to decode data coming from the notification channel
[in] Skt: The handle to the TCP socket.
[out] Items: A list of data items.
[out] NoItems: The number of data items in the list. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetNotification(SOCKET Skt, CAENRFIDNotify
**Items, int *NumberItems);
1.3.26. CAENRFID_GetPower Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetPower A928EU, A948EU The function returns the value of the ERP power setting in the reader
[in] Handle: The handle that identifies the device.
[out] Power: The ERP power of the reader. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID GetPower(CAENRFIDHandle Handle, unsigned int NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
14 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library
*Power);
1.3.27. CAENRFID_SetProtocol Revision date:
17/01/2007 Revision:
2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_SetProtocol. A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function permits to change the tag protocol used by the reader
[in] Handle: The handle that identifies the device.
[in] Protocol: The tag protocol to be set in the reader. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_SetProtocol
(CAENRFIDHandle CAENRFIDProtocol Protocol);
Handle, 1.3.28. CAENRFID_GetProtocol Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetProtocol A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function permits to know what tag protocol is used by the reader
[in] Handle: The handle that identifies the device.
[out] Protocol: The tag protocol to be set in the reader. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetProtocol(CAENRFIDHandle
*Protocol);
Handle, int 1.3.29. CAENRFID_GetReadPointStatus Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetReadPointStatus A928EU, A948EU The function permits to check the status of a read point
[in] Handle: The handle that identifies the device.
[in] ReadPoint: The name of the Read Point.
[out] Status: The status of the read point. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetReadPointStatus(CAENRFIDHandle char *ReadPoint, CAENRFIDReadPointStatus *Status);
Handle, 1.3.30. CAENRFID_GetSourceInChannel Name:
Reader:
Description:
CAENRFID_GetSourceInChannel A928EU, A948EU The function permits to check if a logical source is associated to NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
15 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 Parameters:
Returns:
Syntax:
a specified notification channel that is, the data read from the source is sent to the channel.
[in] Handle: The handle that identifies the device.
[in] SourceName: The name of the Logical Source.
[in] ChannelName: The name of the Channel.
[out] isPresent: A flag indicating if the source is associated to the specified channel. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetSourceInChannel(CAENRFIDHandle char *SourceName, char *ChannelName, short *isPresent);
Handle, 1.3.31. CAENRFID_GetSourceInTrigger Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetSourceInTrigger A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function permits to check if a logical source is associated to a specified trigger.
[in] Handle: The handle that identifies the device.
[in] SourceName: The name of the Logical Source.
[in] TriggerName: The name of the Trigger.
[out] isPresent: A flag indicating if the source is associated to the specified trigger. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetSourceInTrigger(CAENRFIDHandle char *SourceName, char *TriggerName, short *isPresent);
Handle, 1.3.32. CAENRFID_GetTriggerInChannel Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetTriggerInChannel A928EU, A948EU The function permits to check if a trigger is associated to a specified notification channel.
[in] Handle: The handle that identifies the device.
[in] TriggerName: The name of the Trigger.
[in] ChannelName: The name of the ChannelName.
[out] isPresent: A flag indicating if the trigger is associated to the specified channel. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetTriggerInChannel(CAENRFIDHandle char *TriggerName, char *ChannelName, short *isPresent);
Handle, 1.3.33. CAENRFID_GetChannelInTrigger Name:
Reader:
CAENRFID_GetChannelInTrigger A928EU, A948EU NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
16 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 Description:
Parameters:
Returns:
Syntax:
The function permits to check if a channel is associated to a specified notification trigger.
[in] Handle: The handle that identifies the device.
[in] ChannelName: The name of the ChannelName.
[in] TriggerName: The name of the Trigger.
[out] isPresent: A flag indicating if the channel is associated to the specified trigger. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetChannelInTrigger(CAENRFIDHandle char *ChannelName, char *TriggerName, short *isPresent);
Handle, 1.3.34. CAENRFID_GetReadPointInSource Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetReadPointInSource A928EU, A948EU The function permits to check if a read point is associated to a specified logical source that is, the read point is used within a read cycle performed in the source.
[in] Handle: The handle that identifies the device.
[in] SourceName: The name of the Logical Source.
[in] ReadPoint: The name of the Read Point.
[out] isPresent: A flag indicating if the read point is associated to the specified source. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetReadPointInSource(CAENRFIDHandle Handle, char *ReadPoint, char *SourceName, short *isPresent);
1.3.35. CAENRFID_SetNetwork Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_SetNetwork A928EU, A948EU The function permits to configure the network address, the netmask and the default gateway of the reader. The settings are activated after a reboot of the reader.
[in] Handle: The handle that identifies the device.
[in] IPAddress: The IP address to set in the form XXX.XXX.XXX.XXX
[in] NetMask: The netmask to set in the form XXX.XXX.XXX.XXX
[in] Gateway: The Gateway to set in the form XXX.XXX.XXX.XXX An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_SetNetwork(CAENRFIDHandle
*IPAddress, char *NetMask, char *Gateway);
Handle, char NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
17 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library 1.3.36. CAENRFID_SetDE_SB Revision date:
17/01/2007 Revision:
2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_SetDE_SB A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function permits to enable the use of the data exchange status bit in the ISO18000-6b anticollision algorithm.
[in] Handle: The handle that identifies the device.
[in] Enable: Enable flag. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_SetDE_SB(CAENRFIDHandle Handle, unsigned int Enable);
1.3.37. CAENRFID_GetDE_SB Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetDE_SB A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function permits to know if the data exchange status bit is used in the ISO18000-6b anticollision algorithm.
[in] Handle: The handle that identifies the device.
[out] Status: The status flag. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetDE_SB(CAENRFIDHandle handle, unsigned short *Status);
1.3.38. CAENRFID_ProgramID Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_ProgramID A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function permits to program an EPC Class 1 Gen 1 tag
[in] Handle: The handle that identifies the device.
[in] TagID: The EPC to program in the tag.
[in] Password: The kill password to program in the tag.
[in] Lock: Aflag indicating if the EPC has to be locked. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_ProgramID(CAENRFIDHandle Handle, CAENRFIDTag *TagID, char Password, unsigned short Lock);
1.3.39. CAENRFID_KillTag Name:
Reader:
CAENRFID_KillTag A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
18 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 Description:
Parameters:
Returns:
Syntax:
The function permits to kill an EPC Class 1 Gen 1 tag
[in] Handle: The handle that identifies the device.
[in] TagID: The EPC of the tag.
[in] Password: The kill password for the tag. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_KillTag(CAENRFIDHandle Handle, CAENRFIDTag
*TagID, char Password);
1.3.40. CAENRFID_BlockWrite Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_BlockWrite A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU This function allows to write Length bytes to the memory of a specific tag identified by the ID (regardless of its status) at the address specified by Address. This function doesn't work with semi-passive tags
[in] Handle: The handle that identifies the device.
[in] ID: The tag ID.
[in] Address: The address of the memory to write.
[in] Length: The number of bytes to write.
[in] Data: The data to write in the tag's memory An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_BlockWrite(CAENRFIDHandle handle, CAENRFIDTag *ID, int Address, int Length, void *Data);
1.3.41. CAENRFID_SetRS232 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_SetRS232 A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function permits to configure the serial communication of the reader
[in] Handle: The handle that identifies the device.
[in] baud: The baudrate value.
[in] datab: The databit value.
[in] stopb: The stopbit value.
[in] parity: The parity value.
[in] flowc: The flowcontrol value An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_SetRS232(CAENRFIDHandle handle, unsigned long baud, unsigned long datab, unsigned long stopb, CAENRFID_RS232_Parity parity, CAENRFID_RS232_FlowControl flowc);
NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
19 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library 1.3.42. CAENRFID_SetDateTime Revision date:
17/01/2007 Revision:
2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_SetDateTime A828EU, A828US, A829EU, A829US, A946EU, A949EU, A928EU, A948EU The function permits to set the date e the time in the reader.
[in] Handle: The handle that identifies the device.
[in] datetime: The current date ed time. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_SetDateTime(CAENRFIDHandle handle, char
*datetime);
CAENRFIDlib_API CAENRFIDErrorCodes __stdcall _CAENRFID_GroupSelUnsel(CAENRFIDHandle handle, char
*SourceName, CAENRFID_SelUnsel_Op code, int Address, int BitMask, void *data, CAENRFIDTag *ID);
1.3.43. CAENRFID_GetIO Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetIO A928EU, A948EU The function permits to read the IO register
[in] Handle: The handle that identifies the device.
[out] IORegister: The current IO Register An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetIO(CAENRFIDHandle handle, unsigned int
*IORegister);
1.3.44. CAENRFID_SetIO Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_SetIO A928EU, A948EU The function permits to write the IO register
[in] Handle: The handle that identifies the device.
[in] IORegister: The IO Register value. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_SetIO(CAENRFIDHandle handle, unsigned int IORegister);
1.3.45. CAENRFID_SetSourceConfiguration Name:
Reader:
Description:
Parameters:
CAENRFID_SetSourceConfiguration A928EU, A948EU The function permits to configure the Logical Source
[in] Handle : The handle that identifies the device.
[in] SourceName: The Name of the Logical Source. NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
20 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 Returns:
Syntax:
[in] parameter: The parameter of Logical Source to configure.
[in] value: The the value of the parameter. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_SetSourceConfiguration(CAENRFIDHandle handle, char *SourceName, CAENRFID_SOURCE_Parameter parameter, int value);
1.3.46. CAENRFID_GetSourceConfiguration Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetSourceConfiguration A928EU, A948EU The function permits to get the value of the Logical Source configuration
[in] Handle: The handle that identifies the device.
[in] SourceName: The Name of the Logical Source.
[in] parameter: The parameter of Logical Source to configure.
[out] value: The the value of the parameter An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetSourceConfiguration(CAENRFIDHandle handle, char *SourceName, CAENRFID_SOURCE_Parameter parameter, int *pvalue);
1.3.47. CAENRFID_GetAllocatedTriggers Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetAllocatedTriggers A928EU, A948EU The function permits to get the allocated triggers
[in] Handle: The handle that identifies the device.
[out] TriggerNum: The number of triggers allocated.
[out] Triggers: The Triggers's names of allocated triggers An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetAllocatedTriggers(CAENRFIDHandle handle, int
*TriggerNum, char **Triggers);
1.3.48. CAENRFID_GetAllocatedChannels Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetAllocatedTriggers A928EU, A948EU The function permits to get the allocated channels
[in] Handle: The handle that identifies the device.
[out] ChannelNum: The number of channels allocated.
[out] Channels: The channels's names of allocated channels An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID GetAllocatedChannels(CAENRFIDHandle handle, NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
21 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 int *ChannelNum, char **Channels);
1.3.49. CAENRFID_SetEventMode Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_SetEventMode A928EU, A948EU The function permits to set the Event Generation Mode of the reader
[in] Handle: The handle that identifies the device.
[in] EMode: The Event Mode An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_SetEventMode(CAENRFIDHandle handle, CAENRFID_EventMode EMode);
1.3.50. CAENRFID_GetEventMode Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetEventMode A928EU, A948EU The function permits to get the Event Generation Mode of the reader
[in] Handle: The handle that identifies the device.
[out] EMode: The Event Mode of the reader An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetEventMode(CAENRFIDHandle handle, CAENRFID_EventMode *EMode);
1.3.51. CAENRFID_FirmwareUpgrade Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_FirmwareUpgrade A928EU, A948EU The function permits to upgrade the reader's firmware
[in] Handle: The handle that identifies the device.
[in] type: The kind of upgrading
[in] arg: The argument for the upgrading in the form '[tftpserver ip]:[filename]'
An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_FirmwareUpgrade(CAENRFIDHandle handle, CAENRFID_FWUpgradeType type, char *arg);
1.3.52. CAENRFID_Lock_C1G2 Name:
Reader:
CAENRFID_Lock_C1G2 A928EU, A948EU NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
22 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 Description:
Parameters:
Returns:
Syntax:
This function allows to lockthe memory of a specific tag identified by the ID and by Payload
[in] Handle : The handle that identifies the device.
[in] ID : The tag ID.
[in] Payload : The payload of the tag's memory. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_Lock_C1G2(CAENRFIDHandle handle, CAENRFIDTag *ID, int payload);
1.3.53. CAENRFID_KillTag_C1G2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_KillTag_C1G2 A928EU, A948EU The function permits to kill an EPC Class 1 Gen 2 tag
[in] Handle : The handle that identifies the device.
[in] TagID : The EPC of the tag.
[in] Password : The password for the tag. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_KillTag_C1G2(CAENRFIDHandle handle, CAENRFIDTag *ID, int password);
1.3.54. CAENRFID_KillTag_C1G2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_KillTag_C1G2 A928EU, A948EU The function permits to kill an EPC Class 1 Gen 2 tag
[in] Handle : The handle that identifies the device.
[in] TagID : The EPC of the tag.
[in] Password : The password for the tag. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_KillTag_C1G2(CAENRFIDHandle handle, CAENRFIDTag *ID, int password);
1.3.55. CAENRFID_ProgramID_EPC119 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_ProgramID_EPC119 A928EU, A948EU The function permits to program an EPC 119 tag
[in] Handle: The handle that identifies the device.
[in] ID: The actual ID of the tag.
[in] NewID: The new ID for the specified tag. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_ProgramID_EPC119(CAENRFIDHandle handle, CAENRFIDTag *ID, char *NewID );
NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
23 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 1.3.56. CAENRFID_ProgramID_C1G2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_ProgramID_C1G2 A928EU, A948EU The function permits to program an EPC Class 1 Gen 2 tag
[in] Handle: The handle that identifies the device.
[in] ID: The EPC to program in the tag.
[in] nsi: The NSI value for the EPC C1G2. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_ProgramID_C1G2(CAENRFIDHandle handle, CAENRFIDTag *ID, unsigned short nsi );
1.3.57. CAENRFID_Read_C1G2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_Read_C1G2 A928EU, A948EU This function allows to read Length bytes from the bank memory, specified by membank, of a specific tag identified by the ID
(regardless of its status) at the address specified by Address.
[in] Handle : The handle that identifies the device.
[in] ID : The tag ID.
[in] membank : The memory Bank of EPC C1G2 Tag
[in] Address : The address of the memory to read.
[in] Length : The number of bytes to read.
[out] Data : The data read from the tag's memory. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_Read_C1G2(CAENRFIDHandle handle, CAENRFIDTag *ID, short membank, int Address, int Length, void
*Data);
1.3.58. CAENRFID_Write_C1G2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_Write_C1G2 A928EU, A948EU This function allows to write Length bytes to the bank memory, specified by membank, of a specific tag identified by the ID
(regardless of its status) at the address specified by Address.
[in] Handle : The handle that identifies the device.
[in] ID : The tag ID.
[in] membank : The memory Bank of EPC C1G2 Tag
[in] Address : The address of the memory to write.
[in] Length : The number of bytes to write.
[in] Data : The data to write in the tag's memory. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_Write_C1G2(CAENRFIDHandle handle, CAENRFIDTag *ID, short membank,int Address, int Length, void NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
24 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library
*Data);
1.3.59. CAENRFID_QueryTag_C1G2 Revision date:
17/01/2007 Revision:
2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_QueryTag_C1G2 A928EU, A948EU The function permits to perform the Query command of C1G2 protocol
[in] SourceName : The Name of the Logical Source.
[out] isPresent: A flag indicating if the tag answered at Query command An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_QueryTag_C1G2(CAENRFIDHandle handle, char
*SourceName, short *isPresent);
1.3.60. CAENRFID_SetQ_C1G2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_SetQ_C1G2 A928EU, A948EU The function permits to set the Q parameter of C1G2 protocol
[in] Q : The value of Q. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_SetQ_C1G2(CAENRFIDHandle handle, int Q);
1.3.61. CAENRFID_GetQ_C1G2 Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetQ_C1G2 A928EU, A948EU The function permits to get the Q parameter of C1G2 protocol
[out] Q : The value of Q. An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetQ_C1G2(CAENRFIDHandle handle, int *Q);
1.3.62. CAENRFID_GetReaderInfo Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_GetReaderInfo A928EU, A948EU Permits to read the Model and the Serial number of the Reader
[out] Model :
[out] SerialNum :
An error code about the execution of the function CAENRFIDlib_API CAENRFIDErrorCodes __stdcall CAENRFID_GetReaderInfo(CAENRFIDHandle handle,char
*Model, char *SerialNum);
Returns the model of the reader. Returns the Serial number of the reader. NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
25 Document type:
User's Manual (MUT) Title:
RFID ANSI C Library Revision date:
17/01/2007 Revision:
2 1.3.63. CAENRFID_FreeTagsMemory Name:
Reader:
Description:
Parameters:
Returns:
Syntax:
CAENRFID_FreeTagsMemory A928EU, A948EU The function permits to free the allocated by CAENRFIDInventory
[in] Tags : Reference to CAENRFIDTag obtained from CAENRFIDInventory An error code about the execution of the function CAENRFIDlib_API void __stdcall CAENRFID_FreeTagsMemory(CAENRFIDTag **Tags) NPO:
00117/03:RFLIB.MUTx/02 Filename:
RFIDCLIB_REV2.DOC Number of pages:
26 Page:
26
| 1 | User Manual 4 | Users Manual | 1.72 MiB |
Technical Information Manual Revision n. 1 18 February 2006 RFID SOFTWARE USER INTERFACE NPO:
00117/03:Demox.MUTx/01 Document type:
User's Manual (MUT) INDEX Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 1. OVERVIEW ................................................................................................................................................5 2. GETTING STARTED ................................................................................................................................6 2.3.1. 2.3.2. 2.3.3. 2.1. SOFTWARE USER INTERFACE: INSTALLATION.........................................................................................6 2.2. LAUNCHING THE SOFTWARE USER INTERFACE.......................................................................................7 2.3. CONNECTION CONFIGURATION...............................................................................................................8 Reader protocol configuration ......................................................................................................8 Network configuration...................................................................................................................8 Input output management..............................................................................................................9 2.4. LOGICAL SOURCE SELECTION .................................................................................................................9 2.5. DETECTING TEST TAGS WITH THE RF FIELD..........................................................................................10 2.6. READOUT OF ONE TAGS MEMORY........................................................................................................12 EPC protocol tags operations .....................................................................................................13 2.7. TEMPERATURE MONITORING WITH THE SEMIPASSIVE TAG....................................................................14 2.8. CREATING THE LOG FILE ......................................................................................................................15 2.9. RF FIELD TEST .....................................................................................................................................15 2.10. QUIT CAEN RFID DEMO PROGRAM................................................................................................15 ISO18000-6B PROTOCOL TAGS OPERATIONS ...................................................................................15 2.11. EPC1.19 PROTOCOL TAGS OPERATIONS ...........................................................................................17 2.12. 2.12.1. EPC 1.19 Tag Data memory mapping (96 bit)............................................................................17 2.12.2. EPC 1.19 Tag Data memory mapping (64 bit)............................................................................18 2.6.1. 3. FIRMWARE UPGRADE .........................................................................................................................19 3.1. 3.2. FIRMWARE UPGRADE VIA SERIAL PORT ................................................................................................19 FIRMWARE UPGRADE VIA TCP/IP.........................................................................................................20 4. RFID TEST PROGRAM..........................................................................................................................22 4.1. CONNECTION CONFIGURATION.............................................................................................................22 4.2. SETTINGS .............................................................................................................................................23 Antenna selection.........................................................................................................................23 Protocol selection........................................................................................................................23 Power settings .............................................................................................................................24 Reader network configuration.....................................................................................................24 START TEST..........................................................................................................................................24 4.3. 4.4. QUIT CAEN RFID TEST PROGRAM......................................................................................................25 4.2.1. 4.2.2. 4.2.3. 4.2.4. NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
2 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 5. RFID CSDEMO PROGRAM...................................................................................................................26 5.1. CONNECTION CONFIGURATION.............................................................................................................26 5.2. START INVENTORY ...............................................................................................................................27 5.3. READ TAGS MEMORY............................................................................................................................27 LIST OF FIGURES FIG. 2.1 CAEN RFID CD MAIN MENU......................................................................................................6 FIG. 2.2 CAEN RFID DEMO START WINDOW.............................................................................................7 FIG. 2.3 CONNECTION PORT CONFIGURATION .............................................................................................8 FIG. 2.4 READER NETWORK CONFIGURATION.............................................................................................8 FIG. 2.5 READER NETWORK CONFIGURATION.............................................................................................9 FIG. 2.6 LOGICAL SOURCE SELECTION AND TEST.........................................................................................9 FIG. 2.7 EVENT MODE CONFIGURATION ....................................................................................................10 FIG. 2.8 CHANGE EVENT MODE MESSAGE .................................................................................................11 FIG. 2.9 ASYNCHRONOUS ACQUISITION CONFIGURATION.........................................................................11 FIG. 2.10 RFID SERVER............................................................................................................................11 FIG. 2.11 TAGS MEMORY...........................................................................................................................12 FIG. 2.12 TAG READOUT ...........................................................................................................................13 FIG. 2.13 TAG PROGRAMMING ..................................................................................................................13 FIG. 2.14 TAG KILLING..............................................................................................................................14 FIG. 2.15 TEMPERATURE MONITORING/1 ..................................................................................................14 FIG. 2.16 TEMPERATURE MONITORING/2 ..................................................................................................15 FIG. 2.17 ISO18000-6B TAGS MEMORY...................................................................................................16 FIG. 2.18 ISO18000-6B TAG READOUT....................................................................................................16 FIG. 2.19 EPC1.19 TAG PROGRAMMING ...................................................................................................17 FIG. 2.20 EPC1.19 TAG LOCKING.............................................................................................................17 FIG. 2.21 GENERAL STRUCTURE OF 96 BIT EPC NUMBER .........................................................................17 FIG. 2.22 SEPARATION OF 96 BIT DATA STRUCTURE FOR UCODE EPC 1.19............................................18 FIG. 2.23 MAPPING OF 96 BIT DATA STRUCTURE INTO UCODE EPC 1.19 MEMORY ................................18 FIG. 2.24 GENERAL STRUCTURE OF 64 BIT EPC NUMBER .........................................................................18 FIG. 2.25 SEPARATION OF 64 BIT DATA STRUCTURE FOR UCODE EPC 1.19............................................18 FIG. 2.26 MAPPING OF 64 BIT DATA STRUCTURE INTO UCODE EPC 1.19 MEMORY ................................18 FIG. 3.1 CAEN RFID DEMO DIRECTORIES.............................................................................................19 FIG. 3.2 CAEN RFIDUPGRADE/1.............................................................................................................19 FIG. 3.3 SELECTING THE IMAGE FILE.........................................................................................................19 FIG. 3.4 PUMPKIN MENU WINDOW..........................................................................................................20 FIG. 3.5 PUMPKIN OPTIONS WINDOW......................................................................................................20 NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
3 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 FIG. 3.6 FIRMWARE UPGRADE BROWSER...................................................................................................21 FIG. 3.7 FIRMWAREUPGRADE MESSAGE ....................................................................................................21 FIG. 3.8 CONFIRMATION MESSAGE............................................................................................................21 FIG. 4.1 RFID TEST MAIN MENU...............................................................................................................22 FIG. 4.2 CONNECTION PORT CONFIGURATION ...........................................................................................22 FIG. 4.3 SOURCE SELECTION .....................................................................................................................23 FIG. 4.4 SETTING THE PROTOCOL ..............................................................................................................23 FIG. 4.5 POWER SETTINGS FIELDS .............................................................................................................24 FIG. 4.6 NETWORK CONFIGURATION.........................................................................................................24 FIG. 4.7 TAGS DETECTION.........................................................................................................................24 FIG. 5.1 RFID TEST MAIN MENU...............................................................................................................26 FIG. 5.2 CONNECTION CONFIRMATION ......................................................................................................26 FIG. 5.3 TAGS DETECTION.........................................................................................................................27 FIG. 5.4 TAGS MEMORY READOUT.............................................................................................................27 LIST OF TABLES TABLE 2.1 CAEN RFID DEMO DIRECTORIES ...........................................................................................7 NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
4 Document type:
User's Manual (MUT) Title:
RFID Software User Interface 1. Overview Revision date:
18/02/2006 Revision:
1 The present manual describes how to operate with the software pack provided with CAEN RFID UHF readers and development kits. The CD includes the following tools:
RFID Java Demo program RFID Visual C++ test program RFID .Net Sample Upgrade
(for A928EU/A948EU, A828EU/A829EU, firmware and protocols A828US/A829US, A949EU/A946EU) Uninstall tool NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
5 Document type:
User's Manual (MUT) Title:
RFID Software User Interface 2. Getting started 2.1. Software User interface: installation Revision date:
18/02/2006 Revision:
1 Before you begin, be sure that:
the Reader is not connected to your computer;
the Reader supports your operating system (Windows 2000/XP);
1. 2. To install the software:
Place the CD in the CD tray in your PC. Then the following menu will open:
Fig. 2.1 CAEN RFID CD Main Menu If the menu does not open, then Double-click on My Computer. Double-click on the CD-ROM drive. Double click on index.html. Double-click on the file name Install CAEN RFID Demo option. NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
6 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 Setup will install the files in the folder listed under Destination Folder. To install to this folder, click Next. To install to a different folder, click Browse and select another folder. The Setup program creates the following directories:
Table 2.1 CAEN RFID DEMO directories Directory/file name Java CAENRFIDlib.dll1 lib sources RFID_Demo.exe RFIDUpgrade.exe TestRFID.exe Unins000 Directory files description RFID Demo Java Version (see 2) Include files CAENRFIDlib.lib (stub for Microsoft Visual C++ 6.0) demo program Microsoft Visual C++ 6.0 Source files demo program Upgrade firmware and protocols RFID Test program Uninstall tool 2.2. Launching the Software User interface The RFID Demo Java Version is started by launching the CAENRFIDJavaDemo.jar file in the CAEN_RFID_Development_kit_Java\CAENRFIDJavaDemo the CDs Programmer's Interface directory. The present program is developed for demonstrative purposes, the Java classes are available in the Programmer's Interface directory of the CD. Before launching the RFID Demo Java Version, it is necessary to install the Java 2 Platform Standard Edition 5.0, available at: http://java.sun.com/j2se/1.5.0/download.jsp folder in Fig. 2.2 CAEN RFID Demo start window 1 CAENRFIDLib library is described in the relevant Technical Information Manual NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
7 Document type:
User's Manual (MUT) Title:
RFID Software User Interface 2.3. Connection configuration Revision date:
18/02/2006 Revision:
1 Once you have connected the CAEN UHF RFID Reader to your PC, turn it ON, then:
Click on File > Open connection The following pop-up window will open:
Fig. 2.3 Connection port configuration Choose the connection type; if you are using TCP-IP enter the IP address (default address: 192.168.0.125), if you are using RS232, type the connected port (COM1, COM2) then click on <Connect>. If you wish to use RS232 or USB, please make sure that the Java Platform you are running supports such ports. 2.3.1. Reader protocol configuration is possible to change the used protocol (ISO18000-6B or EPC Optionally, it C1G1/C1G2);
click on configuration > change readers protocol A pop-up window will allow to chose between ISO18000-6B (which supports also Philips UCODE EPC 1.19) and EPC C1G1. If the protocol is changed, a reader reboot will be performed; then it is necessary to shut and re-start the CAEN RFID Demo program. 2.3.2. Network configuration Optionally, it is possible to update the readers network settings;
click on configuration > network setup The following pop-up window will open (the figure shows the default configuration):
Fig. 2.4 Reader Network configuration NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
8 Document type:
User's Manual (MUT) Title:
RFID Software User Interface 2.3.3. Input output management Revision date:
18/02/2006 Revision:
1 This function allows to handle the reader general purpose inputs/outputs;
click on configuration > I/O Management The following pop-up window will open:
By checking the Output boxes, the relevant signal will be driven high. The Input status is also monitored: red = active, green = idle. Fig. 2.5 Reader Network configuration 2.4. Logical source selection Click on configuration > configure logical source The following pop-up window will open:
Fig. 2.6 Logical source selection and test the antenna(s) status is checked:
BAD (antenna not connected) = RED POOR (antenna with faulty operation) = YELLOW GOOD (antenna ok) = GREEN Then choose the antenna(s) you wish to use. Finally it is necessary to set the thresholds:
Observed:
READCYCLE MODE (see 2.5): the number of subsequent times a tag must appear in an acquisition before it shifts from glimpsed to observed NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
9 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 TIME MODE (see 2.5): the number of milliseconds a tag must appear in an acquisition before it shifts from glimpsed to observed Lost:
READCYCLE MODE: the number of subsequent times an observed tag must disappear from an acquisition before it shifts from observed to lost TIME MODE: the number of milliseconds an observed tag must disappear from an acquisition before it shifts from observed to lost Read Cycle: the number of times an acquisition must be timed out and then restarted Confirm settings by clicking on <Configure>. Thresholds are meaningful only with Asynchronous Acquisition (see 2.5) 2.5. Detecting test tags with the RF field Now the Reader is ready for detecting tags; click on either:
<Synchronous Acquisition>
<Asynchronous Acquisition>
With Synchronous Acquisition, a one shot readout is performed. Asynchronous Acquisition allows to perform either Timed Acquisition or a I/O Timed-
out acquisition. In the first place it is necessary to set the Event mode by clicking on:
Configuration>Configure Event Mode The following window opens:
Fig. 2.7 Event mode configuration If READCYCLE MODE is selected, the logical source thresholds are expressed in cycles, whose duration is equal to the Delay time set when Asynchronous Acquisition is launched. If TIME MODE is selected, the logical source thresholds are expressed in milliseconds; it must be noticed that the thresholds might not be multiple of the delay time, so a tag can change its status after a non-integer number of cycles. If NOEVENT MODE is selected, the tags are continuously scanned, the threshold values are meaningless (the tag is considered either inside or outside the readers field and no Glimpsed/Observed status is notified) After changing Event Mode it is necessary to restart both the Reader and the RFID Demo Java Version. The following message will be shown:
NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
10 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 Fig. 2.8 Change Event mode message Fig. 2.9 Asynchronous Acquisition configuration If you wish to make a Timed Acquisition in READCYCLE MODE:
choose Timer as trigger type in the drop down menu of the Asynchronous Configuration which is started as Asynchronous Acquisition is selected. set the timer period in Delay time field set the notification on Local or Remote host: in the latter case you have to enter the host IP address Start acquisition The notification takes place on the RFID Server window, which is shown either on the Local host or on the Remote one:
Fig. 2.10 RFID Server If you wish to make a I/O Timed-out Acquisition in READCYCLE MODE:
choose the General Purpose Input you wish to use as trigger type in the drop down menu of the Asynchronous Configuration. set the time out delay in Delay time field NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
11 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 set the notification on Local or Remote host: in the second case you have to enter the host IP address Start acquisition The notification takes place on the RFID ServerConfiguration; after the first acquisition the Reader waits for one Delay time period, then checks the status of the used input: if it is high, then the second acquisition takes place, otherwise it is timed out; at this point the Reader waits for another Delay time, then checks the status of the used input again. If you wish to make a Timed Acquisition in TIME MODE:
choose Timer as trigger type in the drop down menu of the Asynchronous Configuration which is started as Asynchronous Acquisition is selected. set the timer period in Delay time field set the notification on Local or Remote host: in the latter case you have to enter the host IP address Start acquisition The notification takes place on the RFID Server window, which is shown either on the Local host or on the Remote one. The status does not depend on the number of performed cycles, but ONLY on the threshold values (see 2.4); the Delay time must be smaller than the thresholds. If you wish to make an acquisition in NOEVENT MODE, simply :
set the timer period in Delay time field set the notification on Local or Remote host: in the latter case you have to enter the host IP address Start acquisition The notification takes place on the RFID Server window, which is shown either on the Local host or on the Remote one, no status is notified. 2.6. Readout of one tags memory Now the ISO18000-6B detected tags are ready for read/write operations. In case of Timed, Continuous or I/O Acquisition it is necessary to stop scanning, by clicking on the stop acquisition button. Now click on one of the tags Unique IDs; then go to:
Features
>ISO18000-6B
>Read/Write Tag Memory The following window is shown:
Fig. 2.11 Tags memory NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
12 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 By writing in the Value field, it is possible to update the tag memory; changes are saved via the <Update> button, while <Restore> allows to recover the former value. In order to lock one particular address in the tag memory, go to:
Features
>ISO18000-6B
>Lock The following window is shown; <Lock> allows to lock one particular address, <Cancel>
to quit. Locked addresses cannot be changed anymore. Fig. 2.12 Tag readout The configuration of the ISO18000-6B compliant tags is the following:
Byte 0,1 27 810 11 1217 18219 220223 Content E0, 04 hex xx hex 00 hex 02 hex FF hex 00 hex 57 5F 4F 4B hex Status locked locked unlocked unlocked unlocked unlocked unlocked Description Unique serial number Unique serial number User memory User memory User memory User memory w_ok in ASCII, user memory The CAEN RFID Demo program allows to write only bits [2; 17]. 2.6.1. EPC protocol tags operations If EPC tags are detcted, then go to:
Features
>EPC For (over)writing the tags ID, setting the password, and locking them:
>Program ID Fig. 2.13 Tag programming NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
13 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 Go to:
Features
>EPC
>Kill For killing the tag (the password is required). Once killed the tag does not respond to
(any) reader anymore. Fig. 2.14 Tag killing The configuration of the EPC Class 1 Gen 1 compliant tags is the following:
Byte 00, 01 hex 02 hex 0307 hex 080F hex 1017 hex 1837 hex 38FF hex Type System System System System System User RFU Status locked unlocked unlocked unused unlocked unlocked Description Tag header EPC portion EPC portion EPC portion User memory (256 bit) 2.7. Temperature monitoring with the semipassive tag The semipassive tag Mod. A927 includes a temperature sensor; so it is possible to view the temperature parameter as a function of time. This is possible by clicking on the termometer icon. Fig. 2.15 Temperature monitoring/1 A pop-up window with the temperature trace will be then shown:
NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
14 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 Fig. 2.16 Temperature monitoring/2 Status:
Green = tag inside readers field Red = tag outside readers field 2.8. Creating the Log file Click on configuration > Enable logging Then start the Continuous acquisition. When the acquisition is stopped, it will be possible to save the log text file, containing information on the detected tags, for example:
Tue Apr 19 11:01:19.011 e004840306010000 Glimpsed Tue Apr 19 11:01:19.101 e004840306010000 Glimpsed Tue Apr 19 11:01:19.201 e004840306010000 Glimpsed N.B.: creating the Log file is possible only with Continuous acquisition 2.9. RF Field test It is possible to test the RF field emissions in the following way:
Click on configuration > select test & read point Then select the read point to be tested (0..3). Go to the main menu, then set the desired power and choose single acquisition. Click on configuration > experimental > RF ON It is now possible to test the RF field emission on the selected read point. In order to test another read point it is necessary to repeat the procedure from the start. 2.10. Quit CAEN RFID Demo program For quitting the CAEN RFID Demo program click on File > exit Then turn off the reader and disconnect the antenna cable, the power cord and the link cable. 2.11. ISO18000-6B protocol tags operations The ISO18000-6B detected tags are ready for read/write operations. It is necessary to stop scanning, by clicking on the stop acquisition button. Now click on one of the tags Unique IDs; then go to:
NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
15 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 Features
>ISO18000-6B
>Read/Write Tag Memory The following window is shown:
Fig. 2.17 ISO18000-6B Tags memory By writing in the Value field, it is possible to update the tag memory; changes are saved via the <Update> button, while <Restore> allows to recover the former value. In order to lock one particular address in the tag memory, go to:
Features
>ISO18000-6B
>Lock The following window is shown; <Lock> allows to lock one particular address, <Cancel>
to quit. Locked addresses cannot be changed anymore. Fig. 2.18 ISO18000-6B Tag readout The configuration of the ISO18000-6B compliant tags is the following:
Byte 0,1 27 810 11 1217 18219 220223 Content E0, 04 hex xx hex 00 hex 02 hex FF hex 00 hex 57 5F 4F 4B hex Status locked locked unlocked unlocked unlocked unlocked unlocked Description Unique serial number Unique serial number User memory User memory User memory User memory w_ok in ASCII, user memory The CAEN RFID Demo program allows to write only bits [2; 17]. NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
16 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 2.12. EPC1.19 protocol tags operations If EPC1.19 tags are detected, then go to:
Features
>EPC1.19 For (over)writing the tags ID and Memory:
> Read/Write Tag Memory Fig. 2.19 EPC1.19 Tag programming In order to lock one particular address in the tag memory, go to Go to:
Features
>EPC1.19 The following window is shown; <Lock> allows to lock one particular address, <Cancel>
to quit. Locked addresses cannot be changed anymore.
>Lock The configuration of the EPC 1.19 compliant tags is the following:
Fig. 2.20 EPC1.19 Tag locking 2.12.1. EPC 1.19 Tag Data memory mapping (96 bit) Fig. 2.21 General structure of 96 bit EPC number NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
17 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 Fig. 2.22 Separation of 96 bit data structure for UCODE EPC 1.19 Fig. 2.23 Mapping of 96 bit data structure into UCODE EPC 1.19 memory 2.12.2. EPC 1.19 Tag Data memory mapping (64 bit) Fig. 2.24 General structure of 64 bit EPC number Fig. 2.25 Separation of 64 bit data structure for UCODE EPC 1.19 Fig. 2.26 Mapping of 64 bit data structure into UCODE EPC 1.19 memory NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
18 Document type:
User's Manual (MUT) Title:
RFID Software User Interface 3. Firmware upgrade Revision date:
18/02/2006 Revision:
1 3.1. Firmware upgrade via serial port In order to upgrade the Reader firmware, connect the it with the PC Host via RS232, then open the following directory:
Now launch RFIDUpgrade.exe:
Fig. 3.1 CAEN RFID DEMO directories Fig. 3.2 CAEN RFIDUpgrade/1 Select Firmware in the Upgrade Menu and the connected port, then Browse the image file to be uploaded (for example: image-2.0b.bin):
Fig. 3.3 Selecting the image file Now click on <Upgrade>; it will take 10 minutes for uploading the updated firmware and rebooting the Reader; when the Reader is ready the ISO/EPC and the Active leds will light up: do not turn off the Reader before the Active led lights on and then off!
NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
19 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 The image file can be found in the Upgrade_img_file directory of the Driver, Demo software and Technical manuals CD ROM (included in the RFID Development Kit); it can also be downloaded at: http://www.caen.it/rfid/english/download.php 3.2. Firmware upgrade via TCP/IP The Firmware upgrade via TCP/IP works only with the CAENRFID Demo Java Version. First you need a TFTP Server & Client application, if you have not one installed, you can download (from http://www.klever.net/ ), install and run the pumpkin.exe freeware application:
Fig. 3.4 PumpKIN Menu Window Select [Options] and browse the folder where the image file resides with the following selections, then press [OK]
Fig. 3.5 PumpKIN Options Window Connect to the Reader by using CAEN RFID Demo Java version and select Configuration>Firmware Upgrade enter the TFTP server address and browse the image file to be loaded into the Reader, then press [OK]:
NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
20 Document type:
User's Manual (MUT) Title:
RFID Software User Interface Revision date:
18/02/2006 Revision:
1 The following information message will then be shown:
Fig. 3.6 Firmware upgrade browser Press ok and this confirmation message will be returned:
Fig. 3.7 Firmwareupgrade message Press YES then Download image via TFTP; the Firmware Upgrade is then completed. Fig. 3.8 Confirmation message NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
21 Document type:
User's Manual (MUT) Title:
RFID Software User Interface 4. RFID Test program Revision date:
18/02/2006 Revision:
1 This is a simple VisualC++ test program: go to the main directory CAEN RFID DEMO KIT, then launch the TestRFID.exe executable file; the following Menu will be launched:
Fig. 4.1 RFID Test main menu 4.1. Connection configuration Once you have connected the CAEN UHF RFID Reader to your PC, turn it ON, then:
Click on File > Connect The following pop-up window will open:
Fig. 4.2 Connection port configuration Choose the connection type; if you are using TCP-IP enter the IP address (default:
192.168.0.125), if you are using RS232, type the connected port (COM1, COM2) then click on <Connect>. NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
22 Document type:
User's Manual (MUT) Title:
RFID Software User Interface 4.2. Settings Revision date:
18/02/2006 Revision:
1 4.2.1. Antenna selection Click on settings > set source ; then flag the antenna(s) you wish to use Fig. 4.3 Source selection 4.2.2. Protocol selection Click on settings > set source; then flag the protocol you wish to use Fig. 4.4 Setting the protocol NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
23 Document type:
User's Manual (MUT) Title:
RFID Software User Interface 4.2.3. Power settings Revision date:
18/02/2006 Revision:
1 Click on settings > set source; then type the power settings you wish to use Fig. 4.5 Power settings fields 4.2.4. Reader network configuration Optionally, it is possible to update the readers network settings;
click on settings > set network The following pop-up window will open (the figure shows the default configuration):
Fig. 4.6 Network configuration 4.3. Start Test Now click on Start Test : the name of the tags in the readers field will be shown. Click on Stop test in order to stop acquisition. Fig. 4.7 Tags detection NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
24 Document type:
User's Manual (MUT) Title:
RFID Software User Interface 4.4. Quit CAEN RFID Test program Revision date:
18/02/2006 Revision:
1 For quitting the CAEN RFID Test program click on File > exit Then turn off the reader and disconnect the antenna cable, the power cord and the link cable. NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
25 Document type:
User's Manual (MUT) Title:
RFID Software User Interface 5. RFID CsDemo program Revision date:
18/02/2006 Revision:
1 This is a simple RFID .Net Sample program. First of all, go to:
http://www.microsoft.com/downloads/
then download and install on your PC the DotNet Framework 1.1 Then go CAENRFIDCsDemo.exe executable file; the following Menu will be launched:
the main directory CAEN RFID DEMO KIT, then to launch the Fig. 5.1 RFID Test main menu 5.1. Connection configuration Once you have connected the CAEN UHF RFID Reader to your PC, turn it ON, then:
Choose the connection type; if you are using TCP-IP enter the IP address (default:
192.168.0.125), if you are using RS232, type the connected port (COM1, COM2) then click on <Connect>. The following pop-up window will open:
Fig. 5.2 Connection confirmation NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
26 Document type:
User's Manual (MUT) Title:
RFID Software User Interface 5.2. Start inventory Revision date:
18/02/2006 Revision:
1 Select the tag type you want to read, then click on Inventory : the name of the tags in the readers field will be shown. Click on Disconnect in order to stop acquisition. Fig. 5.3 Tags detection 5.3. Read tags memory Select the tag type you want to read, then click on Read: the memory content of the tags in the readers field will be shown. Fig. 5.4 Tags memory readout NPO:
00117/03:Demox.MUTx/01 Filename:
RFIDDEMO_REV1.DOC Number of pages:
27 Page:
27
| frequency | equipment class | purpose | ||
|---|---|---|---|---|
| 1 | 2008-06-24 | 902.75 ~ 927.25 | DSS - Part 15 Spread Spectrum Transmitter | Original Equipment |
| app s | Applicant Information | |||||
|---|---|---|---|---|---|---|
| 1 | Effective |
2008-06-24
|
||||
| 1 | Applicant's complete, legal business name |
CAEN RFID srl
|
||||
| 1 | FCC Registration Number (FRN) |
0015858780
|
||||
| 1 | Physical Address |
via Vetraia, 11 - 55049 Viareggio (LU) - ITALY
|
||||
| 1 |
Viareggio, N/A 55049
|
|||||
| 1 |
Italy
|
|||||
| app s | TCB Information | |||||
| 1 | TCB Application Email Address |
k******@emcc.de
|
||||
| 1 | TCB Scope |
A4: UNII devices & low power transmitters using spread spectrum techniques
|
||||
| app s | FCC ID | |||||
| 1 | Grantee Code |
UVE
|
||||
| 1 | Equipment Product Code |
CAENRFID003
|
||||
| app s | Person at the applicant's address to receive grant or for contact | |||||
| 1 | Name |
A****** B****
|
||||
| 1 | Title |
CEO
|
||||
| 1 | Telephone Number |
+3905********
|
||||
| 1 | Fax Number |
+3905********
|
||||
| 1 |
a******@caen.it
|
|||||
| app s | Technical Contact | |||||
| n/a | ||||||
| app s | Non Technical Contact | |||||
| n/a | ||||||
| app s | Confidentiality (long or short term) | |||||
| 1 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
| 1 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
| if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
| app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
| 1 | Is this application for software defined/cognitive radio authorization? | No | ||||
| 1 | Equipment Class | DSS - Part 15 Spread Spectrum Transmitter | ||||
| 1 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | A528 - OEM UHF multiregional Compact Reader | ||||
| 1 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
| 1 | Modular Equipment Type | Does not apply | ||||
| 1 | Purpose / Application is for | Original Equipment | ||||
| 1 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
| 1 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
| 1 | Grant Comments | Power output listed is peak conducted. The antenna used for this transmitter must be installed to provide a separation distance of at least 20 cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter. End-users and installers must be provided with antenna installation instructions and transmitter operating conditions for satisfying RF exposure compliance. | ||||
| 1 | Is there an equipment authorization waiver associated with this application? | No | ||||
| 1 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
| app s | Test Firm Name and Contact Information | |||||
| 1 | Firm Name |
CMC Centro Misure Compatibilit srl
|
||||
| 1 | Name |
B****** R****
|
||||
| 1 | Telephone Number |
39044********
|
||||
| 1 | Fax Number |
39044********
|
||||
| 1 |
r******@cmclab.it
|
|||||
| Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
| 1 | 1 | 15C | CC | 902.75000000 | 927.25000000 | 0.4570000 | |||||||||||||||||||||||||||||||||||
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC