it is not working . the motors are only been vibrated by the board. only one time we can upgrade firmware and later ee can't as board is bricked . it has very old firmware and have to upgrade the fir.mware that forces board to brick.

it is not working . the motors are only been vibrated by the board. only one time we can upgrade firmware and later ee can't as board is bricked . it has very old firmware and have to upgrade the fir.mware that forces board to brick.

it is not working . the motors are only been vibrated by the board. only one time we can upgrade firmware and later ee can't as board is bricked . it has very old firmware and have to upgrade the fir.mware that forces board to brick.

conforme à la commande

conforme à la commande

conforme à la commande

Tudo certo. placa funcionando perfeitamente. precisa ajustar os parâmetros. Recomendo

Tudo certo. placa funcionando perfeitamente. precisa ajustar os parâmetros. Recomendo

Tudo certo. placa funcionando perfeitamente. precisa ajustar os parâmetros. Recomendo

Nice part at cheap price

Nice part at cheap price

Nice part at cheap price

Perfecta como repuesto si se ha quemado la controladora de un gimball barato.

Perfecta como repuesto si se ha quemado la controladora de un gimball barato.

Perfecta como repuesto si se ha quemado la controladora de un gimball barato.

Driving gimbal with 2206 motors and Hawkers 8SE camera. With default calibration nice stabilisation, about 130mA current while driving motors. Connects to Simple Bgc 2.2. Flexible silicone wires (~25cm)to mpu6050 on small (14x16 mm) board.

Driving gimbal with 2206 motors and Hawkers 8SE camera. With default calibration nice stabilisation, about 130mA current while driving motors. Connects to Simple Bgc 2.2. Flexible silicone wires (~25cm)to mpu6050 on small (14x16 mm) board.

Driving gimbal with 2206 motors and Hawkers 8SE camera. With default calibration nice stabilisation, about 130mA current while driving motors. Connects to Simple Bgc 2.2. Flexible silicone wires (~25cm)to mpu6050 on small (14x16 mm) board.

a volte trema un po'

a volte trema un po'

a volte trema un po'

So like most people, before I even plugged in a motor to see if the controller worked (which it would have), I loaded up the latest GUI software, used the GUI firmware flasher to update to the latest version.... and like others here, I bricked it right from go. Luckily I had a bunch of USBASP and Atmel flashing tools from my old MultiWii and SimonK days, and I found excellent info with links to the unlocked version of 2.2 b2 firmware here: www.brokking.net/article_revive_bgc.html ... so I was able to restore a bootloader using Arduino IDE, then re-flashed the board with 2.2 b2 using AVRDude command line as per the link. So after HOURS of pain, my board is back to 2.2 b2_null firmware, and it loads up fine in the old 2.2 b2 GUI and can be configured - though writing some settings seems to require a power off/on reboot which is annoying. Anyhow, the main thing is it's working again and I hope my review helps some others. In short - leave the firmware alone, and find the GUI version 2.2 b2.

So like most people, before I even plugged in a motor to see if the controller worked (which it would have), I loaded up the latest GUI software, used the GUI firmware flasher to update to the latest version.... and like others here, I bricked it right from go. Luckily I had a bunch of USBASP and Atmel flashing tools from my old MultiWii and SimonK days, and I found excellent info with links to the unlocked version of 2.2 b2 firmware here: www.brokking.net/article_revive_bgc.html ... so I was able to restore a bootloader using Arduino IDE, then re-flashed the board with 2.2 b2 using AVRDude command line as per the link. So after HOURS of pain, my board is back to 2.2 b2_null firmware, and it loads up fine in the old 2.2 b2 GUI and can be configured - though writing some settings seems to require a power off/on reboot which is annoying. Anyhow, the main thing is it's working again and I hope my review helps some others. In short - leave the firmware alone, and find the GUI version 2.2 b2.

So like most people, before I even plugged in a motor to see if the controller worked (which it would have), I loaded up the latest GUI software, used the GUI firmware flasher to update to the latest version.... and like others here, I bricked it right from go. Luckily I had a bunch of USBASP and Atmel flashing tools from my old MultiWii and SimonK days, and I found excellent info with links to the unlocked version of 2.2 b2 firmware here: www.brokking.net/article_revive_bgc.html ... so I was able to restore a bootloader using Arduino IDE, then re-flashed the board with 2.2 b2 using AVRDude command line as per the link. So after HOURS of pain, my board is back to 2.2 b2_null firmware, and it loads up fine in the old 2.2 b2 GUI and can be configured - though writing some settings seems to require a power off/on reboot which is annoying. Anyhow, the main thing is it's working again and I hope my review helps some others. In short - leave the firmware alone, and find the GUI version 2.2 b2.

como uma imagem de 😁🤗

jako obrázek 😁🤗

como uma imagem de 😁🤗

Está bem, está bem

ok

Está bem, está bem