TroubleshootingGravity

C4001 mmWave sensor – target range stuck at 2.84 m

userHead He.He 2026-01-10 09:13:58 130 Views2 Replies

Hi everyone,

 

I recently bought a C4001 mmWave sensor and I’m having an issue with the reported distance value.

After properly wiring and powering the sensor, I tested both I2C and UART communication using the example code from the DFRobot library. However, the target range is always fixed at 2.84 m, regardless of the actual distance to the target. The same thing also happens with the target number: even when there is nothing in front of the sensor, it always reports 1.

 

Here’s an example of the output I’m consistently getting:

 

target number = 1
target speed  = 1.97 m/s
target range  = 2.84 m
target energy = 0

 

target number = 1
target speed  = 2.15 m/s
target range  = 2.84 m
target energy = 0

 

Observations:

Target number is always 1

Target speed changes randomly (0–2 m/s)

Target range is always exactly 2.84 m

Target energy is always 0

Same behavior over both I2C and UART

Issue persists across power cycles

 

I expected the range value to change when moving closer to or farther from the sensor, but it never does.

Has anyone experienced something similar with the C4001?
Is 2.84 m some kind of default or initialization value?

Any help would be greatly appreciated.

 

Thanks in advance!

2026-01-22 13:52:46

Dear Customer,

Sorry for the inconvenience.

Based on your description, this issue may be related to interference in the test environment or installation conditions. To help us analyze it more accurately, could you please provide the following information:

Photos of your test setup and hardware connections

Description of the test environment (indoor/outdoor, presence of metal objects, walls, moving objects, etc.)

The exact power supply method and voltage

The MCU/board you are using and the example code version

You may also send all the above information directly to our technical support team at [email protected].
Our engineers will review your case and assist you as soon as possible.

Thank you for your understanding and cooperation.

Best regards,
DFRobot Team

userHeadPic DFRobot TechSupport
2026-01-22 05:18:06

Yes, I had exactly the same target range stuck at 2.84 when I first used my c4001. It's definitely a bug. I only had that issue using I2C, and switching to UART seemed to fix it. Try changing to UART, double check the wiring, and try sending a few reset commands to it, not sure what causes it though. 

userHeadPic Wugafuzza