GUI (o323BGCTool) FAQ: Difference between revisions

From STorM32-BGC Wiki
Jump to navigation Jump to search
No edit summary
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== General comments ==
Page does need maintenance.
* The AUX, BUT, and POT ports are only active if the [Gimbal Configuration] parameter is set to "hand held".
 
== 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".
* 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.


== 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 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
 
 
== 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.
 
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.
 
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:'''
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.


Pan Mode Control = Aux-01 press
== The "Get Current Motor Directions" Menu Option ==


Pan Mode Default Setting = hold hold pan
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.


Pan Mode Setting #1 = hold hold hold
Thus, if you do this and a Write+Store the controller will henceforth directly use these motor directions and skip the auto motor detection at start-up... this saves you some 7 seconds.


Pan Mode Setting #2 = pan pan pan
== The "Get Current Motor Positions" Menu Option ==


Pan Mode Setting #3 = pan hold pan
In the tools menu, find the option "Get Current Motor Positions". Once your gimbal has reached the state "Normal" you may activate it. It will copy the current motor positions into the motor start-up parameter fields.


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).
The motor start-up values determine the position of the motor directly after the controller has been switched on. In general these positions however do not coincide with the camera being leveled, i.e. the camera will "jump" out of level upon powering up the controller. This can be rectified by a "Get Current Motor Positions" and a Write+Store; the gimbal will henceforth move the motors to a nearly level position quite as the first step in the start-up procedure.  


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.
This makes the start-up also somewhat faster since the leveling goes faster.


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).
A difference has to be noted however for the yaw axis, for the obvious reason that there is nothing such as "leveled" for the yaw axis and it is therefore not moved as part as of the initialization procedure. In general the default yaw motor position won't coincide with the desired "forward" orientation, and the camera would be out of axis. This can be rectified as follows:


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.
Switch to hold mode for the yaw axis, and turn the gimbal such that the camera points forward. No do a "Get Current Motor Positions" and a Write+Store, and the current orientation will be used as start-up henceforth.

Latest revision as of 10:30, 27 May 2014

Page does need maintenance.

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".
  • 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.

Functions

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)

RC Inputs tab - RC Mode Definitions

Relative = stays where you placed it via joystick

Absolute = follows the stick position, returns to level when joystick released

speed = limits maximal speed of tilts

accel = slows it down like panning (off = fast 0 - 100 slower = on)

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 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.

The "Get Current Motor Directions" Menu Option

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.

Thus, if you do this and a Write+Store the controller will henceforth directly use these motor directions and skip the auto motor detection at start-up... this saves you some 7 seconds.

The "Get Current Motor Positions" Menu Option

In the tools menu, find the option "Get Current Motor Positions". Once your gimbal has reached the state "Normal" you may activate it. It will copy the current motor positions into the motor start-up parameter fields.

The motor start-up values determine the position of the motor directly after the controller has been switched on. In general these positions however do not coincide with the camera being leveled, i.e. the camera will "jump" out of level upon powering up the controller. This can be rectified by a "Get Current Motor Positions" and a Write+Store; the gimbal will henceforth move the motors to a nearly level position quite as the first step in the start-up procedure.

This makes the start-up also somewhat faster since the leveling goes faster.

A difference has to be noted however for the yaw axis, for the obvious reason that there is nothing such as "leveled" for the yaw axis and it is therefore not moved as part as of the initialization procedure. In general the default yaw motor position won't coincide with the desired "forward" orientation, and the camera would be out of axis. This can be rectified as follows:

Switch to hold mode for the yaw axis, and turn the gimbal such that the camera points forward. No do a "Get Current Motor Positions" and a Write+Store, and the current orientation will be used as start-up henceforth.

Retrieved from "http:///storm32bgc-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&oldid=1259"