07 Setting up Conductor

The Raspberry Pi that controls ALL of the gantries is not connected to any of the gatries. It is, however, connected to the same network as the other Raspberry Pis. We call this Rapberry Pi the "Conductor."

In this example, the Conductor's hostname should be set to "conductor" so that its user interface is available at http://conductor.local.

In order for the "Conductor" Raspberry Pi to work, it needs to know the name and IP address of each gantry.

1. Go to the Conductor user interface at http://conductor.local

2. Set up the "conductor" user interface.

   1. Select "Conductor _______" where the ______ is the name of your particular board type (Smoothieboard or Printrboard, etc.).
   2. Click the "Create" button.
3. From the main page ("http://conductor.local") select "Conductor___________", just to the right of the plus sign.
4. Add "bot1" to the Conductor by adding its name, "bot1" and it's endpoint "http://bot1.local/v1/bots/solo" to the Player form at the bottom of the page.
5. Click the green Add Player button.
6. Repeat for any additional gantries, i.e. bot2, bot3, bot4, etc...
7. When you have added all of your gantries, click the green "Connect" button. You should now see "Bot1," "Bot2" etc. buttons at the top of the screen.
8. By clicking on each of the individual gantries available at "http://conductor.local" (bot1, bot2, etc...), verify that each of the gantries is providing position feedback in the "POSITIONING" field. You should see a number in the position fields.
9. In case of errors, sometimes a reboot of the software is necessary. We have built in a reset button at the bottom right of the screen. Clicking it will restart HardwareHub and refresh your page.