-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
SURFACE mode doesn't work #4776
Comments
I have mentioned this before |
Surface more is a modifier for altitude hold mode. It has to be enabled together with ALTHOLD or at earlier time. |
I've tried this way as well. See my first comment. |
Or do you mean that firstly I should enable SURFACE and only after this ALTHOLD? |
|
|
Best - take off in ALTHOLD + SURFACE mode |
Will try and reply in 1 hour. BTW, why max sonar range is only 60 cm? |
Crappy sonar hardware. INAV's limits for rangefinder/surface tracking |
Hm.. I'm using us100 + arduino. May there be limits in sketch? |
On a 3-5" quad US-100 gives 60-80cm range unless you use a very good soft-mounting (soft rubber) to isolate US100 from vibrations. |
I was testing range without arming. It just displays -1 write after exceeding 60 cm. That's why I think it is limited somewhere in code. |
That could be limited in Arduino sketch. INAV doesn't have this 60cm limit. |
Here is the sketch I use. For POSHOLD and GSC it (SURFACE) should be enabled simultaneously as well? |
@digitalentity It is definitely limited in the sketch. Playing with these vars PULSE_TO_CM 500, MAX_RANGE 500. Have no idea what is what, behavior is strange, but still))) |
@digitalentity Which behavior should I expect in POSHOLD and GSC modes (with SURFACE modifier)? |
Summarizing discussions from chat, I think the dependence on ALTHOLD is a major usability trap that could be resolved by quietly making SURFACE enable the altitude-hold code. ie pseudocode It is not clear to me what the benefit of keeping SURFACE as a modifier dependent on ALTHOLD, especially if you can't toggle it in flight. |
I agree that this is not very obvious way to switch SURFACE. |
I kind off have the same problem, sensor is a TFMini, however I see no effect of switching on surface mode even together with AltHold. Inav is version 2.2. |
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. |
Any news? |
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. |
Automatically closing as inactive. |
I‘m testing the feature SURFACE as well. But the behavior differs. I had activated SURFACE together with POSHOLD. Seems to work as expected. But sometimes I‘d like to activate POSHOLD without SURFACE. How to parameterize that in INAV configurator? |
Is anyone going to look into this issue? |
@georgekucher: Do you use this feature (SURFACE)? I‘m using the Matek sensor, see https://www.rcgroups.com/forums/showthread.php?3572803-Matek-Lidar-and-INAV. It works more or less. But I do not know how to activate SURFACE in combination with ALTHOLD or POSHOLD. |
Yes I have the same sensor.
I'm enabling it (SURFACE) before enabling ALT/POS HOLD and it works. Enabling SURFACE+ALT/POS HOLD simultaneously didn't work for me. |
I assume it will take a while for me to understand what you are doing. How many positions has the switch which is linked to channel 6? It seams that you control nearly everything with this switch. Right? |
I've mixed 2 3-pos. So 9 positions. |
It was my understanding that SURFACE mode has to be enabled before (or perhaps simultaneously with) ALTHOLD for the surface following mode to activate. SURFACE has no function when activated separately-- it's purely a modifier for ALTHOLD. |
Yes, I totally agree with you. Further more, the same should be done for POSHOLD+SURFACE |
Wait... does this work? You can get into surface following mode while in POSHOLD mode without ALTHOLD on? |
That's my aim. But it does not work. POSHOLD and ALTHOLD works, but without the lidar surface feature. And I thought I can activate the lidar surface feature separately. I assume that I have to try mixing channels to achieve that. I up to now I haven't used the channel mix feature. |
Yes |
Actually I can get into POSHOLD while it SURFACE |
Try it this way. Using two three-pos switches, Switch 2: |
This is my config now |
I have the same. Only with 16 channels and a bit different switches upgrade |
Great! May you be so kind and tell me how to parameterize the mix? I‘d like to use two of my 3 position switches to do what you did. Setup has to be performed in the radio. Right? |
I'm a bit confused why this overly complicated setup is necessary. For example, if you drop the need to fly in althold modes without poshold active (when nav_user_control_mode is set to ATTI, which is the default, you get angle-mode control while in POSHOLD anyway), you could do this: Switch 1: Position hold modes Switch 2: Autonomous navigation modes I don't have the ability to test this right now, but as far as I can tell, NAV WP and NAV RTH override ALTHOLD anyway to follow their programmed waypoints or return-to-home behavior. |
The thing is that I don't want to drop flying in ALTHOLD. This is why I mixed switches into 9pos |
Have you ever seen this strange behavior with SURFACE & POSHOLD and full throttle? |
Hm.. |
No I didn't.
My performs very likely. |
This has now veered far off topic, but IR rangefinders can have difficulty in full sunlight. Also ensure this condition is met from the Matek datasheet:
|
Thanks anyway... |
I know this is a necro but i just want to say that the current behaviour is really bad, even more it's dangerous.... Currently when i switch from poshold to surface + PosHold it just go acro ( i understand that now reading you all ). Now i'm trying to make this work fine but i don't realy found a nice solution. In fact what it should be and i want to know if you agree is :
|
Current Behavior
Quadcopter doesn't hold fixed altitude above the surface in SURFACE mode. Log is attached. Please help.
LOG00067.TXT
Steps to Reproduce
1.Arm and take off
2.Enable SURFACE mode
Expected behavior
Copter is expected to hold altitude above the ground when SURFACE mode is being enabled.
Suggested solution(s)
Maybe it is disabled for my target..
Additional context
Dump
The text was updated successfully, but these errors were encountered: