Omron 6CYCIDV6400202 Carrier ID Reader/Writer User Manual USERS MANUAL FOR V640

Omron Corporation Carrier ID Reader/Writer USERS MANUAL FOR V640

USERS MANUAL FOR V640

SECTION 4Reading from/Writing to ID Tags63CIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsWhen SECS is Used 64When SECS is Not Used 74

64SECTION 4When SECS is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsWhen SECS is UsedThe SEMI standards are subject to revision: you must refer to the actual standards.• SEMI E99 THE CARRIER ID READER/WRITER FUNCTIONAL STANDARD• SEMI E5 EQUIPMENT COMMUNICATION STANDARD 2 MESSAGE CONTENT (SECS II)• SEMI E4 EQUIPMENT COMMUNICATION STANDARD 1 MESSAGE TRANSFER (SECS I)SECS Protocol Specifications Refer to page 113.Message SpecificationsList of Error Messages Refer to page 84.List of Messages UsedClassification S F Direction SECS II names SeeGeneral purpose messages11 S,H→E,reply Are You There Request p.6612 S,H←E On Line Data p.66CIDRW system messages18 1 S,H→E,reply Read Attribute Request p.6618 2 S,H←E Read Attribute Data p.6618 3 S,H→E,reply Write Attribute Request p.6718 4 S,H←E Write Attribute Acknowledge p.6718 5 S,H→E,reply Read Request p.6818 6 S,H←E Read Data p.6818 7 S,H→E,reply Write Request p.6918 8 S,H←E Write Acknowledge p.6918 9 S,H→E,reply Read ID Request p.6918 10 S,H←E Read ID Data p.6918 11 S,H→E,reply Write ID Request p.7018 12 S,H←E Write ID Acknowledge p.7018 13 S,H→E,reply Subsystem Command Request p.7018 14 S,H←E Subsystem Command Acknowledge p.70Data Item DictionarySECS II data items Name Format ValueATTRID Attribute ID 20 Attribute nameATTRVAL Attribute value 20 Attribute valueMID Carrier ID 20 All characters 00H-0FFHDATA Data 20 All characters 00H-0FFHDATALENGTH DataSize 52 Data Segment Area Refer to page 48.DATASEG DataSeg 20STATUS PM information 20 "NE": Normally executedSSACK Result status 20 "NO": Normal"EE": Execution error *3"CE": Communications error"HE": Hardware error *3"TE": Tag error *3

65CIDRW SystemUser’s ManualSECTION 4When SECS is UsedSECTION 4Reading from/Writing to ID Tags*1: "PS" is an expansion command for this unit.*2: When the TARGET ID is "00" (CIDRW), this is a zero length item.*3: "EE," "HE," and "TE" are used only with S18F6, S18F8, S18F10, and S18F12.S9F7 responsesAn S9F7 response is given when a message in an illegal format is received from the host device."Illegal format" here means that there is a problem with the message composition, such as illegal attributes, or insuffi-cient or too many items. If other problems relating to the item contents arise, the response is SSACK = "CE" (commu-nications error).List of STATUS Status L,41.<PMInformation>2.<AlarmStatus>3.<OperationalStatus>4.<HeadStatus> *2The STATUS values are included in the PM infor-mation.CPVAL State request 20 "OP", "MT", "PS" *1TARGETID Target ID 20 "00"-"31""00" indicates the CIDRW Controller itself.SSCMD Subsystem com-mands20 "ChangeState""GetStatus""PerformDiagnostics""Reset"Data Item DictionarySECS II data items Name Format Value

66SECTION 4When SECS is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsSpecifications for Each Stream/Function• Online check• Get attributes S1,F1 Are You There Request S,H→E,replyHeader onlyS1,F2 On Line Data S,H←EL,21.<MDLN>2.<SOFTREV>• Set MDLN (model number).• Set SOFTREV (software revision level).S18,F1 Read Attribute Request S,H→E,replyL,21.<TARGETID> "00"-"31"2.L,n1.<ATTRID1> ⋅ n.<ATTRIDn>• The setting for reading all attributes (CIDRW Controller or heads) is n = 0.S18,F2 Read Attribute Data S,H←EL,41.<TARGETID> "00"-"31"2.<SSACK>3.L,n1.<ATTRVAL1> ⋅ n.<ATTRVALn>4.L,s1.<STATUS1> ⋅ s.<STATUSs>• The order of the attribute data corresponds to the attribute ID specified by S18, F1.When reading of all attributes is specified, unsupported attribute items (ATTRVAL) are omitted.• When the specified target is invalid:n = 0, s = 0, SSACK = "CE" communications error• When one or more undefined attributes are included:n = 0, s = 0, SSACK = "CE" communications error• When head attributes are specified with TARGET = "00" or CIDRW Controller attributes are specified with TARGET <> "00":n = 0, s = 0, SSACK = "CE" communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.

67CIDRW SystemUser’s ManualSECTION 4When SECS is UsedSECTION 4Reading from/Writing to ID Tags• Set attributesF18,F3 Write Attribute Request S,H→E,replyL,21.<TARGETID> "00" (fixed)2.L,n1.L,21.<ATTRID1>2.<ATTRVAL1>n.L,21.<ATTRIDn>2,<ATTRVALn>Since the attributes for heads are all RO in this system, the target ID is fixed as "00".S18,F4 Write Attribute Acknowledge S,H←EL,31.<TARGETID> "00" (fixed)2.<SSACK>3.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, SSACK = "CE" communications error• When one or more undefined attributes or RO attributes are included:s = 0, SSACK = "CE" communications error• When illegal attribute data is specified:s = 0, SSACK = "CE" communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.

68SECTION 4When SECS is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID Tags•Read dataData Segment Area Refer to page 111.S18,F5 Read Request S,H→E,replyL,31.<TARGETID> "01"-"31"2.<DATASEG>3.<DATALENGTH>• When the data of all segments is batch read, both DATASEG and DATALENGTH are omitted (they are zero length items).• When all the data for a particular segment is read, DATALENGTH is omitted (it is a zero length item).• When DATASEG and DATALENGTH are specified, it is not permissible to specify a DATALENGTH that exceeds the maxi-mum length of the relevant DATASEG.• If a DATALENGTH that is under the set length for DATASEG is specified, only the data corresponding to the specified DATALENGTH is read.S18,F6 Read Data S,H→E,replyL,41.<TARGETID> "01"-"31"2.<SSACK>3.<DATA>4.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:DATA item length = 0, s = 0, SSACK = "CE" communications error• When an undefined DATASEG is specified, or the DATALENGTH is illegal:DATA item length = 0, s = 0,SSACK = "CE" communications error• When reading of all segment data is specified in a system where the data segment is not defined:DATA length = 0, SSACK = "NO"• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.

69CIDRW SystemUser’s ManualSECTION 4When SECS is UsedSECTION 4Reading from/Writing to ID Tags• Write dataData Segment Area Refer to page 111.• Read ID Data Segment Area Refer to page 111.S18,F7 Write Request S,H→E,replyL,41.<TARGETID> "01"-"31"2.<DATASEG>3.<DATALENGTH>4.<DATA>• When the data for all segments is batch written, both DATASEG and DATALENGTH are omitted (they are zero length items).• When all the data for a particular segment is written, DATALENGTH is omitted (it is a zero length item).• When DATASEG and DATALENGTH are specified, it is not permissible to specify a DATALENGTH that exceeds the maxi-mum length of the relevant DATASEG.• If a DATALENGTH that is under the set length for DATASEG is specified, only the data corresponding to the specified DATALENGTH is written, compressed into the smaller addresses.• The item lengths of DATASEG and DATA must be matched.• If DATASEG and DATALENGTH are both omitted (made zero length items), the length of DATA must match the total of the set lengths of all segments.S18,F8 Write Acknowledge S,H←EL,31.<TARGETID> "01"-"31"2.<SSACK>3.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, SSACK = "CE" communications error• When DATASEG and DATALENGTH are illegal:s = 0, SSACK = "CE" communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.S18,F9 Read ID Request S,H→E,reply1.<TARGETID> "01"-"31"S18,F10 Read ID Data S,H←EL,41.<TARGETID> "01"-"31"2.<SSACK>3.<MID>4.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, MID item length = 0, SSACK = "CE" communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.

70SECTION 4When SECS is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID Tags• Write IDData Segment Area Refer to page 111.• Subsystem command (ChangeState)S18,F11 Write ID Request S,H→E,replyL,21.<TARGETID> "01"-"31"2.<MID>• If an MID that is under the set ID length is specified, the data is compressed into the smaller addresses, and NULL (0x00) is written as the remaining data.S18,F12 Write ID Acknowledge S,H←EL,31.<TARGETID> "01"-"31"2.<SSACK>3.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, SSACK = "CE" communications error• When there is an MID length error:s = 0, SSACK = "CE" communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.S18,F13 Subsystem Command Request (ChangeState) S,H→E,replyL,31.<TARGETID> "00" (fixed)2.<SSCMD> "ChangeState"3.L,11.<CPVAL1> "OP", "MT" or "PS"CPVAL = "PS" is a parameter setting unique to this CIDRW Controller for switching to the Setting mode.S18,F14 Subsystem Command Acknowledge (ChangeState) S,H←EL,31.<TARGETID> "00"2.<SSACK>3.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, SSACK = "CE" communications error• When SSCMD is invalid:s = 0, SSACK = "CE" communications error• When OperationalStatus is BUSY:s = 0, SSACK = "EE" execution error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.

71CIDRW SystemUser’s ManualSECTION 4When SECS is UsedSECTION 4Reading from/Writing to ID Tags• Subsystem command (GetStatus)• Subsystem command (PerformDiagnostics)S18,F13 Subsystem Command Request (GetStatus) S,HÅ→,replyL,31.<TARGETID> "00"-"31"2.<SSCMD> "GetStatus"3.L,0S18,F14 Subsystem Command Acknowledge (GetStatus) S,H←EL,31.<TARGETID> "00"-"31"2.<SSACK> "GetStatus"3.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, SSACK = "CE" communications error• When SSCMD is invalid:s = 0, SSACK = "CE" communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.S18,F13 Subsystem Command Request (PerformDiagnostics) S,H→E,replyL,31.<TARGETID> "00"-"31"2.<SSCMD> "PerformDiagnostics"3.L,0S18,F14 Subsystem command Acknowledge (PerformDiagnostics) S,H←EL,31.<TARGETID> "00"-"31"2.<SSACK>3.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, SSACK = "CE" communications error• When SSCMD is invalid:s = 0, SSACK = "CE" communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.

72SECTION 4When SECS is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID Tags• Subsystem command (Reset)S18,F13 Subsystem Command Request (Reset) S,H→E,replyL,31.<TARGETID> "00" (fixed)2.<SSCMD> "Reset"3.L,0S18,F14 Subsystem Command Acknowledge (Reset) S,H←EL,31.<TARGETID> "00"2.<SSACK>3.L,0• When the specified target is invalid:SSACK = "CE" communications error• When SSCMD is invalid:SSACK = "CE" communications error

73CIDRW SystemUser’s ManualSECTION 4When SECS is UsedSECTION 4Reading from/Writing to ID TagsOperation ConditionsThe response messages and response codes (SSACK) in each state are shown below:State Initializing Operating MaintenanceMessage Function IDLE BUSYS1,F1 OnlineRequest S1,F0 S1,F2 S1,F2 S1,F2S18,F11 WriteID S18,F0 S18,F0 S18,F0 NOS18,F7 WriteData S18,F0 NO NO S18,F0S18,F3 SetAttribute S18,F0 NO NO NOS18,F13(Reset) Reset S18,F0 NO NO NOS18,F9 ReadID S18,F0 NO NO NOS18,F5 ReadData S18,F0 NO NO S18,F0S18,F13(PerformDiagnostics) Diagnostics S18,F0 NO NO NOS18,F13(GetStatus) GetStatus S18,F0 NO NO NOS18,F1 GetAttribute S18,F0 NO NO NOS18,F13(ChangeState) ChangeState(to MT) S18,F0 NO S18,F0 S18,F0S18,F13(ChangeState) ChangeState(to OP) S18,F0 S18,F0 S18,F0 NOS18,F13(ChangeState) ChangeState(to PS) S18,F0 NO S18,F0 NO

74SECTION 4When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsWhen SECS is Not UsedCommand/Response FormatMeaning of FCS (frame check sequence)This is two ASCII code characters obtained by conversion from the 8-bit exclusive logical sum (EOR) of the charactersfrom the character immediately after SOH to the character immediately before FCS.Example: Reading the data of page 1 and page 2 of node No.1:CommandSOH Node No. Command code Parameter FCS CR1 ⋅ ⋅ ⋅ n01h 0DhResponseSOH Node No. Response codeParameter FCS CR1 ⋅ ⋅ ⋅ n01h 0DhCommandCalculation range(ASCII conversion)

75CIDRW SystemUser’s ManualSECTION 4When SECS is Not UsedSECTION 4Reading from/Writing to ID TagsCommandCommand code listName Value Function SeeREAD 0100 When this command is received, the system communicates with the ID Tag, and reads the specified page(s) of data. Any pages up to a maximum of 16 can be selected.p.76WRITE 0200 When this command is received, the system communicates with the ID Tag, and writes the specified page(s) of data. Any pages up to a maximum of 16 can be selected.p.77Same Write 0300 When this command is received, the system communicates with the ID Tag, and writes the same data in page units to the specified pages. Up to 17 pages, which is the maximum number of pages for an ID Tag, can be specified.p.79Byte Write 0400 When this command is received the system communicates with the ID Tag, and writes data to the area specified by a first address and number of bytes. A maximum of 128 bytes can be specified.p.80TEST 10 Sends received data to the host device. p.81NAK 12 Sends the response made immediately before again. p.82Noise measurement 40 Measures the noise in the vicinity of the CIDRW Head. p.82RESET 7F Resets the Amplifier Unit. p.82Response code listType Response code Name DescriptionNormal end 00 Normal end Command execution is completed normally.Host communi-cations error14 Format error There is a mistake in the command format.(E.g. the command code is undefined, or the page or address spec-ification is inappropriate.)Communica-tions error70 Communications error Noise or another hindrance occurs during communication with an ID Tag, and communications cannot be completed normally.71 Verification error Correct data cannot be written to an ID Tag.72 No Tag error Either there is no ID Tag in front of the CIDRW Head, or the CIDRW Head is unable to detect the ID Tag due to environmental factors (e.g. noise).7B Outside write area error Writing is not completed normally.7E ID system error (1) The ID Tag is in a status where it cannot execute command pro-cessing.7F ID system error (2) An inapplicable ID Tag has been used.

76SECTION 4When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsREADReads any pages of data from the ID Tag. The maximum number of pages that can be read at onetime is 16.Data Segment Area Refer to page 111.The response code (when normal: 00) and the data in the specified pages are returned in ascending order ofpage numbers.Example: Reading the data of pages 1 and 3 of node No.1Parameter descriptionParameter DescriptionPage designation Pages are specified by setting the bits corresponding to pages that are to be read to "1" and setting the other bits to "0", then converting the result to a hexadecimal character string.SOH Node No. Response codeRead dataFCS CRPage n ⋅ ⋅ ⋅ Page m (n<m)Data 1 ⋅ ⋅ ⋅ Data 8 Data 1 ⋅ ⋅ ⋅ Data 801h 0 0 0DhData content of the ID TagPage 1 12h 34h 56h 78h 90h 12h 34h 56hPage 2Page 3 11h 22h 33h 44h 55h 66h 77h 88hPage 4CommandBit 7-07-321076-1076-210PageSys-SysSys-Sys1716151413-8765-1SysSysDesignation 0* 0* 0* 0* 0* 0/1 0/1 0/1 0/1 0/1 ••• 0/1 0/1 0/1 0/1 ••• 0/1 0* 0*Value 00 00 - 07 00 - FF 00 - FC* Always specify 0. If you specify 1 an error (Response code : 14) will occur.SOH Node No. Command code Page designation (8 characters) FCS CR01h 0100 0DhResponseCommand00000000000000000000000000010100Binary notationSOH Node No. Command code Page designation FCS CR01h01010000000014050Dh

77CIDRW SystemUser’s ManualSECTION 4When SECS is Not UsedSECTION 4Reading from/Writing to ID TagsWRITEData is written in page units to the ID Tag. Any page(s) can be specified. It is possible to write to amaximum of 16 pages at one time.Data Segment Area Refer to page 111.The response code (when normal: 00) is returned.SOH Node No. Response code Page 1 Page 3 FCS CR01h 0 1 0 0 123456789012345611223344556677880 70DhParameter descriptionParameter DescriptionPage designation Pages are specified by setting the bits corresponding to pages that are to be read to "1" and setting the other bits to "0", then converting the result to a hexadecimal character string.Write data The data to be written to the specified pages is specified in ascending order of page numbers.SOH Node No. Response code FCS CR01h 0 0 0DhResponseCommandBit 7-07-321076-1076-210PageSys-SysSys-Sys1716151413-8765-1SysSysDesignation 0* 0* 0* 0* 0* 0/1 0/1 0/1 0/1 0/1 ••• 0/1 0/1 0/1 0/1 ••• 0/1 0* 0*Value 00 00 - 07 00 - FF 00 - FC* Always specify 0. If you specify 1 an error (Response code : 14) will occur.SOH Node No.Command codePage designation(8 characters)Write dataFCS CRPage n ⋅ ⋅ ⋅ Page m (n<m)Data 1 ⋅ ⋅ ⋅ Data 8 Data 1 ⋅ ⋅ ⋅ Data 801h 0200 0DHResponse

78SECTION 4When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsExample: Writing data to pages 8 and 10 of node No.1:The ID Tag status on normal completion is as shown below:SOH Node No. Response code FCS CR01h0100010DhPage 8 11h 22h 33h 44h 55h 66h 77h 88hPage 9Page 10 01h 23h 45h 67h 89h ABh CDh EFhCommand00000000000000000000101000000000SOH Node No.Command codePage designation Data of page 8 Data of page 10 FCS CR01h 0 1 0 2 0 000000A0011223344556677880123456789ABCDEF 7 4 0DhBinary notationResponse

79CIDRW SystemUser’s ManualSECTION 4When SECS is Not UsedSECTION 4Reading from/Writing to ID TagsSame WriteWrites the same data to multiple pages of an ID Tag.Any page(s) can be specified.Data Segment Area Refer to page 111.The response code (when normal: 00) is returned.Example: Clearing pages 1 to 17 of node No.1 to 0:Parameter descriptionParameter DescriptionPage designation Pages are specified by setting the bits corresponding to pages that are to be read to "1" and setting the other bits to "0", then converting the result to a hexadecimal character string.Write data Specify the write data.SOH Node No. Response code FCS CR01h 0 0 0DhSOH Node No. Response code FCS CR01h0100010DhCommandSOH Node No. Command code Page designation (8 characters) Write data FCS CRData 1 ⋅ ⋅ ⋅ Data 801h 0 3 0 0 0DHBit 7-07-321076-1076-210PageSys-SysSys-Sys1716151413-8765-1SysSysDesignation 0* 0* 0* 0* 0* 0/1 0/1 0/1 0/1 0/1 ••• 0/1 0/1 0/1 0/1 ••• 0/1 0* 0*Value 00 00 - 07 00 - FF 00 - FC* Always specify 0. If you specify 1 an error (Response code : 14) will occur.ResponseCommand00000000000001111111111111111100Binary notationSOH Node No. Command code Page designation Write data FCS CR01h 0 1 03000007FFFC0000000000000000 0 0 0DhResponse

80SECTION 4When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsByte WriteWrites data to any specified number of bytes starting from the address specified in the ID Tag.The maximum number of bytes that can be written at one time is 128.* Data number n = number of bytes written to (2-character units)Data Segment Area Refer to page 111.The response code (when normal: 00) is returned.Example: Writing to two bytes starting from address 05h of node No.1:The ID Tag status on normal completion is as shown below:SOH Node No. Command code First addressWrite data FCS CRData 1 ••• Data n01h 0400 0DhParameter descriptionParameter DescriptionAddress designation Addresses can be specified in the range 00h to 87h.Write data Up to 128 bytes of write data, starting from the specified address, can be specified.SOH Node No. Response code FCS CR01h 0 0 0DhSOH Node No. Command code First address Write data FCS CRData 1 Data 201h010400051234040DhSOH Node No. Response code FCS CR01h0100010DhPage 1 12h 34hPage 2CommandResponseCommandResponse

81CIDRW SystemUser’s ManualSECTION 4When SECS is Not UsedSECTION 4Reading from/Writing to ID TagsTESTPerforms a communication test on communications between the host device and Amplifier Unit.When an Amplifier Unit receives a test command, it sends the response code and command test datato the host device as the response.* Number of data n < 136 (2-character units)The response code (when normal: 00) and the received test data are returned.Example: Testing by sending the data "12345678" to node No.1:SOH Node No. Command code Test data FCS CRData 1 ••• Data n01h 1 0 0DhParameter descriptionParameter DescriptionTest data The data to be sent in the test is specified with a hexadecimal value. (Max. 270 characters)However, note that odd numbers of characters cannot be used.SOH Node No. Response codeTest data FCS CRData 1 ••• Data n01h 0 0 0DhSOH Node No. Command code Test data FCS CRData 1 Data 2 Data 3 Data 401h01 1 0 12345678080DhSOH Node No. Response codeTest data FCS CRData 1 Data 2 Data 3 Data 401h010012345678090DhCommandResponseCommandResponse

82SECTION 4When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsNAKSends the response made immediately before again.Sends the response made immediately before again.Noise measurementThe levels of noise in the vicinity of the CIDRW Head are measured and the noise level is expressednumerically in the range "00" to "99."The response code (when normal: 00) and the noise level "00" to "99" are returned.Influence of background noise on communication distance Refer to page 110.RESETAll Amplifier Unit processing is stopped, and the initial status is re-established.There is no response to this command.SOH Node No. Command code FCS CR01h 1 2 0DhSOH Node No. Command code FCS CR01h 4 0 0DhSOH Node No. Response code Noise level FCS CR01h 0 0 0DhSOH Node No. Command code FCS CR01h 7 F 0DhCommandResponseCommandResponseCommandResponse

SECTION 5Troubleshooting83CIDRW SystemUser’s ManualSECTION 5TroubleshootingWhen SECS is Used 84When SECS is Not Used 90

84SECTION 5When SECS is UsedCIDRW SystemUser’s ManualSECTION 5TroubleshootingWhen SECS is UsedErrors are indicated by the contents of the CIDRW Controller response messages, and by the indicators.List of Error MessagesWhen responses are made to messages sent by the CIDRW Controller, errors are expressed by thecontents of error messages and the nature of the SSACK response.Controller IndicatorsIf an error or alarm has occurred at the CIDRW Controller, the LEDs on the front of the Controller light.S F Direction SECS II names10S,H←E Abort Transaction90S,H→E Abort Transaction91S,H←E Unrecognized Device ID93S,H←E Unrecognized Stream Type95S,H←E Unrecognized Function Type97S,H←E Illegal Data99S,H←E Transaction Timer Timeout911S,H←E Data Too Long18 0 S,H←E Abort TransactionName FunctionOPERATING (green) Lit when the operation status (status model) of the CIDRW system is "operating."ALARMS (green) Lit when the status of "AlamStatus" of the CIDRW system is "Alarm (1)." BUSY (green) Lit when the status of "OparationalStatus" of the CIDRW system is "BUSY."ERROR (red) When a processing error is detected (when SSACK is other than "NO"), this indicator is lit for 50 ms.

85CIDRW SystemUser’s ManualSECTION 5When SECS is UsedSECTION 5TroubleshootingOperation Check FlowchartNormal Operation Mode• Operating normally in the Normal Operation modeIndicatorsPOWER OPERATING ALARMS BUSY ERRORResponseResponse FunctionS F— — SSACK="NO"There is aresponse to messagetransmission.(SSNAK = other than"NO")Error occurrenceAll LEDs are litor flashing.POWER-LED is off.NoYesNoYesNoAn error has occurred in the CIDRW Controller power supply.Check the power supply of the CIDRW power supply.Check the contents of the response message.When the CIDRW Controller responds to a message transmis-sion Refer to page 86.Yes An error has occurred at the CIDRW Controller.Check the status of the indicators.When all the LEDs are lit or flashing Refer to page 86.Check if the settings of the CIDRW Controller and Amplifier Unit are correct.When the CIDRW Controller fails to respond to messages sent to it Refer to page 87.When an error unrelated to message transmission and responses occurs Refer to page 87.

86SECTION 5When SECS is UsedCIDRW SystemUser’s ManualSECTION 5Troubleshooting• When the CIDRW Controller responds to a message transmissionThere is a mistake in the message sent to the CIDRW Controller or the Amplifier Unit settings. Aftertaking the appropriate corrective action, restart the Controller and the Amplifier Unit and send the mes-sage again.• When all the LEDs are lit or flashingAn error has occurred in the CIDRW Controller.After taking the appropriate corrective action, restart the CIDRW Controller.Response Main check pointsS F— 0 Status conditions when the message was issued (e.g. a Write ID Request message (S18, F11) was sent in the operating mode, or the message was sent during initial processing)Operation Conditions Refer to page 73.9 7 Message composition: illegal attributes, insufficient items, etc.Other than aboveAscertain the cause from the contents of the SSACK response.CE • Mistake in the details of the items in the message(The node number of an amplifier that is not set was specified as the "TARGET ID," or a segment name that is not set has been specified for "DATASEG.")• Connection of RS-485 cables between Amplifier Units (failure to detect Amplifier Units)• Amplifier Unit baud rate settings (failure to detect Amplifier Units)• Node numbers of the Amplifier Units (The same number is set for more than one unit, making detection impossible)• Cable routing between the host device and CIDRW Controller (influence of background noise)• Noise levels of the power supply line to the CIDRW ControllerEE • Installation distance/inclination between the ID Tag and CIDRW Head• Background noise levels of the CIDRW Head• Installation spacing in relation to CIDRW Heads connected in other CIDRW systemsHE • Mistake in the details of the items in the message(A segment that does not match the Amplifier Unit specifications has been set; the response time-out setting is not correct.)• Connection and wiring of cable between CIDRW Controller and Amplifier Unit• Power supply to Amplifier Units• Amplifier Unit terminal resistance settings• Routing of each cable (influence of background noise)• Node numbers of the Amplifier Units (the same number is set for more than one unit)• Amplifier Unit error (hardware error)• Noise levels of the power supply lineTE • Type/specifications of the ID Tags used• Settings of the ID Tags used (lock, etc.)• Environment of use of the ID Tags (ID Tag breakage due to use in unanticipated ways)• ID Tag overwrite lifePOWER OPERATING ALARMS BUSY ERROR Main check points• Supply of 24 VDC power• The CIDRW Controller may be damaged.• Mode switch setting (Is the setting "0"?)If the error cannot be resolved after checking, the CIDRW Controller may be damaged.• The CIDRW Controller may be damaged.

87CIDRW SystemUser’s ManualSECTION 5When SECS is UsedSECTION 5Troubleshooting• When the CIDRW Controller fails to respond to messages sent to itThere is a mistake in the CIDRW Controller or Amplifier Unit settings.After taking the appropriate corrective action, restart the CIDRW Controller and Amplifier Unit.• When an error unrelated to message transmission and responses occursThere is a mistake in the settings of the CIDRW Controller and Amplifier Unit.After taking the appropriate corrective action, restart the CIDRW Controller and Amplifier Unit.POWER OPERATING ALARMS BUSY ERROR Main check points• Mode switch setting (Is the setting "0"?)• Cable wiring between the CIDRW Controller and host device• Communications conditions for communication between the CIDRW Controller and host device (baud rate, character composition, etc.)• Cable wiring between the CIDRW Controller and host device• Node numbers of the Amplifier Units (The same number is set for more than one unit.)POWER OPERATING ALARMS BUSY ERROR Main check points• Mode switch setting (Is the setting "0"?)• Amplifier Unit baud rate settings• Node numbers of the Amplifier Units (The same number is set for more than one unit.)• Connection and wiring of cable between CIDRW Controller and Amplifier Unit• Amplifier Unit error (hardware error)• Routing of each cable (influence of back-ground noise)

88SECTION 5When SECS is UsedCIDRW SystemUser’s ManualSECTION 5TroubleshootingSetting Mode• Operating normally in the Setting modeTerminal initial screen of the host device after startup in the Setting modeTerminal screen when parameter setting has been completed without errorIndicatorsPOWER OPERATING ALARMS BUSY ERRORError occurrenceAll LEDs are litor flashing.POWER-LED is OFFNoYesNoYesAn error has occurred in the CIDRW Controller power supply.Check the power supply of the CIDRW Controller.An error has occurred at the CIDRW Controller.Check the status of the indicators.When all the LEDs are lit or flashing Refer to page 89.Check if the CIDRW Controller settings are correct.When the CIDRW Controller fails to respond to messages sent to it Refer to page 89.When an error unrelated to message transmission and responses occurs Refer to page 89.SETUP_START <L21 ><XXX.XX, YYY.YY>_Software Revision LevelModel numberHardware Revision LevelSETUP_COMPLETE_

89CIDRW SystemUser’s ManualSECTION 5When SECS is UsedSECTION 5Troubleshooting• When all the LEDs are lit or flashingAn error has occurred in the CIDRW Controller. After taking appropriate corrective action, restart theCIDRW Controller and check the indicators.• When the CIDRW Controller responds to a message transmissionThere is a mistake in the CIDRW Controller settings or the sent parameters. After taking appropriatecorrective action, restart the CIDRW Controller and check the indicators.• When the CIDRW Controller fails to respond to messages sent to itThere is a mistake in the CIDRW Controller settings or the sent parameters. After taking appropriatecorrective action, restart the CIDRW Controller and check the indicators.• When an error unrelated to message transmission and responses occursThere is a mistake in the settings of the CIDRW Controller or Amplifier Unit. After taking appropriatecorrective action, restart the CIDRW Controller and Amplifier Unit and check the indicators.POWER OPERATING ALARMS BUSY ERROR Main check points• Supply of 24 VDC power• The CIDRW Controller may be damaged.• Mode switch setting (Is the setting "3"?)If the error cannot be resolved after checking, the CIDRW Controller may be damaged.• The CIDRW Controller may be damaged.POWER OPERATING ALARMS BUSY ERROR Main check points• Sent parameters (Are the parameters cor-rect? Are the settings correct?)Response ContentsSETUP_FAILED [ ] The parameters are not updated. The figure in square brackets [ ] indicates the line number where the error was first detected. If a parity error is detected in the received characters, this figure is [0].POWER OPERATING ALARMS BUSY ERROR Main check points• Transmission parameters (Are the parameters correct?)• Communications conditions for communication between the CIDRW Controller and the host device (baud rate, character composition, etc.)• Mode switch setting (Is the setting "3"?)POWER OPERATING ALARMS BUSY ERROR Main check points• Mode switch setting (Is the setting "3"?)

90SECTION 5When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 5TroubleshootingWhen SECS is Not UsedErrors are indicated by the presence or absence of a response to an Amplifier Unit command, and by theindicators.List of Error MessagesAmplifier Unit IndicatorsType Response code Name DescriptionHost communi-cations error14 Format error There is a mistake in the command format.(E.g. the command portion is undefined, or the page or address speci-fication is inappropriate.)Communications error between the CIDRW Head and ID Tag70 Communications errorNoise or another hindrance has occurred during communication with an ID Tag, and communications cannot be completed normally.71 Verification error Correct data cannot be written to an ID Tag.72 No Tag error Either there is no ID Tag in front of the CIDRW Head, or the CIDRW Head is unable to detect the ID Tag due to environmental factors (e.g. noise).7B Outside write area errorThe ID Tag is at a position where reading is possible but writing is not, so writing does not complete normally.7E ID system error (1) The ID Tag is in a status where it cannot execute the command pro-cessing.7F ID system error (2) An inapplicable ID Tag has been used.Name IndicationsRUN (green) Turns ON when the Amplifier Unit is in normal operation.COMM (orange) Turns ON during communications with the host device or during communications with an ID Tag.NORM (green) Turns On when the communications finish with no error.ERROR (red) Turns ON when an error occurs during communication with the host device, or during communication with an ID Tag.

91CIDRW SystemUser’s ManualSECTION 5When SECS is Not UsedSECTION 5Troubleshooting Operation Check FlowchartFrom Installation to Trial OperationErrors are indicated by whether or not a response to the test command is received and by the status ofthe Amplifier Unit indicators.• If the test command was received normally:IndicatorsRUN COMM NORM ERRORResponse code for the responseType Response code FunctionNormal 00 The command was received normally.Error occurrenceTest command transmissionRUN-LED is OFFNoYes An error has occurred at the Amplifier Unit.Amplifier Unit error Refer to page 92.Check if the Amplifier Unit settings are correct.If there is no response to the command: Refer to page 92.Response received Yes Check the nature of the response.If there is a response to the command Refer to page 92.No(Lights once)

92SECTION 5When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 5Troubleshooting• Amplifier Unit errorCheck the status of the indicator LEDs after transmission of the test command.After taking appropriate corrective action, restart the Amplifier Unit, send the test command again andcheck again.• If there is no response to the command:Check the status of the indicator LEDs after transmission of the test command.After taking appropriate corrective action, restart the Amplifier Unit, send the test command again andcheck again.Method using RS signal control at the host device In a 1:N connection using Link Units, the RS signals generated from the host device by normal control must be input asCS signals. Turn the RS signals OFF within 15 ms after the completion of data transmission. Correct communicationswill not be possible without this control.• If there is a response to the command:Check the status of the indicator LEDs after transmission of the test command.After taking appropriate corrective action, restart the Amplifier Unit, send the test command again andcheck again.RUN COMM NORM ERROR Main check points—(If RUN is OFF, the status of the other indica-tor LEDs can be ignored.)• Influence of background noise (change installation position)• Amplifier Unit power supplyIf the error cannot be resolved after checking, the Amplifier Unit may be damaged.RUN COMM NORM ERROR Main check points• Amplifier Unit baud rate settings• Node numbers of the Amplifier Units (do not match the node number in the test command)• Connection and wiring of the cable between the host device and Amplifier Unit• OFF timing of the RS signals between the host device and Amplifier Unit• Routing of each cable (influence of background noise)If the error cannot be resolved after checking, the Amplifier Unit may be damaged.• Amplifier Unit baud rate settings• Connection and wiring of the cable between the host device and Amplifier Unit• Routing of the cables (influence of background noise)• OFF timing of the RS signals between the host device and Amplifier Unit• FCS (frame check sequence) calculation methodRUN COMM NORM ERROR Main check points• Node numbers of the Amplifier Units (The same number is set for more than one unit)If the error cannot be resolved after checking, the Amplifier Unit may be damaged.There is a mistake in the command format (number of charac-ters, character code, etc.).(Lights once)SD at host deviceRS at host deviceON only during data transmission from the host deviceWithin 15 ms(Lights once)

93CIDRW SystemUser’s ManualSECTION 5When SECS is Not UsedSECTION 5TroubleshootingFrom Trial Operation to CommunicationsErrors are indicated by the status of the indicators after transmission of the write command, and by theresponse code of the response.• If the ID Tag was processed normally:If there is no response to the write command, refer to the From Installation to Trial Operation, Operation Check Flowchart. Refer to page 91.IndicatorsRUN COMM NORM ERRORResponse code for the responseType Response code FunctionNormal 00 The ID Tag was processed normally.Error occurrenceIs the response code 1 ?NoYes Check the command format.If the response code is 1 Refer to page 94.Yes Communication with the ID Tag has failed.If the response code is 7 Refer to page 94.Write command sentRUN-LED is OFFNoYes An error has occurred at the Amplifier Unit.Amplifier Unit error Refer to page 94.Is the response code 7 ?Communications OKNo(Lights once) (Lights once)

94SECTION 5When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 5Troubleshooting• Amplifier Unit errorCheck the status of the indicator LEDs after transmission of the command.After taking appropriate corrective action, send the write command again and check again.• If the response code is 1 :There is a host device communications error.Check the status of the indicator LEDs and the response code of the response after transmission of thecommand.After taking appropriate corrective action, send the write command again and check again.• If the response code is 7 :There is a communications error in communication between the CIDRW Head and ID Tag.Check the status of the indicator LEDs and the response code of the response after transmission of thecommand.After taking appropriate corrective action, send the write command again and check again.* The ID Tag has a lock function, but the amplifier unit has no function for locking an ID Tag.RUN COMM NORM ERROR Main check points—(If RUN is OFF, the status of the other indica-tor LEDs can be ignored.)• Influence of background noise (Change installation position)• Amplifier Unit power supplyIf the error cannot be resolved by checking the two points above, the Amplifier Unit may be damaged.RUN COMM NORM ERRORResponse code Main check points14 Command format(Command code, page designation, address designation, processed data volume, etc.)RUN COMM NORM ERRORResponse code Main check points70• Background noise levels of the CIDRW Head (Check the surroundings with the environmental noise level measurement function)• Distance to another CIDRW Head• Influence of background noise (Change installation position)If the error cannot be resolved after checking, the Amplifier Unit may be damaged.71 • ID Tag overwrite life (Replace the ID Tag)• Environment of use of the ID Tags (ID Tag breakage due to use in unanticipated ways)72 • Connection to the CIDRW Head• Distance between the ID Tag and CIDRW Head• CIDRW Head background noise levels (Check the surroundings with the environmental noise level measurement function)• Distance to another CIDRW Head7B • Distance between the ID Tag and CIDRW Head• Background noise levels of the CIDRW Head (Check the surroundings with the environmental noise level measurement function)• Distance to another CIDRW Head• Influence of background noise (Change installation position)7E • Type/specifications of the ID Tags used• Settings of the ID Tags used (The ID Tag lock function is used.*)• Environment of use of the ID Tags (ID Tag breakage due to use in unanticipated ways)7F(Lights once)(Lights once) (Lights once)

SECTION 6Appendix95CIDRW SystemUser’s ManualSECTION 6AppendixSpecifications and Dimensions 96System Configuration Examples 100When SECS is Not Used 101Data Segment Area 111Regular Inspection 112SECS Protocol Specifications 113ASCII Code Table 118Protective Construction 119

96SECTION 6Specifications and DimensionsCIDRW SystemUser’s ManualSECTION 6AppendixSpecifications and DimensionsControllerV700-L21Item SpecificationsPower supply voltage 24 VDC +10% -15%Current consumption 150 mA max. (inrush current: approx. 10 A max.)Ambient temperature Operating: 0 to +40°C Storage: -15 to +65°C (with no icing)Ambient humidity Operating: 10 to 85% RH Storage: 10 to 95% RH (with no condensation)Degree of protection IP20 (IEC60529)Insulation resistance 50 MΩ min. between power supply terminals and the frame ground terminal (500 VDC M)Dielectric strength Leak current not to exceed 3.5 mA on application of 500 VAC (50/60 Hz for 1 minute) between both power supply terminals and the frame ground terminalVibration resistance Frequency: 10 to 150 Hz; double amplitude: 0.20 mm; acceleration: 15 m/s2 for8 minutes, 10 times each in X, Y, and Z directionsShock resistance Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitionsGround Ground to 100 Ω or less.Case material SECC (coating)Weight Approx. 570 g2:rr/Ǿ(Unit: mm)Mounting dimensionsPower indicatorIndicators(mounting holes)Four, 4.5-dia. holes

CIDRW SystemUser’s ManualSECTION 6Specifications and DimensionsSECTION 6Appendix97Amplifier UnitV640-HAM11Item SpecificationsPower supply voltage 24 VDC +10% -15%Current consumption 150 mA max.Ambient temperature Operating: 0 to +40°C Storage: -15 to +65°C (with no icing)Ambient humidity Operating/Storage: 35 to 85% RH (with no condensation)Degree of protection IP20 (IEC60529 standard)Insulation resistance 20 MΩ min. between power supply terminals and the frame ground terminal (100 VDC M)Dielectric strength Leak current not to exceed 5 mA on application of 1000 VAC (50/60 Hz for 1 minute) between both power supply terminals and the frame ground terminalVibration resistance Frequency: 10 to 150 Hz; double amplitude: 0.20 mm; acceleration: 15 m/s2 for8 minutes, 10 times each in X, Y, and Z directionsShock resistance Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitionsGround Ground to 100 Ω or less.Case material SECC (coating)Weight Approx. 500 g㧔㧕㧔㧕㧔㧕㧔㧕㧔㧕㧔㧕㧔㧕㧔㧕㧔㧕rr Ǿ/DIP switch(Unit: mm)Mounting dimensions4 indicatorsFour, 4.5-dia. holes

98SECTION 6Specifications and DimensionsCIDRW SystemUser’s ManualSECTION 6AppendixCIDRW HeadV640-HS61Item SpecificationsTransmission frequency 134 kHzAmbient temperature Operating: 0 to +40°C Storage: -15 to +65°C (with no icing)Ambient humidity Operating/Storage: 35 to 85% RH (with no condensation)Degree of protection IP60 (IEC60529)Insulation resistance 20 MΩ min. between all terminals and the case (100 VDC M)Dielectric strength Leak current not to exceed 5 mA on application of 1000 VAC (50/60 Hz for 1 minute) between all terminals and the caseVibration resistance Frequency: 10 to 150 Hz; double amplitude: 0.20 mm; acceleration: 15 m/s2 for8 minutes, 10 times each in X, Y, and Z directionsShock resistance Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitionsCasing material ABS/epoxy resinStainless steel mountWeight Approx. 70 gCable length 2 mCable specification 3-mm-dia. coaxial cable (no flexibility)rrǾ/14ǾCoaxial cable 3.0 dia., standard length 2 m(Unit: mm)ConnectorAntenna centerAntenna centerMounting dimensionsFour M3 or 3.5-dia. holesFour, 3.5-dia. holes

CIDRW SystemUser’s ManualSECTION 6Specifications and DimensionsSECTION 6Appendix99Link UnitV700-L11Item SpecificationsPower supply voltage 24 VDC +10% -15%Current consumption 250 mA max. (inrush current: approx. 10 A)Ambient temperature Operating: 0 to +40°C Storage: -15 to +50°C (with no icing)Ambient humidity Operating/Storage: 35 to 85% RH (with no condensation)Degree of protection IP20 (IEC60529)Insulation resistance 50 MΩ min. between power supply terminals and the frame ground terminal (500 VDC M)Dielectric strength Leak current not to exceed 5 mA on application of 1000 VAC (50/60 Hz for 1 minute) between power supply terminals and the frame ground terminalVibration resistance Frequency: 10 to 150 Hz; double amplitude: 0.20 mm; acceleration: 15 m/s2 for 8 minutes, 10 times each in X, Y, and Z directionsShock resistance Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitionsGround Ground to 100 Ω or less.Case material PC/ABS resinWeight Approx. 200 grrǾ/ޓ14ޓǾ(Unit: mm)Mounting dimensionsTwo M4 or 4.2-dia. holesTwo, 4.5-dia. holes

100SECTION 6System Configuration ExamplesCIDRW SystemUser’s ManualSECTION 6AppendixSystem Configuration Examples When SECS is UsedCommunication with the host device is possible using the SECS protocol.Using Link Units to make connections makes it possible to remove and replace just the relevant Ampli-fier Unit while leaving the power to the CIDRW system on in the event of a failure or during mainte-nance.HostThese are antennae forreading the carrier IDsfrom the ID Tags andwriting the carrier IDs.These are units thatcontrol a CIDRW Head. Up to 31 units can beconnected.This is e.g. a host,or equipment con-troller.CIDRW HeadV640-HS61Amplifier UnitV640-HAM11CIDRW ControllerV700-L21Multiple Amplifier Units are controlled in response to commands (SECS) from the host device.RS-232CSECS I/IIMax. 50 mRS-485RS-232CSECS I/IIRS-232CLink unitV700-L11Just the relevant Amplifier Unit can be removed and replaced while the powerremains on.Max. 50 mRS-485Up to 31 units can be connected.

CIDRW SystemUser’s ManualSECTION 6System Configuration ExamplesSECTION 6Appendix101 When SECS is Not UsedCommunications with the host device follow the OMRON proprietary protocol.The Amplifier Units are connected directly to the host device without using a CIDRW Controller.Using Link Units to make connections makes it possible to remove and replace just the relevant Ampli-fier Unit while leaving the power to the CIDRW system on in the event of a failure or during mainte-nance.HostThese are antennae forreading the carrier IDsfrom the ID Tags andwriting the carrier IDs.These are units thatcontrol a CIDRW Head. Up to 31 units can beconnected.This is e.g. a host,or equipment con-troller.Amplifier UnitV640-HAM11RS-232COMRON original protocolMax. 50 mCIDRW HeadV640-HS61Max. 50 mLink unitV700-L11Just the relevant Amplifier Unit can be removed and replaced while the powerremains on.RS-485Up to 31 units can be connected.RS-232COMRON original protocol

102SECTION 6Characteristic Data depending on Conditions of UseCIDRW SystemUser’s ManualSECTION 6AppendixCharacteristic Data depending on Conditions of UseMaps of Communications Areas (Reference Only)Coaxial Mounting• READ•WRITE                Communications Areas (READ)Distance in Y direction (mm)Distance in X direction (mm)        Communications Areas (WRITE)Distance in Y direction (mm)Distance in X direction (mm)

CIDRW SystemUser’s ManualSECTION 6Characteristic Data depending on Conditions of UseSECTION 6Appendix103Parallel Mounting• READ•WRITE                Communications Areas (READ)Distance in Y direction (mm)Distance in X direction (mm)0                Communications Areas (WRITE)Distance in Y direction (mm)Distance in X direction (mm)0

104SECTION 6Characteristic Data depending on Conditions of UseCIDRW SystemUser’s ManualSECTION 6AppendixVertical Mounting• READ•WRITE                Communications Areas (READ)Distance in Y direction (mm)Distance in X direction (mm)                Communications Areas (WRITE)Distance in Y direction (mm)Distance in X direction (mm)

CIDRW SystemUser’s ManualSECTION 6Characteristic Data depending on Conditions of UseSECTION 6Appendix105Mutual Interference Distances (Reference Only)In order to prevent malfunction due to mutual interference when multiple CIDRW Heads are used,install the heads with the spacing indicated below.For Coaxial Installation:For Parallel Installation:For Face-to-Face Installation:1 m min.1 m min.1 m min.

106SECTION 6Characteristic Data depending on Conditions of UseCIDRW SystemUser’s ManualSECTION 6AppendixInfluence of Background Metals (Reference Only)The CIDRW Head can also communicate from an opening in a ceiling panel (metal body).However, ensure the distances indicated below between the CIDRW Head and the metal body. If youdo not ensure these distances the communications distance will be substantially shortened.Metal body (material: AL, SUS)(Thickness : 1 mm)8*5%+&49*'#&10 mm min.10 mm min.20 mm min.20 mm min.Metal body (material: AL, SUS)

CIDRW SystemUser’s ManualSECTION 6Characteristic Data depending on Conditions of UseSECTION 6Appendix107Communications TimeRegardless of whether SECS is used or not, take the time required for processing between the hostdevice and Amplifier Units into account when designing the system.Communication time calculation formula (unit: ms)Read: 150.5 × (number of pages) + 6.1For write, same writing: 468.6 × (number of pages) + 80.3Byte write: 468.6 × (number of pages/8) + 229.9TAT calculation formula (units: ms)TAT = command and response transmission time + communication timeThe command and response transmission time differs depending on the number of characterssent and the communications conditions.This calculation applies to continuous transmission in which the Controller uses no spacesbetween command characters.Example of TAT calculation:Number of command characters: A; number of response characters: BBaud rate: 9600 bps, data length: 8 bits, non parity, 1 stop bitTime DescriptionCommunications time This is the time required for communication between an ID Tag and the CIDRW Head.TAT This is the time required for processing at the Amplifier Unit, seen from the host device.HostAmplifier UnitCommand ResponseCommunications timeTATRounding upTransmission time (ms) = Number of bits per character (bits)Baud rate (bps) × total number of characters of command and responseTAT (ms) = 109600 × (A + B) + Communications time (ms)

108SECTION 6Characteristic Data depending on Conditions of UseCIDRW SystemUser’s ManualSECTION 6AppendixThe graph for communications time for communication between the ID Tag and CIDRW Head, andTAT (when the baud rate is 9600 bps), is shown below.Note however that the communications time and TAT may increase substantially according to the con-ditions of use.㪇㪌㪇㪇㪈㪇㪇㪇㪈㪌㪇㪇㪉㪇㪇㪇㪉㪌㪇㪇㪊㪇㪇㪇㪊㪌㪇㪇㪈㪉㪋㪍㪏㪈㪇㪈㪉㪈㪋㪈㪍ReadNumber of pages processedCommunications timeTAT (9600 bps)Communications time (ms)Communications time (ms)Write (same writing)Number of pages processedCommunications timeTAT (9600 bps)

CIDRW SystemUser’s ManualSECTION 6Characteristic Data depending on Conditions of UseSECTION 6Appendix109        Communications time (ms)Byte WriteNumber of bytes processedCommunications timeTAT (9600 bps)

110SECTION 6Characteristic Data depending on Conditions of UseCIDRW SystemUser’s ManualSECTION 6AppendixCommunications Distance Characteristics vs. Ambient NoiseThe graph below compares the results of measurement using the noise measurement function withcommunications distances.At installation implement measures in regard to metal in the vicinity of the CIDRW Head, power supplynoise, and atmospheric noise, to ensure that the noise level does not exceed "10." Noise measurement command (applies only when SECS is not used) Refer to page 82.   ᦨᄢ୯Noise levelCommunications distance (mm)Relationship between noise level and communications distance (reference values)(Max.)

CIDRW SystemUser’s ManualSECTION 6Data Segment AreaSECTION 6Appendix111Data Segment AreaThe data segment area of the RI-TRP-DR2B ID Tag is shown below.When using a CIDRW Controller, always set the data segment.Refer to page 48.• The carrier ID memory area starts from page 1 (fixed).• 00h to 87h in the table are addresses. Page 8 bytes/1 page1 00h 01h 02h 03h 04h 05h 06h 07h2 08h 09h 0Ah 0Bh 0Ch 0Dh 0Eh 0Fh3 10h 11h 12h 13h 14h 15h 16h 17h4 18h 19h 1Ah 1Bh 1Ch 1Dh 1Eh 1Fh5 20h 21h ••• ••• 27h6 28h 29h ••• ••• 2Fh7 30h 31h ••• ••• 37h89 :10 : :11 :121314 68h 69h ••• ••• 6Fh15 70h 71h ••• ••• 77h16 78h 79h ••• ••• 7Fh17 80h 81h ••• ••• 87hDATASEG LENGTHCarrierID16"S01" 8"S02" 8"S03" 8"S04" 8"S05" 8"S06" 8"S07" 8"S08" 8"S09" 8"S10" 8"S11" 8"S12" 8"S13" 8"S14" 8"S15" 8Carrier ID(16 byte)Data area(Total of 120 bytes)Data segment area Example of datasegment settings

112SECTION 6Regular InspectionCIDRW SystemUser’s ManualSECTION 6AppendixRegular InspectionIn order to maintain optimum performance of the functions of the CIDRW system, daily and periodicinspections are necessary.Inspection item Detail Criteria Tools requiredSupply voltage fluctuation Check that the supply voltage fluctuation at the power supply terminal block is within the permissible range.To be within supply voltage rating. MultimeterCheck that there are no frequent instan-taneous power failures or radical voltage drops.To be within permissible voltage fluctua-tion range.Power supply analyzerEnvironment Ambient tem-peratureCheck that the ambient temperature and humidity are within specified range.To be within the specified range. Maximum and minimum ther-mometerHygrometerAmbient humidityVibration and shockCheck that no vibration or shock is trans-mitted from any machines.Dust Check that the system is free of dust accumulation.To be none.Corrosive gas Check that no metal part of the system is discolored or corroded.I/O power supplyVoltage fluctu-ationCheck on the I/O terminal block that the voltage fluctuation and ripple are within the permissible ranges.To be within the specified range. MultimeterOscilloscopeRippleMounting condition Check that each device is securely mounted.There must be no loose screws. —Check that each connector is securely connected.Each connector must be locked or securely tightened with screws.Check that no screw of the terminal block is loosened.There must be no loose screws.Check that no wire is broken or nearly broken.There must be no wire that is broken or nearly broken.Check if grounding to 100 Ω or less has been done.To be grounded to 100 Ω or less.

CIDRW SystemUser’s ManualSECTION 6SECS Protocol SpecificationsSECTION 6Appendix113SECS Protocol SpecificationsA summary of the SEMI standards that relate to CIDRW is provided for reference when using this product.However, since the SEMI standards are subject to revision, you should also refer to the actual standards.• SEMI E99 THE CARRIER ID READER/WRITER FUNCTIONAL STANDARD• SEMI E5 EQUIPMENT COMMUNICATION STANDARD 2 MESSAGE CONTENT (SECS II)• SEMI E4 EQUIPMENT COMMUNICATION STANDARD 1 MESSAGE TRANSFER (SECS I)Operation ModelSet the CIDRW Controller's mode switch to "0" and start the system. When the system starts, the ini-tial processing is completed first, then the system will operate according to the status defined by E99.CIDRW status modelOperational status OPERATING Operation in progress in the operating modeIDLE Status in which no processing is in progress at any headBUSY Status when processing is in progress at any of the headsMAINTENANCE Operation in progress in the maintenance mode# Transitions according to state changes from the host deviceAlarm status No alarm Status in which there are no alarms currently in effect at the CIDRW Controller or any of the connected headsALARM Status in which an alarm has occurred• If a head in an abnormal status is detected during head detection in initial processing, or no heads are detected. (The error will not be cleared until the system has been restarted with the heads connected correctly.)• When a head error is detected in communications with an ID Tag. (The error will be automatically reset if it is cleared in subsequent processing.)• A CIDRW Controller internal error has occurred.Initial status(INITIALIZING)This is the status during processing such as internal initialization/head detection after startup, which is maintained until the CIDRW system is capable of its proper functions.CIDRW Head status modelOperational status OPERATING Status in which the head is operating normallyIDLE Status in which no processing is in progressBUSY Status in which processing is in progressNON-OPERATING Status in which a head check (CIDRW Head, Link Unit) is necessary(The CIDRW alarm status is the ALARM status.)

114SECTION 6SECS Protocol SpecificationsCIDRW SystemUser’s ManualSECTION 6AppendixProtocol Specifications• Character compositionStart bit (1) + data bits (8) + stop bit (1)* Conforms to SEMI E4• Protocol parameters• Double block detectionThe header of the block currently being received is compared with the correct block received immedi-ately before, and double blocks are detected. A setting in the setting mode determines whether thisfunction is used or not.•Multi-blockMulti-blocks are supported at the receiving side (maximum of 128 blocks).Multi-blocks are used at the sending side.• Message sizeThe maximum receivable message size is 32 kbytes.• InterleavingThe receiving side supports interleaving and block interleaving.The sending side uses interleaving and block interleaving.The maximum number of simultaneously open transactions is 16. If the maximum number isexceeded, SxF0 (abort transmission) is sent.• Device IDThe number of device IDs used is 1. Device IDs are specified in the setting mode.• Block numbersWith a single block, the block number is either 1 or 0. For multi-block transmission, the numbers 1 to128 are used. The block number for a single block is set in the setting mode.• Treatment of the systems byteThe system byte comprises the source ID and the transaction ID.The source ID is a fixed value and is specified in the setting mode.The initial value of the transaction ID is 1 and the maximum value is 0xFFFF. The value is incrementedfrom the first message transmission.Sign Name Default setting Setting range Setting unitBAUD Baud Rate 9600 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200 -DEVID Device ID 0 0 to 32767 1T1 Time-out between characters 0.5 s 0.1 to 10 s 0.1 sT2 Protocol time-out 10 s 0.2 to 25 s 0.2 sT3 Response time-out 45 s 1 to 120 s 1 sT4 Time-out between blocks 45 s 1 to 120 s 1 sRTY Retry limit 3 0 to 31 1M/S Master/slave M M : MasterS : Slave-

CIDRW SystemUser’s ManualSECTION 6SECS Protocol SpecificationsSECTION 6Appendix115•StoringThe method for storing in the BUSY status, e.g. because the internal buffer is full, is to use "NAK trans-mission."• Processing for time-out detectionAt T3 and T4 time-outs, the time-out is notified by the S9F9 message.• SECS parametersItem Default setting Range Setting UnitDouble block detection yes/no 1 1: The header of the block currently being received is compared with the correct block received immediately before, and double blocks are detected.0: Double block detection is not performed.-Source ID 0 0 to 32767 1Single block No. 1 0, 1 -

116SECTION 6SECS Protocol SpecificationsCIDRW SystemUser’s ManualSECTION 6AppendixSupport AttributesCIDRW attribute definitionsAttribute names Description Access Re-quest Format and mountingBasic items "Configuration" Number of CIDRW Heads RO Y 20 "00"-"31"The number of heads connected when the system power is turned ON (automatic recognition)"AlarmStatus" Substate of current CIDRW alarmsRO Y 20"0" = no alarm"0" = alarm has occurred"OperationalStatus" Substate of current CIDRW operationsRO Y 20"IDLE""BUSY""MANT""SoftwareRevisionLevel" Software revision (version) RO Y 20 6byte"VVV.RR"(VVV = version, RR = revision)Option "DateInstalled Date on which the sub-system was installedRW N 20 8 bytesAll " " (space) on shipping"DeviceType" CIDR / CIDRW classifica-tionRO N 20 5 bytes"CIDRW""HardwareRevisionLevel" Hardware revision number RO N 20 6 bytes"VVV.RR"(VVV = version, RR = revision)"MaintenanceData" Supplier dependent RW N 20 80 bytesAll " " (space) on shipping"Manufacturer" Manufacturer's name or ID RO N 20 17 bytes"OMRON Corporation""ModelNumber" Model name according to the makerRO N 20 6 bytes"L21 ""SerialNumber" System serial number RO N 20 max. 20 bytes(Not supported by the CIDRW)

CIDRW SystemUser’s ManualSECTION 6SECS Protocol SpecificationsSECTION 6Appendix117Reader/writer head attribute definitionAttribute names Description Access Re-quest Format and mountingBasic items "HeadStatus" Current status RO Y 20"IDLE""BUSY""NOOP""HeadID" Head number 1 to 31 RO Y(multi)20"01"-"31"("00" indicates the CIDRW itself, so cannot be used.)Option "Cycles" Number of read/write oper-ations executedRO N 54 (unsigned 4-byte integer)(Not supported by the Reader/Writer Head)"HeadCondition" Maintenance status RO N 20"NO": No alarm"NM": Status in which normal operation is not possible and maintenance is neces-sary"RW": Read/write error"RT": Read/write error rate(Not supported by the Reader/Writer Head)"NP": Status of power supply and connection errors"HeadDateInstalled" Date on which the head was installedRO N 20 "YYYYMMDD"(Not supported by the Reader/Writer Head)"HeadMaintenanceData" Supplier dependent N N 20(Not supported by the Reader/Writer Head)

$118SECTION 6ASCII Code TableCIDRW SystemUser’s ManualSECTION 6AppendixASCII Code TableLeftmostbitsRight-most bitsb8 - b50000 1001 0010 0011 0100 0101 0110 0111 1000 1101 1010 1011 1100 1101 1110 1111b4 - b1RowLine0 12 3 4 5 6 7 8 9 10 11 12 13 14 150000 0NUL TC7(DLE)(SP) 0 @ P ` pUndefined Undefined Undefined0001 1TC1(SOH) DC1!1AQaq0010 2TC2(STX) DC2"2BRbr0011 3TC3(ETX) DC3#3CScs0100 4TC4(EOT) DC4$4DTdt0101 5TC5(NEQ) TC8(NAK)%5EUe u0110 6TC6(ACK) TC9(SYN)&6FVf v0111 7BEL TC10(ETB)'7GWgw1000 5FE0(BS) CAN(8HXhx1001 9FE1(HT) EM)9IYiy1010 10FE2(LF) SUB*:JZjz1011 11FE3(VT) ESC+;K[k{1100 12FE4(FF) IS4(FS),<L\ l |1101 13FE5(CR) IS3(GS)-=M]m}1110 14S0 IS2(RS).>N^nÅP1111 15S1 IS1(US)/?OÅQ oDEL$

Omron 6CYCIDV6400202 Carrier ID Reader/Writer User Manual USERS MANUAL FOR V640

Omron Corporation Carrier ID Reader/Writer USERS MANUAL FOR V640

Contents

USERS MANUAL FOR V640

Navigation menu

Namespaces

Views

Navigation