Dear all,

I am new to PCS7, and altought I understand everything is supposed to work without my intervention, at least, at this level of detail, I am eager to understand how things work.

Therefore, I am trying, these last few days, to understand how are statuses passed to control blocks, in Runtime Display.

I have seen that all of them are linked to an .EventState tag, and I took an educated guess and assumed this was responsible for the event state.

In order to confirm this, I have created 32 blocks, and assigned them a event state from 2^1 to 2^32, in order to get all the bits possible, plus a 33rd with 0.

To my great surprise, I do not have all states possible (especially, I do not have 'normal mode state'), and a lot of 'Alarm' state, as you can see on the screenshot (top left is 2^1, bottom right is 2^32, the outcast is 0).

Can you please shed some light on this for me?

Thanks a lot,

Hello,

The .EventState is a PCS7 structure tag included in technology blocks which have a message system (MsgEvId). .EventState ensures that all blocks have the same structure to display statusses. Each bit in the 32-bit word has particular significance and changes depending on incoming/outgoing events. The .EventState is generated automatically, so changing the values of the tag is not recommended.

Additional info:

When using chronological messaging, the data for the group display are made available in the "*.EventState" tag. You can link the "Group Value" property of the group display directly to the "*.EventState" tag. Entry ID 23730649 and Entry ID 23730697 provide detailed information on chronological messaging and the associated requirements. When using the bit alarm procedure or the analog alarms, the "*.EventState" tag is not available by default to provide the group display with the message status.  

Thank you for your answer.

My concern lies one step further. Indeed, I would like to understand how, once generated, the information in EventState Tag is used by the block.

In my little experiment, I did not change EventState status tag, I just severed the connection and used static values to see what happens.

Here you go!  (enclosed)

I did exactly this. Set the Group Value to all bits from 0 to 31. I expected the results described in the PDF, but, as you can see on the screenshot, I don't.

There must be something I did not understand, and did wrong, but I can't figure it out.

It is in my first post

Thanks for your help

Hello,

Oh, I thought you meant that you had another document enclosed.

I assume it's a test project...Did you activate Alarm logging? Did you run OS project editor? The group display will take message classes/types from PCS7 alarm logging by default setting. If they are not defined, maybe there lies the problem.

Overall, numerous things can be wrong. Did you did a OS compile, download etc.. to make sure all settings are transferred, so basically everything is at default setting?