APL_ face plate style

Hello,

I am creating my own block I con with it’s faceplate  but it will be created according to my own block ( FB )

I gona use APL element s like (APL_OP_BUTTON ) to switch between modes ( MAN/AUT /OOS) .

>> But according to the button properties I will have to get some signals from my own block  as in below :

_ permission Tag  :  .OS_PermLog    “ I should receive this signal from my (FB)to activate the button to                                     select between modes “

_Links :  .AutModOp   

            :  .ManModOp

            :  .OosOp

            “ also here I have to receive these via ( .Status1 ) signal to identify the current mode this is output                from my ( FB )  according to this signal csoStMode will be changed ,

             (  .AutModOp   , . ManModOp, .OosOp ) signals are inputs to  my FB  ( I don’t know how these                  signals will be active  ) So I have to include them in my logic to use them.

>> When I press on the previous button( csoStMode)  screen  (@pg_apl_oa_binary105.PDL ) will be opened .

But when after selecting for example ( AUT ) mode nothing changed with me

I think (  .AutModOp   , . ManModOp, .OosOp ) are linked with the buttons in screen  (@pg_apl_oa_binary105.PDL ) by some how .

I tried to dig in the c-script for ((@pg_apl_oa_binary105.PDL ) ) but I found all of these  buttons as in the attachment .

So please I need help to understand how is it working

moelsayed

Hello,

I am creating my own block I con with it’s faceplate  but it will be created according to my own block ( FB )

I gona use APL element s like (APL_OP_BUTTON ) to switch between modes ( MAN/AUT /OOS) .

>> But according to the button properties I will have to get some signals from my own block  as in below :

_ permission Tag  :  .OS_PermLog    “ I should receive this signal from my (FB)to activate the button to                                     select between modes “

_Links :  .AutModOp   

            :  .ManModOp

            :  .OosOp

            “ also here I have to receive these via ( .Status1 ) signal to identify the current mode this is output                from my ( FB )  according to this signal csoStMode will be changed ,

             (  .AutModOp   , . ManModOp, .OosOp ) signals are inputs to  my FB  ( I don’t know how these                  signals will be active  ) So I have to include them in my logic to use them.

 

>> When I press on the previous button( csoStMode)  screen  (@pg_apl_oa_binary105.PDL ) will be opened .

But when after selecting for example ( AUT ) mode nothing changed with me

I think (  .AutModOp   , . ManModOp, .OosOp ) are linked with the buttons in screen  (@pg_apl_oa_binary105.PDL ) by some how .

I tried to dig in the c-script for ((@pg_apl_oa_binary105.PDL ) ) but I found all of these  buttons as in the attachment .

So please I need help to understand how is it working

thanks in advance,

Moelsayed.

 Hello,

OS_PermLog is an output which is defined in your block code. For this you create a input: OS_Perm and use this to define authorizations for specific variables such as AutModOp. By using the "AT" command, you can create views of the double words OS_PermLog and OS_Perm and to address them. You don't have to use the OS_PermLog variable persee, because in the object: "APL_OP_BUTTON" you can disable this by setting parameter: PermissionTag under Permission to "0". Anyway...

The links you have listed like AutModOp are coming from WinCC when your press a button for example (S7_m_c:='true').

When you inserted the APL_OP_BUTTON, you can assign a unique name to it. Please make sure the object name is written in the "stUser" object as well in order to change authorizations when changing users.

Under BinLink 1-5 you can assign the designated tag.

If there are stil problems, you can check if all TAGs exist for your custom block and otherwise you can use apdiag.exe (Under program files(x86)->Siemens->WinCC->uTools) to check for script errors when in runtime.

In the Libraries_APLStyleguide you can find more info on page 108 for the APL_OP_BUTTON.

Please let me know if this helped you!

Link to document: https://support.industry.siemens.com/cs/document/43705259/pcs-7-libraries-apl-style-guide?lc=en-WW

Hi  Oreca,

Thank you very much for your help.

after reading your document i found what i was looking for and so many information about my point.

appreciated.

Moelsayed