Skip to content
This repository has been archived by the owner on Feb 19, 2021. It is now read-only.

Handling of system ID: default, from conf file or from autopilot #149

Open
lbegani opened this issue Mar 27, 2018 · 3 comments
Open

Handling of system ID: default, from conf file or from autopilot #149

lbegani opened this issue Mar 27, 2018 · 3 comments

Comments

@lbegani
Copy link

lbegani commented Mar 27, 2018

@hamishwillee @SaliniVenate
For System ID, this could be a strategy to follow for CSD -

  1. Read from the conf file (-1 : read from network, >=0 : use as it is )

    • If conf file is not there, use some default value (1)
  2. Read from the network (if system ID is set to -1 in conf file)

    • Start sending camera heartbeat with default system ID (1)
    • On receiving autopilot heartbeat, send camera heartbeat with updated system ID.
    • On receiving heartbeats from multiple autopilots, stick to the first one
@hamishwillee
Copy link
Contributor

Sounds good to me. In 90% of cases this will be connected to autopilot with sys id 1 and this will just work.

The only problem I see is the case of multiple autopilots (small fraction of time) - should we somehow report/log multiple autopilots on the network so users can know this is a possible problem?

@lbegani
Copy link
Author

lbegani commented Apr 23, 2018

@hamishwillee Can we close this issue?

@hamishwillee
Copy link
Contributor

Nearly. Can you update the defaults in the sample file - https://github.com/Dronecode/camera-streaming-daemon/blob/master/samples/config/config.sample#L20 e.g. system id default is now effectively 1.

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

No branches or pull requests

2 participants