Advanced Functions - Revision history

OlliW: /* MAVLink */

2015-10-07T01:56:57Z

MAVLink

← Older revision		Revision as of 03:56, 7 October 2015
Line 100:		Line 100:
	Currently, the STorM32's Mavlink capabilities are exploited (to some extend) only by the 32-bit [http://copter.ardupilot.com/ ArduPilot] flight controllers. See also		Currently, the STorM32's Mavlink capabilities are exploited (to some extend) only by the 32-bit [http://copter.ardupilot.com/ ArduPilot] flight controllers. See also

			* [http://www.rcgroups.com/forums/showthread.php?t=2494532 Storm32 with Pixhawk over serial connection @rcgroups]
	* [http://www.rcgroups.com/forums/showpost.php?p=31574509&postcount=4734 STorM32 BGC - Pixhawk/BetaCopter]		* [http://www.rcgroups.com/forums/showpost.php?p=31574509&postcount=4734 STorM32 BGC - Pixhawk/BetaCopter]
	* [http://copter.ardupilot.com/wiki/common-optional-hardware/common-cameras-and-gimbals/common-storm32-gimbal/ ArduPilot > Copter > common-SToRM32 Gimbal Controller]		* [http://copter.ardupilot.com/wiki/common-optional-hardware/common-cameras-and-gimbals/common-storm32-gimbal/ ArduPilot > Copter > common-SToRM32 Gimbal Controller]

OlliW at 14:36, 14 September 2015

2015-09-14T14:36:16Z

← Older revision		Revision as of 16:36, 14 September 2015
Line 11:		Line 11:
	{{COMMENT\|Lipo batteries may be safely discharged down to 3.0 V/cell, under load.}}<br>		{{COMMENT\|Lipo batteries may be safely discharged down to 3.0 V/cell, under load.}}<br>
	{{COMMENT\|The lipo cell number is determined automatically by the firmware when a battery is connected to the board. Connecting discharged batteries may lead to incorrect cell number determination.}}		{{COMMENT\|The lipo cell number is determined automatically by the firmware when a battery is connected to the board. Connecting discharged batteries may lead to incorrect cell number determination.}}

			== Voltage Correction ==

			The parameter {{PARAMNAME\|Voltage Correction}} in the {{GUI\|Main}} tab allows to activate the voltage correction mechanism.

			This mechanism attempts to compensate the effects of a (slowly) varying battery voltage on the PID controller tuning. It does it by modifying the actual motor power. i.e. {{GUI\|Vmax}} values proportionally to the voltage change. The proportionality factor is given by the parameter {{GUI\|Voltage Correction}}. For instance, with a {{GUI\|Voltage Correction}} of 100%, a drop in the battery voltage by 25% leads to an increase of the actually used Vmax value by 25%. With a {{GUI\|Voltage Correction}} of 50%, a voltage drop by 25% leads to a 12.5% increase in Vmax, and so on.

			The mechanism can significantly reduce the dependence of the gimbal performance on the battery voltage, compensating for the slow voltage drop with time when running from a battery. It is not designed to handle short-time power burst due to e.g. sudden aggressive flight maneuvers. It also cannot accomplish what could be achieved with a truly constant (regulated) voltage.

	== Beeps ==		== Beeps ==

OlliW at 19:15, 18 July 2015

2015-07-18T19:15:30Z

← Older revision		Revision as of 21:15, 18 July 2015
Line 1:		Line 1:
	The STorM32 board provides many user features. Many of them can be activated or controlled by an input signal, and are accessible as so-called functions (see [[Inputs and Functions]]). Other features are accessible via specific parameter fields, or the {{GUI\|Tools}} menu.		The STorM32 board provides many user features. Many of them can be activated or controlled by an input signal, and are accessible as so-called functions (see [[Inputs and Functions]]). Other features are accessible via specific parameter fields, or the {{GUI\|Tools}} menu.

			== Second IMU Support ==

			One of the major features of the STorM32 controller is its support of a second imu, providing unmatched performance figures. For a detailed account see the article on [[Using a 2nd IMU]].

	== Lipo Saver ==		== Lipo Saver ==

OlliW: /* Scripts */

2015-05-15T19:41:15Z

Scripts

← Older revision		Revision as of 21:41, 15 May 2015
Line 53:		Line 53:
	== Scripts ==		== Scripts ==

	The innovative concept of on-board scripts, invented by the STorM32 project, allows to modify the controller's behavior and accomplish even complicated tasks. For the details see [[STorM32 Scripts]].		The innovative concept of on-board scripts, invented by the STorM32 project, allows to modify the controller's behavior and accomplish even complicated tasks. For the details see the article on the [[STorM32 Scripts]].

	Some example script files (extension .scr) are available in the firmware folder, which should be sufficiently self-explanatory.		Some example script files (extension .scr) are available in the firmware folder, which should be sufficiently self-explanatory.

OlliW: /* Scripts */

2015-05-15T19:40:38Z

Scripts

← Older revision		Revision as of 21:40, 15 May 2015
Line 53:		Line 53:
	== Scripts ==		== Scripts ==

	The concept of on-board scripts ~~is a very innovative approach of~~ the STorM32 ~~board~~ to modify the ~~boards~~ behavior and ~~achieve~~ even complicated tasks ~~(it was invented and provided first by~~ the STorM32 ~~project!)~~.		The innovative concept of on-board scripts, invented by the STorM32 project, allows to modify the controller's behavior and accomplish even complicated tasks. For the details see [[STorM32 Scripts]].

	~~For details see [[STorM32 Scripts]].~~		Some example script files (extension .scr) are available in the firmware folder, which should be sufficiently self-explanatory.

	Some example script files (extension .scr) are available in the firmware folder, which should be self explanatory ~~enough to use the scripts~~.

	== Motion Control ==		== Motion Control ==

OlliW: /* Scripts */

2015-05-15T15:03:08Z

Scripts

@@ Line 55: / Line 55: @@
 The concept of on-board scripts is a very innovative approach of the STorM32 board to modify the boards behavior and achieve even complicated tasks (it was invented and provided first by the STorM32 project!).
-In total four scripts can be run simultaneously and independently. They are handled via the fields in the {{GUI|Scripts}} tab. For each script, two fields are available, e.g. for Script1:
+For details see [[STorM32 Scripts]].
 Some example script files (extension .scr) are available in the firmware folder, which should be self explanatory enough to use the scripts.

OlliW: /* MAVLink */

2015-05-12T20:13:19Z

MAVLink

← Older revision		Revision as of 22:13, 12 May 2015
Line 115:		Line 115:
	For the supported MAVLink messages, see [[Serial_Communication#Mavlink_Communication\|Serial Communication: Mavlink Communication]] and [[Serial_Communication#Comments_to_STorM32_specific_Mavlink_commands\|Serial Communication: Comments to STorM32 specific Mavlink commands]].		For the supported MAVLink messages, see [[Serial_Communication#Mavlink_Communication\|Serial Communication: Mavlink Communication]] and [[Serial_Communication#Comments_to_STorM32_specific_Mavlink_commands\|Serial Communication: Comments to STorM32 specific Mavlink commands]].

	Currently the STorM32's Mavlink capabilities are exploited (to some extend) only by the [http://copter.ardupilot.com/ ArduPilot] flight controllers ~~(see~~ also [http://copter.ardupilot.com/wiki/common-optional-hardware/common-cameras-and-gimbals/common-storm32-gimbal/]).		Currently, the STorM32's Mavlink capabilities are exploited (to some extend) only by the 32-bit [http://copter.ardupilot.com/ ArduPilot] flight controllers. See also

			* [http://www.rcgroups.com/forums/showpost.php?p=31574509&postcount=4734 STorM32 BGC - Pixhawk/BetaCopter]
			* [http://copter.ardupilot.com/wiki/common-optional-hardware/common-cameras-and-gimbals/common-storm32-gimbal/ ArduPilot > Copter > common-SToRM32 Gimbal Controller]

OlliW: /* Motion Control */

2015-05-12T20:10:14Z

Motion Control

← Older revision		Revision as of 22:10, 12 May 2015
Line 94:		Line 94:
	The following commands are currently (firmware v0.68) possible:		The following commands are currently (firmware v0.68) possible:

			* SetParameter()
			* SetAngle()
	* DoCamera()		* DoCamera()
	* RecenterCamera()		* RecenterCamera()
	* SetAngle()
	* SetParameter()
	* SetPwmOut()		* SetPwmOut()
			* Wait()
	* TextOut()		* TextOut()
	* Wait()

	The motion control programming language is in fact just native [https://www.perl.org/ Perl], so you can do anything you want and is possible with a full-fledged scripting language. You may use all control structures, define variables and even your own functions, as needed.		The motion control programming language is in fact just native [https://www.perl.org/ Perl], so you can do anything you want and is possible with a full-fledged scripting language. You may use all control structures, define variables and even your own functions, as needed.

OlliW: /* Scripts */

2015-05-12T20:09:25Z

Scripts

← Older revision		Revision as of 22:09, 12 May 2015
Line 62:		Line 62:
	Any available parameter, except of the {{PARAMNAME\|Script Control}} parameters, can be modified by the scripts. This allows very powerful possibilities, but obviously also allows to do stupid things. It's in the users responsibility to not do nonsense. Script1 is distinguished in the sense that it allows to modify the {{PARAMNAME\|Script2 Control}}, {{PARAMNAME\|Script3 Control}}, and {{PARAMNAME\|Script4 Control}} parameters, while the other scripts can't modify them.		Any available parameter, except of the {{PARAMNAME\|Script Control}} parameters, can be modified by the scripts. This allows very powerful possibilities, but obviously also allows to do stupid things. It's in the users responsibility to not do nonsense. Script1 is distinguished in the sense that it allows to modify the {{PARAMNAME\|Script2 Control}}, {{PARAMNAME\|Script3 Control}}, and {{PARAMNAME\|Script4 Control}} parameters, while the other scripts can't modify them.

	The following commands are currently (firmware version v0.68) possible:		The following commands are currently (firmware version v0.76a) possible:

	* CASE#DEFAULT		* CASE#DEFAULT
Line 70:		Line 70:
	* STOP		* STOP
	* REPEAT		* REPEAT
	* SET		* SET parametername(string) value(int)
	* SETMINMAX		* SETMINMAX parametername(string) minvalue(int) maxvalue(int)
	* RESTORE		* RESTORE
	* RESTOREALL		* RESTOREALL
	* WAIT		* WAIT time(int, in 0.1secs)
			* SETANGLEPITCH angle(float)
			* SETANGLEROLL angle(float)
			* SETANGLEYAW angle(float)
			* SETANGLE pitchangle(float) rollangle(float) yawangle(float)
			* SETSTANDBY 0/1
			* DOCAMERA 0/1/2/3/4
			* DORECENTER
			* SETPWM pwmvalue(int)

	Some example script files (extension .scr) are available in the firmware folder, which should be self explanatory enough to use the scripts.		Some example script files (extension .scr) are available in the firmware folder, which should be self explanatory enough to use the scripts.

OlliW at 08:26, 30 April 2015

2015-04-30T08:26:41Z

← Older revision		Revision as of 10:26, 30 April 2015
Line 106:		Line 106:

	For the supported MAVLink messages, see [[Serial_Communication#Mavlink_Communication\|Serial Communication: Mavlink Communication]] and [[Serial_Communication#Comments_to_STorM32_specific_Mavlink_commands\|Serial Communication: Comments to STorM32 specific Mavlink commands]].		For the supported MAVLink messages, see [[Serial_Communication#Mavlink_Communication\|Serial Communication: Mavlink Communication]] and [[Serial_Communication#Comments_to_STorM32_specific_Mavlink_commands\|Serial Communication: Comments to STorM32 specific Mavlink commands]].

			Currently the STorM32's Mavlink capabilities are exploited (to some extend) only by the [http://copter.ardupilot.com/ ArduPilot] flight controllers (see also [http://copter.ardupilot.com/wiki/common-optional-hardware/common-cameras-and-gimbals/common-storm32-gimbal/]).