Components structure

[PTKu]

How should the components be structured?

There is some general idea of how the components should look in terms of structure that derives from early discussions.

There is some description in the conventions that needs to be widened.

Some idea about the execution of the tasks is here

Other discussions did run in Slack channel (TAP pattern - async calls of tasks ...)

What we will need to narrow down is the parameter transfer, parameter persistence etc.

[PTKu]

in #60 (comment)
@runtimevic wrote

Hello,
I think that all the components should have a certain structure, for example like the motion PTP axis that I have sent to Tomas
estructure components:
.- Config o settings,
.- Status,
.-Commands,
.-Diagnosis o error,
.- Etc...
example:
stControl: ST_AxisControl;
stStatus: ST_AxisStatus;
stConfig: ST_AxisConfig;
stError: ST_AxisError;
stInputs: ST_AxisInputs;

[PTKu]

Proposal from @runtimevic*

https://github.com/runtimevic/TcOpen.Documentation/blob/dev/articles/Conventions/Conventions.md#components-struct

We need to describe it in more detail, I have a rough idea of what you mean, however, to narrow down the meaning of those structures I have some questions in italic

Components STRUCT:

a component will consist of the following structure:

Config

This seems clear. The structure should contain eventual configuration data for the component
Is this a one-time configuration? Once assigned does not change (immutable) or can change at runtime after assigned?

Control:

What should be in this structure and what is the purpose of its?

Status:

How should this look like? Some components can have multiple states at once (we have TcoTask to provide some status information)

Error:

How do we structure Errors (Last error, error history, buffer)? (how would this add to existing messaging (_mime) or is this meant differently (error lists?)

Inputs:

Outputs:

For complex I/O this should this be VAR_IN_OUT?

[runtimevic]

I think we have converted by , have a look here for example. We may also merge into TcoTask. @runtimevic will try to write it down in a document, today busy, hope will make it by the end of the week... keep the discussion running... One side note I think the drive component is complex enough and good for the discussion, let's keep in mind that we will need to abstract from a specific component.Control``TcoTask``Error

Hi @PTKu ,
https://github.com/TcOpenGroup/TcOpen/blob/feature/TcoDrivesBeckhoff/src/TcoDrivesBeckhoff/src/XaeTcoDrivesBeckhoff/TcoDrivesBeckhoff/POUs/Prototypes/TcoDriveSimple/MotionTasks/MoveAbsoluteTask.TcPOU
MoveAbsoluteTask.TcPOU -- I think that it is not part of a good data structure to be organized and to be able to work correctly with the PTP axis.....

[runtimevic]

https://github.com/TcOpenGroup/TcOpen/tree/initial-dev/src/TcoPneumatics/src/XaeTcoPneumatics/TcoPneumatics/POUs/Cylinders

Cylinders -- passes equal to cylinder does not have a well defined structure

[runtimevic]

I think time should be spent creating a good structure that is the most similar for all components, so that everyone would have the same parts, although of course it is within each structure there would be their particular signals but they would be defined in their corresponding place...

[PTKu]

I think we have converted by , have a look here for example. We may also merge into TcoTask. @runtimevic will try to write it down in a document, today busy, hope will make it by the end of the week... keep the discussion running... One side note I think the drive component is complex enough and good for the discussion, let's keep in mind that we will need to abstract from a specific component. ControlTcoTaskError

Hi @PTKu ,
https://github.com/TcOpenGroup/TcOpen/blob/feature/TcoDrivesBeckhoff/src/TcoDrivesBeckhoff/src/XaeTcoDrivesBeckhoff/TcoDrivesBeckhoff/POUs/Prototypes/TcoDriveSimple/MotionTasks/MoveAbsoluteTask.TcPOU
MoveAbsoluteTask.TcPOU -- I think that it is not part of a good data structure to be organized and to be able to work correctly with the PTP axis.....

@runtimevic you need to be more specific...

[runtimevic]

Hello,
create a Cylinder proposal STRUCT......
proposal of component structure, for example the cylinder component has been chosen, but the PTP axis could also have been made, I hope this helps to make everything clearer ...
#75

[PTKu]

Have also look here #75