Offline operation
Local software workflows that do not depend on an internet connection.
AUTONOMOUS SYSTEMS
Autonomous drone systems
RUSSIA
Software development for autonomous takeoff and landing without an internet connection, for drones used in film and cinema production in Russia.
FILM DRONES / AUTONOMOUS SYSTEMS
Beyond connectivity.
At the heart of motion.
Takeoff
Scroll or select a flight stage. Illustrative 3D flight sequence
Autonomous takeoff
Coding focused on the takeoff processes of film-production drones.
Autonomous landing
Addressing landing scenarios for the final stage of flight.
PROJECT FOCUS
Our engineering approach
We approach the takeoff and landing stages of film-production drones through software workflows that operate independently of an internet connection. The focus is on coding autonomous motion scenarios.
THE THINKING BEHIND THE PROJECT
01
Thinking beyond connectivity in film production
Our work on film-production drones in Russia starts from the reality that internet access varies between shooting locations. The project focuses on autonomous takeoff and landing scenarios handled through local software workflows. We aim to consider creative production needs and the operating conditions of the device within the same engineering framework.
02
Modelling motion as a connected process
The beginning and end of a flight are more than two isolated commands. We consider the sequence of motion, system state, transitions between scenarios and the handling of unexpected conditions together. Development scope is shaped around the selected platform and project requirements, with a focus on control logic that can be reviewed, understood and extended.
03
Connecting creative work with autonomous systems
Our long-term vision is to develop autonomous software as an engineering discipline that contributes to different production environments. Experience from film-related work informs our interest in reducing connectivity dependence and strengthening local processing capabilities. Each new scenario is considered on its own terms, with attention to the conditions and requirements that define its use.
FROM NEED TO SOLUTION
More than
a different screen.
Move the slider to compare the two approaches.
The need
- Variable connectivity on location
- Flight stages treated separately
- Platform-specific control needs
Our approach
- Focus on local software workflows
- Takeoff, flight and landing modelled together
- Control logic shaped by the scenario
Conceptual workflow diagram; not a product screenshot.
Next project
Menu & kitchen software↗04 / CONTACT