Meaning of diagrams in online documentation

Hi everyone,

in the documentation I often come across diagrams like the one shown below, which is from Dependencies of library McPathGen.

While I expect that these diagrams are probably useful for building up an understanding of code organization, dependencies etc. I hardly understand what they actually illustrate. So far I also did not find a legend or guide that explains what is shown.

For example, I do not know what the edges indicate. They appear to be undirected, so they probably do not indicate dependencies? Is there information contained in the vertical/horizontal ordering of blocks? The section at the bottom of “library blocks” seems to show what kind of objects are defined in a library.

To be clear: I do not ask about the specific diagram I pasted here, it is just meant as an example. I am asking about this kind of diagrams that exist in many places in the documentation (at least for mappMotion that is the case).

There is also Library and module dependencies which perhaps is “the full picture”. It also has “dependencies” explicitly in the title. But how do the dependencies of McPathGen, for example, fit into this picture (see second screenshot)?

Would be happy to see explanations or pointers to a helpful legend or something like this.
Lukas

EDIT: typos

Hello,

These Pictures are illustrations for the Interfaces of the Motion System.

They also show optional connections such as between McPathGen and McProgInt.
They also show connections which are made by internal Software such as between AxesGroup and Axis.

These illustrations does not show the compiler dependencies of the Libraries.

It is more the idea behind. That an AxesGroup will connect to an Axis and interact with it during runtime.

McBase in this example is listed because it can interact with the Configuration of an Axis, AxesGroup, …

I hope this helps about the understanding.
Even as a B&R Expert i do not use them, as the information is typicaly found elsewhere, too. But it is a good overview.

Greetings
Michael

Thanks Michael for your explanations, but still my understanding remains too vague. For me, unless I learn how to read these diagrams, they are more decorative than illustrative.

This feels a bit annoying, as they look promising and helpful but so far did not provide relevant insights. This is the situation for me at least.

Perhaps I will appreciate them later, with more experience and some overview I developed by other means. For now I should probably just ignore them. Closing this topic for now.