Raspberry Pi RASPIVEND, Быстрая справка

Страница: 7 / 51

<HEADER> <CMD> <SUBCMD> <PARAMETERS> <CRC>
always 0xFE 1 byte 1 byte variable length, depending on subcommand 1 byte
Table 2: Low level message format
- <HEADER> – Is always a byte with a value of 0xFE.
- <CMD> - Defines the command group sent to the RASPIVend.
- <SUBCMD> - Defines the specific subcommand of the command group.
- <PARAMETERS> - Defines the command parameters that will be send to the MDB
peripheral (for example, the maximum credit that the INTERFACE should accept or the
change it should return from changer). Some commands are not requiring parameters.
Also, the variable length depends on subcommand.
-
<CRC> - Defines the message checksum. The <CRC> is calculated as an XOR of all
message bytes, including the <HEADER>. For example, the command to enabled the bill
validator is: 0xFE 0x42 0x02 and the CRC for this command is 0xBE. Transparent mode
can be used for any application.
2. Communication parameters
The communication settings should meet the following specifications:
a. For the peripherals (excepting the MDB bus), there is no restriction regarding the serial
port settings you need.
b. For then MDB communication parameters:
Parameter Value
baud 57600
data bits 8
parity NONE
hardware flow YES (RTS/CTS)
software flow NO
Table 3: MDB communication parameters
© 2016 – AUTOMATROM SRL – www.vendingtools.ro