Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always "Stabilised Flightmode" #8

Closed
Seeelefant opened this issue Aug 17, 2018 · 17 comments
Closed

Always "Stabilised Flightmode" #8

Seeelefant opened this issue Aug 17, 2018 · 17 comments

Comments

@Seeelefant
Copy link

Hi Eric,
so far everything is working fine. The only problem I currently have, is that I always get "Stabilised Flightmode" independent from the Mode I choose.

image

@zs6buj
Copy link
Owner

zs6buj commented Aug 17, 2018

Hi Seeelephant

Could you remind me what your setup is? Which version of the converter are you using?

Please un-comment Mav_Debug_Heartbeat and let's see what is coming from Mavlink?

@zs6buj
Copy link
Owner

zs6buj commented Aug 17, 2018

#define Mav_Debug_Heartbeat :)

@Seeelefant
Copy link
Author

Hi Eric,
I have version 1.01 running on a Teensy 3.2 in Air Mode. As debug messages I get
image

@Seeelefant
Copy link
Author

Re-Open :-)

@Seeelefant Seeelefant reopened this Aug 17, 2018
@Seeelefant
Copy link
Author

Re-Open :-)

@zs6buj
Copy link
Owner

zs6buj commented Aug 18, 2018

Hey Seeelephant

Unfortunately I cant see the detail on the image very well. Is it possible to give me a long .txt file with the debug messages in it? Please could you then switch modes several times during the test.

Thanks
Eric

@Seeelefant
Copy link
Author

Hi Eric,
sure:
LOG.txt

@Seeelefant
Copy link
Author

Hey Eric,
after looking at it and seeing that only ap_custom_mode changed, the problems seems to be related to athertop/MavLink_FrSkySPort#27.
Thanks
--Seeelefant

@zs6buj
Copy link
Owner

zs6buj commented Aug 19, 2018

Hi Seeelephant

Yes, flight mode is derived from ap_custom_mode on the mavlink heartbeat record, and also depends on the type of frame - ap-type. Obviously a quadcopter does not have the same flight modes as a fixed wing aircraft, an so on.

The LUA script determines the correct flight mode name and enunciation.

If there are other "sensors" on the bus, the Taranis and the LUA script need to decide which one to use for flight-mode. Alex (yaapu) can probably help with that.

Good luck
Eric

@Seeelefant
Copy link
Author

Hi Eric,
unfortunately Alex pointed back to you: yaapu/FrskyTelemetryScript#6 (comment). Seems that "Unfortunately these have to be decoded per flight stack. For PX4 you can find them here. https://github.com/PX4/Firmware/blob/master/src/modules/commander/px4_custom_mode.h#L45".

Can I modify your script? Where do I have to decode and send the the Flight Mode (which variable, format etc.)?

Best
--Seelefant

@zs6buj
Copy link
Owner

zs6buj commented Aug 19, 2018

Hi Seeelephant

Yes, Alex did talk to me. I'm working on it. I'll let you know.

@Seeelefant
Copy link
Author

Thanks Eric,

it´s highly appreciated :-) ....Thinking beyond it: It would be very nice to have all information in one place, sort of QGroundcontrol integrated within the sender....or..?

Best
--Seelefant

@Seeelefant
Copy link
Author

Hi Eric,
may I steel a some time again? I´ve seen that you made some PX4 correction, thank you. However currently PX4 has quite some problems with CAN buses. Therefore I switched to ArduCopter, but unfortunately this time things are reversed. I get perfectly the flightmodes and MAV-messages, but the sensors are empty:
img_9131
Please advice.
Best
--Seelefant

@zs6buj
Copy link
Owner

zs6buj commented Oct 13, 2018

Hey Seelefant
Have you set up the SRx parameters?

capture

@Seeelefant
Copy link
Author

Hi Eric,
looks much better now, thank you 🥇 👍
img_9133
Maybe you can add these settings to your Wiki, even Google does not know much about that.

May I ask another question:
Here https://github.com/Clooney82/MavLink_FrSkySPort/wiki/1.-Setup there is a section on "Combining Teensy with FrSky Sensors". Is this still possible with your solution?
Here https://github.com/Clooney82/MavLink_FrSkySPort/wiki/2.1.-Lipo-Singe-Cell-Monitor there are some remarks how to (mis-) use the Teensy for voltage measurement of the single cells. Could that be implemented within your environment? Which solution would you recommend?

Best
--Seelefant

@zs6buj
Copy link
Owner

zs6buj commented Oct 13, 2018

Hi Seelefant

I personally don't use any additional sensors, so I have no experience at all with them. I read your links, and I would suggest that you simply copy they way they did it there. The Taranis should pick them up.

For individual cell voltage measurement they are using a voltage divider resistor network onto analogue sensor pins on the Teensy. The theory is easy enough to implement, but you need very accurate resistors (kit) and possibly a lot of calibration. I'm happy to look at in the future, but we are about to move house, and then visit my son in Australia for a few weeks, so it won't be very soon I'm afraid. Maybe someone else wants to add that feature in the meantime. :)

@Seeelefant
Copy link
Author

Hey Eric,
well, there is life even beyond Quadrocopters. Maybe I can ask Alex on that topic and do some experiments myself. Drop me a line once your are back, we can have further discussions on that topic 👍 .
Best
--Seeelefant

@zs6buj zs6buj closed this as completed Oct 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants