OPCUA communications redundancy

Forum Home Forums Understanding the Software OPCUA communications redundancy

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #12581
    jl.diez
    Participant

    I need information to communicate with a PLC by two means of communication (GPRS and TETRA) using the same protocol “OPC UA”.
    Currently I have established communications with two different IPs.
    Is this possible?
    Can you help me?

    • This topic was modified 2 years, 5 months ago by Mikhail.
    #12605
    Mikhail
    Moderator

    Hello,

    Option 1
    Read data from the OPC server like there are 2 different devices. Then join data to the 3rd device using formulas.
    This option is good if there are not too many devices.

    Option 2
    Install 2 Communicators. Use the save device number and line number, but with different settings. Ignore bad values using formulas.
    This option is more difficult to setup.

    #12612
    jl.diez
    Participant

    Hello.
    I lean towards option number 2 since I will have many devices.
    In the explanation provided by you I do not understand the procedure.
    The problem I see is that for each channel there can only be one device.
    Can you explain to me how I manage this issue?

    #12618
    Mikhail
    Moderator

    Hello,

    I lean towards option number 2 since I will have many devices.

    OK. To be honest, I haven’t tried this method by myself. However, it should work. Let’s try together.

    The problem I see is that for each channel there can only be one device.

    That’s true. Therefore, the idea is to use 2 Communicators that have communication lines with different types of communication channels.

    #12619
    Mikhail
    Moderator

    1. Setup the 1st Communicator as usual. It will server GPRS channel.

    2. You need to deploy the 2nd instance of Rapid SCADA that includes Agent and Communicator services. You can deploy it on the same machine or on another machine.
    Is it convenient for you to use another (may be virtual machine) for testing? It allows to install Rapid SCADA by the installer. Do you use Windows or Linux?

    3. On the 2nd instance, edit ScadaAgentConfig.xml. You should change Default instance to new instance name.

    4. In your Rapid SCADA project, add a new instance and configure the deployment profile to be able to upload the configuration to it.

    When the above is done, configure the 2nd Communicator to use TETRA.
    Be free to ask follow up questions. Provide screenshots to explain possible questions.

    #12620
    jl.diez
    Participant

    Good afternoon.
    I have proceeded to make the structure that you indicate me but I do not understand how you link the connectors to the same channel.
    I have screenshots but I can’t attach them in the post.
    I have even compressed the application so you can have a look at it.
    When you tell me to edit the ScadaAgentConfig.xml file and change the instance name I don’t understand the procedure since there is only one file in the program “Rapidscada” it is common for all the projects.
    Thanks in advance for your help

    #12624
    Mikhail
    Moderator

    Hello,

    > how you link the connectors to the same channel
    Use external file sharing like Google Drive or https://imgbb.com/

    > I don’t understand the procedure since there is only one file in the program
    I mean that you should deploy additional Rapid SCADA instance on virtual machine that includes Agent and Communicator. This instance also contains ScadaAgentConfig.xml

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.