Failsafe Guide - Revision history

Lmpacent: /* Other Considerations */

2024-07-02T20:08:59Z

Other Considerations

← Older revision		Revision as of 20:08, 2 July 2024
Line 52:		Line 52:

	====Other Considerations====		====Other Considerations====
	* Once the failsafe timer is enabled, it cannot be disabled by any means other than closing and reopening the channel.		Once the failsafe timer is enabled, it cannot be disabled by any means other than closing and reopening the channel.

	===Resetting Failsafe Timer===		===Resetting Failsafe Timer===

2024-07-02T20:07:35Z

Scenario 2: Failsafe Enabled

← Older revision		Revision as of 20:07, 2 July 2024
Line 25:		Line 25:


	When communication is lost, the controller enters a [[#Failsafe State\|failsafe state]] after a predetermined time ([[#Failsafe Time\|failsafe time]]).		When communication is lost, the controller enters a [[#Failsafe State\|failsafe state]] after a predetermined time (the [[#Failsafe Time\|failsafe time]]).

2024-07-02T20:06:36Z

What is Failsafe?

← Older revision		Revision as of 20:06, 2 July 2024
Line 3:		Line 3:
	__TOC__		__TOC__
	==What is Failsafe?==		==What is Failsafe?==
	Failsafe is a feature that activates when communication is lost between an application and ~~the~~ Phidget controller. When enabled, it reverts the controller to a predefined safe state.		Failsafe is a feature that activates when communication is lost between an application and a Phidget controller. When enabled, it reverts the controller to a predefined safe state.

	===Failsafe Example===		===Failsafe Example===

2024-07-02T20:06:24Z

What is Failsafe?

← Older revision		Revision as of 20:06, 2 July 2024
Line 3:		Line 3:
	__TOC__		__TOC__
	==What is Failsafe?==		==What is Failsafe?==
	Failsafe is a feature that activates when communication is lost between ~~your~~ application and the Phidget controller. When enabled, it reverts the controller to a predefined safe state.		Failsafe is a feature that activates when communication is lost between an application and the Phidget controller. When enabled, it reverts the controller to a predefined safe state.

	===Failsafe Example===		===Failsafe Example===

2024-06-07T16:08:01Z

← Older revision		Revision as of 16:08, 7 June 2024
Line 37:		Line 37:

	===Failsafe Timing Example===		===Failsafe Timing Example===
	[[Image:Failsafe_guide_timing_diagram.png\|650px\|center\|link=https://cdn.phidgets.com/docs/images/a/ab/Failsafe_guide_timing_diagram.png]]		[[Image:Failsafe_guide_timing_diagram.png\|650px\|center\|link=https://cdn.phidgets.com/docs/images/a/ab/Failsafe_guide_timing_diagram.png\|Page image]]

	In this example, the channel is opened, and failsafe functionality is enabled with a failsafe time of 1000ms. The controller begins receiving failsafe resets from the application, allowing it to stay in a normal operating state. The application eventually fails to send another reset (application crash, cable physically disconnected, etc.), and after 1000ms the controller enters a failsafe state.		In this example, the channel is opened, and failsafe functionality is enabled with a failsafe time of 1000ms. The controller begins receiving failsafe resets from the application, allowing it to stay in a normal operating state. The application eventually fails to send another reset (application crash, cable physically disconnected, etc.), and after 1000ms the controller enters a failsafe state.

2024-06-07T16:07:46Z

← Older revision		Revision as of 16:07, 7 June 2024
Line 1:		Line 1:
	{{#seo:		{{#seo:description=Learn how to add failsafe functionality to your application.}}
	\|description=Learn how to add failsafe functionality to your application.}}
	[[Category:IntroGuide]]		[[Category:IntroGuide]]
	__TOC__		__TOC__

2024-06-07T16:05:42Z

← Older revision		Revision as of 16:05, 7 June 2024
Line 38:		Line 38:

	===Failsafe Timing Example===		===Failsafe Timing Example===
	[[Image:Failsafe_guide_timing_diagram.png\|650px\|center\|link=https://cdn.phidgets.com/docs/images/a/ab/Failsafe_guide_timing_diagram.png~~\|Page image~~]]		[[Image:Failsafe_guide_timing_diagram.png\|650px\|center\|link=https://cdn.phidgets.com/docs/images/a/ab/Failsafe_guide_timing_diagram.png]]

	In this example, the channel is opened, and failsafe functionality is enabled with a failsafe time of 1000ms. The controller begins receiving failsafe resets from the application, allowing it to stay in a normal operating state. The application eventually fails to send another reset (application crash, cable physically disconnected, etc.), and after 1000ms the controller enters a failsafe state.		In this example, the channel is opened, and failsafe functionality is enabled with a failsafe time of 1000ms. The controller begins receiving failsafe resets from the application, allowing it to stay in a normal operating state. The application eventually fails to send another reset (application crash, cable physically disconnected, etc.), and after 1000ms the controller enters a failsafe state.

2024-06-07T16:05:16Z

← Older revision		Revision as of 16:05, 7 June 2024
Line 1:		Line 1:
	{{#seo:		{{#seo:
	\|description=Learn how to add failsafe functionality to your application.		\|description=Learn how to add failsafe functionality to your application.}}
	~~\|image=https://cdn.phidgets.com/docs/images/a/ab/Failsafe_guide_timing_diagram.png~~}}
	[[Category:IntroGuide]]		[[Category:IntroGuide]]
	__TOC__		__TOC__

2024-06-07T16:04:55Z

← Older revision		Revision as of 16:04, 7 June 2024
Line 39:		Line 39:

	===Failsafe Timing Example===		===Failsafe Timing Example===
	[[Image:Failsafe_guide_timing_diagram.png\|650px\|center\|link=https://cdn.phidgets.com/docs/images/a/ab/Failsafe_guide_timing_diagram.png]]		[[Image:Failsafe_guide_timing_diagram.png\|650px\|center\|link=https://cdn.phidgets.com/docs/images/a/ab/Failsafe_guide_timing_diagram.png\|Page image]]

	In this example, the channel is opened, and failsafe functionality is enabled with a failsafe time of 1000ms. The controller begins receiving failsafe resets from the application, allowing it to stay in a normal operating state. The application eventually fails to send another reset (application crash, cable physically disconnected, etc.), and after 1000ms the controller enters a failsafe state.		In this example, the channel is opened, and failsafe functionality is enabled with a failsafe time of 1000ms. The controller begins receiving failsafe resets from the application, allowing it to stay in a normal operating state. The application eventually fails to send another reset (application crash, cable physically disconnected, etc.), and after 1000ms the controller enters a failsafe state.

2024-06-06T20:23:35Z

← Older revision		Revision as of 20:23, 6 June 2024
Line 1:		Line 1:
	{{#seo:\|description=Learn how to add failsafe functionality to your application.}}		{{#seo:
	~~{{#seo:~~\|image=https://cdn.phidgets.com/docs/images/a/ab/Failsafe_guide_timing_diagram.png}}		\|description=Learn how to add failsafe functionality to your application.
			\|image=https://cdn.phidgets.com/docs/images/a/ab/Failsafe_guide_timing_diagram.png}}
	[[Category:IntroGuide]]		[[Category:IntroGuide]]
	__TOC__		__TOC__