Comments on: GPS + Mikrokopter (II)

By: Dimitri

Dimitri — Tue, 27 Jan 2009 23:31:33 +0000

Hi Speedy, thanks for explanations. Maybe I have spoofed you a bit, I just thought that you somehow “doubled” two small red and green leds on FC as they are almost invisible at daylight.

By: Speedy

Speedy — Tue, 27 Jan 2009 18:40:07 +0000

Hi Dimtri,
Which Version of the FlighCtrl do you have? I think 1.3 (Here is a 1.2 used)
I connected the LEDs to J16 and J17 of the FlightCtrl.
In your case you have to connect the LED from +5V (Servo) to Pin 1 or/and Pin 5 of the “Servo and LED” Port. So you can control the LEDs by the MK-Tool. (Ports PC2 and PC3). The direction of the LED has to be from +5V to the Pins.
A 100Ohm Resistor to limit the current is already integrated to the design.
Hope that is what you wanted/expected.
(For details see schematic of FlightCtrl 1.3 in the Wiki http://www.mikrokopter.de/files/Flight-Ctrl_1_3_doku.pdf)

Greetings, Speedy

By: Dimitri

Dimitri — Tue, 27 Jan 2009 11:07:02 +0000

Hi Speedy. Could you please explain how did you connect two bright LEDs on Flightctrl board? I? I understand right, they works in parallel with original green and red leds on the FC?
On board layout connector named as “SERVO and LED”, but there is viltage on pins.
Thanks

By: Speedy

Speedy — Wed, 24 Sep 2008 11:55:02 +0000

Hi Serge,
Oh – Sorry my fault – You should connect the SerCon additionally to the connection of FC and FlightCtrl (I’ve thought of something different, when I explained that before).
So you should use a cable that connects all three components: FlightCtrl, NaviCtrl and Sercon.
Greetings,
Speedy

By: Serge

Serge — Wed, 24 Sep 2008 11:11:42 +0000

Hi Speedy,

Yes but SV1 is I2C interface and not SPI. If I disconnect SV1 and just leave SV5 (SPI) it does not work. So maybe I leave SV1 but cut the Tx and Rx pins and use those for connection to sercon?

It seems both SPI and I2C interfaces are used between FlightCTRL and NaviCTRL?

Thanks,
Serge

By: Speedy

Speedy — Mon, 22 Sep 2008 19:33:40 +0000

Hi Serge,
It is possible to connect only the SPI interface of the FC to the NaviCtrl and the serial interface to the SerCon. If you want to debug the NaviCtrl values, you can connect the SerCon to the debugging connection on the NaviCtrl. The MK-Tool will detect the NaviCtrl and display the debug values of the NaviCtrl.

Hope that this was useful for you,
Greetings – Speedy

By: Serge

Serge — Mon, 22 Sep 2008 11:49:44 +0000

Hello again,

When NaviCTRL is connected to FC, where to connect sercon for deugging with KopterTool? Do I have to disconnect NaviCTRL?

Thanks,
Serge

By: Speedy

Speedy — Sun, 14 Sep 2008 15:31:46 +0000

Hi Serge,
Yes, that’s no problem. The communication of the FC and the NaviCtrl is based on SPI, so the second UART (which isn’t present on the FC 1.0) is not really necessary.

By: Serge

Serge — Sun, 14 Sep 2008 14:18:48 +0000

Hello Speedy,

Do you know if the NaviCTRL will work with the FltCTRL v1.0 ?

Thanks,
Serge

By: Speedy

Speedy — Sat, 19 Jul 2008 10:37:46 +0000

Hi Olivier,
The MKGPS1 board is a prototype, which is currently tested by the Mikrokopter - Betatesters. It is a board with an UBLOX chip (LEAH4). It will be available in the MK-Shop in the next month(s).
Details of the Ublox-Chip and GPS in general you can find here: http://www.u-blox.com/
The board is nearly the same as the GPS-mouse described in this article: http://speedyweb.at/start/2007/08/13/gps-mikrokopter-i/

Greeings,
Speedy