OS - Linux
Already know what you're doing? Here you go:
If you need older versions of the Phidget22 Linux libraries, click here.
If you need Phidget21 Linux Libraries, click here.
If you're using Phidgets with , you should download the Phidget21 Libraries, as Phidget22 is not yet supported in Artisan.
Getting started with Linux
Welcome to using Phidgets with Linux. If you are ready to go, the first step in creating Linux applications with Phidgets is installing our libraries!
If your Linux machine is running 32-bit Debian, jump ahead to Debian install.
To install our libraries, first install libusb-1.0 development libraries. The exact command and package name will vary depending on distribution. For Debian based distributions, including Ubuntu and Mint, the command would be:
apt-get install libusb-1.0-0-dev
Next, download and unpack the following files:
Open the README file that is included at the top of each directory. This file will give you important information about how to properly install the files.
The libraries are now installed on your machine. Next, let's verify that they are working properly. Jump ahead to verifying.
To install our libraries on Debian, first enter the following command in the terminal:
wget -qO- http://www.phidgets.com/gpgkey/pubring.gpg | apt-key add -
Next, enter the following command if you are running Debian jessie:
echo 'deb http://www.phidgets.com/debian stretch main' > /etc/apt/sources.list.d/phidgets.list
If you are running squeeze (Debian 6), wheezy (Debian 7) or jessie (Debian 8) simply replace stretch in the command above with your release.
Update your package lists:
Finally, install the recommended packages by entering the command below:
apt-get install libphidget22 libphidget22-dev phidget22networkserver libphidget22java phidget22admin
The libraries are now installed on your machine. Next, let's verify that they are working properly.
The best way to verify that your libraries are working properly is to compile and run an example program.
First, download and unpack this C example:
Next, open the terminal at the example location. Compile the example by entering the following command:
gcc HelloWorld.c -o HelloWorld -lphidget22
Run the HelloWorld example:
Your terminal should look something like this:
The HelloWorld program will simply communicate when a Phidget has been attached or detached, as can be seen in the image above.
Your Phidget is now able to communicate with your development machine. The next step is selecting a programming language so you can start to write some code!
Ready to write some code? Select one of the programming languages below:
Great choices for beginners:
Phidget Network Server
The Phidget Network Server is an extremely useful tool that allows you to remotely control Phidgets over your network. If you haven't already, check out the Phidget Network Server page for a complete overview.
Try it out!
In order to try the Phidget Network Server out, you will need a host computer, and a client computer with the Phidget libraries installed:
- Host computer: the computer that is physically connected to the Phidgets via USB and is running the Phidget Network Server.
- Client computer: a computer running a Phidgets application that accesses Phidgets connected to the host computer.
If you only have one computer, don't worry, your machine can act as both a host and a client.
Next, open the terminal on the host computer and type in the following command to run the Network Server in the terminal:
Or, as a daemon:
The Network Server is now running on your machine with the default configuration. If you would like to change the Network Server configuration, you can do so by modifying the following file:
You can also simply point towards your own configuration file with the following command:
phidget22networkserver -c /path/to/configuration/file
Now that you have the Network Server running on your host computer, the next step will be accessing the Phidgets connected to your host computer from your client computer. Follow the steps below:
Open the terminal on the client computer and type in the following command (if you are using a single machine, simply open a new terminal session and continue):
This will list all of the Phidget Servers on your network. Confirm that you can see the Network Server running on your host computer.
After you have confirmed your Network Server is running, type in the following command:
phidget22admin -R -d
This command will list all remote Phidgets on the network. Confirm that you can see the Phidgets attached to your host computer:
The next step will be running a program that uses the Network Server, luckily, every programming language we support comes with example code on how to do this! Jump to programming languages above.
Run Phidget Network Server on boot
If you would like the Network Server to run automatically when your computer boots, take a look at this project.
Setting udev rules
If you don't want to be using sudo to run Phidget programs (including the Network Server) forever, you will want to create a udev rule to allow yourself access to the Phidget when you are not root.
Udev has an easy way to set the owner and permissions of the USB interface of the Phidget - it finds all devices that match a given set of rules, and applies new traits to them. But you need to give udev something to match in order to apply the new settings. Here, we will tell udev to match the vendor code for Phidgets, Inc.
We recommend that you use the rules file included in the library download you have already installed. Check the README file included in that download for information on how exactly to install it, or continue reading here.
The rules for udev are kept in files in /etc/udev/rules.d and are traditionally grouped into order of running (10 runs before 20, 30, etc) and device type (cd, network, etc). There should be one or more files in there already. Simply find the file named 99-libphidget22.rules included with our library files, and move it into /etc/udev/rules.d.
Strictly speaking, the files run in lexical order (i.e. the order they're listed when you use the ls command). A device can match many rules, and all will apply (if possible). If conflicting rules are found, the first rule found is followed.