pbalseiro

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • pbalseiro
    Participant

    Hi,

    Yes, this command for ex:
    <nsPV:Command
    Name=”BYPASS_ON”
    OPCServerKlasse=”BoschFPA5000OpcServer1″
    xmlns:nsPV=”file:///S3K/Proxyverwalter”
    Sender=”Makitron”
    Adresse=”Fire Panel 1-1.Detector.1.1″/>

    Thansks

    pbalseiro
    Participant

    Hi Mikhail,

    I am trying to configure Rapid SCADA as an OPC gateway.

    I wish to publish XML commands from an OPC UA client to an OPC DA server, and also receive (read/subscribe to) the values exposed by the OPC DA server in the OPC UA client.

    I have tried several configurations. In all of them, I am able to receive the sensor values published on the OPC DA server through the OPC UA client; however, I have never been able to publish or send commands from the OPC UA client to the OPC DA server.

    Can you help me with a guide or the steps to follow? Thank you very much.

    pbalseiro
    Participant

    Hi Mikhall,
    What I observe

    DrvOpcClassic (OPC DA device) shows correct values in Communicator (e.g., channels 101–105 = 5, Quality = Good).

    DrvMqttPublisher (MQTT Publisher device) publishes to the broker and topics appear, but payload values are wrong (e.g., 2.6E-322) or the publisher “Current Data” shows 0.000 / NaN.

    Attached files:

    ScadaComm.log (Communicator main log)

    Line000.log (communication line 0 log)

    Device001.txt (OPC Classic device settings)

    Device002.txt (MQTT Publisher device settings)

    PPT/screenshots showing channel list and MQTT Publisher settings

    What I’m observing:

    OPC Classic device shows correct current values (e.g., 5) in Communicator UI.

    MQTT Publisher publishes incorrect values (often 2.6E-322) or zeros instead of the OPC values.

    Relevant excerpts from ScadaComm.log:

    There are intermittent connection errors to the local ScadaServer data source: connection refused on 127.0.0.1:10000, and “connection forced to close by remote host”.

    ScadaComm

    ScadaComm

    https://we.tl/t-BcQwKKinJC

    Could these disconnections cause the MQTT Publisher to read invalid/uninitialized channel values?
    If not, which part of the configuration should I validate next (channel data type / data length / mapping between OPC channels and MQTT Publisher items)?

    Thank you!

Viewing 3 posts - 1 through 3 (of 3 total)