Block Icon with alarms

 Hi David,

You are on the right track, but there are some things not correct.

But no worries, We are here to assist you:

There is a difference between the @TemplateAPL_V8.pdl and @PCS7Typicals_V8.pdl.

Normally, blocks that are inserted in CFC, can have a block icon number assigned. During compile of the OS, the block icons are generated automatically referring to the block type in CFC. The block icons are listed in the @PCS7Typicals file. However, sometimes you will need a block which is not generated automatically and then you will use the @Template file. The difference is the "@" prefix attribute for the ServerName. Without the "@", the block icon is not generated automatically by the system.

So, the easiest way is to copy the block icon from the @PCS7Typicals file. However, since you already created your block icon, please place the "@" back.

Second, each block icon has an attribute called "System", which has a value: "PCS7 MotL Control" for example. This means that when the block icon is clicked on, the faceplate files which has prefix "@PG_MotL_" is called. So, instead of "MotL", fill in the name of the block type. Leave the rest intact.

So, you will have to change the "FB501" name.

Also, another thing you must know is that there are two kind of libraries: Classic (up to PCS7 v7.1) and the APL library. The APL library is the newest library and is your standard library to use.

The FB61 (CTRL_PID) is a block from the Classic library and this will not work with an APL block icon and their faceplate (yeah, it can work, but you need to do a lot of unnecessary time consuming things). So, you will need the PIDConL block (FB1874).

Or when using the classic library, please use the supplied block icon, not from the APL library.

If you need more info, please look at the following thread and see my second post:

https://support.industry.siemens.com/tf/us/en/posts/custom-block-icon/151745/?page=0&pageSize=10

To enable the use of alarms see the following thread for more info:

https://support.industry.siemens.com/tf/cz/en/posts/alarm-8p/154536/?page=0&pageSize=10

Messages are created by using a few system attributes. To check how this is setup: Go to your Blocks folder and open an APL block with messaging like FB1845. Go to Interface and then "IN". Find "MsgEvId1" and open properties. Then check tab: "Attributes" to see which attributes are used by MsgEvId.

You can address the individual bits to generate the message. You can configure the messages by double clicking your custom block type and under: "Messages" you can configure this. But you will need to use the correct system attributes.

David025

Dear Experts,

I am using s7-400 with PCS7 8.1 and i need Your help.

I have over 10 signals in my project which I would like to monitor, assaign alarms and create a new equipment picture to them in wincc.

 I would like to create a source code->FB, cfc from what the block icon, faceplates and alarms would be automaticaly created after the OS compile.

In WinCC from the @TemplateAPL v8.pdl i have chosen the PID CONL, to modify this block icon for my needs (saved it as @PCS7Typicals_MYAPL.pdl). I have also renamed all its' faceplate files to my chosen type (@PG_FB501_Parameter.pdl, @PG_FB501.pdl,  etc...).

From the PCS7 library i have saved FB61 (CTRL_PID) to my library, to configure.

I have read many forum threads, also the block icon, Programming Instruction for blocks, APL style , faceplates pdf files but these are not really helpful to modify an existing block icon with new variables and alarms (I have found only one example, where the motor picture was changed to pump).

Is there a better block icon to choose?

Can you share with me a step by step guide?

Thank you in advance,

David

Hi David,

I didn't see your reply yet, so sorry for the delay.

See below an example on how to use the MsgEvid1.

VAR

 Alarm_8P_1    : Alarm_8P; // Multiple instance Alarm 8P block

END_VAR

First, you can declare a variable as Alarm_8P type. Then, you can call the Alarm_8P as below. You'll see that parameter EV_ID has value "MsgEvId1". For the SIG_1 to SIG_8 means that this is message 1 to 8. As you can see, you can declare code here to trigger the message 1-8.

Alarm_8P_1     ( EN_R   := TRUE,        // Update the ACKL_STATE output
ID      := 16#EEEE,     // PMC communication channel
EV_ID   := MsgEvId1,    //
SIG_1   := (MonDynErr.Value AND NOT MsgLock.Value AND NOT LocalAct.Value),                         // Dynamic time error
SIG_2   := (MonStaErr.Value AND NOT MsgLock.Value AND NOT LocalAct.Value),                         // Static time error
SIG_3   := (CSF.Value AND NOT MsgLock.Value),                                                      // Control System Failure
SIG_4   := (FbkFwd.Value AND FbkRev.Value AND NOT MsgLock.Value AND NOT LocalAct.Value),           // Fbk Fwd and Rev error
SIG_5   := (QPROFI AND NOT MsgLock.Value AND NOT SimOn),                                           // Profibus Communication Alarm
SIG_6   := (QPERAF AND NOT MsgLock.Value AND NOT SimOn),                                           // Periphery Access Failure
SIG_7   := (QPARF AND NOT MsgLock.Value AND NOT SimOn),                                            // Parameter Assignement Error
SIG_8   := (QPPO_ERR AND NOT MsgLock.Value AND NOT SimOn)                                          // Fault PPO Type
);

 S7_a_type is important. It will tell you that the variable with this attribute is used as alarm, alarm_8p, notify, alarm_s.

S7_server is used to configure your messages and the compiler assigns a unique archive number for the messages.

S7_link (=false) must be used, because you must not assign an interconnection to the MsgEvid1 variable. With this, it means you cannot connect anything in CFC.

S7_visible (=false)means MsgEvid1 is not displayed in the block when using in CFC. Because you cannot connect anything, it is automatically hidden with this attribute.

S7_param (=false) means you cannot assign any other parameters, so this is used for the MsgEvid1.

 For more info about system attributes, see the help file when in SCL and search for "Help on System Attributes".

When your block is ready, you can go to the "Blocks" folder and search for the FB number of your custom SCL. Then, right click->Special Object Properties->Message will let you configure the default message types and default texts. When you use multiple block instances, each instance will have the default message types and texts you filled in here.

You can tell if the message has single acknowledgement, so each of the messages must be accepted individual, or it has group acknowledgment (accepting a group will accept all messages in the group).

Priority is normally not used, but can be used if there are some important messages, they will assigned a higher priority. 

David025

Hi Oreca,

Thank you for Your help! I have done all the things in wincc as you suggested.

Now I have a block icon in wincc which is automatically created after OS compile (from the FB1874). In runtime all related faceplates are opened properly, I also have an alarm "low alarm limit violated" (automatically gained from basic CFC)..

There are still several things which I would like to ask...

1. I have checked the MsgEvID1 at my PIDConl block, but I still can not find any details how to assaign it to my DB bool alarm values.

When I create a source file from the PIDConl, I can find only some variables which are declared (I can't see the alarm messages or its' variables).

In the FB1874 MsgEvid  properties I have found: S7_a_type, S7_link, S7_param, S7_server and S7_visible attributes (these are not really helping me out, am I missing something?).

At FB1874->special object properties->messages I have found 8-8 MsgEvID1-2  variables. There I can see events, priority etc. Can I assaign these to my DB to create alarm messages?.Is there an explanation to make it happen?

2. How should I interconnect the FB1874 with my own tags to automatically create alarm messages? How can I link my own cfc tags into the block icon? Should I assaign them manually in wincc at block icon->Linking->Tag connections?