Boards

At present, three different versions of STorM32-BGC boards are in use (v0.17/v1.0 boards are deprecated).

Comments:

• The boards can be populated with different motor drivers: the TC4452 driver in DFN package or the TC4452 driver in SOIC package; the DFN package allows somewhat higher motor currents.
• The boards can in principle be populated with different microcontrollers; the standard configuration is a STM32F103RC.
• For a detailed description of the various connectors on the board see Pins and Connectors.
• To avoid confusion/misunderstandings please note: The boards provide many features hardware-wise, but not all are yet supported by the firmware. Please check the firmware description to find out (see e.g. the project page).

STorM32-BGC v1.3

STorM32-BGC board v1.3 with motor drivers in SOIC package

MCU: STM32F103RC at 72 MHz motor drivers: TC4452 on-board Bluetooth (optional) on-board 6DOF IMU (MPU6050) IR led Futaba S-Bus Spektrum satellite up to seven PWM/Sum-PPM inputs/outputs joystick ports for all three axes additional I2C port (I2C#2) 3 auxiliary ports BUT port

supply voltage: 6 - 18 V or 2 - 4S motor current: max. 1.5 A per motor Comment: This is not yet fully exploited and also depends on the package, with DFN packages motors with resistances of 12 Ohm or larger have been tested to be well handled at 4S (see here, here), motors with 10 Ohm may be handled with care (see here and here). board dimensions: 50 mm x 50 mm, 45 mm bolt to bolt, holes Ø3 mm

STorM32-BGC v1.2

STorM32-BGC board v1.2 with motor drivers in DFN package

Differences to the v1.3 board:

• voltage regulator: smaller SOT223 package
• only 2 auxiliary ports

STorM32-BGC v1.1

STorM32-BGC board v1.1 with motor drivers in SOIC package

Differences to the v1.2 board:

• no Futaba S-bus support
• Spektrum satellite is supported, but no extra Spektrum connector on board
• no extra USB voltage protection diode
• voltage regulator: smaller SOT223 package
• only 2 auxiliary ports

Comment: The order of pins on the I2C#2 port is reversed to that on the I2C#1 port; please consider this then connecting an MPU module to the I2C#2 port. Note that this does not apply to the witespy board; here the issue has been resolved by a smart plug.