If you're reading this article, you've likely had an encounter with the Sensor Inspector, depicted in the screenshot below. The sensor inspector highlights prolonged sensor obstructions negatively affecting the reliability of input detection.
This article provides an overview of how input detection works, resolving issues that might trigger the sensor inspector and performing general system cleaning and maintenance.
How input detection works
The MultiBall system uses a grid of infrared beams to detect interactions with the wall. As soon as both a horizontal and vertical beam are blocked, the intersection point of the beams is transmitted to the active game or app.
As long as only a single interaction is made at a time, the system is trivial.
Once multiple simultaneous inputs are made, things quickly get a lot more complicated: The pairing of blocked horizontal beams with blocked vertical beams is no longer obvious. Blocking objects start casting shadows in which it may no longer be possible to accurately detect new inputs along both axes. In extreme cases where two shadows cast along different axes overlap, input detection is no longer possible.
For this reason, it's important to keep unintended beam obstructions to a minimum. Keep both the sensors clean and the wall clear of any undesired obstacles. To help find such issues, the sensor inspector will appear any time a beam is blocked for more than ~10 seconds.
Resolving Sensor Obstructions
The following step-by-step guide should help you resolve any issues highlighted by the sensor inspector:
- Ensure that nobody is interacting with the wall
Particularly when dealing with younger audiences, it is not uncommon for their unique play-styles to lead to prolonged interactions with the wall.
If removing all players from the wall is enough to resolve the issue, either advise players to change their play style or ask the system operator to disable the sensor inspector for the duration of the play session. More details on this option can be found later on in this article. - Check highlighted border areas and the intersection point for any obvious obstructions
Whether it's a fallen necklace or some pebbles covering the sensor holes or a pool noodle resting against a wall, these are issues that anyone can resolve.
- Remove smaller dust and debris using a vacuum cleaner with brush attachment and/or compressed air
Running a vacuum cleaner along the sensor bar is usually enough to remove any dust that has accumulated over time. A brush attachment is recommended to avoid scratching the sensors.
While dust and debris typically accumulate in easy-to-reach places like on the bottom sensor bar, be aware that other elements such as cobwebs, could also cause issues in more difficult-to-reach areas. The system can't detect at which end of an axis a blockage is caused, so if vacuuming along the bottom sensor bar doesn't solve anything, be sure to also check the top!
For preventative maintenance, we recommend performing this step on a weekly basis.
- Remove the sensor covers and use a lint-free cloth for more thorough cleaning
Remove the covers by unscrewing them using a TX30 Screwdriver. Wipe along the sensors using a lint-free cloth, such as a microfiber cloth.
Do not use any liquid! If unavoidable (e.g., after a spill), please refer to the section "Using liquids for cleaning the sensors" further down in this article.
For preventative maintenance, we recommend performing this step on at least a yearly basis.
- Ensure the system is fully up-to-date
Check the health page of the System in MultiBall admin to rule out any software-related issues. - Recalibrate the sensors
Follow this guide for instructions. - Submit a support ticket
If everything has failed, submit a support ticket from the system's health page in MultiBall admin and we'll do our best to find the cause and get things sorted.
The video below showcases how to vacum and wipe down the sensors:
Disabling the Sensor Inspector
In cases where sensor obstructions are clearly caused by players and a change in player behaviour is not desired or difficult to achieve, it is possible for a system operator to disable the sensor inspector and allow games to continue operating while sensors may be blocked.
Be advised that in this scenario the reliability of input detection can not be guaranteed for all the reasons stated in the "How input detection works" section.
We only recommend this solution as a temporary measure when the system is operated under supervision, as disabling the sensor inspector could lead to other causes for sensor obstructions going unnoticed and degrading the play experience.
To disable the sensor inspector, navigate to the system's settings page in MultiBall Admin. Select the "Menus and overlays" category and within the "Sensor Inspector" section, turn off "Show Sensor Inspector". Click "Update preferences".
You can optionally also disable "Show message" if you want to also hide the message in the top right corner of the screen that appears whenever sensors are blocked for a prolonged period.
Using liquids for cleaning the sensors
Liquids should never be used to clean the sensors unless absolutely necessary. The only exception is in the case of a minor spill where the liquid has not yet entered the sensor itself.
To minimize the risk of further damage, immediately power off the system before attempting any cleaning. Lightly dampen a cloth with purified water (never wet or dripping), and gently wipe the sensors. Ensure everything is completely dry before powering the system back on.
Please be aware that if any liquid enters the sensor itself, the warranty is void and any action taken is entirely at your own risk.