Remote Accessible GPIOs via HTTP

Thanks to Spring 21 team (see below), we have an HTTP interface to the essential LEDs, Switches, Push Buttons.

Start GPIO Server

Since we don’t have access control. It is not recommended to have the server running all the time. When the ZedBoard boots, it is not active.

To control, we have created a service on the zedboard called remote-gpio.service.

To start, use the following command.

systemctl start remote-gpio.service

Check status:

systemctl status remote-gpio.service

Stop the service when you are done

systemctl stop remote-gpio.service

HTTP UI

Connect to your zedboard’s interface http://zedN.nuesl.org:8080 (replace N with your board number).

Remote GPIO Interface Web Page.

Credits

Big thanks to the Spring 2021 team:

• Matt Rizzo: Frontend design and functionality to send/receive data from web app server. As needed, will assist in backend funcationality implementation and or server interfaces via REST API’s (for HTTP Routes) and Websocket calls from Server to Backend.
• Nick Rizzo: Server functionality to translate messages to/from frontend and send/get data from Backend APIs
• Tyler Royere: Backend APIs that interact with pulsecap and kernel remote GPIO modules that allow for reading and writing GPIO state
• Nick Fantasia: Pulsecap kernel module and working partially on its interface with the backend.