Hi,

I want to know that is there any block available to check the status of AS-OS communication,

Means in any case, if OS is not connected or deactivated then AS can take some actions in the logics.

I am using PCS7 9.1 SP2.

I am not aware of any block to check this in 'base' PCS7. 

However, If you are using Route Control or APF, those have some additional blocks & functionality with watchdogs built in which can give you some information in the AS program.  For route control, it would only be 100% accurate if your RC and OS server was the same machine and you had dependent runtime set up, otherwise it might not detect all situations.  APF would be inherent since it runs only in the OS runtime.

You could potentially use the CONx_LOAD output value(s) from the CPU_RT block and compare it >0 average over a certain amount of time which would indicate some traffic is occuring.  (where x = the netpro connection ID integer of your OS connection(s))

Or you could build your own block or use an APL block and write some logic in C or VBS script to run continuously in the OS server (or only on the master server if redundant) and check the watchdog value changes with CFC code.

I've never had this use case but it is an interesting one.  I'm interested if someone else has a different solution or what you finalize on.

Hi RVS.wick,

Thanks for the reply.

We found one option for AS-OS communication status in module information for CPU as mentioned in attached image.

Now we need to find out can we use this value or not?

From where we can find this tag to use further?

RVS.wick

I am not aware of any block to check this in 'base' PCS7. 

However, If you are using Route Control or APF, those have some additional blocks & functionality with watchdogs built in which can give you some information in the AS program.  For route control, it would only be 100% accurate if your RC and OS server was the same machine and you had dependent runtime set up, otherwise it might not detect all situations.  APF would be inherent since it runs only in the OS runtime.

You could potentially use the CONx_LOAD output value(s) from the CPU_RT block and compare it >0 average over a certain amount of time which would indicate some traffic is occuring.  (where x = the netpro connection ID integer of your OS connection(s))

Or you could build your own block or use an APL block and write some logic in C or VBS script to run continuously in the OS server (or only on the master server if redundant) and check the watchdog value changes with CFC code.

I've never had this use case but it is an interesting one.  I'm interested if someone else has a different solution or what you finalize on.

Oh, I forgot about SFC87 / CONEC.

Here's an old thread:  https://support.industry.siemens.com/forum/ww/en/posts/display-cpu-netpro-connections-to-the-wincc-hmi/27837

I'm pretty sure the engineering interface for module information uses a remote call or something similar to display that data.

SFC87 is not put in the AS code directly but its called by CONEC block which is part of basis library.  If you look at the CONEC help should be able to determine which MSGSTA# output word holds the connection information for the netpro connection you want.

Does it work for what you need?

Hi,

Does this block(FB88) work with simulator or do we need CPU?

RVS.wick

Oh, I forgot about SFC87 / CONEC.

Here's an old thread:  https://support.industry.siemens.com/forum/ww/en/posts/display-cpu-netpro-connections-to-the-wincc-hmi/27837

I'm pretty sure the engineering interface for module information uses a remote call or something similar to display that data.

SFC87 is not put in the AS code directly but its called by CONEC block which is part of basis library.  If you look at the CONEC help should be able to determine which MSGSTA# output word holds the connection information for the netpro connection you want.

Does it work for what you need?

SIMIT and PLCSIM have support for SFC87 which is the portion of FB88 you need, however they might substitute some functionality.  You will have to test it yourself and read the manuals.

I still think it would be easier to just build in watchdog functionality to your use case instead of direct monitoring.  What is your use case anyhow?  For example, OPC values coming from the OS server and needing to take action when they go stale?  There are better ways to handle that than monitoring the connection status.

We need to generate SOE/SER (Sequence of events recording), but we required special types of modules for it which supports hardware interrupts.

Then we found block "Alarm_7B" which can generates the alarms automatically, we just need to connect the bits which we wanted to generate alarms with rising edge or falling edge.
Also buffer functionality is available in this block, like if OS is disconnected from AS, then this block can store new alarms in buffer(AS memory) with time stamps and when the OS connection is healthy then all the buffer alarms will go to the OS.
Now, we just need a bit in the AS for OS connection status so that we can connect it to ALarm_7B block.

When using Alarm_7B you have to install OS scripts to do the connection monitoring.  (Similar to what I said initially.)

Buffering of Process Messages including Time Stamps with ALARM_7B

So if I understand your use case correctly, I think there is no reason to monitor the connection status from within the AS with any block other than ALARM_7B as defined in manual of the SIOS article I linked above.  Specifically chapter 5.