Language - AutoIt - Revision history

Burley: /* Step One: Initialize and Open */

2014-06-11T18:18:24Z

Step One: Initialize and Open

← Older revision		Revision as of 18:18, 11 June 2014
Line 69:		Line 69:
	</syntaxhighlight></div>		</syntaxhighlight></div>

	The object name for any type of Phidget is listed in the [{{SERVER}}/documentation/COM_API_Manual.pdf COM API manual], as well as the variety of open ~~call~~ available. Every type of Phidget also shares some functionality ~~from~~ the base Phidget class.		The object name for any type of Phidget is listed in the [{{SERVER}}/documentation/COM_API_Manual.pdf COM API manual], as well as the variety of open calls available. Every type of Phidget also shares some functionality with the base Phidget class.

	====Step Two: Wait for Attachment (plugging in) of the Phidget====		====Step Two: Wait for Attachment (plugging in) of the Phidget====

Burley at 18:31, 2 April 2013

2013-04-02T18:31:50Z

← Older revision		Revision as of 18:31, 2 April 2013
Line 8:		Line 8:
	AutoIt is capable of using the complete Phidget API, including events. However, AutoIt has no Phidget examples for devices at this time.		AutoIt is capable of using the complete Phidget API, including events. However, AutoIt has no Phidget examples for devices at this time.

	AutoIt can be developed with Windows XP/Vista/7/8.		AutoIt can be developed with Windows XP/Vista/7.

	You can compare AutoIt with our other [[Software Overview#Language Support\|supported languages]].		You can compare AutoIt with our other [[Software Overview#Language Support\|supported languages]].

Burley: /* Introduction */

2013-04-02T18:31:38Z

Introduction

← Older revision		Revision as of 18:31, 2 April 2013
Line 8:		Line 8:
	AutoIt is capable of using the complete Phidget API, including events. However, AutoIt has no Phidget examples for devices at this time.		AutoIt is capable of using the complete Phidget API, including events. However, AutoIt has no Phidget examples for devices at this time.

	AutoIt can be developed with Windows ~~2000/~~XP/Vista/7.		AutoIt can be developed with Windows XP/Vista/7/8.

	You can compare AutoIt with our other [[Software Overview#Language Support\|supported languages]].		You can compare AutoIt with our other [[Software Overview#Language Support\|supported languages]].

Burley: /* Introduction */

2012-08-08T17:38:36Z

Introduction

← Older revision		Revision as of 17:38, 8 August 2012
Line 4:		Line 4:
	==Introduction==		==Introduction==

	If this is your first time working with a Phidget, we suggest starting with the ''Getting Started'' page for your specific device. This can be found ~~on your product page on~~ [~~{{SERVER}} our main website~~]. That page will walk you through installing drivers and libraries for your operating system, and will then bring you back here to use AutoIt specifically.		If this is your first time working with a Phidget, we suggest starting with the ''Getting Started'' page for your specific device. This can be found in the [[:Category:UserGuide\|user guide]]. That page will walk you through installing drivers and libraries for your operating system, and will then bring you back here to use AutoIt specifically.

	AutoIt is capable of using the complete Phidget API, including events. However, AutoIt has no Phidget examples for devices at this time.		AutoIt is capable of using the complete Phidget API, including events. However, AutoIt has no Phidget examples for devices at this time.
Line 10:		Line 10:
	AutoIt can be developed with Windows 2000/XP/Vista/7.		AutoIt can be developed with Windows 2000/XP/Vista/7.

	You can compare AutoIt with our other [[Software Overview#Language Support\|supported languages]].		You can compare AutoIt with our other [[Software Overview#Language Support\|supported languages]].

	==Quick Downloads==		==Quick Downloads==

Cora at 18:53, 28 June 2012

2012-06-28T18:53:53Z

← Older revision		Revision as of 18:53, 28 June 2012
Line 4:		Line 4:
	==Introduction==		==Introduction==

	If this is your first time working with a Phidget, we suggest starting with the ''Getting Started'' page for your specific device. This can be found on your product page on [~~http://www.phidgets.com~~ our main website]. That page will walk you through installing drivers and libraries for your operating system, and will then bring you back here to use AutoIt specifically.		If this is your first time working with a Phidget, we suggest starting with the ''Getting Started'' page for your specific device. This can be found on your product page on [{{SERVER}} our main website]. That page will walk you through installing drivers and libraries for your operating system, and will then bring you back here to use AutoIt specifically.

	AutoIt is capable of using the complete Phidget API, including events. However, AutoIt has no Phidget examples for devices at this time.		AutoIt is capable of using the complete Phidget API, including events. However, AutoIt has no Phidget examples for devices at this time.
Line 15:		Line 15:

	{{QuickDownloads\|AutoIt\|		{{QuickDownloads\|AutoIt\|
	{{APIQuickDownloads\|~~http://www.phidgets.com~~/documentation/COM_API_Manual.pdf}}\|		{{APIQuickDownloads\|{{SERVER}}/documentation/COM_API_Manual.pdf}}\|
	* None Provided \|		* None Provided \|
	{{WindowsQuickDownloads}}}}		{{WindowsQuickDownloads}}}}
Line 48:		Line 48:
	There are additional references for writing AutoIt code:		There are additional references for writing AutoIt code:

	{{UsingAPhidgetInCodeGeneral\|both of which are available in AutoIt\|[~~http://www.phidgets.com~~/documentation/COM_API_Manual.pdf COM API]}}		{{UsingAPhidgetInCodeGeneral\|both of which are available in AutoIt\|[{{SERVER}}/documentation/COM_API_Manual.pdf COM API]}}

	===Code Snippets===		===Code Snippets===
Line 69:		Line 69:
	</syntaxhighlight></div>		</syntaxhighlight></div>

	The object name for any type of Phidget is listed in the [~~http://www.phidgets.com~~/documentation/COM_API_Manual.pdf COM API manual], as well as the variety of open call available. Every type of Phidget also shares some functionality from the base Phidget class.		The object name for any type of Phidget is listed in the [{{SERVER}}/documentation/COM_API_Manual.pdf COM API manual], as well as the variety of open call available. Every type of Phidget also shares some functionality from the base Phidget class.

	====Step Two: Wait for Attachment (plugging in) of the Phidget====		====Step Two: Wait for Attachment (plugging in) of the Phidget====

Cora at 16:33, 23 May 2012

2012-05-23T16:33:13Z

← Older revision		Revision as of 16:33, 23 May 2012
Line 126:		Line 126:
	Alternatively, you can usually use the integer value 0 for false and 1 for true.		Alternatively, you can usually use the integer value 0 for false and 1 for true.

	====Close and Delete====		====Step Four: Close and Delete====

	Multiple Phidgets of the same type can easily be run inside the same program.		Multiple Phidgets of the same type can easily be run inside the same program.

Cora: /* Coding For Your Phidget */

2012-05-14T18:53:41Z

Coding For Your Phidget

← Older revision		Revision as of 18:53, 14 May 2012
Line 113:		Line 113:
	Some events such as Attach and Detach belong to the base Phidget object and thus are common to all types of Phidgets.		Some events such as Attach and Detach belong to the base Phidget object and thus are common to all types of Phidgets.
	Please refer to the API manual for a full list of events and their usage.		Please refer to the API manual for a full list of events and their usage.

	~~===Working directly with the Phidget===~~

	Some values can be directly read and set on the Phidget, and inside polling loops used as an alternative to event driven programming.		Some values can be directly read and set on the Phidget, and inside polling loops used as an alternative to event driven programming.
Line 128:		Line 126:
	Alternatively, you can usually use the integer value 0 for false and 1 for true.		Alternatively, you can usually use the integer value 0 for false and 1 for true.

	===~~Working with multiple Phidgets~~===		====Close and Delete====

	Multiple Phidgets of the same type can easily be run inside the same program.		Multiple Phidgets of the same type can easily be run inside the same program.
Line 135:		Line 133:
	If the application needs to distinguish between the devices, open can be called with the serial number of a specific Phidget.		If the application needs to distinguish between the devices, open can be called with the serial number of a specific Phidget.

	~~===Other Phidgets===~~		{{MoreHowTos}}

	~~The design given in this document can also be followed for almost all Phidgets. For example, if you~~
	~~were using a PhidgetRFID instead of an PhidgetInterfacekit, you would declare a PhidgetRFID object~~
	~~instead of a PhidgetInterfaceKit. The methods and events available would change but they can be~~
	~~accessed in a similar manner.~~

	==Common Problems and Solutions/Workarounds==		==Common Problems and Solutions/Workarounds==

	None at this time.		None at this time.

Cora: /* Coding For Your Phidget */

2012-05-14T18:25:14Z

Coding For Your Phidget

← Older revision		Revision as of 18:25, 14 May 2012
Line 71:		Line 71:
	The object name for any type of Phidget is listed in the [http://www.phidgets.com/documentation/COM_API_Manual.pdf COM API manual], as well as the variety of open call available. Every type of Phidget also shares some functionality from the base Phidget class.		The object name for any type of Phidget is listed in the [http://www.phidgets.com/documentation/COM_API_Manual.pdf COM API manual], as well as the variety of open call available. Every type of Phidget also shares some functionality from the base Phidget class.

	===~~Attaching~~ the Phidget===		====Step Two: Wait for Attachment (plugging in) of the Phidget====

	An attached Phidget is one that is attached in hardware - i.e. plugged it. We can account for this connection by waiting or by catching an AttachEvent. WaitForAttachment will block indefinitely until a connection is made to the Phidget, or an optional timeout is exceeded:		An attached Phidget is one that is attached in hardware - i.e. plugged it. We can account for this connection by waiting or by catching an AttachEvent. WaitForAttachment will block indefinitely until a connection is made to the Phidget, or an optional timeout is exceeded:
Line 87:		Line 87:
	One important thing to remember is that when working with Phidgets, a local connection will reserve the device until closed. This means only one program can access the Phidget locally. Many computers can access one Phidget over the [[Phidget WebService]].		One important thing to remember is that when working with Phidgets, a local connection will reserve the device until closed. This means only one program can access the Phidget locally. Many computers can access one Phidget over the [[Phidget WebService]].

	===~~Event Driven Programming~~===		====Step Three: Do Things with the Phidget====

	We recommend the use of event driven programming when working with Phidgets.		We recommend the use of event driven programming when working with Phidgets.

Cora: /* Coding For Your Phidget */

2012-05-14T18:24:03Z

Coding For Your Phidget

← Older revision		Revision as of 18:24, 14 May 2012
Line 52:		Line 52:
	===Code Snippets===		===Code Snippets===

	~~Before~~ you can ~~use~~ the Phidget, you must create the object from the Phidget21COM library at initialization. This can be accomplished through a call to ObjCreate. For example, we can declare and ~~create~~ a PhidgetInterfaceKit with:		Specific calls in AutoIt will differ in syntax from those on the [[General Phidget Programming]] page, but the concepts stay the same.

			It may help to have the [[General Phidget Programming]] page and this section open at the same time, because they parallel each other and you can refer to the AutoIt syntax. However, many additional concepts are covered on the General Phidget Programming page on a high level, such as using multiple Phidgets, handling errors, and different styles of programming.

			====Step One: Initialize and Open====

			To open the Phidget, you must create the object from the Phidget21COM library at initialization. This can be accomplished through a call to ObjCreate. Then, we try to open the Phidget. The open() call is simple most of the time, but it can also handle many different types of open (i.e. remote open using the [[Phidget WebService]], opening [[General Phidget Programming#Using Multiple Phidgets\|multiple Phidgets]], etc). For the details of open (and other functions on this page), refer to the [[General Phidget Programming\|Opening the Phidget]] section on the General Phidget Programming page.

			For example, we can declare, create, and open a PhidgetInterfaceKit with:

	<div class="source"><syntaxhighlight lang=autoit>		<div class="source"><syntaxhighlight lang=autoit>

	$oPhid1 = ObjCreate("Phidget21COM.PhidgetInterfacekit")		$oPhid1 = ObjCreate("Phidget21COM.PhidgetInterfacekit")
			$oPhid1.Open()

	</syntaxhighlight></div>		</syntaxhighlight></div>

	The object name for any type of Phidget is listed in the API manual.		The object name for any type of Phidget is listed in the [http://www.phidgets.com/documentation/COM_API_Manual.pdf COM API manual], as well as the variety of open call available. Every type of Phidget also shares some functionality from the base Phidget class.
	Every type of Phidget also shares some functionality from the base Phidget class.

	===~~Connecting to~~ the Phidget===		===Attaching the Phidget===

	~~The program can try to connect to the~~ Phidget ~~through a call to open~~.		An attached Phidget is one that is attached in hardware - i.e. plugged it. We can account for this connection by waiting or by catching an AttachEvent. WaitForAttachment will block indefinitely until a connection is made to the Phidget, or an optional timeout is exceeded:
	~~Open will continuously try to connect to a Phidget, based on the parameters given, even trying to reconnect if~~ it ~~gets disconnected~~.
	~~This means that simply calling open does not guarantee you can use the Phidget immediately.~~
	We can account for a connection by ~~using event driven programming and tracking the AttachEvents and DetachEvents,~~ or by ~~calling WaitForAttachment~~.
	WaitForAttachment will block indefinitely until a connection is made to the Phidget, or an optional timeout is exceeded.

	<div class="source"><syntaxhighlight lang=autoit>		<div class="source"><syntaxhighlight lang=autoit>

	~~$oPhid1.Open()~~
	$oPhid1.WaitForAttachment(3000)		$oPhid1.WaitForAttachment(3000)
	If NOT $oPhid1.IsAttached Then		If NOT $oPhid1.IsAttached Then
Line 82:		Line 85:
	</syntaxhighlight></div>		</syntaxhighlight></div>

	~~The different parameters and open calls can be used to open the first Phidget of a type it can find, open based on a serial number, or even open across the network.~~		One important thing to remember is that when working with Phidgets, a local connection will reserve the device until closed. This means only one program can access the Phidget locally. Many computers can access one Phidget over the [[Phidget WebService]].
	~~The API manual lists all of the available modes that open provides.~~
	One important thing to remember is that when working with Phidgets, a local connection will reserve the device until closed.
	This ~~prevents any other instances from retrieving data from~~ the Phidget~~, including other programs~~.
	~~The~~ one ~~connection per device limit does not apply when exclusively using~~ the Phidget ~~Webservice~~.

	===Event Driven Programming===		===Event Driven Programming===

Cora: /* Getting Started with AutoIt */

2012-05-09T22:22:47Z

Getting Started with AutoIt

← Older revision		Revision as of 22:22, 9 May 2012
Line 23:		Line 23:
	Applications using Phidgets can be developed in AutoIt v3 through the COM API and this tutorial assumes its use.		Applications using Phidgets can be developed in AutoIt v3 through the COM API and this tutorial assumes its use.

	The Windows ~~drivers~~ above in the [[#Quick Downloads\|Quick Downloads]] section will install the Phidget framework and will register the necessary .dlls for you.		The Windows installers above in the [[#Quick Downloads\|Quick Downloads]] section will install the Phidget framework and will register the necessary .dlls for you.

	In lieu of example code, to begin in AutoIt you can create a new script file and open it with your preferred editor. Then, create a simple user interface to work with and then place an input control for the purpose of capturing some simple output:		In lieu of example code, to begin in AutoIt you can create a new script file and open it with your preferred editor. Then, create a simple user interface to work with and then place an input control for the purpose of capturing some simple output:
Line 43:		Line 43:

	</syntaxhighlight></div>		</syntaxhighlight></div>


	==Coding For Your Phidget==		==Coding For Your Phidget==