Mikhail

Forum Replies Created

Viewing 15 posts - 106 through 120 (of 6,366 total)
  • Author
    Posts
  • Mikhail
    Moderator

    You can edit the project as you described. Make a backup before.
    The Communicator configuration file ScadaCommConfig.xml should be edited manually (in Notepad++) to move devices to other communication lines. Reopen a project after manual editing.

    • This reply was modified 3 months, 2 weeks ago by Mikhail.
    in reply to: Webstation output channel error #17940
    Mikhail
    Moderator

    Hello,

    For testing, you could set the format to an empty value. After you make it works, change the format to Off-On.

    Mikhail
    Moderator

    Hi,

    * Is it possible to duplicate the device within the system to separate polling tasks?
    For example, one device for continuous reading of essential variables and another only for alert or detailed diagnostic variables.

    Yes, this is a good practice.

    * I am also considering a logic where, for example, if I receive a critical flag (such as breaker opened), this event could trigger a Poll on Command to request more detailed readings only at that moment. Is this a viable approach?

    It is possible to send a polling command with Auto Control Module.

    * Is this strategy generally recommended, or could it create communication conflicts, request collisions, or overload the relay?

    It looks OK.

    * I have never used Poll on Command before. Could someone explain, in general terms, how it works in practice?

    Using the Administrator app, try sending a command with the App.Comm.PollDevice code to the selected device.

    * After loading the device and creating the channels, how is the Poll on Command actually triggered?
    Does it require manual activation, scripting, event logic, external commands, or is there native automation for this?

    This checkbox means that an explicit command required to poll a device.

    in reply to: Tailscale and module licenses compatibility #17938
    Mikhail
    Moderator

    Hi,

    If the existing network adapter remains installed, the registration keys should work.

    in reply to: PlgMimShapesJP #17932
    Mikhail
    Moderator
    in reply to: PlgMimCalendarJP #17931
    Mikhail
    Moderator
    in reply to: modbus slave drive #17925
    Mikhail
    Moderator

    Hi,

    Independent Device
    Independent device mode allows receiving data from a controller acting as a Modbus Master. Additionally, the controller can read previously recorded tag data.

    Device Gateway
    Device gateway mode allows you to share current channel data from a selected device with a third-party system. Channel assignment is based on a comparison of the tag codes defined in the Modbus template and the tag codes of the device being broadcast.
    This mode is easy to configure because it allows you to use the same template previously created for Modbus Master devices.

    Channel Gateway
    Channel gateway mode allows you to provide current data from selected channels to a third-party system. Channels are explicitly specified in the Modbus Slave device configuration.

    in reply to: Currency Format #17921
    Mikhail
    Moderator

    Hi,

    en-NZ is a culture code for New Zealand. A culture includes the corresponding language and formatting options.
    In the Administrator app, in the Webstation options, select en-NZ culture for the web application.
    The web app will not find the appropriate language files, and should use the existing English language files and the regional culture settings.
    Does it work?

    Format strings can be found here and here.

    in reply to: MQTT – period must be less than 65 seconds #17910
    Mikhail
    Moderator

    Hi,

    There was an invalid file path in that archive. Sorry.
    Move DrvMqttPublisher.Logic.dll from the ScadaComm directory to ScadaComm\Drv or use this archive.

    Mikhail
    Moderator

    Hi,

    Thank you for the update 🙂

    in reply to: DrvDDEJP #17906
    Mikhail
    Moderator

    The driver has been added to the Store: https://rapidscada.net/store/Module/en/DrvDDEJP

    Mikhail
    Moderator

    Hi,
    According to the source code, the driver tries to reconnect no earlier than 5 seconds after the previous attempt.
    It is a good idea to increase reconnection interval after each unsuccessful attempt. I’ve added it to the backlog.
    Thank you.

    in reply to: MQTT – period must be less than 65 seconds #17903
    Mikhail
    Moderator

    Hello,
    Please try this update. Does it work?

    in reply to: ModActiveDirectory – “Host can’t be null” error #17902
    Mikhail
    Moderator

    rapid_scada database should be created on the DB server.

    in reply to: ModActiveDirectory – “Host can’t be null” error #17901
    Mikhail
    Moderator

    If you upgraded Rapid SCADA from the older version, you need to upgrade ScadaInstanceConfig.xml as follows

    <?xml version="1.0" encoding="utf-8"?>
    <ScadaInstanceConfig>
      <Culture></Culture>
      <LogDir></LogDir>
      <DefaultConnection>Default Connection</DefaultConnection>
      <ActiveStorage>FileStorage</ActiveStorage>
      <Connections>
        <Connection>
          <Name>Default Connection</Name>
          <DBMS>PostgreSQL</DBMS>
          <Server>localhost</Server>
          <Database>rapid_scada</Database>
          <Username>postgres</Username>
          <Password>4D83D8AEB31C1B40335A78AF3539DD22</Password>
          <ConnectionString />
        </Connection>
      </Connections>
      <Storages>
        <Storage code="FileStorage">
          <ViewAvailable>false</ViewAvailable>
        </Storage>
        <Storage code="PostgreSqlStorage">
          <ViewAvailable>true</ViewAvailable>
          <WaitTimeout>30</WaitTimeout>
        </Storage>
      </Storages>
    </ScadaInstanceConfig>
    
Viewing 15 posts - 106 through 120 (of 6,366 total)