1015 User Guide - Revision history

Mparadis at 14:25, 9 May 2018

2018-05-09T14:25:10Z

← Older revision		Revision as of 14:25, 9 May 2018
Line 1:		Line 1:
			__NOINDEX__
	[[Category:UserGuide]]		[[Category:UserGuide]]
	{{UserguideTOC\|1015.jpg\|1015}}		{{UserguideTOC\|1015.jpg\|1015}}

Mparadis: /* Product History */

2016-04-19T20:28:50Z

Product History

← Older revision		Revision as of 20:28, 19 April 2016
Line 116:		Line 116:
	==Product History==		==Product History==
	{{UGhist}}		{{UGhist}}
	{{UGrow\|August 2005\|0\|100 (500)\|Product Release}}		{{UGrow\|August 2005 \|0\|100 (500)\|Product Release}}
	{{UGrow\|~~August 2005~~\|0\|101\|Encore II}}		{{UGrow\|October 2006\|0\|101\|Encore II}}

Mparadis: /* Product History */

2016-04-19T20:28:16Z

Product History

← Older revision		Revision as of 20:28, 19 April 2016
Line 116:		Line 116:
	==Product History==		==Product History==
	{{UGhist}}		{{UGhist}}
	{{UGrow\|August 2005\|0\|100\|Product Release}}		{{UGrow\|August 2005\|0\|100 (500)\|Product Release}}
			{{UGrow\|August 2005\|0\|101\|Encore II}}

Burley at 15:08, 10 August 2012

2012-08-10T15:08:29Z

← Older revision		Revision as of 15:08, 10 August 2012
Line 1:		Line 1:
	[[Category:UserGuide]]		[[Category:UserGuide]]
			{{UserguideTOC\|1015.jpg\|1015}}
	==Getting Started==		==Getting Started==

Mparadis: /* API */

2012-08-08T18:14:06Z

API

← Older revision		Revision as of 18:14, 8 August 2012
Line 86:		Line 86:
	===Functions===		===Functions===
	{{UGapi\|int InputCount() [get] : Constant <nowiki>=</nowiki> 2		{{UGapi\|int InputCount() [get] : Constant <nowiki>=</nowiki> 2
	\|Returns the number of digital inputs supported. Please refer to the Device Inputs section for details on the abstractions used on the 1015.		\|Returns the number of digital inputs supported. Please refer to the [[#Device Inputs\|Device Inputs]] section for details on the abstractions used on the 1015.
	}}		}}

Line 98:		Line 98:

	{{UGapi\|int SensorValue(int SensorIndex) [get]		{{UGapi\|int SensorValue(int SensorIndex) [get]
	\|Returns the sensed value of a particular Analog Input. Please refer to the Device Inputs section for details on the abstractions used on the 1015.		\|Returns the sensed value of a particular Analog Input. Please refer to the [[#Device Inputs\|Device Inputs]] section for details on the abstractions used on the 1015.
	}}		}}

Mparadis at 15:39, 26 July 2012

2012-07-26T15:39:13Z

← Older revision		Revision as of 15:39, 26 July 2012
Line 1:		Line 1:
			[[Category:UserGuide]]

	==Getting Started==		==Getting Started==

Mparadis: /* Product History */

2012-07-26T14:19:58Z

Product History

← Older revision		Revision as of 14:19, 26 July 2012
Line 114:		Line 114:
	==Product History==		==Product History==
	{{UGhist}}		{{UGhist}}
	{{UGrow\| \| \| \| }}		{{UGrow\|August 2005\|0\|100\|Product Release}}

Mparadis: /* Technical Details */

2012-07-19T21:41:39Z

Technical Details

← Older revision		Revision as of 21:41, 19 July 2012
Line 52:		Line 52:

	The PhidgetLinearTouch appears to the Phidget software libraries as an InterfaceKit. Sliding a finger along the touch sensor varies the Analog Input 0 value from 0 to 1000 in approximately 125 discrete steps. When the finger is removed, the final measured value is retained. Two Digital Inputs are also utilized to convey additional information: Digital Input 0 appears True when contact is made with the electrodes on the Phidget, and Digital Input 1 appears True when a finger or contacting object comes in close proximity to the electrodes. The two Digital Inputs are intended to be used as a quality measure, allowing the developer to trust the Analog Input value only when both Digital Inputs are true.		The PhidgetLinearTouch appears to the Phidget software libraries as an InterfaceKit. Sliding a finger along the touch sensor varies the Analog Input 0 value from 0 to 1000 in approximately 125 discrete steps. When the finger is removed, the final measured value is retained. Two Digital Inputs are also utilized to convey additional information: Digital Input 0 appears True when contact is made with the electrodes on the Phidget, and Digital Input 1 appears True when a finger or contacting object comes in close proximity to the electrodes. The two Digital Inputs are intended to be used as a quality measure, allowing the developer to trust the Analog Input value only when both Digital Inputs are true.


	{\| style="border:1px solid darkgray;" cellpadding="7px;"		{\| style="border:1px solid darkgray;" cellpadding="7px;"
Line 70:		Line 71:
	\|-		\|-
	\|}		\|}


	For many projects it is required that the highest and lowest available values be more readily accessible than the full range. The PhidgetLinearTouch board has been designed so that the end-zones of the touch area have a greater contact area, allowing for effective maximum/minimum value control. If it is desired to use the touch slider as an array of buttons, or a combination of an array of buttons and a smaller slide-touch area, one must only interpret specific sub-ranges of sensor values differently in software depending upon the intended use. If sub-ranges of values are to be used as buttons, it is recommended that a small range of sensor values be left between the subranges where a null-response is observed.		For many projects it is required that the highest and lowest available values be more readily accessible than the full range. The PhidgetLinearTouch board has been designed so that the end-zones of the touch area have a greater contact area, allowing for effective maximum/minimum value control. If it is desired to use the touch slider as an array of buttons, or a combination of an array of buttons and a smaller slide-touch area, one must only interpret specific sub-ranges of sensor values differently in software depending upon the intended use. If sub-ranges of values are to be used as buttons, it is recommended that a small range of sensor values be left between the subranges where a null-response is observed.

Mparadis: Created page with "==Getting Started== ===Checking the Contents=== {{UGbox| '''You should have received:''' * A PhidgetLinearTouch board. * A custom USB cable |||}} ===Connecting the Pieces===..."

2012-07-19T21:40:52Z

Created page with "==Getting Started== ===Checking the Contents=== {{UGbox| '''You should have received:''' * A PhidgetLinearTouch board. * A custom USB cable |||}} ===Connecting the Pieces===..."

New page

==Getting Started==

===Checking the Contents===
{{UGbox|
'''You should have received:'''
* A PhidgetLinearTouch board.
* A custom USB cable
|||}}

===Connecting the Pieces===
{{UGbox|
# Connect the PhidgetLinearTouch to your computer using the custom USB cable included.
|[[File:1015_0_Connecting_The_Hardware.jpg|400px|link=]]
||}}

===Testing Using Windows 2000 / XP / Vista / 7===

{{UGwin}}

===Running Phidgets Sample Program===

{{UGwin2|'''InterfaceKit-full'''}}

{{UGbox|
Double Click on the [[File:Ph.jpg|link=]] icon to activate the Phidget Control Panel and make sure that the PhidgetLinearTouch is properly attached to your PC.
|[[File:1015_0_Control_Panel_Screen.jpg|400px|link=]]
|
# Double Click on Phidget Touch Slider in the Phidget Control Panel to bring up InterfaceKit-full and check that the box labelled Attached contains the word True.
# As you bring your finger closer to the board and touch the board, tick marks will appear in the Digital In boxes. The left one shows “touch” and the right one shows “proximity”.
# Move your finger along the backside of the PhidgetLinearTouch and watch the numbers in the Analog box change from 0 to 1000. The numbers are only significant when both Digital In boxes are “tick marked”.
# Adjusting the input sensitivity with the sensitivity slider changes the number of discrete steps that will fire the on-sensor-change event.
|[[File:1015_0_InterfaceKit_Screen.jpg|400px|link=]]
}}

===Testing Using Mac OS X===

{{UGmac|PhidgetLinearTouch|InterfaceKit-full}}

===Using Linux===

{{UGlinux}}

===Using Windows Mobile / CE 5.0 / CE 6.0===

{{UGce}}

==Technical Details==

The PhidgetLinearTouch is actually a capacitive-charge sensor, detecting changes in the capacitance between the on-board electrodes and the object making contact. The side of the circuit board opposite the connector and components is the side intended for contact. The internal sensor used for charge-detection is a Quantum Research Group QT401 Sensor.

===Device Inputs===

The PhidgetLinearTouch appears to the Phidget software libraries as an InterfaceKit. Sliding a finger along the touch sensor varies the Analog Input 0 value from 0 to 1000 in approximately 125 discrete steps. When the finger is removed, the final measured value is retained. Two Digital Inputs are also utilized to convey additional information: Digital Input 0 appears True when contact is made with the electrodes on the Phidget, and Digital Input 1 appears True when a finger or contacting object comes in close proximity to the electrodes. The two Digital Inputs are intended to be used as a quality measure, allowing the developer to trust the Analog Input value only when both Digital Inputs are true.

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #f0f0f0" align=center
! Input || Range || Description
|-
|style="background: #F8F8F8" align=left| Analog Input 0
|style="background: #F8F8F8" align=left| 0 - 1000
|style="background: #F8F8F8" align=left| Analog value representing touch position
|-
|style="background: #F8F8F8" align=left| Digital Input 0
|style="background: #F8F8F8" align=left| True/False
|style="background: #F8F8F8" align=left| True indicates physical contact with electrode
|-
|style="background: #F8F8F8" align=left| Digital Input 1
|style="background: #F8F8F8" align=left| True/False
|style="background: #F8F8F8" align=left| True indicates proximity to electrodes
|-
|}

For many projects it is required that the highest and lowest available values be more readily accessible than the full range. The PhidgetLinearTouch board has been designed so that the end-zones of the touch area have a greater contact area, allowing for effective maximum/minimum value control. If it is desired to use the touch slider as an array of buttons, or a combination of an array of buttons and a smaller slide-touch area, one must only interpret specific sub-ranges of sensor values differently in software depending upon the intended use. If sub-ranges of values are to be used as buttons, it is recommended that a small range of sensor values be left between the subranges where a null-response is observed.

===Dielectric Separation===

The PhidgetLinearTouch has been left without components on the contact side so that it may be mounted behind a sheet of glass or plastic. The recommended thickness of separation material is 1/8 inch. Silicon adhesive is recommended when attaching the Phidget to the material; standing the PhidgetLinearTouch off or creating space between the separation material and the Phidget can cause false-triggering to occur. It should be noted that materials thicker than 1/8” may work, but will require a larger surface area of contact to ensure proper triggering (i.e.: two fingers instead of one).

==API==
{{UGapih}}

===Functions===
{{UGapi|int InputCount() [get] : Constant <nowiki>=</nowiki> 2
|Returns the number of digital inputs supported. Please refer to the Device Inputs section for details on the abstractions used on the 1015.
}}

{{UGapi|bool InputState(int InputIndex) [get]
|Returns the state of a particular digital input.
}}

{{UGapi|int SensorCount() [get] : Constant <nowiki>=</nowiki> 1
|Returns the number of sensors (Analog Inputs) supported by this PhidgetInterfaceKit. Intrepreted together with the digital inputs, this represents the positiion of the user’s finger on the slider.
}}

{{UGapi|int SensorValue(int SensorIndex) [get]
|Returns the sensed value of a particular Analog Input. Please refer to the Device Inputs section for details on the abstractions used on the 1015.
}}

{{UGapi|double SensorChangeTrigger (int SensorIndex) [get,set]
|Returns the change trigger for an analog input. This is the ammount that an inputs must change between successive SensorChangeEvents. This is based on the 0-1000 range provided by getSensorValue. This value is by default set to 10.
}}

===Events===
{{UGapi|OnInputChange(int InputIndex, bool State) [event]
|An event that is issued when the state of a digital input changes.
}}

{{UGapi|OnSensorChange(int SensorIndex, int SensorValue), [event]
|An event that is issued when the returned value from an Analog Input varies by more than the SensorChangeTrigger property.
}}

==Product History==
{{UGhist}}
{{UGrow| | | | }}