Contents

  1. Hardware
    1. FlightControl (FC)
      1. Function and features
        1. FC 1.0
        2. Version V1.3
        3. ME Variant
      2. Explaining the main controllers and sensors
        1. Micro Controller
        2. Gyro Sensors
        3. Acceleration Sensor
        4. Atmospheric pressure sensor
        5. Interfaces
        6. PPM input
        7. I2C Bus
        8. Serial Interface (asynchronous)
        9. ISP Interface (synchronous)
    2. Motor controllers (ESC)
    3. Motors and props
    4. Receiver
    5. Battery
    6. Frame
    7. Compass (MK3MAG)
    8. NaviControl (NC)
    9. GPS (MK-GPS)
    10. BlueTooth (BL)
    11. Complete kits
    12. Shops
  2. Software
    1. FlightControl Software
    2. NaviControl Software
    3. Compass Software
    4. ESC Softwrare
    5. MKTool
    6. MKTool alternatives
    7. Other software tools
  3. Building
  4. First flights
  5. The settings explained
  6. Genaral FAQ

Hardware

FlightControl (FC)

FlightCtrlAnleitung/Flight-Ctrl_Anleitung_Foto_oben2.jpg

Function and features

This board is the MikroKopter’s control board. Currently there are several versions of this board in use. FC1.0-1.2, FC1.3, FC ME

FC 1.0

Features:

It fullfils the following tasks:

Version V1.3

https://www.mikrocontroller.com/images/FlightCtrlV1_3.jpg

(only the differences are listed)

ME Variant

Explaining the main controllers and sensors

Micro Controller

Computing and processing is accomplished by a Atmel ATMEGA644 @ 20MHz. This is a low cost and popular 8-Bit-processor.

The criteria for the choice of the micro controller were:

The flight attitude of a quadrocopter must be controlled electronically. We need different sensors for this.

Gyro Sensors

They measure the angular velocity (rotational speed) of each axis. We need three sensors to stabilize all three axes. These sensors are the most elementary components (-> GyroScope )

Acceleration Sensor

Theoretically we could omit this sensor if the quadrocopter should work in the so called Heading-Hold-Mode. ( --> Acceleration Sensor )

Atmospheric pressure sensor

It serves to stabilize the flight altitude. This sensor is optional. The large pressure openings should be closed with adhesive tape where we make a tiny hole with a needle. This protects from false readings due to wind and light. (--> en/heightsensor )

Airpressure sensor at high altitude: If the Mikrokopter is going to be flown at very high altitudes (eg 2500 meters), then it is possible that the airpressure sensor will not operate correctly. The resistors have been calculated for airpressures of 850 to 1100 hpa. At 2500 metes the airpressure will be about 750 hpa. to correct this, solder a 1.5 (to 4.7) kOhm resistor (value dependent upon altitude) parallel to R21.

Interfaces

The controller board communicates with the outside world through different interfaces.

PPM input

Here we connect the receiver. Two wires for the supply voltage and one for the receiver’s R/C sum signal. Compared to a normal servo PPM signal the sum signal contains all the channels sent by the R/C transmitter before they are decoded by the receiver. This signal is available in every receiver but there are only a few where this signal is directly accessible from outside (e.g. the RX3 Multi by ACT). ( --> RC receiver )

I2C Bus

We connect the BL-ESCs to this bus, which carries the command sequences. The Flight-Ctrl needs our special brushless ESC, to ensure fast communication via the I2C Bus. Standard ESCs cannot be used as they are to slow. The I2C Bus has a clock (SCL) and data (SDA) line. The bus connects all SCL and SDA lines together.

Serial Interface (asynchronous)

Here we connect a PC for testing and calibration. The signal is TTL and not V24. For this reason we need to connect an interface converter if we want to communicate with the standard serial interface of the PC. Later on this interface can also be used for the communication (asynchronous) with other controllers.

ISP Interface (synchronous)

The ATMEL controller will be programmed via an ISP interface. This interface can be also be used for a fast communication (synchronous serial) with other controllers.

Motor controllers (ESC)

Motors and props

Receiver

Battery

Frame

Compass (MK3MAG)

GPS (MK-GPS)

This board hosts a ublox-LEA4H GPS. The GPS provides its information to the NaviControl is a specific proprietary format (not NMEA).

Q: Can the information of the GPS be used by other equipment like the EagleTree OSD?
A: (Jesolins) The GPS can be configured to generate the the UBLOX protocol + NMEA at the same time. The NaviControl does not seem to bother that there is also NMEA in the stream. The other equipment should also not mind that there are UBLOX messages. Also both systems must accept the same baudrate
Use the U-center to set the UART 1 output to ULBOX + NMEA if it is not set already. Make sure you send it and then save the configuration to flash. Connect a second wire splitting off of the GPS Tx pin on the Nav connector and connect this one wire to the GPS signal input on the EagleTree V3. The ET V3 is auto baud and can read 57600bps You might need to update your firmware for it. Ref: http://www.rcgroups.com/forums/showthread.php?t=716870&page=696

BlueTooth (BL)

Complete kits

Shops

Software

FlightControl Software

Compass Software

ESC Softwrare

MKTool

MKTool alternatives

Other software tools

Building

First flights

The settings explained

Genaral FAQ

en/FAQ (last edited 28.04.2010 22:56 by anonymous)