[QUESTION] Communication via Ethercat Bridge to External Plant from two different AppContext

[RGrabichler]

State topic of your question

How would u try to achieve the following.

I have one Plc, controlling two plants.
This Plc communicates with an external Plant via Ethercat Bridge (fixed).
Now i have in my Plc two AppContext with different Code etc.,
but both want to communicate with the external Plant, get Status, set Outputs etc.

Where do i instantiate the Communication Fb, how to make the communication consistent and
available on both AppContexts?

To clarify it, here the Screenshot with my AppContext.
_mainStation and _mainStationWtsPlant, both want to use the communication.
In both Station, there are different components, sequences, hardware etc.

[PTKu]

Hi @RGrabichler
Different TcoContexs are designed to work in isolation from each other to prevent concurrency and racing conditions. While you can access the members from different contexts you must take care about possible concurrency problems on your own. Some features of TcOpen use internal context states, such as counters, to provide information about the execution to framework objects (TcoObject, TcoTask, TcoSequencer, etc.) the use of these types is highly risky in cross context access. If you have a type that does not derive from TcOpen framework type it should be safe to use it.

https://inxton.github.io/TcOpen.Documentation/articles/TcOpenFramework/TcoCore/TcoContext.html

I believe you can declare your communication FB in your current context. Did you consider a different option? Is your question about getting to access to the communication fb from the two plants?

[RGrabichler]

yes, the question is, how to get best access from both context on the same communication fb.
Like in C#, i have an injected service like an dbContext, which i can use.
How would u implement this in TcOpen with the Context.