22.8g without battery, 29.8 with 260 mAh battery (28.0 with 150 mAh but it won't fly with them, it spins up then down, up then down). Doesn't seem to matter if the camera is powered or not.

I think it might be the thin wire/connector I used, so will try the one it came with (but the wires don't fit through the eyelet).

It wasn't ready to fly, it did take some fiddling for both my transmitter, as well as so I could arm it. Also as other have ran into, I could see my switch used for Angle/Horizon/"Air" mode move but angle was only green when out of range. Somehow it just started working, I don't know what I did to get it to register correctly. Might have been doing the "Set motor_pwm_rate=1000" CLI command.

edit: Just noticed a bunch of people have asked this already, but it doesn't appear there was ever an answer. The fets say A08K 33, and the datasheet for something labeled as a mosfet that has A08K in the name appears to support at least 5.9 amps, but I'd really love an official answer.

BeeCore Review

The boards do look very similar, but there are a couple differences between them. The major difference is the USB connector placement, on the BeeCore its on the top of the board so it will work with the stock inductrix frames and Eachine E010 frames. Where the BeeBrain will only work on the stock inductrix frame.

Although the top USB placement is better, its not perfect. Most 3d printed camera mounts will interfere with the connector, but its easy to modify the file or print the mount out of a flexible material to solve that.

Installation of the board is straightfoward, all the hardware you need is included plus an extra screw and rubber mount. Ground and VCC pads are large which makes the camera install easy.

Setup is not as easy as the BeeBrain since the BeeBrain comes ready out of the box. The BeeCore needs a bit of work to get it setup, but since most of us are already familiar with the Betaflight GUI and CLI commands its really not that bad. These are the steps I had to do to get it running.

6 - Setup endpoints, now on the FrSky version you might not have to do this but on the DSM2 board the end points only go from 1083 to 1886 so a cli command needs to be entered to get the end points setup properly

After a couple test flights I would say they both perform the same, the BeeCore does have an F3 processor but on a small brushed quadcopter it doesn't make much of a difference. Saying that I would still reccomend the BeeCore over the BeeBrain since it does work on both types of frames, the FrSky version doesn't use PPM and its a bit cheaper.

I don't know but I suspect not. I've had my review board for a bit over a week now. About to post the review but unless something drastic happens it will be a very positive review. I think I have about 50 flights on the board now (should have kept a log lol). Will post by this weekend.

Although the top USB placement is better, its not perfect. Most 3d printed camera mounts will interfere with the connector, but its easy to modify the file or print the mount out of a flexible material to solve that.

Hmmm I didn't think about that. I have a 3D printed mount but I didn't use it. I thought the screws supplied with the Beecore / vibration mount would be too short. Put a bit of double stick foam type tape (with sticky mostly gone) on board, cut a couple of slots in the foam, and used rubber band via the little studs on the sides of the E010 frame. Worked so good that I decided to just leave it this way. When I hit the camera it moves and I think saves the antenna. LOL don't ask how or why I think this ha ha ha