Get PWM value in any way

[darkchris90]

Hi,

is it possible to get the current PWM status in the version 20190817? I need it for fhem. In some early versions it was in the state variable but now there is only 0,1,-1 and sometimes -2.

Where can I change the source code to get the value? I changed the code on my own and tried to modify the globalMapPortStatus directly or with the function savePortStatus. I prepared a struct which has the PWM value in the state and the output variable, but it doesnt work. I also changed the type of state to uint16_t like in the older versions.

Thanks

[grovkillen]

I use a custom event and send the wanted value, which I store as in internal variable as well as setting the pwm.

So conclusion, you cannot get the value any other way currently.

[darkchris90]

Good evening,

thank you for the fast answering. Can you explain the custom event and how to use it?

[grovkillen]

Using rules you create an event using the event command.

https://espeasy.readthedocs.io/en/lates ... Rules.html

[darkchris90]

Ah ok, I thought you talked about something in the code, because of the internal variable. I will try it. Thank you!

[Cdzn]

How to store adn read PWM to/from Dummy values?
I read this but can`t understand syntax. What exactly used here and what not

For any plugin that registers the used pin(s), the last set pin state can be retrieved, either regular pin state or PWM state, by using this syntax: [Plugin#<pluginId>#Pinstate#N]

Also where i can find plugin and pluginid?

[TD-er]

See the documentation on referring to the pinstate of a specific pin:
https://espeasy.readthedocs.io/en/lates ... task-names

And some example here: https://espeasy.readthedocs.io/en/lates ... tem-events
You need to scroll to the "Matching events" section as the example is at the end of the section above it.

[chromo23]

How to store adn read PWM to/from Dummy values?

To put a value in a dummy device use taskvalueset:
https://espeasy.readthedocs.io/en/lates ... skvalueset

The pwm value you would get with:

Code: Select all

[Plugin#GPIO#Pinstate#12]

...assuming your GPIO is 12
As also discussed here: viewtopic.php?t=9801

So to write to a dummy device simply use:

Code: Select all

TaskValueSet,<name_of_dummy_device,<value_name>,[Plugin#GPIO#Pinstate#12]

To read the value use:

Code: Select all

[<name_of_dummy_device>#<value_name>]

e.g.:

Code: Select all

 LogEntry,'[MyDummy#MyValue]'

[Cdzn]

This is what i can`t understand) I though should use "status,g,5" in command line or something! Thanks a lot. I have PWM fan and wanted to store and restore the last duty.

[Cdzn]

Stil can`t get success.
I wrote 3 rules
1st for restore the last PWM value:

Code: Select all

on System#Boot do
  PWM,5,[TestMemory#Dummy]
endon

2nd for triggering pwm:

Code: Select all

on pwm do
  PWM,5,%eventvalue1%
  //Publish %sysname%/GPIO/GPIO5,[Plugin#GPIO#Pinstate#5]
endon

3rd when the PWM changing duty this should store in memory last value:

Code: Select all

on pwm#state do
  TaskValueSet,TestMemory,Dummy,[Plugin#GPIO#Pinstate#5]
endon

When i push the button with this code

Code: Select all

http://192.168.0.123/control?cmd=event,PWM=1023

fan start spining at max speed and should store this value in Dummy device, but it`s empty.

Image.jpg (22.53 KiB) Viewed 2554 times

[Cdzn]

I guess this is not working because the PWM#State is still 0 and did`t change value when u call it via http. This is why taskvalueset wont work. I could see changes in logs but i dunno.

[Micha_he]

Maybe, because evantname and command are the same !?

[TD-er]

When in doubt whether events are handled and if so with which eventvalues, you can always use "logEntry" to create logs.

Code: Select all

on pwm do
  PWM,5,%eventvalue1%
  //Publish %sysname%/GPIO/GPIO5,[Plugin#GPIO#Pinstate#5]
  logentry,"On pwm Do: EventValue: %eventvalue1% PinState: [Plugin#GPIO#Pinstate#5]"
endon

And please note that rules parsing ends when a matching event is found.
So if "on pwm do" is before "on pwm#state do", the latter one may not be processed. (not 100% sure this is the correct example, but you get the idea)

[chromo23]

2nd for triggering pwm:
...
3rd when the PWM changing duty this should store in memory last value:
...

Why not combining these two?

Like:

Code: Select all

On pwm Do
  PWM,5,%eventvalue1%
  TaskValueSet,TestMemory,Dummy,%eventvalue1%
  //Publish %sysname%/GPIO/GPIO5,%eventvalue1%
Endon

[Cdzn]

Maybe, because evantname and command are the same !?

Nope, coz this only rule is working fine, except others. command successfully executed when i send the duty cycle. But it wont save value in dummy

[Cdzn]

2nd for triggering pwm:
...
3rd when the PWM changing duty this should store in memory last value:
...

Why not combining these two?

Like:

Code: Select all

On pwm Do
  PWM,5,%eventvalue1%
  TaskValueSet,TestMemory,Dummy,%eventvalue1%
  //Publish %sysname%/GPIO/GPIO5,%eventvalue1%
Endon

it`s working. YAASS))
Td-er was right, i guess there problem was in sequence.
Thank You all for help!