FiniteStateMachine - Revision history

BenR: /* Techniques */

2021-12-08T13:20:44Z

Techniques

BenR: /* Techniques */

2021-12-08T13:20:29Z

Techniques

BenR at 11:27, 16 October 2020

2020-10-16T11:27:10Z

BenR at 11:27, 16 October 2020

2020-10-16T11:27:01Z

DavidA at 07:58, 2 July 2019

2019-07-02T07:58:34Z

BenR at 11:37, 30 November 2018

2018-11-30T11:37:24Z

BenR at 17:21, 26 February 2018

2018-02-26T17:21:40Z

BenR at 17:20, 26 February 2018

2018-02-26T17:20:00Z

BenR at 17:19, 26 February 2018

2018-02-26T17:19:28Z

BenR at 09:11, 17 May 2017

2017-05-17T09:11:14Z

← Older revision		Revision as of 13:20, 8 December 2021
Line 35:		Line 35:

	As you can see making a cup of tea actually has a lot of stages and could be made much more complex, e.g. adding sugar, time to let the tea brew, removing the tea bag, milk before or after water, amount of milk....		As you can see making a cup of tea actually has a lot of stages and could be made much more complex, e.g. adding sugar, time to let the tea brew, removing the tea bag, milk before or after water, amount of milk....
		+

	It is also possible to design in error handling at this stage, let's consider the kettle is broken and therefore the water will never boil. We could potentially get stuck forever at stage 2 waiting for the kettle to boil. This can be handled by adding a timeout which resets back to State 0 or a special error state if the stage is taking longer than usual. The error state could display a user message to let you know what the specific problem is. Consider each minor task and try to determine what problems could arise and what you might do to try and catch or work around them.		It is also possible to design in error handling at this stage, let's consider the kettle is broken and therefore the water will never boil. We could potentially get stuck forever at stage 2 waiting for the kettle to boil. This can be handled by adding a timeout which resets back to State 0 or a special error state if the stage is taking longer than usual. The error state could display a user message to let you know what the specific problem is. Consider each minor task and try to determine what problems could arise and what you might do to try and catch or work around them.

← Older revision		Revision as of 13:20, 8 December 2021
Line 36:		Line 36:
	As you can see making a cup of tea actually has a lot of stages and could be made much more complex, e.g. adding sugar, time to let the tea brew, removing the tea bag, milk before or after water, amount of milk....		As you can see making a cup of tea actually has a lot of stages and could be made much more complex, e.g. adding sugar, time to let the tea brew, removing the tea bag, milk before or after water, amount of milk....

		+	It is also possible to design in error handling at this stage, let's consider the kettle is broken and therefore the water will never boil. We could potentially get stuck forever at stage 2 waiting for the kettle to boil. This can be handled by adding a timeout which resets back to State 0 or a special error state if the stage is taking longer than usual. The error state could display a user message to let you know what the specific problem is. Consider each minor task and try to determine what problems could arise and what you might do to try and catch or work around them.

	==FSM Example 1 - Simple comms parsing==		==FSM Example 1 - Simple comms parsing==

← Older revision		Revision as of 11:27, 16 October 2020
Line 5:		Line 5:
	They are a means to allow a fixed number of deterministic states which can vastly simplify a program and is a great tool to add to your coding kit.		They are a means to allow a fixed number of deterministic states which can vastly simplify a program and is a great tool to add to your coding kit.

−	Flowcode now offers a [[State_diagrams\State Diagram]] method of coding but the techniques shown here are still valid and can be used in either coding paradigm.	+	Flowcode now offers a [[State_diagrams\|State Diagram]] method of coding but the techniques shown here are still valid and can be used in either coding paradigm.

← Older revision		Revision as of 11:27, 16 October 2020
Line 1:		Line 1:
		+	==Introduction==
		+
	Finite state machines are used all over the place in Flowcode components to keep track of things.		Finite state machines are used all over the place in Flowcode components to keep track of things.

	They are a means to allow a fixed number of deterministic states which can vastly simplify a program and is a great tool to add to your coding kit.		They are a means to allow a fixed number of deterministic states which can vastly simplify a program and is a great tool to add to your coding kit.
		+
		+	Flowcode now offers a [[State_diagrams\State Diagram]] method of coding but the techniques shown here are still valid and can be used in either coding paradigm.

← Older revision		Revision as of 07:58, 2 July 2019
Line 1:		Line 1:
−	~~<sidebar>Sidebar: Flowcode Help Overview:Variables</sidebar>~~
−
	Finite state machines are used all over the place in Flowcode components to keep track of things.		Finite state machines are used all over the place in Flowcode components to keep track of things.

← Older revision		Revision as of 11:37, 30 November 2018
Line 100:		Line 100:

	{{Fcfile\|ServoController.fcfx\|ServoFeeder}}		{{Fcfile\|ServoController.fcfx\|ServoFeeder}}
		+
		+
		+	==FSM Example 5 - SCADA Slave Firmware==
		+
		+	The firmware for the SCADA Slave targets is driven using a simple state machine approach.
		+
		+	'''Mode 0'''
		+
		+	Monitor incoming comms data for a valid command code, once a valid code is found we assign a count of parameters and returns.
		+
		+	If there are any parameters then move to Mode 1, else action the command and if there are any returns then move to Mode 2. If no returns then stay on Mode 0.
		+
		+
		+	'''Mode 1'''
		+
		+	Store incoming bytes until we have collected all the incoming parameters for the command.
		+
		+	Action the command and if there are any returns then move to Mode 2. If no returns then return to Mode 0.
		+
		+
		+	'''Mode 2'''
		+
		+	Send out all the outgoing return bytes and once complete return to Mode 0.
		+
		+
		+	{{Zip\|Arduino_Uno_SCADA_Firmware.zip\|Arduino Uno SCADA Firmware}}

@@ Line 96: / Line 96: @@
 Here is a project created to drive a pick and place component feeder bank.
-The PC tells us when we need to move to the next component using a motor so we need to use a state machine to listen to and decode the incoming comms to detect when one of our feeder channels gets called up for action. When a valid feeder channel is detected we use a second state machine to start the motor moving and then after a delay to allow the motor to move we bring the motor back to the original start position. The second state machine has 8 tracking variables which allows us to control all 8 servo channels using the state machine. Using the state machines means that we are not having to use blocking code such as delays when moving the motors which means that multiple feeder channels can be in motion at once.
+The PC tells us when we need to move to the next component using a motor so we need to use a state machine to listen to and decode the incoming comms to detect when one of our feeder channels gets called up for action. When a valid feeder channel is detected we use a second state machine to start the motor moving and then after a delay to allow the motor to move we bring the motor back to the original start position. The second state machine has 8 tracking variables which allows us to control all 8 servo channels using the state machine. Using the state machines means that we are not having to use blocking code such as delays when moving the motors which means that multiple feeder channels can be in various stages of motion at once.
 {{Fcfile|ServoController.fcfx|ServoFeeder}}

← Older revision		Revision as of 17:20, 26 February 2018
Line 32:		Line 32:


−	As you can see making a cup of tea actually has a lot of stages and could be made much more complex, e.g. adding sugar, time to let the tea brew, removing the tea bag, milk before or after water....	+	As you can see making a cup of tea actually has a lot of stages and could be made much more complex, e.g. adding sugar, time to let the tea brew, removing the tea bag, milk before or after water, amount of milk....

← Older revision		Revision as of 17:19, 26 February 2018
Line 32:		Line 32:


−	As you can see making a cup of tea actually has a lot of stages and could be made much more complex, e.g. adding sugar, time to let the tea brew, milk before or after water....	+	As you can see making a cup of tea actually has a lot of stages and could be made much more complex, e.g. adding sugar, time to let the tea brew, removing the tea bag, milk before or after water....

← Older revision		Revision as of 09:11, 17 May 2017
Line 1:		Line 1:
		+	<sidebar>Sidebar: Flowcode Help Overview:Variables</sidebar>
		+
	Finite state machines are used all over the place in Flowcode components to keep track of things.		Finite state machines are used all over the place in Flowcode components to keep track of things.