Welcome to our Knowledge Base

Setup and Settings

You are here:
< Back

Cash Actions

This view is primarily a list of all of the cash actions that have occurred for a selected time period. The table contents consist of:

  • Event ID#
  • Date of event
  • Time of event
  • Activity
  • The receipts scanned ID
  • The values changed during a Fill event
  • Value of the event
  • Total fills – The amount added to the cassettes during the selected period
  • Total dispenses – The amount paid to players during the selected period
  • Total delta – The difference between the Cassette fills and Cashing Out

Additionally in this view there are two buttons used to perform redemptions.  If you press ‘Manual redemption’ then a popup will appear with a text area visible.  In case there is damage to the scannable code, on a receipt that contains a printed-text redemption code, you can enter it here to process the transaction.

Additionally there is a ‘Large Redemption’ option.  When this is selected the scanner will activate and a reward receipt can be scanned. When a code is validated using this method there is no maximum value limit used.

Logs

The Logs view displays all of the actions that may occur on the kiosk that are unrelated to practical cash events. The first time that a system is installed you can expect to see initial logs reporting that the door has been opened and closed.

The table contents consist of:

  • Event ID#
  • Date of event
  • Time of event
  • Activity

The ‘Activity’ listed is any of these events:

  • Door opened
  • Scanner model changed to: XXX
  • Printer model changed to: YYY
  • Cassette #X – Bill rejected
  • Cassette #Y – Error Logged
  • Cassette #Z- Refilled to ZZZ
  • Fill requirement changed to: 500 / 500 /100 / 0
  • Denominations changed to: 20 / 5 / 100 / 0
  • Min bills changed to: 10 / 5 / 5 / 0
  • Location details updated. (if any of name, address, phone x3 is changed)
  • Paper jam
  • Out of paper
  • Printer not responding
  • Scanner not responding
  • System reboot triggered
  • System booted
  • System shutdown by user
  • Internet connection lost
  • Internet connection connected
  • Software updated to: vX.YY

Components

The Components view gives a simple look into the Fill status of each cassette, and listed all of the receipt printers that have been associated with the system.

The cassette meter’s height is defined as a percentage of the desired fill rate of each cassette, with the denomination and actual bill count listed for each.

The associated printers are listed, and if authorization to accept a certain printer needs to be removed, the user can simply click the associated red X icon and enter the 9 digit serial of the device.

Adding a printer

In order to authorize a given Pyramid Phoenix Thermal Printer you will need to print off the unique QR ID code of the printer, and then register with the system.

  • Print the QR ID code from the printer
  • Select ‘Add Device’ and the scanner will activate
  • Scan the code from the printer

Settings

Location Information

These are the details used to populate information onto a printed receipt. None of these are required in case some information is desired to be excluded. It is important that you make sure to define your correct time zone for your location.

Hardware

This is specifically for future device compatibility in the scenario that we can operate with alternate configurations. As part of the standard configuration these both should be set to Generic.

Max payout before handpay

Some locations prefer to not have large awards paid automatically, and want either the servicer or an employee to validate the ticket’s authenticity first. Using this field you can assign any value desired in order to invoke this response.

Denominations

No secrets here–you can define the denomination used for each cassette. Different game combinations produce different patterns of bill dispensation, so each location can configure their optimal sort order.

Maximum fill capacity

This area allows you to define the physical limits of a cassette. If a user attempts to exceed this value when performing a Fill, the system will restrict them from entering the value as it is physically impossible.

Fill target levels

Just because a cassette can hold 1,000 bills doesn’t mean that you always want to fill to the max. Each cassette can have a different target fill count defined for your servicer.

Cassette warning levels

You can independently define a fill count for each cassette to trigger the notice.  When a cassette reaches this defined count, then the entered email will be notified that this level has been reached.

Min# of bills before ‘Out of Service’

Just as the title implies, you can limit the machine functionality in order to avoid a situation where a machine might make only a partial payment on a ticket, leaving the player unable to collect their awards due.

**Note: Any time that your cassette settings are adjusted a system reboot is required.

Support Phone Numbers

These numbers are shown at the bottom of the screen for authorized users. In case of a system outage or mechanical issue, you should beagle to contact your servicer here.

Update Device Login

Using this sub–form the user can update both the login and password for this machine. The password must be at least 8 characters long.

Action Buttons

  • Reset – Wipe all information from the system to prepare for it to be installed in a new location.
  • Shutdown – Safely power down the kiosk
  • Restart – The first step in troubleshooting, of course, is ‘Did you restart it?’
  • Update – The new software version should be loaded onto a USB drive and inserted into the system. Once you tap this button the upgrade process will commence.
  • Save – Save any changes made to the settings page

Fill

The Fill view describes the current cash configuration of the kiosk. Each Cassette has its own details of:

  • Denom – The current denomination assigned
  • Fill target – The ideal bill count to be loaded into the cassette
  • Bill count – The current count of bills in a given cassette
  • Rejected – if there is an issue dispensing a bill, it is not dispensed and sent to a Reject Bin in the cabinet. This is a count of how many bills the system expects to be inside the Reject Bin.
  • Total Bills – The total of loaded and rejected bills for each denomination.
  • Value – the total dollar value of each denomination in the machine.

Standard Fill

When selected the servicer is informed of how many bills the system expects to be added to each cassette in order to reach the defined Fill Target Level. By default a servicer cannot ‘Complete Fill’ until at least one of the entries has been ‘confirmed’.

When at least one entry is selected, only at that time is the servicer able to Complete the fill. Only Confirmed entries will be updated on the system.

Ad Hoc Fill

When this mode is entered a user can add (or subtract) any number of bills to any of the cassettes.

Example: The servicer left a location they just serviced with some extra $5.00 bills. They stopped into a different location to check that location’s Kiosk status. They see that the $5 cassette is only half full of the 500x Target Fill, but they only have 80x $5 bills on them so they cannot do a Standard fill. The user chooses to enter ‘80’ into the 5.00 cassettes “# Added Bills” field, and presses confirm. The cassette now has a bill count of 330. 

To subtract  bills from a cassette you use negative numbers.  Example:  It’s Sunday and the banks are closed.  You have a location with a full $5.00 cassette, and another location that is almost empty.  You go to the first location and remove 100 $5.00 bills.  You perform an ad hoc fill of -100 $5.00 and submit.  You then travel to the empty location and perform another ad hoc fill of 100 bills.

Rejects

When a bill cannot be handled by the dispenser it is passed into a reject repository.  When you perform a Fill (of either type) you can see the count of each type of bill that has been rejected.  When a fill is completed these counts will revert to zero, as it is expected that the servicing agent has correctly emptied the repository at the time of fill.

Tags: