Operating several DragonFlies

Why unique names matter

Each DragonFly on a network must have a different hostname. If two units share the same name (the factory default is "Dragonfly"), the software cannot tell them apart and will connect to whichever one answers first. Set a unique name for each controller before connecting them to the same network segment.

To rename a DragonFly, open the DragonFly Configurator and go to General Settings → Device name. Choose a descriptive name relevant to its role (e.g. "dragonfly-roof", "dragonfly-dome2"). The name must be a single word with no spaces.

Switching between units

The DragonFly software connects to one controller at a time. To switch between controllers, change the Connect with controller name setting in the software's connection panel to the target device's hostname. The software will then connect to that specific unit on its next connection attempt.

Second DragonFly—software and port

For continuous operation of two units simultaneously (two separate observatories, or two roles in the same observatory), you need a dedicated software install for the second controller:

1. Run the dedicated secondary installer—this installs the DragonFly application in a different directory and registers it as a separate executable. Do not use the primary installer for the second unit.
2. The default name for the second unit is "dragonfly2". You can change this in the secondary application's configurator.
3. The secondary application uses port 10001 by default (the primary uses port 10000). This allows both to run simultaneously on the same PC without port conflicts.

Scripting with two DragonFlies

In macros and scripts, the standard DragonFly scripting object targets the primary controller. For the secondary unit, use the Dragonfly2nd object instead:

-- Primary controller:
Dragonfly.rl[0] = True

-- Secondary controller:
Dragonfly2nd.rl[0] = True

This applies to relay commands, sensor reads, and all other scripted interactions. Use the correct object to target the intended unit.

Current limitation of the secondary version

An alternative: the Multiple DragonFly application

We're also developing a separate Multiple DragonFly application—a convenient control panel for any number of DragonFlies. It's not yet fully finished, but it's available to try here, and we welcome you trying it out and contributing ideas or suggestions. Features not yet supported: