Use Cases
Typical use case for Qiba's contact closure solution is presented in the picture below. The system includes a Unigate to handle the input signals and process them to generate the output signals, according to the configurations made in Linuquick portal.
When an input is activated (active low), the respective price (configured in Linuquick) will be asked in the Cashless Reader. If the vend is successful, the "Vend Accept" output will be present in the Relays/Outputs (as configured in Linuquick). If not successful, the "Vend deny" output will be presented in the Relays/Outpus (again according to Linuquick Configuration).
Example - Token Dispenser
Imagine you have an Arcade Game facility where all machines are operated with tokens. The functional requirements for such a solution could be:
- You use a button where you can select the prices.
- Each Price Corresponds to a given amount of Tokens to be Dispensed
- Payment method is Cashless Terminal
- Once the selection is paid for in the terminal, the corresponding tokens are dispensed
The following Figure provides an overview on how the system's components would be interconnected. Once assembled, all that is left is to configure the application with the Token amounts and their prices, and also the logical handling of inputs and outputs. In this case a single output (Relay) would be necessary and the amount of pulses would vary according to configuration as well.
