What "zero configuration" means

Traditional remote access to observatory equipment requires network configuration: assigning a static IP to the observatory PC, opening firewall ports, setting up port forwarding on the router, and often a dynamic DNS service. This works, but it's a setup burden, and it can break when the router or ISP changes something.

Which products it covers

This is currently available for Dragonfly customers, and users of the Solo CloudWatcher Android Widget. We'll add this to other products as soon as possible.

How the connection is established

Solo / CloudWatcher Widget

For the Solo/CloudWatcher Widget the system will just be "in the middle", so your weather data is available from anywhere. You can check it out in the Android widget for CW / Solo users guide.

Dragonfly

For the Dragonfly, as the connection is in both directions, the system follows a few steps:

1
Direct connection First it gives each part (the Dragonfly controller and your PC or smartphone program) the network direction of each other, so they can try a direct connection.
2
External addresses If that fails, the same but with the external, internet addresses—the ones of the router(s).
3
Relay If that fails, it will set up a relay, so our server will be in the middle during all the time, sending messages back and forth.

Please note relayed communications are costly. They are not intended for extended periods, so expect them to be limited in time in the future.

Even with this system, it is strongly recommended to have a computer connected to the Dragonfly in the observatory during the imaging sessions. Any remote connection, even if easy to setup, is not by far as reliable as a local one.

At your observatory

So, if you own a Dragonfly and want to try it out, these are the steps you have to follow.

  1. Download the new firmware (4.x) from the Dragonfly firmware & software page.
  2. Install it in your Dragonfly with the program—remember, just drag-and-drop it on the Dragonfly drawing in the MainDragonfly program window.
  3. Now install the new software.
  4. Run "Dragonfly Main"; once connected, go to Configuration → Controller configuration. You'll see a new section—fill it in please, and click Apply.

Nothing else needs to be done at the observatory. Once applied, your Dragonfly will register itself in the system and will listen for remote connections.

At the remote place

Well, "remote" is probably proper for the observatory, but anyway…

  1. Install the new software.
  2. Again, run Dragonfly Main.
  3. Go to Configuration—just configuration—and fill it in, using the same email. Make sure it is.
  4. Last, modify the network timeout, depending on the quality of the internet at your observatory. I'd try 1000 ms (so 1 second) to start with.

When connecting using the system, it will look for a Dragonfly (product), with your same key (email) and same name (dragonfly in the example—it could be whatever name). Click OK, and it will start trying to connect, using different methods.

The Controller internal configuration dialog. Network configuration with the controller name, listen and HTTP ports, DHCP and addresses. At the bottom, circled in red, the Use ZeroConf checkbox and the ZeroConf key (email address) field.
On the device—tick Use ZeroConf and enter your email as the key
The Configuration options dialog on the PC. Connect with controller address or name and controller port, with the network timeout circled, and below it the Zero Configuration Network group with the Use the ZeroConf network system checkbox and the same email address as key.
On the PC—same email, same name
The ZeroConf connection log window. Several Contacting ZeroConf server attempts reporting nodata and Nobody waiting at server, then a successful exchange of remote addresses and ports, and a final line reading Connected!
The connection log—early attempts fail until both ends are waiting

You'll then see a log window, shown mostly for our benefit: if you see anything weird, please capture the screen and send it to us. You can close the window when it has connected.

Last thing worth doing is changing the "refresh period" in the Dragonfly software (the control panel with all the relays and sensors) at home; not being the connection local, I suggest increasing the time to at least 500 ms.

And that's it!