![background image](http://html1.mh-extra.com/html/suzohapp/flow-18-cctalk/flow-18-cctalk_product-manual_1408277020.webp)
Manual 18-ccTalk
Version 0.6
Page 19
- Check if all coin counters balance with the request hopper status command.
- Check the coin level status (empty/full) (see next command)
Request Payout high/low status (header 217)
Command : 03 00 01 D9 23
Response: 01 01 03 00 10 EB
The returned data byte is the levelstatus.
The bits of levelstatus have the following meaning:
Bit nr Description
0
Low Level status (1 = low level)
1
High Level status (1 = high level)
2
not used
3
not used
4
Low Level sensor is fitted
5
High Level sensor is fitted
6
not used
7
not used
Table 7: LevelStatus bit definition
In our example the low level sensor in fitted and the level status is normal.
The High Level sensor is fitted bit will however always be low, and cannot be used to check if the high
level sensor is present.
Request Hopper dispense count (header 168)
Command : 03 00 01 A8 54
Response: 01 03 03 00 2E 02 00 C9
The 3 data bytes
(2E 02 00)
represent the 3 byte total dispense counter: 558 (LSB first).
This counter in incremented each time a coin is paid, and is not reset before any new payout.
The counter is erased with a reset. Power off will not reset te counter
Read Data Block (header 215)
Command : 03 01 01 D7 02 22
Response: 01 08 03 00 2E 02 00 D0 01 FF 00 00 F4
In this example Read Data Block 2 is requested.
The 8 bytes in the response
(2E 02 00 D0 01 FF 00 00)
contain the hopper dispense counter
(2E 02 00)
and a checksum
(D0)
over the counter.
Write Data Block (header 214)
Command : 03 09 01 D6 02 00 00 00 00 00 00 00 00 1B
Response: 01 00 03 00 FC
In this example 8 bytes
(00 00 00 00 00 00 00 00)
were send to EEProm Block 2.
This means that Hopper Dispense count, coins paid and coins unpaid are all reset to 0.