Landing gears: Discussion on remaining issues

[MarAlder]

There will be a working group to exchange on the following remaining issues w.r.t. the new landing gear definition #632:

• linking with controlDistributors
• naming of parent nodes
• extensibility, e.g. Oleo
• exotic landing gears

Conact cpacs[ät]dlr.de to get your login to the online meeting on Tuesday, 09/03/2021 at 09:30-11:30. Any contribution is very welcome.

[MarAlder]

Compare the following status updates with the modified example file.

Linking with controlDistributors

Please have close look at the current implementation. In the case of binary functions (braked/unbraked) I propose to use a simpler implementation omitting the steps:

Naming parent nodes

In our last working group meeting we decided to implement the landingGears/landingGear approach.

Extensibility, e.g. Oleo

In the working group meeting we concluded that a potential extension is possible in future.

Exotic landing gears

We identified that knee landing gears can not be modeled in detail. However, due to missing use-cases we decided to stick to the current implementation.

[MarAlder]

Naming of parent node for retraction, steering and braking

What do you think? control, actuation,global, something else? I think one of control or actuation describes it quite well and distinguishes it a little bit from the meaning of global in other places of CPACS.

Remaining open points:

• Feedback on linking with controlDistributors
• Naming of parent node for retraction, steering and braking

[HHOPs]

I would prefer to name the base node control - as the component functions below this node are not necessarily always based on actuation etc.

As for the linking of the respective LDG-control-functions with the controlDistributors - e.g.:

<commandInputs mapType="vector">0;1</commandInputs>
<controlElements>
    <controlElement>
        <controlDeviceUID>extPathLG1</controlDeviceUID>
        <controlParameters mapType="vector">0;1</controlParameters>
    </controlElement>

from the controlDistributor section links via UID with

<extensionPath uID="extPathLG1">

This allows for a consistent uID search. When found it is clear, which action is linked with the respective parameters...

In general, this is a very good and well required method of linking parameters and actions/functions - therefore OK for me! Thanks Marko for the proposal and rapid way forward!

[MarAlder]

Thanks for all your contributions. I think we can work with this definition now.