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

No more upload when LINK is red #820

Closed
dewagter opened this issue Sep 3, 2014 · 7 comments
Closed

No more upload when LINK is red #820

dewagter opened this issue Sep 3, 2014 · 7 comments

Comments

@dewagter
Copy link
Member

dewagter commented Sep 3, 2014

When your ground station shows link-timeout (RED) after 5 seconds, then you can also not send any new command, flightplan, setting, ... to the plane...

When you have LEDs on your modem you can clearly see that as long as LINK is green, a flightplan command (e.g. standby) is being sent, but as soon as LINK goes RED, it does not send anything anymore.

Surely this is not intended? Do you know if this is a LINK / SERVER / GCS issue

@gautierhattenberger
Copy link
Member

It seems to be a "feature" from 2007.
Question: what do we want ?

@dewagter
Copy link
Member Author

dewagter commented Sep 4, 2014

In our case we absolutely do NOT want it: when a UAV is far away and
telemetry gets bad, it should at least ATTEMPT to still upload commands
(even tough they might not arrive: if you dont send them they will
certainly not arrive)

In which cases is it better not to send?

-Christophe

On Thu, Sep 4, 2014 at 11:29 AM, Gautier Hattenberger <
notifications@github.com> wrote:

It seems to be a "feature" from 2007.
Question: what do we want ?


Reply to this email directly or view it on GitHub
#820 (comment).

@gautierhattenberger
Copy link
Member

When an aircraft is landed and stopped, you don't want to send/need to send messages to it (PING, TRAFFIC_INFO, WIND,...).
I guess the correct way is to really kill the A/C (from GCS, server, link) when the user actually don't want to see it anymore, and continue sending otherwise.
Easy solution: make an option for link to set the timeout (0 for disabled)

@OpenUAS OpenUAS added this to the v5.6 milestone Nov 3, 2014
@flixr flixr removed the New feature label Nov 24, 2014
flixr added a commit that referenced this issue Apr 28, 2015
If no messages are received from an aircraft for some time (default 5000ms=5s),
it is regarded as dead/shut_off and no uplink messages will be sent to it anymore.
Use the `-ac_timeout` paramter to set the timeout in ms. Set to a negative number to disable.

See issue #820
@flixr
Copy link
Member

flixr commented Apr 28, 2015

Added the -ac_timeout parameter to link with a0bee87 and 25d975e, if you set it to zero, the aircraft should never be regarded as dead and uplink never disabled.
Is that enough to close this issue, or do you want add something to completely remove/kill an AC from the ground segment?

@gautierhattenberger
Copy link
Member

@dewagter does the timeout fix enough to close the issue?

@gautierhattenberger
Copy link
Member

closing due to feedback timeout

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants