<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://www.olliw.eu/storm32bgc-v1-wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Larsm</id>
	<title>STorM32-BGC Wiki V1 - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://www.olliw.eu/storm32bgc-v1-wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Larsm"/>
	<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v1-wiki/Special:Contributions/Larsm"/>
	<updated>2026-04-28T21:40:02Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.3</generator>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1507</id>
		<title>STorM32 FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1507"/>
		<updated>2014-10-23T11:28:55Z</updated>

		<summary type="html">&lt;p&gt;Larsm: /* Where should the main board be mounted for correct use of the second IMU? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Electronics ==&lt;br /&gt;
&lt;br /&gt;
==== What connectors are used for connecting the MPU modules to the board? ====&lt;br /&gt;
&lt;br /&gt;
The connectors for the MPU modules on the STorM32bgc board are [http://www.molex.com/molex/products/family?key=picoblade&amp;amp;channel=products&amp;amp;chanName=family&amp;amp;pageTitle=Introduction Molex picoblade] types with 1.25 mm pitch (for a comparison of various connectors see [http://www.rcgroups.com/forums/showthread.php?t=1493712 here]). They are also known as micro JST 1.25 mm, and it is in fact best to search for this, e.g. on ebay: [http://www.ebay.com/sch/i.html?_trksid=p2050601.m570.l1313.TR0.TRC0.H0.Xmicro+jst+1.25&amp;amp;_nkw=micro+jst+1.25&amp;amp;_sacat=0&amp;amp;_from=R40 micro jst 1.25].&lt;br /&gt;
&lt;br /&gt;
==== What about the magnetometer support? ====&lt;br /&gt;
&lt;br /&gt;
In version 0.51.2e magnetometer is not jet supported: http://www.rcgroups.com/forums/showpost.php?p=29756073&amp;amp;postcount=2062&lt;br /&gt;
If a mag-imu is connected as main imu on the camera, mag will not be detected:&lt;br /&gt;
&lt;br /&gt;
v... v0.51&lt;br /&gt;
&lt;br /&gt;
s... ok&lt;br /&gt;
&lt;br /&gt;
IMU is PRESENT @ LOW ADR&lt;br /&gt;
&lt;br /&gt;
IMU2 is PRESENT @ LOW ADR = external IMU&lt;br /&gt;
&lt;br /&gt;
MAG is not available&lt;br /&gt;
&lt;br /&gt;
STATE is NORMAL&lt;br /&gt;
&lt;br /&gt;
== Software and GUI ==&lt;br /&gt;
&lt;br /&gt;
==== Storing the parameter values to the EEPROM doesn&#039;t seem to work ====&lt;br /&gt;
&lt;br /&gt;
Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.&lt;br /&gt;
&lt;br /&gt;
==== Which drivers are needed for the USB? ====&lt;br /&gt;
&lt;br /&gt;
On Win7 the driver is usually installed automatically (this may take few minutes, be patient). The driver, usable also for WinXP, can also be obtained from [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here].&lt;br /&gt;
&lt;br /&gt;
==== Flashing with the usb-ttl adapter produces Windows error messages ====&lt;br /&gt;
&lt;br /&gt;
If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you&#039;re not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.&lt;br /&gt;
&lt;br /&gt;
== Gimbal Construction ==&lt;br /&gt;
&lt;br /&gt;
==== Does it matter where to install the camera IMU sensor? ====&lt;br /&gt;
&lt;br /&gt;
In principle no, one can mount it wherever it is most convenient (of course as long as it tracks the camera motion). Some folks have however reported that the performance can depend on where the IMU sensor is mounted, depending on the specific gimbal some places seem to be better, i.e. allow e.g high PID values, than others. So, it may need experimenting.&lt;br /&gt;
&lt;br /&gt;
==== Where should the main board be mounted for correct use of the second IMU? ====&lt;br /&gt;
&lt;br /&gt;
The second imu must be mounted on the &amp;quot;gimbal support&amp;quot; above the yaw motor so it is not moved by any of the motors. It must not be mounted on one of the axis&#039;s. So you can either mount the gimbal mainboard above the yaw motor using the onboard imu, or put the mainboard somewhere else (on yaw axis for example) and mount an external imu2 above the yaw motor.&lt;br /&gt;
&lt;br /&gt;
The onboard mpu6050 imu is connected to the imu2 connector internally and is set to a non default i2c adress. If you connect an external imu to imu2 connector it can be recognised by its default i2c adress. So you don&#039;t have to change anything in gui, external imu is used automatically when connected.&lt;br /&gt;
&lt;br /&gt;
Activate imu2 in Gimbal Setup -&amp;gt; Imu2 configuration:&lt;br /&gt;
* &amp;quot;gimbal support&amp;quot;: activate imu2 above the yaw motor.&lt;br /&gt;
* &amp;quot;gimbal support xy&amp;quot;: activate imu2 above the yaw motor rotated by 45°.&lt;br /&gt;
* &amp;quot;yaw bracket&amp;quot;, &amp;quot;yaw bracket xy&amp;quot;: do not use it, it iy buggy. (not availible in 0.51.2e)&lt;br /&gt;
&lt;br /&gt;
The calibration of imu2 works similar to the main imu.&lt;br /&gt;
&lt;br /&gt;
http://static.rcgroups.net/forums/attachments/1/4/2/1/a7119019-20-stom32-bgc-2nd-imu-configurations-01.jpg&lt;/div&gt;</summary>
		<author><name>Larsm</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1506</id>
		<title>STorM32 FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1506"/>
		<updated>2014-10-23T11:27:45Z</updated>

		<summary type="html">&lt;p&gt;Larsm: /* What about the magnetometer support? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Electronics ==&lt;br /&gt;
&lt;br /&gt;
==== What connectors are used for connecting the MPU modules to the board? ====&lt;br /&gt;
&lt;br /&gt;
The connectors for the MPU modules on the STorM32bgc board are [http://www.molex.com/molex/products/family?key=picoblade&amp;amp;channel=products&amp;amp;chanName=family&amp;amp;pageTitle=Introduction Molex picoblade] types with 1.25 mm pitch (for a comparison of various connectors see [http://www.rcgroups.com/forums/showthread.php?t=1493712 here]). They are also known as micro JST 1.25 mm, and it is in fact best to search for this, e.g. on ebay: [http://www.ebay.com/sch/i.html?_trksid=p2050601.m570.l1313.TR0.TRC0.H0.Xmicro+jst+1.25&amp;amp;_nkw=micro+jst+1.25&amp;amp;_sacat=0&amp;amp;_from=R40 micro jst 1.25].&lt;br /&gt;
&lt;br /&gt;
==== What about the magnetometer support? ====&lt;br /&gt;
&lt;br /&gt;
In version 0.51.2e magnetometer is not jet supported: http://www.rcgroups.com/forums/showpost.php?p=29756073&amp;amp;postcount=2062&lt;br /&gt;
If a mag-imu is connected as main imu on the camera, mag will not be detected:&lt;br /&gt;
&lt;br /&gt;
v... v0.51&lt;br /&gt;
&lt;br /&gt;
s... ok&lt;br /&gt;
&lt;br /&gt;
IMU is PRESENT @ LOW ADR&lt;br /&gt;
&lt;br /&gt;
IMU2 is PRESENT @ LOW ADR = external IMU&lt;br /&gt;
&lt;br /&gt;
MAG is not available&lt;br /&gt;
&lt;br /&gt;
STATE is NORMAL&lt;br /&gt;
&lt;br /&gt;
== Software and GUI ==&lt;br /&gt;
&lt;br /&gt;
==== Storing the parameter values to the EEPROM doesn&#039;t seem to work ====&lt;br /&gt;
&lt;br /&gt;
Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.&lt;br /&gt;
&lt;br /&gt;
==== Which drivers are needed for the USB? ====&lt;br /&gt;
&lt;br /&gt;
On Win7 the driver is usually installed automatically (this may take few minutes, be patient). The driver, usable also for WinXP, can also be obtained from [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here].&lt;br /&gt;
&lt;br /&gt;
==== Flashing with the usb-ttl adapter produces Windows error messages ====&lt;br /&gt;
&lt;br /&gt;
If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you&#039;re not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.&lt;br /&gt;
&lt;br /&gt;
== Gimbal Construction ==&lt;br /&gt;
&lt;br /&gt;
==== Does it matter where to install the camera IMU sensor? ====&lt;br /&gt;
&lt;br /&gt;
In principle no, one can mount it wherever it is most convenient (of course as long as it tracks the camera motion). Some folks have however reported that the performance can depend on where the IMU sensor is mounted, depending on the specific gimbal some places seem to be better, i.e. allow e.g high PID values, than others. So, it may need experimenting.&lt;br /&gt;
&lt;br /&gt;
==== Where should the main board be mounted for correct use of the second IMU? ====&lt;br /&gt;
&lt;br /&gt;
The second imu must be mounted on the &amp;quot;gimbal support&amp;quot; above the yaw motor so it is not moved by any of the motors. It must not be mounted on one of the axis&#039;s. So you can either mount the gimbal mainboard above the yaw motor using the onboard imu, or put the mainboard somewhere else (on yaw axis for example) and mount an external imu2 above the yaw motor.&lt;br /&gt;
&lt;br /&gt;
The onboard mpu6050 imu is connected to the imu2 connector internally and is set to a non default i2c adress. If you connect an external imu to imu2 connector it can be recognised by its default i2c adress. So you don&#039;t have to change anything in gui, external imu is used automatically when connected.&lt;br /&gt;
&lt;br /&gt;
Activate imu2 in Gimbal Setup -&amp;gt; Imu2 configuration:&lt;br /&gt;
&amp;quot;gimbal support&amp;quot;: activate imu2 above the yaw motor.&lt;br /&gt;
&amp;quot;gimbal support xy&amp;quot;: activate imu2 above the yaw motor rotated by 45°.&lt;br /&gt;
&amp;quot;yaw bracket&amp;quot;, &amp;quot;yaw bracket xy&amp;quot;: do not use it, it iy buggy.&lt;br /&gt;
&lt;br /&gt;
The calibration of imu2 works similar to the main imu.&lt;br /&gt;
&lt;br /&gt;
http://static.rcgroups.net/forums/attachments/1/4/2/1/a7119019-20-stom32-bgc-2nd-imu-configurations-01.jpg&lt;/div&gt;</summary>
		<author><name>Larsm</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1505</id>
		<title>STorM32 FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1505"/>
		<updated>2014-10-23T11:26:33Z</updated>

		<summary type="html">&lt;p&gt;Larsm: /* Electronics */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Electronics ==&lt;br /&gt;
&lt;br /&gt;
==== What connectors are used for connecting the MPU modules to the board? ====&lt;br /&gt;
&lt;br /&gt;
The connectors for the MPU modules on the STorM32bgc board are [http://www.molex.com/molex/products/family?key=picoblade&amp;amp;channel=products&amp;amp;chanName=family&amp;amp;pageTitle=Introduction Molex picoblade] types with 1.25 mm pitch (for a comparison of various connectors see [http://www.rcgroups.com/forums/showthread.php?t=1493712 here]). They are also known as micro JST 1.25 mm, and it is in fact best to search for this, e.g. on ebay: [http://www.ebay.com/sch/i.html?_trksid=p2050601.m570.l1313.TR0.TRC0.H0.Xmicro+jst+1.25&amp;amp;_nkw=micro+jst+1.25&amp;amp;_sacat=0&amp;amp;_from=R40 micro jst 1.25].&lt;br /&gt;
&lt;br /&gt;
==== What about the magnetometer support? ====&lt;br /&gt;
&lt;br /&gt;
In version 0.51.2e magnetometer is not jet supported: http://www.rcgroups.com/forums/showpost.php?p=29756073&amp;amp;postcount=2062&lt;br /&gt;
If a mag-imu is connected as main imu on the camera, mag will not be detected:&lt;br /&gt;
&lt;br /&gt;
v... v0.51&lt;br /&gt;
s... ok&lt;br /&gt;
IMU is PRESENT @ LOW ADR&lt;br /&gt;
IMU2 is PRESENT @ LOW ADR = external IMU&lt;br /&gt;
MAG is not available&lt;br /&gt;
STATE is NORMAL&lt;br /&gt;
&lt;br /&gt;
== Software and GUI ==&lt;br /&gt;
&lt;br /&gt;
==== Storing the parameter values to the EEPROM doesn&#039;t seem to work ====&lt;br /&gt;
&lt;br /&gt;
Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.&lt;br /&gt;
&lt;br /&gt;
==== Which drivers are needed for the USB? ====&lt;br /&gt;
&lt;br /&gt;
On Win7 the driver is usually installed automatically (this may take few minutes, be patient). The driver, usable also for WinXP, can also be obtained from [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here].&lt;br /&gt;
&lt;br /&gt;
==== Flashing with the usb-ttl adapter produces Windows error messages ====&lt;br /&gt;
&lt;br /&gt;
If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you&#039;re not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.&lt;br /&gt;
&lt;br /&gt;
== Gimbal Construction ==&lt;br /&gt;
&lt;br /&gt;
==== Does it matter where to install the camera IMU sensor? ====&lt;br /&gt;
&lt;br /&gt;
In principle no, one can mount it wherever it is most convenient (of course as long as it tracks the camera motion). Some folks have however reported that the performance can depend on where the IMU sensor is mounted, depending on the specific gimbal some places seem to be better, i.e. allow e.g high PID values, than others. So, it may need experimenting.&lt;br /&gt;
&lt;br /&gt;
==== Where should the main board be mounted for correct use of the second IMU? ====&lt;br /&gt;
&lt;br /&gt;
The second imu must be mounted on the &amp;quot;gimbal support&amp;quot; above the yaw motor so it is not moved by any of the motors. It must not be mounted on one of the axis&#039;s. So you can either mount the gimbal mainboard above the yaw motor using the onboard imu, or put the mainboard somewhere else (on yaw axis for example) and mount an external imu2 above the yaw motor.&lt;br /&gt;
&lt;br /&gt;
The onboard mpu6050 imu is connected to the imu2 connector internally and is set to a non default i2c adress. If you connect an external imu to imu2 connector it can be recognised by its default i2c adress. So you don&#039;t have to change anything in gui, external imu is used automatically when connected.&lt;br /&gt;
&lt;br /&gt;
Activate imu2 in Gimbal Setup -&amp;gt; Imu2 configuration:&lt;br /&gt;
&amp;quot;gimbal support&amp;quot;: activate imu2 above the yaw motor.&lt;br /&gt;
&amp;quot;gimbal support xy&amp;quot;: activate imu2 above the yaw motor rotated by 45°.&lt;br /&gt;
&amp;quot;yaw bracket&amp;quot;, &amp;quot;yaw bracket xy&amp;quot;: do not use it, it iy buggy.&lt;br /&gt;
&lt;br /&gt;
The calibration of imu2 works similar to the main imu.&lt;br /&gt;
&lt;br /&gt;
http://static.rcgroups.net/forums/attachments/1/4/2/1/a7119019-20-stom32-bgc-2nd-imu-configurations-01.jpg&lt;/div&gt;</summary>
		<author><name>Larsm</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1494</id>
		<title>STorM32 FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1494"/>
		<updated>2014-10-09T21:29:10Z</updated>

		<summary type="html">&lt;p&gt;Larsm: /* Where should the main board be mounted for correct use of the second IMU? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Electronics ==&lt;br /&gt;
&lt;br /&gt;
==== What connectors are used for connecting the MPU modules to the board? ====&lt;br /&gt;
&lt;br /&gt;
The connectors for the MPU modules on the STorM32bgc board are [http://www.molex.com/molex/products/family?key=picoblade&amp;amp;channel=products&amp;amp;chanName=family&amp;amp;pageTitle=Introduction Molex picoblade] types with 1.25 mm pitch (for a comparison of various connectors see [http://www.rcgroups.com/forums/showthread.php?t=1493712 here]). They are also known as micro JST 1.25 mm, and it is in fact best to search for this, e.g. on ebay: [http://www.ebay.com/sch/i.html?_trksid=p2050601.m570.l1313.TR0.TRC0.H0.Xmicro+jst+1.25&amp;amp;_nkw=micro+jst+1.25&amp;amp;_sacat=0&amp;amp;_from=R40 micro jst 1.25].&lt;br /&gt;
&lt;br /&gt;
== Software and GUI ==&lt;br /&gt;
&lt;br /&gt;
==== Storing the parameter values to the EEPROM doesn&#039;t seem to work ====&lt;br /&gt;
&lt;br /&gt;
Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.&lt;br /&gt;
&lt;br /&gt;
==== Which drivers are needed for the USB? ====&lt;br /&gt;
&lt;br /&gt;
On Win7 the driver is usually installed automatically (this may take few minutes, be patient). The driver, usable also for WinXP, can also be obtained from [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here].&lt;br /&gt;
&lt;br /&gt;
==== Flashing with the usb-ttl adapter produces Windows error messages ====&lt;br /&gt;
&lt;br /&gt;
If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you&#039;re not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.&lt;br /&gt;
&lt;br /&gt;
== Gimbal Construction ==&lt;br /&gt;
&lt;br /&gt;
==== Does it matter where to install the camera IMU sensor? ====&lt;br /&gt;
&lt;br /&gt;
In principle no, one can mount it wherever it is most convenient (of course as long as it tracks the camera motion). Some folks have however reported that the performance can depend on where the IMU sensor is mounted, depending on the specific gimbal some places seem to be better, i.e. allow e.g high PID values, than others. So, it may need experimenting.&lt;br /&gt;
&lt;br /&gt;
==== Where should the main board be mounted for correct use of the second IMU? ====&lt;br /&gt;
&lt;br /&gt;
The second imu must be mounted on the &amp;quot;gimbal support&amp;quot; above the yaw motor so it is not moved by any of the motors. It must not be mounted on one of the axis&#039;s. So you can either mount the gimbal mainboard above the yaw motor using the onboard imu, or put the mainboard somewhere else (on yaw axis for example) and mount an external imu2 above the yaw motor.&lt;br /&gt;
&lt;br /&gt;
The onboard mpu6050 imu is connected to the imu2 connector internally and is set to a non default i2c adress. If you connect an external imu to imu2 connector it can be recognised by its default i2c adress. So you don&#039;t have to change anything in gui, external imu is used automatically when connected.&lt;br /&gt;
&lt;br /&gt;
Activate imu2 in Gimbal Setup -&amp;gt; Imu2 configuration:&lt;br /&gt;
&amp;quot;gimbal support&amp;quot;: activate imu2 above the yaw motor.&lt;br /&gt;
&amp;quot;gimbal support xy&amp;quot;: activate imu2 above the yaw motor rotated by 45°.&lt;br /&gt;
&amp;quot;yaw bracket&amp;quot;, &amp;quot;yaw bracket xy&amp;quot;: do not use it, it iy buggy.&lt;br /&gt;
&lt;br /&gt;
The calibration of imu2 works similar to the main imu.&lt;br /&gt;
&lt;br /&gt;
http://static.rcgroups.net/forums/attachments/1/4/2/1/a7119019-20-stom32-bgc-2nd-imu-configurations-01.jpg&lt;/div&gt;</summary>
		<author><name>Larsm</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1493</id>
		<title>STorM32 FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1493"/>
		<updated>2014-10-09T21:24:34Z</updated>

		<summary type="html">&lt;p&gt;Larsm: /* Where should the main board be mounted for correct use of the second IMU? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Electronics ==&lt;br /&gt;
&lt;br /&gt;
==== What connectors are used for connecting the MPU modules to the board? ====&lt;br /&gt;
&lt;br /&gt;
The connectors for the MPU modules on the STorM32bgc board are [http://www.molex.com/molex/products/family?key=picoblade&amp;amp;channel=products&amp;amp;chanName=family&amp;amp;pageTitle=Introduction Molex picoblade] types with 1.25 mm pitch (for a comparison of various connectors see [http://www.rcgroups.com/forums/showthread.php?t=1493712 here]). They are also known as micro JST 1.25 mm, and it is in fact best to search for this, e.g. on ebay: [http://www.ebay.com/sch/i.html?_trksid=p2050601.m570.l1313.TR0.TRC0.H0.Xmicro+jst+1.25&amp;amp;_nkw=micro+jst+1.25&amp;amp;_sacat=0&amp;amp;_from=R40 micro jst 1.25].&lt;br /&gt;
&lt;br /&gt;
== Software and GUI ==&lt;br /&gt;
&lt;br /&gt;
==== Storing the parameter values to the EEPROM doesn&#039;t seem to work ====&lt;br /&gt;
&lt;br /&gt;
Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.&lt;br /&gt;
&lt;br /&gt;
==== Which drivers are needed for the USB? ====&lt;br /&gt;
&lt;br /&gt;
On Win7 the driver is usually installed automatically (this may take few minutes, be patient). The driver, usable also for WinXP, can also be obtained from [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here].&lt;br /&gt;
&lt;br /&gt;
==== Flashing with the usb-ttl adapter produces Windows error messages ====&lt;br /&gt;
&lt;br /&gt;
If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you&#039;re not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.&lt;br /&gt;
&lt;br /&gt;
== Gimbal Construction ==&lt;br /&gt;
&lt;br /&gt;
==== Does it matter where to install the camera IMU sensor? ====&lt;br /&gt;
&lt;br /&gt;
In principle no, one can mount it wherever it is most convenient (of course as long as it tracks the camera motion). Some folks have however reported that the performance can depend on where the IMU sensor is mounted, depending on the specific gimbal some places seem to be better, i.e. allow e.g high PID values, than others. So, it may need experimenting.&lt;br /&gt;
&lt;br /&gt;
==== Where should the main board be mounted for correct use of the second IMU? ====&lt;br /&gt;
&lt;br /&gt;
The second imu must be mounted on the &amp;quot;gimbal support&amp;quot; above the yaw motor so it is not moved by any of the motors. It must not be mounted on one of the axis&#039;s. So you can either mount the gimbal mainboard above the yaw motor using the onboard imu, or put the mainboard somewhere else (on yaw axis for example) and mount an external imu2 above the yaw motor.&lt;br /&gt;
&lt;br /&gt;
The onboard mpu6050 imu is connected to the imu2 connector internally and is set to a non default i2c adress. If you connect an external imu to imu2 connector it can be recognised by its default i2c adress. So you don&#039;t have to change anything in gui, external imu is used automatically.&lt;br /&gt;
&lt;br /&gt;
Activate imu2 in Gimbal Setup -&amp;gt; Imu2 configuration:&lt;br /&gt;
&amp;quot;gimbal support&amp;quot;: activate imu2 above the yaw motor.&lt;br /&gt;
&amp;quot;gimbal support xy&amp;quot;: activate imu2 above the yaw motor rotated by 45°.&lt;br /&gt;
&amp;quot;yaw bracket&amp;quot;, &amp;quot;yaw bracket xy&amp;quot;: do not use it, it iy buggy.&lt;br /&gt;
&lt;br /&gt;
The calibration of imu2 works similar to the main imu.&lt;br /&gt;
&lt;br /&gt;
http://static.rcgroups.net/forums/attachments/1/4/2/1/a7119019-20-stom32-bgc-2nd-imu-configurations-01.jpg&lt;/div&gt;</summary>
		<author><name>Larsm</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1492</id>
		<title>STorM32 FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1492"/>
		<updated>2014-10-09T19:33:26Z</updated>

		<summary type="html">&lt;p&gt;Larsm: /* Where should the main board be mounted for correct use of the second IMU? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Electronics ==&lt;br /&gt;
&lt;br /&gt;
==== What connectors are used for connecting the MPU modules to the board? ====&lt;br /&gt;
&lt;br /&gt;
The connectors for the MPU modules on the STorM32bgc board are [http://www.molex.com/molex/products/family?key=picoblade&amp;amp;channel=products&amp;amp;chanName=family&amp;amp;pageTitle=Introduction Molex picoblade] types with 1.25 mm pitch (for a comparison of various connectors see [http://www.rcgroups.com/forums/showthread.php?t=1493712 here]). They are also known as micro JST 1.25 mm, and it is in fact best to search for this, e.g. on ebay: [http://www.ebay.com/sch/i.html?_trksid=p2050601.m570.l1313.TR0.TRC0.H0.Xmicro+jst+1.25&amp;amp;_nkw=micro+jst+1.25&amp;amp;_sacat=0&amp;amp;_from=R40 micro jst 1.25].&lt;br /&gt;
&lt;br /&gt;
== Software and GUI ==&lt;br /&gt;
&lt;br /&gt;
==== Storing the parameter values to the EEPROM doesn&#039;t seem to work ====&lt;br /&gt;
&lt;br /&gt;
Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.&lt;br /&gt;
&lt;br /&gt;
==== Which drivers are needed for the USB? ====&lt;br /&gt;
&lt;br /&gt;
On Win7 the driver is usually installed automatically (this may take few minutes, be patient). The driver, usable also for WinXP, can also be obtained from [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here].&lt;br /&gt;
&lt;br /&gt;
==== Flashing with the usb-ttl adapter produces Windows error messages ====&lt;br /&gt;
&lt;br /&gt;
If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you&#039;re not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.&lt;br /&gt;
&lt;br /&gt;
== Gimbal Construction ==&lt;br /&gt;
&lt;br /&gt;
==== Does it matter where to install the camera IMU sensor? ====&lt;br /&gt;
&lt;br /&gt;
In principle no, one can mount it wherever it is most convenient (of course as long as it tracks the camera motion). Some folks have however reported that the performance can depend on where the IMU sensor is mounted, depending on the specific gimbal some places seem to be better, i.e. allow e.g high PID values, than others. So, it may need experimenting.&lt;br /&gt;
&lt;br /&gt;
==== Where should the main board be mounted for correct use of the second IMU? ====&lt;br /&gt;
&lt;br /&gt;
http://static.rcgroups.net/forums/attachments/1/4/2/1/a7119019-20-stom32-bgc-2nd-imu-configurations-01.jpg&lt;/div&gt;</summary>
		<author><name>Larsm</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1491</id>
		<title>STorM32 FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1491"/>
		<updated>2014-10-09T19:09:09Z</updated>

		<summary type="html">&lt;p&gt;Larsm: /* Where should the main board be mounted for correct use of the second IMU? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Electronics ==&lt;br /&gt;
&lt;br /&gt;
==== What connectors are used for connecting the MPU modules to the board? ====&lt;br /&gt;
&lt;br /&gt;
The connectors for the MPU modules on the STorM32bgc board are [http://www.molex.com/molex/products/family?key=picoblade&amp;amp;channel=products&amp;amp;chanName=family&amp;amp;pageTitle=Introduction Molex picoblade] types with 1.25 mm pitch (for a comparison of various connectors see [http://www.rcgroups.com/forums/showthread.php?t=1493712 here]). They are also known as micro JST 1.25 mm, and it is in fact best to search for this, e.g. on ebay: [http://www.ebay.com/sch/i.html?_trksid=p2050601.m570.l1313.TR0.TRC0.H0.Xmicro+jst+1.25&amp;amp;_nkw=micro+jst+1.25&amp;amp;_sacat=0&amp;amp;_from=R40 micro jst 1.25].&lt;br /&gt;
&lt;br /&gt;
== Software and GUI ==&lt;br /&gt;
&lt;br /&gt;
==== Storing the parameter values to the EEPROM doesn&#039;t seem to work ====&lt;br /&gt;
&lt;br /&gt;
Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.&lt;br /&gt;
&lt;br /&gt;
==== Which drivers are needed for the USB? ====&lt;br /&gt;
&lt;br /&gt;
On Win7 the driver is usually installed automatically (this may take few minutes, be patient). The driver, usable also for WinXP, can also be obtained from [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here].&lt;br /&gt;
&lt;br /&gt;
==== Flashing with the usb-ttl adapter produces Windows error messages ====&lt;br /&gt;
&lt;br /&gt;
If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you&#039;re not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.&lt;br /&gt;
&lt;br /&gt;
== Gimbal Construction ==&lt;br /&gt;
&lt;br /&gt;
==== Does it matter where to install the camera IMU sensor? ====&lt;br /&gt;
&lt;br /&gt;
In principle no, one can mount it wherever it is most convenient (of course as long as it tracks the camera motion). Some folks have however reported that the performance can depend on where the IMU sensor is mounted, depending on the specific gimbal some places seem to be better, i.e. allow e.g high PID values, than others. So, it may need experimenting.&lt;br /&gt;
&lt;br /&gt;
==== Where should the main board be mounted for correct use of the second IMU? ====&lt;br /&gt;
&lt;br /&gt;
An welchen Achsen darf und oder sollte die 2. Imu montiert werden? What about the axis orientation?&lt;br /&gt;
&lt;br /&gt;
Angenommen die 2. Imu wird nur ausserhalb des gimbals unterstützt: Was ist, wenn man das main board aus Platzgründen an der yaw Achse befestigt hat. Sollte man dann die onboard Imu deaktivieren?&lt;br /&gt;
&lt;br /&gt;
Angenommen die 2. Imu wird nur ausserhalb des gimbals unterstützt: Wenn man an den Imu2 Anschluss eine zweite externe Imu anschließt und die ausserhalb des Gimbals montiert, woher weiß das Gimbal dann welche es benutzen soll (onboard oder die am Imu2 Anschluss)?&lt;br /&gt;
&lt;br /&gt;
Was bedeuten die Einstellungen unter Gimbal Setup -&amp;gt; Imu2 configuration?&lt;br /&gt;
&lt;br /&gt;
Wo kommt dieses tolle Bild her? Vielleicht wird es ja dort erklährt? http://static.rcgroups.net/forums/attachments/1/4/2/1/a7119019-20-stom32-bgc-2nd-imu-configurations-01.jpg&lt;/div&gt;</summary>
		<author><name>Larsm</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1490</id>
		<title>STorM32 FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1490"/>
		<updated>2014-10-09T17:01:19Z</updated>

		<summary type="html">&lt;p&gt;Larsm: /* Where should the main board be mounted for correct use of the second IMU? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Electronics ==&lt;br /&gt;
&lt;br /&gt;
==== What connectors are used for connecting the MPU modules to the board? ====&lt;br /&gt;
&lt;br /&gt;
The connectors for the MPU modules on the STorM32bgc board are [http://www.molex.com/molex/products/family?key=picoblade&amp;amp;channel=products&amp;amp;chanName=family&amp;amp;pageTitle=Introduction Molex picoblade] types with 1.25 mm pitch (for a comparison of various connectors see [http://www.rcgroups.com/forums/showthread.php?t=1493712 here]). They are also known as micro JST 1.25 mm, and it is in fact best to search for this, e.g. on ebay: [http://www.ebay.com/sch/i.html?_trksid=p2050601.m570.l1313.TR0.TRC0.H0.Xmicro+jst+1.25&amp;amp;_nkw=micro+jst+1.25&amp;amp;_sacat=0&amp;amp;_from=R40 micro jst 1.25].&lt;br /&gt;
&lt;br /&gt;
== Software and GUI ==&lt;br /&gt;
&lt;br /&gt;
==== Storing the parameter values to the EEPROM doesn&#039;t seem to work ====&lt;br /&gt;
&lt;br /&gt;
Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.&lt;br /&gt;
&lt;br /&gt;
==== Which drivers are needed for the USB? ====&lt;br /&gt;
&lt;br /&gt;
On Win7 the driver is usually installed automatically (this may take few minutes, be patient). The driver, usable also for WinXP, can also be obtained from [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here].&lt;br /&gt;
&lt;br /&gt;
==== Flashing with the usb-ttl adapter produces Windows error messages ====&lt;br /&gt;
&lt;br /&gt;
If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you&#039;re not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.&lt;br /&gt;
&lt;br /&gt;
== Gimbal Construction ==&lt;br /&gt;
&lt;br /&gt;
==== Does it matter where to install the camera IMU sensor? ====&lt;br /&gt;
&lt;br /&gt;
In principle no, one can mount it wherever it is most convenient (of course as long as it tracks the camera motion). Some folks have however reported that the performance can depend on where the IMU sensor is mounted, depending on the specific gimbal some places seem to be better, i.e. allow e.g high PID values, than others. So, it may need experimenting.&lt;br /&gt;
&lt;br /&gt;
==== Where should the main board be mounted for correct use of the second IMU? ====&lt;br /&gt;
&lt;br /&gt;
An welchen Achsen darf und oder sollte die 2. Imu montiert werden? What about the axis orientation?&lt;br /&gt;
&lt;br /&gt;
Angenommen die 2. Imu wird nur ausserhalb des gimbals unterstützt: Was ist, wenn man das main board aus Platzgründen an der yaw Achse befestigt hat. Sollte man dann die onboard Imu deaktivieren?&lt;br /&gt;
&lt;br /&gt;
Angenommen die 2. Imu wird nur ausserhalb des gimbals unterstützt: Wenn man an den Imu2 Anschluss eine zweite externe Imu anschließt und die ausserhalb des Gimbals montiert, woher weiß das Gimbal dann welche es benutzen soll (onboard oder die am Imu2 Anschluss)?&lt;br /&gt;
&lt;br /&gt;
Was bedeuten die Einstellungen unter Gimbal Setup -&amp;gt; Imu2 configuration?&lt;/div&gt;</summary>
		<author><name>Larsm</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1489</id>
		<title>STorM32 FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1489"/>
		<updated>2014-10-09T16:57:57Z</updated>

		<summary type="html">&lt;p&gt;Larsm: /* Where should the main board be mounted for correct use of the onboard IMU? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Electronics ==&lt;br /&gt;
&lt;br /&gt;
==== What connectors are used for connecting the MPU modules to the board? ====&lt;br /&gt;
&lt;br /&gt;
The connectors for the MPU modules on the STorM32bgc board are [http://www.molex.com/molex/products/family?key=picoblade&amp;amp;channel=products&amp;amp;chanName=family&amp;amp;pageTitle=Introduction Molex picoblade] types with 1.25 mm pitch (for a comparison of various connectors see [http://www.rcgroups.com/forums/showthread.php?t=1493712 here]). They are also known as micro JST 1.25 mm, and it is in fact best to search for this, e.g. on ebay: [http://www.ebay.com/sch/i.html?_trksid=p2050601.m570.l1313.TR0.TRC0.H0.Xmicro+jst+1.25&amp;amp;_nkw=micro+jst+1.25&amp;amp;_sacat=0&amp;amp;_from=R40 micro jst 1.25].&lt;br /&gt;
&lt;br /&gt;
== Software and GUI ==&lt;br /&gt;
&lt;br /&gt;
==== Storing the parameter values to the EEPROM doesn&#039;t seem to work ====&lt;br /&gt;
&lt;br /&gt;
Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.&lt;br /&gt;
&lt;br /&gt;
==== Which drivers are needed for the USB? ====&lt;br /&gt;
&lt;br /&gt;
On Win7 the driver is usually installed automatically (this may take few minutes, be patient). The driver, usable also for WinXP, can also be obtained from [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here].&lt;br /&gt;
&lt;br /&gt;
==== Flashing with the usb-ttl adapter produces Windows error messages ====&lt;br /&gt;
&lt;br /&gt;
If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you&#039;re not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.&lt;br /&gt;
&lt;br /&gt;
== Gimbal Construction ==&lt;br /&gt;
&lt;br /&gt;
==== Does it matter where to install the camera IMU sensor? ====&lt;br /&gt;
&lt;br /&gt;
In principle no, one can mount it wherever it is most convenient (of course as long as it tracks the camera motion). Some folks have however reported that the performance can depend on where the IMU sensor is mounted, depending on the specific gimbal some places seem to be better, i.e. allow e.g high PID values, than others. So, it may need experimenting.&lt;br /&gt;
&lt;br /&gt;
==== Where should the main board be mounted for correct use of the second IMU? ====&lt;br /&gt;
&lt;br /&gt;
An welchen Achsen darf und oder sollte die 2. Imu montiert werden? What about the axis orientation?&lt;br /&gt;
&lt;br /&gt;
Angenommen die 2. Imu wird nur ausserhalb des gimbals unterstützt: Was ist, wenn man das main board aus Platzgründen an der yaw Achse befestigt hat. Sollte man dann die onboard Imu deaktivieren? Wenn, wie?&lt;br /&gt;
&lt;br /&gt;
Angenommen die 2. Imu wird nur ausserhalb des gimbals unterstützt: Wenn man an den Imu2 Anschluss eine zweite externe Imu anschließt und die ausserhalb des Gimbals montiert, woher weiß das Gimbal dann welche es benutzen soll (onboard oder die am Imu2 Anschluss)?&lt;/div&gt;</summary>
		<author><name>Larsm</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1488</id>
		<title>STorM32 FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1488"/>
		<updated>2014-10-09T16:57:37Z</updated>

		<summary type="html">&lt;p&gt;Larsm: /* Where should the main board be mounted for correct use of the onboard IMU? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Electronics ==&lt;br /&gt;
&lt;br /&gt;
==== What connectors are used for connecting the MPU modules to the board? ====&lt;br /&gt;
&lt;br /&gt;
The connectors for the MPU modules on the STorM32bgc board are [http://www.molex.com/molex/products/family?key=picoblade&amp;amp;channel=products&amp;amp;chanName=family&amp;amp;pageTitle=Introduction Molex picoblade] types with 1.25 mm pitch (for a comparison of various connectors see [http://www.rcgroups.com/forums/showthread.php?t=1493712 here]). They are also known as micro JST 1.25 mm, and it is in fact best to search for this, e.g. on ebay: [http://www.ebay.com/sch/i.html?_trksid=p2050601.m570.l1313.TR0.TRC0.H0.Xmicro+jst+1.25&amp;amp;_nkw=micro+jst+1.25&amp;amp;_sacat=0&amp;amp;_from=R40 micro jst 1.25].&lt;br /&gt;
&lt;br /&gt;
== Software and GUI ==&lt;br /&gt;
&lt;br /&gt;
==== Storing the parameter values to the EEPROM doesn&#039;t seem to work ====&lt;br /&gt;
&lt;br /&gt;
Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.&lt;br /&gt;
&lt;br /&gt;
==== Which drivers are needed for the USB? ====&lt;br /&gt;
&lt;br /&gt;
On Win7 the driver is usually installed automatically (this may take few minutes, be patient). The driver, usable also for WinXP, can also be obtained from [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here].&lt;br /&gt;
&lt;br /&gt;
==== Flashing with the usb-ttl adapter produces Windows error messages ====&lt;br /&gt;
&lt;br /&gt;
If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you&#039;re not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.&lt;br /&gt;
&lt;br /&gt;
== Gimbal Construction ==&lt;br /&gt;
&lt;br /&gt;
==== Does it matter where to install the camera IMU sensor? ====&lt;br /&gt;
&lt;br /&gt;
In principle no, one can mount it wherever it is most convenient (of course as long as it tracks the camera motion). Some folks have however reported that the performance can depend on where the IMU sensor is mounted, depending on the specific gimbal some places seem to be better, i.e. allow e.g high PID values, than others. So, it may need experimenting.&lt;br /&gt;
&lt;br /&gt;
==== Where should the main board be mounted for correct use of the onboard IMU? ====&lt;br /&gt;
&lt;br /&gt;
An welchen Achsen darf und oder sollte die 2. Imu montiert werden? What about the axis orientation?&lt;br /&gt;
&lt;br /&gt;
Angenommen die 2. Imu wird nur ausserhalb des gimbals unterstützt: Was ist, wenn man das main board aus Platzgründen an der yaw Achse befestigt hat. Sollte man dann die onboard Imu deaktivieren? Wenn, wie?&lt;br /&gt;
&lt;br /&gt;
Angenommen die 2. Imu wird nur ausserhalb des gimbals unterstützt: Wenn man an den Imu2 Anschluss eine zweite externe Imu anschließt und die ausserhalb des Gimbals montiert, woher weiß das Gimbal dann welche es benutzen soll (onboard oder die am Imu2 Anschluss)?&lt;/div&gt;</summary>
		<author><name>Larsm</name></author>
	</entry>
	<entry>
		<id>http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1487</id>
		<title>STorM32 FAQ</title>
		<link rel="alternate" type="text/html" href="http://www.olliw.eu/storm32bgc-v1-wiki/index.php?title=STorM32_FAQ&amp;diff=1487"/>
		<updated>2014-10-09T16:32:11Z</updated>

		<summary type="html">&lt;p&gt;Larsm: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Electronics ==&lt;br /&gt;
&lt;br /&gt;
==== What connectors are used for connecting the MPU modules to the board? ====&lt;br /&gt;
&lt;br /&gt;
The connectors for the MPU modules on the STorM32bgc board are [http://www.molex.com/molex/products/family?key=picoblade&amp;amp;channel=products&amp;amp;chanName=family&amp;amp;pageTitle=Introduction Molex picoblade] types with 1.25 mm pitch (for a comparison of various connectors see [http://www.rcgroups.com/forums/showthread.php?t=1493712 here]). They are also known as micro JST 1.25 mm, and it is in fact best to search for this, e.g. on ebay: [http://www.ebay.com/sch/i.html?_trksid=p2050601.m570.l1313.TR0.TRC0.H0.Xmicro+jst+1.25&amp;amp;_nkw=micro+jst+1.25&amp;amp;_sacat=0&amp;amp;_from=R40 micro jst 1.25].&lt;br /&gt;
&lt;br /&gt;
== Software and GUI ==&lt;br /&gt;
&lt;br /&gt;
==== Storing the parameter values to the EEPROM doesn&#039;t seem to work ====&lt;br /&gt;
&lt;br /&gt;
Please double-check that the correct firmware for your board has been flashed. The problem typically happens then e.g. the firmware for a F103RB is flashed onto a board with a F103RC.&lt;br /&gt;
&lt;br /&gt;
==== Which drivers are needed for the USB? ====&lt;br /&gt;
&lt;br /&gt;
On Win7 the driver is usually installed automatically (this may take few minutes, be patient). The driver, usable also for WinXP, can also be obtained from [http://www.st.com/web/en/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168 here].&lt;br /&gt;
&lt;br /&gt;
==== Flashing with the usb-ttl adapter produces Windows error messages ====&lt;br /&gt;
&lt;br /&gt;
If upon flashing you get Windows errors such as mfc110.dll is missing, msvcr110.dll is missing, or application was unable to start correctly (0xc000007b), then first check that you&#039;re not using an outdated GUI version. Otherwise, you need to install the VC++ runtime libraries. Download vcredist_x64.exe or vcredist_x86.exe depending on your Win system from [//www.microsoft.com/en-us/download/details.aspx?id=30679 here], and run the exe file.&lt;br /&gt;
&lt;br /&gt;
== Gimbal Construction ==&lt;br /&gt;
&lt;br /&gt;
==== Does it matter where to install the camera IMU sensor? ====&lt;br /&gt;
&lt;br /&gt;
In principle no, one can mount it wherever it is most convenient (of course as long as it tracks the camera motion). Some folks have however reported that the performance can depend on where the IMU sensor is mounted, depending on the specific gimbal some places seem to be better, i.e. allow e.g high PID values, than others. So, it may need experimenting.&lt;br /&gt;
&lt;br /&gt;
==== Where should the main board be mounted for correct use of the onboard IMU? ====&lt;br /&gt;
&lt;br /&gt;
On the yaw axis or outside of the gimbal? What about the axis orientation?&lt;/div&gt;</summary>
		<author><name>Larsm</name></author>
	</entry>
</feed>