User Manual HF5x Transponder Reader (Serial/SECSII)
ID060003 Rev 01-2006 Printed in Germany Subject to modifications © 2006 BROOKS Automation (Germany) GmbH RFID Division Gartenstrasse 19 D-95490 Mistelgau Germany Tel: +49 9279 991 910 Fax: +49 9279 991 900 E-mail: rfid.support@brooks.com 2 HF5x Transponder Reader (SECS1-Protocol), Release 1.
TABLE OF CONTENTS 1 INTRODUCTION 6 1.1 About this Device ..................................................................6 1.2 About this Manual .................................................................7 2 SAFETY INSTRUCTIONS 8 2.1 Symbols and Types Used in this Manual ................................9 2.2 General Safety Instructions .................................................. 10 2.3 ESD Instructions.................................................................. 11 2.4 Proper Use ....
.10.1 Required Operating Conditions......................................29 4.10.2 Parameter of Serial Interface .........................................29 4 5 OPERATION 30 5.1 Operating Personnel.............................................................30 5.2 Introduction .........................................................................30 5.3 SECS-1 Implementation.......................................................31 5.3.1 Character Structure..............................................
9 ACCESSORIES 122 9.1 Device Options .................................................................. 122 9.2 Antennas ........................................................................... 122 9.2.1 Available Types .......................................................... 122 9.2.2 Reading and Writing Ranges ....................................... 123 9.3 Cables ............................................................................... 132 9.4 Power Supply ....................................
1 I NTRODUCTION 1 INTRODUCTION 1.1 About this Device The BROOKS HF Transponder Reader system is a high-frequency identification system that uses FM transmission. The basic item is a transponder that works as a forgery-proof electronic identity disk. The reading unit of the system sends an energy impulse via the antenna. The capacitor of the passive, battery-free transponder is charged by this impulse. After that, the transponder returns a signal with the stored data.
I NTRODUCTION 1 1.2 About this Manual This manual contains information about installing, operating and error handling the BROOKS HF5x RS232 Transponder Reader. It consists of nine chapters: Introduction Safety Instructions Product Description Installation Operation Service and Error Handling Deinstallation and Storage Transportation and Disposal Accessories HF5x Transponder Reader (SECS1-Protocol), Release 1.
2 S AFETY I NSTRUCTIONS 2 SAFETY INSTRUCTIONS This product is manufactured in accordance with state of the art technology and corresponds to recognized safety regulations. Nevertheless, there are dangers associated with the use of the equipment even for its intended purpose. You should therefore read the following safety information carefully and keep it in mind. Only install and operate this equipment if it is in perfect condition and with reference to this manual.
S AFETY I NSTRUCTIONS 2 2.
2 S AFETY I NSTRUCTIONS 2.2 General Safety Instructions 1 Read and understand all safety and operating instructions before installing and operating the device. 2 This instruction is designed for specially trained personnel. This device is NOT intended for use by the “general population” in an uncontrolled environment. Installation, operation and error handling the device shall be carried out by specially trained personnel only (see additional information on pages 12, 23, 30, and 115).
S AFETY I NSTRUCTIONS 2 All antenna resonant circuit components carry high voltage! The installer is responsible for installing the device to comply with FCC requirements of human exposure to radio frequency. To prevent fire, shock hazard, or annoying interference, use recommended accessories only. Remove the housing lid carefully to prevent damage! Do not operate the device when the housing lid is removed! Do NOT operate this device without a proper antenna attached.
2 S AFETY I NSTRUCTIONS This product is designed to be mounted and operated in an industrial environment as a built-in-device only. It is not designed to be used as a stand-alone or a portable device or in a non-industrial environment, such as a household, vehicle or open-air environment. 2.5 Qualified Personnel This manual is designed for specially trained personnel only. This device must be installed and maintained by the manufacturer or its specially trained representatives.
S AFETY I NSTRUCTIONS 2 2.6 Declaration of Conformity 2.6.1 USA – Federal Communications Commission (FCC) This device complies with Part 15 of the FCC Rules. Operation is subject to the following two 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.
2 S AFETY I NSTRUCTIONS 2.6.
S AFETY I NSTRUCTIONS 2 Gesundheit und Sicherheit gemäß § 3 (1) 1. (Artikel 3 (1) a)) Health and safety requirements pursuant to § 3 (1) 1. (Article 3(1) a)) angewendete harmonisierte Normen Harmonized standards applied EN 60950 Einhaltung der grundlegenden Anforderungen auf andere Art und Weise (hierzu verwendete Standards/ Spezifikationen) Other means of proving conformity with the essential requirements (standards/specifications used) BMPT Decree No.
2 S AFETY I NSTRUCTIONS Einhaltung der grundlegenden Anforderungen auf andere Art und Weise (hierzu verwendete Standards / Schnittstellenbeschreibungen) Other means of proving conformity with the essential requirements (standards/interface specifications used) EN 300 330-1 (06/2001) BROOKS Automation (Germany) GmbH Gartenstr. 19 D-95490 Mistelgau Germany Phone +49 9279 991 910 Fax +49 9279 991 900 16 Mistelgau, 20.09.
P RODUCT D ESCRIPTION 3 3 PRODUCT DESCRIPTION 3.1 Indicating and Operating Elements Antenna plugs (antenna 1 – 5) Reader version without external I/O’s Status LED (red) Serial interface Reset button Power LED (green) Power connector HF5x Transponder Reader (SECS1-Protocol), Release 1.
3 P RODUCT D ESCRIPTION 3.2 Inside View Reset button LED’s (power and status) Power connector 24 VDC fuse controller C513A0 HF relais connector antenna 1 HF module RS232 18 JTAG port memory PSD934F2 conntector input module HF5x Transponder Reader (SECS1-Protocol), Release 1.
P RODUCT D ESCRIPTION 3 3.3 Description Power LED If the device is connected to a power supply, the LED is illuminated green and the reader is ready for use. Status LED The status LED is used to check reading or writing. If the reader is in test mode and the action was OK, the status LED is on. In case of an error occurs the status LED is off. The action depends on reader parameter 38.
3 P RODUCT D ESCRIPTION 3.4 Labeling Information Type Serial number FFFF 3.5 Technical Data 3.5.1 Transponder Reader Parameter Value Operation temperature Stock temperature Permissible humidity @ 50C° 20 0°C to +50°C 32°F to 122°F -25°C to +70°C -13°F to +158°F 25 - 80 % Transmitter frequency 13,56 MHz Max.
P RODUCT D ESCRIPTION 3 3.5.2 Power Supply and Current Input Description Min Type Voltage (proof against connecting to the wrong terminal) 12 Current without presence sensor 24 Max Unit 32 60 VDC mA (starting process excluded) 3.6 Contents of Delivery Number Description 1 HF RS232 Transponder Reader 1 Instruction manual For available or required accessories, e.g. antennas, adapters and cables, see section “Accessories” on page 122 in this manual. 3.
4 I NSTALLATION 4 INSTALLATION 4.1 Installation Environment This device is designed for use in an indoor industrial environment only. Installation is only permitted in an environmental indoor climate with a constant temperature of between 0°C and +50°C / 32°F and 122°F, humidity between 25% and 80%, and a maximum temperature of +50°C / 122°F. Do not install or use this device in or near water. Never spill liquids of any kind onto the device.
I NSTALLATION 4 When the device is installed, the installation location must be adequately illuminated. Do not install the device during periods of lightning. Ensure the installation location complies with FCC requirements for human exposure to radio frequency. When determining the assembly location, consider the length of the antenna cable that will be used, and the reading and writing range. See section „Accessories/Antennas“ for further information. 4.
4 I NSTALLATION 4.4.1 Dimensions for Planning Drawing without external I/O’s Space for plugs* 40 6.5 120 25 80 Space for plugs* 105 118 130 *Keep space free for plugs. Dimensions for straight cable plugs. 45 24 HF5x Transponder Reader (SECS1-Protocol), Release 1.
I NSTALLATION 4 Drawing with external I/O’s 4.5 Installing the Antenna When installing the antenna, consider the required reading and writing ranges (see section “Accessories”, page 122). The reader can be used properly only if the transponder is located within the individual reading/writing range of the antenna! 4.5.1 Positioning Reliable reading and writing depends on the range and position of the transponder to the antenna.
4 I NSTALLATION 4.5.3 Dimensions for Planning 4.5.3.1 Frame Antenna X y ∅ 7 ± 0.5 25 50 M5 30 7 26 22.5 16 15 ∅7 HF5x Transponder Reader (SECS1-Protocol), Release 1.
I NSTALLATION Part number x y ANT-1HF-150x190 150 190 ANT-1HF-190x150 190 150 ANT-1HF-180x190 180 190 ANT-1HF-140x180 140 180 4 4.6 Connecting the Transponder Reader 4.6.1 Antenna Connect the antenna to the antenna plug (see illustration page 18). 4.7 Power Connection Built-in male plug, plastic (power supply) PIN 1 2 3 Signal +24V 0V Screen / PE 1 2 3 The device can be connected to an interior DC power circuit of the equipment or to a DC adapter (see section “Accessories”, page 133).
4 I NSTALLATION 4.8 Terminal Connection Built-in female plug (RS232 interface) PIN 1 2 3 4 5 6 7 8 9 DB9 NC TxD RxD NC GND NC NC NC NC The serial interface is a Sub-D female plug (9 contacts); a serial connection line (switched 1:1) can be used. 4.9 External Input and Output (optional) There are two different versions available: 28 1. One input and one output per antenna head. 2. One input and two outputs per antenna head. HF5x Transponder Reader (SECS1-Protocol), Release 1.
I NSTALLATION 4 4.10 Starting Up 4.10.1 Required Operating Conditions To operate the reader, the following requirements must be met: An antenna must be connected correctly to the reader. The power supply must be connected. The transponder must be located within the individual reading/writing range of the antenna. 4.10.2 Parameter of Serial Interface Baudrate 19200 Databits 8 Stopbit 1 Parity none HF5x Transponder Reader (SECS1-Protocol), Release 1.
5 O PERATION 5 OPERATION 5.1 Operating Personnel The HF5x Transponder Reader is designed to be operated by specially trained personnel only. If you have doubts about the qualification required, contact the manufacturer. Operating the device without special skills can result in damage to the reader and/or connected devices! 5.2 Introduction The SECS-1 standard defines a communication interface that is suitable for exchanging messages between semiconductor processing equipment and a host.
O PERATION 5 5.3 SECS-1 Implementation This message set describes the communication between a SECS-1 reader and a host. The host and the transponder reader communicate via an RS232 interface (SECS-1). 5.3.1 Character Structure Data will be transmitted or received in a serial bit stream of 10 bits per character at one of the specified data rates. The standard character has one start bit (0), 8 data bits and one stop bit (1). All bit transmissions are of the same duration.
5 O PERATION 5.3.2.
O PERATION Upper Device ID R-Bit Lower Device ID 0 0 0 0 0 0 5 1 serial number of the reader Direction reader to host: 0x81xx * Direction Host to equipment (BROOKS HF5x reader): 0x01xx * * … the serial number is located on a label on the housing lid of each reader The W-Bit indicates that the sender of a primary message expects a reply. A value of one in the W-bit means that a reply is expected. The message ID identifies the format and content of the message being sent.
5 O PERATION When the host wants to send, it first sends an and then tries to read. If it receives an , it sends its message and then expects an . ( HOST / READER) (READER / HOST) Source: Receiver: ENQ T2 EOT T2 Length T1 Header Data Checksum T2 ACK T4 (multi-block) ENQ If it receives an , it puts off sending its message, sends an and then reads the other message.
O PERATION 5 5.4 SECS-2 Implementation 5.4.1 Introduction The SEMI Equipment Communication Standard Part 2 (SECS-2) defines details how messages exchanged between intelligent equipment and a host are interpreted. It is the intent of this standard to be fully compatible with SEMI Equipment Communication Standard E4 (SECS-1). The messages defined in this specification support the typical activities required for the BROOKS transponder reader.
5 O PERATION A list is an ordered set of elements, where an element can be either an item or a list. The list header has the same form as an item header with format type 0. However, the length byte refers to the number of elements in the list rather than to the number of bytes. 5.4.
O PERATION 5 Data item examples: Meaning Format Length 65 01 xx 71 04 MSB ... 41 06 1.chr 2.chr zero-length xx 00 List Data Item 01 03 1- Byte Integer 4- Byte Integer ASCII 1. element ... LSB 3.chr 4.chr 5.chr 6.chr 2. element 3. element 5.4.3 Message set The SECSII-message-set used by the BROOKS HF5x transponder reader consist of six different stream types.
5 O PERATION According to SEMI E99 carrier ID read/writer functional standard for SECS-1 and SECS-2 protocol, the BROOKS reader supports the defined stream 18 messages.
O PERATION 5 Data Item Dictionary This section defines the data items used in the standard SECS-2 messages described in the section “Message Details”. Syntax: Name: A unique name for this data item. This name is used in the message definitions. Format: The permitted item format code which can be used for this standard data item. Item format codes are shown in hex and octal, as described in section data items (page 36). The notification “3()” indicates any of the signed integer formats (30, 31, 32, 34).
5 O PERATION Format: A[max25] ATTRID Description: Identifier for an attribute for a specific type of object.
O PERATION “ECID_22” parameter 22 – sensor 2 delay “ECID_23” parameter 23 – sensor 3 delay “ECID_24” parameter 24 – sensor 4 delay “ECID_25” parameter 25 – sensor 5 delay “ECID_26” parameter 26 – watchport for sensor 1 “ECID_27” parameter 27 – watchport for sensor 2 “ECID_28” parameter 28 – watchport for sensor 3 “ECID_29” parameter 29 – watchport for sensor 4 “ECID_30” parameter 30 – watchport for sensor 5 “ECID_31” parameter 31 – r/w max repeat “ECID_32” parameter 32 – type of transpo
5 O PERATION Format: A[max4] ATTRVAL Description: Value of the specified attribute.
O PERATION 5 Format: A[max2] CPVAL Description: “OP” “MT” State request value … … Where used: operating state maintenance state S18F13 Format: A DATA Description: A vector or string of unformatted data. It depends on the size of the MID area. Where used: S18F6, S18F7, S18F68, S18F69 DATALENGTH Description: Format: U2 Total bytes to be sent. The DATALENGTH corresponds to the quantity of bytes that should be read or written.
5 O PERATION Format: B[1] EAC Acknowledge code for new reader constant 0 … Parameter was set successfully 1 … Parameter could not be set Where used: S2F16 Format: U1 ECID Parameter number of reader (see data item ECV) Where used: S2F13, S2F15 Format: U1 ECV Reader parameter definition. The values are displayed as decimal values! Where used: S2F14, S2F15 Parameters : Parameter 0: Gateway ID The gateway ID is a part of the device ID.
O PERATION 5 Parameter 1: Baudrate Data transmission rate to the SECS-Host 3: 300 Baud 6: 600 Baud 12: 1200 Baud 24: 2400 Baud 48: 4800 Baud 96: 9600 Baud 192: 19200 Baud 200: 38400 Baud 201: 57600 Baud 202: 115200 Baud Default :(192) 19200 Baud (see accompanying letter of the reader) Parameter 2: Inter-Character-Timeout T1 1 .. 100 1/10s Default: (10) 1s Parameter 3 : Block-Protocol-Timeout T2 2 .. 250 1/10s Default: (20) 2s Parameter 4: Reply-Timeout T3 1 ..
5 O PERATION Parameter 6: Retry limit RTY Number how often a question or a message shall be repeated. 0 .. 31 Default: 3 Parameter 7: TARGETID HighByte Highbyte of the predefined TARGETID (not changeable). Parameter 8: TARGETID LowByte Lowbyte of the predefined TARGETID (not changeable). Parameter 9: Heartbeattime The reader offers the option of generating a regular heartbeat. This means the reader sends a S1F1 message to the host in the defined interval.
O PERATION 5 Parameter 20: sensor activity The transponder reader offers the option of deactivating the connected sensors. 0x00000000 all 5 Sensors deactivated 0x00000001 Sensor 1 activated 0x00011111 all 5 Sensors activated Default: 0x00011111 (31) Parameter 21: sensor delay for presence sensor 1 Delay time for sensor signal to start a defined action. 0 .. 255 1/10 s Default: (10) 1s Parameter 22: sensor delay for presence sensor 2 Delay time for sensor signal to start a defined action. 0 ..
5 O PERATION Parameter 26: watchport for presence sensor 1 Enables a message to the host if a cassette/FOUP is detected on the I/O port, or if it is removed from I/O port.
O PERATION 5 Parameter 27: watchport for presence sensor 2 See parameter 26. Parameter 28: watchport for presence sensor 3 See parameter 26. Parameter 29: watchport for presence sensor 4 See parameter 26. Parameter 30: watchport for presence sensor 5 See parameter 26. Parameter 31: r/w maxrepeat If a read/write error occurs, this parameter defines the maximum number of attempts to read or write a transponder. 0 .. 5 Default: 5 Parameter 32: type of transponder Defines the type of the transponder.
5 O PERATION Parameter 37: MID area This parameter defines the range of the MID. ‘0’ … ‘10’ pages Default: ‘4’ – MID area = 4 pages = 16 bytes (depends on transponder type). See also parameter 42 – 45 and 99. Parameter 38: Test After Soft Reset This parameter enables/disables the initial test after a software reset.
O PERATION 5 Parameter 42: CarrierIDOffset Defines the offset of the CID within the CID field (MID area – parameter 37). The valid value range depends on the value of the MID area and the value of CarrierIDLength. Valid range: 0 … maximum bytes of CID -1 Default: 0 Offset + Length can not be larger than the length of CID field. For software version RS2H23 and higher. Parameter 43: CarrierIDLength Defines the length of the CID within the CID field (MID area – parameter 37).
5 O PERATION Parameter 44: FixedMID Defines the read, write and error behavior regarding CarrierIDLength defined in SEMI E99-0303. 0 Dynamic CID length (to ensure compatibility with older versions) MID length is variable for writing to the tag. Reading up to the first non-visible ASCII character. 1 Fixed CID length (to meet the new standard revision) Length of MID in the tag must be the same as the reader settings. If there is a non-visible ASCII character within the CID field, an error occurs.
O PERATION 5 Examples: MID string is ‘123456789ABC’ Parameter 45 = ‘0’: tag memory: Page 3, 4 9 A B C Memory address 15 14 13 12 0x00 0x00 0x00 0x00 11 10 9 8 Page 1, 2 1 2 3 4 5 6 7 8 Memory address 7 6 5 4 3 2 1 0 4 Output string: ‘123456789ABC’ Parameter 45 = ‘1’ or ‘2’: tag memory: Page 3, 4 0 0 0 0 1 2 3 Memory address 15 14 13 12 11 10 9 8 Page 1, 2 5 6 7 8 9 A B C Memory address 7 6 5 4 3 2 1 0 Output string (parameter 45 = ‘1’): ‘
5 O PERATION Format: A[6] MDLN Equipment model number. Where used: S1F2 Format: B[10] MHEAD SECS message block header associated with message block in error. Where used: S9F1, S9F3, S9F5, S9F7 Format: A MID Description: Material ID Depending on the type of transponder, it is possible to modify the length of the MID. MID length can be set from “0” (no MID) to “10” (MID occupies the first 10 pages (writeable)) See parameter 37.
O PERATION 5 Format: B[1] ONLACK Acknowledge code for ON-LINE request. 0 … ON-LINE accepted (reader is online) Where used: S1F18 Format: A[2] OUTPUT Number of the output of the antenna head indicated by TARGETID. “01” … Output 1 “02” … Output 2 Where used: S18F77 Format: A[2] PM Information Description: Preventive maintenance information “NE” … Normal execution “MR” … Maintenance required Where used: STATUS Format: B[1] RAC Reset acknowledge code.
5 O PERATION Format: B[1] RIC Reset code. 1 … Power up reset 2 … Software reset Where used: S2F19 Format: B[10] SHEAD Stored SECS message block header. Only the last message is stored, which must still be confirmed by the host! Where used: S9F9 Format: A[max 6] SOFTREV Software revision code. Where used: S1F2 Format: A[2] SSACK Description: “NO” Result information on the status of the request concerning the service request.
O PERATION “CE” … 5 Communication error Syntax error of message or message format or value. “HE” … Hardware error ID reader/writer head fault, ID reader/writer head is powered off. “TE” … Tag error Where used: S18F2, S18F4, S18F6, S18F8, S18F10, S18F12, S18F14, S18F66, S18F68, S18F70, S18F72, S18F74, S18F76, S18F78, S18F80 Format: A[max18] SSCMD Description: Indicates an action to be performed by the subsystem. Used to differentiate between the different subsystem commands indicated.
5 O PERATION Format: A[max 5] STATE Description: State of the external outputs of a specific head. “ON” … Output is ON “OFF” … Output is OFF “FLASH” … Output is flashing “KEEP” … Output remains current state Where used: S18F77 Format: A[2] STATUS Description: Provides status information of a subsystem component. Consists of PM Information and the current values of the CIDRW attributes AlarmStatus, OperationalStatus, and HeadStatus.
O PERATION Format: A[max10] TARGETID Description: 5 Identifies where a request for action or data is to be applied. The TARGETID corresponds to the last four characters of the serial number on a label on top of the reader. The reader uses the 2 digit HeadID as TARGETID to address the right antenna connector. See also reader parameter definitions (data item ECV) parameter 7 and 8.
5 O PERATION 5.5 SEMI E99 5.5.1 Introduction The purpose of the Carrier ID Reader/Writer functional standard is to provide a common specification for concepts, behavior, and services provided by a Carrier ID Reader/Writer to an upstream controller. A standard interface will increase the interchangeability of a Carrier ID Reader/Writer, so that users and equipment suppliers have a wide range of choice. Scope: 1.
O PERATION 5 1 INITIALIZING RUNNING 2 3 OPERATING 8 4 IDLE BUSY 5 NO ALARMS 9 6 7 10 ALARMS MAINTENANCE OPERATIONAL STATUS ALARM STATUS The table below defines the states of the BROOKS transponder reader. State ALARM STATUS Definition Displays the presence or absence of alarms. ALARMS An alarm condition exists. BUSY A service is being performed that affects the state of the hardware CIDRW Super-state of CIDRW state model. Always active when the CIDRW is powered on.
5 O PERATION The table below defines the transitions of the BROOKS SECS-1 state model of the transponder reader. # 62 Previous State 1 Any 2 INITIALIZING 3 INITIALIZING 4 IDLE 5 BUSY Trigger Power up or reset Initialization is complete Default entry into OPERATING A service request to read or write or perform diagnostic is received.
O PERATION 5 5.5.3 Valid Services per State The following table shows which of the various services can be performed by the reader when the reader is in various individual states. X X X Change State X Get Attributes Read ID X Get Status Reset X Perform Diag.
5 O PERATION 5.6 Message Details 5.6.1 Equipment status S1F0: ABORT TRANSACTION (reader <-> host) Used instead of an expected reply to abort a transaction. Function 0 is defined in every stream and has the same meaning in every stream. S1F0 W . * Header Only S1F1: ARE YOU THERE REQUEST (reader <-> host, reply) Establishes if the gateway or host is online. S1F1 W . * Header Only S1F2: ON-LINE DATA (host -> reader) The host signifies that it is online. S1F2 >.
O PERATION 5 S1F15: REQUEST OFF_LINE (host ->reader, reply) The reader is requested to change the communication state to offline. The reader can only be set online again by using message S1F17 (or reset S2F19), all other messages will be aborted by the SxF0 message! S1F15 W. *Header Only S1F16: OFFLINE ACKNOWLEDGE (reader -> host) Acknowledge. S1F16 . S1F17: REQUEST ON_LINE (host ->reader, reply) The reader is requested to change the communication state to online. S1F17 W.
5 O PERATION 5.6.2 Equipment Control S2F0: ABORT TRANSACTION (reader <-> host) Used instead of an expected reply to abort a transaction. Function 0 is defined in every stream and has the same meaning in every stream. S2F0 W . * Header Only S2F13: EQUIPMENT CONSTANT REQUEST (host-> reader, reply) The host requests one constant from the reader. S2F13 W >. S2F14: EQUIPMENT CONSTANT DATA (reader -> host) The reader sends the requested constant to the host. S2F14 >.
O PERATION 5 S2F16: NEW EQUIPMENT CONSTANT ACKNOWLEDGE (reader -> host) The reader acknowledges the setting of the reader constant. S2F16 < EAC>. S2F19: RESET SEND (host -> reader, reply) The host requests the reader to reset the hardware and software. If a heartbeat time is set (parameter 9) the reader sends a S1F1 message when the reset was finished. The power up reset requires a few seconds. S2F19 W < RIC>.
5 O PERATION 5.6.3 System Errors S9F1: UNRECOGNIZED DEVICE ID (reader -> host) The device ID in the message block header does not correspond to the equipment device ID. S9F1 < MHEAD > . S9F3: UNRECOGNIZED STREAM TYPE (reader -> host) The reader does not recognize the stream type in the message block header. S9F3 < MHEAD > . S9F5: UNRECOGNIZED FUNCTION TYPE (reader -> host) The reader does not recognize the function number in the message block header. S9F5 < MHEAD > .
O PERATION 5 5.6.4 Subsystem Control and Data S18F0: ABORT TRANSACTION (reader <-> host) Used instead of an expected reply to abort a transaction. Function 0 is defined in every stream and has the same meaning in every stream. S18F0 W . * Header Only S18F1: READ ATTRIBUTE REQUEST (RAR) (host -> reader, reply) This message requests the current values of specific attributes of the subsystem component indicated in TARGETID. S18F1 W L,2 1. 2. L,n 1. … n.
5 O PERATION S18F3: WRITE ATTRIBUTE REQUEST (WAR) (host -> reader, reply) This message requests the subsystem to set the value of read/write attributes of the component specified in TARGETID. S18F3 ,W L,2 1. 2. L,n 1. L,2 1. 2. … n. L,2 1. 2. S18F4: WRITE ATTRIBUTE ACKNOWLEDGE (WAA) (reader -> host) This message acknowledges the success or reports failure of the request to write attribute data to the subsystem indicated in TARGETID. S18F4 L,3 1.
O PERATION 5 S18F5: READ REQUEST (RR) (host -> reader, reply) The host requests the subsystem indicated in TARGETID to read information. DATASEG may be used to indicate a specific section of data to be read. DATALENGTH is used to limit the amount of data for that section. S18F5 W L,3 1. 2. 3. If DATASEG and DATALENGTH are both omitted (zero length items) then up to 120 bytes of the data area are requested.
5 O PERATION S18F7: WRITE DATA REQUEST (WAR) (host -> reader, reply) This message requests to write data to the subsystem component indicated in TARGETID. DATASEG may be used to indicate a specific section of the data area to be written or overwritten. S18F7 W L,4 1. 2. 3. If DATASEG and DATALENGTH are both omitted (zero length items), then up to 120 bytes in the data area are to be overwritten.
O PERATION 5 S18F9: READ ID REQUEST (RIR) (host -> reader, reply) This message is used to request the subsystem indicated by TARGETID to read the MID. S18F9,W S18F10: READ ID DATA (RID) (reader -> host) This message returns a requested material identifier MID as read by the subsystem indicated in TARGETID. S18F10 L,4 1. 2. 3. 4. L,1 L,s 1. … s. The reader can be in operational or maintenance mode to read the MID with message S18F9.
5 O PERATION S18F11: WRITE ID REQUEST (WIR) (host -> reader, reply) This message is used to request the subsystem indicated by TARGETID to write the MID. S18F11 W L,2 1. 2. Pay attention: The reader must be in maintenance mode to write the MID with message S18F11. S18F12: WRITE ID ACKNOWLEDGE (WIA) (reader -> host) This message acknowledges the success or failure of writing the MID to the subsystem indicated in TARGETID. S18F12 L,3 1. 2. 3. L,1 L,s 1. … s.
O PERATION 5 S18F13: SUBSYSTEM COMMAND REQUEST (SCR) (host -> reader, reply) This message is used to request the subsystem indicated in TARGETID to perform a specific action. S18F13 W L,3 1. 2. 3. L,n 1. … n. S18F14: SUBSYSTEM COMMAND ACKNOWLEDGE (SCA) (reader -> host) This message reports the result from the subsystem specified in TARGETID for the requested action. S18F14 L,3 1. 2. 3. L,1 L,s 1. … s.
5 O PERATION S18F65: SCAN TRANSPONDER REQUEST (STR) (host -> reader, reply) This message is used to request the subsystem indicated in TARGETID to perform a scan. S18F65 W S18F66: SCAN TRANSPONDER ACKNOWLEDGE (STA) (reader -> host) This message reports the result from the subsystem specified in TARGETID for the requested action. S18F66 L,3 1. 2. 3. L,s 1. … s. If the TARGETID is unknown, a communication error (CE) occurs.
O PERATION 5 S18F67: READ REQUEST UID (RRU) (host -> reader, reply) The host requests the subsystem indicated in TARGETID to read information from the transponder indicated in UID. DATASEG may be used to indicate a specific section of data to be read. DATALENGTH is used to limit the amount of data for that section. S18F67 W L,4 1. 2. 3. 4. If DATASEG and DATALENGTH are both omitted (zero length items) then up to 120 bytes of the data area are requested.
5 O PERATION S18F69: WRITE DATA REQUEST UID (WARU) (host -> reader, reply) This message requests to write data to the subsystem component indicated in TARGETID to the transponder indicated in UID. DATASEG may be used to indicate a specific section of the data area to be written or overwritten. S18F69 W L,4 1. 2. 3. 4. 5. If DATASEG and DATALENGTH are both omitted (zero length items), then up to 120 bytes in the data area are to be overwritten.
O PERATION 5 S18F71: SENSOR STATE (SS) (reader -> host) This message reports the change of the state of one of the 5 presence sensors of the reader. The TARGETID corresponds to the number of the sensor. There are two states of the sensor. ON – the sensor is covered, OFF – the sensor is uncovered in case of the sensor polarity is not inverted. S18F71 L,2 1. 2. S18F72 SENSOR STATE ACKNOWLEDGE (SSA) (host -> reader) The host has to acknowledge all incoming S18F71 messages.
5 O PERATION S18F73 READ ID REQUEST UID (RIRU) (host -> reader) This message is used to request the antenna head indicated by TARGETID to read the MID of the tag indicated by UID. S18F73,W L,2 1. 2. S18F74 READ ID DATA (RID) (reader -> host) This message returns a requested material identifier MID of the tag indicated by UID which was read by the antenna head indicated in TARGETID. S18F74 L,4 1. 2. 3. 4. L,1 L,s 1. … s.
O PERATION 5 S18F75 WRITE ID REQUEST UID (WIDU) (host -> reader) This message is used to request the antenna head indicated by TARGETID to write the MID to the tag indicated by UID. S18F75 W L,3 1. 2. 3. Pay attention: The reader must be in maintenance mode to write the MID with message S18F75. S18F76 WRITE ID ACKNOWLEDGE (WIA) (reader -> host) This message acknowledges the success or failure of writing the MID to the antenna head indicated in TARGETID. S18F76 L,3 1. 2.
5 O PERATION S18F77 SET OUTPUT STATE (SOS) (host -> reader) This message sets the output states of the antenna head indicated in TARGETID. S18F77 L,2 1. 2. L,2 L,2 1.
O PERATION 5 S18F79 GET OUTPUT STATE (GOS) (reader -> host) This message requests the output states of the antenna head indicated by TARGETID. S18F79 S18F80 OUTPUT STATE (GOSA) (reader -> host) This message provides the output states of the antenna head indicated by TARGETID. S18F80 L,4 1. 2. 3. L,2 4. L,1 L,s 1. … s. HF5x Transponder Reader (SECS1-Protocol), Release 1.
5 O PERATION 5.
O PERATION 5 S1F1 Message from the host to the reader Host to Reader: S1F1 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 0A ) Out: Header ( 00 00 81 01 80 01 00 00 00 02 ) Out: Checksum ( 05 02 ) In: ACK ( 06 ) Reader to Host: S1F2 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 1C ) In: Header ( 80 00 01 02 80 01 00 00 00 02 ) In: Data 01 02 41 06 52 44 31 2E 30 20 41 06 52 53 32 48 32 37 In: Checksum ( 04 64 ) Out: ACK ( 06 ) HF5x Transponder Reader (SECS1-Protocol), Releas
5 O PERATION Message S1F15 sets the reader offline Host to Reader: S1F15 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 0A ) Out: Header ( 00 00 81 0F 80 01 00 00 00 03 ) Out: Checksum ( 14 02 ) In: ACK ( 06 ) Reader to Host: S1F16 86 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 0D ) In: Header ( 80 00 01 10 80 01 00 00 00 03 ) In: Data In: Checksum ( 01 37 ) Out: ACK ( 06 ) 21 01 00 HF5x Transponder Reader (SECS1-Protocol), Release 1.
O PERATION 5 Message S1F17 sets the reader online Host to Reader: S1F17 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 0A ) Out: Header ( 00 00 81 11 80 01 00 00 00 04 ) Out: Checksum ( 17 02 ) In: ACK ( 06 ) Reader to Host: S1F18 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 0D ) In: Header ( 80 00 01 12 80 01 00 00 00 04 ) In: Data In: Checksum ( 01 3A ) Out: ACK ( 06 ) 21 01 00 HF5x Transponder Reader (SECS1-Protocol), Release 1.
5 O PERATION Request reader constant with message S2F13 Host to Reader (Gateway): S2F13 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 0F ) Out: Header ( 00 00 82 0D 80 01 00 00 00 05 ) Out: Data 01 01 Out: Checksum ( BE 02 ) In: ACK ( 06 ) A5 01 01 ) Parameter 1 Reader to Host: S2F14 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 0F ) In: Header ( 80 00 02 0E 80 01 00 00 00 05 ) In: Data 01 01 A5 01 C0 In: Checksum ( 02 7E ) Out: ACK ( 06 ) Value 192 The host requests th
O PERATION 5 New Reader constant send with S2F15 Host to Reader: S2F15 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 14 ) Out: Header ( 00 00 82 0F 80 01 00 00 00 06 ) Out: Data 01 01 01 02 A5 01 14 Parameter 20 A5 01 05 Value 5 Out: Checksum ( 82 02 ) In: ACK ( 06 ) Reader to Host: S2F16 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 0D ) In: Header ( 80 00 02 10 80 01 00 00 00 06 ) In: Data In: Checksum ( 01 3B ) Out: ACK ( 06 ) 21 01 00 EAC 0 The Host sets the rea
5 O PERATION Host requests a software reset with S2F19 Host to Reader: S2F19 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 0D ) Out: Header ( 00 00 82 13 80 01 00 00 00 09 ) Out: Data Out: Checksum ( 43 02 ) In: ACK ( 06 ) 21 01 02 Software reset Reader to Host: S2F20 90 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 0D ) In: Header ( 80 00 02 14 80 01 00 00 00 09 ) In: Data In: Checksum ( 01 42 ) 21 01 00 RAC HF5x Transponder Reader (SECS1-Protocol), Release 1.
O PERATION 5 The reader detects an unrecognized device ID and sends the message S9F1.
5 O PERATION The reader detects a wrong stream number and sends the S9F3 message Host to Reader: S4F1 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 0A ) Out: Header ( 00 00 84 01 80 01 00 00 00 0B ) Out: Checksum ( 11 02 ) In: ACK ( 06 ) Reader to Host: S9F3 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 16 ) In: Header ( 80 00 09 03 80 01 00 01 00 04 ) In: Data 21 0A 00 00 84 01 80 01 00 00 00 0B In: The wrong message header Checksum ( 02 4E ) Out: ACK ( 06 ) The stream “4”
O PERATION 5 The reader detects an unrecognized function and sends the message S9F5.
5 O PERATION The reader detects wrong data and sends the S9F7 message Host to Reader: S2F13 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 0F ) Out: Header ( 00 00 82 0D 80 01 00 00 00 0D ) Out: Data ( 01 01 A5 01 0F ) Out: Checksum ( D4 02 ) In: ACK ( 06 ) Reader to Host: S2F14 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 0E ) In: Header ( 80 00 02 0E 80 01 00 00 00 0D ) In: Data ( 01 01 A5 00 ) In: Checksum ( 01 C5 ) Out: ACK ( 06 ) Reader to Host: S9F7: In: ENQ ( 05 )
O PERATION 5 The secondary message fails and the reader sends the S9F9 message Reader to Host: S1F1 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 0A ) In: Header 80 00 81 01 80 01 00 01 00 25 In: Checksum ( 01 A9 ) Out: ACK ( 06 ) Host to Reader: S9F9 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 16 ) In: Header 80 00 09 09 80 01 00 01 00 26 In: Data 21 0A 80 00 81 01 80 01 00 01 00 23 In: The stored header Checksum ( 03 0C ) Out: ACK ( 06 ) After sending the S1F1 message,
5 O PERATION Host requests reader attributes with S18F1 Host to Reader: S18F1 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 32 ) Out: Header ( 00 00 92 01 80 01 00 00 00 13 ) Out: Data 01 02 41 02 30 31 TARGETID “01” 01 02 41 07 45 43 49 44 5F 33 37 ECID_37 41 15 53 6F 66 74 77 61 72 65 52 65 76 69 73 69 6F 6E 4C 65 76 65 6C SoftwareRevision Level Out: Checksum ( DF 02 ) In: ACK ( 06 ) Reader to Host: S18F2 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 39 ) In: Header ( 80 00 12 02 80 01
O PERATION In: Data ( 4C 45 ) In: Checksum ( 09 3F ) Out: 5 ACK ( 06 ) The host requests all fundamental CIDRW attributes defined in ATTRID. The reader answers with the current attribute values.
5 O PERATION 41 02 4E 45 PMInformation “NE” 41 01 30 Alarmstatus “0” 41 04 49 44 4C 45 OperationalStatus “ IDLE ” 41 04 49 44 4C 45 HeadStatus “IDLE” In: Checksum ( 06 BF ) Out: ACK ( 06 ) The host writes all fundamental CIDRW attributes defined in ATTRID. The reader answers with the current attribute values.
O PERATION 5 The reader shows the success of the operation with SSACK “NO” (normal operation) and with the read values.
5 O PERATION Host reads material ID of a multipage transponder with S18F9 Host to Reader: S18F9 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 0E ) Out: Header ( 00 00 92 09 80 01 00 00 00 17 ) TARGETID “01” Out: Data 41 02 30 31 Out: Checksum ( D7 02 ) In: ACK ( 06 ) Reader to Host: S18F10 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 3D ) In: Header ( 80 00 12 0A 80 01 00 00 00 17 ) In: Data 01 04 41 02 30 31 TARGETID “01” 41 02 4E 4F SSACK “NO” 41 10 4D 49 44 20 30 30 30 30 30 30 30
O PERATION 5 Host writes material ID of a multipage transponder with S18F11 Host to Reader: S18F11 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 22 ) Out: Header ( 00 00 92 0B 80 01 00 00 00 18 ) Out: Data 01 02 TARGETID “01” 41 02 30 31 41 10 4D 49 44 20 31 31 31 31 31 31 31 31 31 31 31 31 MID “MID 111111111111” Out: Checksum ( 74 02 ) In: ACK ( 06 ) Reader to Host: S18F12 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 2B ) In: Header ( 80 00 12 0C 80 01 00 00 00 18 ) In: Data 01 03 41
5 O PERATION Host changes the reader state from IDLE to MANT with S18F13 Host to Reader: S18F13 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 23 ) Out: Header ( 00 00 92 0D 80 01 00 00 00 22 ) Out: Data 01 03 41 02 30 31 TARGETID “01” 41 0B 43 68 61 6E 67 65 53 74 61 74 65 SSCMD “ChangeState” 01 01 41 02 4D 54 ) Out: Checksum ( 62 02 ) In: ACK ( 06 ) CPVAL “MT” Reader to Host: S18F14 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 2B ) In: Header ( 80 00 12 0E 80 01 00 00 00 22 )
O PERATION 5 In the MAINTENANCE state, the reader could not read (S18F5) or write (S18F7) any DATA in the defined DATASEG. (5.5.3 Valid Services per State).
5 O PERATION Reset is an optional service used to reinitialize the reader. If reader parameter 9 is unequal to 0x00, the reset causes a S1F1 “Are you there” message from the reader.
O PERATION 5 The reader detects no tag Host to Reader: S18F5 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 18 ) Out: Header ( 00 00 92 05 80 01 00 00 00 18 ) Out: Data 01 03 41 02 30 31 TARGETID “01” 41 02 30 30 DATASEG “00” A9 02 00 08 DATALENGTH 0x08 Out: Checksum ( 2D 02 ) In: ACK ( 06 ) Reader to Host: S18F6 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 16 ) In: Header ( 80 00 12 06 80 01 00 00 00 18 ) In: Data 01 03 41 02 30 31 TARGETID “01” 41 02 54 45 SSACK “TE
5 O PERATION The reader scans for transponders in the surrounding of the antenna.
O PERATION 5 The reader reads 8 bytes from a specific tag specified by the data item UID.
5 O PERATION The reader writes 8 bytes to a specific tag specified by the data item UID.
O PERATION 5 The sensor of head 01 is occupied. The reader reports this event with a S18F71 message to the host.
5 O PERATION The sensor of head 01 was released. The reader reports this event with a S18F71 message to the host.
O PERATION 5 The reader reads the MID of the tag specified by the data item UID.
5 O PERATION The reader writes the MID to the tag specified by the data item UID.
O PERATION 5 The host sets the outputs of head 01.
5 O PERATION Out: ACK ( 06 ) The host requests the state of the outputs of head 01.
S ERVICE 6 AND E RROR H ANDLING 6 SERVICE AND ERROR HANDLING 6.1 General The transponder reader and its components must be serviced by the manufacturer only. If errors occur, follow the instructions in this section. Do not carry out any error eliminating measures other than the ones described in this section. If you are uncertain about errors and their handling, contact the manufacturer (see the contact information on page 119 of this manual).
6 S ERVICE AND E RROR H ANDLING 6.3 Safety Instructions All antenna resonant circuit components carry high voltages! When replacement parts are required, use replacement parts specified by the manufacturer only. Unauthorized substitutions may result in fire, electric shock, or other hazards. Static electricity can harm electronic components inside the device. ESD protection measures must be observed when opening the device (see page 11).
S ERVICE AND E RROR H ANDLING 6 Open the device: 1. Loose the 4 screws on the housing 2. Remove the upper part of the housing 6.5 Reader Does Not Respond or Transmit or Cannot be Controlled by the Host 1 Check if the interface connection cable is undamaged and correctly connected to both reader and host. 2 Check the status as indicated by the LEDs (see page 116). 3 Contact BROOKS for the firmware file and the Firmware Update Software to update the firmware of the reader.
6 S ERVICE AND E RROR H ANDLING 6.7 Power Cut After a power cut, the reader carries out a reset with self-test. While the self-test is running, the status LED is ON. If the test was successful, all LEDs, except for the power LED, are extinguished. 6.8 Software Releases 118 Release Date 11/27/2000 04/2003 Version RS2V10 RS2V20 04/2003 RS2V21 05/2003 RS2V22 06/2003 RS2V23 09/2003 RS2H24 10/2003 RS2H25 16.10.03 RS2H26 31.10.03 RS2H27 Description First version.
S ERVICE Release Date Version 18.11.03 RS2H28 AND E RROR H ANDLING 6 Description Parameter 26 – 30: Bit 6: Enables/disables reply expected of message S18F71 6.9 Customer Service BROOKS Automation (Germany) GmbH RFID Division Gartenstraße 19 D-95490 Mistelgau Germany Tel: +49 9279 991 910 Fax: +49 9279 991 900 E-mail: rfid.support@brooks.com 24 hour technical support hotline (Brooks): +1 978 262 2900 HF5x Transponder Reader (SECS1-Protocol), Release 1.
7 D EINSTALLATION AND S TORAGE 7 DEINSTALLATION AND STORAGE 7.1 Deinstallation 1 Disconnect the power supply. 2 Disconnect all cables. 3 Loosen and remove the mounting screws. 4 Remove the reader from its installation surface. 7.2 Storage Store the reader and its components in a clean and dry environment with the power supply disconnected. Make sure the contacts remain clean. Observe the necessary storage conditions (for technical data, see page 20).
T RANSPORTATION 8 AND D ISPOSAL 8 TRANSPORTATION AND DISPOSAL 8.1 Transportation For transportation purposes such as mailing, use a firm cardboard box. Use adequate padding material to protect the device on all sides. 8.2 Disposal The transponder reader and its components consist of different materials. Dispose of these materials separately in accordance with the relevant legislation in your country. Do not throw them away with everyday household trash.
9 A CCESSORIES 9 ACCESSORIES 9.1 Device Options Type Part-No. Transponder Reader without external IO’s THG-S1-1O00-F5-0000 Transponder Reader with one external input THG-S1-1O00-F5-00E0 Transponder Reader with one external input (floating) and 2 external outputs THG-S1-1O00-F5-00E2 9.2 Antennas (Special antenna types are available on request) 9.2.1 Available Types Type 122 Part-No.
A CCESSORIES 9 9.2.2 Reading and Writing Ranges The displayed reading and writing ranges are measured under optimal conditions. In the field the ranges can be reduced by the environment. Case 1: The transponder card is vertical in the reference plane. upper reference plane 190 center reference plane transponder card 180 Case 2: The transponder card is horizontal in the reference plane.
9 A CCESSORIES 9.2.2.1 Reading Range Antenna: ANT-1HF-180x190 Case 1: The following diagram shows the reading range of the transponder card in the center reference plane. This is the recommended position for an optimal reading range for this transponder card orientation. 124 HF5x Transponder Reader (SECS1-Protocol), Release 1.
A CCESSORIES 9 Case 1: The diagram below shows the reading range depending on the transponder position. 1 in upper reference plane 2 60 mm above center reference plane 3 in center reference plane 1 23 HF5x Transponder Reader (SECS1-Protocol), Release 1.
9 A CCESSORIES Case 2: The following diagram shows the reading range of the transponder card in the upper reference plane. This is the recommended position for an optimal reading range for this transponder card orientation. 126 HF5x Transponder Reader (SECS1-Protocol), Release 1.
A CCESSORIES 9 Case 2: The diagram below shows the reading range depending on the transponder position. 1 20 mm above reference plane 2 40 mm above reference plane 3 60 mm above reference plane 4 80 mm above reference plane 5 in upper reference plane 6 30 mm above upper reference plane 1 2 HF5x Transponder Reader (SECS1-Protocol), Release 1.
9 A CCESSORIES 9.2.2.2 Writing Range Antenna: ANT-1HF-180x190 Case 1: The following diagram shows the writing range of the transponder card in the center reference plane. This is the recommended position for an optimal writing range for this transponder card orientation. 128 HF5x Transponder Reader (SECS1-Protocol), Release 1.
A CCESSORIES 9 Case 1: The diagram below shows the writing range depending on the transponder position. 1 in upper reference plane 2 60 mm above center reference plane 3 in center reference plane 123 HF5x Transponder Reader (SECS1-Protocol), Release 1.
9 A CCESSORIES Case 2: The following diagram shows the writing range of the transponder card in the upper reference plane. This is the recommended position for an optimal writing range for this transponder card orientation. 130 HF5x Transponder Reader (SECS1-Protocol), Release 1.
A CCESSORIES 9 Case 2: The diagram below shows the writing range depending on the transponder position. 1 20 mm above center reference plane 2 40 mm above center reference plane 3 60 mm above center reference plane 4 80 mm above center reference plane 5 in upper reference plane 6 30 mm above upper reference plane 1 2 HF5x Transponder Reader (SECS1-Protocol), Release 1.
9 A CCESSORIES 9.3 Cables Type 132 Part-No. Picture HF antenna cable 1.0 m with LEMO plug (size 00) AEX-HF10 n/a HF antenna cable 1.5 m with LEMO plug (size 00) AEX-HF15 n/a HF antenna cable 2.0 m with LEMO plug (size 00) AEX-HF20 n/a HF antenna cable 3.0 m with LEMO plug (size 00) AEX-HF30 n/a HF antenna cable 3.6 m with LEMO plug (size 00) AEX-HF36 n/a HF antenna cable 4.0 m with LEMO plug (size 00) AEX-HF40 n/a HF5x Transponder Reader (SECS1-Protocol), Release 1.
A CCESSORIES 9 9.4 Power Supply Type Power Supply 24VDC EURO-Plug Part-No. Picture SVG 0,33 HF Power Supply 24VDC Adapters for different countries SVG0,6HF-UNI HF5x Transponder Reader (SECS1-Protocol), Release 1.
