Mikhail

Forum Replies Created

Viewing 15 posts - 1,621 through 1,635 (of 6,145 total)
  • Author
    Posts
  • in reply to: Problem with data adquisition #12685
    Mikhail
    Moderator

    When a device is disconnected, channel status = 0. You should also store status in the database, or use status to convert values to NULL if status is zero.

    in reply to: OPC DA to UA Gateway #12684
    Mikhail
    Moderator

    Hi,

    There are 2 independent tasks:
    1. Get data from OPC DA.
    2. Provide data as OPC UA. Rapid SCADA 6 is needed for this.

    To solve the 1st task, use usual configuring sequence, as written above. In case of errors, please provide screenshots of the settings and logs.

    After the 1st task is done, ask about the 2nd,

    in reply to: Map: Data #12683
    Mikhail
    Moderator

    Hi,

    Do you mean displaying data on a map permanently? Could you draw an example?

    in reply to: Remote commumicator #12674
    Mikhail
    Moderator

    Hello,
    In the connection options of the Communicator B you should specify the Server A.
    It would be more efficient if you provide screenshots of your settings.

    in reply to: REST API for the RapidScada #12673
    Mikhail
    Moderator

    Hello,
    API provides access to channel data by channel numbers. Channel names are not unique, so cannot be used to get data.

    Getting channel data using REST API by some unique string codes can be a good idea for the future improvements. Currently, you need an internal dictionary that provides channel number by its name or code.

    in reply to: Structure of many instances #12672
    Mikhail
    Moderator

    Hello,
    I think, you need 4 instances in the project:
    – Default
    – Remote1
    – Remote2
    – Remote3

    The instances are declared in the project, and deployed on different machines.

    in reply to: Problem with data adquisition #12671
    Mikhail
    Moderator

    Also check in log files that data queues of the module do not overflow.

    in reply to: Problem with data adquisition #12670
    Mikhail
    Moderator

    In Rapid SCADA all data uses UTC timestamps. Some databases (like PostgreSQL) have special data type to work with timezone, some databases don’t have such data type.
    If actual timestamps always differs by timezone offset, it’s OK and can be corrected in the SQL request.

    in reply to: Problem with MQTT Client #12669
    Mikhail
    Moderator

    Hi,

    I recommend use the same Tag Code and Topic parameters.
    You don’t need to create commands under the Command node.
    If a subscription is created and not read only, a value can be published.

    in reply to: Problem with MQTT Client #12655
    Mikhail
    Moderator

    https://ibb.co/yPZZWqP

    I suggest trying broker.mqtt-dashboard.com for testing.

    in reply to: Problem with data adquisition #12653
    Mikhail
    Moderator

    Could you tell what is “BBDD”?
    What is the time zone?

    in reply to: Problem with MQTT Client #12652
    Mikhail
    Moderator

    Can’t find a screenshot where the Options node is selected.

    in reply to: Problem with MQTT Client #12649
    Mikhail
    Moderator

    Hello,

    Could you add a screenshots of Device 4 Properties – Options?
    If you try the same on public broker broker.mqtt-dashboard.com, does it work or not?

    in reply to: MQTT not reading messages #12648
    Mikhail
    Moderator

    Hello,

    Currently, the MQTT driver doesn’t support strings. It’s possible to implement in the future.
    Strings are supported by OPC UA driver, for example.

    in reply to: Problem with data adquisition #12645
    Mikhail
    Moderator

    If device communication was OK, and then the device become unavailable, the device data in Communicator should be changed to ---. If not, let me know and provide communication line log.

Viewing 15 posts - 1,621 through 1,635 (of 6,145 total)