# RPi4 question/info **URL:** \ **Category:** Maker\ **Created:** [July 7, 2020, 5:38pm UTC](https://forum.inductiveautomation.com/t/rpi4-question-info/36444 "2020-07-07T17:38:20Z")\ **Posts on this page:** 1\ **Showing post:** 8
**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 18, 2020, 1:46pm UTC](https://forum.inductiveautomation.com/t/rpi4-question-info/36444/8 "2020-07-18T13:46:15Z")
If no one gets to it first, I'll eventually do a driver based on pigpio, as I noted over in this other thread: > [@Maker and Rasbery pi & Jetson nano GPIO access](http://forum.inductiveautomation.com/t/maker-and-rasbery-pi-jetson-nano-gpio-access/36344/2): > > 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. Its worth noting that the driver could be on any gateway that has network access to the RPi, not necessarily on-board. A single gateway could have multiple driver instances pointing into a cloud of RPi's as if they were "Remote I/O". --- _[View the full topic](https://forum.inductiveautomation.com/t/rpi4-question-info/36444)._