SECTION 4
Reading from/Writing to ID Tags
|
|
When SECS is Used |
64 |
|
|
|
|
|
|
When SECS is Not Used |
74 |
|
|
Tags ID to from/Writing Reading 4 SECTION
CIDRW System |
63 |
User’s Manual |
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 113.
Message Specifications
List of Messages Used
|
|
Classification |
S |
F |
|
Direction |
SECS II names |
See |
SECTION |
|
|
|
|
|
|
|
|
|
General purpose |
1 |
1 |
S,H→ |
E,reply |
Are You There Request |
p.66 |
|
|
|
|||||||
|
|
messages |
|
|
|
|
|
|
|
|
1 |
2 |
S,H← |
E |
On Line Data |
p.66 |
|
|
|
|
||||||
|
|
|
|
|
|
|
|
|
4 |
|
CIDRW system |
18 |
1 |
S,H→ |
E,reply |
Read Attribute Request |
p.66 |
|
messages |
|
|
|
|
|
|
|
When |
|
18 |
2 |
S,H← |
E |
Read Attribute Data |
p.66 |
|
|
|
|||||||
|
|
|
|
|
|
|
|
|
|
|
18 |
3 |
S,H→ |
E,reply |
Write Attribute Request |
p.67 |
|
|
|
|
||||||
|
|
|
|
|
|
|
|
|
SECS |
|
|
18 |
4 |
S,H← |
E |
Write Attribute Acknowledge |
p.67 |
|
|
|
|
|
|
|
|
|
|
|
18 |
5 |
S,H→ |
E,reply |
Read Request |
p.68 |
|
|
|
|
||||||
|
|
|
|
|
|
|
|
|
is |
|
|
18 |
6 |
S,H← |
E |
Read Data |
p.68 |
|
|
|
|
|
|
|
|
|
Used |
|
|
18 |
7 |
S,H→ |
E,reply |
Write Request |
p.69 |
|
|
|
|
|
|
|
|
|
|
|
18 |
8 |
S,H← |
E |
Write Acknowledge |
p.69 |
|
|
|
|
||||||
|
|
|
|
|
|
|
|
|
|
|
|
18 |
9 |
S,H→ |
E,reply |
Read ID Request |
p.69 |
|
|
|
|
|
|
|
|
|
|
|
|
18 |
10 |
S,H← |
E |
Read ID Data |
p.69 |
|
|
|
|
|
|
|
|
|
|
|
|
18 |
11 |
S,H→ |
E,reply |
Write ID Request |
p.70 |
|
|
|
|
|
|
|
|
|
|
|
|
18 |
12 |
S,H← |
E |
Write ID Acknowledge |
p.70 |
|
|
|
|
|
|
|
|
|
|
|
|
18 |
13 |
S,H→ |
E,reply |
Subsystem Command Request |
p.70 |
|
|
|
|
|
|
|
|
|
|
|
|
18 |
14 |
S,H← |
E |
Subsystem Command Acknowledge |
p.70 |
|
|
|
|
|
|
|
|
|
List of Error Messages Refer to page 84.
Data Item Dictionary
SECS II data items |
Name |
Format |
Value |
|
ATTRID |
Attribute ID |
20 |
Attribute name |
|
|
|
|
|
|
ATTRVAL |
Attribute value |
20 |
Attribute value |
|
|
|
|
|
|
MID |
Carrier ID |
20 |
All characters 00H-0FFH |
|
|
|
|
|
|
DATA |
Data |
20 |
All characters 00H-0FFH |
|
|
|
|
|
|
DATALENGTH |
DataSize |
52 |
Data Segment Area |
Refer to page 48. |
|
|
|
|
|
DATASEG |
DataSeg |
20 |
|
|
|
|
|
|
|
STATUS |
PM information |
20 |
"NE": Normally executed |
|
|
|
|
|
|
SSACK |
Result status |
20 |
"NO": Normal |
|
|
|
|
"EE": Execution error |
*3 |
|
|
|
"CE": Communications error |
|
|
|
|
"HE": Hardware error |
*3 |
|
|
|
"TE": Tag error *3 |
|
|
|
|
|
|
64 |
|
CIDRW System |
|
||
|
User’s Manual |
|
|
|
|
|
|
|
|
|
SECTION 4 |
|
|
|
|
|
Reading from/Writing to ID Tags |
|
|
|
|
|
|
|
Data Item Dictionary |
|
|
|
|
|
|
|
|
|
|
|
SECS II data items |
|
Name |
Format |
Value |
|
List of STATUS |
|
Status |
L,4 |
The STATUS values are included in the PM infor- |
|
|
|
|
1.<PMInformation> |
mation. |
|
|
|
|
2.<AlarmStatus> |
|
|
|
|
|
3.<OperationalStatus> |
|
|
|
|
|
4.<HeadStatus> *2 |
|
|
|
|
|
|
|
|
CPVAL |
|
State request |
20 |
"OP", "MT", "PS" *1 |
|
|
|
|
|
|
|
TARGETID |
|
Target ID |
20 |
"00"-"31" |
|
|
|
|
|
"00" indicates the CIDRW Controller itself. |
|
|
|
|
|
|
|
SSCMD |
|
Subsystem com- |
20 |
"ChangeState" |
|
|
|
mands |
|
"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" (communications error).
Used is SECS When 4 SECTION
CIDRW System |
65 |
User’s Manual |
Used is SECS When 4 SECTION
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.<MDLN> |
|
|
|
|
|
|
|
|
|
|
|
|
|
2.<SOFTREV> |
|
|
|
|
|
|
|
||
|
|
• Set MDLN (model number). |
|
|
||
|
|
• Set SOFTREV (software revision level). |
|
|
||
|
|
|
|
|
||
• Get attributes |
|
|
||||
|
|
|
|
|
|
|
|
|
S18,F1 |
|
Read Attribute Request |
S,H→ |
E,reply |
|
|
L,2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1.<TARGETID> |
"00"-"31" |
|
|
|
|
|
|
|
|
|
|
|
|
2.L,n |
|
|
|
|
|
|
|
|
|
|
|
|
|
1.<ATTRID1> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
n.<ATTRIDn> |
|
|
|
|
|
|
|
||
|
|
• The setting for reading all attributes (CIDRW Controller or heads) is n = 0. |
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
S18,F2 |
|
Read Attribute Data |
S,H← |
E |
|
|
L,4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1.<TARGETID> |
"00"-"31" |
|
|
|
|
|
|
|
|
|
|
|
|
2.<SSACK> |
|
|
|
|
|
|
|
|
|
|
|
|
|
3.L,n |
|
|
|
|
|
|
|
|
|
|
|
|
|
1.<ATTRVAL1> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
n.<ATTRVALn> |
|
|
|
|
|
|
|
|
|
|
|
|
|
4.L,s |
|
|
|
|
|
|
|
|
|
|
|
|
|
1.<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.
66 |
|
CIDRW System |
|
||
|
User’s Manual |
|
|
|
|
SECTION 4
Reading from/Writing to ID Tags
• Set attributes
F18,F3 |
Write Attribute Request |
S,H→ E,reply |
L,2 |
|
|
|
|
|
|
1.<TARGETID> |
"00" (fixed) |
|
|
|
|
2.L,n |
|
|
|
|
|
1.L,2 |
|
|
|
|
|
1.<ATTRID1> |
|
|
|
|
|
2.<ATTRVAL1> |
|
|
|
|
|
n.L,2 |
|
|
|
|
|
1.<ATTRIDn> |
|
|
|
|
|
2,<ATTRVALn> |
|
|
|
|
Since the attributes for heads are all RO in this system, the target ID is fixed as "00". |
|
|
|
|
|
|
|
4SECTION |
|
|
|
|
|
|
|
S18,F4 |
Write Attribute Acknowledge |
S,H← |
E |
|
||
|
|
|||||
L,3 |
|
|
|
|
|
|
|
|
|
|
|
|
When |
|
|
1.<TARGETID> |
"00" (fixed) |
|
||
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
2.<SSACK> |
|
|
|
|
|
|
|
|
|
|
isSECS |
|
|
|
|
|
|
|
|
|
3.L,s |
|
|
|
|
|
|
1.<STATUS1> |
|
|
|
|
|
|
|
|
|
|
Used |
|
|
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. |
|
|
|
||
|
|
|
|
|
|
|
CIDRW System |
67 |
User’s Manual |
SECTION 4
Reading from/Writing to ID Tags
• Read data
S18,F5 |
Read Request |
S,H→ E,reply |
L,3 |
|
|
|
|
|
|
1.<TARGETID> |
"01"-"31" |
|
|
|
|
2.<DATASEG> |
|
|
|
|
|
3.<DATALENGTH> |
|
|
|
|
•When the data of all segments is batch read, both DATASEG and DATALENGTH are omitted (they are zero length items).
•When all the data for a particular segment is read, DATALENGTH is omitted (it is a zero length item).
•When DATASEG and DATALENGTH are specified, it is not permissible to specify a DATALENGTH that exceeds the maximum length of the relevant DATASEG.
•If a DATALENGTH that is under the set length for DATASEG is specified, only the data corresponding to the specified DATALENGTH is read.
Data Segment Area Refer to page 111.
4SECTION |
|
|
|
|
|
|
S18,F6 |
Read Data |
S,H→ E,reply |
||
|
|
||||
|
|
L,4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
1.<TARGETID> |
"01"-"31" |
When |
|
|
|
|
|
|
|
|
2.<SSACK> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3.<DATA> |
|
isSECS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4.L,s |
|
|
|
|
|
1.<STATUS1> |
|
Used |
|
|
|
|
|
|
|
|
s.<STATUSs> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
• |
When the specified target is invalid: |
|
|
|
|
|
DATA item length = 0, s = 0, SSACK = "CE" communications error |
|
|
|
|
• When an undefined DATASEG is specified, or the DATALENGTH is illegal: |
|
||
|
|
|
DATA item length = 0, s = 0, |
|
|
|
|
|
SSACK = "CE" communications error |
|
|
|
|
• |
When reading of all segment data is specified in a system where the data segment is not defined: |
||
|
|
|
DATA length = 0, SSACK = "NO" |
|
|
|
|
• |
If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items. |
||
|
|
|
|
|
|
68 |
|
CIDRW System |
|
||
|
User’s Manual |
|
|
|
|
|
|
|
|
SECTION 4 |
|
|
|
Reading from/Writing to ID Tags |
|
|
|
|
|
|
• Write data |
|
|
|
|
|
|
|
|
|
|
S18,F7 |
Write Request |
|
S,H→ E,reply |
|
L,4 |
|
|
|
|
|
|
|
|
|
|
1.<TARGETID> |
|
"01"-"31" |
|
|
|
|
|
|
|
2.<DATASEG> |
|
|
|
|
|
|
|
|
|
3.<DATALENGTH> |
|
|
|
|
|
|
|
|
|
4.<DATA> |
|
|
|
|
|
|
|
•When the data for all segments is batch written, both DATASEG and DATALENGTH are omitted (they are zero length items).
•When all the data for a particular segment is written, DATALENGTH is omitted (it is a zero length item).
•When DATASEG and DATALENGTH are specified, it is not permissible to specify a DATALENGTH that exceeds the maximum length of the relevant DATASEG.
•If a DATALENGTH that is under the set length for DATASEG is specified, only the data corresponding to the specified DATALENGTH is written, compressed into the smaller addresses.
•The item lengths of DATASEG and DATA must be matched.
•If DATASEG and DATALENGTH are both omitted (made zero length items), the length of DATA must match the total of the set lengths of all segments.
|
Data Segment Area |
Refer to page 111. |
|
||
|
|
|
|
|
|
|
S18,F8 |
Write Acknowledge |
S,H← E |
||
|
L,3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
1.<TARGETID> |
|
"01"-"31" |
|
|
|
|
|
|
|
|
|
2.<SSACK> |
|
|
|
|
|
|
|
|
|
|
|
3.L,s |
|
|
|
|
|
|
|
|
|
|
|
1.<STATUS1> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
s.<STATUSs> |
|
|
|
|
|
|
|
|
|
• |
When the specified target is invalid: |
|
|
|
|
|
s = 0, SSACK = "CE" communications error |
|
||
|
• When DATASEG and DATALENGTH are illegal: |
|
|||
|
|
s = 0, SSACK = "CE" communications error |
|
||
|
• |
If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items. |
|||
|
|
|
|
|
|
• Read ID
|
S18,F9 |
Read ID Request |
|
S,H→ |
E,reply |
|
|
1.<TARGETID> |
|
|
"01"-"31" |
||
|
|
|
|
|
|
|
|
Data Segment Area |
Refer to page 111. |
|
|||
|
|
|
|
|
|
|
|
S18,F10 |
Read ID Data |
|
S,H← |
E |
|
|
L,4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1.<TARGETID> |
|
"01"-"31" |
|
|
|
|
|
|
|
|
|
|
|
2.<SSACK> |
|
|
|
|
|
|
|
|
|
|
|
|
|
3.<MID> |
|
|
|
|
|
|
|
|
|
|
|
|
|
4.L,s |
|
|
|
|
|
|
|
|
|
|
|
|
|
1.<STATUS1> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
s.<STATUSs> |
|
|
|
|
|
|
|
|
|
|
|
• |
When the specified target is invalid: |
|
|
|
|
|
|
s = 0, MID item length = 0, SSACK = "CE" communications error |
|
|||
|
• |
If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items. |
|
|||
|
|
|
|
|
|
|
Used is SECS When 4 SECTION
CIDRW System |
69 |
User’s Manual |
Used is SECS When 4 SECTION
SECTION 4
Reading from/Writing to ID Tags
• Write ID
S18,F11 |
Write ID Request |
|
S,H→ E,reply |
|
L,2 |
|
|
|
|
|
|
|
|
|
|
|
1.<TARGETID> |
|
"01"-"31" |
|
|
|
|
|
|
|
2.<MID> |
|
|
|
|
|
||
• |
If an MID that is under the set ID length is specified, the data is compressed into the smaller addresses, and NULL (0x00) is |
|||
|
written as the remaining data. |
|
|
|
|
|
|
|
|
Data Segment Area |
Refer to page 111. |
|
||
|
|
|
||
S18,F12 |
Write ID Acknowledge |
S,H← E |
||
L,3 |
|
|
|
|
|
|
|
|
|
|
|
1.<TARGETID> |
|
"01"-"31" |
|
|
|
|
|
|
|
2.<SSACK> |
|
|
|
|
|
|
|
|
|
3.L,s |
|
|
|
|
|
|
|
|
|
1.<STATUS1> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
s.<STATUSs> |
|
|
|
|
|
|
|
• |
When the specified target is invalid: |
|
|
|
|
s = 0, SSACK = "CE" communications error |
|
||
• |
When there is an MID length error: |
|
|
|
|
s = 0, SSACK = "CE" communications error |
|
•If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.
•Subsystem command (ChangeState)
S18,F13 |
Subsystem Command Request (ChangeState) |
S,H→ E,reply |
L,3 |
|
|
|
|
|
|
1.<TARGETID> |
"00" (fixed) |
|
|
|
|
2.<SSCMD> |
"ChangeState" |
|
|
|
|
3.L,1 |
|
|
|
|
|
1.<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← E |
L,3 |
|
|
|
|
|
|
1.<TARGETID> |
"00" |
|
|
|
|
2.<SSACK> |
|
|
|
|
|
3.L,s |
|
|
|
|
|
1.<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.
70 |
|
CIDRW System |
|
||
|
User’s Manual |
|
|
|
|
SECTION 4
Reading from/Writing to ID Tags
• Subsystem command (GetStatus)
S18,F13 |
Subsystem Command Request (GetStatus) |
S,HÅ→ ,reply |
L,3 |
|
|
|
|
|
|
1.<TARGETID> |
"00"-"31" |
|
|
|
|
2.<SSCMD> |
"GetStatus" |
|
|
|
|
3.L,0 |
|
|
|
|
|
|
|
S18,F14 |
Subsystem Command Acknowledge (GetStatus) |
S,H← E |
L,3 |
|
|
|
|
|
|
1.<TARGETID> |
"00"-"31" |
|
|
|
|
2.<SSACK> |
"GetStatus" |
|
|
|
|
3.L,s |
|
|
|
|
|
1.<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.
•Subsystem command (PerformDiagnostics)
S18,F13 |
Subsystem Command Request (PerformDiagnostics) |
S,H→ E,reply |
L,3 |
|
|
|
|
|
|
1.<TARGETID> |
"00"-"31" |
|
|
|
|
2.<SSCMD> |
"PerformDiagnostics" |
|
|
|
|
3.L,0 |
|
|
|
|
|
|
|
S18,F14 |
Subsystem command Acknowledge (PerformDiagnostics) |
S,H← E |
L,3 |
|
|
|
|
|
|
1.<TARGETID> |
"00"-"31" |
|
|
|
|
2.<SSACK> |
|
|
|
|
|
3.L,s |
|
|
|
|
|
1.<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.
Used is SECS When 4 SECTION
CIDRW System |
71 |
User’s Manual |
Used is SECS When 4 SECTION
SECTION 4
Reading from/Writing to ID Tags
• Subsystem command (Reset)
S18,F13 |
Subsystem Command Request (Reset) |
S,H→ |
E,reply |
L,3 |
|
|
|
|
|
|
|
|
1.<TARGETID> |
"00" (fixed) |
|
|
|
|
|
|
2.<SSCMD> |
"Reset" |
|
|
|
|
|
|
3.L,0 |
|
|
|
|
|
|
|
|
|
|
S18,F14 |
Subsystem Command Acknowledge (Reset) |
S,H← |
E |
L,3 |
|
|
|
|
|
|
|
|
1.<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
72 |
|
CIDRW System |
|
||
|
User’s Manual |
|
|
|
|
SECTION 4
Reading from/Writing to ID Tags
Operation Conditions
The response messages and response codes (SSACK) in each state are shown below:
State |
Initializing |
Operating |
Maintenance |
|
|
||
Message |
Function |
IDLE |
BUSY |
|
|
||
|
|
|
|
||||
S1,F1 |
OnlineRequest |
S1,F0 |
S1,F2 |
S1,F2 |
S1,F2 |
|
|
|
|
|
|
|
|
|
|
S18,F11 |
WriteID |
S18,F0 |
S18,F0 |
S18,F0 |
NO |
|
|
|
|
|
|
|
|
|
|
S18,F7 |
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,F13(ChangeState) |
ChangeState(to OP) |
S18,F0 |
S18,F0 |
S18,F0 |
NO |
|
SECTION |
S18,F1 |
GetAttribute |
S18,F0 |
NO |
NO |
NO |
|
|
S18,F13(ChangeState) |
ChangeState(to MT) |
S18,F0 |
NO |
S18,F0 |
S18,F0 |
|
|
|
|
|
|
|
|
|
4 |
S18,F13(ChangeState) |
ChangeState(to PS) |
S18,F0 |
NO |
S18,F0 |
NO |
|
|
|
Used is SECS When |
||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CIDRW System |
73 |
User’s Manual |
Used Not is SECS When 4 SECTION
SECTION 4
Reading from/Writing to ID Tags
When SECS is Not Used
Command/Response Format
Command
SOH |
Node No. |
|
Command code |
|
|
Parameter |
|
|
FCS |
CR |
|||||
|
1 |
|
n |
||||||||||||
|
|
|
|
|
|
|
|
|
|
||||||
01h |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Response
SOH |
Node No. |
Response |
|
|
Parameter |
|
|
FCS |
CR |
|||||
code |
1 |
|
n |
|||||||||||
|
|
|
|
|
|
|||||||||
01h |
|
|
|
|
|
|
|
|
|
|
|
|
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.
Example: Reading the data of page 1 and page 2 of node No.1:
Command
Calculation range
(ASCII conversion)
74 |
|
CIDRW System |
|
||
|
User’s Manual |
|
|
|
|
SECTION 4
Reading from/Writing to ID Tags
Command
Command code list
Name |
Value |
Function |
See |
READ |
0100 |
When this command is received, the system communicates with the ID Tag, and |
p.76 |
|
|
reads the specified page(s) of data. Any pages up to a maximum of 16 can be |
|
|
|
selected. |
|
|
|
|
|
WRITE |
0200 |
When this command is received, the system communicates with the ID Tag, and |
p.77 |
|
|
writes the specified page(s) of data. Any pages up to a maximum of 16 can be |
|
|
|
selected. |
|
|
|
|
|
Same Write |
0300 |
When this command is received, the system communicates with the ID Tag, and |
p.79 |
|
|
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. |
|
|
|
|
|
Byte Write |
0400 |
When this command is received the system communicates with the ID Tag, and |
p.80 |
|
|
writes data to the area specified by a first address and number of bytes. A maximum |
|
|
|
of 128 bytes can be specified. |
|
|
|
|
|
TEST |
10 |
Sends received data to the host device. |
p.81 |
|
|
|
|
NAK |
12 |
Sends the response made immediately before again. |
p.82 |
|
|
|
|
Noise measurement |
40 |
Measures the noise in the vicinity of the CIDRW Head. |
p.82 |
|
|
|
|
RESET |
7F |
Resets the Amplifier Unit. |
p.82 |
|
|
|
|
Response code list
Type |
Response |
Name |
Description |
|
code |
||||
|
|
|
||
Normal end |
00 |
Normal end |
Command execution is completed normally. |
|
|
|
|
|
|
Host communi- |
14 |
Format error |
There is a mistake in the command format. |
|
cations error |
|
|
(E.g. the command code is undefined, or the page or address spec- |
|
|
|
|
ification is inappropriate.) |
|
|
|
|
|
|
Communica- |
70 |
Communications error |
Noise or another hindrance occurs during communication with an |
|
tions error |
|
|
ID Tag, and communications cannot be completed normally. |
|
|
|
|
|
|
|
71 |
Verification error |
Correct data cannot be written to an ID Tag. |
|
|
|
|
|
|
|
72 |
No Tag error |
Either there is no ID Tag in front of the CIDRW Head, or the CIDRW |
|
|
|
|
Head is unable to detect the ID Tag due to environmental factors |
|
|
|
|
(e.g. noise). |
|
|
|
|
|
|
|
7B |
Outside write area error |
Writing is not completed normally. |
|
|
|
|
|
|
|
7E |
ID system error (1) |
The ID Tag is in a status where it cannot execute command pro- |
|
|
|
|
cessing. |
|
|
|
|
|
|
|
7F |
ID system error (2) |
An inapplicable ID Tag has been used. |
|
|
|
|
|
Used Not is SECS When 4 SECTION
CIDRW System |
75 |
User’s Manual |
Used Not is SECS When 4 SECTION
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 |
|
|
Page designation (8 characters) |
|
FCS |
CR |
||||||||||
01h |
|
|
0 |
|
1 |
0 |
|
0 |
|
|
|
|
|
|
|
|
|
|
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Bit |
7 |
- |
0 |
7 |
- |
3 |
2 |
1 |
0 |
7 |
6 |
|
- |
|
1 |
0 |
7 |
6 |
- |
2 |
1 |
0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Page |
Sys |
- |
Sys |
Sys |
- |
Sys |
17 |
16 |
15 |
14 |
13 |
|
- |
|
8 |
7 |
6 |
5 |
- |
1 |
Sys |
Sys |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Designation |
0* |
0* |
|
0* |
0* |
0* |
0/1 |
0/1 |
0/1 |
0/1 |
0/1 |
|
••• |
|
0/1 |
0/1 |
0/1 |
0/1 |
••• |
0/1 |
0* |
0* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Value |
|
00 |
|
|
|
00 - 07 |
|
|
|
|
00 - FF |
|
|
|
|
00 - FC |
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Always specify 0. If you specify 1 an error (Response code : 14) will occur.
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. |
|
|
Data Segment Area |
Refer to page 111. |
The response code (when normal: 00) and the data in the specified pages are returned in ascending order of page numbers.
Response
|
|
|
Response |
|
|
|
|
|
|
Read data |
|
|
|
|
|
|
|
|
|
|||||
SOH |
Node No. |
|
|
Page n |
|
|
|
|
|
|
Page m (n<m) |
|
|
FCS |
CR |
|||||||||
|
code |
|
|
|
|
|
|
|
|
|
||||||||||||||
|
|
|
|
|
|
Data 1 |
|
Data 8 |
|
|
Data 1 |
|
|
|
Data 8 |
|
|
|
||||||
01h |
|
|
0 |
|
0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example: Reading the data of pages 1 and 3 of node No.1
Data content of the ID Tag
|
|
|
|
|
Page 1 |
|
|
|
12h |
|
|
34h |
|
56h |
|
78h |
|
90h |
|
12h |
|
|
34h |
|
56h |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||||||
|
|
|
|
|
Page 2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
Page 3 |
|
|
|
11h |
|
|
22h |
|
33h |
|
44h |
|
55h |
|
66h |
|
|
77h |
|
88h |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||||||
|
|
|
|
|
Page 4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Command |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||
|
SOH |
|
|
Node No. |
|
|
|
|
Command code |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Page designation |
|
|
|
|
|
|
|
|
|
FCS |
|
|
CR |
|||||||||||||||||||||||
|
01h |
|
0 |
|
|
|
1 |
|
|
0 |
|
|
1 |
|
0 |
|
0 |
|
|
|
0 |
|
|
|
0 |
|
|
|
0 |
|
0 |
|
|
0 |
|
|
|
|
0 |
|
|
1 |
|
|
4 |
0 |
|
5 |
|
|
0Dh |
|||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
Binary notation |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
0 |
0 |
|
0 |
0 |
|
|
0 |
0 |
|
0 |
0 |
|
0 |
0 |
|
0 |
|
0 |
|
0 |
|
|
0 |
|
0 |
|
0 |
|
0 |
0 |
|
0 |
|
0 |
|
0 |
|
0 |
|
|
0 |
0 |
0 |
0 |
0 |
1 |
|
0 |
1 |
0 |
|
0 |
|
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
76 |
|
CIDRW System |
|
||
|
User’s Manual |
|
|
|
|
SECTION 4
Reading from/Writing to ID Tags
Response
SOH |
Node No. |
Response |
|
|
|
|
|
|
|
Page 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Page 3 |
|
|
|
|
|
|
|
FCS |
CR |
|||||||||
|
|
|
code |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
01h |
0 |
1 |
0 |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|
8 |
9 |
|
0 |
1 |
2 |
3 |
4 |
5 |
6 |
1 |
1 |
2 |
2 |
3 |
3 |
4 |
|
4 |
5 |
|
5 |
6 |
6 |
7 |
7 |
8 |
8 |
0 |
7 |
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
WRITE
Data is written in page units to the ID Tag. Any page(s) can be specified. It is possible to write to a maximum of 16 pages at one time.
Command
|
|
Node |
|
|
Command |
|
Page designation |
|
|
|
|
|
|
|
|
|
|
|
|
Write data |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||||
SOH |
|
|
|
|
|
|
|
|
Page n |
|
|
|
|
|
|
|
|
|
|
|
Page m (n<m) |
|
FCS |
CR |
||||||||||||||||||||||||||||||
|
|
No. |
|
|
|
code |
|
|
(8 characters) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||
|
|
|
|
|
|
|
|
|
|
Data 1 |
|
|
|
Data 8 |
|
Data 1 |
|
|
|
|
Data 8 |
|
|
|
|
|
||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||||
01h |
|
|
|
|
|
0 |
2 |
|
0 |
0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0DH |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Bit |
|
7 |
|
|
- |
|
0 |
7 |
|
- |
3 |
|
|
|
2 |
|
1 |
0 |
|
7 |
|
|
6 |
|
- |
1 |
|
0 |
|
|
7 |
6 |
|
- |
|
2 |
|
|
1 |
0 |
|
|
||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Page |
|
|
Sys |
|
- |
|
Sys |
Sys |
|
- |
Sys |
|
|
17 |
16 |
15 |
|
14 |
|
13 |
|
- |
8 |
|
7 |
|
|
6 |
5 |
|
- |
|
1 |
|
|
Sys |
Sys |
|
||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Designation |
0* |
|
|
0* |
|
|
|
0* |
|
0* |
0* |
|
|
0/1 |
0/1 |
0/1 |
|
0/1 |
|
0/1 |
|
|
••• |
0/1 |
|
0/1 |
|
0/1 |
0/1 |
|
••• |
0/1 |
|
0* |
0* |
|
|
|||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Value |
|
|
|
|
00 |
|
|
|
|
|
|
|
|
00 - 07 |
|
|
|
|
|
|
|
|
|
|
00 - FF |
|
|
|
|
|
|
|
|
|
00 - FC |
|
|
|
|
|
||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Always specify 0. If you specify 1 an error (Response code : 14) will occur.
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. |
|
|
Write data |
The data to be written to the specified pages is specified in ascending order of page numbers. |
|
|
Data Segment Area |
Refer to page 111. |
Response
The response code (when normal: 00) is returned.
SOH |
Node No. |
Response |
FCS |
CR |
||||
|
code |
|||||||
|
|
|
|
|
|
|
||
01h |
|
|
0 |
|
0 |
|
|
0Dh |
|
|
|
|
|
|
|
|
|
Used Not is SECS When 4 SECTION
CIDRW System |
77 |
User’s Manual |
SECTION 4
Reading from/Writing to ID Tags
Example: Writing data to pages 8 and 10 of node No.1:
Command
SOH |
Node |
|
Command |
Page designation |
|
|
|
|
|
|
Data of page 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Data of page 10 |
FCS |
CR |
||||||||||||||||||||||||||||||||||||||||||
|
No. |
|
|
|
code |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
01h |
0 |
|
1 |
|
0 |
|
2 |
0 |
|
0 |
0 |
0 |
0 |
0 |
0 |
A |
0 |
0 |
1 |
1 |
2 |
2 |
3 |
3 |
4 |
4 |
5 |
5 |
6 |
6 |
7 |
7 |
8 |
8 |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
A |
B |
C |
D |
E |
F |
7 |
4 |
0Dh |
|||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
Binary notation |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0 |
0 |
0 |
0 |
|
0 |
|
0 |
0 |
0 |
|
0 |
0 |
0 |
0 |
|
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
0 |
1 |
0 |
1 |
|
0 |
0 |
0 |
0 |
0 |
0 |
|
0 |
0 |
0 |
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Used Not is SECS When 4 SECTION
Response
SOH |
Node No. |
Response |
|
FCS |
CR |
||||
|
code |
|
|||||||
|
|
|
|
|
|
|
|
||
01h |
0 |
1 |
0 |
|
0 |
0 |
|
1 |
0Dh |
|
|
|
|
|
|
|
|
|
|
The ID Tag status on normal completion is as shown below:
|
|
|
|
|
|
|
|
|
Page 8 |
11h |
22h |
33h |
44h |
55h |
66h |
77h |
88h |
Page 9 |
|
|
|
|
|
|
|
|
Page 10 |
01h |
23h |
45h |
67h |
89h |
ABh |
CDh |
EFh |
|
|
|
|
|
|
|
|
|
78 |
|
CIDRW System |
|
||
|
User’s Manual |
|
|
|
|
SECTION 4
Reading from/Writing to ID Tags
Same Write
Writes the same data to multiple pages of an ID Tag. Any page(s) can be specified.
Command
SOH |
Node No. |
Command code |
Page designation (8 characters) |
|
|
Write data |
|
|
FCS |
CR |
||||||||||||||
Data 1 |
|
Data 8 |
||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||
01h |
|
|
0 |
3 |
0 |
0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0DH |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Bit |
7 |
- |
0 |
7 |
- |
3 |
2 |
1 |
0 |
7 |
6 |
|
- |
|
1 |
0 |
7 |
6 |
- |
2 |
1 |
0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Page |
Sys |
- |
Sys |
Sys |
- |
Sys |
17 |
16 |
15 |
14 |
13 |
|
- |
|
8 |
7 |
6 |
5 |
- |
1 |
Sys |
Sys |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Designation |
0* |
0* |
|
0* |
0* |
0* |
0/1 |
0/1 |
0/1 |
0/1 |
0/1 |
|
••• |
|
0/1 |
0/1 |
0/1 |
0/1 |
••• |
0/1 |
0* |
0* |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Value |
|
00 |
|
|
|
00 - 07 |
|
|
|
|
00 - FF |
|
|
|
|
00 - FC |
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Always specify 0. If you specify 1 an error (Response code : 14) will occur.
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. |
|
|
Write data |
Specify the write data. |
|
|
Data Segment Area |
Refer to page 111. |
Response
The response code (when normal: 00) is returned.
SOH |
Node No. |
Response |
FCS |
CR |
|
||||
|
code |
|
|||||||
|
|
|
|
|
|
|
|
||
01h |
|
|
0 |
|
0 |
|
|
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example: Clearing pages 1 to 17 of node No.1 to 0:
Command
|
SOH |
|
Node No. |
|
Command |
|
|
Page designation |
|
|
|
|
|
|
|
|
|
|
|
Write data |
|
|
|
|
|
|
|
|
|
|
|
|
FCS |
|
|
CR |
|||||||||||||||||||||||||
|
|
|
|
code |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
01h |
0 |
|
|
1 |
|
|
0 |
3 |
0 |
0 |
0 |
|
0 |
0 |
7 |
F |
F |
|
F |
C |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
0 |
|
|
0Dh |
|||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
|
Binary notation |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
0 |
0 |
|
0 |
|
0 |
|
0 |
|
0 |
|
0 |
|
0 |
0 |
|
0 |
|
0 |
|
0 |
0 |
|
1 |
|
1 |
|
1 |
1 |
1 |
|
1 |
|
1 |
1 |
1 |
|
|
1 |
|
1 |
1 |
1 |
|
1 |
|
1 |
|
1 |
1 |
0 |
|
0 |
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Response |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SOH |
|
|
Node No. |
|
|
Response |
|
|
|
|
FCS |
|
|
|
|
CR |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||
|
|
|
|
|
|
|
code |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
01h |
|
|
0 |
|
|
|
1 |
|
0 |
|
|
0 |
|
0 |
|
|
1 |
|
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Used Not is SECS When 4 SECTION
CIDRW System |
79 |
User’s Manual |
Used Not is SECS When 4 SECTION
SECTION 4
Reading from/Writing to ID Tags
Byte Write
Writes data to any specified number of bytes starting from the address specified in the ID Tag. The maximum number of bytes that can be written at one time is 128.
Command
SOH |
Node No. |
|
Command code |
|
First |
|
|
Write data |
|
|
FCS |
CR |
|||||||
|
|
address |
Data 1 |
••• |
Data n |
||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
||||||||
01h |
|
|
0 |
|
4 |
0 |
|
0 |
|
|
|
|
|
|
|
|
|
|
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Data number n = number of bytes written to (2-character units)
Parameter description
Parameter |
Description |
Address designation |
Addresses can be specified in the range 00h to 87h. |
|
|
Write data |
Up to 128 bytes of write data, starting from the specified address, can be specified. |
|
|
Data Segment Area |
Refer to page 111. |
Response
The response code (when normal: 00) is returned.
SOH |
Node No. |
Response |
FCS |
CR |
|
||||
|
code |
|
|||||||
|
|
|
|
|
|
|
|
||
01h |
|
|
0 |
|
0 |
|
|
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example: Writing to two bytes starting from address 05h of node No.1:
Command
SOH |
Node No. |
|
Command code |
|
First address |
|
Write data |
|
|
FCS |
CR |
|||||||
|
|
Data 1 |
|
Data 2 |
|
|
||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
01h |
0 |
1 |
0 |
4 |
0 |
0 |
0 |
5 |
1 |
|
2 |
3 |
|
4 |
0 |
|
4 |
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Response
SOH |
Node No. |
Response |
|
FCS |
CR |
||||
|
code |
|
|||||||
|
|
|
|
|
|
|
|
||
01h |
0 |
1 |
0 |
|
0 |
0 |
|
1 |
0Dh |
|
|
|
|
|
|
|
|
|
|
The ID Tag status on normal completion is as shown below:
Page 1 |
12h |
34h |
Page 2
80 |
|
CIDRW System |
|
||
|
User’s Manual |
|
|
|
|
SECTION 4
Reading from/Writing to ID Tags
TEST
Performs a communication test on communications between the host device and Amplifier Unit. When an Amplifier Unit receives a test command, it sends the response code and command test data to the host device as the response.
Command
SOH |
Node No. |
Command code |
|
|
Test data |
|
|
FCS |
CR |
|||||
Data 1 |
••• |
Data n |
||||||||||||
|
|
|
|
|
|
|
|
|||||||
01h |
|
|
1 |
0 |
|
|
|
|
|
|
|
|
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Number of data n < 136 (2-character units)
Parameter description
Parameter |
Description |
Test data |
The data to be sent in the test is specified with a hexadecimal value. (Max. 270 characters) |
|
However, note that odd numbers of characters cannot be used. |
|
|
Response
The response code (when normal: 00) and the received test data are returned.
SOH |
Node No. |
Response |
|
|
Test data |
|
|
FCS |
CR |
|
|||||
code |
|
Data 1 |
••• |
Data n |
|
||||||||||
|
|
|
|
|
|
|
|
||||||||
01h |
|
|
0 |
|
0 |
|
|
|
|
|
|
|
|
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example: Testing by sending the data "12345678" to node No.1:
Command
SOH |
Node No. |
Command code |
|
|
|
|
|
Test data |
|
|
|
|
|
|
FCS |
CR |
||||
|
Data 1 |
|
Data 2 |
|
Data 3 |
|
Data 4 |
|
||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||
01h |
0 |
1 |
1 |
0 |
1 |
|
2 |
3 |
|
4 |
5 |
|
6 |
7 |
|
8 |
0 |
|
8 |
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Response
SOH |
Node No. |
Response |
|
|
|
|
|
Test data |
|
|
|
|
|
|
FCS |
CR |
|||||
|
code |
|
Data 1 |
|
Data 2 |
|
Data 3 |
|
Data 4 |
|
|||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||
01h |
0 |
1 |
0 |
|
0 |
1 |
|
2 |
3 |
|
4 |
5 |
|
6 |
7 |
|
8 |
0 |
|
9 |
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Used Not is SECS When 4 SECTION
CIDRW System |
81 |
User’s Manual |
Used Not is SECS When 4 SECTION
SECTION 4
Reading from/Writing to ID Tags
NAK
Sends the response made immediately before again.
Command
SOH |
Node No. |
Command code |
FCS |
CR |
|||
01h |
|
|
1 |
2 |
|
|
0Dh |
|
|
|
|
|
|
|
|
Response
Sends the response made immediately before again.
Noise measurement
The levels of noise in the vicinity of the CIDRW Head are measured and the noise level is expressed numerically in the range "00" to "99."
Command
SOH |
Node No. |
Command code |
FCS |
CR |
|||
01h |
|
|
4 |
0 |
|
|
0Dh |
|
|
|
|
|
|
|
|
Response
The response code (when normal: 00) and the noise level "00" to "99" are returned.
SOH |
Node No. |
Response code |
Noise level |
FCS |
CR |
|
||||
01h |
|
|
0 |
0 |
|
|
|
|
0Dh |
|
|
|
|
|
|
|
|
|
|
|
|
Influence of background noise on communication distance |
|
Refer to page 110. |
RESET
All Amplifier Unit processing is stopped, and the initial status is re-established.
Command
SOH |
Node No. |
Command code |
FCS |
CR |
|||
01h |
|
|
7 |
F |
|
|
0Dh |
|
|
|
|
|
|
|
|
Response
There is no response to this command.
82 |
CIDRW System |
User’s Manual |