I have been testing this with the latest release and I have been able to produce a setup that works as I need it to, which is really great, so first of all, thanks.
What I have is the standard PWM driving actuators for heat and cool, which I can use the measured state and create and OR situation where either the heat or cool turn on the fan.
But we discussed previously that introducing a PWM to to drive the fan, even when the heat/cool is not activated could be desirable.
So this idea would be, the fan gets turned on by either heat, cool, or the PWM cycle of the fan.
For the PWN to register a duty cycle, it seems that it needs to drive an actuator, which i expected to use as an input into the logical actuator, and that actuator needs to drive a pin. Without the pin the PWN doesn’t drive the actuator.
These are the blox I needed to create to make it work where it works exactly as I would like it to.
And this is the setup of the logical actuator
So I am using a PIN out (Fan - Observing) only for observation so that I can drive one with the logical actuator.
If I drop the Fan - Observing link to the Spark Pins, the Fan PWN is ineffectual.
I’m not currently using the pins for anything else, so all is good, just wondering if I am not using it as intended.