Handling Errors and Logging - Revision history

Mparadis at 20:28, 3 August 2023

2023-08-03T20:28:11Z

← Older revision		Revision as of 20:28, 3 August 2023
Line 198:		Line 198:
	When <code>NULL</code> is passed to <code>enable()</code> in the above examples, the logging system will output to <code>STDERR</code>.		When <code>NULL</code> is passed to <code>enable()</code> in the above examples, the logging system will output to <code>STDERR</code>.

	For a more comprehensive look at the logging system in Phidget22, you can check out the [[Logging ~~Details~~]] page.		For a more comprehensive look at the logging system in Phidget22, you can check out the [[Phidget Logging]] page.

	==Common Errors==		==Common Errors==

Jdecoux: /* Common Errors */

2023-07-14T18:51:15Z

Common Errors

← Older revision		Revision as of 18:51, 14 July 2023
Line 201:		Line 201:

	==Common Errors==		==Common Errors==
	For more information on how to handle common errors, such as sensor data being Out of Range or Invalid, see our page on [[~~Handling_Out_Of_Range_Errors~~]].		For more information on how to handle common errors, such as sensor data being Out of Range or Invalid, see our page on [[Handling Out Of Range Errors]].

	== Other Problems ==		== Other Problems ==

Jdecoux: /* Other Problems */

2023-07-14T18:50:38Z

Mparadis at 21:14, 19 April 2022

2022-04-19T21:14:18Z

← Older revision		Revision as of 21:14, 19 April 2022
Line 58:		Line 58:
	<syntaxhighlight lang=javascript>		<syntaxhighlight lang=javascript>
	try {		try {
	ch.~~getState()~~		var tmp = ch.state
	}		}
	catch(err) {		catch(err) {
Line 64:		Line 64:
	}		}
	</syntaxhighlight>		</syntaxhighlight>
	The second type is used for asynchronous functions, which return "promises", handled by the ".catch~~" method~~:		The second type is used for asynchronous functions, which return "promises", handled using the 'await' keyword in addition to a try/catch:
	<syntaxhighlight lang=javascript>		<syntaxhighlight lang=javascript>
	ch.open().catch~~(function~~ (err) {
	console.log('Error:' + err.message);		async function main() {
	})		...
			try {
			await ch.open()
			}
			catch(err) {
			console.log('Error:' + err.message);
			})
			}
	</syntaxhighlight>		</syntaxhighlight>
	When in doubt, check the {{Phidget22API}} to see whether the function you're checking returns a promise or not.		When in doubt, check the {{Phidget22API}} to see whether the function you're checking returns a promise or not.
Line 149:		Line 156:
	\|-\|		\|-\|
	JavaScript=<syntaxhighlight lang=javascript>		JavaScript=<syntaxhighlight lang=javascript>
	// Declare the event ~~handler~~		// Declare your object. Replace "DigitalInput" with the object for your Phidget
	function ~~onErrorHandler~~(code, description) {		const ch = new phidget22.DigitalInput()

			// Assign the handler that will be called when the event occurs
			ch.onError = function(code, description) {
	console.log('Code: ' + code)		console.log('Code: ' + code)
	console.log('Description: ' + description)		console.log('Description: ' + description)
	}		}
	~~...~~
	~~// Declare your object. Replace "DigitalInput" with the object for your Phidget~~
	~~var ch = new phidget22.DigitalInput()~~
	~~...~~
	~~// Assign the handler that will be called when the event occurs~~
	~~ch.onError = onErrorHandler~~
	</syntaxhighlight>		</syntaxhighlight>
	</tabber>		</tabber>

Mparadis: /* Logging */

2019-04-11T19:56:17Z

Logging

← Older revision		Revision as of 19:56, 11 April 2019
Line 187:		Line 187:
	PhidgetLog_enable(PHIDGET_LOG_INFO, NULL);		PhidgetLog_enable(PHIDGET_LOG_INFO, NULL);
	</syntaxhighlight>		</syntaxhighlight>
			\|-\|
			JavaScript=
			Client-side logging is not enabled in JavaScript. For library errors, you can check the console, and for communication errors, you can enable logging on the server side. For information on how to enable and access network server logs, see the [[Network Server Troubleshooting]] page.
	</tabber>		</tabber>

Mparadis at 19:17, 11 April 2019

2019-04-11T19:17:26Z

← Older revision		Revision as of 19:17, 11 April 2019
Line 159:		Line 159:
	...		...
	// Assign the handler that will be called when the event occurs		// Assign the handler that will be called when the event occurs
	ch.onError(onErrorHandler)		ch.onError = onErrorHandler
	</syntaxhighlight>		</syntaxhighlight>
	</tabber>		</tabber>

Mparadis at 19:14, 11 April 2019

2019-04-11T19:14:49Z

@@ Line 146: / Line 146: @@
 //Assign the handler that will be called when the event occurs
 Phidget_setOnErrorHandler((PhidgetHandle)ch, onErrorHandler, NULL);
 </syntaxhighlight>
 </tabber>

Mparadis at 18:49, 11 April 2019

2019-04-11T18:49:00Z

@@ Line 53: / Line 53: @@
+}
 </syntaxhighlight>
 </tabber>

Jdecoux: /* Logging */

2019-04-09T15:32:28Z

Logging

← Older revision		Revision as of 15:32, 9 April 2019
Line 139:		Line 139:
	Python=<syntaxhighlight lang=python>		Python=<syntaxhighlight lang=python>
	from Phidget22.Devices.Log import *		from Phidget22.Devices.Log import *
			from Phidget22.LogLevel import *

	Log.enable(~~Phidget22.LogLevel.~~LogLevel.PHIDGET_LOG_INFO, "path/to/log/file.log")		Log.enable(LogLevel.PHIDGET_LOG_INFO, "path/to/log/file.log")
	</syntaxhighlight>		</syntaxhighlight>
	\|-\|		\|-\|

Jdecoux: /* Logging */

2019-04-09T15:25:47Z

Logging

← Older revision		Revision as of 15:25, 9 April 2019
Line 139:		Line 139:
	Python=<syntaxhighlight lang=python>		Python=<syntaxhighlight lang=python>
	from Phidget22.Devices.Log import *		from Phidget22.Devices.Log import *
	from Phidget22.LogLevel import *

	Log.enable(Phidget22.LogLevel.LogLevel.PHIDGET_LOG_INFO, "path/to/log/file.log")		Log.enable(Phidget22.LogLevel.LogLevel.PHIDGET_LOG_INFO, "path/to/log/file.log")

← Older revision		Revision as of 18:50, 14 July 2023
Line 199:		Line 199:

	For a more comprehensive look at the logging system in Phidget22, you can check out the [[Logging Details]] page.		For a more comprehensive look at the logging system in Phidget22, you can check out the [[Logging Details]] page.

			==Common Errors==
			For more information on how to handle common errors, such as sensor data being Out of Range or Invalid, see our page on [[Handling_Out_Of_Range_Errors]].

	== Other Problems ==		== Other Problems ==