- Background
- Versions Required
- Exploration LOG
- FAQ
- How can I get this new feature?
- When will the Android version be updated?
- How to update the app for IOS to get it?
- In the new version of the app, what is the logic of turning off detection, zone detection, and excluding detection in there?
- Setting up multiplayer mode, but reopening the app, it won't save?
- I have two 2As. The HLK radar app seems to find them, then seems to get stuck (see photo).
- Signal is good (between -30 and -70) but clicking on update firmware is not responding
- The ‘true’ multitracking is now enabled regardless of using the hilink app to enable that option?It will continue tracking both the non active target (sitting/lying down) and the active targets?
- I am a developer, what is the protocol for the new firmware version?
- Others
Background
When the initial firmware for the LD2450 was released (May '23), the multiplayer mode wasn't fully available, being able to detect more than one person, but in the end keeping the most active target.
Hilink promised to provide this setting, and after a long wait, in mid-October '23, a new firmware and a new APP (HLKRadarTool V1.4.0
) finally gave us multiplayer mode. As well as, in true Hilink style, a separate setup feature was turned on for the Bluetooth protocol.
We'll summarize some of the information we know here, along with an explanation from the Hilink developers. Hopefully this will help you understand the feature better.
Versions Required
Tool | Version |
APP: HLKRadarTool | ≥ V1.4.0 |
LD2450 Firmware | ≥ V2.02.23090617 |
Exploration LOG
FAQ
How can I get this new feature?
- Update
HLKRadarTool
to the new new version (V1.4.0) and update the LD2450 firmware to the new firmware (V2.02.23090616
) in the APP.At this point the new features of the APP will be visible.
When will the Android version be updated?
On October 17th (CST), after Tiep Pham Minh
discovered that the Play Store version has now been updated( 1.1.53
)
How to update the app for IOS to get it?
- It can be found by searching for
HLKRadarTool
in the APP Store, or you can try going directly to link. - From the current version (LD2450 firmware `V2.02.23090616` ), if zones are turned on, it affects the valid output. This means that if driving to zone detection, then only objects in the zone will result in a detection output, otherwise it is equivalent to no one being present. On the other hand, if area filtering is turned on, then excluding targets in the area will result in no output.
In the new version of the app, what is the logic of turning off detection, zone detection, and excluding detection in there?
From the current version (LD2450 firmware V2.02.23090616
), if the zone is turned on, it affects the valid output.This means that if driving to zone detection, then only objects in the zone will result in a detection output, otherwise it is equivalent to no one being present. On the other hand, if area filtering is turned on, then excluding targets in the area will result in no output.
For this case, this is Hilink's developer reply:
In case of area filtering mode, if there is a moving target in the set area, it will be filtered automatically. It will not be reported.Region detection is to detect targets under the region only. Region filtering is to detect targets outside the region only; region off, is not to do region judgment. If you want to judge which region the moving target belongs to, in fact, according to the coordinates can be, the target is reported with coordinates. Set the region can also be queried through the command, this piece of us will also evaluate, whether the protocol to mention. Now the three areas can be user-defined one or more, and in the future will be added to the presence detection.
- Detection area and filtering area at the same time: targets in the detection area and not in the non-detection area are output;
- Only detection area: moving targets outside the detection area are not detected;
- Only filtering region: only targets outside the filtering region are detected;
This one was confirmed at the beginning, but I felt the logic would be ambiguous, so I followed the current one to come out first
This kind of rule, the current serial port reporting will need to add a few more fields, and the logic will be a bit roundabout for the user. The logic is a bit convoluted for users. We may come up with a separate test firmware later.
Also about the area setting, later may consider adding fan angle on the basis of rectangular box, specifically for fans and other application scenarios. Later in the test firmware this will be mentioned, or to see everyone's feedback, there are good suggestions we will modify ota send.
Setting up multiplayer mode, but reopening the app, it won't save?
The response we got from the developer is that it is currently being investigated and will be fixed in a future firmware and app.
I have two 2As. The HLK radar app seems to find them, then seems to get stuck (see photo).
(From Brian F Morgan
@FB)
From the graph, the signal -96 is in a very bad situation.
Since the LD2450 has a short Bluetooth operating range when not using an external antenna, please try to update it by bringing your cell phone and the 2A close together.
Signal is good (between -30 and -70) but clicking on update firmware is not responding
V1.4.1)
has been completed and we tested it on a new device and it worked fine! So the situation seems to be resolved. (2023-10-18t09:53:13)The issue didn't seem to be there on October 16 (CST, GMT+8), and the problem occurred on October 17 (and is still there on October 18), and we have confirmation from the HiLInk developers that there is a current bug:
I'm aware of this issue, and will have an update out later today, it's a compatibility issue with the 2450 device firmware.
The ‘true’ multitracking is now enabled regardless of using the hilink app to enable that option?It will continue tracking both the non active target (sitting/lying down) and the active targets?
(by Shaq@HA community
)
In terms of multiplayer mode, it might just keep tracking multiple objects, whereas single-player mode is similar to the behavior of the LD2410 (tracking only one of the most active targets).
And the current firmware has not been updated for static capability enhancements, that seems to be in another program at the end of the month.
I am a developer, what is the protocol for the new firmware version?
Looking at the documentation, the source code part isn't too complicated, it's mostly just more switches for Bluetooth, and a multiplayer mode switch.
As well as some protocols for regional settings.
But since the app is all directly operable (except for the bluetooth switch), we haven't bothered with this implementation yet.
For the documentation, we try to give you a copy with machine translation.
Good luck!