LAI Games Let's Bounce, Operator'S Manual

Page: 29 / 90

29
HARD ERRORS
This category of errors is used to identify specific errors serious enough that gameplay must be
stopped, either to prevent damage to the machine or because it would result in a negative gameplay
experience for the player.
When a hard error is triggered, the error name is still displayed on the credit display, in addition to
the words “hard error.”
Name Cause Solution
Ball Gate Error
The ball gate sensors are not
being triggered
Check all three ball gate
position sensors are connected
correctly.
Use the operator menu to
check that the ball gate is
being correctly detected by all
three sensors
– Run Test > Ball
Dispense > Run Ball Dispense.
Ensure there are no balls stuck
underneath the ball gate
– this
can prevent the gate from
returning to the home sensor.
Ball Error
Not enough balls to continue
gameplay were detected
Check that the ball sensor is
connected correctly.
Ensure that there are enough
balls loaded into the ball chute
(no less than 50).
Ensure there are no balls
jammed in the ball gate or
stuck in the chute.
EEP Audit R Error
The CPU cannot read or write
to its on-board EEPROM
resettable audits or is
receiving errors during
communication with the
EEPROM.
Set all audits to default by
viewing the error in the errors
menu and pressing the right
button.
Set resettable audits back to
default by going into the
audits menu and press and
hold the right button. If the
error still occurs, the IC is
faulty and needs to be
replaced.
EEP Audit UR Error
The CPU cannot read or write
to its on-board EEPROM
unresettable audits or is
receiving errors during
communication with the
EEPROM.
Set all audits to default by
viewing the error in the errors
menu and pressing the right
button.
If the error still occurs, the IC is
faulty and needs to be
replaced.