GUI (o323BGCTool) FAQ - Revision history

OlliW at 09:30, 27 May 2014

2014-05-27T09:30:01Z

← Older revision		Revision as of 11:30, 27 May 2014
Line 1:		Line 1:
			Page does need maintenance.

	== General Comments ==		== General Comments ==
	* The AUX, BUT, and POT ports and teh Standby function are only active if the [Gimbal Configuration] parameter is set to "hand held".		* The AUX, BUT, and POT ports and teh Standby function are only active if the [Gimbal Configuration] parameter is set to "hand held".

OlliW: /* General comments */

2014-05-16T21:59:19Z

General comments

← Older revision		Revision as of 23:59, 16 May 2014
Line 1:		Line 1:
	== General ~~comments~~ ==		== General Comments ==
	* The AUX, BUT, and POT ports and teh Standby function are only active if the [Gimbal Configuration] parameter is set to "hand held".		* The AUX, BUT, and POT ports and teh Standby function are only active if the [Gimbal Configuration] parameter is set to "hand held".
	* Any parameter with a "(na)" in its name is not active, i.e., doesn't do anything.		* Any parameter with a "(na)" in its name is not active, i.e., doesn't do anything.

OlliW: /* Tips from Olli */

2014-05-13T12:35:51Z

Tips from Olli

@@ Line 24: / Line 24: @@
 To reverse the direction swap the min and max values, i.e. instead of e.g. min = -90 and max = +25 insert min = +25 and max = -90.
-== Tips from Olli ==
+== The "Get Current Motor Directions" Menu Option ==
-) Step 1 doesn't work for the yaw axis, for the obvious reason that there is nothing such as "levelled" for the yaw axis. As a second consequence the "yaw offset" parameter doesn't work (its there for historical reasons, and because I might change behavior in future). In order to bring the yaw axis into the desired zero position, i.e., heading forward, you can change the startup position parameter.
+In the tools menu, find the option "Get Current Motor Directions". Once your gimbal has reached the state "Normal" you may activate it. It will copy the detected motor directions into the respective parameter fields.

Yang: /* Tips from Olli */

2014-05-12T20:34:27Z

Tips from Olli

← Older revision		Revision as of 22:34, 12 May 2014
Line 27:		Line 27:
	1) In the tools menu, find the option "Get Current Motor Directions". Once your gimbal has reached the state "Normal" you may activate it. It will copy the detected motor directions into the respective parameter fields, so if you do now a write+store it will henceforth directly use these motor directions and skip the auto motor detection at startup... this saves you some 7 seconds.		1) In the tools menu, find the option "Get Current Motor Directions". Once your gimbal has reached the state "Normal" you may activate it. It will copy the detected motor directions into the respective parameter fields, so if you do now a write+store it will henceforth directly use these motor directions and skip the auto motor detection at startup... this saves you some 7 seconds.

	2) In the tools menu, find a option "Get Current Motor Positions". Once your gimbal has reached the state "Normal" you may activate it. It will copy the current level positions into the motor startup parameter fields. The effect is that the gimbal will move the motors to a nearly level position quite as the first step in the start up procedure. This also makes the startup faster.		2) Step 1 doesn't work for the yaw axis, for the obvious reason that there is nothing such as "levelled" for the yaw axis. As a second consequence the "yaw offset" parameter doesn't work (its there for historical reasons, and because I might change behavior in future). In order to bring the yaw axis into the desired zero position, i.e., heading forward, you can change the startup position parameter.

	3) Step 2 doesn't work for the yaw axis, for the obvious reason that there is nothing such as "levelled" for the yaw axis. As a second consequence the "yaw offset" parameter doesn't work (its there for historical reasons, and because I might change behavior in future). In order to bring the yaw axis into the desired zero position, i.e., heading forward, you can change the startup position parameter.


	~~'''On the Functions tab:'''~~

	~~pan = follow = the camera follows slowly the orientation of the gimbal frame~~

	~~hold = locked = the camera stays put with a fixed orientation~~

	the pan and/or hold mode is fundamentally controlled by the [Pitch Pan], [Roll Pan], and [Yaw Pan] values in the [Main] tab... a zero value means hold mode, while non zero value means pan mode, whereby a larger pan value means a faster following.

	~~'''Let's consider a generic example:'''~~

	~~Pan Mode Control = Aux-01 press~~

	~~Pan Mode Default Setting = hold hold pan~~

	~~Pan Mode Setting #1 = hold hold hold~~

	~~Pan Mode Setting #2 = pan pan pan~~

	~~Pan Mode Setting #3 = pan hold pan~~

	If neither of the two buttons connected to Aux-0 and Aux-1 are pressed, or switched on, then the Pan Mode Default Setting is active. In our example it overrides the pitch and roll pan values to zero. This means that the pitch and roll axes will be in hold mode irrespective of the [Pitch Pan], [Roll Pan] values specified in the [Main] tab, while the yaw axis is determined by the [Yaw Pan] value (which implies that if Yaw Pan=0 also the yaw axis would be in hold mode).

	If only the button connected to Aux-0 is pressed/switched on then the Pan Mode Setting #1 is active. In our example it overrides all three pan values to zero, which means that all three axes are in hold mode.

	If only the button connected to Aux-1 is pressed/switched on then the Pan Mode Setting #2 is active. In our example it doesn't affect any of the three pan values, which means that the behavior of three axes is exactly as specified by the [Pitch Pan], [Roll Pan], and [Yaw Pan] values in the [Main] tab (which implies that if any of them is zero the respective axis would be in hold mode).

	Finally, if both buttons connected to Aux-0 and Aux-1 are pressed/switched on then the Pan Mode Setting #3 is active. In our example it overrides the roll pan value to zero. This means that the roll axis will be in hold mode irrespective of the [Roll Pan] values specified in the [Main] tab, while the pitch and yaw axes are determined by the [Pitch Pan], [Yaw Pan] values.

OlliW: /* General comments */

2014-05-11T16:44:33Z

General comments

← Older revision		Revision as of 18:44, 11 May 2014
Line 1:		Line 1:
	== General comments ==		== General comments ==
	* The AUX, BUT, and POT ports are only active if the [Gimbal Configuration] parameter is set to "hand held".		* The AUX, BUT, and POT ports and teh Standby function are only active if the [Gimbal Configuration] parameter is set to "hand held".
	* Any parameter with a "(na)" in its name is not active, i.e., doesn't do anything.		* Any parameter with a "(na)" in its name is not active, i.e., doesn't do anything.
	* With the [Write] button, the GUI parameter values are copied to the board, and become effective immediately. They are however not stored permanently in the Eeprom, i.e., changes will be lost after a power down. To store changes permanently do a [Write+Store], e.g. by clicking the check box next to the [Write] button.		* With the [Write] button, the GUI parameter values are copied to the board, and become effective immediately. They are however not stored permanently in the Eeprom, i.e., changes will be lost after a power down. To store changes permanently do a [Write+Store], e.g. by clicking the check box next to the [Write] button.

OlliW at 13:29, 28 April 2014

2014-04-28T13:29:00Z

OlliW: /* General comments */

2014-04-27T02:22:49Z

General comments

← Older revision		Revision as of 04:22, 27 April 2014
Line 2:		Line 2:
	* The AUX, BUT, and POT ports are only active if the [Gimbal Configuration] parameter is set to "hand held".		* The AUX, BUT, and POT ports are only active if the [Gimbal Configuration] parameter is set to "hand held".
	* Any parameter with a "(na)" in its name is not active, i.e., doesn't do anything.		* Any parameter with a "(na)" in its name is not active, i.e., doesn't do anything.
	* With the [Write] button, the GUI parameter values are copied to the board and become immediately ~~active~~. They are however not stored permanently in the Eeprom, i.e., changes will be lost after a power down. ~~In order to~~ store changes permanently ~~one has to~~ do a [Write+Store], e.g. by clicking the check box next to the [Write] button.		* With the [Write] button, the GUI parameter values are copied to the board, and become effective immediately. They are however not stored permanently in the Eeprom, i.e., changes will be lost after a power down. To store changes permanently do a [Write+Store], e.g. by clicking the check box next to the [Write] button.

	=== Functions ===		=== Functions ===

OlliW: /* RC Inputs tab - RC Mode Definitions */

2014-04-26T15:22:39Z

RC Inputs tab - RC Mode Definitions

← Older revision		Revision as of 17:22, 26 April 2014
Line 22:		Line 22:
	max = the greater the number the more down it will tilt forward		max = the greater the number the more down it will tilt forward

	min = the lesser the number the more up it will tilt back ~~to reverse direction swap min and max~~		min = the lesser the number the more up it will tilt back

	~~The~~ direction ~~of movement can be changed by swaping~~ the min and max values, i.e. instead of e.g. min = -90 and max = +25 ~~one inserts~~ min = +25 and max = -90.		To reverse the direction swap the min and max values, i.e. instead of e.g. min = -90 and max = +25 insert min = +25 and max = -90.

	=== Tips from Olli ===		=== Tips from Olli ===

OlliW: /* General comments */

2014-04-26T08:32:42Z

General comments

← Older revision		Revision as of 10:32, 26 April 2014
Line 2:		Line 2:
	* The AUX, BUT, and POT ports are only active if the [Gimbal Configuration] parameter is set to "hand held".		* The AUX, BUT, and POT ports are only active if the [Gimbal Configuration] parameter is set to "hand held".
	* Any parameter with a "(na)" in its name is not active, i.e., doesn't do anything.		* Any parameter with a "(na)" in its name is not active, i.e., doesn't do anything.
			* With the [Write] button, the GUI parameter values are copied to the board and become immediately active. They are however not stored permanently in the Eeprom, i.e., changes will be lost after a power down. In order to store changes permanently one has to do a [Write+Store], e.g. by clicking the check box next to the [Write] button.

	=== Functions ===		=== Functions ===

OlliW: /* RC Inputs tab - RC Mode Definitions */

2014-04-26T07:36:38Z

RC Inputs tab - RC Mode Definitions

← Older revision		Revision as of 09:36, 26 April 2014
Line 22:		Line 22:

	min = the lesser the number the more up it will tilt back to reverse direction swap min and max		min = the lesser the number the more up it will tilt back to reverse direction swap min and max

			The direction of movement can be changed by swaping the min and max values, i.e. instead of e.g. min = -90 and max = +25 one inserts min = +25 and max = -90.

	=== Tips from Olli ===		=== Tips from Olli ===

← Older revision		Revision as of 15:29, 28 April 2014
Line 1:		Line 1:
	=== General comments ===		== General comments ==
	* The AUX, BUT, and POT ports are only active if the [Gimbal Configuration] parameter is set to "hand held".		* The AUX, BUT, and POT ports are only active if the [Gimbal Configuration] parameter is set to "hand held".
	* Any parameter with a "(na)" in its name is not active, i.e., doesn't do anything.		* Any parameter with a "(na)" in its name is not active, i.e., doesn't do anything.
	* With the [Write] button, the GUI parameter values are copied to the board, and become effective immediately. They are however not stored permanently in the Eeprom, i.e., changes will be lost after a power down. To store changes permanently do a [Write+Store], e.g. by clicking the check box next to the [Write] button.		* With the [Write] button, the GUI parameter values are copied to the board, and become effective immediately. They are however not stored permanently in the Eeprom, i.e., changes will be lost after a power down. To store changes permanently do a [Write+Store], e.g. by clicking the check box next to the [Write] button.

	=== Functions ===		== Functions ==

	Standby---But press (Hold button and standby is on. Release the button and standby is off)		Standby---But press (Hold button and standby is on. Release the button and standby is off)

	Standby---But push (Press button and standby is on. Press the button again and standby is off)		Standby---But push (Press button and standby is on. Press the button again and standby is off)

	=== RC Inputs tab - RC Mode Definitions ===		== RC Inputs tab - RC Mode Definitions ==

	Relative = stays where you placed it via joystick		Relative = stays where you placed it via joystick

Line 26:		Line 24:
	To reverse the direction swap the min and max values, i.e. instead of e.g. min = -90 and max = +25 insert min = +25 and max = -90.		To reverse the direction swap the min and max values, i.e. instead of e.g. min = -90 and max = +25 insert min = +25 and max = -90.

	=== Tips from Olli ===		== Tips from Olli ==

	1) In the tools menu, find the option "Get Current Motor Directions". Once your gimbal has reached the state "Normal" you may activate it. It will copy the detected motor directions into the respective parameter fields, so if you do now a write+store it will henceforth directly use these motor directions and skip the auto motor detection at startup... this saves you some 7 seconds.		1) In the tools menu, find the option "Get Current Motor Directions". Once your gimbal has reached the state "Normal" you may activate it. It will copy the detected motor directions into the respective parameter fields, so if you do now a write+store it will henceforth directly use these motor directions and skip the auto motor detection at startup... this saves you some 7 seconds.