# Questions about the new RPi5 GPIO node

**URL:** <https://discourse.nodered.org/t/questions-about-the-new-rpi5-gpio-node/84208>\
**Category:** Developing Nodes\
**Created:** [2 January 2024 14:55 UTC](https://discourse.nodered.org/t/questions-about-the-new-rpi5-gpio-node/84208 "2024-01-02T14:55:03Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![iiot2k](https://avatars.discourse-cdn.com/v4/letter/i/8baadc/32.png) [@iiot2k](https://discourse.nodered.org/u/iiot2k)\
**Post date:** [2 January 2024 14:55 UTC](https://discourse.nodered.org/t/questions-about-the-new-rpi5-gpio-node/84208/1 "2024-01-02T14:55:03Z")

</div>

I'm currently working on the new RPi5 GPIO node.  
I have questions for you about this:

- Should the node be triggered cyclically or via the input?
- Should only one pin per node be read/written (node input/output is True/False)?
- Or should all selected pins be read/written (node input/output as an array)?  
What do you think ?

---

<div class="post-metadata">

**Author:** ![ralphwetzel](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ralphwetzel/32/53713_2.png) [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)\
**Post date:** [2 January 2024 15:50 UTC](https://discourse.nodered.org/t/questions-about-the-new-rpi5-gpio-node/84208/2 "2024-01-02T15:50:08Z")

</div>

> [@iiot2k](#):
>
> I'm currently working on the new RPi5 GPIO node.

That's great news!

> [@iiot2k](#):
>
> I have questions for you about this:

I'd like to vote for the decision that a _new_ node addressing the specialities of RPi5 should be an update to the existing [node-red-node-pi-gpio](https://flows.nodered.org/node/node-red-node-pi-gpio) node. That might add a bit of complexity to the journey of developing this update - but provides the best experience for users. Those should not need to care about the differences in the architectures of RPi...

Given that the _new_ node is an update to the existing, I'd follow the guidance & setup given there...

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [2 January 2024 16:10 UTC](https://discourse.nodered.org/t/questions-about-the-new-rpi5-gpio-node/84208/3 "2024-01-02T16:10:50Z")

</div>

> [@ralphwetzel](#):
>
> I'd like to vote for the decision that a _new_ node addressing the specialities of RPi5 should be an update to the existing [node-red-node-pi-gpio](https://flows.nodered.org/node/node-red-node-pi-gpio)

+1 for that, unless there is a strong reason for it being a new node.

If I move a flow from an older Pi to a Pi 5 I would hope that I would not need to update the flows to make it work.

---

<div class="post-metadata">

**Author:** ![iiot2k](https://avatars.discourse-cdn.com/v4/letter/i/8baadc/32.png) [@iiot2k](https://discourse.nodered.org/u/iiot2k)\
**Post date:** [2 January 2024 16:50 UTC](https://discourse.nodered.org/t/questions-about-the-new-rpi5-gpio-node/84208/4 "2024-01-02T16:50:07Z")

</div>

Thanks @ralphwetzel and @Colin for the suggestions.  
**node-red-node-pi-gpio** works with the Python RPi.GPIO library.  
Unfortunately, this library no longer supports the RPi5.  
I will use @TotallyInformation suggestion and take the linux GPIO character device method in C/C++.  
When reading the GPIO input, the event method is used in **node-red-node-pi-gpio**.  
First I will read the GPIO inputs with bulk.  
Later I will add the event method because its implementation is a bit more complicated.  
Unfortunately it will be a new node specifically for the RPi5,  
as the distinction between the RPi models becomes very complicated.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [2 January 2024 16:54 UTC](https://discourse.nodered.org/t/questions-about-the-new-rpi5-gpio-node/84208/5 "2024-01-02T16:54:51Z")

</div>

If it is not practical to make it a new node (which I am not qualified to judge) then at least keep it compatible please, so that it is just a matter of switching node-types.

---

<div class="post-metadata">

**Author:** ![ralphwetzel](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ralphwetzel/32/53713_2.png) [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)\
**Post date:** [2 January 2024 17:12 UTC](https://discourse.nodered.org/t/questions-about-the-new-rpi5-gpio-node/84208/6 "2024-01-02T17:12:08Z")

</div>

> [@iiot2k](#):
>
> Unfortunately it will be a new node specifically for the RPi5,  
> as the distinction between the RPi models becomes very complicated.

That might be the case - and that's why I'd like to see that covered by an experienced developer (like you!) rather than by Node-RED users. Under the hood of `node-red-node-pi-gpio` the implementation for RPi5 might be completely different than what's currently existing. I yet don't see any reason to change the interface or create a different node ... unless you hit a road block that is too big to be solved by this community - which I doubt can exist! 😉

---

<div class="post-metadata">

**Author:** ![iiot2k](https://avatars.discourse-cdn.com/v4/letter/i/8baadc/32.png) [@iiot2k](https://discourse.nodered.org/u/iiot2k)\
**Post date:** [2 January 2024 17:29 UTC](https://discourse.nodered.org/t/questions-about-the-new-rpi5-gpio-node/84208/7 "2024-01-02T17:29:45Z")

</div>

Ok, I'll probably develop my own RPi5 node.  
Experienced developers can further develop node-red-node-pi-gpio.  
Thanks again for the suggestions.

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [2 January 2024 18:15 UTC](https://discourse.nodered.org/t/questions-about-the-new-rpi5-gpio-node/84208/8 "2024-01-02T18:15:32Z")

</div>

> [@iiot2k](#):
>
> Python RPi.GPIO library.

I'm not expert but there seems to be a drop in replacement rpi-lgpio. More info here -

[https://forums.raspberrypi.com/viewtopic.php?p=2160578#p2160578](https://forums.raspberrypi.com/viewtopic.php?p=2160578#p2160578)

---

<div class="post-metadata">

**Author:** ![iiot2k](https://avatars.discourse-cdn.com/v4/letter/i/8baadc/32.png) [@iiot2k](https://discourse.nodered.org/u/iiot2k)\
**Post date:** [15 January 2024 17:13 UTC](https://discourse.nodered.org/t/questions-about-the-new-rpi5-gpio-node/84208/9 "2024-01-15T17:13:14Z")

</div>

Is online:

> **[@iiot2k/node-red-rpi-gpiox](https://flows.nodered.org/node/@iiot2k/node-red-rpi-gpiox)**
>
> Node-RED nodes for Raspberry Pi GPIO

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [29 January 2024 17:13 UTC](https://discourse.nodered.org/t/questions-about-the-new-rpi5-gpio-node/84208/10 "2024-01-29T17:13:28Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
