Execute Addon (EXTENDS OpconAddonExec) command from HMI. Object development.

[maj9bj]

My addon extends OpconAddonExec that means I implemented some commands I can execute from my code or chains. I would like to add HMI button which can execute command in manual mode in the same way like standard objects do.
But I do not know how to handle this. Should I create addon extension for manual mode?

[Thorsten_Brach]

Hello Jiri,
for addons there is no separation like between units and extensions.
You would have to work with your HMI directly on the addon and for your manual release ,
you could ( for example ) use a reference in the ParCfg.

I hope that answers your question ?

[maj9bj]

Hello Thorsten, I need to know where and how to map manual function key from HMI.

And where to place code which sets in manual mode ParCmd and executes addon command. For standard objects this is placed in Man+CommandName.

[RottG]

You can also create manually a command SqC, and start the addon command from there. The SqC than can be mapped to the HMI button, and does the same. Not the best and most resourceful solution, but I've seen this in many projects.

[nexidator]

The ManualFunctionKey can only be linked to manual functions. Add-ons don't have an Extension, so they cannot have manual functions. If you want to bring manual functions through the object definition, your object has to be a unit, not an add-on.

Of course, it is possible to create a manual function in the project that calls a command of an add-on. You cannot link the command to the manual function in CpStudio, but the call would have to be implemented manually in the PLC code.