# Maker and Rasbery pi & Jetson nano GPIO access

**URL:** <https://forum.inductiveautomation.com/t/maker-and-rasbery-pi-jetson-nano-gpio-access/36344>\
**Category:** Maker\
**Created:** [July 3, 2020, 2:43pm UTC](https://forum.inductiveautomation.com/t/maker-and-rasbery-pi-jetson-nano-gpio-access/36344 "2020-07-03T14:43:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![joev](https://avatars.discourse-cdn.com/v4/letter/j/b4bc9f/32.png) [@joev](https://forum.inductiveautomation.com/u/joev)\
**Post date:** [July 3, 2020, 2:43pm UTC](https://forum.inductiveautomation.com/t/maker-and-rasbery-pi-jetson-nano-gpio-access/36344/1 "2020-07-03T14:43:29Z")

</div>

What is the best way for maker to access The GPIO pins of devices like rasberry pi

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 3, 2020, 3:19pm UTC](https://forum.inductiveautomation.com/t/maker-and-rasbery-pi-jetson-nano-gpio-access/36344/2 "2020-07-03T15:19:22Z")

</div>

I recommend running the [pigpiod](https://github.com/joan2937/pigpio) daemon and connecting to its socket interface from a long-lived asynchronous thread. The client-side python module for that project looks jython-compatible, but you might want to optimize it. Python’s socket module is notoriously laggy in jython.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [July 3, 2020, 4:27pm UTC](https://forum.inductiveautomation.com/t/maker-and-rasbery-pi-jetson-nano-gpio-access/36344/3 "2020-07-03T16:27:12Z")

</div>

This looks neat, I hadn’t seen this before.

I can no longer recommend using Pi4J / wiringpi libraries because they have been abandoned at this point, which is why we decided not to implement some kind of GPIO driver for maker edition.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 3, 2020, 7:46pm UTC](https://forum.inductiveautomation.com/t/maker-and-rasbery-pi-jetson-nano-gpio-access/36344/4 "2020-07-03T19:46:00Z")

</div>

One of my clients recommended it when I ran into trouble with the baseline CPython `RPi.GPIO` module. I had initially rejected pigpio as too heavyweight, as it runs a daemon. He was delighted to prove me wrong. (:

---

<div class="post-metadata">

**Author:** ![joev](https://avatars.discourse-cdn.com/v4/letter/j/b4bc9f/32.png) [@joev](https://forum.inductiveautomation.com/u/joev)\
**Post date:** [July 6, 2020, 2:42pm UTC](https://forum.inductiveautomation.com/t/maker-and-rasbery-pi-jetson-nano-gpio-access/36344/5 "2020-07-06T14:42:16Z")

</div>

the jetson nano comes with a GPIO python library.

1. can a python GPIO library be used with ignition maker.
2. Does the GPIO used with ignition maker have to be in a jython or jave library.
3. Can the maker GPIO library be executed by associating a script to something like a button.  
4.Are there any examples I can look at that show ignition using the GPIO pins.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 6, 2020, 2:51pm UTC](https://forum.inductiveautomation.com/t/maker-and-rasbery-pi-jetson-nano-gpio-access/36344/6 "2020-07-06T14:51:03Z")

</div>

> [@joev](#):
>
> can a python GPIO library be used with ignition maker.

Almost certainly not, as GPIO access from python is likely via a C DLL python extension.

> [@joev](#):
>
> Does the GPIO used with ignition maker have to be in a jython or jave library.

Yes, unless there is filesystem or socket access available.

> [@joev](#):
>
> Can the maker GPIO library be executed by associating a script to something like a button.

Probably not, except for filesystem or socket access.

> [@joev](#):
>
> Are there any examples I can look at that show ignition using the GPIO pins.

Not that I know of.
