Hello from a new forum member,
Here are my specs:
1). Flat octo, CF 1000 mm custom frame; T-motor 4014 400kv; T-motor 30A ESC Pro; T-motor 14*4.8 CF props; Pulse 10000 mah 6S battery
2). Graupner MX-20 TX, Graupner HoTT GR-16, PPM sum
3). AVL58, iOSD Mark II, small FPV camera with pitch servo, LEDs for night flying.
The gimbal I use most often was custom made for PJ710V (or other camcorder with similar dimensions), 3-axis stabilized with zoom and camera mode controls, independently operated from a second TX (JR9503). It also has its own 5.8G video transmitter. Apart from using power from the main battery via slip ring in yaw motor, the gimbal is attached to the copter frame only mechanically, by quick release system. All-up weight is 6.8 kg
View attachment 20174
So far it is working very well, flight times are good, position hold is especially impressive. Have been flying full day at mountain ski resort in -18 C to -5 C windy weather with no issues whatsoever. Used styrofoam pads to keep the batteries warm in flight.
Here are my nitpicks (some of them mentioned before):
1. In A2 Assistant software, there's no clear indication of whether failsafe is working/engaged or not.
2. Only 8 channels are available via PPM. To me it looks like an artificial limitation, because I know that Mikrokopter is capable of extracting all 12 channels from the very same RX/TX pair.
3. No easy way to calibrate endpoints on third-party ESCs. I would go with DJI ESCs instead of T-motors because they do not require throttle calibration, but the ones I found only supported 4S max.
4. GPS is sensitive to slightest obstructions. I can sometimes drop the number of satellites from 14 to zero by just leaning over the copter. Because of this behavior, I don't want to risk flying in obstructed environments.
5. No way to set up a dedicated motors on/off switch. It might be a personal issue, but I find DJI system awkward and counterintuitive. More than once I have narrowly escaped damage when, after landing, the motors didn't stop and the copter fell on its side.
6. Inaccurare altitude display via iOSD. Could be off by 2-3 meters. Doesn't affect alt. hold, though.
7. Getting into compass calibration mode is a huge pain, so much that I am thinking of using an Arduino board that could be temporarily plugged in between the receiver and controller, with pre-programmed routine just to get into this mode. Shouldn't be so hard...
Regards,
Gene