Acro mode! And more...

[afernan]

@Adam: thanks for your offer. Max told me that but I didn´t want to bother you for 20$.

@Max. Not yet in OpenTx. I´m learning how to install the thing (it´s all new for me). I plan to do it along the WE with fw OpenTX 2.2.0 RC1 (N351). Then start testing, of course with HIL (great tool again!)

Best regards

Angel

[afernan]

OpenTx 2.2.0 RC1 (N351) working fine on my new HORUS!
All working well. Tested extensively with HILS

[afernan]

I´m trying to get basic telemetry with OpenTx 2.2 and my HORUS Tx.
Using M4/N4 USART2 (Tx,Rx in pwm7 & 8, no other outputs set to them) and the config shown below.

Using the adapter "Pixhawk to FrSky X4R/X4R-SB Telemetry Cable" from http://www.craftandtheoryllc.com/produc ... try-cable/

Then in "HORUS/MDL/TELEMETRY/Discover New Sensors" I get nothing but the basic onboard "RSSI, RxBt & A2" . Nothing from AQ exported telemetry as was suposed: Max pointed: "If you enable S-port telemetry but set "custom data" off, then you get basic things like voltages and location sent in standard FrSky format, meaning no special Taranis scripts are necessary."

Any help is wellcome
Angel

[Max]

I'm not sure Angel, it should "just work." I've had it hooked up to M4 serial port 2 as well (via N4 PWM pins), so that should be OK. Did you try switching Rx/Tx perhaps? Is firmware built with HAS_TELEM_SMARTPORT macro defined? Do you see "FrSky SPort init" message during AQ startup (maybe make/check MSG.LOG on SD card)?

I've never used the new "discover sensors" feature of OTx though (my Taranis still on v2.0). Main voltage/current (FAS), altitude/v-speed (vario), GPS, per-cell voltage (FLVSS), and (optionally) ACC data should be coming through as if they were being sent by the respective FrSky sensors. On my Taranis/OTx2.0 I just choose which values to show on the 3 telemetry screens available. I also set "voltage source" to "FAS" sensor (in model telemetry setup screen).

-Max

[afernan]

[Max]

The init message was probably just getting lost during startup, which is why I suggested checking the message log on AQ uSD card. You don't need to change any code for s-port to work.

Anyway, if you are getting the init message, the next thing I'd check would probably be the hardware connections & the adapter cable.

-Max

[afernan]

Got it!

...as always, you were right and your code was perfect.
I miss a +5V cable in the adapter pinout to make it work. For some (stupid) reason, I thought it was a pasive cable, but it´s not. So, now I get a few more sensors (13) from AQ, for the moment without any script.

Thank you very much for your work and your patient support.

Attached a small document "HowTo" summary. I´ll try to update wiki with that.

[jason0999]

Hi All,

Its great to see that Max is still around and working through queries with users, I would like to ask Max if he has anything new in the Pipeline as things have been a bit quite around here without him,

Kind Regards,

Jason.

[afernan]

Hi Jason:
Did you try Feature Integration branch, r1923? There´s lots of things to test, including HILs.

I can offer you to test GoTo preliminary implementation based on Max´s work. I´ve largely tested in HILs and real flight. It works perfectly. Just let me know and I´ll share the necesary fw and QGC.

Angel

[Patscherpofel]

Hi Max
bit off topic ,the pids you posted in the first post
is that something you fly? and if yes, what are the specs of that frame?
especially the very high angleP and low angleD made me curious

thanks!