Axis Interface: MB_AxisInterfaceBase Inputs

[bkautzman]

When I add the MB_AxisInterfaceBase function block to my Ladder program there are four inputs displayed that are not listed in the documentation(iOpMode, bStart, udiCycleCounter, CmdDoneInternal and DynLimDoneInternal).

I have been unable to find any information about these inputs, other that the tooltip text that appears when hovering over each of them. There’s no information about them in the ctrlX PLC Library Reference documentation and they also don’t appear via Intellisense when I add the same function block in a Structured Text program. The equivalent block in the MLC, MB_AxisInterfaceType01, does not display these additional inputs when added to a ladder program.

Does anyone have information about these properties?

[Jochen_Mueller]

Wy are you not using the standart way to insert the MotionInterface? So you don't have to care about the "internal" FBs...

The insert will

• add a MotionInterface program to the project
• and change the tast configuration
  
  • add MainTaskMotIF and call the main AxisInterface program (and some demo progs which can be deleted)
  • add a MotionTask, in which a possible motion sync prog part of the motion interface will be called.

Now you can easily command axis by

• writing the global command array stuct
• reading the global status array struct. 

Regards

Jochen

[bkautzman]

Hello Jochen,

Thank you for your response.

I am well aware of the standard way to add AxisInterface functionality to a project and I will be encouraging my customer to use this method. They were used to adding the function block directly in IndraWorks and this question arose after testing in the ctrlX ecosystem.

I would still like to understand why these inputs are displayed in this manner. Despite being an "internal" function block, it is still available to a user and is listed in library documentation. 

[Jochen_Mueller · Accepted solution]

@bkautzman 

The mentioned inputs are only for internal use. These inputs should not be displayed (“attribute 'conditionalshow'”). But in LD unfortunately it will be visible. In ST not. (see Screenshot) We will check this behavior and try to find a way that this inputs always not visible. 

Regards

Jochen

[AndreasL]

Refactor them as properties and they will not be visible in LD (and will also be 100% compatible), and also if they are internal they should be marked as internal: