Money Controls SCH2, Technical Manual

Page: 28 / 61

SCH2 Technical Manual TSP016.doc Issue 3.0 – January 2005

Money Controls 2005. All rights reserved.
Page 28 of 61
15. Full Initialisation & Payout Sequence
This is an example of a full initialisation and payout sequence on SCH2…
Notation : cctalk command’s are shown highlighted.
Optional… Address Resolution
If { network indeterminate } then
Address poll Ö resolve addresses with BROADCAST address
While { Address clash on any address } then
Address random
Ö
scramble addresses with BROADCAST address
Address poll Ö resolve addresses with BROADCAST address
Request equipment category id Ö identify each device on bus
Address change
Ö
assign new addresses if required
In other words, if we do not know where the serial hoppers are on the bus then we need to
locate them. If any of the device addresses clash then we need to scramble them and look
again. However, since the wiring harness for the hopper should initialise the device addresses
in a non-ambiguous manner, this address resolution software can be avoided.
Inititialisation
Simple poll
Ö
returns ACK to confirm device is attached, powered-up and 9600 baud comms is
working fine
Request equipment category id
Ö returns ‘Payout’. Otherwise you will probably be trying to
dispense a coin from an acceptor !
Request variable set
Ö
connector address ( physical position in machine )
Request serial number Ö store for reference
Optional… Product Data
Request manufacturer id Ö e.g. ‘Money Controls’
Request product code Ö e.g. ‘SCH2’
Request software revision Ö e.g. ‘SCH2-Vx.y’
Request comms revision Ö cctalk comms level
Request hopper coin
Ö
coin name if stored
Request build code Ö level sensor details
PIN Number Unlocking
Test hopper Ö check to see if PIN number mechanism is enabled
If { PIN enabled } then
Enter PIN number
else
Enter new PIN number Ö randomise and log against serial number for
future reference
Optional… Write data block
Ö log host id in user data memory
The PIN number mechanism should only be enabled if the host machine has some way of
remembering it ! The easiest method is to make all the PIN numbers the same but that is not
very secure. It is much better to randomise them but in that case there will be problems if
hoppers are swapped between machines. You may wish to implement a central database of
PIN numbers versus serial numbers or perhaps make use of the user data section of the hopper
memory to store an encrypted PIN number.
Continued…