707
V600/V620 ID Controller Protocol Appendix P
Note 1. Execute Sequence No. 510 before executing Sequence No. 511.
2. Data from Data Carriers designated for ASCII is stored beginning with the smallest offset from the
receive data words.
3. Retry processing is not performed for this sequence.
Polling Auto-read Sub-command (ASCII/4) (Sequence No. 512
(Hex 0200))
This sequence is used when the maximum number of Heads to be read from the Carrier is 4. Up to 48 bytes of
data can be read for each Read/Write Head.
Send Data Word Allocation (3rd Operand of PMCR(260))
The send data word allocation is similar to that of Sequence No. 502 (Read (ASCII/4)). However, the leading
address No. and number of read bytes are not used and will be the value specified for sequence #510.
Receive Data Word Allocation (4th Operand of PMCR(260))
The receive data word allocation is similar to that of Sequence No. 502 (Read (ASCII/4)).
Note 1. Execute Sequence No. 510 before executing Sequence No. 512.
2. Data from Data Carriers designated for ASCII is stored beginning with the smallest offset from the
receive data words.
3. Retry processing is not performed for this sequence.
Polling Auto-read Sub-command (ASCII/8) (Sequence No. 513
(Hex 0201))
This sequence is used when the maximum number of Heads to be read from the Carrier is 8. Up to 20 bytes of
data can be read for each Read/Write Head.
Send Data Word Allocation (3rd Operand of PMCR(260))
The send data word allocation is similar to that of Sequence No. 503 (Read (ASCII/8)). However, the leading
address No. and number of read bytes are not used and will be the value specified for sequence #510.
Receive Data Word Allocation (4th Operand of PMCR(260))
The receive data word allocation is similar to that of Sequence No. 503 (Read (ASCII/8)).
Note 1. Execute Sequence No. 510 before executing Sequence No. 513.
2. Data from Data Carriers designated for ASCII is stored beginning with the smallest offset from the
receive data words.
3. Retry processing is not performed for this sequence.