obicons

Consider packet time in obstacle distance message

6

This attempts to address the concern that I raised in [this issue](https://github.com/ArduPilot/ardupilot/issues/21291). I realize this solution might not be perfect, but I hope I can be advised further in this...

Use packet timestamps where possible

1

Updated message handlers that populate structs with `sample_timestamp` fields to use the timestamp supplied by the packet. This matches the behavior already exhibited by other message handlers. ## Describe problem...

Removed old ulanding driver

1

There was an old ulanding driver, which could be enabled by defining the `ULANDING_VERSION` symbol. I propose we remove this old code. I did some `git blame` sleuthing, and it...

`handle_message_set_gps_global_origin`: use packet timestamp

1

[`handle_message_hil_state_quaternion`](https://github.com/PX4/PX4-Autopilot/blob/dfdfbbfa9ce7de0d644b6ee11d54102a7a3bc486/src/modules/mavlink/mavlink_receiver.cpp#L2749) sets `timestamp_sample` to `hrt_absolute_time`. Instead, we should use `mavlink_timesync` to synchronize the packet's timestamp and use this value for `timestamp_sample`. I'll open a PR if we agree this is...

## Describe the bug In [`handle_message_landing_target`](https://github.com/PX4/PX4-Autopilot/blob/30e2490d5b50c0365052e00d53777b1f4068deab/src/modules/mavlink/mavlink_receiver.cpp#L2420), the created `irlock_report` has a timestamp set to the receiver time. I think this should be set to the time reported by the system,...

Timestamp format of `mavlink_hil_optical_flow_t` not properly handled

2

## Describe the bug In [handle_message_hil_optical_flow](https://github.com/PX4/PX4-Autopilot/blob/8cc6d02af324ba713beb80b374236f70ac7f0a9a/src/modules/mavlink/mavlink_receiver.cpp#L856), the `sensor_optical_flow` timestamp is assigned `flow.integration_time_us`. But `flow.integration_time_us` could be in any format -- time since system boot or UTC. The representation should be...

## Describe the bug Inside of the message handler for [`handle_message_hil_gps`](https://github.com/PX4/PX4-Autopilot/blob/8cc6d02af324ba713beb80b374236f70ac7f0a9a/src/modules/mavlink/mavlink_receiver.cpp#L2362), the `time_utc_usec` field is written to with the value of the message's `time_usec` field. This is incorrect because [MAVLink...

## Describe the bug In [this file](https://github.com/PX4/PX4-Autopilot/blob/8cc6d02af324ba713beb80b374236f70ac7f0a9a/src/modules/mavlink/mavlink_receiver.cpp#L1855), the timestamp of an obstacle distance message is ignored. If there is transport delay or a buggy component, then an incorrect timestamp can...

As mentioned in the Readme, storing passwords in plaintext on the FS isn't exactly secure. Obviously, this issue can help be reduced by using proper permissions on the file. In...

Re: Issue #147

1

* `UNINSTALL` can now accept a list of systems to remove * `UNINSTALL` can now optionally and safely remove a system's dependencies