STorM32-Link: Difference between revisions
No edit summary |
No edit summary |
||
Line 5: | Line 5: | ||
The primary goal of the STorM32-Link is too overcome two general and hard-to-tackle issues with 3-axis gimbals, namely the drifting of the yaw axis in the hold mode and the tilting of the horizon in high-g flight maneuvers. The respective mechanisms are called '''''Yaw Drift Compensation''''' and '''''Horizon Drift Compensation''''', and both are available for T-STorM32 gimbals since firmware v2.35e, as demonstrated by the videos below. However, the STorM32-Link can also be used to achieve other innovative features in the future, such as novel yaw pan modes or automatic recalibration at startup. | The primary goal of the STorM32-Link is too overcome two general and hard-to-tackle issues with 3-axis gimbals, namely the drifting of the yaw axis in the hold mode and the tilting of the horizon in high-g flight maneuvers. The respective mechanisms are called '''''Yaw Drift Compensation''''' and '''''Horizon Drift Compensation''''', and both are available for T-STorM32 gimbals since firmware v2.35e, as demonstrated by the videos below. However, the STorM32-Link can also be used to achieve other innovative features in the future, such as novel yaw pan modes or automatic recalibration at startup. | ||
The same physical connection used for the STorM32-Link is also used for exchanging the conventional serial commands, for controlling e.g. the tilt and pan of the camera, described in the articles [[Serial Communication]] | The same physical connection used for the STorM32-Link is also used for exchanging the conventional serial commands, for controlling e.g. the tilt and pan of the camera, described in the articles [[Serial Communication]] and [[Uavcan]]. However, although the same bus is shared, this communication must not be considered part of the STorM32-Link (it's like TCP and UDP, they both share the same physical connection, but TCP is not UDP and vice versa). | ||
A comment on its history, and why STorM32-Link is a T-STorM32 feature: The STorM32-Link has probably the most colorful development history. Originally conceived early 2015, at a time when neither BaseCam/AlexMos nor Greemsy had such a feature, it never really took off besides being partially available since then (see [http://www.rcgroups.com/forums/showthread.php?t=2395475 STorM32-Link]). The game changed with the introduction of T-STorM32 in early 2017, since the more accurate data on the gimbal joint angles available with the encoders help significantly in implementing the goals. And | A comment on its history, and why STorM32-Link is a T-STorM32 feature: The STorM32-Link has probably the most colorful development history. Originally conceived early 2015, at a time when neither BaseCam/AlexMos nor Greemsy had such a feature, it never really took off besides being partially available since then (see [http://www.rcgroups.com/forums/showthread.php?t=2395475 STorM32-Link]). The game changed with the introduction of T-STorM32 in early 2017, since the more accurate data on the gimbal joint angles available with the encoders help significantly in implementing the goals. And that's why the STorM32-Link features have been made available only for T-STorM32. | ||
{{#ev:youtube|l8rz78kDWNY|480}} | {{#ev:youtube|l8rz78kDWNY|480}} | ||
{{#ev:youtube|z03PkDf0R-0|480}} | {{#ev:youtube|z03PkDf0R-0|480}} |
Revision as of 06:06, 9 May 2018
The information on this page refers to firmware v2.35e and higher.
The STorM32-Link refers to a communication link between the STorM32 gimbal controller and a drone's flight controller, in order to achieve advanced functions which otherwise would not be possible.
The primary goal of the STorM32-Link is too overcome two general and hard-to-tackle issues with 3-axis gimbals, namely the drifting of the yaw axis in the hold mode and the tilting of the horizon in high-g flight maneuvers. The respective mechanisms are called Yaw Drift Compensation and Horizon Drift Compensation, and both are available for T-STorM32 gimbals since firmware v2.35e, as demonstrated by the videos below. However, the STorM32-Link can also be used to achieve other innovative features in the future, such as novel yaw pan modes or automatic recalibration at startup.
The same physical connection used for the STorM32-Link is also used for exchanging the conventional serial commands, for controlling e.g. the tilt and pan of the camera, described in the articles Serial Communication and Uavcan. However, although the same bus is shared, this communication must not be considered part of the STorM32-Link (it's like TCP and UDP, they both share the same physical connection, but TCP is not UDP and vice versa).
A comment on its history, and why STorM32-Link is a T-STorM32 feature: The STorM32-Link has probably the most colorful development history. Originally conceived early 2015, at a time when neither BaseCam/AlexMos nor Greemsy had such a feature, it never really took off besides being partially available since then (see STorM32-Link). The game changed with the introduction of T-STorM32 in early 2017, since the more accurate data on the gimbal joint angles available with the encoders help significantly in implementing the goals. And that's why the STorM32-Link features have been made available only for T-STorM32.