The HLK-LD2412 has some nice enhancements to the LD2410 (we use it for a range of our radars, such as the 1U, 1WX, 1MS, etc.):
Better antenna design
Larger coverage area
Better static capability
The included light module is also better at performing in low light.
Up to 12 gate detections means you can fine-tune the sensitivity of certain gates by filtering them.
With three resolutions (0.25m, 0.5m, 0.75m), compared to the LD2410, there are 0.5m more.
In our tests, we also found some shortcomings:
The shortest detection distance showed a large numerical error, and the HLK developers explained that the ranging aspect of the radar was weakened in favour of enhanced overall radar detection.
How does this differ from the F2? I’m very happy with the 3 F2 sensors I purchased, but if I was looking to expand my sensor network, how would you describe the use case for the F2 versus the new L12?
Things are still just getting started, and it’s hard to specify how much of a difference it makes, but there are some nice enhancements relative to the LD2410. For the F2, it’s great, but the price is higher.
I think with all these radar modules, even hlk probably can’t figure out how exactly they are any different.
So it’s subtle and we’ll gather more user opinions after our initial testing.
For our first impressions, the ld2412 has a nice relative ld2410 boost, and our sense is that it’s more stable. But the f2 has low heat and strong antennae, it’s nice and one of those don’t worry about it radars. And the ld2412, ld2410 is like one of those manual cars that can be a lot of fun to operate for complex situations where you want to fine-tune (especially with the increase in the number of adjustable doors from 8 to 13, and the addition of 0.5m which is an intermediate resolution between 0.2m and 0.75m). I think it belongs to the kind of people who love to toss it around.
There has been some feedback from the initial L12 users and so far it looks positive, we will be releasing the source code in 1-2 weeks and as time is running out we will get this done as soon as possible. We’ll post an announcement in the screek community when we do, so you can keep an eye out for that.
Hi, quick question on the mmwave sensors you’ve tested.
I have built my own “assistant” based on the 2450 and esp32, so it includes light sensor, LED, speaker, microphone, temp sensor etc and sits in the corner of my lounge.
One of the main problems I find with the 2450 is that if there are 2 people in the room, and 1 person leaves, it marks the as no occupancy. It also isn’t very good at tracking stationary people as we already know.
I like the gimmick of tracking location in the room, but honestly, I’d rather more accurate presence detection. So with the 2410b (or the 2412 which seems like it’s better?), how does it handle the scenario where one person leaves a room?
Since the code is primarily designed for the ESP32-C3 DIO mode of the L12, you can remove it:
components: [esp32, uart, ld2412] inside libraries other than ld2412.
On esp32-c3 the serial port logging functionality is lost, so the patch is used.
Hi @screek-workshop ,
I used your code as reference to adapt the current official code for LD2410. I don’t have to much time to work on this so I removed the engineering part because is way to much for me. One think is missing is the distance resolution which I consider important. Since you wrote that you are working with the production company, do you have more info about this? There is no documented command to read or write this configuration
Hi @screek-workshop,
I can’t find it. In the official product page, the drive folder linked has only one file about the protocol and is dated 21 may. Is the same file that I used until now and I didn’t find any information about the distance resolution
Hi @screek-workshop,
thanks for your help! I managed to add the resolution picklist with the provided document. It was a pain to translate the chinese document in English!
I uploaded all my code to github if someone need it:
amazing, nice work, I’ll give it a try later.
Is there any chance this could be packaged up as a remote component, would be good to benefit from any improvements, rather than downloading files.
Sorry, I was being dim! Thanks for that.
You might want to add the example code for how to integrate it, just for anyone following along months after. Cheers!