FrSky support 3.0.1 R3

[michi1g]

Why was the FrSky telemetry support disabled? As I rebuilt my Quad I wanted to try out v3 which I am very satisfied with. I then noticed, that FrSky implementation was no longer available. Any possibility to get this feature back to work?

[smurfy]

It is not disabled, it's not implemented (yet).

3.0.1 is a new adaption of mpng. since v3 of arducopter it supports different hardware abstraction layers, which means the copter logic itself is seperate from the hardware its running on. (apm, pixhawk, mpng).

SirAlex created a new abstraction layer for the "all in one" boards. which works with almost the vanilla arducopter source just with different hardware.

stuff like sonar and frsky was added to the old version of arducopter before the hal layer. which means currently all additional stuff except the boards itself are not supported at the moment, if they are not already supported by ardupilots offical version.

Sonar support is beeing worked on in #32 but this is a bit different too.

Not sure about frsky tho. i guess its planned

[michi1g]

Already read the I2C Sonar thread. I wasn't aware of the HAL layer in v3. When I get it right, it's just an adaption to the new layout. Maybe I'll have a look at it and try my luck or just put an Arduino nano on my hexa to convert mavlink externally (jdrones ioboard firmware. Cheapest solution would be to be patient :-) Thanks for your reply!

[smurfy]

no problem, you can also readup here: diydrones/ardupilot#643

[SirAlex]

All additional stuff like Sonar, FrSky, EOSD was removed from 3.0.1 because we encountered problems with CPU performance. So I'm focused to solve this problems before all other features.

[NoRCexperience]

Since CPU load seems to be a constant issue and since losing a copter to a malfunction is horrible, can we please keep the base megapirate stripped down and then add functions to a 328 board on serial 1? I am running paku 2.9.1 with rs232-ttl on serial 1 for frsky but I am wondering why can't we move to the jdioboard model, do frsky code on 328 and add things like sonar calc and optical flow to 328. 328 can then pass final calculations back to crius, etc...? It would mean this dear flight controller can live longer and only cost $5 to add 328 board. Plus it would take care of other functions (led, frsky, etc..).

[doronby]

I like this idea of an AUX CPU. I have done it before on a work related project. We added a tiny atmega8 to the pcb to relieve CPU overload issues. It worked great and was very easy to implement ! This http://www.aliexpress.com/item/New-Atmega328-5v-Version-Pro-Mini-Module16M-For-Arduino-Compatible-Free-Shipping/1573159215.html seems like an easy $5 'fix'.

[ghost]

+1