709
V600/V620 ID Controller Protocol Appendix P
2. Data from Data Carrier designated for hexadecimal is stored beginning with the largest offset from
the receive data words.
3. Retry processing is not performed for this sequence.
Polling Auto-read Sub-command (Hex/4) (Sequence No. 516
(Hex 0204))
This sequence is used when the maximum number of Heads to be read from the Carrier is 4. Up to 24 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. 506 (Read (Hex/4)). However, the leading
address No. and number of read bytes are not used and will be the value specified for sequence #514.
Receive Data Word Allocation (4th Operand of PMCR(260))
The receive data word allocation is similar to that of Sequence No. 506 (Read (Hex/4)).
Note 1. Execute Sequence No. 514 before executing Sequence No. 516.
2. Data from Data Carrier designated for hexadecimal is stored beginning with the largest offset from
the receive data words.
Polling Auto-read Sub-command (Hex/8) (Sequence No.517 (Hex
0205))
This sequence is used when the maximum number of Heads to be read from the Carrier is 8. Up to 10 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. 507 (Read (Hex/8)). However, the leading
address No. and number of read bytes are not used and will be the value specified for sequence #514.
Receive Data Word Allocation (4th Operand of PMCR(260))
The receive data word allocation is similar to that of sequence No. 507 (Read (Hex/8)).
Note 1. Execute sequence No. 514 before executing sequence No. 517.
2. Data from Data Carriers designated for hexadecimal is stored beginning with the largest offset from
the receive data words.
3. Retry processing is not performed for this sequence.
To Next Page
Loading...
Need help?
General
