I did a Beckhoff TwinCAT3 motion training course a couple of months ago. To be honest, it was a little tough going as it was my first sight of Beckhoff and I could have used a more elementary course first. Added to that, I'm getting older and I'm struggling to retain new information.
I'm reviewing the training programs we worked on and I'm having difficulty understanding one part and wondered if some kind soul would take a look.
I've uploaded the solution archive here:
https://file.io/YUPOFu
My question is this; the visualizations use a structure of type ST_HMI_Axis. I can see it's instantiated in the Interface Editor tab of the VISU VFM_Axis_Ctrl:
VAR_IN_OUT
stHMI_Axis: ST_HMI_Axis;
END_VAR
However, that's the only place I can see it. The POUs (P_Axis1 & P_Axis2) use a variable gHMI.Axis_1 (also a structure of type ST_HMI_Axis) to pass the HMI data to the program. It must be the same data, coming from the visualization but I cannot see how stHMI_Axis is linked to gHMI.Axis_1 & gHMI.Axis_2. Could someone explain the mechanics to me, please?
I'm reviewing the training programs we worked on and I'm having difficulty understanding one part and wondered if some kind soul would take a look.
I've uploaded the solution archive here:
https://file.io/YUPOFu
My question is this; the visualizations use a structure of type ST_HMI_Axis. I can see it's instantiated in the Interface Editor tab of the VISU VFM_Axis_Ctrl:
VAR_IN_OUT
stHMI_Axis: ST_HMI_Axis;
END_VAR
However, that's the only place I can see it. The POUs (P_Axis1 & P_Axis2) use a variable gHMI.Axis_1 (also a structure of type ST_HMI_Axis) to pass the HMI data to the program. It must be the same data, coming from the visualization but I cannot see how stHMI_Axis is linked to gHMI.Axis_1 & gHMI.Axis_2. Could someone explain the mechanics to me, please?