Differences

This shows you the differences between two versions of the page.

--- raspberry-phidget [2015/03/25 17:35] – Stéphane Lavirotte
+++ raspberry-phidget [2016/01/28 12:57] (current) – [Give access USB Phidget InterfaceKit for a regular user] Stéphane Lavirotte
@@ Line 1: / Line 1: @@
+{{:public_namespace:phidgets.jpg?200|}}{{:public_namespace:raspberrypi.png?80|}}
 ====== Install Phidgets on Raspberry Pi ======
 To be able to use Phidget on Raspberry, you will have to do the following steps.
+{{:public_namespace:phidget_ik.jpg?200|}} {{:public_namespace:phidget_sensors.jpg?500|}}
 ===== Install Phidgets librairies =====
@@ Line 15: / Line 18: @@
 </code>
-Then you have to add Phidget available for Mono.
+Then you have to add Phidget .NET library available for Mono. First you have to download the needed packages with the following commands:
+<code>
+wget http://www.phidgets.com/downloads/libraries/Phidget21-windevel.zip
+unzip Phidget21-windevel.zip
+</code>
+Then, to add the library to the Mono GAC:
 <code>
 sudo gacutil -i phidget21-windevel/Phidget21.NET.dll
@@ Line 21: / Line 30: @@
 </code>
-===== Give access to regular user to USB Phidget InterfaceKit =====
+===== Give access USB Phidget InterfaceKit for a regular user =====
 Last step to be able to use the Phidget InterfaceKit on Raspberry Pi is a problem of permissions on files; only root can access to data of usb pluged devices. So for any program working with Phidget InterfaceKit, you would need to run it as root user (with a sudo). Of course, this is not the right solution.
@@ Line 35: / Line 44: @@
 <code>
 Bus 001 Device 004: ID 06c2:0045 Phidgets Inc. (formerly GLAB) PhidgetInterface Kit 8-8-8
-</code>
-As you added a new rule, you have to restart the udev service.
-<code>
-sudo service udev restart
 </code>
@@ Line 48: / Line 52: @@
 </code>
-After adding group and user to group, you have to logout and login again to have the right permissions.
+After adding group and user to group, you have to logout and login again to have the right permissions. Then  you have to restart the udev service.
+<code>
+sudo service udev restart
+</code>