-
Notifications
You must be signed in to change notification settings - Fork 165
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
mDNS for common hostname #15
Comments
Please provide a description |
Even better should be apsync_MAVID ! Even if the more general use case is to use one uav, in case of multi drone it will be better! |
On Fri, 3 Feb 2017, khancyr wrote:
Even better should be apsync_MAVID ! Even if the more general use case is to
use one uav, in case of multi drone it will be better!
Interesting point you raise there about multiple drones.
When we start to allow configuration as a WiFi client we'll definitely
look at that. At the moment a simple "ssh into the machine called apsync"
is what I'm after :-)
Question: what mavlink sysid were you thinking of using there? At the
moment there's the PixHawk's, one for mavproxy and another one you don't
see much of for the dataflash logger......
|
@peterbarker I am thinking about autopilot id so pixhawk id ! What I did on my swarm is : each drone have the same ip and mavlink id, that way it is simple to remember and each got their mavid in their hostname ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are moving to have a common hostname for the apsync image ("apysync" in place of "edison" or "pi" or "ubuntu-nvidiatx1").
We should advertise the presence of this host on a local network using mDNS, allowing people to
ssh apsync@apsync
rather thanssh [email protected]
The text was updated successfully, but these errors were encountered: