General

Shoplink : MK-USB

The MK-USB is a USB adapter to program and parameterize the Mikrokopter.

He is on one side with a USB-miniUSB cable connected to the PC.
On the other hand, can be connected via two 10-pin male connectors assemblies.
By setting a jumper, the target board can be supplied if required (handy for example when testing individual small components that require only 5V).

On all pre-populated circuit boards (FlightCtrl, NaviCtrl, MK3Mag,...) is a bootloader installed. So it is very easy to update a current software .

A boot loader can not be installed with the MK-USB. If you want to assemble your own circuit boards, you can do this with a appropriate Atmega with pre-installed bootloader (in the Shop to buy), or install the boot loader with an ISP programmer (like this Sercon).

Not all bootloaders are public! Therefor are processors in the shop with pre-installed bootloader.

Circuit points

The MK-USB has three ports.

• x1 -> Mini-USB connector port for connecting to the computer.

• x2 -> SIO Connection to FlightCtrl or NaviCtrl

• x3 -> EPI Connection to MK3Mag or BLCtrl

So the sockets are later placed the right way, is right next to the solder pad, the number "1 " printed.

Assemble

The first thing to be fitted to the MK-USB with the remaining parts (2 x 10-pin headers, 1 x 2-pin connector).

The MK-USB finish soldered with pin headers:

Take care of a proper soldering / Contact of the pin connectors!

On the connector is on the front of a small arrow. This marks the PIN "1".A ribbon cable is crimped with the red side of this arrow.

Driver Installation

To use the MK-USB to a computer can be installed for your operating system drivers.

Windows

Driver

Here you find the latest driver: VCP-driver

MK-USB COM-Port

After installation of the the driver and insert the MK-USB, you should be finding the MK-USB in Windows Device Manager under "Ports (COM & LPT)".

Here you can find the COM port for the MK-USB and you can change it (if needed) under "Properties".

In the Device Manager can be accessed through the Control Panel, or type in >Start>Run "devmgmt.msc".

Linux

In the Device Manager can be accessed through the Control Panel or Linux, take the USB FTDI Single Port Serial Driver, which is available in the current kernel. The module is ftdi_sio.ko and the symbol USB_SERIAL_FTDI_SIO.
The MK-USB adapter should be available under / dev are / ttyUSBx . The following output should provide "dmesg":

• Link to alternative operating systems: http://www.ftdichip.com/Drivers/VCP.htm

Mac OS

Under Mac OS X (tested with 10.5.5) the current FTDI-driver installing. With the System Profiler or

In a terminal window you can see whether the MK-USB has been recognized.

The output in the terminal window should contain a line in the /dev/include tty.usbserial-xyz, where xyz stands for a cryptic letters and numbers. It looks something like this:

• Link to alternative operating systems: http://www.ftdichip.com/Drivers/VCP.htm

There is the /dev/xyz-tty.usbserial also a corresponding /dev/xyz-cu.usbserial the example should be used for the QMK Ground Station: Background: tty devices are intended for incoming connections, while cu (Calling Unix) devices are designed for outbound connections. If a tty device opened, so it waits for an assertion of DCD (handshake), which at the MK MKUSB (other than a handshake supported) results that will be maintained forever.

MK-USB testing under Windows XP (Echo-Test)

For this purpose, the MK-USB pin 1 and 9 from the port x2 (SIO) will be bridged. The easiest way to do this is to plugged in the ribbon cable on the MK-USB (x2/SIO) and placed at the other end plugs into the post a piece of wire in pin 1 +9.

The pin numbering is the post connector as follows:

Pin 1 is marked by the arrow at the Header. Below pin 1 is pin 2, next to pin 1 is pin 3, below is pin 4, etc.
If you look at the connector of the ribbon cable, it looks like (arrow left):

Now you start the Hyper Terminal. Here one should be pin 1+9 bridge to see an echo in his keystrokes. Pin 1 and 9 will be interrupted again, there is no response from keyboard input. <<BR> At Echo test should each of the characters entered in Hyperterminal the red and green LED on the MK-USB flash briefly. If pin 1 and 9 is not lit, only the red LED briefly. Windows Vista is the way, no application called Hyperterminal, for example, you can test on Vista The Open Source TelNet client client "Putty" http://www.putty.org/ .

Settings in Hyperterminal:
Here are selected, the correct COM port of the MK-USB and some minor adjustments are made.

In the dialog "ASCII Setup" should the hook "to spend locally typed characters" in his set, it is by the double appearance of the typed characters, the function of MK-USB unequivocally clear.

The terminal window should look like if Pin 1 and 9 are connected.
(without a bridge or when the MK-USB is not working correctly, there is no echo, ie no duplicate characters).
]

KopterTool

In KopterTool the COM port can be adjusted in the terminal window.
To get into the terminal window, simply click on Firmware Update & Terminal in KopterTool.

Clicking on Debug ... to return back to the main window.

Connection to the flight control

Connection to the NaviControl

Connection to the Bluetooth

---

• KategorieMK-Baugruppe/en