IEC 61499之施耐德EAE适配器介绍

Adapters provide the single line engineering for EcoStruxure Automation Expert. Instead of having multiple connections for events and data an adapter can encapsulate all of these and provide a single connection between function blocks.

Much of the common process library makes connections using adapters and sometimes this is the only way to connect blocks in the required way.

Adapters are single connecting links that can be made in a function block network but contain multiple event and data connections. They are like a multicore or ribbon cable but with some restrictions:

• Both events and data can be carried
• Links can be for input or output
• They are bi-directional for different links
• Data types are checked
•  

The adapter itself needs to be created with the event and data paths being defined. Plugs and sockets also need to be added to Composite function blocks to allow the adapter to be connected.

 

Note: Adapters cannot be used with Basic or Service function blocks.

Concept

Adapters consist of a plug, a socket and a set of events and variables connecting the plug and socket.

A composite function block can contain adapter plugs and sockets allowing an adapter to be connected. When connecting an adapter, the Adapter plug must be connected to the composite socket and the Adapter socket connected to the composite plug.

Inside the composite, adapter connectors can be switched from plug to socket and vice versa using the right click menu and reversing.

Examining an Adapter

To find out the type of adapter used for an interface, hover the mouse over the interface pin. Here we can see the interface is using the IRealPv adapter from the SE.AppCommonProcess Library.

As adapters carry multiple signals, both events and data it is not possible to show a single display in the application. Instead, hovering the mouse over the adapter connection will show the structure.

 

When adding a watch, it is also not possible to show the multiple values on a single interface so a popup will be displayed, showing the adapter and the watch values.

 

This is echoed in the watch window with the name:
<Device>.<Resource>.<FB Name>.<Adapter Interface Name>.<Adapter Signal>

To find out the type of adapter used for an interface, hover the mouse over the interface pin. Here we can see the interface is using the IRealPv adapter from the SE.AppCommonProcess Library.

It is possible to extract information from an adapter by creating a composite function block that passes the data through and adding outputs for the information to be extracted.

Here the PV, Low and High data values are passed through, together with the associated event, but the Sim data and CNF Event are attached to outputs.

Using this composite function block in an application allows these to be connected to other function blocks, in this case for status display.

This is a useful way of displaying information that is encapsulated in an adapter.

Adapters also have a cardinality of 1:1, meaning that they can only be connected to a single function block. If multiple output connections are required, for example to connect a single analog input to two analog outputs, this can also be achieved using a composite.

 

1. With the solution running in the EcoRT, add a watch to the analog input.

         

Observe that watches have been added to all interfaces except >>IExtPv and IPv>>. These do not have watches as they are adapters – they can be recognised by the >> (pointing into the block) for an adapter socket or >> (pointing out of the block) for an adapter plug.

Adapters have their own watch method as they contain many signals.

1. Add a Watch to the adapter.

1. Right-click IPv>> and select Watch.

         

This will show the adapter with the watch values for each element.

1. In the HMI, set the analog input so that it goes into alarm and observe the effect on the values in the adapter.

  

1. Hover over the Pv watch to see the value.

 

Tip: This information can also be seen in the watch window.

1. Change the PvHi and PvLo values.

All this information is being transferred into the application using the adapter.

Currently, there is no indication on the main page when this analog input is in simulation mode. However, if there is a requirement for this it can be extracted from the adapter.

1. Determine the type of adapter being used.

1. Hover the mouse over the IPv>> interface.

 

 

Here it can be seen that the adapter is using IRealPv from the common process library.

1. Create a new composite function block to extract information.

1. Add the IRealPv adapter to the composite function block.

 

The adapter will be added as a socket to allow it to be connected to the analog input. The following shows the interfaces that now exist for the function block.

 

 

 

1. Create an adapter plug to allow the connection to the next block in the chain.

Again, hovering over the pin to be connected will show what is required.

 

1. Add an IRealSP to the ExtractSimulate function block.

Right-click the IRealSp and select Reverse to change it to a plug output.

1. Link the two adapter connectors as shown.