LD2410C randomly triggers presence detection

Viewed 35
ld2410c

Hi Hi-Link,
I have nearly 30 LD2410C modules in use, and about 10 of them have started acting up. They randomly report a presence event (still or motion) that lasts less than a second, even though all gate values remain below their thresholds during the trigger.

I’ve already tried reflashing the firmware (I’m on the latest version), but it didn’t make any difference. When I replace the problematic module with another LD2410C in the exact same location and setup, the issue disappears — which strongly suggests the sensor itself is at fault.

Is there anything I can do to recover these modules, or are they simply failing and need to be replaced? I’d appreciate any guidance on whether this is a known reliability issue or if there’s a recommended fix

Wasn't sure if I need to respond to the AI message but it's not configuration settings of the gates. As I mentioned above, the motion/still get triggered even though the logs show that the energy is below the thresholds.

Yaniv•
1 Answers

Hello, could you pls help to share us how long is the unmanned delay time? thank you inadvance.
If the unmanned delay time is set to 0s, there may be a frame that is triggered but not displayed in the app. Therefore, don't set the unmanned delay time to 0s. recommended to set it to more than 5s.
More question,pls feel free to contact our team: info@hlktech.com

HLK-Ellen186

Thank you @hlk-ellen,
I have unmanned set to 0. My understanding is that unmanned works the opposite way—once presence is detected, it should stay active for the number of seconds defined by the unmanned value.

My issue is different: I’m seeing still or motion triggers even when all energy levels are BELOW the configured thresholds.

I emailed support@hlktech.cn but haven’t received a reply, so I’ll try info@hlktech.com next.

Yaniv•

One more note — these sensors had been running flawlessly with the same configuration for over a year. The only major change was updating the firmware from 2.04.23022511 to 2.44.25070917. I even tried downgrading a few units to rule that out, but the issue persisted.

Yaniv•

Hello, I have received your question along with the second email.
Please help confirm the following items:

  1. Are the threshold values set for the problematic and normal modules the same?
  2. You may perform a background noise test using the radar App tool, then check and share the results.
HLK-Ellen•
Related
URGENT: Can we sense a non-living object solely with LD2410C?
1 answers