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

Download:
Mirror Download [FCC.gov]
Document ID	1350843
Application ID	S/qiJBYbyIoeb8IQrEOE1w==
Document Description	User manual2& 65288;V3)
Short Term Confidential	No
Permanent Confidential	No
Supercede	No
Document Type	User Manual
Display Format	Adobe Acrobat PDF - pdf
Filesize	73.68kB (921007 bits)
Date Submitted	2010-09-29 00:00:00
Date Available	2010-09-30 00:00:00
Creation Date	2010-09-17 16:56:45
Producing Software	Acrobat Distiller 8.1.0 (Windows)
Document Lastmod	2010-09-17 16:57:04
Document Title	Z307-E1-01
Document Creator	FrameMaker 7.0
Document Author:	OMRON

SECTION 4
Reading from/Writing to ID Tags
When SECS Is Used
70
72
Get Attributes
72
Set Attributes
73
Read Data
74
Write Data
75
Read ID
76
Write ID
76
Subsystem Command (ChangeState)
77
Subsystem Command (GetStatus)
78
Subsystem Command (PerformDiagnostics)
78
Subsystem Command (Reset)
79
When SECS Is Not Used
81
READ
84
WRITE
85
SAME WRITE
87
BYTE WRITE
88
TEST
89
NAK
90
GET PARAMETER
90
GET LAST COMMAND
92
GET COMMUNICATIONS HISTORY
93
CLEAR COMMUNICATIONS HISTORY
94
NOISE MEASUREMENT
94
RESET
94
CIDRW System
User’s Manual
SECTION 4 Reading from/Writing to ID Tags
Online Check
69
SECTION 4
Reading from/Writing to ID Tags
When SECS Is Used
The 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 Specifications
List of Messages Used
SECTION 4 When SECS Is Used
Classification
General purpose
messages
CIDRW system
messages
18
18
Direction
SECS II names
See
S,H→E,reply
Are You There Request
p.72
S,H←E
On Line Data
p.72
S,H→E,reply
Read Attribute Request
p.72
S,H←E
Read Attribute Data
p.72
18
S,H→E,reply
Write Attribute Request
p.73
18
S,H←E
Write Attribute Acknowledge
p.73
18
S,H→E,reply
Read Request
p.74
18
S,H←E
Read Data
p.74
18
S,H→E,reply
Write Request
p.75
18
S,H←E
Write Acknowledge
p.75
18
S,H→E,reply
Read ID Request
p.76
18
10
S,H←E
Read ID Data
p.76
18
11
S,H→E,reply
Write ID Request
p.76
18
12
S,H←E
Write ID Acknowledge
p.76
18
13
S,H→E,reply
Subsystem Command Request
p.77
18
14
S,H←E
Subsystem Command Acknowledge
p.77
List of Error Messages
Refer to page 96.
Data Item Dictionary
SECS II data items
70
Name
Format
Value
ATTRID
Attribute ID
20
Attribute name
ATTRVAL
Attribute value
20
Attribute value
MID
Carrier ID
DATA
Data
20
All characters 00H-0FFH
DATALENGTH
DataSize
52
Offset designation: 1 to 224
Segment 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
CIDRW System
User’s Manual
MID
2016 to 7E16 (Visible ASCII)
SECTION 4
Reading from/Writing to ID Tags
Data Item Dictionary
SECS II data items
Name
SSACK
Result status
List of STATUS
Status
Format
20
L,4
1.
2.
3.
4. *2
Value
"NO":
"EE":
"CE":
"HE":
"TE":
Normal
Execution error *3
Communications error
Hardware error *3
Tag error *3
The STATUS values are included in the PM information.
State request
20
"OP", "MT", "PS" *1
TARGETID
Target ID
20
"00"-"31"
"00" indicates the CIDRW Controller itself.
SSCMD
Subsystem commands
20
"ChangeState"
"GetStatus"
"PerformDiagnostics"
"Reset"
*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 Responses
An 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 insufficient or too many items. If other problems relating to the item contents arise, the response is SSACK = "CE" (communi-
SECTION 4 When SECS Is Used
CPVAL
cations error).
Communications with the Host Device
Communicate with the host device only after confirming that the CIDRW Controller has started. Also, unstable signals
may occur at the host interface when the CIDRW Controller is started. When initializing operation, clear the reception
buffer at the host device or take other suitable methods to clear unwanted signals.
CIDRW System
User’s Manual
71
SECTION 4
Reading from/Writing to ID Tags
■ Specifications for Each Stream/Function
• Online Check
S1,F1
Are You There Request
S,H→E,reply
Header only
S1,F2
On Line Data
S,H←E
L,2
1.
2.
• Set MDLN (model number).
• Set SOFTREV (software revision level).
SECTION 4 When SECS Is Used
• Get Attributes
S18,F1
Read Attribute Request
S,H→E,reply
1.
"00"-"31"
L,2
2.L,n
1.
⋅
n.
• The setting for reading all attributes (CIDRW Controller or Heads) is n = 0.
S18,F2
Read Attribute Data
S,H←E
1.
"00"-"31"
L,4
2.
3.L,n
1.
⋅
n.
4.L,s
1.
⋅
s.
• 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.
72
CIDRW System
User’s Manual
SECTION 4
Reading from/Writing to ID Tags
• Set Attributes
F18,F3
Write Attribute Request
S,H→E,reply
1.
"00" (fixed)
L,2
2.L,n
1.L,2
1.
2.
n.L,2
1.
2,
Since the attributes for Heads are all RO in this system, the target ID is fixed as “00”.
Write Attribute Acknowledge
S,H←E
1.
"00" (fixed)
SECTION 4 When SECS Is Used
S18,F4
L,3
2.
3.L,s
1.
⋅
s.
• 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.
CIDRW System
User’s Manual
73
SECTION 4
Reading from/Writing to ID Tags
• Read Data
S18,F5
Read Request
S,H→E,reply
1.
"01"-"31"
L,3
2.
3.
SECTION 4 When SECS Is Used
• 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 specified 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 corresponding to specified DATALENGTH is read.
ID Tag Memory Maps
S18,F6
Refer to page 147.
Read Data
S,H→E,reply
1.
"01"-"31"
L,4
2.
3.
4.L,s
1.
⋅
s.
• 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" communications 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.
74
CIDRW System
User’s Manual
SECTION 4
Reading from/Writing to ID Tags
• Write Data
S18,F7
Write Request
S,H→E,reply
1.
"01"-"31"
L,4
2.
3.
4.
ID Tag Memory Maps
S18,F8
Refer to page 147.
Write Acknowledge
S,H←E
1.
"01"-"31"
L,3
SECTION 4 When SECS Is Used
• 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 specified 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 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.
2.
3.L,s
1.
⋅
s.
• 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" (communications 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.
CIDRW System
User’s Manual
75
SECTION 4
Reading from/Writing to ID Tags
• Read ID
S18,F9
Read ID Request
S,H→E,reply
1.
"01"-"31"
ID Tag Memory Maps
S18,F10
Refer to page 147.
Read ID Data
S,H←E
1.
"01"-"31"
L,4
2.
3.
4.L,s
1.
SECTION 4 When SECS Is Used
⋅
s.
• 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.
• Write ID
S18,F11
Write ID Request
S,H→E,reply
1.
"01"-"31"
L,2
2.
• 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.
ID Tag Memory Maps
S18,F12
Refer to page 147.
Write ID Acknowledge
S,H←E
1.
"01"-"31"
L,3
2.
3.L,s
1.
⋅
s.
• 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.
76
CIDRW System
User’s Manual
SECTION 4
Reading from/Writing to ID Tags
• Subsystem Command (ChangeState)
S18,F13
Subsystem Command Request (ChangeState)
S,H→E,reply
1.
"00" (fixed)
2.
"ChangeState"
L,3
3.L,1
1.
"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←E
1.
"00"
L,3
SECTION 4 When SECS Is Used
2.
3.L,s
1.
⋅
s.
• 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.
CIDRW System
User’s Manual
77
SECTION 4
Reading from/Writing to ID Tags
• Subsystem Command (GetStatus)
S18,F13
Subsystem Command Request (GetStatus)
S,H→Ε,reply
1.
"00"-"31"
2.
"GetStatus"
L,3
3.L,0
S18,F14
Subsystem Command Acknowledge (GetStatus)
S,H←E
1.
"00"-"31"
2.
"GetStatus"
L,3
3.L,s
1.
SECTION 4 When SECS Is Used
⋅
s.
• 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.
• Subsystem Command (PerformDiagnostics)
S18,F13
Subsystem Command Request (PerformDiagnostics)
S,H→E,reply
L,3
1.
"00"-"31"
2.
"PerformDiagnostics"
3.L,0
S18,F14
Subsystem command Acknowledge (PerformDiagnostics)
S,H←E
1.
"00"-"31"
L,3
2.
3.L,s
1.
⋅
s.
• 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.
78
CIDRW System
User’s Manual
SECTION 4
Reading from/Writing to ID Tags
• Subsystem Command (Reset)
S18,F13
Subsystem Command Request (Reset)
S,H→E,reply
L,3
1.
"00" (fixed)
2.
"Reset"
3.L,0
S18,F14
Subsystem Command Acknowledge (Reset)
S,H←E
1.
"00"
L,3
2.
3.L,0
SECTION 4 When SECS Is Used
• When the specified target is invalid:
SSACK = “CE” communications error
• When SSCMD is invalid:
SSACK = “CE” communications error
CIDRW System
User’s Manual
79
SECTION 4
Reading from/Writing to ID Tags
■ Operation Conditions
The response messages and response codes (SSACK) in each state are shown below.
State
Message
SECTION 4 When SECS Is Used
80
Function
S1,F1
OnlineRequest
S18,F11
S18,F7
Initializing
Operating
IDLE
Maintenance
BUSY
S1,F0
S1,F2
S1,F2
S1,F2
WriteID
S18,F0
S18,F0
S18,F0
NO
WriteData
S18,F0
NO
NO
S18,F0
S18,F3
SetAttribute
S18,F0
NO
NO
NO
S18,F13(Reset)
Reset
S18,F0
NO
NO
NO
S18,F9
ReadID
S18,F0
NO
NO
NO
S18,F5
ReadData
S18,F0
NO
NO
S18,F0
S18,F13(PerformDiagnostics)
Diagnostics
S18,F0
NO
NO
NO
S18,F13(GetStatus)
GetStatus
S18,F0
NO
NO
NO
S18,F1
GetAttribute
S18,F0
NO
NO
NO
S18,F13(ChangeState)
ChangeState(to MT)
S18,F0
NO
S18,F0
S18,F0
S18,F13(ChangeState)
ChangeState(to OP)
S18,F0
S18,F0
S18,F0
NO
S18,F13(ChangeState)
ChangeState(to PS)
S18,F0
NO
S18,F0
NO
CIDRW System
User’s Manual
SECTION 4
Reading from/Writing to ID Tags
When SECS Is Not Used
Command/Response Format
■ 1:N Protocol
Command
SOH
Node No.
Parameter
Command code
⋅⋅⋅
FCS
01h
CR
0Dh
SOH
Parameter
Response
code
Node No.
⋅⋅⋅
FCS
01h
SECTION 4 When SECS Is Not Used
Response
CR
0Dh
■ 1:1 Protocol
Command
Command code
Parameter
⋅⋅⋅
CR
0Dh
Response
Response
code
Parameter
⋅⋅⋅
CR
0Dh
Meaning of FCS (frame check sequence)
This is two ASCII code characters obtained by conversion from the 8-bit exclusive logical sum (EOR) of the characters
from the character immediately after SOH to the character immediately before FCS.
CIDRW System
User’s Manual
81
SECTION 4
Reading from/Writing to ID Tags
Example: Reading the data of page 1 and page 2 of node No.1
Command
Calculation range
SECTION 4 When SECS Is Not Used
82
(ASCII conversion)
CIDRW System
User’s Manual
SECTION 4
Reading from/Writing to ID Tags
Command
Command Code List
Name
Value
Function
See
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.84
WRITE
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.85
SAME 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.87
BYTE 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.88
TEST
10
Sends received data to the host device.
p.89
NAK
12
Sends the response made immediately before again.
p.90
GET PARAMETER
14
Gets the model number, MAC address, or another parameter.
p.90
GET LAST COMMAND
15
Gets the command code of the last command that was executed.
p.92
GET COMMUNICA- 16
TIONS HISTORY
Gets the history of communications from when the power was turned ON (total num- p.93
ber of communications, total successful communications, and total number of failed
communications).
CLEAR COMMUNI- 17
CATIONS HISTORY
Clears the communications history.
p.94
NOISE MEASUREMENT
40
Measures the noise in the vicinity of the CIDRW Head.
p.94
RESET
7F
Resets the Amplifier Unit.
p.94
SECTION 4 When SECS Is Not Used
READ
Response Code List
Type
Normal end
Response
code
00
Name
Description
Normal end
Command execution is completed normally.
Host commu- 14
nications error
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.)
Communications error
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.
70
Communications with the Host Device
Communicate with the host device only after confirming that the CIDRW Controller has started. Also, unstable signals
may occur at the host interface when the CIDRW Controller is started. When initializing operation, clear the reception
buffer 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, the
details for a 1:1 protocol are the same if the SOH, node number, and FCS are deleted.
CIDRW System
User’s Manual
83
SECTION 4
Reading from/Writing to ID Tags
■ READ
Reads any pages of data from the ID Tag. The maximum number of pages that can be read at one time
is 16.
Command
SOH
Node No.
Command code
01h
Bit
Page
Sys
Designation
0*
0*
Value
Sys Sys
0*
Page designation (8 characters)
FCS
0Dh
Sys
17
16
15
14
13
0*
0*
0/1
0/1
0/1
0/1
0/1
•••
0/1
0/1
0/1
0/1
•••
0/1
00
CR
00 to 07
00 to FF
Sys Sys
0*
0*
00 to FC
SECTION 4 When SECS Is Not Used
* Always specify 0. If you specify 1 an error (Response code: 14) will occur.
Parameter Description
Parameter
Description
Page 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.
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 of
page numbers.
Response
Read data
SOH
Response
code
Node No.
Page n
⋅⋅⋅
Data 1
01h
Page m (n
Model number
Software Revision Level
Hardware Revision Level
Terminal Display When Parameter Setting Has Been Completed without Error
SETUP_COMPLETE
100
Refer to page
CIDRW System
User’s Manual
SECTION 5
Troubleshooting
• When All the Indicators Are Lit or Flashing
An error has occurred in the CIDRW Controller.
After taking appropriate corrective action, restart the CIDRW Controller 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.
• When the CIDRW Controller Responds to a Message Transmission
There is a mistake in the CIDRW Controller settings or the sent parameters.
POWER
OPERATING
ALARMS
BUSY
ERROR
Main check points
• Sent parameters (Are the parameters correct?
Are the settings correct?)
Response
SETUP_FAILED [
Contents
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].
• When the CIDRW Controller Fails to Respond To Messages Sent to It
SECTION 5 When SECS Is Used
After taking appropriate corrective action, restart the CIDRW Controller and check the indicators.
There 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.
POWER
OPERATING
ALARMS
BUSY
ERROR
Main check points
• Transmission parameters (Are the parameters
correct?)
• Communications conditions for communications between the CIDRW Controller and the
host device (baud rate, character composition,
etc.)
• Mode switch setting (Is the setting 3?)
• When an Error Unrelated to Message Transmission and Responses Occurs
There 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 check
the indicators.
POWER
OPERATING
ALARMS
BUSY
ERROR
Main check points
• Mode switch setting (Is the setting 3?)
CIDRW System
User’s Manual
101
SECTION 5
Troubleshooting
When SECS Is Not Used
Errors are indicated by the presence or absence of a response to an Amplifier Unit command, and by the
indicators.
List of Error Messages
Type
Host communications error
14
Name
Description
SECTION 5 When SECS Is Not Used
Format error
There is a mistake in the command format. (For example, the command portion is undefined, or the page or address specification is
inappropriate.)
Communications
error
Noise or another hindrance has occurred during communications with
an ID Tag, and communications cannot be completed normally.
Verification error
Correct data cannot be written to an ID Tag.
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
The 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 processing.
7F
ID system error (2)
An inapplicable ID Tag has been used.
Communications 70
error between
the CIDRW Head 71
and ID Tag
72
Amplifier Unit Indicators
Name
102
Response
code
Indications
RUN (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.
CIDRW System
User’s Manual
SECTION 5
Troubleshooting
Operation Check Flowchart
■ From Installation to Trial Operation
Errors are indicated by whether or not a response to the test command is received and by the status of
the Amplifier Unit indicators.
Error occurrence
RUN indicator
Yes
An error has occurred at the Amplifier Unit.
Amplifier Unit error
OFF?
Refer to page 104.
No
SECTION 5 When SECS Is Not Used
Test command transmission
Response received?
Yes
Check the nature of the response.
If there is a response to the command
Refer to page 104.
No
Check if the Amplifier Unit settings are correct.
If There Is No Response to the Command:
Refer to page 104.
• If the Test Command Was Received Normally:
Indicators
RUN
COMM
NORM
ERROR
(Lights once)
Response Code for the Response
Type
Normal
Response
code
00
Function
The command was received normally.
CIDRW System
User’s Manual
103
SECTION 5
Troubleshooting
• Amplifier Unit Error
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 and
check again.
RUN
COMM
NORM
ERROR
—
Main check points
• Influence of background noise (change installation position)
• Amplifier Unit power supply
(If RUN is OFF, the status of the other indicaIf the error cannot be resolved after checking, the Amplifier Unit
tors can be ignored.)
may be damaged.
• 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 and
check again.
RUN
COMM
NORM
ERROR
Main check points
SECTION 5 When SECS Is Not Used
• 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.
(Lights once)
• 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 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 as
CS signals. Turn the RS signals OFF within 15 ms after the completion of data transmission. Correct communications
will not be possible without this control. When using a USB-serial adapter, direct control of the RS signal may not be
possible. Test operation in advance to make sure direct control of the RS signal is correct.
ON only during data transmission from the host device
RS at host device
SD at host device
Within 15 ms
• 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 and
check again.
RUN
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.
104
CIDRW System
User’s Manual
SECTION 5
Troubleshooting
RUN
COMM
NORM
ERROR
Main check points
There is a mistake in the command format (number of characters, character code, etc.).
(Lights once)
SECTION 5 When SECS Is Not Used
CIDRW System
User’s Manual
105
SECTION 5
Troubleshooting
■ From Trial Operation to Communications
Errors are indicated by the status of the indicators after transmission of the write command, and by the
response code of the response.
Error occurrence
Write command sent
An error has occurred at the Amplifier Unit.
Yes
RUN indicator
Amplifier Unit error
OFF?
Refer to page 107.
No
SECTION 5 When SECS Is Not Used
Is the response
code 1
Check the command format.
Yes
If the response code is 1
No
Is the response
code 7
Yes
Communications with the ID Tag has failed.
If the response code is 7
No
Communications OK
• If the ID Tag Was Processed Normally:
Indicators
RUN
COMM
NORM
ERROR
(Lights once)
(Lights once)
Response Code for the Response
Response
code
Type
Normal
00
Function
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.
106
Refer to page 107.
CIDRW System
User’s Manual
Refer to page 103.
Refer to page 107.
SECTION 5
Troubleshooting
• Amplifier Unit Error
Check the status of the indicators after transmission of the command. After taking appropriate corrective action, send the write command again and check again.
RUN
COMM
NORM
ERROR
—
Main check points
• Influence of background noise (Change installation position)
• Amplifier Unit power supply
(If RUN is OFF, the status of the other indicators can be ignored.)
If the error cannot be resolved by checking the two points above,
the Amplifier Unit may be damaged.
• 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 the
command. After taking appropriate corrective action, send the write command again and check again.
RUN
COMM
NORM
ERROR
(Lights once)
14
Main check points
Command format
(Command code, page designation, address designation, processed data volume, etc.)
• 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 the
command.After taking appropriate corrective action, send the write command again and check again.
RUN
COMM
(Lights once)
Response
code
NORM
ERROR
(Lights once)
Main check points
70
• 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
•
•
•
•
7B
• 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
SECTION 5 When SECS Is Not Used
Response
code
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 Head
* The ID Tag has a lock function, but the Amplifier Unit has no function for locking an ID Tag.
CIDRW System
User’s Manual
107
SECTION 5
Troubleshooting
MEMO
SECTION 5 When SECS Is Not Used
108
CIDRW System
User’s Manual
SECTION 6
Appendix
110
System Configuration Examples
115
When SECS Is Not Used
116
Characteristic Data According to Conditions of Use
117
ID Tag Memory Maps
147
Regular Inspection
148
SECS Protocol Specifications
149
ASCII Code Table
154
Protective Construction
155
CIDRW System
User’s Manual
SECTION 6 Appendix
Specifications and Dimensions
109
SECTION 6
Appendix
Specifications and Dimensions
Controller
V700-L22
(Unit: mm)
150
130
28
Mounting dimensions
(1:2)
130±0.2
Power indicator
151±0.2
151
167
4-M4
24
Operation indicators
SECTION 6 Specifications and Dimensions
110
30
P6X3
Item
(mounting
Four,
4.5-dia.
holesholes)
4-φ4.5
Specifications
Power 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 terminal
Vibration 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 directions
Shock resistance
Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitions
Ground
Ground to 100 Ω or less.
Case material
SECC (coating)
Weight
Approx. 580 g
CIDRW System
User’s Manual
SECTION 6
Appendix
Amplifier Units
V640-HAM11-V3 and V640-HAM11-L
(30.2)
(15.8)
DC power supply connector
(Unit: mm)
Four operation indicators
(18.2)
55.5
(32.5)
(22.5) (12)
46
56
80
0.6 6.8 6.8 6.8
(13)
(12) (17.75)
RS-485 connector
160
175
185
RS-232C connector
DIP switch
Four, 4.5-dia. holes
(11.5)
(4.2)
(5.7)
(32.5)
43
(1)
SECTION 6 Specifications and Dimensions
Mounting dimensions
46±0.5
175±0.5
4-M4
Specifications
Item
V640-HAM11-V3
Power supply voltage
24 VDC +10% -15%
Current consumption
150 mA max.
V640-HAM11-L
400 mA max.
Ambient temperature
Operating: 0 to +40°C
Ambient humidity
Operating/Storage: 35% to 85% (with no condensation)
Storage: -15 to +65°C (with no icing)
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 terminal
Vibration 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 directions
Shock resistance
Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitions
Ground
Ground to 100 Ω or less.
Case material
PC/ABS resin
Shape
80×185×43 mm (W×D×H)
Weight
Approx. 250 g
CIDRW Head
V640-HS61
V640-HS62
CIDRW System
User’s Manual
111
SECTION 6
Appendix
CIDRW Heads
V640-HS61
(Unit: mm)
Four, 3.5-dia. holes
Antenna center
Coaxial cable 3.0 dia., standard length 2 m
Connector
Mounting dimensions
Four M3 or 3.5-dia. holes
SECTION 6 Specifications and Dimensions
112
Antenna center
Item
Transmission frequency
Specifications
134 kHz
Ambient temperature
Operating: 0 to +40°C
Ambient humidity
Operating/Storage: 35% to 85% (with no condensation)
Storage: -15 to +65°C (with no icing)
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 case
Vibration 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 directions
Shock resistance
Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitions
Casing material
ABS/epoxy resin
Stainless steel mount
Weight
Approx. 70 g
Cable length
2m
Cable specification
3-mm-dia. coaxial cable
CIDRW System
User’s Manual
SECTION 6
Appendix
V640-HS62
(Unit: mm)
Four 3.5-dia. (mounting holes)
Connector
Max.28
30
20
12
10
Coaxial cable, Dia.: 3.0, Length: 1.9 m
Center of coil
21
39.2
65
Ferrite core
Max.20.5
12
14.5
49
Mounting Hole Dimensions
Center of coil
Item
Specifications
Transmission frequency
134 kHz
Ambient temperature
Operating: 0 to +40°C
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 case
Vibration 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 directions
Shock resistance
Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitions
Casing material
ABS/epoxy resin
Stainless steel mount
Weight
Approx. 100 g
Cable length
1.9 m
Cable specification
3-mm-dia. coaxial cable
Storage: -15 to +65°C (with no icing)
CIDRW System
User’s Manual
SECTION 6 Specifications and Dimensions
21±0.2
20±0.2
Four M3 or 3.5-dia. holes
113
SECTION 6
Appendix
Link Unit
V700-L11
(Unit: mm)
110
35.2
16.7
10.7
41.3
20.3
Two,
4.5-dia. holes
2-φ4.5
65
41.5
26.5
18.5
60
SECTION 6 Specifications and Dimensions
114
55±0.2
Mounting dimensions
100±0.2
Item
Power supply voltage
Two M4
4.2-dia. holes
2-M4
OR or
φ4.2
Specifications
24 VDC +10% -15%
Current consumption
250 mA max. (inrush current: approx. 10 A)
Ambient temperature
Operating: 0 to +40°C
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 terminal
Vibration 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 directions
Shock resistance
Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitions
Ground
Ground to 100 Ω or less.
Case material
PC/ABS resin
Weight
Approx. 200 g
CIDRW System
User’s Manual
Storage: -15 to +50°C (with no icing)
SECTION 6
Appendix
System Configuration Examples
When SECS Is Used
Communications with the host device is possible using the SECS protocol.
CIDRW Controller
V700-L22
Host
RS-232C
SECS I/II
This is a host computer,
equipment controller, etc.
Amplifier Unit
CIDRW Head
V640-HAM11-V3
V640-HS61
V640-HAM11-L
V640-HS62
RS-232C
Multiple Amplifier Units
are controlled in
response to commands
(SECS) from the host
device.
RS-485
50 m max.
The CIDRW Heads are the
antennas for reading the carrier IDs from the ID Tags and
writing the carrier IDs.
With the above system configuration, the Amplifier Unit connected directly to the CIDRW Controller
converts signals from RS-232C to RS-485. If this Amplifier Unit is removed, communications will not be
possible with the other Amplifier Units. If the Amplifier Unit connected directly to the CIDRW Controller
must be removed while the system is operating, insert a Link Unit (V700-L11) between the CIDRW
Controller and the first Amplifier Unit. If an Amplifier Unit on the end of the network is removed, be sure
to turn ON the terminating resistance on the Amplifier Unit that will end up on the end of the network
while the Amplifier Unit is removed.
Link Unit
V700-L11
Just the relevant Amplifier Unit can be
removed and replaced while the power
remains on.
RS-232C
SECS I/II
SECTION 6 System Configuration Examples
The Amplifier Units control the CIDRW Heads.
Up to 31 Units can be
connected.
RS-232C
RS-485
50 m max.
Up to 31 Units can be connected.
CIDRW System
User’s Manual
115
SECTION 6
Appendix
When SECS Is Not Used
Communications with the host device follow the OMRON proprietary protocol.
The Amplifier Units are connected directly to the host device without using a CIDRW Controller.
Host
Amplifier Units
CIDRW Heads
V640-HAM11-V3
V640-HS61
V640-HAM11-L
V640-HS62
RS-232C
OMRON original protocol
This is a host computer, equipment
controller, etc.
RS-485
50 m max.
SECTION 6 System Configuration Examples
The Amplifier Units control the CIDRW Heads.
Up to 31 Units can be
connected.
The CIDRW Heads are the
antennas for reading the carrier IDs from the ID Tags and
writing the carrier IDs.
With the above system configuration, the Amplifier Unit connected directly to the CIDRW Controller
converts signals from RS-232C to RS-485. If this Amplifier Unit is removed, communications will not be
possible with the other Amplifier Units. If the Amplifier Unit connected directly to the CIDRW Controller
must be removed while the system is operating, insert a Link Unit (V700-L11) between the CIDRW
Controller and the first Amplifier Unit. If an Amplifier Unit on the end of the network is removed, be sure
to turn ON the terminating resistance on the Amplifier Unit that will end up on the end of the network
while the Amplifier Unit is removed.
Link Unit
V700-L11
Just the relevant Amplifier Unit can be
removed and replaced while the power
remains on.
RS-232C
OMRON original protocol
RS-485
50 m max.
Up to 31 Units can be connected.
116
CIDRW System
User’s Manual
SECTION 6
Appendix
Characteristic Data According to Conditions of Use
Maps of Communications Areas (Reference Only)
The figures given below for communications areas (communications distances) are reference values
only. The maps of communications areas will vary according to the ID Tags that you use, the background metals, the ambient noise, the effects of temperature and so on, and should be thoroughly confirmed on installation. The direction of the ID Tags will affect communications performance. Check the
direction of the coils in the ID Tags before using the ID Tags.
■ V640-HAM11-V3
• Coaxial Mounting (RI-TRP-DR2B)
• READ
Communications Area (READ)
100
90
Distance in Y direction (mm)
80
Measurement point
70
SECTION 6 Characteristic Data According to Conditions of Use
60
50
40
30
20
10
-80
-70
-60
-50
-40
-30
-20
-10
10
20
30
40
50
60
70
80
Distance in X direction (mm)
• WRITE
Communications Area (WRITE)
100
90
80
Distance in Y direction (mm)
70
Measurement point
60
50
40
30
20
10
-80
-70
-60
-50
-40
-30
-20
-10
10
20
30
40
50
60
70
80
Distance in X direction (mm)
CIDRW System
User’s Manual
117
SECTION 6
Appendix
• Coaxial Mounting (RI-TRP-DR2B)
• READ
Communications Area (READ)
100
90
Distance in Y direction (mm)
80
70
60
50
40
30
Measurement point
20
10
-80
-70
-60
-50
-40
-30
-20
-10
10
20
30
40
50
60
70
80
Distance in Z direction (mm)
Communications Area (WRITE)
100
90
80
Distance in Y direction (mm)
SECTION 6 Characteristic Data According to Conditions of Use
118
• WRITE
70
60
50
40
30
Measurement point
20
10
-80
-70
-60
-50
-40
-30
-20
-10
10
20
Distance in Z direction (mm)
CIDRW System
User’s Manual
30
40
50
60
70
80

---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : Yes
Modify Date                     : 2010:09:17 16:57:04+09:00
Create Date                     : 2010:09:17 16:56:45+09:00
Title                           : Z307-E1-01
Author                          : OMRON
Creator                         : FrameMaker 7.0
Producer                        : Acrobat Distiller 8.1.0 (Windows)
Page Count                      : 50
Mod Date                        : 2010:09:17 16:57:04+09:00
Creation Date                   : 2010:09:17 16:56:45+09:00
Metadata Date                   : 2010:09:17 16:57:04+09:00

EXIF Metadata provided by EXIF.tools