Yury Kapacheuski

@hamishwillee I'm actually happy with MAV_FRAME_{ORIGIN_LOCATION}_{FRAME_ORIENTATION} Frames format. By the way, I think that needs to be added additional orientation options like NAV. So with the origin of the body...

@hamishwillee Yes, but I think "BODY" should not confuse in terms of frame "origin", It just points to the center of mass of an object. > The [RFC](https://github.com/mavlink/rfcs/pull/2/files) makes it...

@hamishwillee Thanks for the detailed explanation now it is much clear. So I will use it with care :) By the way what about @chobitsfan question? So we should use...

@dakejahl Hi. About LOCAL_NED - I think it has some advantages to use it as a case of target movement. For example, a landing system can have an internal filter...

@hamishwillee according to the discussion maybe it is possible to make as I proposed before in the [comment](https://github.com/mavlink/mavlink/pull/1737#issuecomment-1233784507)? Perhaps it has the sense to replace BODY with UXV and LOCAL...

@hamishwillee Hi. > The dev call think these are not the right changes - i.e. there is no appetite to add more frames unless there is a use case that...

@chobitsfan Hi. It looks like we are thinking some way! I think it needs to be implemented. By the way, we need to keep in mind that the distance to...

@rishabsingh3003 Hi. Thanks for the review! Sorry for the mess - it my first PR in Ardupilot. > There are some extensive changes to the library's front end (AC_PrecLand.cpp). In...

Hi @chobitsfan It looks good! By the way, we are talking with @rishabsingh3003 according to the structure of PrecLand. Maybe it needs to change the Backend completely to support different...

Hi. Yes, actually, it is important functionality. I'm working on it as well. But IMHO it needs to be fixed in the backend and precision landing algorithms. In my case...