Scanner Interface
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | |
Byte 0 |
|
|
| Operation code X’12’ |
|
|
| |
|
|
|
|
|
|
|
| |
1 |
| Logical unit number |
|
| (Reserved) |
| EVPD | |
2 |
|
|
|
|
|
|
|
|
|
|
|
| Page code |
|
|
| |
3 |
|
|
|
|
|
|
| |
|
|
| (Reserved) |
|
|
| ||
|
|
|
|
|
|
|
| |
4 |
|
|
| Allocation length |
|
|
| |
5 |
|
|
|
|
|
|
| |
|
|
| Control byte |
|
|
| ||
|
|
|
|
|
|
|
|
|
a.EVPD (enable vital product data) : Byte 1
The scanner returns the Standard inquiry data, if this bit is 0. If this bit is 1 and Page code is X’F0’, M3093DG returns the Vital product data.
b.Page code: Byte 2
The scanner supports page code for VPD page number specification. This is effective when EVPD is set to 1. If this bit is other than X’F0’, the scanner returns the following error information.
∙ Status: | B’00001’ (CHECK CONDITION) |
∙ Sense key: X’5’ (ILLEGAL REQUEST)
c.Allocation length: Byte 4
This field specifies the storage area in bytes that the initiator allocates for inquiry data. If a 0 is set here, inquiry data is not transferred, but this is not regarded as an error. The target terminates the DATA IN phase when it has transferred either the bytes of inquiry data specified in this field or all of effective inquiry data.
Appendix