Reader classic-pro Reader

Transcription

1 Integration Guide i-scan classic-pro References for using the Advanced Protocol Frame instead off Standard Protocol Frame Preliminary public (B) N10710-e-ID-B.doc

2 Copyright 2011 by FEIG ELECTRONIC GmbH Lange Strasse 4 D Weilburg-Waldhausen Tel.: Note With the edition of this document, all previous editions become void. Indications made in this manual may be changed without previous notice. Copying of this document, and giving it to others and the use or communication of the contents thereof are forbidden without express authority. Offenders are liable to the payment of damages. All rights are reserved in the event of the grant of a patent or the registration of a utility model or design. Composition of the information in this document has been done to the best of our knowledge. FEIG ELECTRONIC GmbH does not guarantee the correctness and completeness of the details given in this manual and may not be held liable for damages ensuing from incorrect or incomplete information. Since, despite all our efforts, errors may not be completely avoided, we are always grateful for your useful tips. The instructions given in this manual are based on advantageous boundary conditions. FEIG ELECTRONIC GmbH does not give any guarantee promise for perfect function in cross environments and does not give any guaranty for the functionality of the complete system which incorporates the subject of this document. FEIG ELECTRONIC call explicit attention that devices which are subject of this document are not designed with components and testing methods for a level of reliability suitable for use in or in connection with surgical implants or as critical components in any life support systems whose failure to perform can reasonably be expected to cause significant injury to a human. To avoid damage, injury, or death, the user or application designer must take reasonably prudent steps to protect against system failures. FEIG ELECTRONIC GmbH assumes no responsibility for the use of any information contained in this document and makes no representation that they free of patent infringement. FEIG ELECTRONIC GmbH does not convey any license under its patent rights nor the rights of others. OBID and OBID i-scan are registered trademarks of FEIG ELECTRONIC GmbH. FEIG ELECTRONIC GmbH Page 2 of 9 N10710-e-ID-B.doc

3 Contents 1. Introduction 4 2. What is the difference of the protocol formats Standard Protocol Frame Advanced Protocol Frame Necessary modification in Software Applications Detecting s with different Protocol Frames in one App Detecting at serial port Detecting at USB... 9 FEIG ELECTRONIC GmbH Page 3 of 9 N10710-e-ID-B.doc

4 1. Introduction In the ambition to provide the markets with high performance RFID-Products, future RFID-s will only support the Advanced Protocol Frame. With the development oft the Mid Range ID ISC.MR200 in the year 2004 the Advanced Protocol has been realized the first time. All following readers like the ID ISC.LR(M)2000/2500 or the new ID ISC.MR102 supporting the Advanced Protocol and the Standard Protocol parallel. With the development of the new ID ISC.MR102 and the ID ISC.LR2500 readers the default reader configuration setting is set to Advanced Protocol only the first time. In future all further new reader developments will support the Advanced Protocol only! That s why FEIG ELECTRONIC GmbH strongly recommends to support the Advanced Protocol with new and also already existing software application. This will make sure that also in future the integration of new FEIG reader can be realized very easy and without running in any trouble. The following table gives an overview of the FEIG readers and the supported protocol formats: Firmware Support Standard Standard und Advanced Advanced i-scan MR100 / PR100 / PRH100 M01 / LR(M)200 MR200 / M02 MR101 / PR101 / PRH101/102 LR(M)2000 MR102 LR(M)2500 MRU102 LR1002 Default Setting Standard Standard & Advanced Advanced Firmware Support Standard Standard und Advanced Advanced classic-pro CPR/CPRM02 CPR04 CPR40.xx CPR44 CPR03 CPR50/52/MAX50 Future s Default Setting Standard Standard & Advanced Advanced Note: The reader send a status message 0x80 (Unknown Command) if a Standard Protocol is send and only Advanced Protocol Frame is supported. FEIG ELECTRONIC GmbH Page 4 of 9 N10710-e-ID-B.doc

5 2. What is the difference of the protocol formats With the Standard Protocol Frame the first byte indicates the length information (number of following bytes) of the following protocol. So the maximum protocol length is limited to 255 bytes only. With the Advanced Protocol Frame we are using 2 bytes for the length information of the protocol. Now it is theoretical possible to use protocol length up to bytes. In praxis the maximum protocol length is limited by the reader buffer size of the corresponding reader type. An Advanced Protocol starts always with the first STX byte [0x02] followed by the 2 byte length information ( ALENGTH ( )). So it is easy to identify if it is an Advanced- or a Standard Protocol Standard Protocol Frame Host n-2 n-1 n LENGTH = n Host COM-ADR CONTROL- BYTE (DATA) (5...n-2) n-1 n LENGTH = n COM-ADR CONTROL- BYTE STATU S (DATA) LENGTH: Number of protocol bytes: 1-n (6 255) incl. length byte and checksum 2.2. Advanced Protocol Frame Host (6...n-2) n-1 n STX (0x02) Host ALENGTH ALENGTH COM- ADR CONTROL- BYTE (DATA) (7...n-2) n-1 n STX (0x02) ALENGTH ALENGTH COM- ADR CONTROL- BYTE STATUS (DATA) STX: If the responded protocol of the starts with the STX sign (0x02) the protocol frame is Advanced Protocol-Length. Then the protocol length is defined by the 2 Byte Parameter ALENGTH. ALENGTH (n = ): Number of protocol bytes including STX, ALENGTH and FEIG ELECTRONIC GmbH Page 5 of 9 N10710-e-ID-B.doc

6 3. Necessary modification in Software Applications In constellations when OBID i-scan - and/or OBID classic-pro s, supporting only Standard Protocol Frame or only Advanced Protocol Frame, must be detected together in one application, the detection algorithm must be prepared with more logic to prevent long-term timeouts Detecting s with different Protocol Frames in one App High-level APIs like C++, Java or.net class libraries have integrated a flexible algorithm with the methods FindBaudRate() 1 and ReadInfo(). Programmers using these Methods have nothing to do. Applications based on Low-level APIs (up to the protocol layer realized with FEISC) must implement this logic separately. For serial port and USB, different strategies must be applied. For TCP/IP s the protocol frame can always be set to Advanced. 1 only for serial or Bluetooth connection FEIG ELECTRONIC GmbH Page 6 of 9 N10710-e-ID-B.doc

7 Detecting at serial port Detecting a at the serial port needs protocol transmissions. The program flow illustrated below works with the simple [0x52] Get Baud protocol, which is probed with different port frames, different port baudrates and alternating protocol frames. All this with reduced timeout to speed up the detection process. When all transmission settings are fit, the returns a response, otherwise, the transmission runs in a timeout. Figure 1: Detection algorithm FEIG ELECTRONIC GmbH Page 7 of 9 N10710-e-ID-B.doc

8 FECOM and FEISC // NOTE: this sample is without error handling. In real applications, the error handling for every // FECOM and FEISC function call must be added!! int back = 0; int iporthandle = FECOM_OpenPort("1"); int ihandle = FEISC_New(iPortHandle); char ctimeout[8]; char coldbaud[8]; char coldframe[8]; char coldtimeout[8]; char cprtframe[10]; char* baud[] = "115200", "57600", "38400", "19200", "9600", "4800" ; char* frame[] = "8E1", "8N1", "8O1" ; if(iporthandle > 0 && ihandle > 0) // call detect function back = MyDetectCOM(iPortHnd, ihandle); // detect function for serial port int MyDetectCOM(int iporthnd, int ihandle) // save actual baudrate, frame, timeout FECOM_GetPortPara( iporthnd, "baud", coldbaud ); FECOM_GetPortPara( iporthnd, "frame", coldframe ); FECOM_GetPortPara( iporthnd, "timeout", coldtimeout ); // reduce timeout to 300ms FECOM_SetPortPara( iporthnd, "timeout", 300 ); // for some OBID s (ISC.MR/PR/PRH100, ISC.LR200, ISC.M02, CPR.M02, CPR.02, CPR.04) // we setup Standard Protocol Frame to give these Reasers a chance FEISC_SetPara(iHandle, "FrameSupport", "STANDARD"); for( int j=0; j<3; j++ ) // try all frames "8E1", "8N1", "8O1" // set the next frame FECOM_SetPortPara( iporthnd, "frame", frame[j]); for( int i=0; i<3; i++ ) // try all baudrates, beginning with "115200" // set the next baudrate FECOM_SetPortPara( iporthnd, "baud", baud[i]); // search for the connected // with busaddress 255 each is answering back = FEISC_0x52_GetBaud(iHandle, 255); if(back = 0) // detected, restore communication timeout FECOM_SetPortPara(iPortHandle, "Timeout", coldtimeout); return -1; // alternate protocol frame FEISC_GetPara(iHandle, "FrameSupport", cprtframe); if(strcmp(cprtframe, "STANDARD") == 0) FEISC_SetPara(iHandle, "FrameSupport", "ADVANCED"); else FEISC_SetPara(iHandle, "FrameSupport", "STANDARD"); // no detected, restore previous port settings FECOM_SetPortPara(iPortHandle, "baud", coldbaud); FECOM_SetPortPara(iPortHandle, "frame", coldframe); FECOM_SetPortPara(iPortHandle, "Timeout", coldtimeout); return 0; FEIG ELECTRONIC GmbH Page 8 of 9 N10710-e-ID-B.doc

9 Detecting at USB Detecting a at USB needs no protocol transmissions and it makes the setting of the protocol frame much easier. When a is detected by the kernel driver, the s name is requested and evaluated. If the name is found in a positive list (CPR.04, ISC.MR100, ISC.PRH100), the protocol frame is set to Standard, otherwise to Advanced. FEUSB and FEISC // NOTE: this sample is without error handling. In real applications, the error handling for every // FEUSB and FEISC function call must be added!! int back = 0; int ihandle = FEISC_New(0); char cporthandle[11]; char cdevicename[32]; if(ihandle > 0) // call detect function back = MyDetectUSB(iHandle); // detect function for USB int MyDetectUSB(int ihandle) int iporthandle = FEUSB_ScanAndOpen(0); // connect first found OBID if(iporthandle < 0) return -1; // no connected // set port handle in reader object sscanf(cporthandle, "%d", &iporthandle); FEISC_SetPara(iHandle, PortHnd, cporthandle); // request name to detect ISC.MR/PRH100-U or CPR.04-USB, // which supports only Standard Protocol Frame // all other USB-s supports Advanced Protocol Frame FEUSB_GetDevicePara(iPortHandle,, cdevicename); if(strcmp(cdevicename, ID CPR.04-USB") == 0) FEISC_SetPara(iHandle, "FrameSupport", "STANDARD"); else if(strcmp(cdevicename, ID ISC.MR100-U") == 0) FEISC_SetPara(iHandle, "FrameSupport", "STANDARD"); else if(strcmp(cdevicename, ID ISC.PRH100-U") == 0) FEISC_SetPara(iHandle, "FrameSupport", "STANDARD"); else FEISC_SetPara(iHandle, "FrameSupport", "ADVANCED"); // detected return 0; FEIG ELECTRONIC GmbH Page 9 of 9 N10710-e-ID-B.doc