autonomousorganization
/
ao-manual
2
0
Fork 0
Code Issues Pull Requests Releases Activity
User manual for the AO. The same text is intended to be displayed in both the command line (ao-cli) and the web browser (ao-svelte or ao-3).
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1 Commit
1 Branch
0 Tags
389 KiB
 
Tree: 5a1066a0b1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '5a1066a0b1'
${ noResults }
ao-manual/12_administration/1_connecting_hardware.md

1.3 KiB
Raw Blame History

title
Connecting hardware resources

The AO can connect over a wired LAN or wifi to control the GPIO pins on a raspberry pi. This allows hardware peripherals to be connected to the AO, controlled by members, and restricted with a fee or to active members.

To use a hardware resource with the AO, it must be connected, and a custom control panel GUI must be written for it to display in the Resources panel.

To set up the RFID fob:

  1. Plug in your RFID reader device

  2. Find the name of the hardware by finding where your OS has its hardware devices, and save this info for the init process (type it exactly)

  3. Do gpio-export (there are two different numbering systems for the pins)

8 . Set it up to autostart with systemctl

To connect a hardware resource to the AO via a Raspberry Pi:

  1. Install an OS on your Raspberry Pi (we suggest Debian).

  2. git clone https://github.com/AutonomousOrganization/pi

  3. cd pi

  4. npm i

  5. Create a user on your AO for the hardware resource to use (or use an existing user)

  6. npm run init

The AO connect script on the pi will log into the AO as the user and use that access to trigger resource-used events on the server.

GPIO has two modes: BCM and 'board'. For 'board', the order is the physical order of the pins themselves. BCM stands for Board Control Module, and the order is the logical order of the pins.