English Product Manual RFID Reader LF60C SoliD The operating manual must be read prior to the initial start-up. Observe the safety instructions! Store for future use! This documentation is not subject to revisions.
Information This product manual corresponds with "Directive 1999/5/EC of the European Parliament and the Council on radio equipment and telecommunications transmission equipment and the mutual recognition of the conformity". This product manual is addressed to the operating company who must pass it on to the personnel responsible for installation, connection, use and repairs of the machine.
Information Archiving Store the product manual in the vicinity of the device! Always keep the product manual handy! Symbols and signal words The following symbols and signal words are used in this documentation. The combination of a pictograph and a signal word classifies the respective safety information. The symbol can vary depending on the type of danger.
Information Target group The operating instructions are addressed to personnel with the following areas of responsibility: Area of responsibility Competence Installation, transport and storage Specialized personnel Commissioning, operation and decommissioning Instructed personnel Troubleshooting Specialized personnel Definition according to DIN EN 60204-1: Instructed personnel: Persons who have been instructed and, if required, trained by a specialist as to the tasks assigned to them, the possible r
Contents 1 2 3 4 5 6 Identification . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.1 Designated use 8 1.2 Incorrect use 9 Declaration of Conformity . . . . . . . . . . . . . . . 10 2.1 USA - Federal Communications Commission (FCC) 10 2.2 Europe - CE conformity 12 General Instructions . . . . . . . . . . . . . . . . . . . 14 3.1 Liability and warranty 14 3.2 Objectives of the operating instructions 14 Safety Instructions . . . . . . . . . . . . . . . . . . . . 16 4.
Contents 7 6.4 Assembly of the device 30 6.5 Antenna installation 31 6.5.1 Positioning the antenna 31 6.5.2 Available antenna types 32 6.5.3 Dimensions for planning 32 6.6 Connecting the transponder reader 33 6.7 Power/RS485 bus connection 34 6.8 RS232 connection 35 6.9 Commissioning 35 6.9.1 Required operating conditions 35 6.9.2 Parameters of the serial interface 35 6.10 Ethernet connection 36 6.11 Input and output 37 6.12 DIP switches 38 Operation . . . . . .
Contents 7.4.9 HSMS message examples 7.4.10 SECS-I message examples 8 9 10 11 124 124 Service and Troubleshooting . . . . . . . . . . . . 147 8.1 General 147 8.2 Qualified troubleshooting personnel 148 8.3 Safety instructions 148 8.4 Error codes 149 8.4.1 Error ID and Alarm ID 149 8.4.2 SSACK 151 8.4.3 Stream function 152 8.5 Error display with LED 153 8.5.1 Power LED does not light up 153 8.5.2 Read fail LED flashes 153 8.6 Reader does not respond 153 8.
Chapter 1 Identification 1 Identification This chapter gives you an overview of the following topics: Model LF60C Model LF60CM ■ Designated use ■ Incorrect use Serial number 1101MIS10001 Part number TLS-23B-7O00-T1-00E1 RS232/Ethernet TLS-13B-7O00-T1-00E1 RS232 Serial number 1101MIS10001 Part number TLS-23B-7O00-T1-66E1 RS232/Ethernet Manufacturer Brooks Automation (Germany) GmbH RFID Division Gartenstr.
Chapter 1 Identification Intended use also includes the following: ■ following all instructions in the operating instructions ■ observing all safety information Before using the device, the user should ensure that the national approval requirements for use are met. 1.
Chapter 2 Declaration of Conformity 2 Declaration of Conformity This chapter gives you an overview of the following topics: ■ USA - Federal Communications Commission (FCC) ■ Europe - CE conformity 2.1 USA - Federal Communicatio ns Commission (FCC) This device complies with Part 15 of the FCC Rules.
Chapter 2 Declaration of Conformity FCC ID: N5GLF60C Compliance with: FCC Code of Federal Regulations, Part 15 Subpart C, Section §15.205 FCC Code of Federal Regulations, Part 15 Subpart C, Section §15.209 WARNING Changes or modifications not expressly approved by the party responsible for compliance may void the user's authority to operate the equipment.
Chapter 2 Declaration of Conformity 2.
Chapter 2 Declaration of Conformity Schutzanforderungen in Bezug auf die elektromagnetische Verträglichkeit (§ 3 (1) 2, Artikel 3 (1) b) Protection requirements concerning electromagnetic compatibility § 3(1)(2), (Article 3(1)(b)) angewendete harmonisierte Normen Harmonized standards applied EN 301 489-1 V1.8.1 EN 301 489-3 V1.4.
Chapter 3 General Instructions 3 General Instructions This chapter gives you an overview of the following topics: ■ Liability and warranty ■ Objectives of the operating instructions 3.1 Li ab i l i t y an d wa rr an t y The "General sales and delivery conditions" of Brooks Automation (Germany) GmbH always apply. The warranty period is 12 months beginning with the delivery of the device, which is verified by the invoice or other documents.
Chapter 3 General Instructions Objectives: ■ to avoid accidents ■ to increase the service life and reliability of the device ■ to reduce costs due to production downtimes Product Manual - RFID Reader LF60C SoliD 15
Chapter 4 Safety Instructions 4 Safety Instructions This chapter gives you an overview of the following topics: ■ Area of application and symbols ■ Obligations ■ ESD instructions ■ Residual risks ■ Additional instructions 4.1 DANGER Ar ea o f a pp l i ca t i o n a n d s y m bo l s Danger to life, risk of injuries or loss of property Risks exist when disregarding the operating instructions and the safety instructions therein.
Chapter 4 Safety Instructions 4.1.2 Warning symbols Warning: Hazardous area Warning against hazardous electrical voltage Warning against electromagnetic radiation Warning: Flammable materials Warning: Potentially explosive atmosphere Warning against electrostatically sensitive components 4.1.3 Prohibition symbols Unauthorized access is prohibited Fire, open flame and smoking is prohibited Switching is prohibited Prohibition 4.1.
Chapter 4 Safety Instructions 4.2 Obligatio ns 4.2.1 Operating company's obligations The safe condition and use of the device is a requirement for the safe operation of the device.
Chapter 4 Safety Instructions 4.3 CAUTION E SD instruct ions Static electricity can damage electronic components in the device. All persons installing or maintaining the device must be trained in ESD protection. ESD protective measures must be applied when opening the device. Disconnect the power supply prior to removing or adding components! Discharge your body and all tools used prior to touching any components on the interior of the device! 4.
Chapter 4 Safety Instructions ATTENTION Disconnect the device from the power supply system if active parts of the device can be accessed with tools. Access is only permitted for authorized personnel. Regularly check the electrical equipment of the device. Regularly check all moving cables for damage within the scope of maintenance and repairs. DANGER Risk of fire and explosions Fire and explosions may occur within the vicinity of the device.
Chapter 4 Safety Instructions Rules and regulations ■ Install the device only in accordance with the manufacturer's instructions. ■ Use only the accessories and cables supplied by the manufacturer. ■ Troubleshooting that is not described in the chapter Service and Troubleshooting may only be performed by the manufacturer. ■ People with hearing aids should be aware that the radio signals emitted by the device can cause annoying noises in the hearing aid.
Chapter 5 Product Specifications 5 Pr o d u c t S p e c i f i c a t i o n s This chapter gives you an overview of the following topics: ■ Function ■ Images ■ Technical data 5.1 Function The BROOKS Transponder Reader System is a high-frequency identification system that uses FM transmissions. 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.
Chapter 5 Product Specifications 5.2 Images 5.2.
Chapter 5 Product Specifications 5.2.2 Rear view 1 2 4 1 Switches: Protocol selection (from FW SG2IS12 / SG2IV1.
Chapter 5 Product Specifications 5.3 Techni cal data Technical data - device Operating temperature 0 °C to +50 °C 32 °F to 122 °F Storage temperature -20 °C to +70 °C -4 °F to +158 °F Permissible humidity at 50 °C / 122 °F 25 - 80 % Transmitter frequency 134.
Chapter 5 Product Specifications 5.3.1 Device label The device label with the CE mark, part/serial number, and the MAC address is on the device housing. 1 2 3 1 Part number 2 Serial number 3 MAC address 5.3.
Chapter 6 Installation 6 Installation This chapter gives you an overview of the following topics: ■ Safety instructions ■ Qualified installation personnel ■ Unpacking ■ Assembly of the device ■ Antenna installation ■ Connecting the transponder reader ■ Power/RS485 bus connection ■ RS232 connection ■ Commissioning ■ Ethernet connection ■ Input and output ■ DIP switches Follow the instructions in the safety chapter Follow the general safety instructions in th
Chapter 6 Installation CAUTION Never expose the device to extreme temperature fluctuations, since otherwise condensation develops in the device and causes damage. Do not install the device in the vicinity of voltage lines or other power lines with which they could collide (for example, when drilling), which could result in serious injuries or even death.
Chapter 6 Installation ATTENTION When determining the installation site, keep in mind the length of the antenna wire and the read/write range of the antenna used. 6.2 Quali fied install ati on per sonnel CAUTION The installation is to be carried out by specially trained personnel only. If you are uncertain about their qualification, contact the manufacturer. CAUTION Operating the device without special training can result in damage to the reader and/or connected devices. 6.
Chapter 6 Installation 6.4 ATTENTION Assembly of the device The mounting surface must be stable, non-flammable, dry and clean. If necessary, clean it before installing the device. The device must be installed so that air can freely circulate vertically through the heat sink, and the operating and environmental conditions specified under Technical data are met at all times.
Chapter 6 Installation 6.5 ATTENTION Antenna installation When installing the antenna, consider the required reading and writing ranges. The reader can only be used properly if the transponder is located within the individual reading/writing range of the antenna. If the transponder is very close to the antenna, the transponder may be detuned by the metal of the antenna and a reading/writing is not possible. We recommend keeping a minimum distance between transponder and antenna of about 10 mm. 6.5.
Chapter 6 Installation Parallel The illustration shows the optimal position of the transponder if it is positioned parallel to the axis of the antenna. Perpendicular The illustration shows the optimal position of the transponder if it is perpendicular to the axis of the antenna. 6.5.2 Available antenna types Different types of antennas are available on request. 6.5.
Chapter 6 Installation Mini antenna a1 Length of antenna cylinder 68 mm a2 Complete mounting dimensions (cable with 90 ° angle) 85 mm b1 Diameter of antenna cylinder 10.0 mm a1 Length of antenna cylinder 40 mm a2 Complete mounting dimensions (cable with 90 ° angle) 60 mm b1 Diameter of antenna cylinder 10.0 mm Micro antenna 6.6 Antenna C onnecting the t r a n sp o n d er r e a de r Connect the antenna to the antenna port ( Images).
Chapter 6 Installation 6.7 LF60C DANGER P ower/RS485 bus connection Software version SG2S12/SG2IV1.2 does not support communication over RS485. Risk of death due to dangerous voltage Risks exist when supplying the device with the incorrect voltage. Only use cables, plugs and adapters supplied by the manufacturer. Observe power ratings of the technical data ( Technical data). The device can be connected to an interior DC power circuit of the equipment or to a DC adapter.
Chapter 6 Installation 6. 8 RS232 c onn ect ion The RS232 port is a shielded RJ45 socket. A cable for connecting to a PC is available. Pin Signal 4 Ground 5 TxD 6 RxD 6.9 C ommissioning 6.9.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.
Chapter 6 Installation 6.10 Ethernet co nnection The 10/100 BaseT Ethernet interface has the following default settings: DHCP mode IP address Gateway address Subnet mask OFF 10.73.254.211 10.73.254.254 255.255.254.0 If DHCP is enabled and the DHCP Server is not available, the device initializes the Ethernet connection with the following values: IP address Gateway Subnet mask Primary DNS Server IP Secondary DNS Server I (MAC address 169.254.MAC5.MAC6 169.254.MAC5.254 255.255.255.0 0.0.0.0 0.0.0.
Chapter 6 Installation 6.11 Input and output LF60C The port labeled Remote I/O is used for external presence sensors and an external output like a LED for status indication. The input signal is used for pod placement and pod removal events. The port is a shielded RJ45 socket.
Chapter 6 Installation LF60CM 5-pin connecting plug 6.12 DIP switches The activation of a DIP switch depends on the value of parameter 36. Switch # 1 "Test mode" function Deactivation of automatic protocol recognition from version SG2S12 "OFF" - automatic protocol recognition active "ON" - automatic protocol recognition deactivated The protocol setting depends on the DIP2 switch setting.
Chapter 7 Operation 7 O pera ti o n This chapter gives you an overview of the following topics: ■ Operating personnel ■ Protocol change ■ Operation of the ASC-I1 protocol ■ Operation of SECS/HSMS Protocol 7.1 CAUTION Operating personnel The RFID Reader LF60C SoliD is designed to be operated by specially trained personnel only. If you have doubts about the required qualifications, contact the manufacturer.
Chapter 7 Operation 7.2.2 Automatic protocol recognition (default) The reader automatically adapts to the relevant protocol by checking and analyzing the first message it receives after a reset. Depending on the data received, the interface is switched over accordingly and reinitialized. This procedure can take several seconds. The messages sent are then lost. The protocol found is used for further communication. Another change can only take place after another reset.
Chapter 7 Operation 7.3 Operation of t he A S C-I 1 p ro t o co l 7.3.1 Structure of the communication protocol General remarks: ■ The communication is done with ASCII packages. ■ Each reader represents a transponder reader with an RS232 interface or Ethernet interface to which an address from 0 to E can be assigned. When the reader is delivered, the address is 0. ■ After each command to the reader, a defined response is sent. We recommend waiting for this response before sending a new command.
Chapter 7 Operation Message structure The message includes a command, a target address and a source address as well as information. Message Command Address Information Command ASCII character ( Commands reader to host) Address Target/source address; ASCII character '0'...'E' for the reader * Information Depends on the command (includes none, one or more ASCII characters '0'...'F') The message length describes the number of characters of a message. * The reader is preset with 0 when delivered.
Chapter 7 Operation 7.3.
Chapter 7 Operation Commands reader to host Command Description x Read data/acknowledgement w Write data/acknowledgement R Automatic read g Request parameter value/acknowledgement p Set parameter/acknowledgement n Reset/acknowledgement e Error message h Heartbeat/acknowledgement v Query software version/acknowledgement l Lock a page of the transponder/acknowledgement i Set tuning of the RF module/acknowledgement j Request tuning settings of the RF module/acknowledgement A Sensor
Chapter 7 Operation Message items CMD 1 byte Command of the message. See table in chapter Commands reader to host Data 16 bytes The data are interpreted in HEX format. That means that 2 ASCII characters define one byte tag data in HEX format. The data always contains all 8 bytes of the specified page of the transponder.
Chapter 7 Operation Reader ID 1 byte Address of the device (0 .. E). The default address of the card is 0 on delivery. Response code 4 bytes This feature is not used for the single reader. This code is always "0000". Serial No. 4 bytes Contains the 4-byte serial number of the reader. The serial number is also shown on the label of the reader.
Chapter 7 Operation X - Read data Command X starts the reading of a transponder. If there is no tag in the reading range of the antenna, the reader returns an error message (error 4 - no tag). Data item "Page" can have the following values. Value 1) Description '01' to '17’ read page# ’98’ read more pages until end character or empty character1) ’99’ read entire tag data 'E' respectively 'F' in ID Bit 0...
Chapter 7 Operation W - Write data The command W starts the writing to a transponder. If there is no tag in the writing range of the antenna, the reader returns an error message (error 4 - no tag). Host Reader CMD Reader ID Page Data W 1 byte 2 bytes 16 bytes Reader Host CMD Reader ID w 1 byte If 'write tag' fails, writing is repeated in the defined time frame (parameter 3: r/w delay time; parameter 4: r/w maxrepeat).
Chapter 7 Operation R - Automatic read The external input is used to trigger an automatic read action. The R command sends the read data to the host. The host then has to confirm the message.
Chapter 7 Operation G - Request parameter value The command G is used to request the value of all public parameters of the device. Host Reader CMD Reader ID G 1 byte Reader Host CMD Reader ID Parameter No. Parameter value g 1 byte 2 bytes 16 bytes The reader sends an individual protocol package for each available public parameter. After the last parameter the reader sends an end package including the command 'g' and the source address '0'..
Chapter 7 Operation P - Set parameter Command P can be used to change the value of individual parameters. After successfully changing a parameter, the device sends a confirmation message. Host Reader CMD Reader ID Parameter No.
Chapter 7 Operation N - Reset The command N performs a reset of the reader hardware and software. After the reset the device sends a confirmation message. Host Reader CMD Reader ID N 1 byte Reader Host CMD Reader ID n 1 byte If the power to the device has been turned on (hardware reset), the host is informed about it (RS232 interface only). With regard to the TCP/IP option of the device, no command is sent after a hardware reset because a TCP/IP connection must be opened first.
Chapter 7 Operation e - Error message If an error occurs, the device sends an error message with the corresponding error code to the host. Reader Host CMD Reader ID Error ID e 1 byte 1 byte For more information on error codes and the corresponding correcting actions please refer to Error codes.
Chapter 7 Operation H - Heartbeat The command H sends a heartbeat request to the reader. The reader responds with his serial number and a response code. Host Reader CMD Reader ID H 1 byte Reader Host CMD Reader ID Serial No. Response code h 1 byte 4 bytes 4 bytes The response code is part of the protocol but is not used for this device. The response code is always '0000'. Because of compatibility with other systems, the heartbeat is also allowed with the address 'F'.
Chapter 7 Operation V - Query software version The command V is used to request the installed software version of the transponder reader. Host Reader CMD Reader ID V 1 byte Reader Host CMD Reader ID Software version v 1 byte 16 bytes The 8 characters of the software version are described by 16 ASCII characters. Each character is described in HEX format represented by 2 ASCII characters (see section Message examples).
Chapter 7 Operation L - Lock a page of An individual page of a multipage transponder can be locked (read only). the transponder Host Reader CMD Reader ID Page L 1 byte 2 bytes Reader Host CMD Reader ID l 1 byte If the page of the transponder could not be locked, the writing action is repeated automatically (parameter 3: r/w delaytime and parameter 4: r/w maxrepeat). If the page still could not be locked, an error message NoTag (4) is sent to the host.
Chapter 7 Operation I - Set tuning of the RF module Depending on the surroundings of the antenna it might be necessary to tune the RF module to get the optimal reading/writing range for this special installation environment. The RF module therefore has 3 capacitors which can be switched ON or OFF. Each capacitor has one reserved bit which shows its status. The tuning can be set manually (not recommended) or automatic tuning can be performed (recommended).
Chapter 7 Operation J - Request tuning settings of RF module Command J requests the current setting of the tuning capacitors. The response message contains the current status of the capacitors in hexadecimal format. Each capacitor has one reserved bit which shows its status.
Chapter 7 Operation A - Sensor event If parameter watchport is activated ('01'), the reader reports the release event of the external sensor. The event message must be confirmed by the host. Host Reader CMD Reader ID A 1 byte Reader Host CMD Reader ID a 1 byte If the host does not send an acknowledge message, the message is repeated (value 6: RS232 maxrepeat) in the defined time frame (value 5: RS232 delaytime).
Chapter 7 Operation 7.3.4 Parameters No. (dec.) No. (hex) Parameter name 0 0x00 Sensor delay 1 0x01 Read mode 2 0x02 Read page 3 0x03 r/w repeat time 4 0x04 r/w max repeat 5 0x05 RS232 repeat time 6 0x06 RS232 max repeat 7 0x07 Watch port F Parameter 0 (0x00) Reader address Sensor delay Operation delay for the presence sensor. 01 .. 99 (0.1 seconds) Default: 10 (1s) Parameter 1 (0x01) Read mode Readmode for automatic read triggered by external input.
Chapter 7 Operation Parameter 2 (0x02) Read page Page for readmode "00". 00 - First page of any type of transponder 01 .. 17 - Page of multipage transponder Default: 00 (first page of any type of transponder) Parameter 3 (0x03) r/w repeat time Time between two read or write attempts. 01 .. 99 (0.1 s) Default: 05 (0.5 s) Parameter 4 (0x04) r/w max repeat Maximum number of read/write attempts. 01 ..
Chapter 7 Operation Parameter F Reader address Reader address of the device. 0 .. E - 0 up to 14 Default: 0 7.3.
Chapter 7 Operation W - Write data (write to page 1 of multipage transponder) >> W0013132333435363738 << w0 Command W Reader ID Page Data 0 01 '3132333435363738' ASCII "12345678" R - Automatic reading << R0013132333435363738 >> r0 Command R Reader ID Page Data 0 01 '3132333435363738' ASCII "12345678" V - Request software version >> V0 << v05347324956312E30 Command V Reader ID 0 Software Version '5347324956312E30' ASCII "SG2IV1.
Chapter 7 Operation 7.4 Operation of SECS/HSMS Protocol 7.4.1 Introduction The SECS-I standard defines a communication interface that is suitable for exchanging messages between semiconductor processing equipment and a host. A host is a computer or network of computers that exchanges information with the equipment to perform/execute the production. The standard does not define the data contained within a message.
Chapter 7 Operation 7.4.2 SECS-I implementation This message set describes the communication between a SECS-I reader and a host. The host and the transponder reader communicate via an RS232 interface (SECS-I). Character structure Data is 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.
Chapter 7 Operation Message block SECS message blocks have the following form: structure Byte Length 0 1 msb Length without checksum, 10 - 254 R 2 3 6 Upper device ID (Reader ID) Lower device ID (Gateway ID) W 4 5 Description Upper message ID (Stream) Lower message ID (Function) E Upper block number Lower block number 7 System byte 1 8 System byte 2 9 System byte 3 10 System byte 4 Text 11 - 254 message text, user data Check sum 255, 256 16-bit unsigned checksum System bytes
Chapter 7 Operation Upper device ID R-bit 0 Lower device ID Last two digits of the serial number Direction reader to host 0 0 0 0 1 0x81xx * Direction Host to equipment (reader) 0x01xx * * The serial number is located on a label on the reader. The W bit indicates that the sender of a primary message expects a reply. A value of 1 in the W bit means that a reply is expected. The message ID identifies the format and content of the message being sent.
Chapter 7 Operation Block transfer The drawing below illustrates some simple message interactions between the host protocol and the equipment. The figure shows the possible handshake sequence to acquire the status of the equipment. 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 . If it receives an , it puts off sending its message, sends an and then reads the other message.
Chapter 7 Operation 7.4.3 HSMS option The hardware version with an Ethernet interface uses the HSMS protocol. It works as a HSMS server. That means that it waits for a connection inquiry of any HOST PC. TCP/IP: IP address xxx.xxx.xxx.xxx Port 3241 If a connection inquiry of any HOST takes place, the reader initializes the HSMS connection, and the SECS-II messages defined in the message set are forwarded from the reader to the respective HOST and vice versa.
Chapter 7 Operation B - NOT SELECTED A sub-status of CONNECTED in which no HSMS session has been established or any previously established HSMS sessions have ended. C - SELECTED A sub-status of CONNECTED in which at least one HSMS session has been established. This is the normal "operating" status of HSMS: data messages may be exchanged in this status. # Current status Trigger New status Comment 1 ...
Chapter 7 Operation 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.
Chapter 7 Operation HSMS message format This section defines the detailed format of the messages used by the procedures in the previous section. An HSMS message is transmitted as a single continuous 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.
Chapter 7 Operation HSMS message header The message header is a 10-byte field. The bytes in the header are numbered from byte 0 (first byte transmitted) to byte 9. The format of the message header is as follows: Bytes Description 0-1 Session ID (Device ID) 2 Header byte 2 3 Header byte 3 4 P-type 5 S-type 6-9 System bytes The physical byte order is designed to correspond as closely as possible to the SECS-I header.
Chapter 7 Operation Value Description 0 SECS-II Encoding 1 - 127 Reserved for subsidiary standards 128 255 Reserved, not used S-type (session type) is a 1-byte unsigned integer value which occupies header byte 5. Value Description Value Description 0 Data message 6 Linktest.rsp 1 Select.req 7 Reject.req 2 Select.rsp 8 Not used 3 Deselect.req 9 Separate.req 4 Deselect.req 10 Not used 5 Linktest.
Chapter 7 Operation HSMS message format summary Message header Message type bytes 0 - 1 Session ID byte 2 byte 3 byte 4 P-type Data message * SECS Functio n 0 (no R bit) W bit and SECS stream Select req * 0 0 Select.rsp Same as.req 0 Deselect.req * Deselect.rsp byte 5 S-type bytes 6 - 9 System bytes Message text 0 Primary: Unique Reply: Same as primary Text 0 1 Unique None Select status 0 2 Same as.req None 0 0 0 3 Unique None Same as.
Chapter 7 Operation 7.4.5 Introduction SECS-II implementation The SEMI Equipment Communication Standard Part 2 (SECS-II) defines 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-I). The messages defined in this specification support the typical activities required for the BROOKS transponder reader.
Chapter 7 Operation Byte 0 1 Name Format and number of the length bytes Length bytes 1-2 1-3 Next Data Description The data format is coded in the upper 6 bits. The two less significant bits determine the number of the following length bytes. The length corresponds to the number of the bytes of a data element. In the "List" format, the length corresponds to the number of the list elements. The standard does not require the minimum possible number of length bytes for a given data length.
Chapter 7 Operation Data items The formats represent arrays of types: [number of elements], whereby is one of the following: Octcode Hexcode Format Meaning Example 00 01 List List element with the number of the "Length" data elements 11 25 Boolean 1-byte Boolean false = 00 true = 01 10 21 Binary Byte sequence of the length "Length" 20 41 ASCII Printable ASCII characters 31 65 I1 1-byte signed integer
Chapter 7 Operation Data item examples Meaning Format Length 1-byte integer 65 01 xx 4-byte integer 71 04 MSB ... ... LSB ASCII 41 06 1st chr 2nd chr 3rd chr 4th chr Zero-length xx 00 List data item 01 03 Message set 1st element 2nd element 5th chr 6th chr 3rd element The SECS-II message set used by the LDN reader consists of six different stream types.
Chapter 7 Operation Stream 5: (Exception handling) S5F1 and S5F2 Alarm report send Stream 9: (System errors) S9F1 Unrecognized device ID S9F3 S9F5 S9F7 S9F9 Unrecognized stream type Unrecognized function type Illegal data Transaction timer timeout For more information on error codes and the corresponding correcting actions please refer to Error codes.
Chapter 7 Operation Data item This section defines the data items used in the standard SECS-II messages dictionary 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 the chapter Data items.
Chapter 7 Operation ALARM STATUS Description Format: A[1] The value of the alarm status refers to the last reading process. If a read or write error occurs, the alarm status is set. A successful read or write resets the alarm status. When leaving maintenance mode, the alarm status is also deleted. 0 1 ... ... Where used No alarm Alarm S18F13 ALCD Format: B[1] Alarm code byte Only the occurrence of an error is reported. Errors are not generally reset.
Chapter 7 Operation ALTX Format: A[max40] Alarm text The length of the alarm text is 0 to 40 characters. According to the reader version, status information about the sensor or sensors is also transmitted during a reader error message.
Chapter 7 Operation "ECID_06" "ECID_07" "ECID_08" "ECID_09" "ECID_10" "ECID_11" "ECID_12" "ECID_20" "ECID_22" "ECID_23" "ECID_24" "ECID_25" "ECID_26" "ECID_27" "ECID_29" "ECID_30" "ECID_31" "ECID_32" "ECID_33" "ECID_34" "ECID_35" "ECID_36" "ECID_37" "ECID_38" "ECID_40" "ECID_41" "ECID_42" "ECID_43" "ECID_44" "ECID_45" "ECID_98" "ECID_99" parameter parameter parameter parameter parameter parameter parameter parameter parameter parameter param
Chapter 7 Operation ATTRVAL Format: A[max4] Description: Value of the specified attribute.
Chapter 7 Operation CPVAL Format: A[] Description Status request value OpStatus Operation status "OP" ... "MT" ... Maintenance or Idle Operating status Maintenance status LEDStatus LED state "Off" ... "On" ... "Flash" ... Switch LED off Switch LED on Switch LED to flash with 1Hz LedNO LED number, 1 byte "1" "2" "3" "4" "5" Status LED Status LED External output Read OK LED Read Fail LED Timeout Timeout period Units Seconds Range "1" - "98" "99" has a special meaning: it specifies "always".
Chapter 7 Operation DATALENGTH Format: U2 Description Total bytes to be sent. The DATALENGTH corresponds to the quantity of bytes that are to be read or written. The valid range depends on the length of the MID area (parameter 37). Where used S18F5, S18F7 DATASEG Format:A[2] Description Used to identify the data requested. The DATASEG corresponds to the page number (PAGEID) of the ISO 15693 transponder.
Chapter 7 Operation ECID Format: U1 Parameter number of reader (see data item ECV) Where used 2F13, S2F15 ECV Format: U1 Reader parameter definition. The values are displayed as decimal values. MDLN Format: A[6] Equipment model number. Where used S1F2 MF Format: B[1] Material format code. 20: The material port number corresponds to the sensor number and status Where used S3F5, S3F7 MHEAD Format: B[10] SECS message block header associated with message block in error.
Chapter 7 Operation MID Format: A Description Material ID Depending on the type of transponder, it is possible to modify the length of the MID. Multipage transponder MID can be set from "0" (no MID) to "10" (MID occupies the first 10 pages (writeable)) IMPORTANT Read/write transponder MID corresponds to DATA (writeable) Read/only transponder MID corresponds to DATA (fix) Where used S18F10, S18F11 Please note parameters 42 - 45.
Chapter 7 Operation MIDRA Format: B[1] Material ID acknowledge code 2 Acknowledge, will send MID later in S3F13 Where used S3F12 OFLACK Format: B[1] Acknowledge code for OFF-LINE request. 0 OFF-LINE acknowledge (reader is offline) Where used S1F16 ONLACK Format: B[1] Acknowledge code for ON-LINE request.
Chapter 7 Operation PAGEDATA Format: B[9] The cassette identifier that has been read or will be written. The PAGEDATA corresponds to the value of a transponder page. PAGEDATA [0] Corresponds to the page number. The value of the page number is displayed in the data item "PAGE_ID". PAGEDATA [1] The 8 bytes (one page) of the transponder ID follow. PAGEDATA [8] Where used S3F7, S3F12, S3F13, S3F65 PIN Format: B[1] Information about the status of up to two sensors and the initiator of the message.
Chapter 7 Operation PM Information Description Preventive maintenance information "NE "… Normal execution "MR "… Maintenance required Where used Format: A[2] S18F2, S18F4, S18F8, S18F10, S18F12, S18F14 RAC Format: B[1] Reset acknowledge code 0 1 … … Where used Reset to be done Reset could not be done S2F20 RIC Format: B[1] Reset code 1 2 … … Where used Power-up reset Software reset S2F19 SHEAD Format: B[10] Stored SECS message block header.
Chapter 7 Operation SSACK Format: A[2] Description: Result information on the status of the request concerning the service request. "NO" Normal operation Indicates the success of the requested action. "EE" Execute error Cannot read tag data. Cannot read ID sequence. However, equipment is normal. "CE" 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.
Chapter 7 Operation Format: A[max 18] SSCMD Description: Indicates an action to be performed by the subsystem. Used to differentiate between the different subsystem commands indicated. "ChangeStatus" … CPVAL: "GetStatus" … Get status "Reset" … Reset CIDRW "PerformDiagnostics"… Change status A hardware self test is performed.
Chapter 7 Operation TARGETID Description Format: A[max 4] Identifies where a request for action or data is to be applied. Alternatively, you can use the HeadID. See also reader parameter definitions (data item ECV) parameter 7, 8 and 12. The 4 ASCII character TARGETID is changeable, and defined in parameter 7 and 8 ("ECID_07", "ECID_08"). The 2 ASCII character HeadID is changeable, and defined in parameter 12 ('ECID_12').
Chapter 7 Operation 7.4.6 Parameters No. (dec.) No.
Chapter 7 Operation No. (dec.) Parameter 0 (0x00) No. (hex) Parameter name 37 0x25 MID area 38 0x26 Test after software reset 40 0x28 Transponder load duration (write-mode) 41 0x29 Delay time between read cycles 42 0x2A CarrierIDOffset 43 0x2B CarrierIDLength 44 0x2C FixedMID 46 0x2D MIDFormat 98 0x62 Protocol change allowed 99 0x63 Customer code Gateway ID The gateway ID is a part of the device ID.
Chapter 7 Operation Parameter 2 (0x02) Inter-character timeout T1 1 .. 100 1/10 s Default: (5) 0.5 s Parameter 3 (0x03) Block protocol timeout T2 2 .. 250 1/10 s Default: (10) 1 s Parameter 4 (0x04) Reply timeout T3 1 .. 120 1 s Default: (10) 10 s Parameter 5 (0x05) Inter-block timeout T4 This parameter is ineffective if the used messages are not larger than one block. 1 .. 120 1 s Default: (45) 45 s Parameter 6 (0x06) Retry limit RTY Number of times a question or message is to be repeated. 0 ..
Chapter 7 Operation Parameter 9 (0x09) Heartbeat time The reader offers the option of generating a regular heartbeat. This means the reader sends an S1F1 message to the host at the defined interval. 0 … No heartbeat 1 … 255 10 s (10 s - 2,550 s) Default: 0 no heartbeat Parameter 11 (0x0B) ReaderID 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 ..
Chapter 7 Operation Parameter 23 (0x17) Triggered read frequency If a read/write error occurs, the triggered read frequency defines the time between two attempts to read or write a transponder; or the read frequency if there is a triggered read (no polling). 2 .. 10 from 1/10 s Default: (5) 500 ms Parameter 24 (0x18) r/w max repeat Delay time for sensor signal to start a defined action. 0 ..
Chapter 7 Operation Parameter 29 (0x1D) Transponder load duration (read mode) The time required to load a transponder during a read process. The default value (50 ms) should not be changed. 00 .. 255 ms Default: (50) 50 ms Parameter 30 (0x1E) r/w synchronize Enables/disables reader synchronization. If synchronization is enabled, the reader takes notice of interference or other active readers and synchronizes the reading cycle.
Chapter 7 Operation Parameter 33 (0x21) Automatic antenna adjustment The parameter defines the permitted causes for an antenna adjustment. 0 Automatic adjustment is not activated 1 2 3 Automatic adjustment only by DIP8 Automatic adjustment only by external command Automatic adjustment by DIP8 or external command Default: (3) automatic antenna adjustment by DIP8 or external command Parameter 34 (0x22) Sensor type for presence sensor Type of sensor signal to start an automatic read.
Chapter 7 Operation Parameter 37 (0x25) MID area This parameter defines the range of the MID. '0' … '10' pages Default: '2' - MID area = 2 pages = 16 bytes (depends on parameter 25). IMPORTANT Parameter 38 (0x26) See also parameters 42 - 45 and 99. Test after software reset This parameter enables/disables the initial test after a software reset.
Chapter 7 Operation Parameter 42 (0x2A) 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 the CarrierIDLength. Valid range 0 … maximum bytes of CID -1 Default 0 Offset + Length cannot be larger than the length of the CID field. Parameter 43 (0x2B) CarrierIDLength Defines the length of the CID within the CID field (MID area - parameter 37).
Chapter 7 Operation Parameter 44 (0x2C) FixedMID Defines the read, write and error behavior regarding the 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.
Chapter 7 Operation Parameter 98 (0x62) Protocol change allowed This parameter enables/disables the automatic change between the BROOKS ASCII and SECS protocol. If protocol change is enabled, the reader detects the protocol type on the communication port, and switches to the new protocol type.
Chapter 7 Operation 7.4.7 Introduction SEMI E99 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 increases the interchangeability of a carrier ID reader/writer, so that users and equipment suppliers have a wide choice.
Chapter 7 Operation The table below defines the status of the BROOKS transponder reader. Status Definition ALARM STATUS Displays the presence or absence of alarms. ALARMS An alarm condition exists. BUSY A service is being performed that affects the status of the hardware. CIDRW Super-status of the CIDRW status model. Always active when the CIDRW is powered on. IDLE No service is being performed. All heads are idle. INITIALIZING The CIDRW is carrying out initialization and a self-diagnostic.
Chapter 7 Operation The table below defines the transitions of the BROOKS SECS-I status model of the transponder reader. # Previous state Trigger New status Action Comment 1 Any Power-up or reset INITIALIZING Initialize hardware and software Default entry on power-up 2 INITIALIZING Initialization is complete. RUNNING None The CIDRW is now able to communicate.
Chapter 7 Operation Valid services per status The following table shows which of the various services can be performed by the reader when the reader is in various individual statuses. X X X Change status X Get attributes Read ID X Get status Reset X Perform diag.
Chapter 7 Operation 7.4.8 Equipment status Message details 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/reader or host is online. S1F1 W . * Header only S1F2: ON-LINE DATA (host -> reader) The host signals that it is online.
Chapter 7 Operation S1F17: REQUEST ON_LINE (host -> reader, reply) The reader is requested to change the communication status to online. S1F17 W.*Header only S1F18: ONLINE ACKNOWLEDGE (reader -> host) Acknowledge. S1F18 . 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 .
Chapter 7 Operation S2F16: NEW EQUIPMENT CONSTANT ACKNOWLEDGE (reader -> host) The reader acknowledges the setting of the reader constant. S2F16 . 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 an S1F1 message when the reset is finished. The power-up reset requires a few seconds. S2F19 W . S2F20: RESET ACKNOWLEDGE (reader -> host) The reader acknowledges the reset.
Chapter 7 Operation S3F7: CASSETTE LOST SEND (reader -> host, reply) The reader sends the information that the cassette was removed from the I/O port (presence sensor). This message is sent only if a sensor is connected and activated (see parameters 27 'watchport' and 26 'sensor activity'). The PAGEDATA can be given only if the PAGEDATA that was read last is still available. S3F7 W. * >.
Chapter 7 Operation S3F13: RETURN READ MID (reader -> host, reply) The reader sends the ID of the cassette at the I/O port to the host. S3F13 W >. S3F14: MID ACKNOWLEDGE (host -> reader) The host acknowledges the received data. S3F14 . S3F65: WRITE MID AT I/O PORT (host -> reader, reply) The host requests that the reader write the PAGEDATA.
Chapter 7 Operation S3F73: LOCK MID AT I/O PORT (host -> reader, reply) The host requests the reader to lock the requested page. S3F73 W . ATTENTION Locking a transponder page is permanent. You cannot unlock a transponder page. S3F74: LOCK ACKNOWLEDGE (reader -> host) The reader acknowledges the receipt of the locking command only. The locking acknowledgement is sent later. S3F74 >.
Chapter 7 Operation S5F1: GATEWAY READER ALARM REPORT SEND (reader -> host, reply) The reader reports all errors to the host. S5F1 W * alarm code byte * alarm ID * alarm text >. S5F2: ALARM REPORT ACKNOWLEDGE (host -> reader) The host acknowledges an alarm. S5F2 .Exception handling System errors S9F1: UNRECOGNIZED DEVICE ID (reader -> host) The device ID in the message block header does not correspond to the equipment device ID.
Chapter 7 Operation S9F9: TRANSACTION TIMER TIMEOUT (reader -> host) This message indicates that a transaction timer has timed out and that the corresponding transaction was aborted. Only the last sent message (which must be confirmed by the host) is stored and controlled. S9F9 < B[10] SHEAD > .
Chapter 7 Operation S18F2: READ ATTRIBUTE DATA (RAD) (reader -> host) This message returns the current values of the requested attributes and the current status of the requested component indicated in the TARGETID. S18F2 L,4 1. 2. 3. L,n 1. … n. 4. L,1 L,s 1. … s. If the ATTRID of the S18F1 message is unknown, the corresponding ATTRVAL has the value .
Chapter 7 Operation S18F4: WRITE ATTRIBUTE ACKNOWLEDGE (WAA) (reader -> host) This message acknowledges the success or reports the error of the request to write attribute data to the subsystem indicated in the TARGETID. S18F4 L,3 1. 2. 3. L,1 L,s 1. … s. If the ATTRID of the S18F3 message is unknown, a communication error (CE) occurs. S18F5: READ REQUEST (RR) (host -> reader, reply) The host requests the subsystem indicated in the TARGETID to read information.
Chapter 7 Operation S18F7: WRITE DATA REQUEST (WAR) (host -> reader, reply) This message requests to write data to the subsystem component indicated in the 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 all data in the data area are to be overwritten.
Chapter 7 Operation S18F10: READ ID DATA (RID) (reader -> host) This message returns a requested material identifier MID as read by the subsystem indicated in the TARGETID. S18F10 L,4 1. 2. 3. 4. L,1 L,s 1. … s. S18F11: WRITE ID REQUEST (WIR) (host -> reader, reply) This message is used to request the subsystem indicated by the TARGETID to write the MID. S18F11 W L,2 1. 2.
Chapter 7 Operation S18F12: WRITE ID ACKNOWLEDGE (WIA) (reader -> host) This message acknowledges the success or error of writing the MID to the subsystem indicated in the TARGETID. S18F12 L,3 1. 2. 3. L,1 L,s 1. … s. If the TARGETID is unknown, a communication error (CE) occurs. S18F13: SUBSYSTEM COMMAND REQUEST (SCR) (host -> reader, reply) This message is used to request the subsystem indicated in the TARGETID to perform a specific action. S18F13 W L,3 1.
Chapter 7 Operation 7.4.9 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.
Chapter 7 Operation S1F1 Message from the host to the reader Host to Reader: S1F1 14:04:09 Outgoing: ENQ ( 05 ) 14:04:11 Incoming: EOT ( 04 ) 14:04:11 Outgoing: Length Byte ( 0A ) 14:04:11 Outgoing: Header ( 01 34 81 01 80 01 00 00 00 27 ) 14:04:11 Outgoing: Checksum ( 01 5F ) 14:04:11 Incoming: ACK ( 06 ) Reader to Host: S1F2 14:04:11 14:04:11 14:04:11 14:04:11 14:04:11 14:04:11 14:04:11 14:04:11 14:04:11 Incoming: ENQ ( 05 ) Outgoing: EOT ( 04 ) Incoming: Length Byte ( 1C ) Incoming: Header ( 81 34 01 0
Chapter 7 Operation Message S1F17 puts the reader online Host to Reader: S1F17 10:33:24 Outgoing: ENQ ( 05 ) 10:33:24 Incoming: EOT ( 04 ) 10:33:24 Outgoing: Length byte ( 0A ) 10:33:24 Outgoing: Header ( 01 FF 81 11 80 01 00 00 00 04 ) 10:33:24 Outgoing: Checksum ( 17 02 ) 10:33:24 Incoming: ACK ( 06 ) Reader to Host: S1F18 10:33:24 10:33:24 10:33:24 10:33:24 10:33:24 10:33:24 10:33:24 Incoming: ENQ ( 05 ) Outgoing: EOT ( 04 ) Incoming: Length byte ( 0D ) Incoming: Header ( 81 FF 01 12 80 01 00 00 00 04
Chapter 7 Operation New reader constant sent with S2F15 Host to Reader: S2F15 10:39:32 Outgoing: ENQ ( 05 ) 10:39:32 Incoming: EOT ( 04 ) 10:39:32 Outgoing: Length byte ( 14 ) 10:39:32 Outgoing: Header( 01 FF 82 0F 80 01 00 00 00 07 ) 10:39:32 Outgoing: Data 01 01 01 02 A5 01 14 Parameter 20 A5 01 05 Value 5 10:39:32 Outgoing: Checksum ( 83 02 ) 10:39:32 Incoming: ACK ( 06 ) Reader to Host: S2F16 10:39:32 Incoming: ENQ ( 05 ) 10:39:32 Outgoing: EOT ( 04 ) 10:39:32 Incoming: Length byte ( 0D ) 10:39:32
Chapter 7 Operation Host requests a hardware reset with S2F19 Host to Reader: S2F19 14:18:59 Outgoing: ENQ ( 05 ) 14:18:59 Incoming: EOT ( 04 ) 14:18:59 Outgoing: Length Byte ( 0D ) 14:18:59 Outgoing: Header ( 01 34 82 13 80 01 00 00 00 2F ) 14:18:59 Outgoing: Data ( 21 01 01 ) Hardware reset 14:18:59 Outgoing: Checksum ( 01 9D ) 14:18:59 Incoming: ACK ( 06 ) The reader sends the message S3F5 after the sensor detects a cassette Reader to Host: S3F5 15:51:45 Incoming: ENQ ( 05 ) 15:51:46 Outgoing: EOT ( 0
Chapter 7 Operation The reader sends the message S3F13 after the sensor was detected and the transponder could be read Reader to Host: S3F13 15:51:46 Incoming: ENQ ( 05 ) 15:51:46 Outgoing: EOT ( 04 ) 15:51:46 Incoming: Length byte ( 1A ) 15:51:46 Incoming: Header ( 81 FF 83 0D 80 01 00 03 00 05 ) 15:51:46 Incoming: Data 01 02 21 01 39 Initiator=0, Sensor 0=1 21 09 81 11 11 11 11 10 00 00 00 PAGEDATA 15:51:46 Incoming: Checksum ( 03 F6 ) 15:51:46 Outgoing: ACK ( 06 ) Host to Reader: S3F14 15:51:46 Outg
Chapter 7 Operation Host to Reader: S3F8 15:51:52 15:51:52 15:51:52 15:51:52 15:51:52 15:51:52 15:51:52 Outgoing: ENQ ( 05 ) Incoming: EOT ( 04 ) Outgoing: Length byte ( 0D ) Outgoing: Header ( 01 FF 03 08 80 01 00 03 00 06 ) Outgoing: Data ( 21 01 00 ) ACKC3 Outgoing: Checksum ( B8 01 ) Incoming: ACK ( 06 ) The reader detects an unrecognized device ID and sends the message S9F1.
Chapter 7 Operation The reader detects a wrong stream number and sends the S9F3 message Host to Reader: S4F1 20:03:20 Outgoing: ENQ ( 05 ) 20:03:20 Incoming: EOT ( 04 ) 20:03:20 Outgoing: Length byte ( 0A ) 20:03:20 Outgoing: Header ( 01 FF 84 01 80 01 00 00 00 08 ) 20:03:20 Outgoing: Checksum ( 0E 02 ) 20:03:20 Incoming: ACK ( 06 ) Reader to Host: S9F3 20:03:20 Incoming: ENQ ( 05 ) 20:03:20 Outgoing: EOT ( 04 ) 20:03:20 Incoming: Length byte ( 16 ) 20:03:20 Incoming: Header ( 81 FF 09 03 80 01 00 00 00 09
Chapter 7 Operation The reader detects wrong data and sends the S9F7 message Host to Reader: S2F13 16:49:00 Outgoing: ENQ ( 05 ) 16:49:00 Incoming: EOT ( 04 ) 16:49:00 Outgoing: Length byte ( 0F ) 16:49:00 Outgoing: Header ( 01 FF 82 0D 80 01 00 00 00 36 ) 16:49:00 Outgoing: Data ( 01 01 A5 01 0F ) 16:49:00 Outgoing: Checksum ( 79 02 ) 16:49:00 Incoming: ACK ( 06 ) Reader to Host: S2F14 16:49:00 16:49:00 16:49:00 16:49:00 16:49:00 16:49:00 16:49:00 Incoming: ENQ ( 05 ) Outgoing: EOT ( 04 ) Incoming: Lengt
Chapter 7 Operation Host to Reader: S9F9 20:08:01 20:08:01 20:08:01 20:08:01 20:08:01 20:08:01 20:08:01 20:08:01 Incoming: ENQ ( 05 ) Outgoing: EOT ( 04 ) Incoming: Length byte ( 16 ) Incoming: Header ( 81 FF 09 09 80 01 00 00 00 02 ) Incoming: Data ( 21 0A 81 FF 81 ) Incoming: Data ( 01 80 01 00 00 00 01 ) The stored header Incoming: Checksum ( 04 C3 ) Outgoing: ACK ( 06 ) Host requests reader attributes with S18F1 Host to Reader: S18F1 15:19:31 Outgoing: ENQ ( 05 ) 15:19:31 Incoming: EOT ( 04 ) 15:19
Chapter 7 Operation Reader to Host: S18F2 15:19:31 Incoming: ENQ ( 05 ) 15:19:31 Outgoing: EOT ( 04 ) 15:19:31 Incoming: Length byte ( 44 ) 15:19:31 Incoming: Header ( 81 FF 12 02 80 01 00 00 00 03 ) 15:19:31 Incoming: Data 01 04 41 04 31 32 33 34 TARGETID "1234" 41 02 4E 4F SSACK "NO" 01 04 41 02 30 31 Configuration "01" 41 01 30 Alarmstatus "0" 41 04 49 44 4C 45 OperatingStatus "IDLE" 41 06 53 47 32 53 31 30 SoftwareRevisionLevel "SG2S10" 01 04 ' STATUS 41 02 4E 45 PMInformation "NE" 4
Chapter 7 Operation Host writes new reader attributes with S18F3 Host to Reader: S18F3 15:18:14 Outgoing: ENQ ( 05 ) 15:18:14 Incoming: EOT ( 04 ) 15:18:14 Outgoing: Length Byte ( 8E ) 15:18:14 Outgoing: Header ( 01 34 92 03 80 01 00 00 00 44 ) 15:18:14 Outgoing: Data ( 01 02 41 02 30 31 01 06 01 02 41 0D 43 6F 6E 66 69 67 75 72 61 74 69 6F 6E 41 02 30 31 01 02 41 11 4F 70 65 72 61 74 69 6F 6E 61 6C 53 74 61 74 75 73 41 04 49 44 4C 45 01 02 41 0B 41 6C 61 72 6D 53 74 61 74 75 73 41 01 31 01 02 41 0F 43 61
Chapter 7 Operation Host reads data on page 8 of a multipage transponder with S18F5 Host to Reader: S18F5 17:52:17 Outgoing: ENQ ( 05 ) 17:52:17 Incoming: EOT ( 04 ) 17:52:17 Outgoing: Length byte ( 1A ) 17:52:17 Outgoing: Header ( 01 FF 92 05 80 01 00 00 00 08 ) 17:52:17 Outgoing: Data 01 03 41 04 31 32 33 34 TARGETID "1234" 41 02 30 38 DATASEG "08" A9 02 00 08 DATALENGTH 0x08 17:52:17 Outgoing: Checksum ( 91 02 ) 17:52:17 Incoming: ACK ( 06 ) Reader to Host: S18F6 17:52:17 Incoming: ENQ ( 05 ) 17:5
Chapter 7 Operation Host writes data on page 10 with S18F7 Host to Reader: S18F7 13:14:15 Outgoing: ENQ ( 05 ) 13:14:15 Incoming: EOT ( 04 ) 13:14:15 Outgoing: Length byte ( 24 ) 13:14:15 Outgoing: Header (01 FF 92 07 80 01 00 00 00 18 ) 13:14:15 Outgoing: Data 01 04 41 04 31 32 33 34 TARGETID "1234" 41 02 30 41 DATASEG "0A" A9 02 00 08 DATALENGTH 0x08 41 08 41 42 43 44 45 46 47 48 DATA ABCDEFGH" 13:14:15 Outgoing: Checksum ( 1A 02 ) 13:14:15 Incoming: ACK ( 06 ) Reader to Host: S18F8 13:14:16 Incom
Chapter 7 Operation Host reads the material ID of a multipage transponder with S18F9 Host to Reader: S18F9 14:31:32 Outgoing: ENQ ( 05 ) 14:31:32 Incoming: EOT ( 04 ) 14:31:32 Outgoing: Length byte ( 10 ) 14:31:32 Outgoing: Header ( 01 FF 92 09 80 01 00 00 00 2D ) 14:31:32 Outgoing: Data 41 04 31 32 33 34 TARGETID "1234" 14:31:32 Outgoing: Checksum ( 58 02 ) 14:31:32 Incoming: ACK ( 06 ) Reader to Host: S18F10 14:31:32 Incoming: ENQ ( 05 ) 14:31:32 Outgoing: EOT ( 04 ) 14:31:32 Incoming: Length byte ( 37
Chapter 7 Operation Host writes the material ID of a multipage transponder with S18F11 Host to Reader: S18F11 16:46:22 Outgoing: ENQ ( 05 ) 16:46:22 Incoming: EOT ( 04 ) 16:46:22 Outgoing: Length byte ( 1C ) 16:46:22 Outgoing: Header ( 01 FF 92 0B 80 01 00 00 00 66 ) 16:46:22 Outgoing: Data 01 02 41 04 31 32 33 34 TARGETID "1234" 41 08 4E 72 2E 30 30 41 42 43 MID "Nr.
Chapter 7 Operation Host changes the reader status from IDLE to MANT with S18F13 Host to Reader: S18F13 17:12:29 Outgoing: ENQ ( 05 ) 17:12:29 Incoming: EOT ( 04 ) 17:12:29 Outgoing: Length byte ( 25 ) 17:12:29 Outgoing: Header ( 01 FF 92 0D 80 01 00 00 00 67 ) 17:12:29 Outgoing: Data 01 03 41 04 31 32 33 34 ' TARGETID "1234" 41 0B 43 68 61 6E 67 65 53 74 61 74 65 SSCMD "ChangeStatus" 01 01 41 02 4D 54 CPVAL1 "MT" 17:12:29 Outgoing: Checksum ( 13 02 ) 17:12:29 Incoming: ACK ( 06 ) Reader to Host: S18
Chapter 7 Operation Host requests a reset with S18F13 Host to Reader: S18F13 11:45:34 Outgoing: ENQ ( 05 ) 11:45:34 Incoming: EOT ( 04 ) 11:45:34 Outgoing: Length byte ( 1F ) 11:45:34 Outgoing: Header ( 01 FF 92 0D 80 01 00 00 00 3F ) 11:45:34 Outgoing: Data 01 03 41 04 31 32 33 34 TARGETID "1234" 41 05 52 65 73 65 74 SSCMD "Reset" 01 01 41 02 4D 54 CPVAL1 "MT" 11:45:34 Outgoing: Checksum ( A1 02 ) 11:45:34 Incoming: ACK ( 06 ) Reader to Host: S18F14 11:45:34 Incoming: ENQ ( 05 ) 11:45:34 Outgoing: E
Chapter 7 Operation Host requests the setting of a LED with S18F13 Host to Reader: S18F13 15:37:12 Outgoing: ENQ ( 05 ) 15:37:12 Incoming: EOT ( 04 ) 15:37:12 Outgoing: Length Byte ( 28 ) 15:37:12 Outgoing: Header ( 01 34 92 0D 80 01 00 00 00 46 ) 15:37:12 Outgoing: Data ( 01 03) 41 02 30 31 TargetID "01" 41 06 53 65 74 4C 45 44 SSCMD "SetLED" 01 03 41 05 46 4C 41 53 48 LedState "FLASH" 41 02 31 30 Timeout "10" 41 01 33 ) LEDNo "3" external LED 15:37:12 Outgoing: Checksum ( 07 5C ) 15:37:12 Incom
Chapter 7 Operation Host requests a perform diagnostic with S18F13 the reader has no valid adjustment! Host to Reader: S18F13 15:52:29 Outgoing: ENQ ( 05 ) 15:52:29 Incoming: EOT ( 04 ) 15:52:29 Outgoing: Length Byte ( 26 ) 15:52:29 Outgoing: Header ( 01 34 92 0D 80 01 00 00 00 4A ) 15:52:29 Outgoing: Data ( 01 03 41 02 30 31 41 12 50 65 72 66 6F 72 6D 44 69 61 67 6E 6F 73 74 69 63 73 "PerformDiagnostics" 01 00 ) 15:52:29 Outgoing: Checksum ( 09 EE ) 15:52:29 Incoming: ACK ( 06 ) Reader to Host: S18F14
Chapter 7 Operation Reader to Host: S18F2 15:52:39 Incoming: ENQ ( 05 ) 15:52:39 Outgoing: EOT ( 04 ) 15:52:39 Incoming: Length Byte ( 30 ) 15:52:39 15:52:39 15:52:39 15:52:39 15:52:39 15:52:39 15:52:39 15:52:39 15:52:39 15:52:39 15:52:39 Incoming: Incoming: Incoming: Incoming: Incoming: Incoming: Incoming: Incoming: Incoming: Incoming: Incoming: Header ( 81 34 12 02 80 01 00 00 00 4B ) Data ( 01 04 Data (41 02 30 31) Data (41 02 4E 4F) Data (01 01) Data (41 01 46) "F" Failure Detected Data (01 01 01 0
Chapter 7 Operation Reader to Host: S18F6 13:44:33 Incoming: ENQ ( 05 ) 13:44:33 Outgoing: EOT ( 04 ) 13:44:33 Incoming: Length byte ( 18 ) 13:44:33 Incoming: Header ( 81 FF 12 06 80 01 00 00 00 40 ) 13:44:33 Incoming: Data 01 03 41 04 31 32 33 34 TARGETID "1234" 41 02 43 45 SSACK "CE" 41 00 DATA "" 13:44:33 Incoming: Checksum ( 04 78 ) 13:44:33 Outgoing: ACK ( 06 ) The TARGETID in the S18F5 message does not correspond to the TARGETID in the reader detecting the error.
Chapter 7 Operation Reader to Host: S18F6 17:29:27 Incoming: ENQ ( 05 ) 17:29:27 Outgoing: EOT ( 04 ) 17:29:27 Incoming: Length byte ( 18 ) 17:29:27 Incoming: Header ( 81 FF 12 06 80 01 00 00 00 43 ) 17:29:27 Incoming: Data 01 03 41 04 31 32 33 34 TARGETID "1234" 41 02 54 45 SSACK "TE" 41 00 DATA "" 17:29:27 Incoming: Checksum ( 04 8C ) 17:29:27 Outgoing: ACK ( 06 ) The reader receives a valid S18F5 message.
Chapter 8 Service and Troubleshooting 8 Service and Troubleshooting This chapter gives you an overview of the following topics: ■ General ■ Qualified troubleshooting personnel ■ Safety instructions ■ Error codes ■ Error display with LED ■ Reader does not respond ■ Reset ■ Power cut ■ Software releases ■ Customer service 8.1 General Follow the instructions specified in the safety chapter Follow the general safety information in the chapter Safety Instructions.
Chapter 8 Service and Troubleshooting 8.2 Quali fied tr oubleshoo ting personnel CAUTION Error handling shall be carried out by specially trained personnel only. If you are uncertain about the qualifications that are required, contact the manufacturer. CAUTION Error handling the device without the special skills required and unqualified interference with the device can result in personal injury and damage to the reader and/or connected devices. 8.
Chapter 8 Service and Troubleshooting 8.4 E rro r codes 8.4.
Chapter 8 Service and Troubleshooting ID Name Description Possible cause 7 unconfig the device is not wrong reader address is check syntax of message, check configured sent parameter F „Reader address“ wrong baud rate is set check baud rate of serial interface 8 check (COM port) parity and/or checksum error Correcting action transmission errors on check RS232 cable and connectors, serial communication check disturbing sources at RS232 double or wrong check host communication settings
Chapter 8 Service and Troubleshooting ID Name C (12) bad type Description Possible cause Correcting action incorrect transponder incorrect transponder check transponder type and replace type type is used (read only it or read/write instead of Multipage) * because the device is still busy or because a message has not been confirmed by the previous read up to now 8.4.
Chapter 8 Service and Troubleshooting SSACK Name Description Possible cause Correcting action no readable tag within put a transponder into the antenna the reading range range, verify type and function of the transponder antenna is not check antenna connection connected correctly TE Tag error antenna and check orientation between antenna no transponder or transponder are in a and transponder (see Antenna antenna installed bad orientation installation) antenna is not tuned perform an
Chapter 8 Service and Troubleshooting 8.5 E rro r display with LED 8.5.1 Power LED does not light up Check the power supply and the connection cables! If the LED does not light up, disconnect the device from the power supply and carefully remove the fuse. Test the fuse. If it is defective, replace it with a fuse specified by the manufacturer! If the above measures do not solve the problem, leave the reader disconnected and contact the manufacturer! 8.5.
Chapter 8 Service and Troubleshooting 8.7 Reset In the case of a malfunction, a hardware reset can be performed by switching the power supply off and on! After the reset, the reader performs a self-test. The self test can take up to five seconds. As the first step in these self-tests, all LEDs (Status, Read OK and Read Fail) light up. At the second step, the reader displays the selected protocol type. The read fail LED signalizes the SECS-II protocol. The read ok LED signalizes the ASCII protocol.
Chapter 8 Service and Troubleshooting 8.10 Customer service Brooks Automation (Germany) GmbH RFID Division Gartenstr. 19 D-95490 Mistelgau GERMANY Telephone Fax E-mail +49 (0) 9279 - 991 550 +49 (0) 9279 - 991 501 rfid.support@brooks.
Chapter 9 Dismantling and Storage 9 Dismantling and Storage This chapter gives you an overview of the following topics: ■ Dismantling ■ Storage 9.1 Dismantl ing Remove the power supply device! Remove all cables! Loosen and remove the mounting screws! Remove the device from the installation area! 9.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.
Chapter 10 Transport and Disposal 10 Transport and Disposal This chapter gives you an overview of the following topics: ■ Transport ■ Disposal 1 0 . 1 Tr an sp o r t For transportation purposes such as mailing, use a firm cardboard box. Use adequate padding material to protect the device on all sides. 10.2 Disposal The device and its components are made of various materials. Dispose of these materials separately, and observing the legal regulations of your country.
Chapter 11 Accessories 11 Accessories This chapter gives you an overview of the following topics: ■ Antennas ■ Cables ■ Power supply ■ Mounting adapter plates 11.1 Antennas 11.1.1 Available types . Type Part-No.
Chapter 11 Accessories 11.1.2 Reading and writing ranges ATTENTION If the transponder is very close to the antenna the transponder may be detuned by the metal of the antenna and reading/writing is not possible. We recommend keeping a minimum distance between transponder and antenna of about 10 mm. The following reading/writing ranges are measured with a 32 mm glass transponder (read only, read/write, multipage).
Chapter 11 Accessories Writing range micro antenna Product Manual - RFID Reader LF60C SoliD 160
Chapter 11 Accessories Reading range mini antenna Product Manual - RFID Reader LF60C SoliD 161
Chapter 11 Accessories Writing range mini antenna Product Manual - RFID Reader LF60C SoliD 162
Chapter 11 Accessories Reading range rod antenna Product Manual - RFID Reader LF60C SoliD 163
Chapter 11 Accessories Writing range rod antenna Product Manual - RFID Reader LF60C SoliD 164
Chapter 11 Accessories 11.2 C ables Type Part-No. Power supply cable (cable length: 2,000 mm) KBV24-20-020 RS232 cable (cable length: 2,000 mm) RSK9-20-020 Picture 11.3 P ower supply Type Part-No. Power supply 1.8 A SVG24V-1,8A-020 Picture SVG24V-1,8A-GB-020 SVG24V-1,8A-US-020 Power supply 0.
Chapter 11 Accessories 11.4 M oun ting adapter pl ates No. Part-No.
Index A A - Sensor event 59 ACKC3 81 ACKC5 81 ALARM STATUS 82 ALCD 82 ALID 82 ALTRID 83 ALTX 83 Antenna 32 Antenna port 24 ATTRVAL 85 Automatic tuning 57 B Block transfer protocol 68 C Carrier ID 107 CE conformity 12 Checksum 62, 67 CIDRW 107 CMD 45 Commands of protocol 43 CPVAL 86 D DATA 86 Data 45 DATALENGTH 87 DATASEG 87 DC power 34 Device ID 66 Device label 26 DHCP-Server 36 DIP switches 38 E e - Error message 53 EAC 87 ECID 88 ECV 88 EIA RS-232-C 64 Electronic Industries Association Standards 64 Er
Index G G - Request parameter value 50 H H - Heartbeat 54 High byte 41 HSMS message examples 124 HSMS message format 72 HSMS message format summary 75 HSMS option 69 Humidity 27 I I - Set tuning of the RF module 57 IP address 36 J J - Request tuning 58 L L - Lock a page of the transponder 56 Low byte 41 M MDLN 88 Message 41 Message block structure 66 Message set 79 MF 88 MHEAD 88 Micro antenna 33 MID 89 MIDAC 89 MIDRA 90 Mini antenna 33 N N - Reset 52 No tag 47 NOTAG 48 O OFLACK 90 ONLACK 90 P P - S
Index PAGEDATA 91 Parameter 38, 45 Parameter 0, Gateway ID 97 Parameter 0, Sensor delay 60 Parameter 1, Baudrate 97 Parameter 1, Read mode 60 Parameter 11, ReaderID 99 Parameter 12, HeadID 99 Parameter 2, Inter-character timeout T1 98 Parameter 2, Read page 61 Parameter 20, Sensor delay for presence sensor 99 Parameter 22, Sensor-triggered action for presence sensor 99 Parameter 23, Triggered read frequency 100 Parameter 24, r/w max repeat 100 Parameter 25, Transponder type 100 Parameter 26, Sensor activity
Index Parameter value 45 PIN 91 PM Information 92 Power/RS485 bus connection 24, 34 Prohibition symbols 17 R R - Automatic read 49 RAC 92 Read mode 60 Read page 61 Reader address 62 Reader ID 46 Relative humidity 27 Remote I/O 37 Remote I/O port 23 Response code 46 RIC 92 RJ45 35 Rod antenna 32 RS232 35 RS232 max repeat 61 RS232 port 23 RS232 repeat time 61 S Safety Instructions 16 Safety symbols 16 SECS-I 64 SECS-I message examples 124 SECS-II 64, 76 SEMI E99 107 SEMI Equipment Communication Standard 76
Index W W - Write data 48 Warning symbols 17 Warranty 14 Watchport 61 X X - Read data 47
