APL &basic elements

moelsayed

Hello,

I created my own face plate by using face plate designer 

I tried to use APL-ELEMENT like  (APL_OP_BUTTON, csoIOAnaSP ) but I couldn’t  it appeared as it is not active .

I removed the permission tags but nothing changed.

But when I used elements from  ( @pcs7element.pdl ) they worked with me .

So what should I do to use APL-ELEMENT in my own FACE PLATE.

Thanks in advance,

Moelsayed

 Hi moelsayed,

Attached is a print screen of the APL styleguide. Using objects from the @PCS7ElementsAPL.pdl is mandatory.

I am having a similar problem with the APL_OP_BUTTON. I copied the button from @PCS7ElementsAPL.pdl into my faceplate, configured the script in the StUser object, and configured the PermissionTag and BinPermBitIndex values, but the object is always disabled. My logged in user is an administrator with full permissions for the area. Is there anything else I should be doing to make this object work? 

Thanks in advance.

Thank you both Harry and Oreca for your help and suggestions. Unfortunately, I am still not having any luck. I have checked my configuration, and it very much follows what Harry documented. To answer Oreca's question,  I am using my own custom block. I have included a screenshot of my button's configuration. The button is called "btnCommand2" so you can see it in the stUser script. The PermissionTag I am using is called ".CmdEnable." Admittedly, it is a WORD, and not a STRUCT as the APL Style Guide wants, however, I have used a WORD data type in this application before without issue. I have verified that the .CmdEnable variable is changing state, and the individual bits are readable in the faceplate. 

I have used apdiag.exe with the Output Window open, and no script errors are occurring. The thing about this I find odd is that to test apdiag I renamed my tag to a tag that doesn't exist, but still no script errors are occurring.

I believe now that the issue is not with how my button is configured, but rather with the authorization level somehow not getting transferred correctly into the faceplate. (None of the other two buttons are working either.) The OperationLevel1-3 are set to ProcessControlling, Higher Process Controlling, and Highest Process Controlling in the block icon (and my logged in user is an administrator with full access to all OS areas. Are there any other settings in the block icon I might be missing?

Thanks!

Hi Oreca,

Thanks for the wild guesses.

I am not using the Op_Level system attribute. I checked the APL Styleguide (2012 revision) and I could not find any mention of it. I did search a bit for it and read what I could find, which was limited. I see that it would be used to populate the "BinAuthorizationLevel1-5" fields in the Links tab of the button. Right now, I just have static "1" in there, which I assume should be fine. (This corresponds to whatever I have in "OperationLevel1" in the block icon, right? For me is set to Process controlling.)

I did not have OS_PermLog. Instead I had CmdEnable, which is a WORD. However, just for the sake of being thorough, I did create an OS_PermLog variable as a DWORD and tried configuring it in the button. In the block I set the value OS_PermLog to 16#FFFFFFFF, which should turn on all the bits, so that should eliminate byteswap and wordswap in WinCC from being an issue. However, that it not resolve the issue either.

It would be nice if apdiag would help, but no errors are showing up. I set the "Operation" parameter of the button to YES, which enables it, but in runtime I can see something is turning it off.

HarrY, thanks for wanting to help.

To keep things simple, I created a new very simple block. I compiled it, and created a very simple faceplate the same way I did my other one, and it is exhibiting the same problem. I've attached a zip file containing the SCL code, PDL files for the facepate as well as a PDL file with a block icon I am using to open it. (The faceplate and block icon are modified versions of OpDi01 block.)

Please let me know if you see any issues and can or cannot replicate the problem.