• arwing pro
  • manual, assembly guide and tips
  • features
  • assembly
    • tips
• matek 743
  • GPIOs
  • RCx_OPTION: RC input option
  • 구성
  • FC Specifications
  • FC Firmware
  • Physical
• openHD
  • opto bl 30A
  • Aomway TX001
• radiomaster
  • tutorial
  • specification
  • Features
  • 4.3” IPS Color Display
  • External Module Bay
  • Radio overview
  • telemetry debug tool and blog
• reciever R81
  • Specification
• Futaba rc and receiver 6303
  • Introduction
• wing covering
  • material
• RadioLink MiniPix
  • Specifications
• Where to Buy
• Peripheral Connections
• Default UART order
  • Firmware handling
  • pdb bee rotor pdb
  • antenna
  • setup overview
  • raspi connection
    • wiring
    • setting up the Pixhawk
    • telem wiring
    • Configure MAVProxy to always run
    • installing dronekit on raspi
    • USB camera

arwing pro

intro

guide

sonicmodellrc.com for product info

somic-modell for gallery and other information.

or others

manual, assembly guide and tips

arwing-pro

arwing-assembly

arwing-intro

PartsAssemblies

customizations

features

1- Black EPP molded wing and fuselage, plus pre-built in carbon fiber spar, durable, light and flexible

2- Detachable wing and wingtip, portable and easy to take for out door FPV fly.

3- Multiple bonus camera mount, compatible for all FPV HD camera in the market

4- Easy to hand launch, super stable flying performance, 10km/h - 80km/h flying speed

5- Wingspan 900mm with high efficiency airfoil, create powerful elevating force.

6- “No-glue” required assembly, open box and fly in few seconds

7- Exactly the same motor / ESC / prop / camera with racing quads, exchangeable between each other.

8- Spacious equipment bay for more https://youtu.be/hGxbYiV6TEAFPV gear.

9- Movable battery slot for better “CG” adjustment

10- With bump for “CG” mark under the mainwing.

11- With 2 skids for hand launch grip and landing

12- With “NACA” Air inlet and outlet for FPV gear cooling

https://www.dronetrest.com/t/how-to-connect-the-unmanned-telemetry-kit-v2-to-pixhack-autopilot/1334

assembly

tips

1. First and foremost, thanks for buying this unit. You’re not only supporting our work and families but also keeping alive a hobby that’s being threaten by all sides right now.
2. This Wing is called “PRO” for a reason. If you’re a beginner we strongly encourage you to seek advice from experience FPV pilots even before trying to put this unit together. Seriously.
3. The provided CG marks are a reference and a starting point for your tuning. It’s what worked for us after all the math and flights done. This doesn’t mean that will work for your flying style or type of mission. If you know what you’re doing, feel free to experiment with it.
4. The provided “Basic Power Combo” with the PNP version is just a “middle pcesium ionoint” performance kit to get you in the air and have a great experience with a good balance between speed and range. If you have something specific in mind for yourBeeRotor wing, like a super fast unit or a super long range one, we suggest you to get the KIT and use your own selected electronics. A Premium power combo will be also offered down the road.
5. In our experience the DJI FPV system was easier to setup and reply using the dedicated main hatch and placing it in the center on the wing. In any case, you can also use the side pockets and do some DIY if needed.
6. Without any doubt, this wing is BY FAR the most aerodynamic and the one with the better cooling system from all the 1 meter wings available in the market… use this advantages wisely and keep it light and clean.
7. We strongly suggest “Frisbee” style launching for this unit, as you have no grip in the bottom (precisely to keep it clean and aerodynamic)… Any other style of hand-launching could damage your fingers. Be careful.
8. This wing was meant to be flown with modern autopilot units for best performance. You can fly it manual, but you will need to have a perfect tuning for this. To improve aerodynamics and handling this design is not very forgiving to rookie mistakes or poor setup. Take your time to double check all is OK before going airborne.
9. Our best results battery wise, were with a ZOHD 4S2P 18650 7000mAh and that’s what we recommend. Having said that, if you’re a PRO, you will know what to do ;)

matek 743

preview

gd-dfu

spec layout wiring ardupilotMapping

ardu-pinout Camera-1 and Vsw On by default Make sure 2 cameras are set with identical video format, both PAL or both NTSC.

GPIOs

PD10 PINIO1 OUTPUT GPIO(81) //Vsw pad power switch PD11 PINIO2 OUTPUT GPIO(82) //Camera switch

RCx_OPTION: RC input option

28 Relay On/Off 34 Relay2 On/Off 35 Relay3 On/Off 36 Relay4 On/Off e.g.

RELAY_PIN 81 //Vsw GPIO RC7_OPTION 28 //Relay On/Off, Use CH7 of Transmitter to switch Vsw RELAY_PIN2 82 //Camera switch GPIO RC8_OPTION 34 //Relay2 On/Off, Use CH8 of Transmitter to switch camera or

RELAY_PIN3 81 //Vsw GPIO RC9_OPTION 35 //Relay3 On/Off, Use CH9 of Transmitter to switch Vsw RELAY_PIN4 82 //Camera switch GPIO RC10_OPTION 36 //Relay4 On/Off, Use CH10 of Transmitter to switch camera The configured feature will be triggered when the auxiliary switch’s pwm value becomes higher than 1800. It will be deactivated when the value falls below 1200.

Check the pwm value sent from the transmitter when the switch is high and low using the Mission Planner’s Initial Setup » Mandatory Hardware » Radio Calibration screen. If it does not climb higher than 1800 or lower than 1200, it is best to adjust the servo end points in the transmitter. Matek Systems H743-WING FLIGHT CONTROLLER

• 마텍사의 신형 항공용 플라이트 컨트롤러입니다.

• 라인업 중 가장 파워풀한 제품입니다.

• 자이로센서가 MPU6000과 ICM20602 두 가지 모두 내장되어 있습니다.

• 정밀 고도계(DPS310)가 내장되어 있습니다.

• OSD가 내장되어 여러가지 정보를 화면으로 보실 수 있습니다.

• 8셀까지 직결이 가능하며, 트리플 BEC가 내장되어 있습니다.

• FC용 5V 2A, VTX용 9V 2A(12V전환가능), 서보용 5V 8A(6V/7.2V전환가능)

• 듀얼 카메라를 지원하며, 조종기 토글키로 간단하게 스위칭 할 수 있습니다.

• GPS와 에어스피드센서를 완벽하게 지원합니다.

• 기존 제품의 USB포트가 파괴되는 문제를 해결하였습니다.

• 고정익이나 대형드론에 강력 추천드립니다.

​

베타플라이트와 아두파일럿을 지원합니다. (INAV는 추후 지원)

아두파일럿 펌웨어를 올리시면 픽스호크와 동일하게 사용하실 수 있습니다.

동사의 GPS, 디지털에어스피드센서를 함께 쓰시길 추천드립니다.

​

구성

하단 사진 참조

​

​

FC Specifications

MCU: STM32H743VIT6, 480MHz , 1MB RAM, 2MB Flash

IMU: MPU6000 (SPI1) & ICM20602 (SPI4)

Baro: Infineon DPS310 (I2C2)

OSD: AT7456E (SPI2)

Blackbox: MicroSD card slot (SDIO)

7x Uarts (1,2,3,4,6,7,8) with built-in inversion.

13x PWM outputs(including “LED” pad)

2x I2C

1x CAN

6x ADC (VBAT, Current, RSSI, Analog AirSpeed, VB2, CU2)

3x LEDs for FC STATUS (Blue, Red) and 3.3V indicator(Red)

1x SPI3 breakout

USB/Beep Extender with Type-C(USB2.0)

Dual Camera Inputs switch

5V/9V(12V) for Camera/VTX power switch

High-precision Current Sense

ADC VB2 voltage divider: 1K:10K

ADC AirSpeed voltage divider: 10K:10K

INAV TR/SA VTX control: Yes

Beeper : Yes

RSSI: Yes

Analog Airspeed sensor: Yes

Digital Airspeed sensor: Yes

Static power 160mA@5V

​

FC Firmware

Mateksys

ArduPilot(ChiBiOS): MATEKH743

INAV: MATEKH743 (To be supported soon)

BetaFlight: MATEKH743

​

• PDB

Input voltage range: 9~36V (3~8S LiPo) w/TVS protection

2x ESC power pads

Battery Voltage Sensor: 1:10 (Scale 1100 in INAV, BATT_VOLT_MULT 11.0 in ArduPilot)

Current Senor: 132A, 3.3V ADC (Scale 250 in INAV, 40 A/V in ArduPilot)

Sense resistor: 60A continuous, 132A burst.

​

• BEC 5V output

Designed for Flight controller, Receiver, OSD, Camera, Buzzer, 2812 LED_Strip, Buzzer, GPS module, AirSpeed

Continuous current: 2 Amps, Max.3A

​

BEC 9V /12V output

Designed for Video Transmitter, Camera, Gimbal ect.

Continuous current: 2 Amps, Max.3A

12V option with Jumper pad

​

BEC Vx output

Designed for Servos

Voltage adjustable, 5V Default, 6V or 7.2V via jumper

Continuous current: 8 Amps, Max.10A

​

BEC 3.3V output

Linear Regulatorhttp://www.mateksys.com/?p=5159#tab-id-11

Continuous current: 200mA

​

Physical

Mounting: 30.5 x 30.5mm, Φ4mm with Grommets Φ3mm

Dimensions: 54 x 36 x 13 mm

Weight: 30g with USB exte

1x USB(Type-C)/Beep (Passive buzzer) Extender http://www.mateksys.com/?p=5159#tab-id-11 1x 20cm SH-4P to GH-4P cable for CAN port

1x 20cm SH-6P to SH-6P cable for USB extender.

Dupont 2.54 pins (Board is shipped unsoldered)

​

마텍 홈페이지에 가시면 세팅에 관한 많은 자료를 찾을 수 있습니다.

IMPORTANT In order to replace the exisiting firmware by Matek for Arduplane, you should follow the link in the Matek home page. firmware_link; in case there is an error, try zadig to upload firmware from local.

download

What is new on the H743-Wing V2

Use ICM42605 instead of ICM20602

Moved PDB/current sensor from FC board to bottom plate.

Moved 8A BEC from top board to bottom plate. JST-GH connector for CAN port instead of JST-SH connector. Add a JST-GH connector for I2C2, for plug and play with ASPD-4525

ArduPilot

H743-WING-V2 with ICM42605 is supported by ArduPilot 4.1 latest or newer, ICM42605 is defined as first IMU (IMU0) , MPU6000 is the 2nd (IMU1). with ArduPilot 4.1 or higher, set INS_ENABLE_MASK to 7 or default 127. Current sensor range is 220A on H743-WING-V2, make sure you set the BATT_AMP_PERVLT to 66.7 It is recommended to use STM32CubeProgrammer to erase MCU and upload firmware. check this blog http://www.mateksys.com/?p=6905 Known issue and solution, H7 will not initialize with Ardupilot firmware

INAV

Current sensor range is 220A on H743-WING-V2, make sure you set the Current Meter Scale to 150 IMU ICM42605 is supported by INAV3.0.2 or higher.

MPU6000 is the first IMU(IMU0, default), ICM42605 is the 3rd IMU (IMU2) in INAV MATEKH743 target. If you want to try the new ICM-4 series of IMUs. download inav_3.0.2_MATEKH743.hex set gyro_to_use = 2 set acc_hardware = icm42605 save If you stick with MPU6000 only, H743-WING-V2 works with stable version 3.0.x downloaded from configurator also. SD card and MSC mode for H743 were not implemented in INAV3.x. They are supported by INAV4.x or higher.

Others

If the ESCs you are using don’t have enough capacitors integrated, low ESR electrolytic capacitor is required for reducing ESC noise.

openHD

openHD-raspi

setup

opto bl 30A

• 1. Specification

1.1 Output: Continuous 30A, burst 40A up to 10 seconds.

1.2 Input Voltage: 2-6 cells lithium battery or 5-18 cells NiMH battery.

1.3 BEC: Not available.

1.4 Refresh rate of the throttle signal: 50Hz to 432Hz.

1.5 Control Signal Transmission: Optical/electrical coupled system.

1.6 Max Speed: 210000rpm for 2 Poles BLM, 70000rpm for 6 poles BLM, 35000rpm for 12 poles BLM. (BLM = BrushLess Motor)

1.7 Size: 55mm (L) * 25mm (W) * 12mm (H).

1.8 Weight: 31g.

• 2 Features

2.1 High performance microprocessor, best compatibility with all kinds of motors, highest driving efficiency.

2.2 Optimized for multi-rotor aircraft.

2.3 Smooth, linear, quick and precise throttle response.

2.4 Multiple protection features: Low-voltage cut-off protection / Over-heat protection / Throttle signal loss protection.

2.5 The throttle signal is transfered through optical/electrical coupled system to avoid electromagnetic interference.

2.6 The firmware of the ESC can be updated through the built-in USB adapter in the Professional LCD Program Box.

2.7 User programmable.

2.8 Multiple program methods supported: transmitter stick, Digital LED Program Card, Professional LCD Program Box, PC software. Very easy to program the ESC at home or at the flying field.

Aomway TX001

Switchable 25mW/200mW/600##mW 5.8G 40CH FPV Transmitter Adjustable Power: 25mW/200mW/600mW 5.8G 40CH Tranmitter with Raceband 2 kinds of connector, the extend cord is 50mm long Indicator LED to show the frequency and power

• Specification

radiomaster

radiomaster.com

guide

manual

tutorial

specification

• Type: TX16S MAX Transmitter https://youtu.be/hGxbYiV6TEA
• Size: 286.9128.9183.8mm
• Weight: 750g (without battery)/820g (with 2 x 18650 batteries installed)
• Voltage: DC7-8.4V
• Battery: 2 x 18650 (tray supplied) or 2S lipo (batteries not included)
• Current: 350mah (NO CRSF)
• Channel: 16ch
• External Micro SD slot: Card Included
• 2 x External UART Expansion Ports
• Touch Panel installed (Requires OpenTX/EdgeTX 2.4 Update)

Features

• STM32F429BIT6 MCU
• Industrial grade 4.3 inch IPS 480*272 Screen with touch
• Compatible with OpenTX
• Wheel menu button
• Full Size HALL sensor gimbals with CNC Aluminum Facia.
• Internal Multi-protocol RF System
• Native Full Speed TBS Crossfire support (400K)
• Supports Telemetry (Protocol and Receiver dependent)
• Memory 16M (can be expanded by Micro SD card)
• Voice function
• Vibration reminder function
• Improved JR module slot
• 6-Flight Mode Buttons (Pixhawk, custom fu##nctions and more!)
• Three-color LED status display
• USB-C Charging port.
• USB-C Simulator and PC connection port.
• External UART ports to expand the capabilities of your radio.
• CNC option parts and leather grips factory fitted.
• Neck Strap included

4.3” IPS Color Display

The TX16s features a bright and clear 4.3-inch IPS color display for easy and convenient model setup and operation with adjustable brightness to suit all conditions.

• Touch Panel included with TX16S Hall and TX16S Hall MasterFire combo only. Touch functionality requires OpenTX 2.4 (coming soon). TX16S Standard version is Touch Panel ready and can be upgraded with optional touch panel sold separately.

External Module Bay

The TX16s natively supports Team Black Sheep MicroTX modules in CRSFmode with LUA scripts. Best of all the TX16s Internal 4-in-1 Multi-protocol module allows you to keep the MicroTX installed and switch between internal RF and Crossfire via software, no more module swapping.

Radio overview

telemetry debug tool and blog

blog

terminalBpp

reciever R81

product

Specification

• Type: R81 - D8 Nano Sbus Receiver
• Channels: 8
• Frequency range: 2400-2483.5Mhz
• Power input range: 4.5-6V
• Signal format: Frsky D8 Compatible
• Output format: SBUS
• RSSI: RSSI on Ch9 of Sbus Output
• Range: more than 1km
• Antenna length: Approximately 6cm
• Size: 17x11mm
• Weight: 2 grams

Futaba rc and receiver 6303

Introduction

Turbines, helicopters, scale models, F3X gliders and large aerobatic models… they all carve up the sky in their own unique manner. Yet they all have one thing in common – they all need advanced radios to control them.

Few R/C systems offer the required level of sophistication, but Futaba’s latest radio, the 12FG, appears to tick all the right boxes. Let’s see if it lives up to expectations.

The 12FG straddles a large gap between the 9C and the flagship 14MZ. However, with 14-channels (12 + 2 switched), 30 model memories (expandable to 1882), and dual-band support via plug-in RF modules, it strays tantalisingly close to 14MZ territory.

I needed little persuasion to review this radio. As a 4000 owner, I was keen to see how Futaba’s new offering would stack up as a possible replacement.

Out of the Box

I have to admit to turning into a kid in a toyshop when the man from Parcel Force arrived, and the package was soon spilling its contents. These included a smart looking transmitter, R5114 receiver, mains charger and user manual. Also included were a couple of Allen keys, and a bright orange neck strap.

No servos are provided with the 12FG. However, I was surprised to see that a receiver battery was also omitted, even though it is mentioned in the packing list in the user manual.

Note that it is not possible to alter the stick mode after purchase, so make sure you specify the mode before ordering.

2.4 GHz or 35 MHz? You Choose! Thanks to the use of plug-in RF modules, the Futaba 12FG offers a genuine all-in-one solution for BeeRotorthose with 35 MHz gear who may wish migrate to 2.4 GHz later on.

The system comes with a MZ-FM 35 MHz installed. The TM-14 2.4 GHz module should be available as an extra by the time you read this. It has an integral antenna and is capable of driving any Futaba 2.4 GHz FASST aircraft receiver, from the 6-channel FS606, right up to the 14-channel R6014FS. Price of the TM-14 is £119.99, and the 14-channel R6014FS receiver will set you back £149.99.

Note that earlier 12FG transmitters will need a firmware upgrade in order to work with the TM-14. Also, transmitters are region-coded, so for example a UK supplied transmitter won’t work with a US module. This may be an issue if you intend to use this radio abroad.

PCM-G3 (narrowband PCM)

Futaba’s latest PCM-G3 modulation providhttps://usa.banggood.com/Sonicmodell-AR-Wing-Pro-1000mm-Wingspan-EPP-FPV-Flying-Wing-RC-Airplane-KIT-or-PNP-p-1756841.html?cur_warehouse=CN&ID=531466 PCM-G3 provides programmable failsafe of servo positions in the event of signal loss. There is also a separate battery fail safe.

All the benefits of PCM-G3 will also apply to the forthcoming 2.4 GHz module. In fact, I understand from the importers that the only difference between PCM-G3 and 2.4 GHz is the transmission scheme used (narrowband FM v. Spread Spectrum). Futaba claim that the 2.4 GHz module adds negligible (~2ms) additional latency so quick servo responses should also be maintained.

The Transmitter

First impressions were most favourable, starting with the smart black and silver mouldings. At just over 1 kg the box is nicely weighted without being heavy and it also feels comfortable to hold, thanks to the use of rubber mouldings and textured surfaces.

The aerial is just over a meter in length and screws into a smart chromed ball-joint. The angle is adjustable using an Allen key, and when not in use the aerial can be stored in a recess near the bottom of the case.

A good compromise has been struck with the balance. With the aerial extended, there is a slight tendency for the top to tip down, while the opposite is the case when the aerial is removed for 2.4 GHz operation. Either way, balance is acceptable.

The lower part of the facia is dominated by the LCD display. Unfortunately, while its large size is commendable, the contrast is rather poor. No amount of tweaking the contrast menu helped, and when working indoors I often found myself wishing for a backlight.

The stick units are very smooth, thanks to twMap { id: _map

//-- Qt 5.9 has rotation gesture enabled by default. Here we limit the possible gestures.
gesture.acceptedGestures:   MapGestureArea.PinchGesture | MapGestureArea.PanGesture | MapGestureArea.FlickGesture
gesture.flickDeceleration:  3000
plugin:                     Plugin { name: "QGroundControl" }

// https://bugreports.qt.io/browse/QTBUG-82185
opacity:                    0.99

property string mapNin ball races on each axis. The spring tension was a bit weak for my liking, but was easily adjusted using an Allen key.

Nestling in the side cheeks are a couple of rotary levers. These have a ratchet action and a centre detent, though the centre positions were barely detectable on the review unit.

There are six digital trims. They have a positive action, with each step accompanied by a beep. The size of each increment is adjustable and their positions are displayed on the LCD.

The remaining controls comprise a pair of rotary knobs and eight switches. All switches are three-position types, except for the rear shoulder switches, which are two-position. All switches are of excellent quality with a silky feel and minimal lateral play.

https://usa.banggood.com/Sonicmodell-AR-Wing-Pro-1000mm-Wingspan-EPP-FPV-Flying-Wing-RC-Airplane-KIT-or-PNP-p-1756841.html?cur_warehouse=CN&ID=531466e.g. ‘T1’ for trim 1, ‘LS’ for left slider, etc. As we’ll see later, all have freely assignable functions.

At the back is the compartment for the battery and SD card, as well as sockets for a charger and DSC/trainer cable.

Removing the back of the case reveals a beautifully neat assembly. The electronics are mainly confined to a single motherboard that is dominated by a huge 120-pin custom chip. All in all a remarkably low component count for such a capable system. Of course this also means there’s less to go wrong!

The overall impression is of a very well engineered, high-quality unit. Inevitably though, squeezing so much functionality into a small box has led to one or two compromises that may be noticed especially by those coming from a Euro style box. The transmitter feels a little too ‘busy’, and I’d have liked unused switches to be removable as on the 12Z and 14MZ. Finally, little concession has been made to the needs of the thumb-and-forefinger style flyer, except via the rather limited stick length adjustment.

https://usa.banggood.com/Sonicmodell-AR-Wing-Pro-1000mm-Wingspan-EPP-FPV-Flying-Wing-RC-Airplane-KIT-or-PNP-p-1756841.html?cur_warehouse=CN&ID=531466 Futaba have struck a reasonable compromise with the ergonomics.

Battery and Charging

Lifting the hinged battery cover reveals a 6-cell NiMH pack. Capacity is 1700 mAh, and based on the published current consumption of 500 mA the maximum safe duration should be around 2.5 to 3 hours. This may be a little borderline for some applications, and no doubt some users will wish to replace the pack with higher capacity cells. An audible alarm sounds when the battery voltage falls to 6.8 volts.

Using the supplied charger, a full charge takes 15-hours. If you want to use your own fast charger, it must be connected directly to the battery. Fortunately the battery is easily disconnected from the main board (the lead terminates in a standard J-connector).

Documentation

The instruction manual runs to 127 pages and is divided into seven sections. These include ‘Introduction’, ‘Basic setting up procedure’, and descriptions of the System, Linkage and Model menus.

On the face of it the manual looks comprehensive, but dig deeper and it has to be said the quality is somewhat lacking. It’s written largely in ‘Janglish’, many key features are glossed over, and one or two are completely missing. For example, there is no description at all of ‘offset’ mixers even though they have their own unique screens. Neither is there a reference section – a single concise schematic showing the way the controls and mixers link would have saved an awful lot of hassle.

All this may make it difficult for less technical users to explore the many advanced features of this radio. If in doubt, I’d recommend downloading the manual from the Futaba web site. On a more positive note, there is a very handy servo monitor menu that shows what the channels are doing in real time. This does at least allow experiment without the need to operate a model. BeeRotor

Programming Interface

Futaba have done a good job with the programming interface. There are just two controls: a large dial labelled ‘edit’, which you either twist or click, and a smaller button labelled ‘S1’.

Menus are organised hierarchically under three headings ‘System’, ‘Linkage’, and ‘Model’. Click to see a list of available functions, click again to get to a specific menu. Navigation within a menu is consistent too; press the S1 button to get to the ‘home’ field. Press a bit longer, and you’re all the way back to the opening screen. Within a menu, navigation and data entry are performed in an equally consistent manner.

Looking at the menu categories in more detail: The System menus provide access to system-wide settings such as buddy-box setup, LCD contrast, system timer and so on. The Linkage menus are where you do all the basic setting up, including creating new models, frequency selection, control assignments, and servo adjustments. Finally the Model menus are where you set up the flight conditions, response curves, and mixers. All in all, the user interface is consistent aMap { id: _map

//-- Qt 5.9 has rotation gesture enabled by default. Here we limit the possible gestures.
gesture.acceptedGestures:   MapGestureArea.PinchGesture | MapGestureArea.PanGesture | MapGestureArea.FlickGesture
gesture.flickDeceleration:  3000
plugin:                     Plugin { name: "QGroundControl" }

// https://bugreports.qt.io/browse/QTBUG-82185
opacity:                    0.99

property string mapNnd reasonably quick, though the consistency breaks slightly when it comes to the individual mixer screens.

Programming Capability

With a wide variety of programming features, the 12FG is well equipped to handle even the most complex of models. Unfortunately there isn’t space to cover everything, so I’ll choose a few key features. BeeRotor Model Types The Futaba 12FG provides a wide range of options when creating a model. For aircraft and gliders, there is a choice of seven wing configurations, from the simplest single-servo setup, to wings with eight servos. Tailless wings are similarly supported. Tail configuration options include V-tail and ‘ailevator’ (tailerons). For helicopters, there’s a choice of 8 swashplate configurations.

There is no ‘universal’ option available - you must choose from the stock templates, and your choice determines the number and type of stock mixers available. However, with availability of programmable mixers, this is unlikely to be a constraint in practice.

Freely Assignable Functions

All sticks, knobs, switches and levers can be freely assigned to any function. For example, setting up cross trims is just a question of re-assigning the trim levers. Or an unused trim lever can be used to drive an auxiliary channel. Multiple servos can be linked to the same function, thus avoiding the need for Y-leads in the model. Each linked servo can be adjusted for travel and centring. One obvious application is twin elevator and rudder servos for large models. Finally, servos can be assigned to any channel number. This makes it easy to emulate the channel arrangement of another transmitter.

Flight Conditions

Flight conditions are superbly flexible on the Futaba 12FG. They enable the whole character of the transmitter to be changed – the trim settings, mixer curves, and even the control assignments can be altered at the flick of a switch. It’s not an all-or-nothing feature either as the user decides which features should be condition dependent and which should be global.

Up to eight flight conditions are available (including the default condition). Each condition is assigned a priority, the highest priority taking precedence if multiple conditions are selected.

With a little planning, it’s possible to cook up some very powerful schemes, e.g. flight conditions and mixer interlocks all controlled from the same switch. This can greatly reduce the load on the pilot.

With a tilt towards traditionalists, flight conditions are disabled by default in favour of the more familiar dual rate functions.

Switches

Switches may be used in multiple contexts, with the state of each position (i.e. either on or off) independently configurable in each context. Sticks and levers can also be made to act like switches, with user-configurable on/off points. Logic switches may be defined based on two switches, using AND, OR or EOR operators.

Curves (AFR)

Curves (or AFR as they are rather cryptically called) provide a flexible way of altering the response of sticks and mixers. Curves may be linear or exponential, or point-based (up to 17 points). Expo can be set separately in each direction.

Servo Adjustments

Servos can be adjusted for gain, direction and end-points. I was pleased to see that the end-points act as true electronic end stops, essential on models which use aggressive mixing. On the downside, these adjustments are too crude to match up the movement of large paired control surfaces like flaps, where even the slightest differences in linkage geometry can cause subtle mistracking which is difficult to correct. It’s a shame that Futaba did not include an AFR (curves) option for each servo, in order to correct for this.

Mixers

As one might expect, the Futaba 12FG offers a comprehensive list of built-in mixers (too many to list here) as well as ten free mixers. All mixers are based on the ‘master-slave’ concept, whereby one control affects multiple servos. For example, with the ELE-CAMBER mixer, an elevator command will move all the servos assigned to the Camber function. BeeRotor

The menus differ in detail, but they all have elements in common. For example, most have an AFR page for setting the curves. A second page allows a further percentage rate to be applied to each servo. A third page specifies how the mixer is activated; e.g. permanently, or via a dedicated switch, or according to flight condition.

Many mixers also offer a ‘fine tune’ facility whereby a mixer rate can be modified dynamically. For example, you can use a volume knob to adjust aileron differential. Or the amount of ELE-FLAP mixing can be automatically reduced as flaps are deployed. All-in-all the programming on the Futaba 12FG is superbly flexible, the only slight niggle being the aforementioned lack of servo-side curves.

Real World Testing

Field testing often reveals strengths and weaknesses which are hidden during bench testing, so I like wherever possible to test fly a review radio.https://youtu.be/FOqkUmWkrmI

With a 30 mph Westerly breeze forecast for the only spare day, my Sting F3F racer was the obvious candidate for flight tests. This is a full-house competition glider, with four servos in the wing, and two in the V-tail. Not only is this a challenging model to program, but with the fast speeds (up to 90 mph) and short 100 meter course, fast servos and minimal latency are essential to avoid having to ‘anticipate the buzz’ at each end of the run.

The goals for programming the Futaba 12FG were: (a) to minimise the number of switches needed to control the phases of flight and (b) allow adjustment of mixing and differential during flight. In short, to replicate the setup that I’ve honed on the Multiplex 4000 over many seasons of competitive flying.

To accomplish this with the Futaba 12FG, I used a variety of stock mixers to control the wings and V-tail. I set up three flight conditions named Landing, Normal and Launch, all controlled by a three-position switch. I then programmed the same switch to deactivate the snapflap and crow mixers according to the flight condition. Finally the rotary knobs were programmed to allow snapflap and aileron rates to be adjusted during flight.

There were a couple of hurdles to overcome, for example the flap linkage on the Sting is arranged so the servos can use their full range of travel, even though the flap movement is grossly asymmetric (95% down/5% up). This might seem a simple task, but on many radios it is difficult or impossible to achieve. After some experimentation, a solution was found via the undocumented ‘offset’ mix.

As mentioned earlier, the crude servo adjustments were insufficient to accurately match up the flap travel on each side, however given a bit more time this could have been achieved using a corrective multi-point mix.

The tight installation precluded the use of the R5114 receiver, so the existing MPX IPD receiver was kept, with the transmitter in PPM mode. Nevertheless it did offer a chance to test the 12FG’s compatibility with a third party PPM receiver, and no problems were encountered.

With all programming done, it was off to the slope for a most enjoyable three-hour session. Inevitably the model had to be re-trimmed, mixer and diff adjusted, in fact it was like starting with a brand new model, let alone a new radio! Nevertheless, retrimming was accomplished with great ease and soon the Sting was having a ball. Nicest of all, the control responses were noticeably quicker than the 4000. Other F3F flyers using 12FG’s have reported similar quick response in PCM-G3 mode.

The only irritation was that LCD again – unlike on Euro style sets, the low position means that it is often obscured by the neck strap, and I found myself having to remove the neckstrap from around my neck to do any programming.

There are some nice little points, however. A warning beep is emitted if you try to power up with a non-default flight condition – this could save a few undercarriages being retracted on the ground. Also, the transmitter emits a warning beep if no activity is detected after several minutes – so less chance of arriving at the field with a drained battery. It’s often the little details which count.

Conclusion

As a confirmed Multiplex user, I have to admit to having a healthy dose of scepticism when faced with the Futaba 12FG. Yet the more I got to know it, the more reluctant I was to give it back. It’s a superbly flexible piece of kit, both in terms of programming and in the RF options available. It’s accurate, responsive and should be well up to the task of controlling the most complex of models. The sticks are excellent too.

I did have one or two reservations though. It has to be said that the user manual doesn’t cut the mustard for such a complex piece of kit, although there are various Internet forums available to get help if needed. Also the LCD is crying for a backlight. Finally, the duration on a full charge can only be described as average.

Nevertheless, these reservations should be kept in context, as the 12FG is a very fine radio. It’s much closer to the 14MZ than that the large price differential would suggest – think of it as a 14MZ, without the twin processors or touch screen, and a few features removed. And just like the 14MZ it offers a viable route into 2.4 GHz.

£775 may seem a lot to pay for a radio. However, if you’re looking for a top end system with all-round flexibility, and you can afford the price tag, the Futaba 12FG deserves a place near the top of your shortlist.

At a Glance

Channel count: 12 proportional + 2 switched Model memories: 30 expanded to 1882 via SD card Frequency band: Determined by plug-in module. MZ-FM 35 MHz module supplied Modulation (TM-FM module): PCM-G3, PCM-1024, FM/PPM switchable Programming Features: Aircraft, Glider, Heli Current drain: 500 mA (avg) Battery: 7.2V 1700 mAh Ni-MH Tx weight: 1.1 kg incl. battery BeeRotor

wing covering

material

• 3m 734 P600 for abrasive sand paper
• oracover
• other comments from rcgroups.com

I got the lam film from Aloft Hobbies initially, but when I realized how good it was at strengthening EPP, I ordered up a lifetime supply (that is full rolls) from from http://www.laminatorwarehouse.com/la...aminating-film

I also ordered up a couple of these: http://amazon.com/Top-Flite-Sock-Iro...ilpage_o05_s00 (Hint: when you get them you'll thing the end you need to slip the iron into has been stitched shut. But no. You plonk the iron onto the sock and when you pull the drawstring tight, it wraps the sock around the iron!) The iron in question is http://smile.amazon.com/Top-Flite-TO...rch_detailpage (I wish it had an indicator light to remind me that it was powered on!)

I'd also get some Scotch filament tape to protect the leading edges of the wings and V-tail, and perhaps the underside of the fuselage (depending on what you think is going to hit the ground first! )http://smile.amazon.com/Scotch-Filam...rch_detailpage

========================================

RadioLink MiniPix

warning:: This autopilot is not recommended because some versions of the board are not compatible with the official ArduPilot software despite multiple efforts to work with the manufacturer to make them compatible. The manufacturer is also apparently not abiding by the GPLv3 license which requires releasing the modified source code to its customers. “V1.0” and “V1.2” probably work, “V1.0 II” and “V1.1” definitely do not work.

.. image:: ../../../images/minipix1.jpg :target: ../_images/minipix1.jpg

above image and some content courtesy of the RadioLink website <http://www.radiolink.com.cn/doce/product-detail-133.html>__

Specifications

==============

• Processor and Sensors

  • STM32F405VGT6 ARM microcontroller
  • InvenSense MPU6500
  • Compass QMC5883L
  • Barometer LPS22HB

• Interfaces

  • 6x PWM outputs
  • 1x RC input (PWM/PPM, SBUS)
  • 3 UARTS (flow-control on Telem 1 & 2, no flow-control on GPS port)
  • external I2C
  • 2 x ADC for voltage and current sensor
  • 1 x additional ADC for analog RSSI or analog airspeed
  • SDIO microSD card slot
  • micro USB connector
  • includes buzzer / safety-switch, power module, I2C expansion board and TS100 GPS / mag combo depending on kit features
  • size 39 x 39 x 12 mm
  • weight 12 g without wires

• Where to Buy

• RadioLink hardware is available from various warehouses like banggood.com <https://www.banggood.com/de/Radiolink-Mini-PIX-F4-Flight-Controller-MPU6500-w-TS100-M8N-GPS-UBX-M8030-For-RC-Drone-FPV-Racing-p-1240423.html?cur_warehouse=CN>__

• Peripheral Connections

.. image:: ../../../images/minipix_periphs.jpg :target: ../_images/minipix_periphs.jpg

• Default UART order

• SERIAL0 = console = USB
• SERIAL1 = Telemetry1 = USART3
• SERIAL2 = Telemetry2 = USART2 (see Notes for reversed plastic case labels!)
• SERIAL3 = GPS1 = UART4

Serial protocols can be adjusted to personal preferences.

Firmware handling

=================

This hardware comes preflashed with a RadioLink-branded version of ArduCopter and an ArduPilot-compatible bootloader. To use non-branded ChibiOS-based ArduPilot firmware versions, download the required vehicle firmware .apj file from https://firmware.ardupilot.org/ an##d flash your board using MissionPlanner’s “custom firmware” option.

In case a bootloader re-installation is required, you can boot your board to DFU-mode using the following solder-points:

.. image:: ../../../images/minipix_dfu.jpg :target: ../_images/minipix_dfu.jpg

Then follow the instructions on how to :ref:load firmware onto ChibiOS boards <common-loading-firmware-onto-chibios-only-boards>.

.. warning:: The flightcontroller’s plastic case shows the telemetry ports’ numbers reversed compared to the board’s PCB imprints and the
firmware’s SERIALn assignments, this requires additional attention!

.. note:: MiniPix voltage and current sensing pins use Pixhawk standard ( :ref:BATT_VOLT_PIN<BATT_VOLT_PIN> = 2, :ref:BATT_CURR_PIN<BATT_CURR_PIN> = 3). The additional ADC pin can be used for either RSSI or analog airspeed. Set required option to PIN = 11.

pdb bee rotor pdb

The battery is connected to the power module’s male connector. The ESC or Power Distribution Board should be connected to the power module’s female connector.

Configuration Most ground stations provide a battery monitor interface but the parameters can also be set manually:

BATT_MONITOR = 3 to measure only voltage or 4 to measure both voltage and current (you will need to reboot the board after changing this)
BATT_VOLT_PIN = 2. The autopilot pin connected to the power module’s voltage pin
BATT_VOLT_MULT converts the analog voltage received from the power module’s voltage pin to the battery’s voltage
BATT_CURR_PIN = 3. The autopilot pin connected to the power module’s current pin
BATT_AMP_PERVLT converts the analog voltage received from the power module’s current pin to the battery’s current
BATT_AMP_OFFSET voltage offset received from the power module’s current pin when ther is no current being pulled from the battery

Instructions for setup and calibration using the Mission Planner can be found here A Blog post with instructions for set-up using QGC can be found here Enable voltage and current sensing Enter the properties your monitor can measure, the type of monitor, the type of autopilot, and the battery capacity:

Monitor: Voltage and Current or Battery Volts Sensor: Supported power module, or “Other” APM ver: Autopilot (e.g. Pixhawk ) Battery Capacity: Battery capacity in mAh The Sensor selection list offers a number of analog Power Modules (including popular models from 3DR and AttoPilot) which you can select to automatically configure your module. If your PM is not on the list then you can select Other, enter its recommended values, or perform a manual calibration as described below.

• using QGC

On this case I’m setting up with a 16000 mAh 12S battery, so the Minimum Arming Voltage value set to 3.5V per cell and connected to the Port 1 on a CUAV V5 board that has 2 power inputs.

The values from the Voltage Multiplier and Amps per Volt are supplied by the manufacturer of the Mauch Power Module 46 otherwise you’ll have to determine that manually.

Now that we’ve set how ArduPilot monitors the power condition, let’s move to the Safety tab on QGC and set the battery failsafes. Please note that we can only set the Battery Failsafe triggers for the Battery 1, because we haven’t the battery 2 enabled (yet)

• how to connect

• summary screen

arwing_beerotor

antenna

pagoda

The Quanum Pagoda-2 omnidirectional antenna was designed by Maarten Baert who wanted some key features to be incorporated into his design, these were as follows;

• Good omnidirectional radiation pattern • Good axial ratio • Compact dimensions • Easy to manuwiringfacture and at low cost

He succeeded in his goal in designing an antenna with these attrubutes. The Quanum Pagoda-2 antenna is built using regular PCB’s spaced at exact intervals with the final design taking months of fine tuning. The Quanum Pagoda-2 also have spacers in between the plates to ensure they are kept aligned with each other. The end result is an antenna with a smoother radiation pattern and a significantly better axial ratio than most other antenna’s.

Specs: Polarization: RHCP Center Frequency: 5.8GHz Bandwidth: 500MHz (5.55~6.05GHz) SWR: S11 < -20dB, VSWR < 1.22 (at center frequency) Axial Ratio: < 1.3 Gain: 1.2dBi Radiation Efficiency: 95% Weight: 9.9g Dimensions: 95 x 22.5mm Connector: SMA-plug (crimp shield + heatshrink)

Includes: 2 x Quanum Pagoda-2 antenna

aomway AOMWAY ANT007b 5.8GHz Panel Antenna

setup overview

raspi connection

pdf

• to make a network connection without a need to set up

edit the wpa_supplicant.conf file

country=US
ctrl_interface-DIR=/va/run/wap_supplicant GROUP=sudo
update_config=1

network={
    ssid="aiegoo"
    psk="yourpassword"
}

sudo apt update
sudo apt upgrade
sudo apt install python-pip
sudo apt install python-dev
sudo apt install future
sudo apt install screen python-wxgtk4.0 python-lxml
sudo apt install pyserial
sudo apt install dronekitThe Quanum Pagoda-2 omnidirectional antenna was designed by Maarten Baert who wanted some key features to be incorporated into his design, these were as follows;


• Good omnidirectional radiation pattern
• Good axial ratio
• Compact dimensions
• Easy to manufacture and at low cost


He succeeded in his goal in designing an antenna with these attrubutes. The Quanum Pagoda-2 antenna is built using regular PCB's spaced at exact intervals with the final design taking months of fine tuning. The Quanum Pagoda-2 also have spacers in between the plates to ensure they are kept aligned with each other.  The end result is an antenna with a smoother radiation pattern and a significantly better axial ratio than most other antenna's.


Specs:
Polarization: RHCP
Center Frequency: 5.8GHz
Bandwidth: 500MHz (5.55~6.05GHz)
SWR: S11 < -20dB, VSWR < 1.22 (at center frequency)
Axial Ratio: < 1.3
Gain: 1.2dBi
Radiation Efficiency: 95%
Weight: 9.9g
Dimensions: 95 x 22.5mm
Connector: SMA-plug (crimp shield + heatshrink)


Includes:
2 x Quanum Pagoda-2 antenna
sudo apt install MAVProxy

• set up RPI for UART communications raspi-config then disable UART for console, enable it for serial prt hardware Go into /boot/config.txt and add “dtoverlay=disalbe-bt” If ttyAMA0 isn’t in /dev, enable_uart=1 in /boot/config

mavproxy.py --master=/dev/ttyAMA0

>Stabilize mode GUIDED
GUIDED> APM: PreArm: Hartware safety swithc 

wiring

to-do list telem cable —– >

Its very imporant to connect tx, rx and ground if you want to use GPIO, and not only tx & rx.

https://www.raspberrypi.org/documentation/hardware/raspberrypi/power/README.md

setting up the Pixhawk

wiring

change the following params from the qgc or mp

1. :ref:SERIAL2_PROTOCOL <copter:SERIAL2_PROTOCOL> = 1 (the default) to enable MAVLink on the serial port.
2. :ref:SERIAL2_BAUD <copter:SERIAL2_BAUD> = 921 so the Pixhawk can communicate with the Raspberry Pi at 921600 baud.
3. :ref:LOG_BACKEND_TYPE <copter:LOG_BACKEND_TYPE> = 3 if you are using APSync twiringo stream the dataflash log files to the Raspberry Pi.

telem wiring

telem cable - jst 1.25mm ebay

wiring

Configure MAVProxy to always run

to setup MAVProxy to start whenever the raspi is restarted open, a terminal windown and edit the /etc/rc.local file, adding the following lines just before the final “exit 0” line

date
echo $PATH
PATH=$PATH:/bin:/sbin:/usr/bin:/usr/local/bin
export PATH
cd /home/pi
screen -d -m -s /bin/bash mavproxy.py --master=/dev/ttyAMA0 --baudrate 57600 --aircraft
MyCopter
) > /tmp/rc.log 2>&1
exit 0

installing dronekit on raspi

To install DroneKit-Python dependencies (most of which will already be present from when you installed MAVProxy) and set DroneKit to load when MAVProxy starts:

sudo apt-get install python-pip python-dev python-numpy python-opencv python-serial
python-pyparsing python-wxgtk2.8 libxml2-dev libxslt-dev
sudo pip install droneapi
echo "module load droneapi.module.api" >> ~/.mavinit.scr





MANUAL> api start vehicle_state.py

USB camera

PiCam¹ Logitech C920 Logitech C615 GoPro. (Can be used with HDMI to CSI converter). This allows users to record and view live stream simultaneously.

Other cameras may also work. search for (camera type) and gStreamer.

The following wiki, pages and posts are tagged with drone