User's Manual

ManualsBrandsBrooks Automation ManualsElectronicsInductive TAG System

Page 1 of 91

2000-09-29

Release: 0.3

ID: ID000093

*** Draft ***

RS232

Transponder Reader

(SEMI SECS-1-

Protocol)

Technical Reports

Summary of content (91 pages)

PAGE 1
Page 1 of 91 2000-09-29 Release: 0.
PAGE 2
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 2 of 91 2000-09-29 ID: ID000093 1 SYSTEM DESCRIPTION.......................................................................................5 2 IMPORTANT NOTES:............................................................................................6 3 HARDWARE ..............................................................................................................7 3.1 3.2 3.3 CONSTRUCTION ....................................
PAGE 3
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 3 of 91 2000-09-29 ID: ID000093 7.2 7.3 7.4 8 PLUGS OF RS232-INTERFACE............................................................................ 33 PLUGS OF THE EXTERNAL SENSOR/A CTOR ..................................................... 33 POWER SUPPLY.................................................................................................... 33 INTRODUCTION......................................................................
PAGE 4
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 4 of 91 2000-09-29 ID: ID000093 9.3.12 S3F67: RETURN WRITE SUCCESS ( reader -> host, reply ).............................. 73 9.3.13 S3F68: WRITE SUCCESS ACKNOWLEDGE ( host -> reader) ............................ 73 9.3.14 S3F73: LOCK MID AT I/O PORT ( host -> reader, reply ).................................. 73 9.3.15 S3F74: LOCK ACKNOWLEDGE ( reader -> host )........................................... 73 9.3.
PAGE 5
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 5 of 91 2000-09-29 ID: ID000093 1 System Description The HERMOS Transponder Reader System is a high frequency identification system using the FM-transmission. The basic item is a transponder working as a forgery-proof electronic identity disc. The reading unit of the system sends an energy impulse via the antenna. The capacitor of the passive, battery-less transponder is charged by this impulse.
PAGE 6
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 6 of 91 2000-09-29 ID: ID000093 2 Important Notes: 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.
PAGE 7
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 7 of 91 2000-09-29 ID: ID000093 3 Hardware 3.1 Construction External input Plug for antenna External output Tuning LED’s HF-module Reset button Prog.
PAGE 8
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 8 of 91 2000-09-29 ID: ID000093 The power LED signalizes whether 5V are existing on the board. The HF-module is the analog part of the device. It triggers the antenna and transmits the received data to the controller. The 6 tuning LED’s show the switch status of the adjustment-relays (only valid if automatic tuning integrated).
PAGE 9
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 9 of 91 2000-09-29 ID: ID000093 3.2 Standard-Housing Fixing holes (4xØ4,2mm) space for plugs * space for plugs * * Keep space free for plugs. Dimensions for straight cable plugs. Angled cable plugs decrease space RS232Interface Connectors for ext. input antenna Connector for power ext.
PAGE 10
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 10 of 91 2000-09-29 ID: ID000093 3.3 3.3.
PAGE 11
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 11 of 91 2000-09-29 ID: ID000093 Power LED: The LED lights after the device had been connected to the power supply. Tuning pushbutton: The automatic calibration is carried out after pushing the button which can be reached by a drilled hole at the side of the housing (only valid if automatic tuning integrated).
PAGE 12
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 12 of 91 2000-09-29 ID: ID000093 3.3.
PAGE 13
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 13 of 91 2000-09-29 ID: ID000093 Power - LED: If the device is connected to a power supply, the LED lights green and the reader is ready for use. Tuning / LED: The antenna’s efficiency is optimized by pushing the automatic calibration key. The LED lights up red during the calibration process and subsequently goes out when the tuning had been successful.
PAGE 14
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 14 of 91 2000-09-29 ID: ID000093 Test / LED: The test mode serves for the checking of the most important reader features, the reading respectively the writing, which are operated by pushing the corresponding key in polling mode. If the device is in test mode, this is signalised by the test - LED. The test-key has to be pushed again to leave the mode.
PAGE 15
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 15 of 91 2000-09-29 ID: ID000093 3.
PAGE 16
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 16 of 91 2000-09-29 ID: ID000093 Sub-D female plug The serial interface is also carried out with the Sub-D female plug (9 contacts), a serial connection line (switched 1:1) can be used.
PAGE 17
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 17 of 91 2000-09-29 ID: ID000093 Ext. Input Pin Signal 1 GND Sensor Type: NPN GND 2 +24V + 24V DC 3 IN npn Output Q floating contact positive logic Antenna Pin Signal 1 Antenna “+” 2 Antenna “-“ 3 NC Ext. Output Pin Signal 1 +5V 2 OUT LED The ext. output is dimensioned for connecting a LED (without resistor).
PAGE 18
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 18 of 91 2000-09-29 ID: ID000093 3.5 Antenna 3.5.1 Rod Antenna b1 a1 a2 a1 a2 b1 3.5.2 length of antenna cylinder complete mounting dimensions (cable with 90° angle) diameter of antenna cylinder 125mm 150mm 23.0mm Mini Antenna b1 a1 a2 a1 a2 b1 length of antenna cylinder complete mounting dimensions (cable with 90° angle) diameter of antenna cylinder 68mm 85mm 10.
PAGE 19
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 19 of 91 2000-09-29 ID: ID000093 3.5.3 Micro Antenna a2 a1 b1 a1 a2 b1 length of antenna cylinder complete mounting dimensions (cable with 90° angle) diameter of antenna cylinder 40mm 60mm 10.
PAGE 20
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 20 of 91 2000-09-29 ID: ID000093 3.5.
PAGE 21
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 21 of 91 2000-09-29 ID: ID000093 3.6 3.6.1 Technical Data Antenna Cable Cable of Rod Antenna and Frame Antenna diameter : 5,5mm bending radius: 15 x diameter, only once 6 x diameter material: PVC 3.6.2 Cable of Mini Antenna and Micro Antenna diameter : 4,1mm bending radius: 20 x diameter, only once 5 x diameter material: PVC 3.
PAGE 22
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 22 of 91 2000-09-29 ID: ID000093 3.8 Power Supply and Current Input Description Voltage (proof against connecting to the wrong terminal) Current with/without presence sensor (starting process excluded) Reading/writing impulse rod antenna without/with presence sensor micro antenna without/with presence sensor 3.
PAGE 23
RS232-Transponder Reader (SECS1-Protocol), Release 0.
PAGE 24
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 24 of 91 2000-09-29 ID: ID000093 5 Warranty and Liability The warranty period is 6 months and starts with the moment of the delivery of the device which has to be proved by invoice or other documents. The warranty includes the repair of all damages of the device, occurring within the warranty period, which are evidently caused by faults of the material or productional defects.
PAGE 25
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 25 of 91 2000-09-29 ID: ID000093 6 Reading and Writing Ranges These diagrams have been taken at optimal conditions. 6.
PAGE 26
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 26 of 91 2000-09-29 ID: ID000093 6.
PAGE 27
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 27 of 91 2000-09-29 ID: ID000093 6.
PAGE 28
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 28 of 91 2000-09-29 ID: ID000093 6.
PAGE 29
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 29 of 91 2000-09-29 ID: ID000093 6.
PAGE 30
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 30 of 91 2000-09-29 ID: ID000093 6.
PAGE 31
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 31 of 91 2000-09-29 ID: ID000093 6.
PAGE 32
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 32 of 91 2000-09-29 ID: ID000093 6.
PAGE 33
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 33 of 91 2000-09-29 ID: ID000093 7 Accessories 7.1 Plugs / Cabling of Power • • • 7.2 • 7.3 • • • 7.4 • Female plug, straight : Female plug, angled : Current connector with two cores : KBV-GK KBV-WK KBV24 Plugs of RS232-Interface Shielded male plug, straight : KSRS-GM Plugs of the External Sensor/Actor Cable plug, ext. sensor, metal : Cable plug, ext.
PAGE 34
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 34 of 91 2000-09-29 ID: ID000093 8 Introduction The SECS-1 standard defines a communication interface suitable for the exchange of messages between semiconductor processing equipment and a host. A host is a computer or network of computers which exchanges information with the equipment to accomplish manufacturing. The standard does not define the data contained within a message.
PAGE 35
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 35 of 91 2000-09-29 ID: ID000093 8.1 SECS-1 Implementation This message set describes the communication between a SECS-1 reader and a host. The communication between the host and the transponder-reader happens via a RS232 interface (SECS-1). 8.1.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.
PAGE 36
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 36 of 91 2000-09-29 ID: ID000093 3.
PAGE 37
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 37 of 91 2000-09-29 ID: ID000093 Upper Device-ID Lower Device-ID R Not used 0x01 serial number of the reader Direction reader to host: Direction Host to equipment (HERMOS SECS-1 Reader): 0x81xx * 0x01xx * * … the serial number is on a sticker on the cap of each reader The W-Bit is used to indicate that the sender of a primary message expects a reply. A value of one in the W-bit means that a reply is expected.
PAGE 38
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 38 of 91 2000-09-29 ID: ID000093 4. Block Transfer Protocol The drawing below illustrates some simple message interactions between the host and the equipment. The figure shows the handshake sequence possible to acquire the status of the equipment.
PAGE 39
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 39 of 91 2000-09-29 ID: ID000093 When both the host and the equipment try to send at the same time, the host must cancel its inquiry because the host works in slave mode. First he has to receive the equipment message because the reader is the master. Only now the host is allowed to send his message. For more detailed information about all possible cases see SEMI E4-0997.
PAGE 40
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 40 of 91 2000-09-29 ID: ID000093 8.2 8.2.1 SECS-2 Implementation Introduction The SEMI Equipment Communication Standard Part 2 (SECS-2) defines the details of the interpretation of messages exchanged between intelligent equipment and a host. It is the intent of this standard to be fully compatible with SEMI Equipment Communication Standard E4 (SECS-1).
PAGE 41
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 41 of 91 2000-09-29 ID: ID000093 Byte Name Description 0 Format and number of the length-bytes The data format is coded in the upper 6 bits. The two less significant bits determine the number of the following length -bytes. 1 1-2 1-3 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.
PAGE 42
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 42 of 91 2000-09-29 ID: ID000093 8.2.
PAGE 43
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 43 of 91 2000-09-29 ID: ID000093 8.2.3 Message set The SECSII-message-set used by the HERMOS SECS-1 reader consist of 6 different stream types.
PAGE 44
RS232-Transponder Reader (SECS1-Protocol), Release 0.
PAGE 45
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 45 of 91 2000-09-29 ID: ID000093 8.2.4 Data Item Dictionary This section defines the data items used in the standard SECS-2 messages described in the section “Message Details”. Syntax: Name: A unique name for this data item. This name is used in the message definitions. Format: The allowable item format code which can be used for this standard data item. Item format codes are shown in hex and octal, as described inchapter 1.2.
PAGE 46
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 46 of 91 2000-09-29 ID: ID000093 8.2.5 Data Item Dictionary: ACKC3 Format: B[1] Acknowledge Code 0 1 >1 : : : Where used: Sensor 0 was the initiator Sensor 1 was the initiator error, not accepted S3F6, S3F8 ACKC5 Format: B[1] Acknowledge Code 0 >0 : : Where used: no error error, not accepted S5F2 ALCD Format: B[1] Alarm Code Byte. Only the occurring of a failure is told. Failures will not be reset on principle.
PAGE 47
RS232-Transponder Reader (SECS1-Protocol), Release 0.
PAGE 48
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 48 of 91 2000-09-29 ID: ID000093 ALTX[1] “0”: “1”: “E”: “F”: State of sensor 0 Sensor not occupied Sensor is occupied Sensors tate is not available Sensor not defined ALTX[2] “0”: “1”: “E”: “F”: State of sensor 1 Sensor not occupied Sensor is occupied Sensorstate is not available Sensor not defined ALTX[3] ‘:’ a colon separates the alarm text from the sensor states Where used: S5F1 ATTRID Description: type of object.
PAGE 49
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 49 of 91 2000-09-29 ID: ID000093 ATTRVAL Description: Format: A[max4] Value of the specified attribute.
PAGE 50
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 50 of 91 2000-09-29 ID: ID000093 DATA Format: A[max8] Description: A vector or string of unformatted data. The first page (page 1) of each transponder contains the MID.
PAGE 51
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 51 of 91 2000-09-29 ID: ID000093 EAC Format: B[1] Acknowledge code for new reader constant 0: 1: parameter set successfully parameter could not be set Where used: S2F16 ECID Format U1[1] Parameter number of reader (look data item ECV) Where used: ECV S2F13, S2F15 Format U1[1] Reader parameters definition. The values here are shown as decimal-values! Parameters : Parameter 0: Gateway-ID The gateway-ID is a part of the device-ID.
PAGE 52
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 52 of 91 2000-09-29 ID: ID000093 Parameter 1: Baudrate Data transmission rate to the SECS-Host 3: 300 Baud 6: 600 Baud 12: 1200 Baud 24: 2400 Baud 48: 4800 Baud 96: 9600 Baud 192: 19200 Baud 200: 38400 Baud 201: 57600 Baud 202: 115200 Baud default: (200) 38400 Baud (look covering letter of the reader) Parameter 2: Inter-Character-Timeout T1 1 .. 100 1/10s default: (5) 0.5s Parameter 3 : Block-Protocol-Timeout T2 2 ..
PAGE 53
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 53 of 91 2000-09-29 ID: ID000093 Parameter 21: not defined! Parameter 22: sensor triggered action for sensor 0 and sensor 1 0 : read all transponders 1 : read the page 1 of a multipage-transponder ...
PAGE 54
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 54 of 91 2000-09-29 ID: ID000093 Parameter 28: transmitter-level The intensity of field strength to load a transponder. The default value (1) should not change! 0 reduced field strength 1 maximum field strength default: (1) maximum field strength Parameter 29: transponder load duration The used time to load a transponder. The default value (50ms) should not change! 00 ..
PAGE 55
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 55 of 91 2000-09-29 ID: ID000093 MF Format: B[1] Material format code. 20: The material port number corresponds to the sensor number and state Where used: S3F5, S3F7 MHEAD Format: B[10] SECS Message Block Header associated with message block in error. Where used: S9F1, S9F3, S9F5, S9F7, S9F9 MID Format: A[max16] Description: Material ID.
PAGE 56
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 56 of 91 2000-09-29 ID: ID000093 MIDAC Format: B[1] Acknowledge Code 0 1 2 >2 : material-ID acknowledged; the sensor 0 was the initiator : not defined : material-ID acknowledged - reaction on externally triggered action; the message cannot be related to any sensor : material-ID not acknowledged The initiator can be determined from the data item Portnumber PTN.
PAGE 57
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 57 of 91 2000-09-29 ID: ID000093 OFLACK Format: B[1] Acknowledge code for offline request. 0: gateway is offline Where used: S1F16 ONLACK Format: B[1] Acknowledge code for online request.
PAGE 58
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 58 of 91 2000-09-29 ID: ID000093 PAGEDATA Format: B[9] The cassette identifier that has been read or shall be written. The PAGEDATA corresponds to the value of a transponder page. PAGEDATA [0] corresponds to the page number. The values of the page number (MID[0]) are shown in the data item “PAGE_ID”. PAGEDATA [1] – the 8 byte (one page) of the transponder-ID are following.
PAGE 59
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 59 of 91 2000-09-29 ID: ID000093 Initiator: bit6 – bit7 The initiator represents the number of the sensor which has caused the generation of a message 0 Sensor 0 1 Sensor 1 (not realized at present) 3 cannot be assigned Where used: S3F5, S3F7, S3F12, S3F13, S3F67 RAC Format: B[1] Reset acknowledge code. 0: 1: reset to be done reset could not be done Where used: S2F20 RIC Format: B[1] Reset code.
PAGE 60
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 60 of 91 2000-09-29 ID: ID000093 SSACK Format: A[2] Description: “NO” “EE” “CE” “HE” “TE” Where used: Indicates the success or failure of a requested action. … … … … … normal operation execute error communication error hardware error tag error S18F2, S18F4, S18F6, S18F8, S18F10, S18F12, S18F14 SSCMD Format: A[max18] Description: Indicates an action to be performed by the subsystem.
PAGE 61
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 61 of 91 2000-09-29 ID: ID000093 TARGETID Format: A[max10] Description: Identifies where a request for action or data is to be applied. The text conforms to OBJSPEC.
PAGE 62
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 62 of 91 2000-09-29 ID: ID000093 8.3 SEMI E99-0600 8.3.1 Introduction The purpose of the Carrier ID Read/Writer Functional Standard effort 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 interchangeability of Carrier ID Reader/Writer so that users and equipment suppliers have a wide range of choices. Scope: 1.
PAGE 63
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 63 of 91 2000-09-29 ID: ID000093 8.3.2 State Models To facilitate independent control of the individual heads, there are two separate state models defined, one for CIDRW subsystem and one for each individual head. The HERMOS SECS-1 reader combines the CIDRW subsystem and the head together. The state model for the HERMOS reader is shown in the state model.
PAGE 64
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 64 of 91 2000-09-29 ID: ID000093 The shown table defines the states of the HERMOS SECS-1 transponder reader. State ALARM STATUS ALARMS BUSY CIDWR IDLE INITIALIZING NO ALARMS OPERATING OPERATIONAL STATUS RUNNING MAINTENANCE Definition Shows the presence or absence of alarms. An alarm condition exists. A service is being performed that affects the state of the hardware Superstate of CIDRW state model. Always active when CIDRW powered on.
PAGE 65
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 65 of 91 2000-09-29 ID: ID000093 The shown table defines the transitions of the HERMOS SECS-1 transponder reader state model. # Previous State 1 Any 2 INITIALIZING 3 4 5 IDLE 7 MAINTENANCE 8 INITIALIZING 10 11 Powerup or reset Initialization is complete Default entry into INITIALIZING OPERATING A service request to read or write or IDLE perform diagnostic is received.
PAGE 66
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 66 of 91 2000-09-29 ID: ID000093 9 MESSAGE DETAILS 9.1 Equipment status 9.1.1 S1F0: ABORT TRANSACTION (reader <-> host) Used in lieu 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 9.1.2 S1F1: ARE YOU THERE REQUEST ( reader <-> host, reply ) Establishes if the gateway or host is online. S1F1 W . * Header Only 9.1.
PAGE 67
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 67 of 91 2000-09-29 ID: ID000093 9.1.6 S1F16: OFFLINE ACKNOWLEDGE ( reader -> host ) Acknowledge. S1F16 . 9.1.7 S1F17: REQUEST ON_LINE ( host ->reader, reply ) The reader should change the communication state to online. S1F17 W. *Header Only 9.1.8 S1F18: ONLINE ACKNOWLEDGE ( reader -> host ) Acknowledge. S1F18 .
PAGE 68
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 68 of 91 2000-09-29 ID: ID000093 9.2 9.2.1 Equipment Control S2F0: ABORT TRANSACTION (reader <-> host) Used in lieu 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 9.2.2 S2F13: EQUIPMENT CONSTANT REQUEST (host-> reader , reply) The host requests one constant from the gateway or reader. S2F13 W >. 9.2.
PAGE 69
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 69 of 91 2000-09-29 ID: ID000093 9.2.5 S2F16: NEW EQUIPMENT CONSTANT ACKNOWLEDGE (reader -> host ) The reader acknowledges the new host constant. S2F16 . 9.2.6 S2F19: RESET SEND ( host -> reader, reply ) The host requests the reader to reset the hard- and software. In both cases there will be a communication inquiry with S1F1. The powerup reset requires a few seconds. S2F19 W . 9.2.
PAGE 70
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 70 of 91 2000-09-29 ID: ID000093 9.3 9.3.1 Material Status S3F0: ABORT TRANSACTION (reader <-> host) Used in lieu of an expected reply to abort a transaction. Function 0 is defined in every stream and has the same meaning in every stream. S3F0 W . * Header Only 9.3.2 S3F5: CASSETTE FOUND SEND ( reader -> host, reply ) The reader sends the information that a cassette was detected by the sensor.
PAGE 71
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 71 of 91 2000-09-29 ID: ID000093 9.3.4 S3F7: CASSETTE LOST SEND ( reader -> host, reply ) The reader sends the information that the cassette was removed from I/O port (sensor). This message will only be sent, if a sensor is connected and activated (see ‘watchport’ and ‘sensor activity’). The PAGEDATA can only be given, if the PAGEDATA read at last is still known. S3F7 W.
PAGE 72
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 72 of 91 2000-09-29 ID: ID000093 9.3.7 S3F12: READ ACKNOWLEDGE ( reader -> host ) The reader only acknowledges the receipt of the reading command. The reading ID will be sent later! S3F12 * a zero-length PTN indicates that no PTN is available * a zero-length PAGEDATA indicates that no DATA is available >. 9.3.
PAGE 73
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 73 of 91 2000-09-29 ID: ID000093 9.3.11 S3F66: WRITE ACKNOWLEDGE ( reader -> host ) The reader only acknowledges the receipt of the writing command. The writing acknowledge will be sent later! S3F66 >. 9.3.12 S3F67: RETURN WRITE SUCCESS ( reader -> host, reply ) The reader reports the successful writing of the transponder. The reader sends information about sensor 0. S3F67 W . 9.3.
PAGE 74
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 74 of 91 2000-09-29 ID: ID000093 9.3.16 S3F75: RETURN LOCK SUCCESS ( reader -> host, reply ) The reader reports the successful writing of the transponder. The reader sends information about sensor 0. S3F75 W . 9.3.17 S3F76: LOCK SUCCESS ACKNOWLEDGE ( host -> reader) The host acknowledges the received lock success message (S3F67). S3F76 .
PAGE 75
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 75 of 91 2000-09-29 ID: ID000093 9.4 9.4.1 Exception Handling S5F0: ABORT TRANSACTION (reader <-> host) Used in lieu of an expected reply to abort a transaction. Function 0 is defined in every stream and has the same meaning in every stream. S5F0 W . * Header Only 9.4.2 S5F1: GATEWAY READER ALARM REPORT SEND (reader -> host, reply ) The reader reports all errors to the host. S5F1 W >.
PAGE 76
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 76 of 91 2000-09-29 ID: ID000093 9.5 9.5.1 System Errors S9F1: UNRECOGNIZED DEVICE ID ( reader -> host ) The device-ID in the message block header did not correspond to the equipment device ID’s. S9F1 . 9.5.2 S9F3: UNRECOGNIZED STREAM TYPE (reader -> host ) The reader does not recognize the stream type in the message block header. S9F3 . 9.5.
PAGE 77
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 77 of 91 2000-09-29 ID: ID000093 9.6 9.6.1 Subsystem Control and Data S18F1: READ ATTRIBUTE REQUEST (RAR) (host -> reader, reply) This message requests the current values of specified attributes of the subsystem component indicated in TARGETID. S18F1 W L,2 1. A,8 2. L,n 1. … n. If n=0 then all attributes of the target component are requested. 9.6.
PAGE 78
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 78 of 91 2000-09-29 ID: ID000093 9.6.3 S18F3: WRITE ATTRIBUTE REQUEST (WAR) (host -> reader, reply) This message reques ts the subsystem to set the value of read/write attributes of the component specified in TARGETID. S18F3 ,W L,2 1. A,8 2. L,n 1. L,2 1. 2. … n. L,2 1. 2. 9.6.
PAGE 79
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 79 of 91 2000-09-29 ID: ID000093 9.6.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. A,8 2. A,2 3.
PAGE 80
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 80 of 91 2000-09-29 ID: ID000093 If DATASEG and DATALENGTH are both omitted (zero length items) then all data is to be overwritten. If only DATALENGTH is omitted or if DATALENGTH has a value of zero, then all data within the indicated section are to be written. 9.6.8 S18F8: WRITE DATA ACKNOWLEDGE (WDA) (reader -> host) This message acknowledges the success or failure of writing data to the subsystem indicated in TARGETID. S18F8 L,3 1.
PAGE 81
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 81 of 91 2000-09-29 ID: ID000093 9.6.11 S18F11: WRITE ID REQUEST (WIR) (host -> reader, reply) This message is used to request the subsystem indicated by TARGETID to write an identifier. S18F11 W L,2 1. A,8 2. A,8 9.6.12 S18F12: WRITE ID ACKNOWLEDGE (WIA) (reader -> host) This message acknowledges the success or failure of writing the ID to the subsystem indicated in TARGETID. S18F12 L,3 1. A,8 2.
PAGE 82
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 82 of 91 2000-09-29 ID: ID000093 9.6.14 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. A,8 2. A,2 3. L,s 1. … t. s=0 if and only if TARGETID is unknown.
PAGE 83
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 83 of 91 2000-09-29 ID: ID000093 10 SECS-1 MESSAGE EXAMPLES All examples are produced with the default gateway-ID 255 (decimal) or 0x00FF (hexadecimal) ! 1.
PAGE 84
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 84 of 91 2000-09-29 ID: ID000093 3.
PAGE 85
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 85 of 91 2000-09-29 ID: ID000093 5.
PAGE 86
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 86 of 91 2000-09-29 ID: ID000093 Reader to Host: S2F16 17:41:53 Incoming: ENQ ( 05 ) 17:41:53 Outgoing: EOT ( 04 ) 17:41:54 Incoming: Length Byte ( 0D ) 17:41:54 Incoming: Header ( 81 FF 02 10 80 01 00 00 00 0C ) 17:41:54 Incoming: Data ( 21 01 00 ) => setting was successful 17:41:54 Incoming: Checksum ( 02 41 ) 17:41:54 Outgoing: ACK ( 06 ) The Host sets the reader2 parameter „7“ (watchport) with the value „3“.
PAGE 87
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 87 of 91 2000-09-29 ID: ID000093 Host to Reader: S3F6 19:39:15 Outgoing: ENQ ( 05 ) 19:39:15 Incoming: EOT ( 04 ) 19:39:15 Outgoing: Length Byte ( 0D ) 19:39:15 Outgoing: Header ( 01 FF 03 06 80 01 00 01 00 09 ) 19:39:15 Outgoing: Data ( 21 01 01 ) ->Sensor 1 Acknowledge 19:39:15 Outgoing: Checksum ( B7 01 ) 19:39:15 Incoming: ACK ( 06 ) 9.
PAGE 88
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 88 of 91 2000-09-29 ID: ID000093 10. The reader sends the message S3F7 after the cassette was removed from the sensor.
PAGE 89
RS232-Transponder Reader (SECS1-Protocol), Release 0.
PAGE 90
RS232-Transponder Reader (SECS1-Protocol), Release 0.3 Draft Page 90 of 91 2000-09-29 ID: ID000093 13. The reader detects an unrecognized function and sends the message S9F5.
PAGE 91
RS232-Transponder Reader (SECS1-Protocol), Release 0.