Skip to content

T-00

The engineering beneath the picture.

An operational picture is only as good as the systems that produce it. These are the technical domains JEISYN works across, and how they relate to one another.

T-01

Eight domains, one system.

Select a domain to see what it is responsible for, what it depends on, the technologies of interest, and the limitations we design around. Technologies are listed as areas of interest — not as a statement of what is already integrated.

Technology domains · select a layer

T1Conceptual· provisional

Robotics & flight systems

Reliable vehicle control is the foundation: flight controllers, failsafes, geofencing and predictable behaviour under fault conditions.

Inputs
  • Setpoints
  • IMU / GNSS / barometer
  • Failsafe policies
Outputs
  • Stable flight
  • Vehicle telemetry
Key dependencies
  • Hardware platform
Technologies of interest
  • PX4 autopilot
  • MAVLink telemetry & command protocol
Limitations
  • Platform-specific tuning and certification are required for each airframe.

T-02

What each domain contributes.

T1

Robotics & flight systems

Airframes, autopilots, safety envelopes.

Reliable vehicle control is the foundation: flight controllers, failsafes, geofencing and predictable behaviour under fault conditions.

  • PX4 autopilot
  • MAVLink telemetry & command protocol
T2

Perception & sensor fusion

Combining RGB, thermal, LiDAR and inertial data.

Fuse complementary sensors so that each compensates for another's blind spots — thermal through low light, LiDAR through low texture, cameras for semantics.

  • RGB and radiometric thermal imaging
  • LiDAR
  • Visual-inertial odometry
T3

Spatial mapping & 3D reconstruction

SLAM, photogrammetry, elevation models.

Turn sensor streams into geometry: localisation and mapping in flight, and dense reconstruction after capture.

  • SLAM
  • Structure-from-motion
  • Multi-sensor registration
T4

Multi-agent coordination

Several vehicles, one objective.

Share state and intent between vehicles so they divide work, avoid conflicts and adapt when one of them drops out.

  • Market-based / auction task allocation
  • Decentralised consensus
T5

Mission planning & optimisation

Coverage, energy and time trade-offs.

Plan routes that cover an area efficiently given battery limits, sensor footprints, terrain and no-fly constraints.

  • Coverage path planning
  • Vehicle routing with energy constraints
T6

Edge computing

Compute where the data is produced.

Run filtering, compression and inference on the vehicle or a field server so operations do not depend on cloud connectivity.

  • Embedded GPU modules
  • Containerised field servers
T7

Communications & networking

Local-first, resilient links.

Keep vehicles and operators connected over local IP networking, prioritising critical messages and tolerating dropouts.

  • ROS 2 / DDS middleware
  • Local IP mesh networking
T8

Operational visualisation

Making complex state legible.

Present layered spatial data, fleet state and uncertainty so operators can make fast, well-founded decisions.

  • WebGL 3D terrain
  • Layered map views
  • Mission timelines

Names such as ROS 2, PX4 and MAVLink refer to open-source projects and protocols of technical interest. Their mention does not imply affiliation, endorsement, or that they are integrated into a production JEISYN system.

See the domains working together in ReconGrid.