All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Alfred GPS higher update rate
Date: Thu, 22 Oct 2015 02:53:25 +0200	[thread overview]
Message-ID: <20151022005325.GB930@lunn.ch> (raw)
In-Reply-To: <CAKaWdxbrS90fbV4if4ZhRYtdL-neikMc4iVb_EtowJf8M=9dvg@mail.gmail.com>

On Thu, Oct 22, 2015 at 11:07:48AM +1300, Keith Chew wrote:
> Hi
> 
> I am experimenting with using Alfred on a group of drones (initially
> 10 units) to send their GPS locations to each other.
> 
> The drones will be connected via batman-adv on WIFI, and each of them
> read the GPS every 200ms (5Hz).
> 
> I would like to change alfred-gpsd from updating the GPS coordinates
> every 10s to 200ms.
> 
> Does anyone see any issues with this change? ie it is even feasible/practical?

You need to change more than alfred-gpsd. The core alfred server does
updates every 10 seconds. You need to change ALFRED_INTERVAL so that
it will propagate GPS data faster. If you want 200ms, i doubt such a
change would be accepted back to the core code. So you probably need
to add a command line option to allow setting this interval.

alfred-gpsd will also need some changes. It currently updated the
information in alfred every 2 seconds. You will need to modify this as
well.

When i wrote the alfred-gpsd code, i was not particularly interested
in fast updates. So you might need to change the architecture a
little. In particular, i knew gpsd was giving fixes much faster than
alfred would distribute them, so i didn't tell alfred about every
change. You might need this.

	Andrew

  reply	other threads:[~2015-10-22  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 22:07 [B.A.T.M.A.N.] Alfred GPS higher update rate Keith Chew
2015-10-22  0:53 ` Andrew Lunn [this message]
2015-10-22  1:03   ` Keith Chew
2015-10-22  1:14     ` Andrew Lunn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151022005325.GB930@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.