We’re small, extremely agile, and malleable.We autonomously control many vehicles and vehicle types on multiple mission types and use cases – we do this on multiple media choices using multiple optional input devices communicate across multiple datalink and protocol options drive vehicles across multiple domains and apply multiple autonomy behaviors.One without the other is only a half-solution We’re more than just a pretty face – we combine an elegant Natural User Interface with some slick autonomy algorithms and behaviors.A streamlined and targeted common control station – it is not the Q-Ground Control behemoth.We get asked all the time, “What makes you different?” Our response: These “functional artwork” control stations support pre-mission planning/rehearsal minutes/hours/days ahead of any mission, mission-time execution command/control, and post-mission debrief/evaluation/training capabilities. This implies that system and software architectures must be able to provide trusted autonomy and this is a big part of our designs. The human operator can place controls on the software to let it run fully autonomously, provide suggested courses of action that the human must select, or require a great deal of human input. We attempt to make these visualizations of the system a piece of “functional artwork.” The human can either let the software run its course, or intervene to override or command some alternative action or behavior.

When it has communications reach-back to the human operators, a copy of that same software is running on a device in front of that human to provide visualizations that indicate to the human what the software has concluded and is executing. In the ideal scenario, the software is using various sensor input feeds to accurately sense its environment, divine a game plan, and automatically execute that game plan.

While software is our principal product, the combination of our software running on a mobile device, workstation, or on-board mission computer becomes the tangible product. We do this via software but of course the software needs a device to operate on. This is intended to take more of the cognitive burden off human operators/supervisors and serves as a force multiplier to make the human and machine a more capable team. The Autonodyne design is placing increasing autonomy in system computation.

Software wrapper defi