MR60FDA2 60GHZ mmWave Sensor takes a long time to detect Fall Status

gvt123 · February 15, 2025, 11:14am

I recently bought MR60FDA2 and tested it with the fall_demo code as shown:

github.com/Love4yzp/Seeed-mmWave-library

examples/fall_demo/fall_demo.ino

main


#include <Adafruit_NeoPixel.h>
#include <Arduino.h>
#include <hp_BH1750.h>  //inlude the library
#include "Seeed_Arduino_mmWave.h"

#ifdef ESP32
#  include <HardwareSerial.h>
HardwareSerial mmwaveSerial(0);
#else
#  define mmwaveSerial Serial1
#endif

#define LIGHT_GPIO D0

/****** instance ******/

hp_BH1750 BH1750;  // create the sensor object

SEEED_MR60FDA2 mmWave;

This file has been truncated. show original

I realized it took about 20 seconds for the Sensor to change the status to “EXIST_PEOPLE” to " PEOPLE_FALL"

I would like to ask if there is any API or method or writing bytes to change the settings of the MR60FDA2 by shortening the time to confirm a FALL?

PJ_Glasso · February 15, 2025, 7:13pm

Hi there,
So I’m interested in this as well, Radar vs. IMU on a wearable by the patient. I doubt any firmware code can be changed AS I’m pretty sure it’s proprietary firmware. Let’s see what the Fellow Seeeder’s have to say…BUMP?

HTH
GL PJ

Marco_Mura · February 17, 2025, 3:37pm

Hi!
I have purchased some MR60FDA2 modules too. I don’t think you can change that. Beside this, I am experiencing some issues with the module’s functionality. Specifically, the sensor outputs false positives (i.e., detects a fall) when a person is sitting on a chair at the edge of the fall detection area. Is anyone having a similar problem?