OS - Linux - Revision history

Patrick at 17:17, 18 September 2017

2017-09-18T17:17:53Z

← Older revision		Revision as of 17:17, 18 September 2017
Line 27:		Line 27:
	#*Note that libusb-1.0 may be already on your system, but the development libraries probably aren't.		#*Note that libusb-1.0 may be already on your system, but the development libraries probably aren't.
	#*Search for {{Code\|libusb-1.0-0-dev}} or similar in your distribution package directory.		#*Search for {{Code\|libusb-1.0-0-dev}} or similar in your distribution package directory.
	#*Or install [http://~~www.~~libusb.~~org~~/ from source].		#*Or install [http://libusb.info/ from source].
	#Unpack and install the [{{SERVER}}/downloads/phidget21/libraries/linux/libphidget.tar.gz Phidget Libraries]		#Unpack and install the [{{SERVER}}/downloads/phidget21/libraries/linux/libphidget.tar.gz Phidget Libraries]
	#*From the main unpacked libraries directory, run:		#*From the main unpacked libraries directory, run:

Mparadis at 16:00, 7 June 2017

2017-06-07T16:00:23Z

← Older revision		Revision as of 16:00, 7 June 2017
Line 28:		Line 28:
	#*Search for {{Code\|libusb-1.0-0-dev}} or similar in your distribution package directory.		#*Search for {{Code\|libusb-1.0-0-dev}} or similar in your distribution package directory.
	#*Or install [http://www.libusb.org/ from source].		#*Or install [http://www.libusb.org/ from source].
	#Unpack and install the [{{SERVER}}/downloads/libraries/libphidget.tar.gz Phidget Libraries]		#Unpack and install the [{{SERVER}}/downloads/phidget21/libraries/linux/libphidget.tar.gz Phidget Libraries]
	#*From the main unpacked libraries directory, run:		#*From the main unpacked libraries directory, run:
	#*:{{Code\|./configure}}		#*:{{Code\|./configure}}
Line 43:		Line 43:
	====Software====		====Software====

	To confirm that the libraries were installed correctly and can be used in code, you can use the [{{SERVER}}/downloads/examples/phidget21-c-examples.tar.gz Phidget Generic C Examples].		To confirm that the libraries were installed correctly and can be used in code, you can use the [{{SERVER}}/downloads/phidget21/examples/c/phidget21-c-examples.tar.gz Phidget Generic C Examples].

	The easiest way to confirm correct installation will be to compile and run the {{Code\|HelloWorld}} C example, included in the examples download. This does not involve writing any C code, but it does involve compiling the example and running it, which is a quick process as we show below. If you feel more comfortable running the {{Code\|HelloWorld}} example for your specific language, you can skip below and pick your language, but keep in mind that any problems could be with the C library installation and not necessarily with your language.		The easiest way to confirm correct installation will be to compile and run the {{Code\|HelloWorld}} C example, included in the examples download. This does not involve writing any C code, but it does involve compiling the example and running it, which is a quick process as we show below. If you feel more comfortable running the {{Code\|HelloWorld}} example for your specific language, you can skip below and pick your language, but keep in mind that any problems could be with the C library installation and not necessarily with your language.
Line 164:		Line 164:
	#*Try {{Code\|apt-cache search avahi}} in a terminal to find current packages		#*Try {{Code\|apt-cache search avahi}} in a terminal to find current packages
	#*Often, this is installed in a default system, you may already have it		#*Often, this is installed in a default system, you may already have it
	#Unpack and install the [{{SERVER}}/downloads/~~libraries~~/phidgetwebservice.tar.gz Phidgets WebService] source code tarball for Linux		#Unpack and install the [{{SERVER}}/downloads/phidget21/servers/linux/phidgetwebservice.tar.gz Phidgets WebService] source code tarball for Linux
	#*From the unpacked WebService source code directory, run:		#*From the unpacked WebService source code directory, run:
	#*:{{Code\|./configure}}		#*:{{Code\|./configure}}
Line 356:		Line 356:
	# An initialization file for the script		# An initialization file for the script

	First, the script. We will walk through Debian here, both because it is such a common distribution and because it is the distribution that our [{{SERVER}}products.php?product_id=1073 Single Board Computer] runs. But {{Code\|init}} is surprisingly diverse on Linux, including everything from a different boot order, to different initialization programs and structure, and even different runlevels.		First, the script. We will walk through Debian here, both because it is such a common distribution and because it is the distribution that our [{{SERVER}}/products.php?product_id=1073 Single Board Computer] runs. But {{Code\|init}} is surprisingly diverse on Linux, including everything from a different boot order, to different initialization programs and structure, and even different runlevels.

	On Debian (including Ubuntu), the initialization script covers:		On Debian (including Ubuntu), the initialization script covers:
Line 366:		Line 366:
	* What to do when the service is given instructions to '''start''', '''stop''', or '''reload'''.		* What to do when the service is given instructions to '''start''', '''stop''', or '''reload'''.

	The Debian script we use to start the webservice on the [{{SERVER}}products.php?product_id=1073 Single Board Computer]:		The Debian script we use to start the webservice on the [{{SERVER}}/products.php?product_id=1073 Single Board Computer]:

	<div class="source">		<div class="source">
Line 497:		Line 497:
	</div>		</div>

	For the Phidget libraries, the {{Code\|./configure}} tool works this way as well. You'd use this in the [[#Installing\|install the libraries section]] setup. For example, let's say you're building the libraries to develop code for the [{{SERVER}}products.php?product_id=1073 Single Board Computer] as a target. Your system is a standard Linux system (i686-pc-linux-gnu) and the target system for the SBC is {{Code\|arm-linux-gnueabi}}. For this target, you'll need the base of the GNU embedded Debian chain:		For the Phidget libraries, the {{Code\|./configure}} tool works this way as well. You'd use this in the [[#Installing\|install the libraries section]] setup. For example, let's say you're building the libraries to develop code for the [{{SERVER}}/products.php?product_id=1073 Single Board Computer] as a target. Your system is a standard Linux system (i686-pc-linux-gnu) and the target system for the SBC is {{Code\|arm-linux-gnueabi}}. For this target, you'll need the base of the GNU embedded Debian chain:

	<div class="source">		<div class="source">
Line 519:		Line 519:
	Our libraries are installed by building from source, and their main dependency is the {{Code\|libusb-1.0-0-dev}} library, so if you can get gcc on your machine (or set up a cross compiler for it) and you can also install the libusb-1.0 development headers, you can probably get Phidgets to work. Of course, we don't offer much support for these systems, so - depending on your system - expect to spend some raw time getting it up and going.		Our libraries are installed by building from source, and their main dependency is the {{Code\|libusb-1.0-0-dev}} library, so if you can get gcc on your machine (or set up a cross compiler for it) and you can also install the libusb-1.0 development headers, you can probably get Phidgets to work. Of course, we don't offer much support for these systems, so - depending on your system - expect to spend some raw time getting it up and going.

	If you're new to the embedded computer thing, keep in mind that for these super basic systems, once you've gotten a power supply, and storage, and put the kernel you want on it, and then spent a couple of days of time getting things working, and more time getting your drivers going, costs add up pretty quickly. If you want a compact system that works right out of the box (and which can use all of our analog sensors in addition to our USB Phidgets), check out our [{{SERVER}}products.php?product_id=1073 Single Board Computer]. Our SBC3:		If you're new to the embedded computer thing, keep in mind that for these super basic systems, once you've gotten a power supply, and storage, and put the kernel you want on it, and then spent a couple of days of time getting things working, and more time getting your drivers going, costs add up pretty quickly. If you want a compact system that works right out of the box (and which can use all of our analog sensors in addition to our USB Phidgets), check out our [{{SERVER}}/products.php?product_id=1073 Single Board Computer]. Our SBC3:
	* Has many more USB ports than super-stripped devices, and also has digital and analog ports		* Has many more USB ports than super-stripped devices, and also has digital and analog ports
	* Includes a power supply and can run on batteries easily		* Includes a power supply and can run on batteries easily

Mparadis: /* Quick Downloads */

2017-05-03T20:51:25Z

Quick Downloads

← Older revision		Revision as of 20:51, 3 May 2017
Line 10:		Line 10:

	If you are already a pro, and just want the downloads:		If you are already a pro, and just want the downloads:
	*[{{SERVER}}/downloads/libraries/libphidget.tar.gz Phidget Libraries for Linux]		*[{{SERVER}}/downloads/phidget21/libraries/linux/libphidget.tar.gz Phidget Libraries for Linux]
	*[{{SERVER}}/downloads/~~libraries~~/phidgetwebservice.tar.gz Phidget WebService for Linux]		*[{{SERVER}}/downloads/phidget21/servers/linux/phidgetwebservice.tar.gz Phidget WebService for Linux]
	*[[Software License]]		*[[Software License]]

			If you need old versions of the libraries, [{{SERVER}}/downloads/phidget21/libraries/linux/libphidget/ click here].

	==Getting Started with Linux==		==Getting Started with Linux==

Kat: added a getting started on Linux video.

2014-05-06T20:01:47Z

added a getting started on Linux video.

← Older revision		Revision as of 20:01, 6 May 2014
Line 15:		Line 15:

	==Getting Started with Linux==		==Getting Started with Linux==

			{{#ev:youtube\|6pXWhGzX4Fg}}

	===Installing===		===Installing===

Burley: /* Common Problems and Solutions */

2014-01-08T15:51:16Z

Common Problems and Solutions

← Older revision		Revision as of 15:51, 8 January 2014
Line 537:		Line 537:

	Linux only polls data from the analog inputs on Phidgets when you ask it to. So there is some delay between when you open the device and when it actually attaches when data from those inputs are accumulating...and overrunning the buffer. This is simply in the nature of how Linux polls USB - we recommend catching (but ignoring) this one-time initial error.		Linux only polls data from the analog inputs on Phidgets when you ask it to. So there is some delay between when you open the device and when it actually attaches when data from those inputs are accumulating...and overrunning the buffer. This is simply in the nature of how Linux polls USB - we recommend catching (but ignoring) this one-time initial error.

			{{ProblemSolution\|Raspberry Pi USB Current\|Your device doesn't seem to run as expected on a Raspberry Pi.}}

			The USB ports on the standard Raspberry Pi are only capable of supplying around 100mA reliably. Since USB specification dictates 500mA of current maximum, many USB devices require several hundred mA to run smoothly. Since the Pi cannot supply this much current it is common to see buggy performance or complete failure to run at all. The get around this you should use a USB hub connected to the Pi that has it's own external power supply. This will allow the devices connected to have as much power as they require.

Mparadis: /* Quick Downloads */

2013-12-09T21:53:40Z

Quick Downloads

← Older revision		Revision as of 21:53, 9 December 2013
Line 12:		Line 12:
	*[{{SERVER}}/downloads/libraries/libphidget.tar.gz Phidget Libraries for Linux]		*[{{SERVER}}/downloads/libraries/libphidget.tar.gz Phidget Libraries for Linux]
	*[{{SERVER}}/downloads/libraries/phidgetwebservice.tar.gz Phidget WebService for Linux]		*[{{SERVER}}/downloads/libraries/phidgetwebservice.tar.gz Phidget WebService for Linux]
	*[~~{{SERVER}}/Drivers_Info.html#linux~~ Software ~~license~~]		*[[Software License]]

	==Getting Started with Linux==		==Getting Started with Linux==

Mparadis: /* Linux on Non-Standard Systems */

2013-10-18T18:59:14Z

Linux on Non-Standard Systems

← Older revision		Revision as of 18:59, 18 October 2013
Line 511:		Line 511:
	===Linux on Non-Standard Systems===		===Linux on Non-Standard Systems===

	We occasionally get requests to use Phidgets on Linux systems other than a standard laptop or desktop. One example is the ~~new~~ Raspberry Pi system. Often these systems include USB ports, so the combination makes sense.		We occasionally get requests to use Phidgets on Linux systems other than a standard laptop or desktop. One example is the Raspberry Pi system. Often these systems include USB ports, so the combination makes sense.

	Our libraries are installed by building from source, and their main dependency is the {{Code\|libusb-1.0-0-dev}} library, so if you can get gcc on your machine (or set up a cross compiler for it) and you can also install the libusb-1.0 development headers, you can probably get Phidgets to work. Of course, we don't offer much support for these systems, so - depending on your system - expect to spend some raw time getting it up and going.		Our libraries are installed by building from source, and their main dependency is the {{Code\|libusb-1.0-0-dev}} library, so if you can get gcc on your machine (or set up a cross compiler for it) and you can also install the libusb-1.0 development headers, you can probably get Phidgets to work. Of course, we don't offer much support for these systems, so - depending on your system - expect to spend some raw time getting it up and going.

Mparadis at 19:51, 4 February 2013

2013-02-04T19:51:53Z

← Older revision		Revision as of 19:51, 4 February 2013
Line 362:		Line 362:
	* What to do when the service is given instructions to '''start''', '''stop''', or '''reload'''.		* What to do when the service is given instructions to '''start''', '''stop''', or '''reload'''.

	The Debian script we use to start the webservice on the [{{SERVER}}products.php?product_id=~~1072~~ Single Board Computer]:		The Debian script we use to start the webservice on the [{{SERVER}}products.php?product_id=1073 Single Board Computer]:

	<div class="source">		<div class="source">
Line 493:		Line 493:
	</div>		</div>

	For the Phidget libraries, the {{Code\|./configure}} tool works this way as well. You'd use this in the [[#Installing\|install the libraries section]] setup. For example, let's say you're building the libraries to develop code for the [{{SERVER}}products.php?product_id=~~1072~~ Single Board Computer] as a target. Your system is a standard Linux system (i686-pc-linux-gnu) and the target system for the SBC is {{Code\|arm-linux-gnueabi}}. For this target, you'll need the base of the GNU embedded Debian chain:		For the Phidget libraries, the {{Code\|./configure}} tool works this way as well. You'd use this in the [[#Installing\|install the libraries section]] setup. For example, let's say you're building the libraries to develop code for the [{{SERVER}}products.php?product_id=1073 Single Board Computer] as a target. Your system is a standard Linux system (i686-pc-linux-gnu) and the target system for the SBC is {{Code\|arm-linux-gnueabi}}. For this target, you'll need the base of the GNU embedded Debian chain:

	<div class="source">		<div class="source">
Line 515:		Line 515:
	Our libraries are installed by building from source, and their main dependency is the {{Code\|libusb-1.0-0-dev}} library, so if you can get gcc on your machine (or set up a cross compiler for it) and you can also install the libusb-1.0 development headers, you can probably get Phidgets to work. Of course, we don't offer much support for these systems, so - depending on your system - expect to spend some raw time getting it up and going.		Our libraries are installed by building from source, and their main dependency is the {{Code\|libusb-1.0-0-dev}} library, so if you can get gcc on your machine (or set up a cross compiler for it) and you can also install the libusb-1.0 development headers, you can probably get Phidgets to work. Of course, we don't offer much support for these systems, so - depending on your system - expect to spend some raw time getting it up and going.

	If you're new to the embedded computer thing, keep in mind that for these super basic systems, once you've gotten a power supply, and storage, and put the kernel you want on it, and then spent a couple of days of time getting things working, and more time getting your drivers going, costs add up pretty quickly. If you want a compact system that works right out of the box (and which can use all of our analog sensors in addition to our USB Phidgets), check out our [{{SERVER}}products.php?product_id=~~1072~~ Single Board Computer]. Our ~~SBC~~:		If you're new to the embedded computer thing, keep in mind that for these super basic systems, once you've gotten a power supply, and storage, and put the kernel you want on it, and then spent a couple of days of time getting things working, and more time getting your drivers going, costs add up pretty quickly. If you want a compact system that works right out of the box (and which can use all of our analog sensors in addition to our USB Phidgets), check out our [{{SERVER}}products.php?product_id=1073 Single Board Computer]. Our SBC3:
	* Has many more USB ports than super-stripped devices, and also has digital and analog ports		* Has many more USB ports than super-stripped devices, and also has digital and analog ports
	* Includes a power supply and can run on batteries easily		* Includes a power supply and can run on batteries easily

Mparadis at 19:51, 4 February 2013

2013-02-04T19:51:23Z

← Older revision		Revision as of 19:51, 4 February 2013
Line 352:		Line 352:
	# An initialization file for the script		# An initialization file for the script

	First, the script. We will walk through Debian here, both because it is such a common distribution and because it is the distribution that our [{{SERVER}}products.php?product_id=~~1072~~ Single Board Computer] runs. But {{Code\|init}} is surprisingly diverse on Linux, including everything from a different boot order, to different initialization programs and structure, and even different runlevels.		First, the script. We will walk through Debian here, both because it is such a common distribution and because it is the distribution that our [{{SERVER}}products.php?product_id=1073 Single Board Computer] runs. But {{Code\|init}} is surprisingly diverse on Linux, including everything from a different boot order, to different initialization programs and structure, and even different runlevels.

	On Debian (including Ubuntu), the initialization script covers:		On Debian (including Ubuntu), the initialization script covers:

Burley: /* Setting udev Rules */

2013-01-24T20:44:50Z

Setting udev Rules

← Older revision		Revision as of 20:44, 24 January 2013
Line 324:		Line 324:

	Strictly speaking, the files run in lexical order (i.e. the order they're listed when you use {{Code\|ls}}). A device can match many rules, and all will apply (if possible). If conflicting rules are found, the first rule found is followed.		Strictly speaking, the files run in lexical order (i.e. the order they're listed when you use {{Code\|ls}}). A device can match many rules, and all will apply (if possible). If conflicting rules are found, the first rule found is followed.

	~~To make sure the Phidget udev rules are found first, we can create a file {{Code\|10-persistent-usb.rules}} (all udev rule files need to end with {{Code\|.rules}}) and add one line to it:~~

	~~<div class="source">~~
	~~<syntaxhighlight lang=bash>~~
	~~SUBSYSTEM=="usb", ATTRS{idVendor}=="06c2", MODE="0666", OWNER="user"~~
	~~</syntaxhighlight>~~
	~~</div>~~

	Make sure to replace {{Code\|user}} with your user name. You probably recognize the '''06c2''' from the vendor discussion above. We have added the match on {{Code\|SUBSYSTEM}} to search first within usb (within a possibly big database). The {{Code\|MODE}} sets read and write privileges for everyone to the device, and {{Code\|OWNER}} sets the owner to be you.

	~~Save the {{Code\|10-persistent-usb.rules}} in {{Code\|/etc/udev/rules.d/}} and then change its permissions so it can be read by all:~~

	~~<div class="source">~~
	~~<syntaxhighlight lang=bash>~~
	~~sudo chmod a+r /etc/udev/rules.d/10-persistent-usb.rules~~
	~~</syntaxhighlight>~~
	~~</div>~~

	The udev rule is now set, and it just has to get read in. The reading of the rules is goverened by a daemon, {{Code\|udevd}}, which you can manage via the program {{Code\|udevadm}}. The {{Code\|udevadm}} man page is quite extensive for all sorts of uses of {{Code\|udevadm}} while you are testing this or other udev rules. To re-read and implement the rules without having to reset the daemon or reset the computer, you can use:

	~~<div class="source">~~
	~~<syntaxhighlight lang=bash>~~
	~~sudo udevadm control --reload-rules~~
	~~</syntaxhighlight>~~
	~~</div>~~

	~~Finally, if you performed all of these steps with the Phidget plugged in to your computer, you will need to unplug and plug the Phidget back in before trying to use usb access without root privileges.~~

	===Starting the WebService at Boot===		===Starting the WebService at Boot===