Configure the RC Input - Revision history

OlliW at 13:46, 21 January 2023

2023-01-21T13:46:51Z

← Older revision		Revision as of 15:46, 21 January 2023
Line 1:		Line 1:
	<span style="font-size:88%">''by Yang/wdaehn, with edits by OlliW, descriptions refer to firmwares v2.xx</span>''		<span style="font-size:88%">''by Yang/wdaehn, with edits by OlliW, descriptions refer to firmwares v2.xx''</span>

	The orientation of the camera can be controlled by a variety of external input signals such as from a receiver, a joystick, or buttons. The source of the input signal and the exact behavior of the camera in relation to the input is configured in the {{GUI\|Rc Inputs}} tab, which is described in the first chapter below. Physically the signal sources need to be connected to certain pins on the controller. The various possibilities are described in the subsequent chapters. For a general overview of the available pins on the controller consult [[Pins and Connectors\|Pins and Connectors]].		The orientation of the camera can be controlled by a variety of external input signals such as from a receiver, a joystick, or buttons. The source of the input signal and the exact behavior of the camera in relation to the input is configured in the {{GUI\|Rc Inputs}} tab, which is described in the first chapter below. Physically the signal sources need to be connected to certain pins on the controller. The various possibilities are described in the subsequent chapters. For a general overview of the available pins on the controller consult [[Pins and Connectors\|Pins and Connectors]].

OlliW: /* Testing Inputs */

2022-09-26T11:03:57Z

Testing Inputs

← Older revision		Revision as of 13:03, 26 September 2022
Line 124:		Line 124:
	For that purpose, the STorM32 GUI provides the {{GUI\|Inputs Tool}}, which shows the values for all inputs, as well as the values which each function uses.		For that purpose, the STorM32 GUI provides the {{GUI\|Inputs Tool}}, which shows the values for all inputs, as well as the values which each function uses.

	However, there is a catch ~~for this to work~~ for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.		However, there is a catch for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.

	See also [[Inputs and Functions#GUI Inputs Tool\|Inputs and Functions: GUI Inputs Tool]].		See also [[Inputs and Functions#GUI Inputs Tool\|Inputs and Functions: GUI Inputs Tool]].

OlliW: /* Testing Inputs */

2022-09-26T11:03:42Z

Testing Inputs

← Older revision		Revision as of 13:03, 26 September 2022
Line 126:		Line 126:
	However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.		However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.

	See also ~~[Inputs_and_Functions#GUI_Inputs_Tool]~~ [[Inputs and Functions#GUI Inputs Tool\|Inputs and Functions: GUI Inputs Tool]].		See also [[Inputs and Functions#GUI Inputs Tool\|Inputs and Functions: GUI Inputs Tool]].

	== Next Step - Basic Gimbal Functions ==		== Next Step - Basic Gimbal Functions ==

	Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.		Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.

OlliW: /* Testing Inputs */

2022-09-26T11:03:27Z

Testing Inputs

← Older revision		Revision as of 13:03, 26 September 2022
Line 126:		Line 126:
	However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.		However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.

	See also [Inputs_and_Functions#GUI_Inputs_Tool] [Inputs and Functions: GUI Inputs Tool\|Inputs and Functions#GUI Inputs Tool].		See also [Inputs_and_Functions#GUI_Inputs_Tool] [[Inputs and Functions#GUI Inputs Tool\|Inputs and Functions: GUI Inputs Tool]].

	== Next Step - Basic Gimbal Functions ==		== Next Step - Basic Gimbal Functions ==

	Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.		Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.

OlliW: /* Testing Inputs */

2022-09-26T11:02:11Z

Testing Inputs

← Older revision		Revision as of 13:02, 26 September 2022
Line 126:		Line 126:
	However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.		However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.

	See also [Inputs_and_Functions#GUI_Inputs_Tool] [[Inputs and Functions: GUI Inputs Tool\|Inputs and Functions#GUI Inputs Tool]].		See also [Inputs_and_Functions#GUI_Inputs_Tool] [Inputs and Functions: GUI Inputs Tool\|Inputs and Functions#GUI Inputs Tool].

	== Next Step - Basic Gimbal Functions ==		== Next Step - Basic Gimbal Functions ==

	Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.		Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.

OlliW: /* Testing Inputs */

2022-09-26T11:02:01Z

Testing Inputs

← Older revision		Revision as of 13:02, 26 September 2022
Line 126:		Line 126:
	However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.		However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.

	See also [Inputs_and_Functions#GUI_Inputs_Tool] [[Inputs and Functions#GUI Inputs Tool]].		See also [Inputs_and_Functions#GUI_Inputs_Tool] [[Inputs and Functions: GUI Inputs Tool\|Inputs and Functions#GUI Inputs Tool]].

	== Next Step - Basic Gimbal Functions ==		== Next Step - Basic Gimbal Functions ==

	Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.		Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.

OlliW: /* Testing Inputs */

2022-09-26T11:01:17Z

Testing Inputs

← Older revision		Revision as of 13:01, 26 September 2022
Line 126:		Line 126:
	However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.		However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.

	See also [Inputs_and_Functions#GUI_Inputs_Tool].		See also [Inputs_and_Functions#GUI_Inputs_Tool] [[Inputs and Functions#GUI Inputs Tool]].

	== Next Step - Basic Gimbal Functions ==		== Next Step - Basic Gimbal Functions ==

	Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.		Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.

OlliW: /* Testing Inputs */

2022-09-26T11:00:45Z

Testing Inputs

← Older revision		Revision as of 13:00, 26 September 2022
Line 125:		Line 125:

	However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.		However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.

			See also [Inputs_and_Functions#GUI_Inputs_Tool].

	== Next Step - Basic Gimbal Functions ==		== Next Step - Basic Gimbal Functions ==

	Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.		Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.

OlliW: /* Testing Inputs */

2022-09-26T07:07:57Z

Testing Inputs

← Older revision		Revision as of 09:07, 26 September 2022
Line 122:		Line 122:
	During setup it can happen that one wants to "see" what input values are received by the STorM32 controller, for testing a configuration or for finding configuration mistakes.		During setup it can happen that one wants to "see" what input values are received by the STorM32 controller, for testing a configuration or for finding configuration mistakes.

	For that purpose, the STorM32 GUI provides the Inputs Tool, which shows the values for all inputs, as well as the values which each function uses.		For that purpose, the STorM32 GUI provides the {{GUI\|Inputs Tool}}, which shows the values for all inputs, as well as the values which each function uses.

	However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.		However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.

OlliW: /* Testing Inputs */

2022-09-26T07:07:08Z

Testing Inputs

← Older revision		Revision as of 09:07, 26 September 2022
Line 120:		Line 120:
	== Testing Inputs ==		== Testing Inputs ==

	During setup it can happen that one wants to "see" what input values are received by the STorM32 controller, for testing a configuration or for finding configuration mistakes. However, the STorM32 controller can't provide a display of its input signals. This is so because it disables all input pins which are not configured, which it does to keep the system free of noise. The following procedure can be suggested, which usually does the trick:		During setup it can happen that one wants to "see" what input values are received by the STorM32 controller, for testing a configuration or for finding configuration mistakes.

	~~The DataDisplay displays~~ the values ~~representing the~~ inputs for the functions {{PARAMNAME\|Rc Pitch}}, {{PARAMNAME\|Rc Roll}}, {{PARAMNAME\|Rc Yaw}}, {{PARAMNAME\|Pan Mode Control}}, {{PARAMNAME\|Camera Control}}, {{PARAMNAME\|Standby}}, and {{PARAMNAME\|Re-center Camera}}, ~~see [[Using~~ the ~~DataDisplay]], 6th point~~.		For that purpose, the STorM32 GUI provides the Inputs Tool, which shows the values for all inputs, as well as the values which each function uses.

	~~Thus~~, ~~in order~~ to ~~check if an input~~ is ~~received by~~ the STorM32, one ~~can~~ set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to ~~the desired~~ input channel, e.g., {{PARAMVALUE\|Virtual-1}}~~, start the DataDisplay, and check if the corresponding value in the DataDisplay is responding to changes in the input~~. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} ~~were used~~ here exemplarily, the procedure works for any of the mentioned function, and for all input channels.		However, there is a catch for this to work for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.

	== Next Step - Basic Gimbal Functions ==		== Next Step - Basic Gimbal Functions ==

	Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.		Depending on the type of gimbal, where and how it is used, you might want to select different modes of operation. Basically, the controller can either keep the camera at the same position with respect to the ground or with respect to the gimbal support frame, and this for each axis individually. See examples and setup strategies in the [[Hold versus Pan Mode]] chapter.

← Older revision		Revision as of 13:03, 26 September 2022
Line 124:		Line 124:
	For that purpose, the STorM32 GUI provides the {{GUI\|Inputs Tool}}, which shows the values for all inputs, as well as the values which each function uses.		For that purpose, the STorM32 GUI provides the {{GUI\|Inputs Tool}}, which shows the values for all inputs, as well as the values which each function uses.

	However, there is a catch ~~for this to work~~ for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.		However, there is a catch for the virtual channels, namely that at least one virtual channel must be configured (this is so because the STorM32 controller disables all input pins which are not configured, to keep the system free of noise). If no virtual channel is used, one may set e.g. the parameter {{PARAMNAME\|Rc Pitch}} to an arbitrary input channel, e.g., {{PARAMVALUE\|Virtual-1}}. Obviously, {{PARAMNAME\|Rc Pitch}} and {{PARAMVALUE\|Virtual-1}} are suggested here exemplarily, the procedure works for any of the mentioned function, and for all input channels.

	See also [[Inputs and Functions#GUI Inputs Tool\|Inputs and Functions: GUI Inputs Tool]].		See also [[Inputs and Functions#GUI Inputs Tool\|Inputs and Functions: GUI Inputs Tool]].