Casio CTK6000 User Manual
Page 38
Table 1
7
6
5
4
3
2
1
0
Memory data 00:
[00.7]
[00.6]
[00.5]
[00.4]
[00.3]
[00.2]
[00.1]
[00.0]
Memory data 01:
[01.7]
[01.6]
[01.5]
[01.4]
[01.3]
[01.2]
[01.1]
[01.0]
Memory data 02:
[02.7]
[02.6]
[02.5]
[02.4]
[02.3]
[02.2]
[02.1]
[02.0]
:
Memory data 32:
[32.7]
[32.6]
[32.5]
[32.4]
[32.3]
[32.2]
[32.1]
[32.0]
(Bit M of the NNth byte is indicated at [NN.M].)
Table 2
7
6
5
4
3
2
1
0
Send data 00:
0
[00.6]
[00.5]
[00.4]
[00.3]
[00.2]
[00.1]
[00.0]
Send data 01:
0
[01.5]
[01.4]
[01.3]
[01.2]
[01.1]
[01.0]
[00.7]
Send data 02:
0
[02.4]
[02.3]
[02.2]
[02.1]
[02.0]
[01.7]
[01.6]
:
Send data 37:
0
0
0
[32.7]
[32.6]
[32.5]
[32.4]
[32.3]
Though transferred data always sequentially uses from bit 0 through bit 7, unused upper bit fields in
the final transfer data are filled in with 0.
Parameter Set Packet Splitting
When a parameter set is transferred, a single parameter set memory
image can be split so it can fit into the preset transfer message size, and transferred as multiple packets.
Even when a packet is split, the memory image must be transferred from the beginning in the sequence
it is arranged without interruption. When sending a parameter set to the Instrument, the size of a
System Exclusive message for a single packet must fit within a preset size. The parameter set memory
image to be transferred can be split into 1-byte units, and it does not matter whether the length of each
packet is different. When a packet receive error is generated, the sending device needs to resend, but
the size of the packet sent does not necessarily need to be the same size as the packet sent when the
error was generated. Even the sizes of parameter sets are small, using a single packet to send multiple
parameter sets is not supported. With this Instrument, the data size, transfer time interval, and other
communication parameters for split packets can be adjusted using the parameters described under “24.2
System Exclusive Protocol Parameter”. For details, see “24.2 System Exclusive Protocol Parameter.”
20.3.15
crc : Cyclic Redundancy Check
Format:
LSB
0aaaaaaaB
0bbbbbbaB
0cccccbbB
0ddddcccB
MSB
0000ddddB
CRC32 (in accordance with ISO 8802-3 or IEEE803.2 regulations) 32-bit value (ddddddddccccccc-
cbbbbbbbbaaaaaaaaB) calculated for the byte string from “MAN: Manufacturer’s ID” to the last byte of
“img: Parameter Set Memory Image” is stored in this “crc: Cyclic Redundancy Check”. The receiving
unit checks the value, and if it is not correct sends an error as a re-request.
38