2019-07-10 10:59:07 +02:00
|
|
|
|
2020-01-28 19:09:31 +01:00
|
|
|
<script type="text/html" data-help-name="rpi-gpio in">
|
2019-07-10 10:59:07 +02:00
|
|
|
<p>Raspberry Pi input node. Generates a <code>msg.payload</code> with either a
|
|
|
|
0 or 1 depending on the state of the input pin.</p>
|
|
|
|
<h3>Outputs</h3>
|
|
|
|
<dl class="message-properties">
|
|
|
|
<dt>payload <span class="property-type">number</span></dt>
|
|
|
|
<dd>the payload will be a 1 or a 0.</dd>
|
|
|
|
<dt>topic <span class="property-type">string</span></dt>
|
2021-02-11 12:02:00 +01:00
|
|
|
<dd>the topic will be set to <code>gpio/{the bcm spio number}</code>.</dd>
|
2019-07-10 10:59:07 +02:00
|
|
|
</dl>
|
|
|
|
<h3>Details</h3>
|
|
|
|
<p>You may also enable the input pullup resistor or the pulldown resistor.</p>
|
|
|
|
<p>Requires the RPi.GPIO python library version 0.5.10 (or better) in order to work.</p>
|
|
|
|
</script>
|
|
|
|
|
2020-01-28 19:09:31 +01:00
|
|
|
<script type="text/html" data-help-name="rpi-gpio out">
|
2019-07-10 10:59:07 +02:00
|
|
|
<p>Raspberry Pi output node. Can be used in Digital or PWM modes.</p>
|
|
|
|
<h3>Inputs</h3>
|
|
|
|
<dl class="message-properties">
|
|
|
|
<dt>payload <span class="property-type">number | string | boolean</span></dt>
|
|
|
|
</dl>
|
|
|
|
<h3>Details</h3>
|
|
|
|
<p>Digital mode - expects a <code>msg.payload</code> with either a 0 or 1 (or true or false),
|
|
|
|
and will set the selected physical pin high or low depending on the value passed in.</p>
|
|
|
|
<p>The initial value of the pin at deploy time can also be set to 0 or 1.</p>
|
|
|
|
<p>PWM mode - expects an input value of a number 0 - 100. It can be floating point.</p>
|
|
|
|
<p>PWM mode can be used to drive a servo using input values between 10 and 20 only,
|
|
|
|
but will accept floating point values.
|
|
|
|
The GPIO2 pin is best for this as it uses hardware to do the PWM. For better servo support
|
|
|
|
consider the alternative node-red-node-pi-gpiod node.</p>
|
|
|
|
<p>Requires the RPi.GPIO python library version 0.5.10 (or better) in order to work.</p>
|
|
|
|
</script>
|
|
|
|
|
2020-01-28 19:09:31 +01:00
|
|
|
<script type="text/html" data-help-name="rpi-mouse">
|
2019-07-10 10:59:07 +02:00
|
|
|
<p>Raspberry Pi mouse button node. Requires a USB mouse.</p>
|
|
|
|
<h3>Outputs</h3>
|
|
|
|
<dl class="message-properties">
|
|
|
|
<dt>payload <span class="property-type">number</span></dt>
|
|
|
|
<dd>1 or 0 when the selected mouse button is pressed and released.</dd>
|
|
|
|
<dt>button <span class="property-type">number</span></dt>
|
|
|
|
<dd>1, 2, 4 corresponding to left, right and middle buttons, so you
|
|
|
|
can work out which button or combination was pressed.</dd>
|
|
|
|
<dt>topic <span class="property-type">string</span></dt>
|
|
|
|
<dd>set to <code>pi/mouse</code></dd>
|
|
|
|
</dl>
|
|
|
|
</script>
|
|
|
|
|
2020-01-28 19:09:31 +01:00
|
|
|
<script type="text/html" data-help-name="rpi-keyboard">
|
2019-07-10 10:59:07 +02:00
|
|
|
<p>Raspberry Pi keyboard handling node. Requires a USB keyboard.</p>
|
|
|
|
<h3>Outputs</h3>
|
|
|
|
<dl class="message-properties">
|
|
|
|
<dt>payload <span class="property-type">number</span></dt>
|
|
|
|
<dd>contains the keycode value</dd>
|
|
|
|
<dt>action <span class="property-type">string</span></dt>
|
|
|
|
<dd>set to "up", "down", or "repeat"</dd>
|
|
|
|
<dt>topic <span class="property-type">string</span></dt>
|
|
|
|
<dd>set to <code>pi/key</code></dd>
|
|
|
|
</dl>
|
|
|
|
</script>
|