<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://www.olliw.eu/storm32bgc-v2-wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Greg+Covey</id>
	<title>STorM32-BGC Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://www.olliw.eu/storm32bgc-v2-wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Greg+Covey"/>
	<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/Special:Contributions/Greg_Covey"/>
	<updated>2026-04-29T09:01:35Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.3</generator>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=Docu_for_witespy_board(s)&amp;diff=1466</id>
		<title>Docu for witespy board(s)</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=Docu_for_witespy_board(s)&amp;diff=1466"/>
		<updated>2014-08-13T15:44:26Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page provides documentation for the STorM32-BGC board sold by [http://witespyquad.gostorego.com/flight-controllers/storm32-bgc-3-axis-stm32-brushless-gimbal-controller.html Witespy - Ready To Fly Quads].&lt;br /&gt;
&lt;br /&gt;
== Dos and Don&#039;ts ==&lt;br /&gt;
&lt;br /&gt;
Please read the tutorial&#039;s [[Getting Started#Dos and Don&#039;ts|Dos and Don&#039;ts]]. &lt;br /&gt;
&lt;br /&gt;
== Shop Link == &lt;br /&gt;
&lt;br /&gt;
http://witespyquad.gostorego.com/flight-controllers/storm32-bgc-3-axis-stm32-brushless-gimbal-controller.html&lt;br /&gt;
&lt;br /&gt;
== Board Configuration ==&lt;br /&gt;
* board version: v1.1&lt;br /&gt;
* board color: blue&lt;br /&gt;
* motor drivers in DFN packages: yes&lt;br /&gt;
* on-board MPU: yes&lt;br /&gt;
* on-board bluetooth module: no&lt;br /&gt;
* I2C plug type: picoblade (1.25mm JST)&lt;br /&gt;
* I2C#2 plug type: picoblade (1.25mm JST)&lt;br /&gt;
* pin headers: no&lt;br /&gt;
&lt;br /&gt;
Included accessories:&lt;br /&gt;
* MPU module&lt;br /&gt;
* cable with connectors for MPU module&lt;br /&gt;
&lt;br /&gt;
Comments:&lt;br /&gt;
* diode for on-board bluetooth module not populated (see [[Docu for witespy board#On-board Bluetooth|here]])&lt;br /&gt;
* the board comes without firmware, it hence has first to be flashed (see [[Docu for witespy board#Flashing Firmware|here]])&lt;br /&gt;
&lt;br /&gt;
== Specifications ==&lt;br /&gt;
&lt;br /&gt;
* supply voltage: 6 - 18 V or 2 - 4S&lt;br /&gt;
* motor current: max. 1.5 A per motor&amp;lt;br/&amp;gt;&#039;&#039;&#039;&#039;&#039;Comment&#039;&#039;&#039;: This is not yet fully exploited, motors with resistances of 12 Ohm or larger have been tested to be well handled at 4S (see [//www.rcgroups.com/forums/showthread.php?t=2055844&amp;amp;page=2&amp;amp;pp=50#post27515444 here], [//www.rcgroups.com/forums/showthread.php?t=2055844&amp;amp;page=15&amp;amp;pp=50#post28578479 here]), motors with 10 Ohm may be handled with care (see [http://www.rcgroups.com/forums/showpost.php?p=28825482&amp;amp;postcount=947 here] and [http://www.rcgroups.com/forums/showpost.php?p=28852888&amp;amp;postcount=953 here])&#039;&#039;.&lt;br /&gt;
* board dimensions: 50 mm x 50 mm, 45 mm bolt to bolt, holes Ø3 mm&lt;br /&gt;
&lt;br /&gt;
== Pins and Connectors ==&lt;br /&gt;
&lt;br /&gt;
[[File:Stom32-bgc-witespy-ports-and-connections-01.jpg|600px]]&lt;br /&gt;
&lt;br /&gt;
== Flashing Firmware ==&lt;br /&gt;
&lt;br /&gt;
Follow the instructions for {{WARNING|v1.1 boards}} in the [[How to flash firmware]] manual.&lt;br /&gt;
&lt;br /&gt;
[[File:Stom32-bgc-witespy-flashing-w-usbttladapter-connections-01.jpg|600px]]&lt;br /&gt;
&lt;br /&gt;
== On-board Bluetooth ==&lt;br /&gt;
&lt;br /&gt;
The witespy board can be equipped with a [[Bluetooth Module HC06|HC06 bluetooth module]] on the bottom side of the board. However, a diode, which is needed for the on-board bluetooth module to work, is not populated. Its location is shown in the photo below. In principle any diode which fits on the pads can be used, but preferably a Shottky diode is choosen. The &amp;quot;original&amp;quot; type is a [http://www.nxp.com/documents/data_sheet/BAS40_1PSXXSB4X_SER.pdf 1PS76SB40]. A possibly simpler solution is to just short circuit the two pads by e.g. soldering a piece of wire across them. However, the communication via the UART port wouldn&#039;t work then anymore, i.e. this should only be done if one is not going to use the UART port anytime.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Since most of us don&#039;t seem to need or use the UART port, we can simply jumper across the diode pads permanently with a piece piece of wire.&lt;br /&gt;
&lt;br /&gt;
For further info on the HC06 bluetooth module, and its installation and configuration, see [[Bluetooth Module HC06]].&lt;br /&gt;
&lt;br /&gt;
[[File:Storm32bgc-v11-witespy-diode-location.jpg|450px]]&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=919</id>
		<title>GUI (o323BGCTool) FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=919"/>
		<updated>2014-04-12T12:48:38Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;General comments:&#039;&#039;&#039;&lt;br /&gt;
* The AUX, BUT, and POT ports are only active if the [Gimbal Configuration] parameter is set to &amp;quot;hand held&amp;quot;.&lt;br /&gt;
* Any parameter with a &amp;quot;(na)&amp;quot; in its name is not active, i.e., doesn&#039;t do anything. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Functions:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Standby---But press (Hold button and standby is on. Release the button and standby is off)&lt;br /&gt;
&lt;br /&gt;
Standby---But push (Press button and standby is on. Press the button again and standby is off)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;RC Inputs tab - RC Mode Definitions:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Relative = stays where you placed it via joystick&lt;br /&gt;
&lt;br /&gt;
Absolute = follows the stick position, returns to level when joystick released&lt;br /&gt;
&lt;br /&gt;
speed = limits maximal speed of tilts&lt;br /&gt;
&lt;br /&gt;
accel = slows it down like panning (off = fast 0 - 100 slower = on)&lt;br /&gt;
&lt;br /&gt;
max = the greater the number the more down it will tilt forward&lt;br /&gt;
&lt;br /&gt;
min = the lesser the number the more up it will tilt back to reverse direction swap min and max&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Tips from Olli:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1) In the tools menu, find the option &amp;quot;Get Current Motor Directions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
2) In the tools menu, find a option &amp;quot;Get Current Motor Positions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
3) Step 2 doesn&#039;t work for the yaw axis, for the obvious reason that there is nothing such as &amp;quot;levelled&amp;quot; for the yaw axis. As a second consequence the &amp;quot;yaw offset&amp;quot; parameter doesn&#039;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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;On the Functions tab:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
pan = follow = the camera follows slowly the orientation of the gimbal frame&lt;br /&gt;
hold = locked = the camera stays put with a fixed orientation&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Let&#039;s consider a generic example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Pan Mode Control = Aux-01 press&lt;br /&gt;
&lt;br /&gt;
Pan Mode Default Setting = hold hold pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #1 = hold hold hold&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #2 = pan pan pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #3 = pan hold pan&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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&#039;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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=918</id>
		<title>GUI (o323BGCTool) FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=918"/>
		<updated>2014-04-12T12:48:19Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;General comments:&#039;&#039;&#039;&lt;br /&gt;
* The AUX, BUT, and POT ports are only active if the [Gimbal Configuration] parameter is set to &amp;quot;hand held&amp;quot;.&lt;br /&gt;
* Any parameter with a &amp;quot;(na)&amp;quot; in its name is not active, i.e., doesn&#039;t do anything. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Functions:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Standby---But press (Hold button and standby is on. Release the button and standby is off)&lt;br /&gt;
&lt;br /&gt;
Standby---But push (Press button and standby is on. Press the button again and standby is off)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;RC Inputs tab - RC Mode Definitions:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Relative = stays where you placed it via joystick&lt;br /&gt;
&lt;br /&gt;
Absolute = follows the stick position, returns to level when joystick released&lt;br /&gt;
&lt;br /&gt;
speed = limits maximal speed of tilts&lt;br /&gt;
&lt;br /&gt;
accel = slows it down like panning (off = fast 0 - 100 slower = on)&lt;br /&gt;
&lt;br /&gt;
max = the greater the number the more down it will tilt forward&lt;br /&gt;
&lt;br /&gt;
min = the lesser the number the more up it will tilt back to reverse direction swap min and max&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Tips from Olli:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1) In the tools menu, find the option &amp;quot;Get Current Motor Directions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
2) In the tools menu, find a option &amp;quot;Get Current Motor Positions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
3) Step 2 doesn&#039;t work for the yaw axis, for the obvious reason that there is nothing such as &amp;quot;levelled&amp;quot; for the yaw axis. As a second consequence the &amp;quot;yaw offset&amp;quot; parameter doesn&#039;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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;On the Functions tab:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
pan = follow = the camera follows slowly the orientation of the gimbal frame&lt;br /&gt;
hold = locked = the camera stays put with a fixed orientation&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Let&#039;s consider a generic example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Pan Mode Control = Aux-01 press&lt;br /&gt;
&lt;br /&gt;
Pan Mode Default Setting = hold hold pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #1 = hold hold hold&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #2 = pan pan pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #3 = pan hold pan&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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&#039;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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=917</id>
		<title>GUI (o323BGCTool) FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=917"/>
		<updated>2014-04-12T12:47:30Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;General comments:&#039;&#039;&#039;&lt;br /&gt;
* The AUX, BUT, and POT ports are only active if the [Gimbal Configuration] parameter is set to &amp;quot;hand held&amp;quot;.&lt;br /&gt;
* Any parameter with a &amp;quot;(na)&amp;quot; in its name is not active, i.e., doesn&#039;t do anything. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Functions:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Standby---But press (Hold button and standby is on. Release the button and standby is off)&lt;br /&gt;
&lt;br /&gt;
Standby---But push (Press button and standby is on. Press the button again and standby is off)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;RC Inputs tab - RC Mode Definitions:&#039;&#039;&#039;&lt;br /&gt;
Relative = stays where you placed it via joystick&lt;br /&gt;
Absolute = follows the stick position, returns to level when joystick released&lt;br /&gt;
speed = limits maximal speed of tilts&lt;br /&gt;
accel = slows it down like panning (off = fast 0 - 100 slower = on)&lt;br /&gt;
max = the greater the number the more down it will tilt forward&lt;br /&gt;
min = the lesser the number the more up it will tilt back&lt;br /&gt;
to reverse direction swap min and max&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Tips from Olli:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1) In the tools menu, find the option &amp;quot;Get Current Motor Directions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
2) In the tools menu, find a option &amp;quot;Get Current Motor Positions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
3) Step 2 doesn&#039;t work for the yaw axis, for the obvious reason that there is nothing such as &amp;quot;levelled&amp;quot; for the yaw axis. As a second consequence the &amp;quot;yaw offset&amp;quot; parameter doesn&#039;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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;On the Functions tab:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
pan = follow = the camera follows slowly the orientation of the gimbal frame&lt;br /&gt;
hold = locked = the camera stays put with a fixed orientation&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Let&#039;s consider a generic example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Pan Mode Control = Aux-01 press&lt;br /&gt;
&lt;br /&gt;
Pan Mode Default Setting = hold hold pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #1 = hold hold hold&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #2 = pan pan pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #3 = pan hold pan&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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&#039;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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=How_to_install_and_use_a_joystick&amp;diff=916</id>
		<title>How to install and use a joystick</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=How_to_install_and_use_a_joystick&amp;diff=916"/>
		<updated>2014-04-12T12:45:23Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;This joystick solution is from irun4fundotca.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here&#039;s my joystick solution that wont break the bank (about $5-10usd). First off, its installed on a makeshift mount until I find a better one, due to selling my last one in frustration. It&#039;s a joystick sold on ebay for about $3.59usd with free shipping and comes with locking Molex. All that&#039;s needed is some wire, 3pin locking Molex housings, a 1-row 5-pin female Dupont header (to connect to POT pins GND,POT0,POT1,POT2,VCC).&lt;br /&gt;
&lt;br /&gt;
All power on the joystick&#039;s ports is shared, so only one ground and vcc is needed. The other 3 wires provide the X(Roll- POT0), Y(Pitch-POT1), Z(button-POT2) signal.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Here&#039;s my connection drawing to make it simple using roll instead of pan as I don&#039;t have it connected on this one.&lt;br /&gt;
&lt;br /&gt;
[http://www.rcgroups.com/forums/showpost.php?p=28055684&amp;amp;postcount=358 Joystick Solution Details]&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=How_to_install_and_use_a_joystick&amp;diff=915</id>
		<title>How to install and use a joystick</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=How_to_install_and_use_a_joystick&amp;diff=915"/>
		<updated>2014-04-12T12:43:53Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;This joystick solution is from irun4fundotca.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here&#039;s my joystick solution that wont break the bank (about $5-10usd). First off, its installed on a makeshift mount until I find a better one, due to selling my last one in frustration. It&#039;s a joystick sold on ebay for about $3.59usd with free shipping and comes with locking Molex. All that&#039;s needed is some wire, 3pin locking Molex housings, a 1-row 5-pin female Dupont header (to connect to POT pins GND,POT0,POT1,POT2,VCC).&lt;br /&gt;
&lt;br /&gt;
All power on the joystick&#039;s ports is shared, so only one ground and vcc is needed. The other 3 wires provide the X(Roll- POT0), Y(Pitch-POT1), Z(button-POT2) signal.&lt;br /&gt;
 &lt;br /&gt;
Here&#039;s my connection drawing to make it simple using roll instead of pan as I don&#039;t have it connected on this one.&lt;br /&gt;
&lt;br /&gt;
[http://www.rcgroups.com/forums/showpost.php?p=28055684&amp;amp;postcount=358 Joystick Solution Details]&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=How_to_install_and_use_a_joystick&amp;diff=914</id>
		<title>How to install and use a joystick</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=How_to_install_and_use_a_joystick&amp;diff=914"/>
		<updated>2014-04-12T12:42:47Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;This joystick solution is from irun4fundotca.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here&#039;s my joystick solution that wont break the bank (about $5-10usd). First off, its installed on a makeshift mount until I find a better one, due to selling my last one in frustration. It&#039;s a joystick sold on ebay for about $3.59usd with free shipping and comes with locking Molex. All that&#039;s needed is some wire, 3pin locking Molex housings, a 1-row 5-pin female Dupont header (to connect to POT pins GND,POT0,POT1,POT2,VCC).&lt;br /&gt;
&lt;br /&gt;
All power on the joystick&#039;s ports is shared, so only one ground and vcc is needed. The other 3 wires provide the X(Roll- POT0), Y(Pitch-POT1), Z(button-POT2) signal.&lt;br /&gt;
 &lt;br /&gt;
Here&#039;s my connection drawing to make it simple using roll instead of pan as I don&#039;t have it connected on this one.&lt;br /&gt;
[http://www.rcgroups.com/forums/showpost.php?p=28055684&amp;amp;postcount=358 Joystick]&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=How_to_install_and_use_a_joystick&amp;diff=913</id>
		<title>How to install and use a joystick</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=How_to_install_and_use_a_joystick&amp;diff=913"/>
		<updated>2014-04-12T12:31:25Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: Created page with &amp;quot;&amp;#039;&amp;#039;&amp;#039;This joystick solution is from irun4fundotca.&amp;#039;&amp;#039;&amp;#039;  Here&amp;#039;s my joystick solution that wont break the bank (about $5-10usd). First off, its installed on a makeshift mount until...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;This joystick solution is from irun4fundotca.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here&#039;s my joystick solution that wont break the bank (about $5-10usd). First off, its installed on a makeshift mount until I find a better one, due to selling my last one in frustration. It&#039;s a joystick sold on ebay for about $3.59usd with free shipping and comes with locking Molex. All that&#039;s needed is some wire, 3pin locking Molex housings, a 1-row 5-pin female Dupont header (to connect to POT pins GND,POT0,POT1,POT2,VCC).&lt;br /&gt;
&lt;br /&gt;
All power on the joystick&#039;s ports is shared, so only one ground and vcc is needed. The other 3 wires provide the X(Roll- POT0), Y(Pitch-POT1), Z(button-POT2) signal.&lt;br /&gt;
 &lt;br /&gt;
Here&#039;s my connection drawing to make it simple using roll instead of pan as I don&#039;t have it connected on this one.&lt;br /&gt;
[[File:Example.jpg]]&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=883</id>
		<title>GUI (o323BGCTool) FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=883"/>
		<updated>2014-04-08T23:04:10Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Functions:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Standby---But press (Hold button and standby is on. Release the button and standby is off)&lt;br /&gt;
&lt;br /&gt;
Standby---But push (Press button and standby is on. Press the button again and standby is off)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Tips from Olli:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1) In the tools menu, find the option &amp;quot;Get Current Motor Directions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
2) In the tools menu, find a option &amp;quot;Get Current Motor Positions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
3) Step 2 doesn&#039;t work for the yaw axis, for the obvious reason that there is nothing such as &amp;quot;levelled&amp;quot; for the yaw axis. As a second consequence the &amp;quot;yaw offset&amp;quot; parameter doesn&#039;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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;On the Functions tab:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
pan = follow = the camera follows slowly the orientation of the gimbal frame&lt;br /&gt;
hold = locked = the camera stays put with a fixed orientation&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Let&#039;s consider a generic example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Pan Mode Control = Aux-01 press&lt;br /&gt;
&lt;br /&gt;
Pan Mode Default Setting = hold hold pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #1 = hold hold hold&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #2 = pan pan pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #3 = pan hold pan&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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&#039;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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=882</id>
		<title>GUI (o323BGCTool) FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=882"/>
		<updated>2014-04-08T23:03:49Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Functions:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Standby---But press (Hold button and standby is on. Release the button and standby is off)&lt;br /&gt;
&lt;br /&gt;
Standby---But push (Press button and standby is on. Press the button again and standby is off)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tips from Olli:&lt;br /&gt;
&lt;br /&gt;
1) In the tools menu, find the option &amp;quot;Get Current Motor Directions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
2) In the tools menu, find a option &amp;quot;Get Current Motor Positions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
3) Step 2 doesn&#039;t work for the yaw axis, for the obvious reason that there is nothing such as &amp;quot;levelled&amp;quot; for the yaw axis. As a second consequence the &amp;quot;yaw offset&amp;quot; parameter doesn&#039;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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;On the Functions tab:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
pan = follow = the camera follows slowly the orientation of the gimbal frame&lt;br /&gt;
hold = locked = the camera stays put with a fixed orientation&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Let&#039;s consider a generic example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Pan Mode Control = Aux-01 press&lt;br /&gt;
&lt;br /&gt;
Pan Mode Default Setting = hold hold pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #1 = hold hold hold&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #2 = pan pan pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #3 = pan hold pan&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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&#039;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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=881</id>
		<title>GUI (o323BGCTool) FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=881"/>
		<updated>2014-04-08T23:03:34Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Functions:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Standby---But press (Hold button and standby is on. Release the button and standby is off)&lt;br /&gt;
&lt;br /&gt;
Standby---But push (Press button and standby is on. Press the button again and standby is off)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tips from Olli:&lt;br /&gt;
&lt;br /&gt;
1) In the tools menu, find the option &amp;quot;Get Current Motor Directions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
2) In the tools menu, find a option &amp;quot;Get Current Motor Positions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
3) Step 2 doesn&#039;t work for the yaw axis, for the obvious reason that there is nothing such as &amp;quot;levelled&amp;quot; for the yaw axis. As a second consequence the &amp;quot;yaw offset&amp;quot; parameter doesn&#039;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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;On the Functions tab:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
pan = follow = the camera follows slowly the orientation of the gimbal frame&lt;br /&gt;
hold = locked = the camera stays put with a fixed orientation&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Let&#039;s consider a generic example:&#039;&#039;&#039;&lt;br /&gt;
Pan Mode Control = Aux-01 press&lt;br /&gt;
&lt;br /&gt;
Pan Mode Default Setting = hold hold pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #1 = hold hold hold&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #2 = pan pan pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #3 = pan hold pan&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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&#039;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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=880</id>
		<title>GUI (o323BGCTool) FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=880"/>
		<updated>2014-04-08T23:03:19Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Functions:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Standby---But press (Hold button and standby is on. Release the button and standby is off)&lt;br /&gt;
&lt;br /&gt;
Standby---But push (Press button and standby is on. Press the button again and standby is off)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tips from Olli:&lt;br /&gt;
&lt;br /&gt;
1) In the tools menu, find the option &amp;quot;Get Current Motor Directions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
2) In the tools menu, find a option &amp;quot;Get Current Motor Positions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
3) Step 2 doesn&#039;t work for the yaw axis, for the obvious reason that there is nothing such as &amp;quot;levelled&amp;quot; for the yaw axis. As a second consequence the &amp;quot;yaw offset&amp;quot; parameter doesn&#039;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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;On the Functions tab:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
pan = follow = the camera follows slowly the orientation of the gimbal frame&lt;br /&gt;
hold = locked = the camera stays put with a fixed orientation&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Let&#039;s consider a generic example:&#039;&#039;&#039;&lt;br /&gt;
Pan Mode Control = Aux-01 press&lt;br /&gt;
&lt;br /&gt;
Pan Mode Default Setting = hold hold pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #1 = hold hold hold&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #2 = pan pan pan&lt;br /&gt;
&lt;br /&gt;
Pan Mode Setting #3 = pan hold pan&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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&#039;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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=879</id>
		<title>GUI (o323BGCTool) FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=879"/>
		<updated>2014-04-08T23:02:44Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Functions:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Standby---But press (Hold button and standby is on. Release the button and standby is off)&lt;br /&gt;
&lt;br /&gt;
Standby---But push (Press button and standby is on. Press the button again and standby is off)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tips from Olli:&lt;br /&gt;
&lt;br /&gt;
1) In the tools menu, find the option &amp;quot;Get Current Motor Directions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
2) In the tools menu, find a option &amp;quot;Get Current Motor Positions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
3) Step 2 doesn&#039;t work for the yaw axis, for the obvious reason that there is nothing such as &amp;quot;levelled&amp;quot; for the yaw axis. As a second consequence the &amp;quot;yaw offset&amp;quot; parameter doesn&#039;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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;On the Functions tab:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
pan = follow = the camera follows slowly the orientation of the gimbal frame&lt;br /&gt;
hold = locked = the camera stays put with a fixed orientation&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Let&#039;s consider a generic example:&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;nowiki&amp;gt;Pan Mode Control = Aux-01 press&lt;br /&gt;
Pan Mode Default Setting = hold hold pan&lt;br /&gt;
Pan Mode Setting #1 = hold hold hold&lt;br /&gt;
Pan Mode Setting #2 = pan pan pan&lt;br /&gt;
Pan Mode Setting #3 = pan hold pan&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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&#039;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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=878</id>
		<title>GUI (o323BGCTool) FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=878"/>
		<updated>2014-04-08T23:01:09Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Functions:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Standby---But press (Hold button and standby is on. Release the button and standby is off)&lt;br /&gt;
&lt;br /&gt;
Standby---But push (Press button and standby is on. Press the button again and standby is off)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tips from Olli:&lt;br /&gt;
&lt;br /&gt;
1) In the tools menu, find the option &amp;quot;Get Current Motor Directions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
2) In the tools menu, find a option &amp;quot;Get Current Motor Positions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
3) Step 2 doesn&#039;t work for the yaw axis, for the obvious reason that there is nothing such as &amp;quot;levelled&amp;quot; for the yaw axis. As a second consequence the &amp;quot;yaw offset&amp;quot; parameter doesn&#039;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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;On the Functions tab:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
pan = follow = the camera follows slowly the orientation of the gimbal frame&lt;br /&gt;
hold = locked = the camera stays put with a fixed orientation&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Let&#039;s consider a generic example:&#039;&#039;&#039;&lt;br /&gt;
Pan Mode Control = Aux-01 press&lt;br /&gt;
Pan Mode Default Setting = hold hold pan&lt;br /&gt;
Pan Mode Setting #1 = hold hold hold&lt;br /&gt;
Pan Mode Setting #2 = pan pan pan&lt;br /&gt;
Pan Mode Setting #3 = pan hold pan&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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&#039;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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=874</id>
		<title>GUI (o323BGCTool) FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v2-wiki/index.php?title=GUI_(o323BGCTool)_FAQ&amp;diff=874"/>
		<updated>2014-04-06T14:19:15Z</updated>

		<summary type="html">&lt;p&gt;Greg Covey: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Functions:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Standby---But press (Hold button and standby is on. Release the button and standby is off)&lt;br /&gt;
&lt;br /&gt;
Standby---But push (Press button and standby is on. Press the button again and standby is off)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tips from Olli:&lt;br /&gt;
&lt;br /&gt;
1) In the tools menu, find the option &amp;quot;Get Current Motor Directions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
2) In the tools menu, find a option &amp;quot;Get Current Motor Positions&amp;quot;. Once your gimbal has reached the state &amp;quot;Normal&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
3) Step 2 doesn&#039;t work for the yaw axis, for the obvious reason that there is nothing such as &amp;quot;levelled&amp;quot; for the yaw axis. As a second consequence the &amp;quot;yaw offset&amp;quot; parameter doesn&#039;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.&lt;/div&gt;</summary>
		<author><name>Greg Covey</name></author>
	</entry>
</feed>