Max Value for Command GPIO: Pulse,<GPIO>,<value>

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
alwashe
Normal user
Posts: 4
Joined: 10 Dec 2018, 14:32

Max Value for Command GPIO: Pulse,<GPIO>,<value>

#1 Post by alwashe » 09 Aug 2019, 14:31

what ist the max value for Pulse?

When I use 3999ms as value it works and I get a log entry.
But when I use 4000ms as value it works but I don't get a log entry.
Why?

[edit]
ok I think I found the answer: https://espeasy.readthedocs.io/en/lates ... e#commands

before I just knew this site: https://www.letscontrolit.com/wiki/index.php/GPIO

User avatar
ThomasB
Normal user
Posts: 406
Joined: 17 Jun 2018, 20:41
Location: USA

Re: Max Value for Command GPIO: Pulse,<GPIO>,<value>

#2 Post by ThomasB » 09 Aug 2019, 20:56

Sounds like you found the solution. An important thing to note here is that the Pulse rule command is a blocking event. The P001 plugin uses the delay() function for this action, so nothing else can occur while the pulse is active. That is why you must avoid it on long time periods because important scheduled system events will be adversely delayed and/or lost.

The LongPulse and LongPulse_ms commands don't block (they use the PluginTaskTimer instead of a hard delay). So use these commands instead in your long duration pulse rules.

- Thomas

alwashe
Normal user
Posts: 4
Joined: 10 Dec 2018, 14:32

Re: Max Value for Command GPIO: Pulse,<GPIO>,<value>

#3 Post by alwashe » 10 Aug 2019, 12:31

Thank you very much for that info.

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 12 guests