User Manual HF80 Transponder Reader (Ethernet – HSMS)
ID090014 Rev 03-2009 Printed in Germany Subject to modifications © 2009 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 HF80 Transponder Reader – HSMS, 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 ....
.11.2 Parameter of Serial Interface .........................................28 4.11.3 Parameter of Ethernet Interface .....................................29 4 5 OPERATION 31 5.1 Operating Personnel.............................................................31 5.2 Introduction .........................................................................31 5.3 Modes..................................................................................32 5.4 SECS-1 Implementation.................................
7.2 Storage .............................................................................. 145 8 TRANSPORTATION AND DISPOSAL 146 8.1 Transportation ................................................................... 146 8.2 Disposal ............................................................................ 146 9 ACCESSORIES 147 9.1 Device Options .................................................................. 147 9.2 Antennas ........................................................................
1 I NTRODUCTION 1 INTRODUCTION 1.1 About this Device The BROOKS Transponder Reader System is a 13.56 MHz highfrequency 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 HF80 Transponder Reader RS232/Ethernet. It consists of nine chapters: Introduction Safety Instructions Product Description Installation Operation Service and Error Handling Deinstallation and Storage Transportation and Disposal Accessories HF80 Transponder Reader – HSMS, 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, 22, 31, and 141).
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 2.4 Proper Use This product was developed for reading and writing transponders only. Any other use of this device would constitute abuse and would render the user’s authority to install and operate the device invalid. 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.
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.
2 S AFETY I NSTRUCTIONS BROOKS Automation (Germany) GmbH Gartenstr. 19 D-95490 Mistelgau Germany Phone +49 9279 991 910 Fax +49 9279 991 900 16 Mistelgau, 01.08.2008 Gerald Dittrich (Place and date of issue) (Name and signature) HF80 Transponder Reader – HSMS, Release 1.
P RODUCT D ESCRIPTION 3 3 PRODUCT DESCRIPTION 3.1 Indicating and Operating Elements Antenna plugs (antenna 1 – 5) Reader option without external I/O’s Status LED (red) TCP/IP interface (PoE) RS232 interface (optional) DIP- switch Connector for power supply Power LED (green) HF80 Transponder Reader – HSMS, Release 1.
3 P RODUCT D ESCRIPTION 3.2 Description of Components 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 as feedback for reading and writing action in test mode and polling mode. If the reader is in test mode or polling mode and the read action was successful the red LED is on. In case of a reading error the LED is off.
P RODUCT D ESCRIPTION 3 3.3 Labeling Information Part number Serial number 3.4 Technical Data 3.4.1 Transponder Reader Parameter Value Operation temperature Stock temperature 0°C to +50°C 32°F to 122°F -25°C to +70°C -13°F to +158°F Permissible humidity @ 50C° 25 - 80 % Transmitter frequency 13.56 MHz Max.
3 P RODUCT D ESCRIPTION 3.4.2 Power Supply and Current Input Description Min Type Voltage (proof against connecting to the wrong terminal) 12 Current without presence sensor Max Unit 24 42 80 – 300 VDC mA (starting process excluded) Electrical Power: max. 7W ) Pay attention to the power consumption to ensure that your PoE infrastructure has a sufficient power supply. Take care that you connect only one type of power supply to the reader at the same time.
I NSTALLATION 4 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.
4 I NSTALLATION 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.
I NSTALLATION 4 4.4.1 Dimensions for Planning 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 HF80 Transponder Reader – HSMS, Release 1.
4 I NSTALLATION Drawing with external I/O’s 4.5 Installing the Antenna ) When installing the antenna, consider the required reading and writing ranges. 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. Optimal position of the transponder and antenna for different orientations of the transponder. 4.5.
I NSTALLATION 4 4.6 Connecting the Transponder Reader 4.6.1 Antenna Connect the antenna to the antenna plug (see illustration page 17). 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 147). Note the required voltage (see technical data, page 20).
4 I NSTALLATION 4.8 Terminal Connection Built-in female plug (RS232 interface) - optional 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: 26 1. One input per antenna head. 2. One input and two outputs per antenna head. HF80 Transponder Reader – HSMS, Release 1.
I NSTALLATION 4.10 4 DIP-Switches The DIP switches can be used to change the behavior of some features of the reader. Parameter 100 enables or disables the functionality of the DIP-switches.
4 I NSTALLATION 4.11 Starting Up 4.11.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 (except POE is used). ) The transponder must be located within the individual reading/writing range of the antenna. ) Setting of the DIP switches is correct. 4.11.
I NSTALLATION 4 4.11.3 Parameter of Ethernet Interface The connection to the Ethernet is realized by an independent Ethernet component. There are small tools available to configure the Ethernet component. Using a discovery tool all readers available in the network can be found. A double click on the IP address in the list opens a Webserver applet in a web browser window to configure the Ethernet component.
4 I NSTALLATION The link ‚Network’ opens the page to change the IP address. The button ‘Apply’ confirms the change and starts a reboot of the device. The TCP/IP port used by the HSMS protocol is set to 3241 by default. If you want to set another port please contact the manufacturer. 30 HF80 Transponder Reader – HSMS, Release 1.
O PERATION 5 5 OPERATION 5.1 Operating Personnel The HF80 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.
5 O PERATION 5.3 Modes The HF80 reader offers the possibility to work as SECS1 and HSMS reader. You can easily change between the two modes by switching one of the DIP- switches on the front panel of the reader. The second possibility to switch the modes is changing reader parameter 13. (communication port). SECS1 uses the serial interface to establish the direction of communication for passing message blocks. The SECS1 message set describes the communication between the reader and a host.
O PERATION 5 5.4 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 a RS232 interface (SECS-1). 5.4.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.4.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.5 HSMS Implementation HSMS defines the procedure for all messages exchanges between entities across the TCP/IP. The HSMS Connection State Diagram - The HSMS state machine is illustrated in the diagram below.
5 O PERATION # 1 2 3 4 5 6 Current State ... Not connected Trigger Local entity-specific preparation for TCP/IP communication A TCP/IP connection is established for HSMS communication. Breaking of TCP Connected connection. Not Selected Selected Not Selected Successful completion of HSMS Select procedure. Successful completion of HSMS Deselect or Separate.
O PERATION 5 5.5.1 HSMS Message Exchange Procedures HSMS defines the procedures for all message exchanges between entities across the TCP/IP connection established according to the procedures in the previous section. As explained in the overview, once the connection is established, the two entities establish HSMS communications with the Select procedure. The data messages may be exchanged in any direction at any time.
5 O PERATION Active Entity Passive Entity DISCONNECT Send Separate.req Receive Close connection Close connection LINKTEST Send Linktest.req Receive T6 Linktest.rsp Receive 40 Send HF80 Transponder Reader – HSMS, Release 1.
O PERATION 5 5.5.2 HSMS Message Format This section defines the detailed format of the messages used by the procedures in the previous section. A HSMS Message is transmitted as a single contiguous stream of bytes in the following order: Number of Bytes Description 4 Bytes Message Length. MSB first. Specifies the number of bytes in the Message Header plus the Message Text. 10 Bytes Message Header 0 - n Bytes Message Text. Format is further specified by P-Type field of message header.
5 O PERATION The physical byte order is designed to correspond as closely as possible to the SECS-I header. Session ID is a 16-bit unsigned integer values, which occupies bytes 0 and 1 of the header(byte 0 is MSB). Its purpose is to provide an association by reference between control messages and subsequent messages. Header Byte 2 is used in different ways for different HSMS messages. For Control Messages it contains zero or a status code. For a Data Message it contains the W-Bit and SECS stream.
O PERATION 5 5.5.4 HSMS Message Format Summary Message Header Message Type Bytes 0 – 1 Session ID Data Message W-bit and SECS SECS (no R-Bit) stream Function Byte 2 Byte 3 * Byte 4 PType Byte 5 Bytes 6 - 9 Message Text SType System Bytes 0 0 Primary: Unique Reply: Same as primary Text Select.req * 0 0 0 1 Unique None Select.rsp Same as.req 0 Select Status 0 2 Same as.req None Deselect.req * 0 0 0 3 Unique None Deselect.rsp Same as.
5 O PERATION 5.6 SECS-2 Implementation 5.6.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.
O PERATION 5 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.6.
5 O PERATION Data item examples: Meaning Format Length 1- Byte Integer 4- Byte Integer ASCII 65 01 xx 71 04 MSB ... 41 06 1.chr 2.chr zero-length xx 00 List Data Item 01 03 1. element ... LSB 3.chr 4.chr 5.chr 6.chr 2. element 3. element 5.6.3 Message set The SECSII-message-set used by the BROOKS transponder reader consist of six different stream types.
O PERATION 5 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.
5 O PERATION 5.6.4 Data Items 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 45). The notification “3()” indicates any of the signed integer formats (30, 31, 32, 34).
O PERATION Format: A[max25] ATTRID Description: 5 Identifier for an attribute for a specific type of object.
5 O PERATION “ECID_25” Æ “ECID_26” Æ “ECID_27” Æ “ECID_28” Æ “ECID_29” Æ “ECID_30” Æ “ECID_31” Æ “ECID_32” Æ “ECID_37” Æ “ECID_38” Æ “ECID_42” Æ “ECID_43” Æ “ECID_44” Æ “ECID_45” Æ “ECID_56” Æ “ECID_57” Æ “ECID_99” Æ “ECID100” Æ parameter parameter parameter parameter parameter parameter parameter parameter parameter parameter parameter parameter parameter parameter parameter parameter parameter parameter 25 – sensor 5 delay 26 – watchport for sensor 1 27 – watchport for sensor 2 28 – watchport for sensor
O PERATION Format: A[max4] ATTRVAL Description: 5 Value of the specified attribute.
5 O PERATION Format: A[max2] CPVAL Description: “OP” “MT” State request value … … Where used: operating state maintenance state S18F13 Format: A [max 200] DATA Description: A vector or string of unformatted data. It depends on the size of the MID area. Where used: S18F6, S18F7, S18F68, S18F69 Format: B [max 200] DATAB Description: Byte array of transponder data. It depends on the size of the MID area.
O PERATION Format:A[2] DATASEG Description: 5 Used to identify the data requested. The DATASEG corresponds to the page number (PAGEID) of the ISO 15693 transponder. “00”: First page of any type of transponder or first page of the DATA area. Where used: S18F5, S18F7, S18F67, S18F69 Format:B[1] DATASEGB Description: Used to identify the data requested. The DATASEG corresponds to the real byte of the ISO 15693 transponder. Empty First byte of DATA area (depends on MID settings).
5 O PERATION 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. The BROOKS reader works simultaneously as a gateway and a reader (CIDRW with integrated head). It is the “lower message ID” in the message header. 00 ..
O PERATION 5 Parameter 3 : Block-Protocol-Timeout T2 2 .. 250 1/10s Default: (20) 2s Parameter 4: Reply-Timeout T3 1 .. 120 1s Default: (45) 45s Parameter 5: Inter-Block Timeout T4 This parameter is ineffective if the used messages are not larger than one block. 1 .. 120 1s Default: (45) 45s 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).
5 O PERATION Parameter 10: Not defined! Parameter 11: Reader-ID The reader ID is a part of the device ID. In the message header, it corresponds to the 7 LSB (last significant bits) of the “upper message ID”. 00 .. 127 Default: 0x00 The BROOKS reader works as a gateway (CIDRW) with up to 5 integrated heads. Therefore the reader ID is predefined as 0x00. Of course, the ID can be changed within the valid scope.
O PERATION 5 Parameter 13: Communication port The communication with the host can be done by by HSMS (TCP/IP) or optional by SECS1 (RS232) interface. The following options are possible: 0x11: Host Æ Reader Æ Reader: Host: HSMS HSMS 0x22: Host Æ Reader Æ Reader: Host: SECS1 SECS1 The setting of the DIP switch 1 affects this parameter! The setting of the DIP switch has priority and will be stored in the parameter after a reset.
5 O PERATION 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 ..
O PERATION Default: 5 (10) 1s HF80 Transponder Reader – HSMS, Release 1.
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 tag.
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. 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 Parameter 99: custom code If the customer requires special parameter settings that deviate from the default values, a customer code can be assigned by BROOKS to set several parameter values via one parameter. Parameter 99 will not be stored in the reader and can not be read out. The following values are defined to change several parameters in one step.
O PERATION 5 Parameter 99 = 0x07 32 37 53 54 Parameter# – Tag type – MID area – Readmode – Writemode Value 0x07 0x04 Low High Parameter 99 = 0x85 32 37 53 54 Parameter# – Tag type – MID area – Readmode – Writemode Value 0x85 0x04 Low Low Parameter 100: (0x64) DIP-Switch Enabled Defines which DIP switches are enabled and have influence to the behavior. Via bit 0 to bit 3 the individual DIP switches can be enabled or disabled.
5 O PERATION 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. Where used: S18F10, S18F11, S18F74, S18F75 Format: B[1] OFLACK Acknowledge code for OFF-LINE request.
O PERATION 5 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. 0 … Reset to be done 1 … Reset could not be done Where used: S2F20 Format: B[1] RIC Reset code.
5 O PERATION 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. … Normal operation Indicates the success of the requested action “EE” … Execute error Cannot read tag data . Cannot read ID sequence.
O PERATION 5 Format: A[max18] SSCMD Description: Indicates an action to be performed by the subsystem. Used to differentiate between the different subsystem commands indicated. “ChangeState” … Change state “GetStatus” … Get state “PerformDiagnostics” … Perform diagnostics “Reset” … Reset CIDRW Where used: S18F13 Format: A[max 3] SSTATE Description: Provides status information of the external I/O of a specific head.
5 O PERATION 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. List of a Status L,4 For data items OperationalStatus and HeadStatus see data item ATTRVAL.
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 Write Counter Description: Format: B[4] Write Counter. Part of Tag data which counts the number of write actions to this specific tag. Where used: S18F88, S18F90 Write Counter Length Description: Format: U1 Length of write counter data on tag. Where used: S18F87, S18F89 74 HF80 Transponder Reader – HSMS, Release 1.
O PERATION 5 5.7 SEMI E99 5.7.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.
5 O PERATION 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 Definition ALARM STATUS 76 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.
O PERATION 5 The table below defines the transitions of the BROOKS SECS-1 state model of the transponder reader. # 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.
5 O PERATION 5.7.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.
O PERATION 5 S1F2: ON-LINE (reader -> host) The reader signifies that it is online. S1F2 >. 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 .
5 O PERATION 5.8.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.8.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.8.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 200 bytes of the data area are requested.
5 O PERATION S18F5: READ REQUEST BINARY (RR) (host -> reader, reply) The host requests the subsystem indicated in TARGETID to read information. DATASEGB 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 DATASEGB and DATALENGTH are both omitted (zero length items) then up to 200 bytes of the data area are requested.
O PERATION 5 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 200 bytes in the data area are to be overwritten.
5 O PERATION S18F7: WRITE DATA REQUEST BINARY (host -> reader, reply) This message requests to write data to the subsystem component indicated in TARGETID. DATASEGB 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 DATASEGB and DATALENGTH are both omitted (zero length items), then length of DATAB will be written to the tag.
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 200 bytes of the data area are requested.
5 O PERATION S18F67: READ REQUEST UID BINARY (host -> reader, reply) The host requests the subsystem indicated in TARGETID to read information from the transponder indicated in UID. DATASEGB 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 DATASEGB and DATALENGTH are both omitted (zero length items) then up to 200 bytes of the data area are requested.
O PERATION 5 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 200 bytes in the data area are to be overwritten.
5 O PERATION S18F69: WRITE DATA REQUEST UID BINARY (WARU) (host > reader, reply) This message requests to write data to the subsystem component indicated in TARGETID to the transponder indicated in UID. DATASEGB may be used to indicate a specific section of the data area to be written or overwritten. S18F69 W L,5 1. 2. 3. 4. 5. If DATASEGB and DATALENGTH are both omitted (zero length items), then up to 200 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. HF80 Transponder Reader – HSMS, Release 1.
5 O PERATION S18F85: SCAN UID AND READ ID REQUEST (STR) (host -> reader, reply) This message is used to request the subsystem indicated in TARGETID to perform a scan and the read of the MID. S18F85 W S18F86: SCAN UID AND READ ID ACKNOWLEDGE (STA) (reader -> host) This message reports the result from the subsystem specified in TARGETID for the requested action. S18F86 L,3 1. 2. 3.
O PERATION 5 S18F87: Read Write-Counter (host -> reader, reply) This message is used to request the subsystem indicated in TARGETID to read out the write counter of the tag. > > S18F88: Read Write-Counter Response (reader -> host) This message reports the result from the subsystem specified in TARGETID for the requested action. > > HF80 Transponder Reader – HSMS, Release 1.
5 O PERATION S18F89: Read Write-Counter with UID (host -> reader, reply) This message is used to request the subsystem indicated in TARGETID to read out the write counter of the tag specified by his UID. > > S18F90: Read Write-Counter Response with UID (reader -> host) This message reports the result from the subsystem specified in TARGETID for the requested action.
O PERATION 5 5.
5 O PERATION 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 ) 106 HF80 Transponder Reader – HSMS, Release 1.
O PERATION 5 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 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 HF80 Transponder Reader – HSMS, Release 1.
5 O PERATION 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 108 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 HF80 Transponder Reader – HSMS, Release 1.
O PERATION 5 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 request
5 O PERATION 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 re
O PERATION 5 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 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 HF80 Transponder Reader – HSMS, Release 1.
5 O PERATION The reader detects an unrecognized device ID and sends the message S9F1.
O PERATION 5 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
5 O PERATION The reader detects an unrecognized function and sends the message S9F5.
O PERATION 5 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
5 O PERATION 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,
O PERATION 5 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
5 O PERATION In: Data ( 4C 45 ) In: Checksum ( 09 3F ) Out: ACK ( 06 ) The host requests all fundamental CIDRW attributes defined in ATTRID. The reader answers with the current attribute values.
O PERATION 41 02 4E 45 Æ PMInformation “NE” 41 01 30 Æ Alarmstatus “0” 5 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.
5 O PERATION The reader shows the success of the operation with SSACK “NO” (normal operation) and with the read values.
O PERATION 5 S18F5 Read Data: U2 DATASEGB=<56> und DATALENGTH=<4> Host to Reader: S18F5 Out: Header (00 00 92 05 00 00 00 00 00 0A) Out: Data 01 03 41 02 30 31 Æ Head ID 01 A9 02 00 38 Æ DATASEGB 56dez A9 02 00 04 Æ DATALENGTH 4dez Host to Reader: S18F6 Out: Header (00 00 92 05 00 00 00 00 00 0A) Out: Data 01 03 41 02 30 31 Æ Head ID 01 41 02 4E 4F Æ SSACK “NO” 21 04 00 00 00 00 Æ 4 Byte tag data HF80 Transponder Reader – HSMS, Release 1.
5 O PERATION Host writes data on first page of DATA area with S18F7 Host to Reader: S18F7 Out: ENQ ( 05 ) In: EOT ( 04 ) Out: Length Byte ( 22 ) Out: Header ( 00 00 92 07 80 01 00 00 00 2B ) Out: Data 01 04 41 02 30 31 Æ TARGETID “01” 41 02 30 30 Æ DATASEG “00” A9 02 00 08 Æ DATALENGTH 0x08 41 08 32 32 32 32 32 32 32 32 Æ DATA “22222222” Out: Checksum ( 1C 02 ) In: ACK ( 06 ) Reader to Host: S18F8 In: ENQ ( 05 ) Out: EOT ( 04 ) In: Length Byte ( 2B ) In: Header ( 80 00 12 08 80 0
O PERATION 5 S18F7 Write Data: DATASEG=<56> and DATALENGTH=<4> and DATA[4] < L4 < < < < > A TARGETID = '01' > U2 DATASEGB = 56 > U2 DATALENGTH = 4 > B DATA = 44 45 46 47 > S18F8 (WDA) - write data ACK < L3 < A TARGETID = '01' > < A SSACK = 'NO' > < L4 - STATUS1 < PMInformation < A = 'NE' > < A = '0' > < A = 'IDLE' > < A = 'IDLE' > > > 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 0
5 O PERATION 30 30 30 30 30 30 31 Æ MID “MID0000000000001” 01 01 01 04 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 ( 0A 5E ) Out: ACK ( 06 ) The host wants to read the material ID of any transponder. The reader confirms the success of the read command with SSACK “NO” and returns the material ID. (For chapter data items, see page 45).
O PERATION 5 01 01 01 04 41 02 4E 45 41 01 30 41 04 4D 41 4E 54 41 04 4E 4F 4F 50 In: Checksum ( 07 04 ) Out: ACK ( 06 ) The host wants to write a new material ID to any transponder. The reader confirms the success of the write MID command with SSACK “NO”. Note: the material ID can be changed only if the reader is in the maintenance state. (MANT) If the reader remains in the IDLE state, the command fails and the reader answers with SSACK “EE” (execute error).
5 O PERATION 01 03 41 02 30 31 Æ TARGETID “01” 41 02 4E 4F Æ SSACK “NO” 01 01 01 04 41 02 4E 45 Æ PMInformation “NE” 41 01 30 Æ Alarmstatus “0” 41 04 4D 41 4E 54 Æ OperationalStatus “MANT” 41 04 4E 4F 4F 50 Æ HeadStatus “NOOP” In: Checksum ( 07 10 ) Out: ACK ( 06 ) ChangeState is an optional service that requests the CIDRW to change its operational sub state to MAINTENANCE (“MT”) or to OPERATING (“OP”).
O PERATION In: Header ( 80 00 12 0E 80 01 00 00 00 21 ) In: Data 5 01 03 41 02 30 31 Æ TARGETID “01” 41 02 4E 4F Æ SSACK “NO” 01 01 01 04 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 DF ) Out: ACK ( 06 ) 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.
5 O PERATION In: Header ( 80 00 12 06 80 01 00 00 00 1A ) In: Data 01 03 41 02 30 31 Æ TARGETID “01” 41 02 43 45 Æ SSACK “CE” 41 00 Æ DATA “” In: Checksum ( 02 E7 ) Out: ACK ( 06 ) The TARGETID in the S18F5 message does not correspond to the TARGETID in the reader detecting the error. The reader therefore answers with a communication error “CE”. 128 HF80 Transponder Reader – HSMS, Release 1.
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 Æ
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.
O PERATION 5 The host requests the write counter of the tag of head 01. Host to Reader: S18F87 Out: Header (00 00 92 57 00 00 00 00 00 0C) Out: Data 01 02 41 02 30 31 Æ TARGETID A5 01 04 Æ Write Counter Length Reader to Host: S18F88 In: Header (00 00 12 58 00 00 00 00 00 0C) In: Data 01 03 41 02 30 31 Æ TARGETID 41 02 4E 4F Æ SSACK “NO” 21 04 00 00 00 02 Æ Write-Counter HF80 Transponder Reader – HSMS, Release 1.
5 O PERATION 5.10 HSMS MESSAGE EXAMPLES Starting routine of the HSMS-protocol Outgoing: Length Byte ( 00 00 00 0A ) Outgoing: Select.req ( FF FF 00 00 00 01 80 00 00 01 ) Incoming: Length Byte ( 00 00 00 0A ) Incoming: Select.rsp ( FF FF 00 00 00 02 80 00 00 01 ) Outgoing: Length Byte ( 00 00 00 0A ) Outgoing: Linktest.req ( FF FF 00 00 00 05 80 00 00 02 ) Incoming: Length Byte ( 00 00 00 0A ) Incoming: Linktest.req ( FF FF 00 00 00 05 80 00 00 01 ) Outgoing: Length Byte ( 00 00 00 0A ) Outgoing: Linktest.
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 144 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 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 LED’s (see page 142). 3 If you are not sure about the active host interface then test both interfaces (RS232 and Ethernet).
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 LED’s, except for the power LED, are extinguished. 6.8 Software Releases Release Date 12/2008 Version RS2P15 01/2009 RS2P20 02/2009 RS2P21 Description First Version. (Fineversion 150) Fineversion 200.
D EINSTALLATION 7 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 19). HF80 Transponder Reader – HSMS, Release 1.
8 T RANSPORTATION 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.
A CCESSORIES 9 9 ACCESSORIES 9.1 Device Options Type Part-No.
9 A CCESSORIES 9.2 Antennas Different antenna types are available on request! 9.2.1 Reading and Writing Ranges The reading and writing range depends on the type of antenna, the type of tag, the power level at antenna and the installation environment (metal close to antenna and/or tag). 9.3 Power Supply Type Power Supply 24VDC EURO-Plug Part-No. SVG 0,33 HF Power Supply 24VDC Adapters for different countries 148 SVG0,6HF-UNI HF80 Transponder Reader – HSMS, Release 1.
