Version 2.41 (32 bit)

From BaseCam Electronics Help
Jump to: navigation, search
Other languages:čeština 0% • ‎Deutsch 0% • ‎English 100% • ‎español 0% • ‎français 0% • ‎日本語 0% • ‎한국어 0% • ‎русский 0% • ‎中文(中国大陆)‎ 0%

Connection to PC

To connect board to your PC, you need a miniUSB cable. First time a USB cable is plugged, you need to install the appropriate software driver. If your PC does not install the driver automatically, install one manually from this link: After you install the driver and connecting the board, a new virtual COM port will be created. You need to choose this COM port in the SimleBGC software (GUI) to initiate the connection. It is safe to connect USB and main power (battery) simultaneously. But be very careful to not reverse the polarity of the main battery, because in this case it will burn out controller and may damage your PC! There is also a possibility to use Bluetooh–To-Serial adapter (HC-05, Sparkfun BlueSMiRF, and comparable) to connect to the GUI and tune the board remotely. There is a special connector on the board that matches the same one on the BT module. It is marked as UART and contains pins: 5V, GND, RX, TX. You can solder BT module over it or use extender Male-Male 4pin cable. Important Note: Bluetooth module must be configured at 115200 baud rate and Even parity (generally its not set by default, refer your module's user manual to find how to configure it). With these settings, you will be able to connect to the GUI and even to upgrade firmware remotely. Note, that HC-06 with original firmware does not support 'Even' parity. It will connect to GUI, but won't let to update firmware.

Running Program

Follow these steps to connect your main controller board to the GUI software:

  • Connect the mini-USB cable.
  • Start the GUI, select correct COM-port from the list, and click Connect. After the connection is established, all board settings and profiles will be loaded into the GUI. You can re-load the current board parameters anytime by clicking the READ button.
  • After adjusting parameters in the GUI you should write them to the controller board by clicking the WRITE button. Only the current profile parameters will be saved to the board. To return to the default settings select from menu “Board” - "Reset to defaults". This command restores default setting for active profile only and does not affect general settings and calibration data. To completely restore factory setting, choose “Board” - “Erase EEPROM” command. This command erases all settings in all profiles, and all calibration data.
  • To choose a different profile (with different settings) select it from the list of profiles (located in the upper right corner of the GUI window). You can store different settings as three different profiles onto the controller board. You can switch profiles saved on the board, by choosing the profile in the GUI, by pressing the hardware MENU button, or from RC transmitter.

You can give names to profile to better distinguish them. Custom names are stored in the GUI settings (starting from 2.41 version, names are stored in the board, too). Remember that some settings are common for all profiles and can not be saved on a per profile basis. Parameters such as sensor orientation, hardware configuration, RC inputs, and motors outs are the same across all profiles and are called “general” settings further.

GUI Overview

The GUI contains different functional blocks:

SimpleBGC GUI version 2.4
  1. Configuration block in the central part of the window, organized by tabs:
    • Basic — basic gimbal stabilization settings. Adjusting these settings is usually adequate to achieve good camera stabilization.
    • Advanced — more precise tuning options.
    • RC Settings — settings to control the gimbal roll/pitch/yaw orientation with RC inputs.
    • Service — Specify the behavior of the MENU button (located on the controller board or mounted externally) and tune the battery monitoring service.
    • Follow — settings related to special mode of the camera control when it follows frame.
    • Monitoring — real-time sensor data monitoring. This screen is extremely helpful in tuning your gimbal performance.
    • Upgrade — lets you to check the fresh version of firmware and upgrade if necessary.
  2. Connection — COM-port selection and connection status.
  3. Profile — Profile selection, loading, re-naming, and saving.
  4. Control Panel — graphic visualization of gimbal orientation angles in three axes.
    • Black arrows are displaying the angles, blue arrows are a 10x time magnification to provide higher precision. Red marks show target angles that gimbal should keep.
    • Thin blue lines shows the maximum (peak) deflection from the central, neutral point.
    • Blue digits show peak deflection amplitude. Using these numbers, stabilization quality can be estimated.
    • Vertical red bars to the right of the scales show actual power level, from 0 to 100%.
    • Gray arrows shows the angle of a stator of each motor, if known.
  5. READ, WRITE buttons are used to transfer setting from/to board.
  6. MOTORS ON/OFF button is used to toggle motors state.
  7. At the bottom of the screen, tips, status or error messages (in red color) are displayed . Overall cycle time and I2C error count is also displayed.
  8. Battery voltage indicator with warning sector.

Language menu

The GUI starts in the English version of the user interface. To change the interface language, choose one in the 'language' menu and restart the program.

View menu

You can change a visual theme from the “View” menu. For example, when using GUI outdoor, better to switch to one of the high-contrast themes. Further in this manual each tab is described in details. At the end of this manual, you can find step-by- step tuning recommendations.

Basic Settings

Note: Before tuning your controller, install the camera into the gimbal firmly and ensure your gimbal’s center of gravity is leveled as much as possible.

  • P,I,D – PID regulation parameters for all axes.
    • P–describesthepowerofdisturbanceresponse.Highervaluesmeansastronger response reaction to external disturbance. Raise this value until the stabilization quality of fast disturbances will be adequate. If the “P” value is too high, oscillations of the axis will start to be present. These oscillations will get worse if there are vibrations that reach the IMU sensor board. If oscillations occur, raise the “D” parameter by 1 or 2 units, and then try to raise the “P" value again.
    • D – The “D” value reduces the reaction speed. This value helps to remove low-frequency oscillations. A “D” value that is too high can cause high-frequency oscillations, particularly, when the IMU sensor is exposed to vibrations.
    • I–The“I”value changes the speed at which the gimbal moves to incoming RC commands and to move the gimbal back to neutral. Low values result in a slow and smooth reaction to RC commands and to getting back to neutral. Increase this value to speed up the movement
  • Limit Accelerations — this option lets to limit angular accelerations in case of hard RC or Serial control (useful to prevents jerks or skipped steps, smoother camera control, less impact on the multirotor's frame). The less is value, the smoother is camera rotation under control.
  • POWER — maximum voltage supplied to the motors (0-255, where 255 means full battery voltage). Choose this parameter according to your motor characteristics. Basic tuning:
    • Motors should not get too hot! Motor temperatures of over 80 °С will cause permanent damage to motor magnets.
    • A Power value that is too low will not provide enough force for the motor to move the gimbal and stabilize the camera adequately. A low power value will be most noticeable in windy conditions, when the gimbal is not well balanced, or if the gimbal suffers from mechanical friction. Slowly lower the Power parameter to find its optimal value. Find the lowest value that still provides good stabilization and adequate holding torque.
    • Raising the power equals raising the “P” value of PID settings. If you raise the POWER value, you should re-tune your PID values as well.
  • "+" — Additional power that will be add to the main power in case of big error (caused by missed steps). It helps to return camera to the normal position. If main power + additional power is greater than 255, the result is limited to 255.
  • INVERT — reverse motor rotation direction. It's extremely important to choose the correct motor rotation direction to not damage your gimbal. To determine the correct direction, set the P, I, and D values to 0 and the POWER values to 80 (or higher if your motors don’t produce enough force to hold/move the camera). Level the camera tray horizontally and click the AUTO button in the "Motor configuration" settings. The gimbal will make small movement to determine correct motor rotation direction. Wait for the calibration procedure to complete. Then, re-set your PID values and tune your Power values.
  • NUM.POLES — Number of motor poles. This value needs to be equal to the number of magnets in your motor’s bell. During the “auto” calibration process described above, this value is automatically detected. However, this value is sometimes not correctly determined during the “auto” calibration process and will need to be verified and possibly corrected manually. Most brushless gimbal motors are built with 14 poles (or magnets) and utilize a DLRK winding scheme. Count your motor magnets and enter this value if the value is not correct in the GUI.
  • External FC Gain — Gain value for matching the gimbal data from your flight controller (optional). For better stabilization and utilization of some additional features, the knowledge about the frame inclination angles is required. SimpleBGC IMU doesn't provide such information. Most of FC have servo outs for connecting gimbals. This outs should be connected to SimpleBGC controller through EXT_ROLL and EXT_PITCH inputs.
    • Activate gimbal outs in FC and set range limits for angles you generally fly (for example, ±30 degrees of frame inclination should equals full servo range about 1000–2000).
    • Deactivate all filters and smoothing of FC gimbal settings (if present).
    • In the RC-settings tab, make sure that inputs EXT_ROLL, EXT_PITCH doesn't used to control gimbal. (i.e. are not chosen as source for any other RC control task).
    • In REALTIME DATA tab, check availability of EXT_FC_ROLL, EXT_FC_PITCH signals, and make sure they are split to axes correctly. (Frame roll angle tilting should cause EXT_FC_ROLL change in approximately 900..2100 range. The same is for pitch.)
    • Connect power supply, and setup stabilization as described above (tune POWER, INVERT, PID).
    • Push AUTO button in FLIGHT CONTROL GAIN group, and smoothly incline copter frame to different directions by all axes for 10–30 seconds.
    • Push AUTO button again to complete calibration. (Calibration will stop automatically after some time too.) New gains will be written into EEPROM and shown in the GUI.
      NOTE: You may skip this step and leave zero values at initial setup.
  • Sensor — Specify your IMU sensor board’s orientation and position on the gimbal . For a standard IMU sensor installation, look at the gimbal from behind just like the camera will view out from the gimbal. Viewing the gimbal in this way, the UP and Right direction will match the Z and X axis. You can place the IMU sensor in any direction, keeping its sides always parallel to the motor axis (be very accurate here, it is a very important to precisely align the sensor and mount it firmly). Configure your IMU orientation in the GUI. The correct configuration should result in the following:
    • Camera pitches forward — the PITCH arrows pins clockwise in the GUI.
    • Camera rolls right — ROLL arrows pins clockwise in the GUI.
    • Camera yaws clockwise — YAW arrows pins clockwise.
Gyro Calibration.png
  • Skip Gyro calibration at startup — With this option, the board starts working immediately after powering it on, using the saved calibration data from last gyroscope calibration call. However, stored calibration data may become inaccurate over time or during temperature changes. We recommend you to re-calibrate your gyro from time to time to ensure the best performance.

Second IMU sensor

There is an option to install the second IMU sensor on the gimbal's frame. The advantage is more precise stabilization (you may use lower PID's to get the same quality) and knowing of frame tilting, that greatly helps for 3-axis system to extend the range of working angles. Second IMU should be connected to the same I2C bus as main (in parallel). Sensors should have different I2C-address (Main IMU – 0x68, Frame IMU – 0x69). On the Basecam IMU, address 0x69 may be set by cutting the ADDR bridge, located on the back side of the sensor:

Mounting the Frame IMU

There are two options where to place the second IMU: below YAW motor and above it. In case of 2- axis stabilization, there is only one option – above ROLL motor. If the sensor is placed above YAW motor, it helps to stabilize ROLL, PITCH and YAW motors. But the system becomes less stable during long work (because the frame heading, estimated from the second IMU, may drift with time and auto-correction may not work in all cases). If the sensor is placed below YAW motor, it does not help YAW axis stabilization, but works more reliable. Like the main (camera) IMU, the frame IMU may be mounted in any orientation, keeping its axis parallel with motor's axis.

Configuring the frame IMU

To configure the frame IMU, first of all set its location in the “Advanced” tab, “Sensor” area. Write settings to the board and go to the “Basic” tab. Press the button “Frame IMU”: If the second IMU is connected properly, this button becomes active. It means that all IMU settings now affect on the frame IMU. Change sensor orientation (axis TOP, RIGHT) and write setting to the board, if necessary (board will be restarted). After restart, calibrate the accelerometer and gyroscope like you did it for the main IMU. For the accelerometer, you can do simple calibration or extended 6-point calibration. You may notice that right panels with arrows are displaying now angles not for the main, but for the frame IMU. Also, in the “Realtime Data” tab, accelerometer's and gyroscope's data go for the frame IMU. It helps to properly configure an orientation of the sensor and check its calibration.

Advanced Tab

  • AHRS — options influencing on camera angle determination accuracy.
    • Gyro trust — The higher is value, the more trust to the gyro data compared with the accelerometer data when estimating angles. It can reduce errors caused by accelerations during moving, but also decreases gyro drift compensation, resulting in horizon drift over time. For smooth flying, it is recommended to set low values (40–80), which will give more stable horizon for longer time. For aggressive flying, it's better to set higher values (100–150).
    • Accelerations compensation — enable it to use a physical model of multirotor to compensate accelerations during flight. This option works only when external FC is connected and calibrated.
  • Serial port speed — changes baud rate used for serial communication. Decrease it when using over-the-air serial adapters that can't work on maximum speed. The GUI can auto-detect the baud rate configured in the board.
  • PWM Frequency — sets the PWM frequency used to drive motors by power stage. Two modes are available: Low Frequency (in audible range) and High Frequency (outside audible range). In the high frequency mode it is necessary to increase the POWER setting a bit.
  • Motor outputs — you can assign hardware motor outs for any of stabilization axes. For example, you can use second controller for YAW stabilization and set it up this way: ROLL=disabled, PITCH=disabled, YAW=ROLL_OUT, and connect a YAW motor to hardware ROLL_OUT.

Connection diagram:

With a single controller you can stabilize and control any of two axes. With 3rd axis expansion board is connected, you can stabilize and control all three axes.

Connection diagram:

  • RC Sub-Trim — allows to correct transmitter inaccuracy.
    • ROLL, PITCH, YAW trim — central point trimming. Central point here is PWM 1500. It's better to trim it in transmitter. But in case of it is not possible (when using joystick, for example), you can use AUTO function in the GUI. Just place stick in center, and press AUTO button. Actual data becomes new center point. Press WRITE button to apply settings.
    • Deadband — adjusts a dead band around neutral point. There's no control while RC signal is inside this range. This feature works only in SPEED mode, and helps to achieve better control by eliminating jitters of stick around neutral point.
    • Expo curve — adjusts the curvature of an exponential function, that allows to get precise control from RC in the range of the small values, but rough and strong control near endpoints. Works only in SPEED mode.
  • Sensor
    • Gyro LPF — adjusts filtering gyro data. It's not recommended to set values different than 0, because it will make adjusting PID controller harder. You can experiment with this.
    • Gyro high sensitivity — Increases gyro sensitivity twice. Use this option for big-sized DSLR cameras, in case if your PID settings are close to upper limits, but stabilization still not good. Increasing gyro sensitivity equals to multiplying P and D values by 2.
    • I2C Pullups Enable — turns ON builtin I2C pull-up resistors for SDA and SCLlines. Use function on only if sensor doesn't work properly.
    • FrameIMU – set the location of the frame IMU. See Second IMU sensor section of this manual.

RC Settings Tab

  • RC Input Mapping — here you can assign hardware RC inputs to virtual control channels. There are 4 hardware inputs provided on the board for RC Radio control connections, which you can assign to control any of three channels, one for each axes, and one command channel. If control for an axis is not needed, leave the option at "no input".
  • RC_ROLL pin mode — allows to configure several formats of incoming signal for RC_ROLL pin:
    • Normal – incoming signal is in the PWM format, that most RC-receivers generally outputs
    • Sum-PPM - some receivers may have this signal output. It is a PWM format modification, in which every channel transmits sequentially through one cable. In this case you do not need to connect other channels (read your receiver's user manual to check if it has SumPPM out).
    • Futaba s-bus – receivers made by Futaba may transmit data in special digital format, up to 16 channels by one wire. Connect it to RC_ROLL pin.
    • Spektrum – another digital multi-channel protocol, that is used to communicate Spektrum's satellite modules with the main module, and in its clones. Because there are many modifications of this protocol, it may not work as expected in the first versions of SimpleBGC firmware (but we will work on correct implementation in next versions). There is a dedicated socket on the board (marked Spektrum) that matches standard connector. You should bind satellite module with the transmitter manually.
  • For each control targets you can choose appropriate hardware input from the drop-down list.
    • RC_ROLL, RC_PITCH, RC_YAW, FC_ROLL, FC_PITCH – hardware inputs on board that accept signal in the PWM (Pulse Width Modulation) format (excepting RC_ROLL, see above). Most RC receivers output this signal type.
    • ADC1, ADC2, ADC3 — dedicated analog inputs, marked on the board as A1,A2,A3and accepts analog signal in range from 0 to +3.3 volts. For example, joystick variable resistor provides such signal. Connect A1…A3 to the center contact of variable resistor, +3.3V and GND to side contacts. See Connection Diagram for more info.
    • VIRT_CH_XX – In case of RC_ROLL pin mode is set to multi-channel signal format, you can chose one of the virtual channels.
  • Control targets:
    • ROLL, PITCH, YAW — controls the position of the camera.
    • CMD allows to execute some actions. You can configure 2- or 3-position switch on your RC for specified channel, and assign it to CMD channel. Its range is splitted into 3 sections: LOW, MID, HIGH. When changing the position of your RC-switch, signal jumps from one section to another, and assigned command is executed. The full list of available commands is described in the section "MENU BUTTON" of this manual.
    • FC_ROLL, FC_PITCH — used to enter signal from an external flight controller. "See External FC gain" section for details.
  • RC Mix — you can mix 2 inputs together before applying to any of ROLL, PITCH or YAW axis. It lets to control the camera from the 2 sources (joystick and RC for example). You can adjust the proportion of the mix from 0 to 100%.
  • ANGLE MODE — RC stick will control the camera angle directly. The full RC range will cause a camera to go from min to max angles, as specified above. If RC stick doesn't move, camera stands still. The speed of rotation depends on the "SPEED" setting and the acceleration limiter setting.
  • SPEED MODE — RC stick will control the rotation speed. If stick is centered — camera stands still, if stick is deflected, camera starts to rotate, but does not exceed min-max range. Speed is slightly decreased near min-max borders. Speed of rotation is proportional to stick angle and the SPEED setting. RC control inversion is allowed in both of control modes.
  • MIN.ANGLE, MAX.ANGLE — range of the angles controlled from RC or in Follow mode. To inverse the control, set higher value first, and lower value second. For example, if you want to configure a camera to go from leveled position to down position, set 0–90 (or 90–0 to inverse). To disable constraints in SPEED mode, set MIN.ANGLE=MAX.ANGLE=0.
  • LPF — Control signal filtering. The higher is value, the smoother is reaction to the stick commands. This filter cuts fast stick movements, but adds some delay.

Service Tab

Menu Button

If you've connected menu button to BTN connector on the controller, you can assign different actions to it. Action is activated by pressing button several times sequentially (1 to 5 clicks), by pressing and holding (long press).

Available actions:

  • Use profile 1…3 — loads selected profile.
  • Calibrate ACC — accelerometer calibration, works the same as button in the GUI.
  • Calibrate Gyro — gyroscope calibration
  • Swap RC PITCH – ROLL — temporary swap RC inputs from PITCH to ROLL. In most cases only one PITCH channel is enough to control a camera in 2-axis systems. Before a flight you can assign control from pitch channel to roll, and make a camera precisely leveled. Activating this function again swaps channels back, and saves roll position in the static memory.
  • Swap RC YAW – ROLL — like the previous.
  • Set tilt angles by hand — motors will be turned off, after that you can take the camera in hands and fix it in the new position for a few seconds. Controller will save and hold the new position. This function may be useful to correct camera position before flight if there is no RC control connected.
  • Motors toggle, Motors ON, Motors OFF — commands to change the state of the motors.
  • Reset controller.

Battery Monitoring

On the all 32-bit boards (and some 8-bit boards) there is a voltage sensor installed to monitor the main battery voltage. It is used to apply voltage drop compensation (to make PID stay stable during whole battery life-cycle), and to make low-voltage alarms and do the motor cut-off when the battery becomes discharged.

  • Calibrate — adjust the rate of internal multiplier to make measured voltage more precise. You need a multimeter to measure the real voltage, than enter this value in the calibration dialog.
  • Low voltage - alarm — set the threshold to make alarm when the voltage drops below it.
  • Low voltage - stop motors — set the threshold to stop motors when the voltage drops below it.
  • Compensate voltage drop — set this option to automatically increase the POWER parameter (which controls the output power goes to the motors), when the battery loose voltage due to discharge process.
  • Set defaults for — select the battery type to fill the fields above with the default settings for selected type.
    NOTE: You can add the voltage sensor to old boards in DIY way, by soldering a voltage divider 33k/10k: 33k goes to the battery "+", 10k goes to the GND, and common point goes to the pin 19 of the 328p MCU (if this pin is grounded, de-solder it first).


On some boards there is an output to the buzzer (or buzzer is installed on-board), that is triggered on some events, like notification on errors or confirmation for user actions. Events are configured (turned ON or OFF) in the GUI. You can connect an active buzzer only (which has an internal sound generator), working from 5..12V, currents below 40mA (check this [product search] for example). If you have no buzzer connected, there is an option to beep by motors. Motors can emit sound only if powered and turned on.

Status LED

There are 2 LEDs on board. Red led lights when the power for MCU is present. Green/blue LED signals show actual state of the system:

  • LED is off — pause before calibration, to take hands off or to level gimbal.
  • LED blinks slowly — Calibration in action. Freeze gimbal during this process.
  • LED blinks fast — system error, stabilization cannot be performed. To check error description, connect to GUI.
  • LED blinks fast for short time – confirmation for user action.
  • LED is on — normal operation mode.
  • LED is on, but blinks irregularly — I2C errors appears. Check in the GUI I2C errors counter.

Also, additional LEDs may present to signal serial communication on RX and TX line.

Follow Mode Tab

There is a special control mode, when the camera "follows" for a tilting of the outer frame, but eliminates small frame jerking. Several modes of operation are possible:

  • Disabled — camera is locked to ground and may be rotated only from RC.
    • Estimate frame angles from motors — it use magnetic field for rough estimation of frame tilting. Helps to increase the range of the frame angles where the gimbal's operation is stable. To proper operation in this mode, it is strictly required to calibrate Offset setting (see below). Like with the Follow mode, its not recommended to use this option in flight, its dedicated for hand-held systems only.

NOTE that this option is ignored if you connect second IMU mounted on the frame, because the data from the second IMU is more precise than from motors.)

  • Follow Flight Controller — camera is controlled from RC together with the mixed signal from an external flight controller (FC). Almost every FC has servo outputs to drive a gimbal. It feeds the information about the frame angles to this outputs, in the PWM format that all servos understand. SimpleBGC can get this information and use it to control a camera. It is necessary to connect and calibrate external flight controller (see EXT.FC GAIN settings). After calibration you can setup the percentage values for ROLL and PITCH axis, so the camera will follow frame inclinations.
  • Follow PITCH, ROLL — this mode is dedicated to hand-held systems. FC connection is not required. In this mode, the position of the outer frame by PITCH and ROLL is estimated from the motor's magnetic field. This means that if motor skips steps, position will be estimated incorrectly and operator should correct camera by hands, returning it to proper position. You should use this mode carefully for FPV flying, because if the camera misses its initial direction, there is no chance to return it back automatically.
ROLL axis mode.png
    • Follow ROLL start, deg. — Set the angle (in degrees) of the camera PITCH-ing up or down, where the ROLL axis enters follow mode. Below this angle, ROLL is in lock mode.
    • Follow ROLL mix, deg. — Set the range (in degrees) of the camera PITCH-ing, where the ROLL axis is gradually switched from the "lock" mode to "follow" mode (see picture).
      Hint: to completely disable follow for ROLL, set these values to (90, 0). To permanently enable follow for ROLL (regardless of the camera PITCH-ing), set values to (0, 0).
  • Follow YAW — the same as above, except it can be enabled only for YAW axis. For example, you can lock camera by ROLL and PITCH axis by selecting "Disabled" option, but still control camera by YAW by enabling "Follow YAW" option.

There are additional settings to tune follow mode:

  • Dead band, degrees — you can set the range where the rotation of an outer frame does not affect the camera. It helps to skip small jerks when you operate gimbal by hands.
  • Expo curve — you can specify the strength of the control when outer frame declines from neutral position. For example: when the expo curve is enabled (i.e. is not flat), small or medium declination of an outer frame will cause very fine control even if I-term is configured high. But the strength of control exponentially grows when angles of declination becomes close to 60 degrees. It gives a big freedom in camera operation: from fine and smooth control to very fast movements.
  • OFFSET — it is a very important to properly configure the initial position of the motor's magnetic poles, because all further calculations use this information. For YAW axis it allows to fine adjust a camera heading relative to a frame heading. For PITCH and ROLL axis there is an option to calibrate offset automatically. To do this, power on system, hold frame leveled, and press AUTO button. Don't forget to write setting when finished.
    If the camera after power on is not leveled, you need to adjust the offset setting.
Operation in the Follow Mode.png
  • SPEED — adjust the speed of the camera rotation in the follow mode. Don't set big values that motors can not handle (if motor does not produce enough torque, it will skip steps and synchronization will be broken). In this case, acceleration limiter may help to have big speed but do not miss steps.

Operation in the Follow Mode

At system startup in the follow mode, keep the frame horizontally and manually adjust the camera to the horizontal position, and adjust it's heading. Camera easily "jumps" between the magnetic poles. Rotate the camera by hands to desired horizontal position, it will stick to the nearest magnetic pole.

Gently rotate and tilt the frame. Turns within ±45° will control the speed of the camera from 0 to 100%. Camera rotates in accordance with the SPEED settings until it's angles are not equal the frame's angles, or until given restrictions will be achieved.

If the camera moves unpredictably, perhaps its the wrong direction of rotation of the motors and you need to change the Reverse flag in the "Basic" tab .

To achieve the smooth motion, increase the LPF parameter (in the 'RC' tab), increase Expo curve, and decrease the SPEED and the Acceleration limits. For more dynamic control, change these settings in the opposite direction.

In case of failure of stabilization due to external disturbances, the camera can completely lose synchronization with the frame . In this case, it is necessary to return it to the proper position by hands. IT IS VERY IMPORTANT to keep the frame horizontally, because at this point the frame's zero angles are calibrated.

You can switch between modes on-the-fly by activating different profiles. Camera will keep their position between modes.

Realtime Data Monitoring Tab

In this tab you can see raw sensor data stream, and logical RC input levels.

  • ACC_X,Y,Z — accelerometer data.
  • GYRO_X,Y,Z — gyroscope data. Helps to determine quality of P and D settings. Disturb gimbal by hand and see trace. If it looks like sine wave, D setting is too low and gimbal tends to low- frequency oscillations. If some noise is always present even without any disturbance, D setting is too high and gimbal tends to high-frequency self-excitation.
  • ERR_ROLL,ERR_PITCH,ERR_YAW — stabilization error graph. Same as peak indicators on the control panel and shows maximum deflection angle.

Each graph can be turned on or off, scale can be adjusted for Y axis. You can pause the data transmission at any time. You can receive extended debug information from the board by selecting the checkbox “Receive extended debug info”. Useful information you can get from the board:

  • RMS_ERR_R,RMS_ERR_P,RMS_ERR_Y – RMS amplitude of gyro sensor data. In case of oscillations, it helps to define which axis is unstable. Its may be not so clearly from raw gyro data, because oscillations may have high frequency, far above a frame rate that GUI can receive and display.
  • FREQ_R, FREQ_P, FREQ_Y – the main frequency of oscillation. If RMS_ERR is too small, this parameter is useless.

Firmware Upgrade Tab

To check if the firmware upgrade is available, connect the board and press “CHECK” button. You will receive information about all available versions of firmware and can choose version to upgrade. When selecting a version in drop-down list, its full description is displayed in the text area below. To upload selected version to the board, press the UPGRADE button. Uploading process will be started. Generally, it takes about 10…30 seconds to finish. Do not disconnect USB cable (or break wireless connection) while firmware is uploading! If you get error during uploading firmware "CreateProcess error=14001", you need to install Microsoft Visual C++ 2008 x86 redistributable from this link: [[1]]. There is an option to configure system to check updates automatically. When new version will be issued, you will be prompted to upgrade to it.

Uploading Firmware in the Manual Mode

This option intended to special cases when the board becomes bricked (GUI cannot connect to it) and you need to upload special “recovery” version of firmware. Use this mode carefully and only if you understand what you are doing!

  1. Disconnect any power source, USB cable.
  2. Close (set) FLASH jumper on board (attach jumper to 2 pins marked as 'FLASH', shorting them)
  3. Connect board to PC by USB cable
  4. Run GUI, select COM port (but not connect!) and go to "Upgrade firmware" - "Manual" tab
    DO NOT PRESS CONNECT IN THE GUI, IF JUMPER IS CLOSED! If pressed, you need to repeat all steps from the beginning.
  5. Choose firmware .hex file. Select board version (v3 for 32bit boards).
  6. Press FLASH button and wait for process to be finished.
  7. Open (remove) FLASH jumper.

If board is alive (you can connect to the GUI), you can upload firmware in manual mode without setting FLASH jumper:

  1. Connect to the board normal way
  2. Choose firmware .hex file. Select board version (v3 for 32bit boards).
  3. Press FLASH button and wait for process to be finished.

FAQ and Troubleshooting

Firmware uploading process was interrupted and board is not working now, not responding to GUI. Is it fatal? No, its not fatal for your board (moreover, its impossible to damage board such way). You just need to upload special "recovery" firmware. You can find it in the "firmware" folder, named "simplebgc_recovery_32bit.hex", or download from our site. Refer to instructions how to upload firmware in the manual mode. Then, you can connect to the board and upgrade to any version, as regular.

I know from somebody, that there is fresh version, but I don't see it when checking for updates. Why? Its normal. There are may be beta versions, available for beta-testers only, or may be different versions for different boards. You will receive only stable versions, issued for your board.

Can I upgrade firmware from Mac or Linux? Sorry, currently not. We are using flash tool from St company (manufacturer of MCU), Flash Loader Demonstrator. Unfortunately, it is available for Windows only.

My board has no USB connector, but has bluetooth. Can I upgrade firmware? Yes, you can ugrade via Bluetooth the same way as USB. Integrated module already configured properly to work for upgrade.

I am using external bluetooth module and it works fine with the GUI. Can I upgrade firmware through it? Yes, if you configure module to "Even" parity. To work with GUI, it may be both "Even" and "No" parity setting, but to upgrade firmware, it should be configured in the "Even" parity only. Look for instruction for your module how to configure it.

Is it required to disconnect battery when upgrading firmware? No, there is no matter if board powered from battery, or from USB only.

After upgrade, my GUI can't connect to the board. What to do? Its important that firmware and GUI both have matched versions. Changes in the firmware usually require changes in the GUI, so old GUI will not work with the fresh firmware. You can download matched GUI from our website. Link to matched GUI generally provided in the description of the firmware.

I got error during uploading: "CreateProcess error=14001" Some required libraries are missed in your system. You need to install Microsoft Visual C++ 2008 x86 redistributable:

Setup Step-by-Step Sequence

Adjusting the Mechanics

Mount the camera on the tray and balance the gimbal in all three axes. Stabilization quality is hardly connected to the balance quality. To check your balance, pick your turned off gimbal in hands. Make fast motions along all axes, trying to catch resonance point and swing the gimbal. If it is hard to do - gimbal is balanced correctly.

NOTE: With good balance and low friction, It's possible to scale down power consumption and keep good quality of stabilization.

If you rewound motors by yourself, it's recommended to check winding. Remove motors from gimbal, connect them to controller and set parameters P=0, I=0.1, D=0 for each axis and set enough POWER. Connect main power supply. Motors should spin smoothly, while rolling the sensor. Little jitter is normal due to magnetic force between rotor and stator ("cogging" effect).

Pay great attention to sensor installation. Its axes must be parallel with motor axes. Pay attention to mechanical links. They must be a VERY RIGID and backlash-free. Sensor provides feedback data for stabilization, and even any little freedom or flexibility will cause delays and low-frequency resonances. This can result in difficult PID setting, and unstable work in real conditions ( frame vibrations, wind, etc)

Calibrating the Sensor

Gyro is calibrated every time you turn controller on, and lasts about 4 seconds. Try to immobilize sensor (camera) as hard as you can in first seconds after powering on, while signal LED is blinking. After powering on you have 3 seconds to freeze gimbal before calibration starts.

If you activated option "Skip gyro calibration at startup", gyro is not calibrated every time and controller start working immediately after powering up. Be careful and recalibrate gyro manually, if you will notice something wrong with IMU angles.

Calibrating Accelerometer

You must perform ACC calibration only once, but it's recommended to recalibrate it from time to time or when the temperature significantly changes.

  • Simple calibration mode: set sensor horizontally, and press CALIB.ACC in the GUI (or menu button, if it's assigned). LED will blink for 3 seconds. Try not to move sensor during calibration. At this step no matter how camera is leveled. You are calibrating the sensor, not the camera!
  • Advanced mode (recommended): perform calibration in simple mode as above. Then turn sensor in order that each side of sensor looks up (6 positions at all, including base one). Fix the sensor in each position, press CALIB.ACC button in the GUI, and wait about 3–4 seconds, while LED if flashing. The order does not matter, but the base position always goes first (because the simple calibration cancels a result of advanced calibration). You have not to press WRITE button, calibration data is written automatically after each step.

NOTE: Precise accelerometer calibration is a very important for horizon holding during dynamic flying or YAW rotation.

Calibrating Accelerometer.png

Tuning Basic Settings

  • Connect the main power supply.
  • Set POWER according to the motor configuration (see recommendations above).
  • Auto-detect number of poles and motors direction.
  • Adjust PID controller. To check stabilization quality, use peak indicator in control panel. Incline the frame by small angles and try to minimize peak values by increasing P, I and D to its maximum. You may use gyro data from Realtime Data tab to estimate stabilization quality, too.
  • At this time it is possible to get 1 degree mistake , otherwise 2–3 degrees is a good result to.

Connecting and Configuring RC

Connect one of the free receiver's channels to RC_PITCH input, preserving right polarity In the RC Settings tab:

  • Set SORCE=PWM.
  • Assign RC_PITCH input to PITCH axis.
  • Leave all other axes and CMD as "no input".
  • For PITCH axis, set MIN.ANGLE=−90, MAX.ANGLE=90, ANGLE MODE=checked, LPF=5, SPEED=10 (not used in angle mode).
  • Connect the battery to the main controller and receiver, and check that RC_PITCH input receives data in the "Realtime Data" tab (slider should be blue filled and reflects to stick movement).

Now you can control the camera from your RC transmitter, from −90 to 90 degrees. If you are not satisfied with the speed of movement, adjust the I-term setting for PITCH in the "Basic" tab.

Try the SPEED mode and feel difference with the ANGLE mode.

Connect and tune remaining axes the same way, as required.

Testing Gimbal in Real Conditions

Connect controller to the GUI and turn ON multirotor motors, holding it above your head. Check the vibrations on the camera by using Realtime Data tab / ACC raw data. Try to decrease the level of vibrations using soft dampers.

NOTE: Brushless motors versus traditional servos provide faster reaction, but less torque. That's why it's hard for them to fight against wind and air flows from props. If you are developing multirotor frame by yourself, try to avoid this influences (for example, lengthen arms a bit, or tilt motors away from center or place camera above props in case of H-frame). Also keep in mind, that when copter moves with high speed, an air flow is deflected and can affect the gimbal.

Connecting YAW Expansion Board

Main board contains only two motor drivers, and can stabilize two axes. Extension board allows to get stabilization for all three axes. It's connected with I2C and gets commands from main board.

No extra sensor is needed.

Connection diagram:

To activate 3rd axis, go to Advanced / Motor outputs and set YAW=YAW ext.board.

NOTE: The expansion board needs extra power supply to operate. When you are tuning gimbal connected to PC, It can't get power supply from FTDI or USB, and therefore may not be recognized by the main board.

Status LED on expansion board shows current mode of operation:

  • LED is OFF — power supply is not connected, or short-circuit protection in action, or current overload detected (protection strategy – turn motors off for 1 second)
  • LED is ON — power supply connected, but no I2C commands received.
  • LED is ON and blinking — normal operation mode.

Possible Problems and Solutions

Problem Possible causes Solutions
Motors don’t spin
  • Power supply is not connected;
  • Supply polarity inverted;
  • POWER set to 0.
  • Check all connections;
  • Set POWER between 50…200.
Camera is trying to align, but falls back
  • Camera not balanced;
  • It's an error in motor windings, or one phase is broken;
  • POWER is not high enough.
  • Balance camera;
  • Check motor winding;
  • Increase POWER parameter.
During fast YAW rotating, camera deflects by ROLL, and then slowly gets to horizon
  • Bad accelerometer calibration;
  • Sensor is not in parallel with motor axes.
  • Make advanced ACC calibration by 6 positions;
  • Align sensor with motor axes.
YAW arrow slowly spins in the GUI
  • Slow drift is normal (less than 1 degree/minute). It’s because of gyro drifts in time
  • Pay attention to sensor Immobility during gyro calibration;
  • Re-calibrate gyro.
Camera slowly drifts by any or all axes just after power on
  • Bad gyro calibration
  • Re-calibrate gyro
Clicks and crunch are heard during work. LED is synchronously blinking
  • I2C errors present. Errors are possible if sensor wires are too long, or motors outs affects sensor by capacitive linkage
  • Shorter sensor wires;
  • Lower pullup resistors value on the sensor board;
  • Install spike LC-filter on motor outs (make 2-3 turns of motor cable through ferrite coil);
  • Instal spike LC-filter on sensor wires (the same as motor filter);
  • Replace sensor with version with LLC.
High-frequency oscillations
  • Feedback self-exitating as a result of high D parameter
  • Check the graphs to understand on what axis the problem is, and lower D value
Low-frequency oscillations
  • Feedback self-exitating as a result of high D parameter or high P
  • Lower P, increase D
GUI cannot connect to board
  • Wrong COM-port selected;
  • GUI and firmware versions doesn’t match.
  • Try different COM-ports;
  • Upload the latest firmware, and download matching GUI version.