This article covers common Bugcount Analyzer issues related to power and startup, slow performance, and higher than expected or unstable readings. Follow the troubleshooting steps below before contacting Customer Support.
3. Higher than expected or unstable readings
1. Power and startup issues
My Bugcount analyzer will not power on
Power issues are typically related to battery charge level or power supply.
My Bugcount analyzer powers on but will not complete a reading
If the device turns on but does not progress past the startup screen or shuts off during testing, you may notice:
- Indicator lights illuminate, but startup does not complete
- The device is frozen or unresponsive
These issues are typically related to battery stability or storage capacity.
Troubleshooting steps
Step 1: Verify power supply
- Plug the Bugcount analyzer into a wall outlet using the provided USB power adapter.
- Confirm the Status LED is illuminated.
If the device has some remaining charge:
- Press the Power button while plugged in.
- The device should power on immediately.
If the battery is fully depleted:
- Allow the device to charge for 5–10 minutes, then attempt to power on.
- In rare deep-discharge cases, up to 30 minutes may be required before the device responds.
Does the device power on?
-
Yes:
- The device may continue operating while plugged in, or you may unplug and resume portable use.
-
No:
- Unplug for 5 seconds and reconnect.
- Confirm the Status LED is illuminated.
- Try a different wall outlet.
- Try a different USB cable.
If the device still does not power on after 30 minutes of confirmed charging using a verified outlet and cable, contact Customer Support.
Step 2: Reboot the device
If the device powers on but is frozen or resets during a reading, first try a normal restart:
- Press and hold the Power button until the device shuts off.
- Press Power again to restart.
If the issue persists after a normal restart, perform a hard reboot:
- Press and hold the Up button and the Blue Action button.
- While holding both, press the Power button.
- Release all buttons once the screen shuts down.
- Press Power again to restart.
This procedure resolves most temporary firmware or memory lock conditions.
2. Device performance
My device is running slowly
When storage is at or near capacity, the Bugcount analyzer automatically overwrites the oldest stored result to make room for a new one. This process may take a few moments, which can cause the device to respond slowly during or after a reading.
If the device is running slowly, check whether storage is at or near capacity. Allow any in-progress overwrite to complete before continuing. If slowness persists, contact Technical Support.
Troubleshooting steps
To free up space proactively
- Navigate to Settings
- Select Storage
- Choose Erase Stored Results
- Confirm Yes, delete all results
- Allow the process to complete
Individual results can also be deleted from the Results screen. To delete all results at once, use the steps above.
3. Higher than expected or unstable readings
A properly functioning Bugcount analyzer should produce consistent, low-RLU readings when no sample is present and the chamber is fully closed.
First check: Chamber door and DOOR OPEN error
The Bugcount analyzer has a light sensor on the chamber door. If too much ambient light reaches the sensor, the device will display a DOOR OPEN error and will not run a test. If you see this error and cannot clear it:
- Confirm the chamber lid is completely shut before initiating a reading.
- Operating with an open or partially closed lid may allow ambient light to affect results.
Common Symptoms
- Significant variation between repeated measurements
Troubleshooting steps
1. Reduce ambient light exposure
- Ensure the chamber is fully closed.
- Avoid operating in direct sunlight or directly under high-intensity lighting.
- Do not leave the chamber open in bright environments.
If excessive light exposure is suspected:
- Power down the device.
- Store it in a low-light environment.
- Allow several hours of recovery (up to 24 hours in rare prolonged cases).
2. Contaminated or Damaged Components
Inspect:
- Sample chamber interior
Look for:
- Residue
- Scratches
- Cracks
- Clouding
Always use a fresh test tube for each reading. Replacement sample chambers are available through the LuminUltra maintenance kit.
Use only Luminultra-approved Bugcount test kits and consumables. Non-approved kits may produce inconsistent or invalid results.
3. Static Electricity Interference
Static discharge can interfere with Bugcount analyzer sensors and may cause inconsistent readings.
Gloves are recommended in some testing applications—refer to the relevant article on myLuminUltra for guidance. Note that certain glove materials may increase static buildup in dry environments.
If static interference is suspected:
- Ground yourself before testing (touch grounded metal surface).
- If wearing gloves, try a different glove material (e.g., nitrile vs. latex).
- Increase ambient humidity if environment is very dry.
- Move to a different testing location if needed.
4. Customer Support
If issues persist after completing the above steps, contact Luminultra Support.
When contacting support, include:
- Device serial number
- Firmware version
- Description of issue
- Approximate RLU values observed
- Steps already attempted
Contact Us
Need help from our team? You can reach us in any of the following ways:
Submit a request through our myLuminultra Knowledge Center Submit a Request
Email help@luminultra.com
Phone 1-888-389-4491
Available Monday to Friday, 4:00 AM to 4:00 PM EST
If your request is related to an existing order, service request, or support case, please include as much detail as possible so our team can assist you quickly.