Articles in this section

Troubleshooting: Factbird Production Counts Are Too High (Double Counts or Spikes)

Summary: Use this guide to troubleshoot when production counts are higher than actual output due to double counting, false triggers, or data spikes.

Symptom

You may be experiencing this issue if:
  • The counter increases by 2–3 when only 1 product passes

  • Counts are consistently 2x or 3x actual production

  • Random counts occur when nothing passes

  • Sudden unrealistic spikes appear in production data


Prerequisites

Before you begin, please confirm:
  • The DUO is powered on

  • The sensor is securely mounted and wired correctly

  • You can observe live counting behavior while products pass


Diagnostic Steps

Follow these steps in order.
  1. Verify debounce value is not too low

    1. What to check: Review the debounce setting in the DUO configuration.

    2. What result indicates success: Debounce is high enough to prevent multiple triggers from one product.

    3. If result is not correct, increase debounce incrementally (start at 5,000 µs and adjust as needed), then test with 10 manual passes.

  2. Observe sensor behavior during one product pass

    1. What to check: Watch the sensor LED and DUO LED during a single product pass.

    2. What result indicates success: Both LEDs activate once per product.

    3. If result is not correct, inspect for mechanical vibration, reflective surfaces, or product features causing multiple triggers.

  3. Review historical data for spikes

    1. What to check: Identify unrealistic spikes in the data.

    2. What result indicates success: Spikes do not reoccur after debounce adjustment.

    3. If result is not correct, inspect for electrical noise or unstable wiring.


Common Root Causes

  • Cause 1:
    • Debounce set too low, allowing multiple triggers per product.

    • Increase debounce time and validate against live production.

  • Cause 2:
    • Mechanical vibration or electrical noise causing false triggers.

    • Secure mounting, inspect wiring, and eliminate environmental interference.


Resolution

Once resolved:
  • Each product results in one count only

  • No random counts occur when the line is idle

  • No unrealistic spikes appear in data


If The Issue Persists

Contact Support and include:
  • DUO serial number

  • Current debounce value

  • Screenshot of recent spike timestamps

  • Video showing sensor behavior during one product pass


Related Articles

Was this article helpful?
0 out of 0 found this helpful