Upgrading Code from Phidget21 to Phidget22 - Revision history

Mparadis at 20:07, 28 July 2021

2021-07-28T20:07:48Z

← Older revision		Revision as of 20:07, 28 July 2021
Line 1:		Line 1:
			[[Category:Troubleshooting]]

	In order to use your older Phidget applications with new [[What_is_VINT?\|VINT]] devices, or new versions of the library, you'll have to update to Phidget22. Many structural changes have been made to the library to accommodate the increasing complexity and variety of Phidgets devices. This guide will highlight the most important changes, so you can update your older applications. Please note that for relatively simple programs and applications, you may just want to rewrite them entirely, using the old program as a guideline. For very complex applications, it may be quicker to follow this guide.		In order to use your older Phidget applications with new [[What_is_VINT?\|VINT]] devices, or new versions of the library, you'll have to update to Phidget22. Many structural changes have been made to the library to accommodate the increasing complexity and variety of Phidgets devices. This guide will highlight the most important changes, so you can update your older applications. Please note that for relatively simple programs and applications, you may just want to rewrite them entirely, using the old program as a guideline. For very complex applications, it may be quicker to follow this guide.

Jdecoux at 20:47, 28 February 2019

2019-02-28T20:47:07Z

← Older revision		Revision as of 20:47, 28 February 2019
Line 4:		Line 4:
	== Step 1: Install Phidget22 and Update References ==		== Step 1: Install Phidget22 and Update References ==

	The first step in updating your program will be to [[~~Software Overview~~\|install phidget22]] and update your program's include list or references list, replacing all instances of Phidget21 with Phidget22. Visit the [[~~Software_Overview#Language_Support~~\|language]] page for your programming language for more information on including libraries. Once you've removed Phidget21 and added Phidget22, your program will have a number of syntax errors. This will provide an indicator of where in your program you need to focus as you continue to the next few steps.		The first step in updating your program will be to [[Operating_System_Support\|install phidget22]] and update your program's include list or references list, replacing all instances of Phidget21 with Phidget22. Visit the [[Programming Resources\|language]] page for your programming language for more information on including libraries. Once you've removed Phidget21 and added Phidget22, your program will have a number of syntax errors. This will provide an indicator of where in your program you need to focus as you continue to the next few steps.

	== Step 2: Split up Objects ==		== Step 2: Split up Objects ==

Mparadis at 21:57, 23 January 2018

2018-01-23T21:57:19Z

← Older revision		Revision as of 21:57, 23 January 2018
Line 372:		Line 372:

	Keep trying to compile your program as you make these changes. Incorrectly named objects or properties and mismatched types will both be caught by the compiler. Once your program compiles with no errors, test it thoroughly just in case one of the library changes has affected your application in subtle ways.		Keep trying to compile your program as you make these changes. Incorrectly named objects or properties and mismatched types will both be caught by the compiler. Once your program compiles with no errors, test it thoroughly just in case one of the library changes has affected your application in subtle ways.

			== Other Differences ==

			=== Persistence of Outputs and Settings ===
			In Phidget21, you could create an object, open it, set properties, and close it. When re-opening, the properties that you set would still be there. For example, you could open an ''InterfaceKit'' object, use setOutputState to set one of the outputs to TRUE, and then close the InterfaceKit object. As long as the Phidget wasn't disconnected and didn't lose power, you could count on that output to remain TRUE, even after being reopened.

			In Phidget22, outputs and settings are not persistent; when a channel is opened or closed, it is completely reset. In an equivalent example from the one above, if you open a ''DigitalOutput'' object and use setState to set it to TRUE, it will revert back to FALSE when it is closed. The reason this change was made is because we wanted Phidget channels to be in a predictable state when first opened. It's not generally a good idea to count on the state of a Phidget that you don't have explicitly opened, because unexpected detaches can happen at any time, and these should be handled by your code. It's a good idea to keep your handles open as long as you need an output set.

	== Support ==		== Support ==

	If you come across problems with Phidget22, you can {{ContactUs\|contact us}} for help. Alternatively, you can create a topic on our forums in the appropriate programming language section. Be sure to post the part of your code that's causing the problem and describe what happens when you try to run it.		If you come across problems with Phidget22, you can {{ContactUs\|contact us}} for help. Alternatively, you can create a topic on our forums in the appropriate programming language section. Be sure to post the part of your code that's causing the problem and describe what happens when you try to run it.

Jdecoux at 19:59, 26 June 2017

2017-06-26T19:59:05Z

← Older revision		Revision as of 19:59, 26 June 2017
Line 166:		Line 166:
	\|style="background: #f0f0ff; border-top:solid 3px darkgray;"\| 1015		\|style="background: #f0f0ff; border-top:solid 3px darkgray;"\| 1015
	\|style="background: #fff0f0; border-top:solid 3px darkgray;"\|InterfaceKit		\|style="background: #fff0f0; border-top:solid 3px darkgray;"\|InterfaceKit
	\|style="background: #f0fff0; border-top:solid 3px darkgray;"\|~~HumanInput~~		\|style="background: #f0fff0; border-top:solid 3px darkgray;"\|CapacitiveTouch
	\|-		\|-
	\|style="background: #f0f0ff; border-top:solid 3px darkgray;"\| 1016		\|style="background: #f0f0ff; border-top:solid 3px darkgray;"\| 1016
	\|style="background: #fff0f0; border-top:solid 3px darkgray;"\|InterfaceKit		\|style="background: #fff0f0; border-top:solid 3px darkgray;"\|InterfaceKit
	\|style="background: #f0fff0; border-top:solid 3px darkgray;"\|~~HumanInput~~		\|style="background: #f0fff0; border-top:solid 3px darkgray;"\|CapacitiveTouch
	\|-		\|-
	\|style="background: #f0f0ff; border-top:solid 3px darkgray;"\| 1017		\|style="background: #f0f0ff; border-top:solid 3px darkgray;"\| 1017

Mparadis at 20:02, 17 April 2017

2017-04-17T20:02:37Z

← Older revision		Revision as of 20:02, 17 April 2017
Line 1:		Line 1:

	In order to use your older Phidget applications with new [[VINT]] devices, or new versions of the library, you'll have to update to Phidget22. Many structural changes have been made to the library to accommodate the increasing complexity and variety of Phidgets devices. This guide will highlight the most important changes, so you can update your older applications. Please note that for relatively simple programs and applications, you may just want to rewrite them entirely, using the old program as a guideline. For very complex applications, it may be quicker to follow this guide.		In order to use your older Phidget applications with new [[What_is_VINT?\|VINT]] devices, or new versions of the library, you'll have to update to Phidget22. Many structural changes have been made to the library to accommodate the increasing complexity and variety of Phidgets devices. This guide will highlight the most important changes, so you can update your older applications. Please note that for relatively simple programs and applications, you may just want to rewrite them entirely, using the old program as a guideline. For very complex applications, it may be quicker to follow this guide.

	== Step 1: Install Phidget22 and Update References ==		== Step 1: Install Phidget22 and Update References ==

Mparadis: /* SensorValue */

2017-04-17T19:55:08Z

SensorValue

← Older revision		Revision as of 19:55, 17 April 2017
Line 367:		Line 367:
	The SensorValue abstraction used in Phidget21 (a number ranging from 0 to 1000 that represents a 0 to 5 volt value) doesn't exist in Phidget22. Instead, VoltageInput channels will report the actual voltage read from 0 to 5 volts, so you may need to change some formulae in your code.		The SensorValue abstraction used in Phidget21 (a number ranging from 0 to 1000 that represents a 0 to 5 volt value) doesn't exist in Phidget22. Instead, VoltageInput channels will report the actual voltage read from 0 to 5 volts, so you may need to change some formulae in your code.

	However, there is a completely different property called '''SensorValue''' in Phidget22, which is automatically converted into the appropriate value for the sensor if you set the '''SensorType''' property. For example, if you're using an 1127 Phidget Light sensor, you can set the '''SensorType''' to ''PN_1127''. This will cause '''SensorValue''' to be automatically converted into lux according to the formula for the 1127. You can use the '''SensorUnit''' property to confirm which unit '''SensorValue''' is currently using. Have a look at the '''SensorType''' enumeration in the VoltageInput and VoltageRatioInput sections of the {{Phidget22API}} for a complete list of supported sensors.		However, there is a completely different property called '''SensorValue''' in Phidget22, which is automatically converted into the appropriate value for the sensor if you set the '''SensorType''' property. For example, if you're using an 1127 Phidget Light sensor, you can set the '''SensorType''' to '''PN_1127'''. This will cause '''SensorValue''' to be automatically converted into lux according to the formula for the 1127. You can use the '''SensorUnit''' property to confirm which unit '''SensorValue''' is currently using. Have a look at the '''SensorType''' enumeration in the VoltageInput and VoltageRatioInput sections of the {{Phidget22API}} for a complete list of supported sensors.

	== Step 4: Clean Up Remaining Syntax Errors and Test ==		== Step 4: Clean Up Remaining Syntax Errors and Test ==

Mparadis: /* SensorValue */

2017-04-17T19:53:30Z

SensorValue

← Older revision		Revision as of 19:53, 17 April 2017
Line 365:		Line 365:
	=== SensorValue ===		=== SensorValue ===

	The SensorValue abstraction (a number ranging from 0 to 1000 that represents a 0 to 5 volt value) doesn't exist in Phidget22. Instead, VoltageInput channels will report the actual voltage read from 0 to 5 volts, so you may need to change some formulae in your code.		The SensorValue abstraction used in Phidget21 (a number ranging from 0 to 1000 that represents a 0 to 5 volt value) doesn't exist in Phidget22. Instead, VoltageInput channels will report the actual voltage read from 0 to 5 volts, so you may need to change some formulae in your code.

	However, there is a completely different property called '''SensorValue''' in Phidget22, which is automatically converted into the appropriate value for the sensor if you set the '''SensorType''' property. For example, if you're using an 1127 Phidget Light sensor, you can set the '''SensorType''' to ''PN_1127''. This will cause '''SensorValue''' to be automatically converted into lux according to the formula for the 1127. You can use the '''SensorUnit''' property to confirm which unit '''SensorValue''' is currently using. Have a look at the '''SensorType''' enumeration in the VoltageInput and VoltageRatioInput sections of the {{Phidget22API}} for a complete list of supported sensors.		However, there is a completely different property called '''SensorValue''' in Phidget22, which is automatically converted into the appropriate value for the sensor if you set the '''SensorType''' property. For example, if you're using an 1127 Phidget Light sensor, you can set the '''SensorType''' to ''PN_1127''. This will cause '''SensorValue''' to be automatically converted into lux according to the formula for the 1127. You can use the '''SensorUnit''' property to confirm which unit '''SensorValue''' is currently using. Have a look at the '''SensorType''' enumeration in the VoltageInput and VoltageRatioInput sections of the {{Phidget22API}} for a complete list of supported sensors.

Mparadis: /* Step 3: Update Property and Method Names */

2017-04-17T19:53:06Z

Step 3: Update Property and Method Names

← Older revision		Revision as of 19:53, 17 April 2017
Line 362:		Line 362:

	If you're using a simpler development environment, you'll want to have the {{Phidget22API}} for your device open as you make your replacements.		If you're using a simpler development environment, you'll want to have the {{Phidget22API}} for your device open as you make your replacements.

			=== SensorValue ===

			The SensorValue abstraction (a number ranging from 0 to 1000 that represents a 0 to 5 volt value) doesn't exist in Phidget22. Instead, VoltageInput channels will report the actual voltage read from 0 to 5 volts, so you may need to change some formulae in your code.

			However, there is a completely different property called '''SensorValue''' in Phidget22, which is automatically converted into the appropriate value for the sensor if you set the '''SensorType''' property. For example, if you're using an 1127 Phidget Light sensor, you can set the '''SensorType''' to ''PN_1127''. This will cause '''SensorValue''' to be automatically converted into lux according to the formula for the 1127. You can use the '''SensorUnit''' property to confirm which unit '''SensorValue''' is currently using. Have a look at the '''SensorType''' enumeration in the VoltageInput and VoltageRatioInput sections of the {{Phidget22API}} for a complete list of supported sensors.

	== Step 4: Clean Up Remaining Syntax Errors and Test ==		== Step 4: Clean Up Remaining Syntax Errors and Test ==

Mparadis: /* Step 2: Split up Objects */

2017-04-12T21:30:28Z

Step 2: Split up Objects

← Older revision		Revision as of 21:30, 12 April 2017
Line 14:		Line 14:


	{\|style="width:~~600px~~"		{\|style="width:800px"
	\|- valign="top"		\|- valign="top"
	\|'''Phidget21:'''		\|'''Phidget21:'''
Line 71:		Line 71:


	{\|style="width:~~600px~~"		{\|style="width:800px"
	\|- valign="top"		\|- valign="top"
	\|'''Phidget21:'''		\|'''Phidget21:'''

Mparadis: /* Step 2: Split up Objects */

2017-04-12T21:29:36Z

Step 2: Split up Objects

← Older revision		Revision as of 21:29, 12 April 2017
Line 10:		Line 10:
	One of the major changes between Phidget21 and Phidget22 is the way device objects are organized. In Phidget21, each device would have one object which contained properties and methods to interact with each of that device's features. In Phidget22, objects have been broken up so that each object belongs to a single feature, input, or output. Some objects that were already self-contained may have been renamed.		One of the major changes between Phidget21 and Phidget22 is the way device objects are organized. In Phidget21, each device would have one object which contained properties and methods to interact with each of that device's features. In Phidget22, objects have been broken up so that each object belongs to a single feature, input, or output. Some objects that were already self-contained may have been renamed.

	For example, in Phidget21 if you were using a 1018 Phidget InterfaceKit, you'd open the InterfaceKit object, which contained methods and properties to read digital inputs, read ~~voltage~~ inputs, and control the digital outputs. In Phidget22, there are separate objects for digital inputs, digital outputs, ~~voltage~~ inputs (0-5V input), and voltage ratio inputs (0-5V input in ratiometric mode). In C#, the difference may look something like this:		For example, in Phidget21 if you were using a 1018 Phidget InterfaceKit, you'd open the InterfaceKit object, which contained methods and properties to read digital inputs, read analog inputs, and control the digital outputs. In Phidget22, there are separate objects for digital inputs, digital outputs, analog inputs (0-5V input), and voltage ratio inputs (0-5V input in ratiometric mode). In C#, the difference may look something like this:

← Older revision		Revision as of 19:59, 26 June 2017
Line 166:		Line 166:
	\|style="background: #f0f0ff; border-top:solid 3px darkgray;"\| 1015		\|style="background: #f0f0ff; border-top:solid 3px darkgray;"\| 1015
	\|style="background: #fff0f0; border-top:solid 3px darkgray;"\|InterfaceKit		\|style="background: #fff0f0; border-top:solid 3px darkgray;"\|InterfaceKit
	\|style="background: #f0fff0; border-top:solid 3px darkgray;"\|~~HumanInput~~		\|style="background: #f0fff0; border-top:solid 3px darkgray;"\|CapacitiveTouch
	\|-		\|-
	\|style="background: #f0f0ff; border-top:solid 3px darkgray;"\| 1016		\|style="background: #f0f0ff; border-top:solid 3px darkgray;"\| 1016
	\|style="background: #fff0f0; border-top:solid 3px darkgray;"\|InterfaceKit		\|style="background: #fff0f0; border-top:solid 3px darkgray;"\|InterfaceKit
	\|style="background: #f0fff0; border-top:solid 3px darkgray;"\|~~HumanInput~~		\|style="background: #f0fff0; border-top:solid 3px darkgray;"\|CapacitiveTouch
	\|-		\|-
	\|style="background: #f0f0ff; border-top:solid 3px darkgray;"\| 1017		\|style="background: #f0f0ff; border-top:solid 3px darkgray;"\| 1017