Wish AddListener

[Siam]

hi,

AddListener is a great funktion but i miss the possibility to say by which signal addlistner should trigger
(CHANGE, RISING or FALLING)

I know i can check the Port but today i have found a issue that triggers the addlistner but the port was sometimes so fast back to low that I do not find out which signal has now triggered.

as example i need the Rising trigger the falling i don't need so
i have written a programm which checks the port if the port was high then do someting if the port is low do nothing.
sometimes it works sometimes not this means my signal (which i can't change) is long enough for the addlistner but sometimes to short to to read by the port.

 

[Erel]

The pin listener is very simple. It just checks every iteration, whether the current value is different than the previous value.

You can create such a listener yourself with AddLooper.

 

[Siam]

thanks for this information ! so its running ... solong i don't add some other code it seems we need a hardware interrupt for b4r

 

[Erel]

You can catch interrupts in libraries. Running code directly inside interrupts is problematic and is likely to break all kinds of things.

 

[Siam]

that means i can catch the interrupt and call a b4r sub directly from a library without any problems on b4r side?

 

[thetahsk]

If the hardware platform is AVR based you can change the compiler flags in platform.txt to achieve more speed.
This article describes the procedure.
https://www.instructables.com/id/Arduino-IDE-16x-compiler-optimisations-faster-code/
https://gcc.gnu.org/onlinedocs/gnat_ugn/Optimization-Levels.html

 

[Erel]

that means i can catch the interrupt and call a b4r sub directly from a library without any problems on b4r side?

Almost. It doesn't happen immediately. It goes through B4R message queue. See how receiveEvent is implemented in rWire.cpp.

 

[Siam]

ok i will give it a try Thank you for this information