Advanced Functions: Difference between revisions

From STorM32-BGC Wiki V1
Jump to navigation Jump to search
Line 86: Line 86:
* Wait():
* 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.
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.

Revision as of 13:43, 6 April 2015

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). Others are accessible via specific parameter fields, or the [Tools] menu.

Lipo Saver

The parameter Low Voltage Limit in the [Main] tab allows to activate a lipo saver. When the battery voltage falls below the specified voltage per cell, the motors are disabled to minimize current draw. This state is signaled also by the fast blinking green and red led. The board needs to be repowered or reset to resume normal function.

Comment: Lipo batteries maybe safely discharged down to 3.0 V/cell, under load. 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.

Beeps

The parameter Beep with Motors in the [Setup] tab allows to activate the emission of beeps by the motors upon certain events. Two settings are available:

  • "basic":
  • "full":

Comment: The beeps are audible only when the motors are enabled. Hence, beeps are e.g. not heard when the board is powered only by the USB.

Standby

This function can be activated and its trigger source be specified by the parameter Standby in the [Functions] tab.

When in normal operation, it will disable the motors. When in standby mode, it will enable the motors and do a quick relevel. It will not go through the full initialization process and e.g. will not do a gyro calibration. Hence the standby function allows to quickly resume operation. It also means however that if the camera position has been heavily changed or the system has been put into other unfavorable conditions, that the relevel may fail.

Re-center Camera

This function can be activated and its trigger source be specified by the parameter Re-center Camera in the [Functions] tab.

It will recenter the camera, i.e. will undo any change in camera position due to a manual control signal. For the yaw axis, it does not undo the cumulative center position changes when switching between hold and pan mode.

IR Camera Remote Control

This function can be activated and its trigger source be specified by the parameter IR Camera Control in the [Functions] tab.

Pwm Out

This function needs to be enabled via the parameter Pwm Out Configuration in the [setup] tab, and the PWM output format and frequency be specified. When it can be activated and its trigger source be specified by the parameter Pwm Out Control in the [Functions] tab.

When activated the PWM signal is output on the pin RC-1. The "Rc-1" input channel yields zero value.

The details of the signal and its behavior can be fine tuned via these fields the [Functions] tab:

  • Pwm Out Mid:
  • Pwm Out Min:
  • Pwm Out Max:
  • Pwm Out Speed Limit:

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!).

In total four scripts can be run simultaneously and independently. They are handled via the fields in the [Scripts] tab. For each script, two fields are available, e.g. for Script1:

  • Script1 Control:
  • Script1:

Any available parameter, except of the 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 Script2 Control, Script3 Control, and Script4 Control parameters, while the other scripts can't modify them.

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

  • CASE#DEFAULT:
  • CASE#1:
  • CASE#2:
  • CASE#3:
  • STOP:
  • REPEAT:
  • SET:
  • SETMINMAX:
  • RESTORE:
  • RESTOREALL:
  • WAIT:

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

Motion Control

The STorM32 controller provides a rich set of commands for remote controlling the camera. These commands can be send to the board via any of the serial ports (USB, UART, Bluetooth). A very convenient method to make use of that are motion control scripts. A typical example application would be a pano, i.e. shooting a sequence of photos which are later stitched together to a large panorama view.

Some example motion control script files (extension .mcs) are available in the firmware folder, which should be self explanatory enough to use them.

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

  • DoCamera():
  • RecenterCamera():
  • SetAngle():
  • SetParameter():
  • SetPwmOut():
  • TextOut():
  • Wait():

The motion control programming language is in fact just native 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.