# Ignition and Raspberry Pi GPIO

**URL:** <https://forum.inductiveautomation.com/t/ignition-and-raspberry-pi-gpio/37306>\
**Category:** Ignition\
**Created:** [August 3, 2020, 6:45am UTC](https://forum.inductiveautomation.com/t/ignition-and-raspberry-pi-gpio/37306 "2020-08-03T06:45:58Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\
**Post date:** [August 4, 2020, 6:38am UTC](https://forum.inductiveautomation.com/t/ignition-and-raspberry-pi-gpio/37306/4 "2020-08-04T06:38:21Z")

</div>

The alternative is making a driver module using a Java GPIO library (like PI4J).

That driver could then provide the pins as tags.

If you want to stick to scripting, you could include a Java library in Ignition, and call to that. see [Adding java custom classes to Ignition](http://forum.inductiveautomation.com/t/adding-java-custom-classes-to-ignition/15202) . Or you could use OS calls to shell program that can communicate with the GPIO.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-and-raspberry-pi-gpio/37306)._