Skip to content

Add HomePosition message and timestamp fields to telemetry#401

Closed
PavelGuzenfeld wants to merge 2 commits intomavlink:mainfrom
PavelGuzenfeld:feat/home-position-telemetry
Closed

Add HomePosition message and timestamp fields to telemetry#401
PavelGuzenfeld wants to merge 2 commits intomavlink:mainfrom
PavelGuzenfeld:feat/home-position-telemetry

Conversation

@PavelGuzenfeld
Copy link
Copy Markdown
Contributor

Summary

  • Add HomePosition message type with full HOME_POSITION MAVLink fields (local NED, quaternion, approach vector, timestamp)
  • Change HomeResponse.home type from Position to HomePosition
  • Add timestamp_us field to GroundTruth and Altitude messages

Note

Breaking change: HomeResponse.home type changes from Position to HomePosition. This requires a major version bump.

Split from #400 per review feedback.

Add time_usec field (uint64) to Altitude and GroundTruth proto messages
in both telemetry and telemetry_server protos. This exposes the
timestamp already present in the underlying MAVLink messages (ALTITUDE
and HIL_STATE_QUATERNION), enabling time-series analysis and log
correlation.

Fixes mavlink/MAVSDK#2391
Add a new HomePosition message to telemetry.proto that exposes all
fields from the MAVLink HOME_POSITION message (mavlink#242):
- Global GPS position (lat/lon/alt)
- Local NED position (x/y/z)
- Surface quaternion (q[4])
- Approach vector (approach_x/y/z)
- Timestamp (time_usec)

Change HomeResponse to return HomePosition instead of Position.

Fixes mavlink/MAVSDK#2310
@PavelGuzenfeld
Copy link
Copy Markdown
Contributor Author

Duplicate of #399, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant