STorM32-Link - Revision history

OlliW at 19:24, 20 January 2024

2024-01-20T19:24:59Z

← Older revision		Revision as of 21:24, 20 January 2024
Line 9:		Line 9:
	What this means is that these two aspects of the communication should be distinguished:		What this means is that these two aspects of the communication should be distinguished:

	* '''''Control and operation of the gimbal''''': The serial communication allows us to control the orientation of the gimbal, such as the tilt and pan of the camera, with higher precision than possible with the standard inputs, and gives us access to all other features of the STorM32 controller, such as triggering a camera, executing on-board scripts, and so on. It also allows the STorM32 to feed back information to the flight controller and ground control station, such as the actual camera orientation. Advanced operation modes such as follow me, smart shots, or object tracking, also fall into this category.		* '''''Control and operation of the gimbal''''': The serial communication allows us to control the orientation of the gimbal, such as the tilt and pan of the camera, with higher precision than possible with the standard inputs, and gives us access to all other features of the STorM32 controller, such as triggering a camera, executing on-board scripts, and so on. It also allows the STorM32 controller to feed back information to the flight controller and ground control station, such as the actual camera orientation. Advanced operation modes such as follow me, smart shots, or object tracking, also fall into this category.

	* '''''Improved performance''''': In addition, the serial link is used to transfer dedicated low-level data from the flight controller to the STorM32 controller, which helps it achieving better and more precise stabilization, and hence better videos. The two main features are the ''Yaw Drift Compensation'' and ''Horizon Drift Compensation'' mentioned before, but other innovative features may become possible in future.		* '''''Improved performance''''': In addition, the serial link is used to transfer dedicated low-level data from the flight controller to the STorM32 controller, which helps it achieving better and more precise stabilization, and hence better videos. The two main features are the ''Yaw Drift Compensation'' and ''Horizon Drift Compensation'' mentioned before, but other innovative features may become possible in future.
Line 17:		Line 17:
	The STorM32-Link support depends on the autopilot/flight-stack which is being used; for specific details please consult <!-- [[Using STorM32 with DJI]] and [[Using STorM32 with ArduPilot]]-->[[Using STorM32 with BetaPilot]].		The STorM32-Link support depends on the autopilot/flight-stack which is being used; for specific details please consult <!-- [[Using STorM32 with DJI]] and [[Using STorM32 with ArduPilot]]-->[[Using STorM32 with BetaPilot]].

	A comment on history: The STorM32-Link has a colorful development history. Originally conceived in early 2015, at a time when neither BaseCam/AlexMos nor Gremsy 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 encoders help significantly in implementing the goals. And that's why the STorM32-Link features have been made available first for only T-STorM32. With firmware version v2.49e the STorM32-Link has become also available for conventional STorM32, besides the inherent limitations this implies.		A comment on history: The STorM32-Link has a colorful development history. Originally conceived in early 2015, at a time when neither BaseCam/AlexMos nor Gremsy 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 encoders help significantly in implementing the goals. And that is why the STorM32-Link features have been made available first for only T-STorM32. With firmware version v2.49e the STorM32-Link has become also available for conventional STorM32, besides the inherent limitations this implies.

	{{COMMENT\|For T-STorM32 the STorM32-Link is fully tested and confirmed to work by the firmware author. This is not so however for the conventional STorM32; here STorM32-Link was added due to community request, and testing was left to the community~~, and is still going on~~. Please see [[https://www.rcgroups.com/forums/showthread.php?2055844-STorM32-BGC-32-bit-3-axis-brushless-gimbal-controller/page236&perpage=50#post43495807]].}}		{{COMMENT\|For T-STorM32 the STorM32-Link is fully tested and confirmed to work by the firmware author. This is not so however for the conventional STorM32; here STorM32-Link was added due to community request, and testing was left to the community. Please see [[https://www.rcgroups.com/forums/showthread.php?2055844-STorM32-BGC-32-bit-3-axis-brushless-gimbal-controller/page236&perpage=50#post43495807]].}}

	{{#ev:youtube\|l8rz78kDWNY\|480}}		{{#ev:youtube\|l8rz78kDWNY\|480}}

	{{#ev:youtube\|z03PkDf0R-0\|480}}		{{#ev:youtube\|z03PkDf0R-0\|480}}

OlliW at 10:49, 16 January 2023

2023-01-16T10:49:43Z

← Older revision		Revision as of 12:49, 16 January 2023
Line 1:		Line 1:
	''The information on this page refers to firmware v2.49e and higher.''		''The information on this page refers to firmware v2.49e 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 performance which otherwise would not be possible.		The STorM32-Link refers to a communication link between the STorM32 gimbal controller and a drone's flight controller for exchanging low-level data, in order to achieve advanced performance 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 and the tilting of the horizon in high-''g'' flight maneuvers such as high-speed turns. The respective mechanisms are called '''''Yaw Drift Compensation''''' and '''''Horizon Drift Compensation''''', and both are ~~available as~~ demonstrated by the videos below. The STorM32-Link may allow us to achieve further innovative features in the future, such as precision 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 and the tilting of the horizon in high-''g'' flight maneuvers such as high-speed turns. The respective mechanisms are called '''''Yaw Drift Compensation''''' and '''''Horizon Drift Compensation''''', and both are demonstrated in the videos below. The STorM32-Link may allow us to achieve further innovative features in the future, such as precision yaw pan modes or automatic recalibration at startup.

	~~The~~ physical connection used by the STorM32-Link is also used for exchanging the conventional serial commands for controlling the gimbal (these commands are described in the article [[Serial Communication]]). 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~~.		Maybe confusingly, the physical connection used for the STorM32-Link is also used for exchanging the conventional serial commands for controlling and operating the gimbal (these commands are described in the article [[Serial Communication]]). However, although the same bus is shared, this communication must not be considered part of the STorM32-Link.

	What this means is that these two aspects of the communication should be distinguished:		What this means is that these two aspects of the communication should be distinguished:

	* '''''Control of the gimbal''''': The serial communication allows us to control the orientation of the gimbal, such as the tilt and pan of the camera, with higher precision than possible with the standard inputs, and gives access to all other features of the STorM32 controller, such as triggering a camera, executing on-board scripts, and so on. It also allows the STorM32 to feed back information to the flight controller and ground control station, such as the actual camera orientation. Advanced operation modes such as follow me, smart shots, or object tracking, also fall into this category.		* '''''Control and operation of the gimbal''''': The serial communication allows us to control the orientation of the gimbal, such as the tilt and pan of the camera, with higher precision than possible with the standard inputs, and gives us access to all other features of the STorM32 controller, such as triggering a camera, executing on-board scripts, and so on. It also allows the STorM32 to feed back information to the flight controller and ground control station, such as the actual camera orientation. Advanced operation modes such as follow me, smart shots, or object tracking, also fall into this category.

	* '''''Improved ~~stabilization~~''''': In addition, the serial link is used to transfer dedicated data from the flight controller to the STorM32 controller, which helps it achieving better and more precise stabilization, and hence better videos. The two main features are the ''Yaw Drift Compensation'' and ''Horizon Drift Compensation'' mentioned before, but other innovative features may become possible in future.		* '''''Improved performance''''': In addition, the serial link is used to transfer dedicated low-level data from the flight controller to the STorM32 controller, which helps it achieving better and more precise stabilization, and hence better videos. The two main features are the ''Yaw Drift Compensation'' and ''Horizon Drift Compensation'' mentioned before, but other innovative features may become possible in future.

	Only the second aspect of the communication makes up the STorM32-Link.		Only the second aspect of the communication makes up the STorM32-Link.

	The STorM32-Link support depends on the autopilot/flight-stack which is used, for ~~the~~ specific details please consult <!-- [[Using STorM32 with DJI]] and [[Using STorM32 with ArduPilot]]-->[[Using STorM32 with BetaPilot]].		The STorM32-Link support depends on the autopilot/flight-stack which is being used; for specific details please consult <!-- [[Using STorM32 with DJI]] and [[Using STorM32 with ArduPilot]]-->[[Using STorM32 with BetaPilot]].

	A comment on history: The STorM32-Link has a colorful development history. Originally conceived in early 2015, at a time when neither BaseCam/AlexMos nor Gremsy 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 encoders help significantly in implementing the goals. And that's why the STorM32-Link features have been made available first for only T-STorM32. With firmware version v2.49e the STorM32-Link has become also available for conventional STorM32, besides the inherent limitations this implies.		A comment on history: The STorM32-Link has a colorful development history. Originally conceived in early 2015, at a time when neither BaseCam/AlexMos nor Gremsy 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 encoders help significantly in implementing the goals. And that's why the STorM32-Link features have been made available first for only T-STorM32. With firmware version v2.49e the STorM32-Link has become also available for conventional STorM32, besides the inherent limitations this implies.

OlliW at 10:45, 13 January 2023

2023-01-13T10:45:45Z

← Older revision		Revision as of 12:45, 13 January 2023
Line 15:		Line 15:
	Only the second aspect of the communication makes up the STorM32-Link.		Only the second aspect of the communication makes up the STorM32-Link.

	The STorM32-Link support depends on the autopilot/flight-stack which is used, for the specific details please consult [[Using STorM32 with DJI]] and [[Using STorM32 with ArduPilot]].		The STorM32-Link support depends on the autopilot/flight-stack which is used, for the specific details please consult <!-- [[Using STorM32 with DJI]] and [[Using STorM32 with ArduPilot]]-->[[Using STorM32 with BetaPilot]].

	A comment on history: The STorM32-Link has a colorful development history. Originally conceived in early 2015, at a time when neither BaseCam/AlexMos nor Gremsy 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 encoders help significantly in implementing the goals. And that's why the STorM32-Link features have been made available first for only T-STorM32. With firmware version v2.49e the STorM32-Link has become also available for conventional STorM32, besides the inherent limitations this implies.		A comment on history: The STorM32-Link has a colorful development history. Originally conceived in early 2015, at a time when neither BaseCam/AlexMos nor Gremsy 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 encoders help significantly in implementing the goals. And that's why the STorM32-Link features have been made available first for only T-STorM32. With firmware version v2.49e the STorM32-Link has become also available for conventional STorM32, besides the inherent limitations this implies.

OlliW at 10:42, 13 January 2023

2023-01-13T10:42:44Z

← Older revision		Revision as of 12:42, 13 January 2023
Line 3:		Line 3:
	The STorM32-Link refers to a communication link between the STorM32 gimbal controller and a drone's flight controller, in order to achieve advanced performance which otherwise would not be possible.		The STorM32-Link refers to a communication link between the STorM32 gimbal controller and a drone's flight controller, in order to achieve advanced performance 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 and the tilting of the horizon in high-g flight maneuvers such as high-speed turns. The respective mechanisms are called '''''Yaw Drift Compensation''''' and '''''Horizon Drift Compensation''''', and both are available as demonstrated by the videos below. The STorM32-Link may allow us to achieve further innovative features in the future, such as precision 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 and the tilting of the horizon in high-''g'' flight maneuvers such as high-speed turns. The respective mechanisms are called '''''Yaw Drift Compensation''''' and '''''Horizon Drift Compensation''''', and both are available as demonstrated by the videos below. The STorM32-Link may allow us to achieve further innovative features in the future, such as precision yaw pan modes or automatic recalibration at startup.

	The physical connection used by the STorM32-Link is also used for exchanging the conventional serial commands for controlling the gimbal (these commands are described in the article [[Serial Communication]]). 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.		The physical connection used by the STorM32-Link is also used for exchanging the conventional serial commands for controlling the gimbal (these commands are described in the article [[Serial Communication]]). 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.

OlliW at 12:13, 9 December 2022

2022-12-09T12:13:07Z

← Older revision		Revision as of 14:13, 9 December 2022
Line 3:		Line 3:
	The STorM32-Link refers to a communication link between the STorM32 gimbal controller and a drone's flight controller, in order to achieve advanced performance which otherwise would not be possible.		The STorM32-Link refers to a communication link between the STorM32 gimbal controller and a drone's flight controller, in order to achieve advanced performance 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 and the tilting of the horizon in high-g flight maneuvers such as high-speed turns. The respective mechanisms are called '''''Yaw Drift Compensation''''' and '''''Horizon Drift Compensation''''', and both are available ~~for STorM32~~ as demonstrated by the videos below. The STorM32-Link may allow us to achieve further innovative features in the future, such as precision 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 and the tilting of the horizon in high-g flight maneuvers such as high-speed turns. The respective mechanisms are called '''''Yaw Drift Compensation''''' and '''''Horizon Drift Compensation''''', and both are available as demonstrated by the videos below. The STorM32-Link may allow us to achieve further innovative features in the future, such as precision yaw pan modes or automatic recalibration at startup.

	The physical connection used by the STorM32-Link is also used for exchanging the conventional serial commands for controlling the gimbal (these commands are described in the article [[Serial Communication]]). 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.		The physical connection used by the STorM32-Link is also used for exchanging the conventional serial commands for controlling the gimbal (these commands are described in the article [[Serial Communication]]). 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.

OlliW at 12:12, 9 December 2022

2022-12-09T12:12:42Z

← Older revision		Revision as of 14:12, 9 December 2022
Line 3:		Line 3:
	The STorM32-Link refers to a communication link between the STorM32 gimbal controller and a drone's flight controller, in order to achieve advanced performance which otherwise would not be possible.		The STorM32-Link refers to a communication link between the STorM32 gimbal controller and a drone's flight controller, in order to achieve advanced performance 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 and the tilting of the horizon in high-g flight maneuvers such as high-speed turns. The respective mechanisms are called '''''Yaw Drift Compensation''''' and '''''Horizon Drift Compensation''''', and both are available, for T-STorM32~~, since firmware v2.35e,~~ as demonstrated by the videos below. The STorM32-Link may allow us to achieve further innovative features in the future, such as precision 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 and the tilting of the horizon in high-g flight maneuvers such as high-speed turns. The respective mechanisms are called '''''Yaw Drift Compensation''''' and '''''Horizon Drift Compensation''''', and both are available for STorM32 as demonstrated by the videos below. The STorM32-Link may allow us to achieve further innovative features in the future, such as precision yaw pan modes or automatic recalibration at startup.

	The physical connection used by the STorM32-Link is also used for exchanging the conventional serial commands for controlling the gimbal (these commands are described in the article [[Serial Communication]]). 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.		The physical connection used by the STorM32-Link is also used for exchanging the conventional serial commands for controlling the gimbal (these commands are described in the article [[Serial Communication]]). 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.

OlliW at 10:29, 8 January 2020

2020-01-08T10:29:19Z

← Older revision		Revision as of 12:29, 8 January 2020
Line 17:		Line 17:
	The STorM32-Link support depends on the autopilot/flight-stack which is used, for the specific details please consult [[Using STorM32 with DJI]] and [[Using STorM32 with ArduPilot]].		The STorM32-Link support depends on the autopilot/flight-stack which is used, for the specific details please consult [[Using STorM32 with DJI]] and [[Using STorM32 with ArduPilot]].

	A comment on history: The STorM32-Link has a colorful development history. Originally conceived early 2015, at a time when neither BaseCam/AlexMos nor Gremsy 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 encoders help significantly in implementing the goals. And that's why the STorM32-Link features have been made available first for only T-STorM32. With firmware version v2.49e the STorM32-Link has become also available for conventional STorM32, besides the inherent limitations this implies.		A comment on history: The STorM32-Link has a colorful development history. Originally conceived in early 2015, at a time when neither BaseCam/AlexMos nor Gremsy 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 encoders help significantly in implementing the goals. And that's why the STorM32-Link features have been made available first for only T-STorM32. With firmware version v2.49e the STorM32-Link has become also available for conventional STorM32, besides the inherent limitations this implies.

	{{COMMENT\|For T-STorM32 the STorM32-Link is fully tested and confirmed to work by the firmware author. This is not so however for the conventional STorM32; here STorM32-Link was added due to community request, and testing was left to the community, and is still going on. Please see [[https://www.rcgroups.com/forums/showthread.php?2055844-STorM32-BGC-32-bit-3-axis-brushless-gimbal-controller/page236&perpage=50#post43495807]].}}		{{COMMENT\|For T-STorM32 the STorM32-Link is fully tested and confirmed to work by the firmware author. This is not so however for the conventional STorM32; here STorM32-Link was added due to community request, and testing was left to the community, and is still going on. Please see [[https://www.rcgroups.com/forums/showthread.php?2055844-STorM32-BGC-32-bit-3-axis-brushless-gimbal-controller/page236&perpage=50#post43495807]].}}

OlliW at 10:28, 8 January 2020

2020-01-08T10:28:43Z

← Older revision		Revision as of 12:28, 8 January 2020
Line 7:		Line 7:
	The physical connection used by the STorM32-Link is also used for exchanging the conventional serial commands for controlling the gimbal (these commands are described in the article [[Serial Communication]]). 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.		The physical connection used by the STorM32-Link is also used for exchanging the conventional serial commands for controlling the gimbal (these commands are described in the article [[Serial Communication]]). 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.

	~~That~~ is, these two aspects of the communication should be distinguished:		What this means is that these two aspects of the communication should be distinguished:

	* '''''Control of the gimbal''''': The serial communication allows us to control the orientation of the gimbal, such as the tilt and pan of the camera, with higher precision than possible with the standard inputs, and gives access to all other features of the STorM32 controller, such as triggering a camera, executing on-board scripts, and so on. It also allows the STorM32 to feed back information to the flight controller and ground control station, such as the actual camera orientation. Advanced operation modes such as follow me, smart shots, or object tracking, also fall into this category.		* '''''Control of the gimbal''''': The serial communication allows us to control the orientation of the gimbal, such as the tilt and pan of the camera, with higher precision than possible with the standard inputs, and gives access to all other features of the STorM32 controller, such as triggering a camera, executing on-board scripts, and so on. It also allows the STorM32 to feed back information to the flight controller and ground control station, such as the actual camera orientation. Advanced operation modes such as follow me, smart shots, or object tracking, also fall into this category.

OlliW at 10:27, 8 January 2020

2020-01-08T10:27:39Z

← Older revision		Revision as of 12:27, 8 January 2020
Line 3:		Line 3:
	The STorM32-Link refers to a communication link between the STorM32 gimbal controller and a drone's flight controller, in order to achieve advanced performance which otherwise would not be possible.		The STorM32-Link refers to a communication link between the STorM32 gimbal controller and a drone's flight controller, in order to achieve advanced performance 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 and the tilting of the horizon in high-g flight maneuvers such as high-speed turns. The respective mechanisms are called '''''Yaw Drift Compensation''''' and '''''Horizon Drift Compensation''''', and both are available for T-STorM32 since firmware v2.35e, as demonstrated by the videos below. The STorM32-Link may allow us to achieve further innovative features in the future, such as precision 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 and the tilting of the horizon in high-g flight maneuvers such as high-speed turns. The respective mechanisms are called '''''Yaw Drift Compensation''''' and '''''Horizon Drift Compensation''''', and both are available, for T-STorM32, since firmware v2.35e, as demonstrated by the videos below. The STorM32-Link may allow us to achieve further innovative features in the future, such as precision yaw pan modes or automatic recalibration at startup.

	The physical connection used by the STorM32-Link is also used for exchanging the conventional serial commands for controlling the gimbal (these commands are described in the article [[Serial Communication]]). 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.		The physical connection used by the STorM32-Link is also used for exchanging the conventional serial commands for controlling the gimbal (these commands are described in the article [[Serial Communication]]). 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.

OlliW at 00:24, 8 January 2020

2020-01-08T00:24:52Z

← Older revision		Revision as of 02:24, 8 January 2020
Line 15:		Line 15:
	Only the second aspect of the communication makes up the STorM32-Link.		Only the second aspect of the communication makes up the STorM32-Link.

	The STorM32-Link support depends on the autopilot/flight-stack which is used, for details please consult [[Using STorM32 with DJI]] and [[Using STorM32 with ArduPilot]].		The STorM32-Link support depends on the autopilot/flight-stack which is used, for the specific details please consult [[Using STorM32 with DJI]] and [[Using STorM32 with ArduPilot]].

	A comment on history: The STorM32-Link has a colorful development history. Originally conceived early 2015, at a time when neither BaseCam/AlexMos nor Gremsy 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 encoders help significantly in implementing the goals. And that's why the STorM32-Link features have been made available first for only T-STorM32. With firmware version v2.49e the STorM32-Link has become also available for conventional STorM32, besides the inherent limitations this implies.		A comment on history: The STorM32-Link has a colorful development history. Originally conceived early 2015, at a time when neither BaseCam/AlexMos nor Gremsy 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 encoders help significantly in implementing the goals. And that's why the STorM32-Link features have been made available first for only T-STorM32. With firmware version v2.49e the STorM32-Link has become also available for conventional STorM32, besides the inherent limitations this implies.

			{{COMMENT\|For T-STorM32 the STorM32-Link is fully tested and confirmed to work by the firmware author. This is not so however for the conventional STorM32; here STorM32-Link was added due to community request, and testing was left to the community, and is still going on. Please see [[https://www.rcgroups.com/forums/showthread.php?2055844-STorM32-BGC-32-bit-3-axis-brushless-gimbal-controller/page236&perpage=50#post43495807]].}}

	{{#ev:youtube\|l8rz78kDWNY\|480}}		{{#ev:youtube\|l8rz78kDWNY\|480}}

	{{#ev:youtube\|z03PkDf0R-0\|480}}		{{#ev:youtube\|z03PkDf0R-0\|480}}