General Troubleshooting - Revision history

Mparadis at 19:53, 4 February 2013

2013-02-04T19:53:42Z

← Older revision		Revision as of 19:53, 4 February 2013
Line 83:		Line 83:
	Communication problems come from either (a) power issues, or (b) connection issues. Once everything is plugged in and powered properly, there is not a whole lot that can go wrong with cables.		Communication problems come from either (a) power issues, or (b) connection issues. Once everything is plugged in and powered properly, there is not a whole lot that can go wrong with cables.

	The one exception to communications problems being only from power or connections is if you're using a wireless internet connection to the [{{SERVER}}/products.php?product_id=~~1072~~ Single Board Computer]. Help for setting up and troubleshooting that Wifi connection can be found on the [[OS - Phidget SBC\|SBC operating system page]].		The one exception to communications problems being only from power or connections is if you're using a wireless internet connection to the [{{SERVER}}/products.php?product_id=1073 Single Board Computer]. Help for setting up and troubleshooting that Wifi connection can be found on the [[OS - Phidget SBC\|SBC operating system page]].

	==Webservice Troubleshooting==		==Webservice Troubleshooting==
Line 107:		Line 107:

	===Version Mismatch===		===Version Mismatch===
	If you are experiencing a "Version Mismatch" error this is due to either end of the connection having an out of date version of the WebService. To fix this make sure that both ends are fully updated and try again. Note that on the SBC this means you will need to go to the System->Packages tab and upgrade all of the systems packages. For more information on upgrading the SBC refer to the [[~~1072~~ User Guide#Recovery / Upgrade System\|SBC's User Guide]].		If you are experiencing a "Version Mismatch" error this is due to either end of the connection having an out of date version of the WebService. To fix this make sure that both ends are fully updated and try again. Note that on the SBC this means you will need to go to the System->Packages tab and upgrade all of the systems packages. For more information on upgrading the SBC refer to the [[1073 User Guide#Recovery / Upgrade System\|SBC's User Guide]].

	==Device Troubleshooting==		==Device Troubleshooting==

Burley: /* Version Mismatch */

2013-01-22T17:16:26Z

Version Mismatch

← Older revision		Revision as of 17:16, 22 January 2013
Line 107:		Line 107:

	===Version Mismatch===		===Version Mismatch===
	If you are experiencing a "Version Mismatch" error this is due to either end of the connection having an out of date version of the WebService. To fix this make sure that both ends are fully updated and try again. Note that on the SBC this means you will need to go to the System->Packages tab and upgrade all of the systems packages. For more information on upgrading the SBC refer to the [[~~SBC's~~ User Guide\|#Recovery / Upgrade System]].		If you are experiencing a "Version Mismatch" error this is due to either end of the connection having an out of date version of the WebService. To fix this make sure that both ends are fully updated and try again. Note that on the SBC this means you will need to go to the System->Packages tab and upgrade all of the systems packages. For more information on upgrading the SBC refer to the [[1072 User Guide#Recovery / Upgrade System\|SBC's User Guide]].

	==Device Troubleshooting==		==Device Troubleshooting==

Burley: /* Version Mismatch */

2013-01-22T17:15:41Z

Version Mismatch

← Older revision		Revision as of 17:15, 22 January 2013
Line 107:		Line 107:

	===Version Mismatch===		===Version Mismatch===
	If you are experiencing a "Version Mismatch" error this is due to either end of the connection having an out of date version of the WebService. To fix this make sure that both ends are fully updated and try again. Note that on the SBC this means you will need to go to the System->Packages tab and upgrade all of the systems packages. For more information on upgrading the SBC refer to the [[SBC's User Guide\|~~1072 User Guide~~#Recovery / Upgrade System]].		If you are experiencing a "Version Mismatch" error this is due to either end of the connection having an out of date version of the WebService. To fix this make sure that both ends are fully updated and try again. Note that on the SBC this means you will need to go to the System->Packages tab and upgrade all of the systems packages. For more information on upgrading the SBC refer to the [[SBC's User Guide\|#Recovery / Upgrade System]].

	==Device Troubleshooting==		==Device Troubleshooting==

Burley: /* Version Mismatch */

2013-01-22T17:15:30Z

Version Mismatch

← Older revision		Revision as of 17:15, 22 January 2013
Line 107:		Line 107:

	===Version Mismatch===		===Version Mismatch===
	If you are experiencing a "Version Mismatch" error this is due to either end of the connection having an out of date version of the WebService. To fix this make sure that both ends are fully updated and try again. Note that on the SBC this means you will need to go to the System->Packages tab and upgrade all of the systems packages. For more information on upgrading the SBC refer to the [[SBC's User Guide\|1072 User Guide#Recovery/Upgrade System]].		If you are experiencing a "Version Mismatch" error this is due to either end of the connection having an out of date version of the WebService. To fix this make sure that both ends are fully updated and try again. Note that on the SBC this means you will need to go to the System->Packages tab and upgrade all of the systems packages. For more information on upgrading the SBC refer to the [[SBC's User Guide\|1072 User Guide#Recovery / Upgrade System]].

	==Device Troubleshooting==		==Device Troubleshooting==

Burley: /* Version Mismatch */

2013-01-22T17:15:13Z

Version Mismatch

← Older revision		Revision as of 17:15, 22 January 2013
Line 107:		Line 107:

	===Version Mismatch===		===Version Mismatch===
	If you are experiencing a "Version Mismatch" error this is due to either end of the connection having an out of date version of the WebService. To fix this make sure that both ends are fully updated and try again. Note that on the SBC this means you will need to go to the System->Packages tab and upgrade all of the systems packages. For more information on upgrading the SBC refer to the [[SBC's User Guide\|1072 User Guide#~~Recover~~/Upgrade System]].		If you are experiencing a "Version Mismatch" error this is due to either end of the connection having an out of date version of the WebService. To fix this make sure that both ends are fully updated and try again. Note that on the SBC this means you will need to go to the System->Packages tab and upgrade all of the systems packages. For more information on upgrading the SBC refer to the [[SBC's User Guide\|1072 User Guide#Recovery/Upgrade System]].

	==Device Troubleshooting==		==Device Troubleshooting==

Burley: /* Webservice Troubleshooting */

2013-01-22T17:15:06Z

Webservice Troubleshooting

← Older revision		Revision as of 17:15, 22 January 2013
Line 105:		Line 105:

	Finally, if you suspect multicast DNS may be the problem, use the IP address and port form of the '''<code>open()</code>''' function to directly connect to the computer controlling the Phidget. On [[OS - Linux\|Linux]], the use of mDNS can be compiled out of the webservice, and the webservice can be tested without it.		Finally, if you suspect multicast DNS may be the problem, use the IP address and port form of the '''<code>open()</code>''' function to directly connect to the computer controlling the Phidget. On [[OS - Linux\|Linux]], the use of mDNS can be compiled out of the webservice, and the webservice can be tested without it.

			===Version Mismatch===
			If you are experiencing a "Version Mismatch" error this is due to either end of the connection having an out of date version of the WebService. To fix this make sure that both ends are fully updated and try again. Note that on the SBC this means you will need to go to the System->Packages tab and upgrade all of the systems packages. For more information on upgrading the SBC refer to the [[SBC's User Guide\|1072 User Guide#Recover/Upgrade System]].

	==Device Troubleshooting==		==Device Troubleshooting==

Mparadis: /* Communications Troubleshooting */

2013-01-11T20:51:52Z

Communications Troubleshooting

← Older revision		Revision as of 20:51, 11 January 2013
Line 77:		Line 77:
	:*Use powered USB hubs or direct connections to a computer.		:*Use powered USB hubs or direct connections to a computer.
	:*Try unplugging everything on the hub except the Phidget.		:*Try unplugging everything on the hub except the Phidget.
			:*Try plugging the Phidget directly into the computer instead of using a hub. If this solves the problem, either the hub is at fault, or the added length of cable from the hub to the computer may have caused instability.
	:*Make sure any cables between Phidgets are correctly connected. Helpful pictures can be found on the ''Getting Started'' page for your device [{{SERVER}} on our main website]		:*Make sure any cables between Phidgets are correctly connected. Helpful pictures can be found on the ''Getting Started'' page for your device [{{SERVER}} on our main website]
	:*If your Phidget needs external power, such as the motors and relays, the proper way to provide it can be found on the product page for your device [{{SERVER}} on our main website]		:*If your Phidget needs external power, such as the motors and relays, the proper way to provide it can be found on the product page for your device [{{SERVER}} on our main website]

Mparadis: /* Operating System Troubleshooting */

2012-09-27T20:49:02Z

Operating System Troubleshooting

← Older revision		Revision as of 20:49, 27 September 2012
Line 60:		Line 60:

	'''If the problem is with your operating system:'''		'''If the problem is with your operating system:'''
	:*Make sure '''no other programs''' are accessing the Phidget USB port at the same time as your code. This '''includes''' the Phidget Control Panel on [[OS ~~- Windows~~ \| ~~Windows]] and the~~ Phidget Preference Pane on ~~[[OS - OS X \|~~ OS X]].		:*Make sure '''no other programs''' are accessing the Phidget USB port at the same time as your code. This '''includes''' the [[Phidget Control Panel]] on Windows and the [[Phidget Control Panel#OS X\|Phidget Preference Pane]] on OS X.
	:*Make sure your [[Software Overview#Operating System Support \| operating system version is supported]]; this includes virtual machine versions (check the page for both the host and emulated machines)		:*Make sure your [[Software Overview#Operating System Support \| operating system version is supported]]; this includes virtual machine versions (check the page for both the host and emulated machines)
	:*Ensure the Phidget libraries and drivers [[Software Overview#Operating System Support \| for your operating system]] are the '''most recent''' version		:*Ensure the Phidget libraries and drivers [[Software Overview#Operating System Support \| for your operating system]] are the '''most recent''' version

Burley at 14:32, 24 August 2012

2012-08-24T14:32:12Z

← Older revision		Revision as of 14:32, 24 August 2012
Line 9:		Line 9:
	Once you have found the <span style="background:#EDEDED;padding:5px;border:1px dashed;">part of your system</span> with the problem, click on the <font size="+1">'''<span style="color:#006600">green link</span>'''</font> within the box to learn more about how to troubleshoot that portion.		Once you have found the <span style="background:#EDEDED;padding:5px;border:1px dashed;">part of your system</span> with the problem, click on the <font size="+1">'''<span style="color:#006600">green link</span>'''</font> within the box to learn more about how to troubleshoot that portion.

	[[Image:troubleshooting.png]]		[[Image:troubleshooting.png\|link=]]

	The content that you need to solve your problem probably exists somewhere within our documentation. We cover everything from compiling the Phidget Libraries for embedded systems, to using our example on Visual Studio 6, to how Solid State Relays actually work. The purpose of this page, then, is to distill the problem you have enough that you can get to the documentation you need.		The content that you need to solve your problem probably exists somewhere within our documentation. We cover everything from compiling the Phidget Libraries for embedded systems, to using our example on Visual Studio 6, to how Solid State Relays actually work. The purpose of this page, then, is to distill the problem you have enough that you can get to the documentation you need.

Burley: /* Diagnosing Hardware Problems */

2012-08-10T19:26:54Z

Diagnosing Hardware Problems

← Older revision		Revision as of 19:26, 10 August 2012
Line 114:		Line 114:
	:*Make sure all the pieces are hooked up correctly. Helpful photos can be found on the ''Getting Started'' page for your device in its [[:Category:UserGuide\|user guide]].		:*Make sure all the pieces are hooked up correctly. Helpful photos can be found on the ''Getting Started'' page for your device in its [[:Category:UserGuide\|user guide]].
	:*If you're trying to do something especially involved, become well-versed in your hardware. We provide lots of information on our [[:Category:Primer\| primer pages]].		:*If you're trying to do something especially involved, become well-versed in your hardware. We provide lots of information on our [[:Category:Primer\| primer pages]].

			It may be tempting to assume that a device "not working" indicates a problem with the hardware. But this troubleshooting page itself shows that even something as simple as a device "not working" could be due to a problem at several different points. The best place to start if you haven't worked through our documentation yet would be the ''Getting Started'' guide for your device, found in its [[:Category:UserGuide\|user guide]].

	===Diagnosing Hardware Problems===		===Diagnosing Hardware Problems===
Line 119:		Line 121:

	====Heat====		====Heat====
	One of the surest ways to discover a problem is as simple as touching the board. When current flows through electronics it will generate heat, this is a fundamental fact with all electronics. The more current that you are pushing, the more heat that will be generated. As a result of this the instance where you have the most current possible flowing (a short circuit)		One of the surest ways to discover a problem is as simple as touching the board. When current flows through electronics it will generate heat, this is a fundamental fact with all electronics. The more current that you are pushing, the more heat that will be generated. As a result of this the instance where you have the most current possible flowing (a short circuit) will also generate the most heat. So much heat that it will likely be painful to the touch so be careful when poking and prodding the various parts of the board. Keep in mind that some heat build up is to be expected, but if you can find a part of the board that is unusually hot then there is a strong possibility that there is a short circuit somewhere in that section and the board has been damaged. You should [[Contact Us]] if this is the case.

	~~It may be tempting~~ to ~~assume~~ that ~~a device "not working" indicates a problem with~~ the ~~hardware~~. ~~But this troubleshooting page itself shows that even something as simple as a device "not working" could~~ be ~~due~~ to ~~a problem at several different points~~. ~~The best place~~ to ~~start if~~ you ~~haven't worked through~~ our ~~documentation yet would be the ''Getting Started'' guide for your device~~, ~~found in its~~ [[~~:Category:UserGuide\|user guide~~]].		====Checking Voltages====
			If you have a multimeter at your disposal another good way of checking your board is to check that all of the ICs on the board are getting the power they should. If you look at the labelling on the top of the ICs you should be able to get the part number of the chip. If it is too small or hard to read you can always look at the high resolution product images on our website to get a better look. Failing that, [[Contact Us]] and we can give you the part number. Once you have it search the internet for a data sheet for the part. The data sheet will have a pin diagram from which you can determine which pins are V<sub>cc</sub> and Gnd. Take your multimeter and measure the voltage between those pins. Does the chip appear to be getting the voltage it should be? If not then it is possible there is a short somewhere in the power line.

	~~Another good idea~~ is to ~~check out~~ our guide for [[Addressing Electromagnetic Interference with Phidgets\|addressing EMI issues]].		====EMI====
			One of the most difficult hardware related problems to diagnose and debug is electromagnetic interference or EMI. In fact, it is such a complex topic that we have a guide devoted entirely to it. If you think you may be having EMI difficulties or if you don't know what kind of difficulties you might be having (an apparent lack of other explanation is a good sign your problems might be EMI related) you should read our guide for [[Addressing Electromagnetic Interference with Phidgets\|addressing EMI issues]].

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