Your mission
Connect third-party autopilots and sensors to our robotics stack and make the ROS 2 ↔ MAVLink ↔ PX4/ArduPilot command/telemetry loops rock-solid in the field. This is a middleware & interfaces role: build the bridges, prove reliability, and ship to hardware, beyond lab demos.
- ROS 2 ↔ MAVLink bridges in production (heartbeats, params, missions, telemetry) with latency/jitter within budget, controlled packet loss, metrics and alerts in place. Measure: traces, dashboards, field endurance tests.
- Sensor integration (GNSS/IMU/camera/LiDAR/radar): acquisition, time sync, correct frames, clean interfaces to the autopilot and our ROS nodes. Measure: bag replays, end-to-end validation.
- Embedded deployment (Jetson/ARM): reproducible CI/CD images, versioned releases, rollbacks, watchdogs, health checks. Measure: crash rate, MTTR, stable field runs.
- Write/maintain ROS 2 nodes for sensor drivers, message transforms, and PX4/ArduPilot interfaces.
- Implement MAVLink flows (HEARTBEAT, PARAM, MISSION, ATTITUDE/IMU, failsafes), manage routing and custom messages where needed.
- Own operational reliability: DDS QoS, retries, heartbeats, watchdogs, link loss recovery, structured logging and tracing.
- Drive Git-centric delivery (PRs/reviews/tags), packaging with colcon/containers, deployment scripts, and bag replays for integration tests.
- Conduct weekly to biweekly field tests with live hardware. Validate software changes under operational conditions, debug in the field, and iterate based on flight performance data.