General Troubleshooting - Revision history

Mparadis at 17:08, 20 January 2022

2022-01-20T17:08:01Z

← Older revision		Revision as of 17:08, 20 January 2022
Line 23:		Line 23:
	----		----
	{{Collapse		{{Collapse
	\|The Phidget shows up but the row is coloured red		\|The Phidget shows up but the text or row is coloured red
	\|		\|
	[[File:~~Controlpanel_windows_firmwareupgrade~~.png\|link=\|300px\|right]]		[[File:Controlpanel_mac_firmwareupgrade.png\|link=\|300px\|right]]
	~~This~~ means that a firmware update is available for your device. Double-clicking on the red bar will download and install the update, which should take less than a minute. If the firmware update fails, you may need to download the latest version of the Phidget drivers and try again. Once the device is updated and working, you can proceed to [[#Step 2: Test with our Sample Code\|step 2]].
			On MacOS, the red text means that a firmware update is available for your device. In older versions of the Windows control panel, the row may be red for the same reason (newer versions show a blue arrow instead). Double-clicking on the red bar or text will download and install the update, which should take less than a minute. If the firmware update fails, you may need to download the latest version of the Phidget drivers and try again. Once the device is updated and working, you can proceed to [[#Step 2: Test with our Sample Code\|step 2]].


	}}		}}
	----		----

Mparadis at 20:30, 4 April 2019

2019-04-04T20:30:24Z

Show changes

Jdecoux at 20:53, 28 February 2019

2019-02-28T20:53:58Z

← Older revision		Revision as of 20:53, 28 February 2019
Line 35:		Line 35:
	'''If the problem is in your code:'''		'''If the problem is in your code:'''
	:*Syntax help can be found in the {{Phidget22API}} and code snippets for [[Programming Resources\|your programming language]]		:*Syntax help can be found in the {{Phidget22API}} and code snippets for [[Programming Resources\|your programming language]]
	:*High-level concept help (logging, catching errors, using the API) is ~~on the~~ [[~~Software Overview~~]] ~~page~~		:*High-level concept help (logging, catching errors, using the API) is contained within [[Phidget Programming Basics]]
	:*Compiler help (linking libraries, running code) can be found on the [[Programming Resources\| page for your language]]		:*Compiler help (linking libraries, running code) can be found on the [[Programming Resources\| page for your language]]
	:*Ensure you wait enough time for the Phidget to respond to your requests, such as when switching between ratiometric and non-ratiometric sensing, or to get and set device data.		:*Ensure you wait enough time for the Phidget to respond to your requests, such as when switching between ratiometric and non-ratiometric sensing, or to get and set device data.

Jdecoux at 20:52, 28 February 2019

2019-02-28T20:52:14Z

Mparadis: /* Languages */

2019-01-18T17:45:04Z

Languages

← Older revision		Revision as of 17:45, 18 January 2019
Line 369:		Line 369:

	Likely Fix: Please ensure that you do not use more patches(of the same Phidget object) than you have of the actual Phidget device.		Likely Fix: Please ensure that you do not use more patches(of the same Phidget object) than you have of the actual Phidget device.

	==Contact Us==		==Contact Us==

Mparadis: /* Issue: Curl doesn't install smoothly */

2019-01-17T17:57:14Z

Issue: Curl doesn't install smoothly

← Older revision		Revision as of 17:57, 17 January 2019
Line 266:		Line 266:
	There is an issue with the embedded version of PHP5.3, try forcing it to install the specific version that you need. This can be done with the following command:		There is an issue with the embedded version of PHP5.3, try forcing it to install the specific version that you need. This can be done with the following command:
	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	apt-get install php5-common~~<nowiki>~~=~~</nowiki>~~5.3.3-7+squeeze14		apt-get install php5-common=5.3.3-7+squeeze14
	</syntaxhighlight>		</syntaxhighlight>

Jdecoux at 21:44, 31 October 2018

2018-10-31T21:44:06Z

← Older revision		Revision as of 21:44, 31 October 2018
Line 35:		Line 35:
	'''If the problem is in your code:'''		'''If the problem is in your code:'''
	:*Syntax help can be found in the {{Phidget22API}} and code snippets for [[Software Overview#Language Support\|your programming language]]		:*Syntax help can be found in the {{Phidget22API}} and code snippets for [[Software Overview#Language Support\|your programming language]]
	:*High-level concept help (logging, catching errors, using the API) is on the [[~~General Phidget Programming~~]] page		:*High-level concept help (logging, catching errors, using the API) is on the [[Software Overview]] page
	:*Compiler help (linking libraries, running code) can be found on the [[Software Overview#Language Support \| page for your language]]		:*Compiler help (linking libraries, running code) can be found on the [[Software Overview#Language Support \| page for your language]]
	:*Ensure you wait enough time for the Phidget to respond to your requests, such as when switching between ratiometric and non-ratiometric sensing, or to get and set device data.		:*Ensure you wait enough time for the Phidget to respond to your requests, such as when switching between ratiometric and non-ratiometric sensing, or to get and set device data.

Mparadis: /* Windows */

2018-05-14T21:07:18Z

Windows

← Older revision		Revision as of 21:07, 14 May 2018
Line 209:		Line 209:
	==Common Problems and Solutions==		==Common Problems and Solutions==
	===Windows===		===Windows===

			====Issue: Windows computer's servers are visible, but not their attached Phidgets====
			If you can see the server for a Windows computer, but not the attached Phidgets, make sure the Network Server isn't being blocked by Windows Firewall. You can change this setting by going to the start menu and searching for "Windows Firewall". In the Windows Defender Firewall, choose "Allow an app or feature through" and add the Network Server to the list (you can find it at C:\Program Files\Phidgets\Phidget22\NetworkServer.exe).

	====Issue: Software projects are not working after a Phidget22 reinstall====		====Issue: Software projects are not working after a Phidget22 reinstall====
	Solution: You need to reset your references and library paths. When you reinstall the Phidgets drivers all of the old paths can get broken. Make sure that you are including the correect header files and that you have referenced the correct libraries and that should fix the problem.		Solution: You need to reset your references and library paths. When you reinstall the Phidgets drivers all of the old paths can get broken. Make sure that you are including the correect header files and that you have referenced the correct libraries and that should fix the problem.

Lmpacent at 18:11, 4 July 2017

2017-07-04T18:11:45Z

@@ Line 341: / Line 341: @@
 On a full Linux operating system, you would use the logs written to by cron to find the error output and debug it.  On the SBC, however, cron does not write logs (otherwise, these logs would eat up the SBC memory very quickly even for routine jobs).  For short-term debugging, you can write output from your program to a file, and read that file afterwards to figure out what your program is doing.
-===Languages - C/C++===
+===Languages===
-====Issue: I am using a non US-English version of Windows, and the Visual C/C++ examples run into a linker error====
+====C/C++====
 The example projects, by default finds the phidget22.h and phidget22.lib in ${SystemDrive}\Program Files\Phidgets\Phidget22. If you are using a non US-English version of Windows, the Phidget libraries may be installed into a different location. To resolve, you will have to modify the paths to these two files. For instructions, please see your environment/compiler section.
 ==Contact Us==

Lmpacent at 17:05, 4 July 2017

2017-07-04T17:05:23Z

← Older revision		Revision as of 17:05, 4 July 2017
Line 340:		Line 340:

	On a full Linux operating system, you would use the logs written to by cron to find the error output and debug it. On the SBC, however, cron does not write logs (otherwise, these logs would eat up the SBC memory very quickly even for routine jobs). For short-term debugging, you can write output from your program to a file, and read that file afterwards to figure out what your program is doing.		On a full Linux operating system, you would use the logs written to by cron to find the error output and debug it. On the SBC, however, cron does not write logs (otherwise, these logs would eat up the SBC memory very quickly even for routine jobs). For short-term debugging, you can write output from your program to a file, and read that file afterwards to figure out what your program is doing.

			===Languages - C/C++===
			====Issue: I am using a non US-English version of Windows, and the Visual C/C++ examples run into a linker error====
			The example projects, by default finds the phidget22.h and phidget22.lib in ${SystemDrive}\Program Files\Phidgets\Phidget22. If you are using a non US-English version of Windows, the Phidget libraries may be installed into a different location. To resolve, you will have to modify the paths to these two files. For instructions, please see your environment/compiler section.

	==Contact Us==		==Contact Us==

← Older revision		Revision as of 20:52, 28 February 2019
Line 28:		Line 28:

	==Code Troubleshooting==		==Code Troubleshooting==
	To determine whether the problem is in your code, '''you should run the provided examples''' for [[~~Software Overview#Language Support~~\|your programming language]].		To determine whether the problem is in your code, '''you should run the provided examples''' for [[Programming Resources\|your programming language]].

	* If the examples run, the problem is within your code.		* If the examples run, the problem is within your code.
Line 34:		Line 34:

	'''If the problem is in your code:'''		'''If the problem is in your code:'''
	:*Syntax help can be found in the {{Phidget22API}} and code snippets for [[~~Software Overview#Language Support~~\|your programming language]]		:*Syntax help can be found in the {{Phidget22API}} and code snippets for [[Programming Resources\|your programming language]]
	:*High-level concept help (logging, catching errors, using the API) is on the [[Software Overview]] page		:*High-level concept help (logging, catching errors, using the API) is on the [[Software Overview]] page
	:*Compiler help (linking libraries, running code) can be found on the [[~~Software Overview#Language Support~~ \| page for your language]]		:*Compiler help (linking libraries, running code) can be found on the [[Programming Resources\| page for your language]]
	:*Ensure you wait enough time for the Phidget to respond to your requests, such as when switching between ratiometric and non-ratiometric sensing, or to get and set device data.		:*Ensure you wait enough time for the Phidget to respond to your requests, such as when switching between ratiometric and non-ratiometric sensing, or to get and set device data.

	To download and run the examples, visit the page about [[~~Software Overview#Language Support~~ \| your programming language]]. The API section on the product page for your device [{{SERVER}} on our main website] will tell you the software object -- and thus example file name -- for your Phidget. Make sure to use either that object-specific example or the '"HelloWorld" example if one is available.		To download and run the examples, visit the page about [[Programming Resources\| your programming language]]. The API section on the product page for your device [{{SERVER}} on our main website] will tell you the software object -- and thus example file name -- for your Phidget. Make sure to use either that object-specific example or the '"HelloWorld" example if one is available.

	When debugging, it helps to extract from your code what is known as a '''Minimum Reproducible Unit''' (MRU). This is the minimum lines of code that can reproduce the issue. We can help with this. An MRU will allow you to find what part of your use of Phidgets in code is causing the problem. Extracting an MRU is a powerful process which can not only isolate the problem, but also allow you to examine and organize your code. Also, it helps us debug your problem faster if you can show exactly what the problem is in the part of your code that deals with Phidgets.		When debugging, it helps to extract from your code what is known as a '''Minimum Reproducible Unit''' (MRU). This is the minimum lines of code that can reproduce the issue. We can help with this. An MRU will allow you to find what part of your use of Phidgets in code is causing the problem. Extracting an MRU is a powerful process which can not only isolate the problem, but also allow you to examine and organize your code. Also, it helps us debug your problem faster if you can show exactly what the problem is in the part of your code that deals with Phidgets.
Line 194:		Line 194:

	'''If the problem is within the Network Server:'''		'''If the problem is within the Network Server:'''
	:*Make sure the Phidget library and Network Server versions are the '''same''' on both computers. Different Network Server versions do not work together. Find the Network Server download on the [[~~Software Overview#~~Operating System Support \| page for your operating system]]		:*Make sure the Phidget library and Network Server versions are the '''same''' on both computers. Different Network Server versions do not work together. Find the Network Server download on the [[Operating System Support\| page for your operating system]]
	:*Wait some time (a few seconds, to start) before trying to do things with the Phidget upon first connecting remotely, sometimes delay occurs over a network		:*Wait some time (a few seconds, to start) before trying to do things with the Phidget upon first connecting remotely, sometimes delay occurs over a network
	:*Check the network setup on both sides. Typos can occur in the IP address, port number, server name, and password.		:*Check the network setup on both sides. Typos can occur in the IP address, port number, server name, and password.