Human detection 2410B

Give it a try, it costs you nothing !
Post Reply
User avatar
Basicboy
Posts: 179
Joined: Sat Jul 20, 2024 11:42 am
Location: Australia
Has thanked: 56 times
Been thanked: 13 times

Human detection 2410B

Post by Basicboy »

I found this on aliexpress and it looks quite interesting
https://www.aliexpress.com/item/1005006315304472.html

I understand I can use the out pin to tell me if there is someone around or not, but I was hoping Annex would also support the serial input which includes much more information
I love this community!
User avatar
PeterN
Posts: 647
Joined: Mon Feb 08, 2021 7:56 pm
Location: Krefeld, Germany
Has thanked: 298 times
Been thanked: 363 times
Contact:

Re: Human detection 2410B

Post by PeterN »

Hi BasicBoy

One of the most popular and beautiful functions of today's virtual libraries, even may be THE best feature, is THE SEARCH BUTTON ;-)

[Local Link Removed for Guests]

[Local Link Removed for Guests]

[Local Link Removed for Guests]

[Local Link Removed for Guests]
User avatar
Basicboy
Posts: 179
Joined: Sat Jul 20, 2024 11:42 am
Location: Australia
Has thanked: 56 times
Been thanked: 13 times

Re: Human detection 2410B

Post by Basicboy »

Thanks Peter
I actually searched in the Annexhelp for the module number but there was no match. I assumed (now I know mistakenly) that this means that it's not implemented with Annex. From now on I guess I will have to search the forums as well before I come to a conclusion.

Is there a way to make a new "index" thread and link to it all such important posts like this one?
I love this community!
User avatar
PeterN
Posts: 647
Joined: Mon Feb 08, 2021 7:56 pm
Location: Krefeld, Germany
Has thanked: 298 times
Been thanked: 363 times
Contact:

Re: Human detection 2410B

Post by PeterN »

Very often, a new sensor or actuator comes with a well-known interface, such as serial, I2C, SPI, etc. However, it communicates in its own specific protocol over that interface. By using the generic interface commands/functions provided by Annex, it is often straightforward to “talk” to the device and set up a BASIC program to translate its input and output.
In some cases, this approach may encounter challenges, such as critical timing requirements or the high complexity of the input/output. These situations can make it necessary—and more convenient for the user—to implement a dedicated “driver” for the device.
Each “new” driver becomes an integrated part of Annex, but whether implementing a driver is a good idea depends on various factors and circumstances.
For example, regarding the LD2410 and even more so the LD2450 (as well as many other sensors/actuators), you can find posts on the forum discussing how to use BASIC code to create a “driver” or how to utilize a “real” driver.
Post Reply