JW

Forum Replies Created

Viewing 15 posts - 121 through 135 (of 147 total)
  • Author
    Posts
  • in reply to: Modbus Comm Bug #7998
    JW
    Participant

    When I try to set delay to 20 or 50ms, it become even worse. it can never finish a complete request cycle of 50 element groups.

    This is strange. Delay just does Thread.Sleep(50) after receiving an answer from a device.

    I try this setting again, but it works fine today. And I can’t reproduce the problem. it maybe not the cause.

    in reply to: Modbus Comm Bug #7981
    JW
    Participant

    I am thinking about the following parameters.

    number of request retry on error: 3

    Currently, scada comm retry with in the same TCP connection.
    when reply from request is mis-aligned, retrying seems meaning less, because the header will never match again. then after 3 times, it set the element groups as undefined, then restart a new TCP session. the comm resumed normal on new TCP connection. but a false alarm already trigged.
    thus this setting doesn’t increase the tolerance for comm error on this case.

    Is it possible to have an other option to retry on new TCP connection, or count the error on failed TCP connection other than request?
    Then either starting from the previous failed element group or starting all over again.
    When the comm fails on 3 connection, then set the failed element groups to undefined.
    This should have more tolerance for comm error.

    StayConneceted: True / False

    by default, it’s set to true.
    when set to false, scada comm use new TCP session for each request cycle.
    But I am not able to test will it change the handling of retry. will it retry on the same TCP connection or new TCP connection? if scada comm retries on new TCP connection , then it should solve my problem. but I guest this parameter does not affect the retry handling.

    in reply to: Modbus Comm Bug #7980
    JW
    Participant

    The happening frequency seems pretty random.

    On my test yesterday, it happened a few times per hour. but when I try to repeat this today with the same pc and the same project, it doesn’t happen at all.

    in reply to: Modbus Comm Bug #7972
    JW
    Participant

    Just check the scadacomm log of other projects, all project with similar settings.

    most project detects a communication line disconnection every few days.
    I disabled detailed log, so it only show disconnection but not the cause.
    I believe they may have the same cause.
    —–
    2021-01-04 06:36:05 Establish a TCP connection with 127.0.0.1:1502
    2021-01-04 10:55:21 Disconnect from 127.0.0.1
    2021-01-04 10:55:22 Establish a TCP connection with 127.0.0.1:1502
    2021-01-04 23:00:03 Disconnect from 127.0.0.1
    2021-01-04 23:00:04 Establish a TCP connection with 127.0.0.1:1502
    2021-01-06 12:28:49 Disconnect from 127.0.0.1
    2021-01-06 12:28:50 Establish a TCP connection with 127.0.0.1:1502
    2021-01-10 12:00:03 Disconnect from 127.0.0.1
    2021-01-10 12:00:04 Establish a TCP connection with 127.0.0.1:1502
    2021-01-11 02:57:53 Disconnect from 127.0.0.1
    2021-01-11 02:57:54 Establish a TCP connection with 127.0.0.1:1502
    ————-

    in reply to: scheme editor bug when scrolling #7858
    JW
    Participant

    Hi, It’s fixed on my test.

    in reply to: Scheme behaviour on different Browsers (AutoSize Problem) #7857
    JW
    Participant

    It’s fixed on version 5.8.2. Have a try.

    in reply to: Administrator Find and Replace Bug #7755
    JW
    Participant

    this bug is fixed by above update.

    in reply to: Administrator Find and Replace Bug #7737
    JW
    Participant

    Hi,

    I found the difference.

    Selecting “Input channels” the whole table then find and replace will not experience crash.

    But selecting sub tables such as “[11]ADAM-6015 Server room” then find and replace will experience crash.

    in reply to: Administrator Find and Replace Bug #7731
    JW
    Participant

    yes, that’s the same actions I did.

    I am going to try on another computer tomorrow and see what’s the result.

    in reply to: Administrator Find and Replace Bug #7709
    JW
    Participant

    Hi Mikhail,

    I Found a way to reproduce this consistently using the DemoProject.en-GB.
    1. goto input channel table [11]
    2. find and replace
    Column: Name
    Find: t
    Replace with: s_t
    uncheck match whole cell.
    3. the 1st time will be performed correctly
    4. do the same find and replace again, Administrator app will crash.

    in reply to: Users, roles, rights #7592
    JW
    Participant

    Sometimes when you change settings in role table or interface table, you will need to restart the IIS service for Windows or apache2 service for Linux to make it effective, instead of just restarting the scada server.

    in reply to: Log in web page #7570
    JW
    Participant

    Hi, I tried the auto login module with rapid scada 5.8.1 on both windows and linux. Neither of them work.

    When try to use auto login URL, the web show only the following error message.

    Application Error
    An application error occurred. If it repeats often, please contact the support.
    Details:
    c:\SCADA\ScadaWeb\Login.aspx(19): error CS0103: The name ‘phrases’ does not exist in the current context

    ——————————————————————————–
    Web Log
    ——————————————————————————–
    2020-11-18 10:40:27 <os-server><www-data><ACT> Initialize common web application data
    2020-11-18 10:40:27 <os-server><www-data><ACT> Connect to SCADA-Server “localhost”
    2020-11-18 10:40:27 <os-server><www-data><ACT> Refresh the tables of the configuration database
    2020-11-18 10:40:27 <os-server><www-data><ACT> Fill input channels properties
    2020-11-18 10:40:27 <os-server><www-data><ACT> Fill output channels properties
    2020-11-18 10:40:27 <os-server><www-data><ACT> Fill input channel statuses properties
    2020-11-18 10:40:32 <os-server><www-data><ACT> User information has been added. IP address: ::1. Session: A3B4E3B4CDA8C7978F544E55
    2020-11-18 11:20:18 <os-server><www-data><ACT> Request SCADA-Server state
    2020-11-18 11:20:18 <os-server><www-data><ERR> Incorrect SCADA-Server response to state request
    2020-11-18 11:20:18 <os-server><www-data><ACT> Disconnect from SCADA-Server
    2020-11-18 11:20:18 <os-server><www-data><ACT> Connect to SCADA-Server “localhost”
    2020-11-18 11:20:18 <os-server><www-data><ACT> User information has been added. IP address: ::1. Session: 9B83F0E5C6DE2ACFC877FA8A
    2020-11-18 11:20:20 <os-server><www-data><ERR> Unsuccessful login attempt: admin – Incorrect username or password. IP address: ::1
    2020-11-18 11:20:23 <os-server><www-data><ERR> Unsuccessful login attempt: admin – Incorrect username or password. IP address: ::1
    2020-11-18 11:20:27 <os-server><www-data><ERR> Unsuccessful login attempt: admin – Incorrect username or password. IP address: ::1
    2020-11-18 11:20:37 <os-server><www-data><ERR> Unsuccessful login attempt: admin – Incorrect username or password. IP address: ::1
    2020-11-18 11:20:43 <os-server><www-data><ACT> Login: guest (Guest). IP address: ::1
    2020-11-18 11:20:43 <os-server><www-data><ACT> User information has been updated. IP address: ::1. Session: 9B83F0E5C6DE2ACFC877FA8A
    2020-11-18 11:20:43 <os-server><www-data><ACT> Retrieve components from the installed plugins
    2020-11-18 11:20:55 <os-server><www-data><ACT> Logout: guest. IP address: ::1
    2020-11-18 11:21:01 <os-server><www-data><ERR> Unsuccessful login attempt: admin – Incorrect username or password. IP address: ::1
    2020-11-18 11:21:07 <os-server><www-data><ACT> Login: guest (Guest). IP address: ::1
    2020-11-18 11:21:07 <os-server><www-data><ACT> User information has been updated. IP address: ::1. Session: 9B83F0E5C6DE2ACFC877FA8A
    2020-11-18 11:21:07 <os-server><www-data><ACT> Retrieve components from the installed plugins
    2020-11-18 11:35:25 <os-server><www-data><ACT> Application shutdown
    ——————————————————————————–
    ——————————————————————————–
    2020-11-18 11:36:40 <os-server><www-data><ACT> Initialize common web application data
    2020-11-18 11:36:40 <os-server><www-data><ACT> Connect to SCADA-Server “localhost”
    2020-11-18 11:36:40 <os-server><www-data><ACT> Refresh the tables of the configuration database
    2020-11-18 11:36:40 <os-server><www-data><ACT> Fill input channels properties
    2020-11-18 11:36:40 <os-server><www-data><ACT> Fill output channels properties
    2020-11-18 11:36:40 <os-server><www-data><ACT> Fill input channel statuses properties
    2020-11-18 11:36:46 <os-server><www-data><EXC> Application error:
    System.Web.Compilation.CompilationException (0x80004005): CS0103: The name `phrases’ does not exist in the current context
    at System.Web.Compilation.AssemblyBuilder.BuildAssembly (System.Web.VirtualPath virtualPath, System.CodeDom.Compiler.CompilerParameters options) [0x00312] in <716e5fc6fa1b4b5db9a4701d451ead9c>:0
    at System.Web.Compilation.AssemblyBuilder.BuildAssembly (System.Web.VirtualPath virtualPath) [0x00008] in <716e5fc6fa1b4b5db9a4701d451ead9c>:0
    at System.Web.Compilation.BuildManager.GenerateAssembly (System.Web.Compilation.AssemblyBuilder abuilder, System.Web.Compilation.BuildProviderGroup group, System.Web.VirtualPath vp, System.Boolean debug) [0x00202] in <716e5fc6fa1b4b5db9a4701d451ead9c>:0
    at System.Web.Compilation.BuildManager.BuildInner (System.Web.VirtualPath vp, System.Boolean debug) [0x00106] in <716e5fc6fa1b4b5db9a4701d451ead9c>:0
    Page: http://localhost/scada/Error.aspx
    ——————————————————————————–

    ——————————————————————————–
    Server Log
    ——————————————————————————–
    2020-11-18 10:03:01 <os-server><root><ACT> ScadaServerService 5.1.4.0 is started
    2020-11-18 10:03:02 <os-server><root><ACT> Check the existence of the data directories is completed successfully
    2020-11-18 10:03:02 <os-server><root><ACT> Check the existence of the configuration database files is completed successfully
    2020-11-18 10:03:02 <os-server><root><ACT> Input channels are read from the configuration database. Active channel count: 5
    2020-11-18 10:03:02 <os-server><root><ACT> Ouput channels are read from the configuration database
    2020-11-18 10:03:02 <os-server><root><ACT> Users are read from the configuration database
    2020-11-18 10:03:02 <os-server><root><ACT> Formulas are read from the configuration database
    2020-11-18 10:03:06 <os-server><root><ACT> The formulas source code has been compiled
    2020-11-18 10:03:06 <os-server><root><ACT> Connection listener is started
    2020-11-18 10:03:06 <os-server><root><ACT> Start server
    2020-11-18 10:03:06 <os-server><root><ACT> Current data are loaded
    2020-11-18 10:03:13 <os-server><root><ACT> Connect to client 127.0.0.1
    2020-11-18 10:03:13 <os-server><root><ACT> The user ScadaComm is successfully authenticated
    2020-11-18 10:40:27 <os-server><root><ACT> Connect to client 127.0.0.1
    2020-11-18 10:40:27 <os-server><root><ACT> The user ScadaWeb is successfully authenticated
    2020-11-18 10:41:32 <os-server><root><ACT> Disconnect client 127.0.0.1
    2020-11-18 11:20:18 <os-server><root><ACT> Connect to client 127.0.0.1
    2020-11-18 11:20:18 <os-server><root><ACT> The user ScadaWeb is successfully authenticated
    2020-11-18 11:20:20 <os-server><root><ACT> Check username and password for admin. Result: failed
    2020-11-18 11:20:23 <os-server><root><ACT> Check username and password for admin. Result: failed
    2020-11-18 11:20:27 <os-server><root><ACT> Check username and password for admin. Result: failed
    2020-11-18 11:20:37 <os-server><root><ACT> Check username and password for admin. Result: failed
    2020-11-18 11:20:43 <os-server><root><ACT> Check username and password for guest. Result: passed
    2020-11-18 11:21:01 <os-server><root><ACT> Check username and password for admin. Result: failed
    2020-11-18 11:21:07 <os-server><root><ACT> Check username and password for guest. Result: passed
    2020-11-18 11:22:14 <os-server><root><ACT> Disconnect client 127.0.0.1
    2020-11-18 11:36:40 <os-server><root><ACT> Connect to client 127.0.0.1
    2020-11-18 11:36:40 <os-server><root><ACT> The user ScadaWeb is successfully authenticated
    2020-11-18 11:37:40 <os-server><root><ACT> Disconnect client 127.0.0.1
    ——————————————————————————–

    in reply to: ModAutoControl’s sengding command is disabled #7545
    JW
    Participant

    **note: the files in the link above are the configs that will trigger the issue, not the workaround.

    in reply to: ModAutoControl’s sengding command is disabled #7543
    JW
    Participant

    The picture you post is not visible.

    Below are my experience and tips of sending command to external modbus device. Not sure is it the same issue you encountered.

    When 1 trigger triggers and sends 2 commands to 1 same external device. the auto control module stops working will work at the beginning, but fail after a few events.

    Then I set some delay to each command, then it seems ok as a work around.

    my device comm setting, auto control setting and server log are attached in the following link.
    https://drive.google.com/drive/folders/19fHCCfyO-0bWff_Tsadruy29eT05lmyJ?usp=sharing

    in reply to: Read and Write hour / min data of ArchiveDAT #7508
    JW
    Participant
Viewing 15 posts - 121 through 135 (of 147 total)