Omron V640HAM11L Carrier ID Reader/Writer (RFID) User Manual Z307 E1 01

Omron Corporation Carrier ID Reader/Writer (RFID) Z307 E1 01

User manual2(L)

SECTION 4Reading from/Writing to ID Tags69CIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsWhen SECS Is Used 70Online Check 72Get Attributes 72Set Attributes 73Read Data 74Write Data 75Read ID 76Write ID 76Subsystem Command (ChangeState) 77Subsystem Command (GetStatus) 78Subsystem Command (PerformDiagnostics) 78Subsystem Command (Reset) 79When SECS Is Not Used 81READ 84WRITE 85SAME WRITE 87BYTE WRITE 88TEST 89NAK 90GET PARAMETER 90GET LAST COMMAND 92GET COMMUNICATIONS HISTORY 93CLEAR COMMUNICATIONS HISTORY 94NOISE MEASUREMENT 94RESET 94
70SECTION 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 149.Message SpecificationsList of Error Messages Refer to page 96.List of Messages UsedClassification S F Direction SECS II names SeeGeneral purpose messages11 S,H→E,reply Are You There Request p.7212 S,H←E On Line Data p.72CIDRW system messages18 1 S,H→E,reply Read Attribute Request p.7218 2 S,H←E Read Attribute Data p.7218 3 S,H→E,reply Write Attribute Request p.7318 4 S,H←E Write Attribute Acknowledge p.7318 5 S,H→E,reply Read Request p.7418 6 S,H←E Read Data p.7418 7 S,H→E,reply Write Request p.7518 8 S,H←E Write Acknowledge p.7518 9 S,H→E,reply Read ID Request p.7618 10 S,H←E Read ID Data p.7618 11 S,H→E,reply Write ID Request p.7618 12 S,H←E Write ID Acknowledge p.7618 13 S,H→E,reply Subsystem Command Request p.7718 14 S,H←E Subsystem Command Acknowledge p.77Data Item DictionarySECS II data items Name Format ValueATTRID Attribute ID 20 Attribute nameATTRVAL Attribute value 20 Attribute valueMID Carrier ID MID 2016 to 7E16 (Visible ASCII)DATA Data 20 All characters 00H-0FFHDATALENGTH DataSize 52 Offset designation: 1 to 224Segment designation: Refer to ID Tag Memory Maps page 147.DATASEG DataSeg 20 Offset designation: "00", "01"..."0222", "0223"Segment designation: Refer to ID Tag Memory Maps page 147.STATUS PM information 20 "NE": Normally executed
71CIDRW 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" (communi-cations error).Communications with the Host DeviceCommunicate with the host device only after confirming that the CIDRW Controller has started. Also, unstable signalsmay occur at the host interface when the CIDRW Controller is started. When initializing operation, clear the receptionbuffer at the host device or take other suitable methods to clear unwanted signals. SSACK Result status 20 "NO": Normal"EE": Execution error *3"CE": Communications error"HE": Hardware error *3"TE": Tag error *3List 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
72SECTION 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.
73CIDRW SystemUser’s ManualSECTION 4When SECS Is UsedSECTION 4Reading from/Writing to ID Tags• Set AttributesF18,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.
74SECTION 4When SECS Is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID Tags• Read DataID Tag Memory Maps Refer to page 147.S18,F5 Read Request S,H→E,replyL,31.<TARGETID> "01"-"31"2.<DATASEG>3.<DATALENGTH>• When DATASEG is specified as "0" and a character string, the size of data determined by the DATALENGTH setting is read, starting from the address indicated by the DATASEG setting. If DATALENGTH = 0, data is read up to the end of the data area.• If DATASEG is specified as a character string, a size of data determined by DATALENGTH, starting from the address speci-fied by DATASEG, is read (segment specification).• 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).• In a segment specification, it is not possible to specify a DATALENGTH that exceeds the maximum length of the relevant DATASEG.• In a segment specification, if a DATALENGTH that is under the set length for DATASEG is specified, only the data corre-sponding to 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• In an address specification, if: (SEGMENT + DATALENGTH) ≤ total value for all segments then SSACK = "NO"• In an address specification, if: (SEGMENT + DATALENGTH) > total value for all segments then DATA item length = 0, s = 0, SSACK = "CE" communica-tions error• In a segment specification, if an undefined DATASEG is specified, or if 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.
75CIDRW SystemUser’s ManualSECTION 4When SECS Is UsedSECTION 4Reading from/Writing to ID Tags• Write DataID Tag Memory Maps Refer to page 147.S18,F7 Write Request S,H→E,replyL,41.<TARGETID> "01"-"31"2.<DATASEG>3.<DATALENGTH>4.<DATA>• If DATASEG is specified as "0" and a character string, a size of data corresponding to the DATALENGTH setting and starting from the address within the data area indicated by the DATASEG setting is written (address specification). If DATALENGTH = 0, data is written up to the end of the data area.• If DATASEG is specified as a character string, a size of data determined by DATALENGTH, starting from the address speci-fied by DATASEG, is written (segment specification).• 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).• In a segment specification, it is not possible to specify a DATALENGTH that exceeds the maximum length of the relevant DATASEG.• In a segment specification, if a DATALENGTH that is under the set length for DATASEG is specified, only the data corre-sponding 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• In an address specification, if:(SEGMENT + DATALENGTH) ≤ total value for all segments then SSACK = "NO"• In an address specification, if:(SEGMENT + DATALENGTH) > total value for all segments then DATA item length = 0, s = 0, SSACK = "CE" (communica-tions error)• In a segment specification, if 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.
76SECTION 4When SECS Is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID Tags• Read ID ID Tag Memory Maps Refer to page 147.• Write IDID Tag Memory Maps Refer to page 147.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>• If the MID data contains Non-Visible ASCII code:s = 0, MID item length = 0, SSACK = "EE" execution error• 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.S18,F11 Write ID Request S,H→E,replyL,21.<TARGETID> "01"-"31"2.<MID>• If an MID that is under the length set for the CarrierIDlength attribute is specified, an error occurs and the MID data is not written.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 MID data contains Non-Visible ASCII code:s = 0, SSACK = "EE" execution error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.
77CIDRW SystemUser’s ManualSECTION 4When SECS Is UsedSECTION 4Reading from/Writing to ID Tags• Subsystem Command (ChangeState)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.
78SECTION 4When SECS Is UsedCIDRW SystemUser’s ManualSECTION 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.
79CIDRW SystemUser’s ManualSECTION 4When SECS Is UsedSECTION 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
80SECTION 4When SECS Is UsedCIDRW SystemUser’s ManualSECTION 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
81CIDRW SystemUser’s ManualSECTION 4When SECS Is Not UsedSECTION 4Reading from/Writing to ID TagsWhen SECS Is Not UsedCommand/Response Format■1:N Protocol■1:1 ProtocolMeaning 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.CommandSOH Node No. Command code Parameter FCS CR1 ⋅ ⋅ ⋅ n01h 0DhResponseSOH Node No. Response codeParameter FCS CR1 ⋅ ⋅ ⋅ n01h 0DhCommandCommand code Parameter CR1 ⋅ ⋅ ⋅ n0DhResponseResponse codeParameter CR1 ⋅ ⋅ ⋅ n0Dh
82SECTION 4When SECS Is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsExample: Reading the data of page 1 and page 2 of node No.1CommandCalculation range(ASCII conversion)
83CIDRW SystemUser’s ManualSECTION 4When SECS Is Not UsedSECTION 4Reading from/Writing to ID TagsCommandCommunications with the Host DeviceCommunicate with the host device only after confirming that the CIDRW Controller has started. Also, unstable signalsmay occur at the host interface when the CIDRW Controller is started. When initializing operation, clear the receptionbuffer at the host device or take other suitable methods to clear unwanted signals. The command and response details are given for a 1:N protocol. Just as in the previous command format, thedetails for a 1:1 protocol are the same if the SOH, node number, and FCS are deleted. Command 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.84WRITE 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.85SAME 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.87BYTE 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.88TEST 10 Sends received data to the host device. p.89NAK 12 Sends the response made immediately before again. p.90GET PARAMETER 14 Gets the model number, MAC address, or another parameter. p.90GET LAST COM-MAND15 Gets the command code of the last command that was executed. p.92GET COMMUNICA-TIONS HISTORY16 Gets the history of communications from when the power was turned ON (total num-ber of communications, total successful communications, and total number of failed communications). p.93CLEAR COMMUNI-CATIONS HISTORY17 Clears the communications history. p.94NOISE MEASURE-MENT40 Measures the noise in the vicinity of the CIDRW Head. p.94RESET 7F Resets the Amplifier Unit. p.94Response Code ListType Response code Name DescriptionNormal end 00 Normal end Command execution is completed normally.Host commu-nications error14 Format error There is a mistake in the command format. (For example, the command code is undefined, or the page or address specification is inappropriate.)Communica-tions error70 Communications error Noise or another hindrance occurs during communications 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 A write operation was not completed normally because the ID Tag was in an area in which the ID Tag could be read but not written. 7E ID system error (1) The ID Tag is in a status where it cannot execute command processing.7F ID system error (2) An inapplicable ID Tag has been used.
84SECTION 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 one timeis 16.ID Tag Memory Maps Refer to page 147.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.1Parameter 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 - 210Page Sys - Sys Sys - Sys 17 16 15 14 13 - 8 7 6 5 - 1 Sys SysDesignation 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 to 07 00 to FF 00 to 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
85CIDRW 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 a max-imum of 16 pages at one time.ID Tag Memory Maps Refer to page 147.The response code (when normal: 00) is returned.SOH Node No. Response code Page 1 Page 3 FCS CR01h010012345678901234561122334455667788070DhParameter 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 - 210Page Sys - Sys Sys - Sys 17 16 15 14 13 - 8 7 6 5 - 1 Sys SysDesignation 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 to 07 00 to FF 00 to 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
86SECTION 4When SECS Is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsExample: Writing data to pages 8 and 10 of node No.1The 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
87CIDRW SystemUser’s ManualSECTION 4When SECS Is Not UsedSECTION 4Reading from/Writing to ID Tags■SAME WRITEThis command writes the same data to multiple pages of an ID Tag. Any page(s) can be specified.ID Tag Memory Maps Refer to page 147.The response code (when normal: 00) is returned.Example: Clearing pages 1 to 17 of node No.1 to 0Parameter 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 - 210Page Sys - Sys Sys - Sys 17 16 15 14 13 - 8 7 6 5 - 1 Sys SysDesignation 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 to 07 00 to FF 00 to 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
88SECTION 4When SECS Is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID Tags■BYTE WRITEThis command writes data to any specified number of bytes starting from the address specified in theID 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)ID Tag Memory Maps Refer to page 147.The response code (when normal: 00) is returned.Example: Writing to two bytes starting from address 05h of node No.1The 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 DescriptionFirst address 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
89CIDRW SystemUser’s ManualSECTION 4When SECS Is Not UsedSECTION 4Reading from/Writing to ID Tags■TESTPerforms a communications 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.1SOH 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. (270 characters max.)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
90SECTION 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.■GET PARAMETERThis command gets the model number, firmware version, or another parameter. The response code (00: normal) and received parameter value are returned.* The contents and length of the parameter value depend on the parameter type that is specified for the command. Example 1: Getting the Model Number of Node 1SOH Node No. Command code FCS CR01h 1 2 0DhSOH Node No. Command code Parameter type FCS CR01h 1 4 0DhParameter DescriptionParameter Value DescriptionParameter type 01 Model number02 Firmware version20 Memory status21 Antenna connection statusSOH Node No. Response code Parameter value FCS CR01h 0 0 0DhSOH Node No. Command code Parameter type FCS CR01h 0 1 1 4 0 1 0 5 0DhCommandResponseCommandResponseCommand
91CIDRW SystemUser’s ManualSECTION 4When SECS Is Not UsedSECTION 4Reading from/Writing to ID TagsThe product model number is returned as an ASCII text string. Example 2: Getting the Firmware Version of Node 1The response code (00: normal) and firmware version are returned as a 4-digit decimal number.* The above response is for a firmware version of 1.00. Example 3: Getting the Memory Status of Node 1The response code (00: normal) and memory check results for internal EEPROM are returned. * The above response is for normal memory status. The response will show 00 for error status. SOH Node No. Response code Model number FCS CR01h 0 1 0 0 V640-HAM11 -V3 4 4 0DhSOH Node No. Command code Parameter type FCS CR01h 0 1 1 4 0 2 0 6 0DhSOH Node No. Command code Parameter type FCS CR01h 0 1 1 4 2 0 0 6 0DhSOH Node No. Response code Memory status FCS CR01h0100 0 1 000DhResponseCommandResponseSOH Node No. Response code Firmware version FCS CR01h01 0 0 0100000DhMajor version Minor versionCommandResponse
92SECTION 4When SECS Is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsExample 4: Getting the Antenna Connection Status of Node 1The response code (00: normal) and Antenna connection status are returned.* The above response is for normal Antenna connection status. The response will show 00 for error status. ■GET LAST COMMANDGets the command code of the last command that was executed. This command returns the command code of the last command that was executed. When There Is a Previously Executed Command* The command code is given as two or four characters. When There Is No Previously Executed CommandSOH Node No. Command code Parameter type FCS CR01h 0 1 1 4 2 1 0 7 0DhSOH Node No. Response codeAntenna connec-tion status FCS CR01h0100 0 1 000DhSOH Node No. Command code FCS CR01h 1 5 0DhSOH Node No. Response code Command code FCS CR01h 0 0 0DhSOH Node No. Response codeCommand code FCS CR01h 0 0 0 0 0DhCommandResponseCommandResponse
93CIDRW SystemUser’s ManualSECTION 4When SECS Is Not UsedSECTION 4Reading from/Writing to ID Tags■GET COMMUNICATIONS HISTORYThis command gets the history of communications from when the power was turned ON (total numberof communications, total successful communications, and total number of failed communications). This command returns the history of communications from when the power was turned ON. Four hexadecimaldigits each are returned for the total number of communications, total number of successful communications,and total number of failed communications.If the total number of communications exceeds 65,535, all data in the communications history will be reset to0. Example: Getting the Communications History of Node 1The following response is returned if there are 32,000 total communications, 30,000 successful communications, and2,000 failed communications. SOH Node No. Command code FCS CR01h 1 6 0DhSOH Node No. Response codeTotal number of com-municationsTotal number of suc-cessful communica-tionsTotal number of failed communications FCS CR01h 0 0 0DhSOH Node No. Command code FCS CR01h 0 1 1 6 0 6 0DhSOH Node No. Response codeTotal number of com-municationsTotal number of suc-cessful communica-tionsTotal number of failed communications FCS CR01h 0 1 0 0 7D00753007D0 0 0 0DhCommandResponseCommandResponse
94SECTION 4When SECS Is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID Tags■CLEAR COMMUNICATIONS HISTORYThis command clears the communications history. ■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 communications distance Refer to page 146.■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 7 0DhSOH Node No. Response code FCS CR01h 0 0 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 5Troubleshooting95CIDRW SystemUser’s ManualSECTION 5TroubleshootingWhen SECS Is Used 96When SECS Is Not Used 102
96SECTION 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 indicators on the front of the Controllerlight.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 in AlarmStatus of the CIDRW system is Alarm (1). BUSY (green) Lit when the status in OperationalStatus 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.
97CIDRW SystemUser’s ManualSECTION 5When SECS Is UsedSECTION 5TroubleshootingOperation Check Flowchart■Normal Operation Mode• Operating Normally in the Normal Operation ModeIndicatorsPOWER OPERATING ALARMS BUSY ERRORResponseResponse FunctionS F— — SSACK="NO"Response to messagetransmission(SSNAK = other than“NO”)?Error occurrenceAll indicators litor flashing?POWER indicator 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 98.Yes An error has occurred at the CIDRW Controller.Check the status of the indicators.When all the indicators are lit or flashing Refer to page 98.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 99.When an Error Unrelated to Message Transmission and Responses Occurs Refer to page 99.
98SECTION 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 Indicators 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 80.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 systems• When the ID read command is executed, the carrier ID contains non-visible ASCII code.HE • 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.
99CIDRW 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 communica-tions 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)
100SECTION 5When SECS Is UsedCIDRW SystemUser’s ManualSECTION 5Troubleshooting■Setting Mode• Operating Normally in the Setting modeTerminal Initial Display of the Host Device after Startup in the Setting modeTerminal Display When Parameter Setting Has Been Completed without ErrorIndicatorsPOWER OPERATING ALARMS BUSY ERRORError occurrenceAll indicators litor flashing?POWER indicator OFF?NoYesNoYesAn 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 indicators are lit or flashing Refer to page101.Check if the CIDRW Controller settings are correct.When the CIDRW Controller fails to respond to messages sent to it Refer to page 101.When an Error Unrelated to Message Transmission and Responses Occurs Refer to page 101.SETUP_START <L22 ><XXX.XX, YYY.YY>_Software Revision LevelModel numberHardware Revision LevelSETUP_COMPLETE_
101CIDRW SystemUser’s ManualSECTION 5When SECS Is UsedSECTION 5Troubleshooting• When All the Indicators Are Lit or FlashingAn error has occurred in the CIDRW Controller. After taking appropriate corrective action, restart the CIDRW 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 appropriate corrective 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 appropriate corrective 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 appropriate corrective action, restart the CIDRW Controller and Amplifier Unit and checkthe 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 correct? 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 communica-tions 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?)
102SECTION 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 MessagesAmplifier Unit IndicatorsType Response code Name DescriptionHost communi-cations error14 Format error There is a mistake in the command format. (For example, the com-mand portion is undefined, or the page or address specification is inappropriate.)Communications error between the CIDRW Head and ID Tag70 Communications errorNoise or another hindrance has occurred during communications 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 communications with the host device, or during communications with an ID Tag.
103CIDRW 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 indicator OFF?NoYes An error has occurred at the Amplifier Unit.Amplifier Unit error Refer to page 104.Check if the Amplifier Unit settings are correct.If There Is No Response to the Command: Refer to page 104.Response received? Yes Check the nature of the response.If there is a response to the command Refer to page 104.No(Lights once)
104SECTION 5When SECS Is Not UsedCIDRW SystemUser’s ManualSECTION 5Troubleshooting• Amplifier Unit ErrorCheck the status of the indicators 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 indicators after transmission of the test command.After taking appropriate corrective action, restart the Amplifier Unit, send the test command again andcheck again.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. When using a USB-serial adapter, direct control of the RS signal may not bepossible. Test operation in advance to make sure direct control of the RS signal is correct. • If There Is a Response to the Command:Check the status of the indicators 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-tors 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• Amplifier Unit node number setting (More than one Amplifier Unit may be set to the same node number.) • 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.(Lights once)SD at host deviceRS at host deviceON only during data transmission from the host deviceWithin 15 ms
105CIDRW SystemUser’s ManualSECTION 5When SECS Is Not UsedSECTION 5TroubleshootingThere is a mistake in the command format (number of charac-ters, character code, etc.).RUN COMM NORM ERROR Main check points(Lights once)
106SECTION 5When SECS Is Not UsedCIDRW SystemUser’s ManualSECTION 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 103.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 107.Yes Communications with the ID Tag has failed.If the response code is 7 Refer to page 107.Write command sentRUN indicator OFF?NoYes An error has occurred at the Amplifier Unit.Amplifier Unit error Refer to page 107.Is the response code 7 ?Communications OKNo(Lights once)(Lights once)
107CIDRW SystemUser’s ManualSECTION 5When SECS Is Not UsedSECTION 5Troubleshooting• Amplifier Unit ErrorCheck the status of the indicators after transmission of the command. After taking appropriate correc-tive 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 indicators 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 communications between the CIDRW Head and ID Tag.Check the status of the indicators 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-tors 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)
108SECTION 5When SECS Is Not UsedCIDRW SystemUser’s ManualSECTION 5TroubleshootingMEMO
SECTION 6Appendix109CIDRW SystemUser’s ManualSECTION 6AppendixSpecifications and Dimensions 110System Configuration Examples 115When SECS Is Not Used 116Characteristic Data According to Conditions of Use 117ID Tag Memory Maps 147Regular Inspection 148SECS Protocol Specifications 149ASCII Code Table 154Protective Construction 155
110SECTION 6Specifications and DimensionsCIDRW SystemUser’s ManualSECTION 6AppendixSpecifications and DimensionsControllerV700-L22 Item 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% Storage: 10% to 95% (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. 580 g15016728130315130P6X3130±0.2151±0.24-M4247(1:2)4-φ4.5 (Unit: mm)Mounting dimensionsPower indicatorOperation indicators(mounting holes)Four, 4.5-dia. holes
CIDRW SystemUser’s ManualSECTION 6Specifications and DimensionsSECTION 6Appendix111Amplifier UnitsV640-HAM11-V3 and V640-HAM11-LItem SpecificationsV640-HAM11-V3 V640-HAM11-LPower supply voltage 24 VDC +10% -15%Current consumption 150 mA max. 400 mA max.Ambient temperature Operating: 0 to +40°C Storage: -15 to +65°C (with no icing)Ambient humidity Operating/Storage: 35% to 85% (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 PC/ABS resinShape 80×185×43 mm (W×D×H)Weight Approx. 250 gCIDRW Head V640-HS61 V640-HS6216017518555.54656806.86.86.80.6(4.2)(1)(11.5)(32.5)435(5.7)(13)(17.75)(12)(32.5)(30.2)(15.8)(12)(18.2)(22.5)4-M4175±0.546±0.5DIP switch(Unit: mm)Mounting dimensionsFour, 4.5-dia. holesDC power supply connectorRS-485 connectorRS-232C connectorFour operation indicators
112SECTION 6Specifications and DimensionsCIDRW SystemUser’s ManualSECTION 6AppendixCIDRW HeadsV640-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% (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 cableCoaxial 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 6Appendix113V640-HS62Item 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% (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. 100 gCable length 1.9 mCable specification 3-mm-dia. coaxial cable3020121096539.221Max.281244914.5Max.20.5921±0.220±0.2Ferrite core(Unit: mm)ConnectorCoaxial cable, Dia.: 3.0, Length: 1.9 mCenter of coilMounting Hole DimensionsFour M3 or 3.5-dia. holesFour 3.5-dia. (mounting holes)Center of coil
114SECTION 6Specifications and DimensionsCIDRW SystemUser’s ManualSECTION 6AppendixLink 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% (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 g6541106035.218.526.541.520.341.310.716.7555±0.2100±0.242-φ4.52-M4 OR φ4.2(Unit: mm)Mounting dimensionsTwo M4 or 4.2-dia. holesTwo, 4.5-dia. holes
CIDRW SystemUser’s ManualSECTION 6System Configuration ExamplesSECTION 6Appendix115System Configuration Examples When SECS Is UsedCommunications with the host device is possible using the SECS protocol.With the above system configuration, the Amplifier Unit connected directly to the CIDRW Controllerconverts signals from RS-232C to RS-485. If this Amplifier Unit is removed, communications will not bepossible with the other Amplifier Units. If the Amplifier Unit connected directly to the CIDRW Controllermust be removed while the system is operating, insert a Link Unit (V700-L11) between the CIDRWController and the first Amplifier Unit. If an Amplifier Unit on the end of the network is removed, be sureto turn ON the terminating resistance on the Amplifier Unit that will end up on the end of the networkwhile the Amplifier Unit is removed. HostThe CIDRW Heads are theantennas for reading the car-rier IDs from the ID Tags andwriting the carrier IDs.The Amplifier Units con-trol the CIDRW Heads. Up to 31 Units can beconnected.This is a host computer,equipment controller, etc.CIDRW HeadV640-HS61V640-HS62Amplifier UnitV640-HAM11-V3V640-HAM11-LCIDRW ControllerV700-L22Multiple Amplifier Units are controlled in response to commands (SECS) from the host device.RS-232CSECS I/II50 m max.RS-485RS-232CRS-232CSECS I/IIRS-232CLink UnitV700-L11Just the relevant Amplifier Unit can be removed and replaced while the powerremains on.50 m max.RS-485Up to 31 Units can be connected.
116SECTION 6System Configuration ExamplesCIDRW SystemUser’s ManualSECTION 6Appendix 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.With the above system configuration, the Amplifier Unit connected directly to the CIDRW Controllerconverts signals from RS-232C to RS-485. If this Amplifier Unit is removed, communications will not bepossible with the other Amplifier Units. If the Amplifier Unit connected directly to the CIDRW Controllermust be removed while the system is operating, insert a Link Unit (V700-L11) between the CIDRWController and the first Amplifier Unit. If an Amplifier Unit on the end of the network is removed, be sureto turn ON the terminating resistance on the Amplifier Unit that will end up on the end of the networkwhile the Amplifier Unit is removed.HostThe CIDRW Heads are theantennas for reading the car-rier IDs from the ID Tags andwriting the carrier IDs.The Amplifier Units con-trol the CIDRW Heads. Up to 31 Units can beconnected.This is a host com-puter, equipmentcontroller, etc.Amplifier UnitsV640-HAM11-V3V640-HAM11-LRS-232COMRON original protocol50 m max.CIDRW HeadsV640-HS61V640-HS62RS-48550 m max.Link 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
CIDRW SystemUser’s ManualSECTION 6Characteristic Data According to Conditions of UseSECTION 6Appendix117Characteristic Data According to Conditions of UseMaps of Communications Areas (Reference Only)The figures given below for communications areas (communications distances) are reference valuesonly. The maps of communications areas will vary according to the ID Tags that you use, the back-ground metals, the ambient noise, the effects of temperature and so on, and should be thoroughly con-firmed on installation. The direction of the ID Tags will affect communications performance. Check thedirection of the coils in the ID Tags before using the ID Tags.■V640-HAM11-V3• Coaxial Mounting (RI-TRP-DR2B)• READ• WRITE0102030405060708090100-80 -70 -60 -50 -40 -30 -20 -10 0 10 20 30 40 50 60 70 80Communications Area (READ)Distance in Y direction (mm)Distance in X direction (mm)Measurement point0102030405060708090100-80 -70 -60 -50 -40 -30 -20 -10 0 10 20 30 40 50 60 70 80Communications Area (WRITE)Distance in Y direction (mm)Distance in X direction (mm)Measurement point
118SECTION 6Characteristic Data According to Conditions of UseCIDRW SystemUser’s ManualSECTION 6Appendix• Coaxial Mounting (RI-TRP-DR2B)• READ• WRITE0102030405060708090100-80 -70 -60 -50 -40 -30 -20 -10 0 10 20 30 40 50 60 70 80Communications Area (READ)Distance in Z direction (mm)Measurement pointDistance in Y direction (mm)0102030405060708090100-80 -70 -60 -50 -40 -30 -20 -10 0 10 20 30 40 50 60 70 80Communications Area (WRITE)Distance in Z direction (mm)Measurement pointDistance in Y direction (mm)

Navigation menu