Data not coming in Realtime

Forum Home Forums Communicating with Devices Data not coming in Realtime

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #8618
    Avatarafzal
    Participant

    Hi,

    i am communicating through modbus, my slave devices are sending data at the interval of some milliseconds but scada is receiving after 2 seconds or sometimes after 4 seconds.
    i have already set current data setting “On Change”
    why scada is slow to receive the data ?
    if it can communicate to 65535 device, it should not feel any burden.
    where could be the problem ?

    Regards
    Afzal

    #8622
    MikhailMikhail
    Moderator

    Hi,

    Please provide communication line log.

    #8628
    Avatarafzal
    Participant

    i place the communication log below.

    2021-04-01 15:47:15 Communication session with the Device 1 “IN_TEMP”, type: KpModbus, address: 1
    Request element group “TEMPERATURE”
    Send (8): 01 03 11 93 00 0A 30 DC
    Receive (5/5): 01 03 14 08 34
    Receive (20/20): 08 2A 00 0A 00 0A 00 14 00 2D 00 28 00 32 00 3C 00 46 83 84
    OK!

    2021-04-01 15:47:16 Communication session with the Device 2 “IN_FLOW”, type: KpModbus, address: 2
    Request element group “Flow”
    Send (8): 02 04 0D AB 00 05 43 76
    Receive (5/5): 02 04 0A 04 0B
    Receive (10/10): 03 77 03 61 03 6B 03 75 AC 3D
    OK!

    2021-04-01 15:47:16 Communication session with the Device 3 “IN_PRESSURE”, type: KpModbus, address: 3
    Request element group “PRESSURE”
    Send (8): 03 03 09 C3 00 05 77 8B
    Receive (5/5): 03 03 0A 03 4D
    Receive (10/10): 03 57 03 61 03 6B 03 75 D1 0C
    OK!

    2021-04-01 15:47:17 Communication session with the Device 4 “OUT_SENECA_DO”, type: KpModbus, address: 4
    No elements for request

    2021-04-01 15:47:17 Communication session with the Device 5 “OUT_POMPA_A”, type: KpModbus, address: 5
    No elements for request

    2021-04-01 15:47:17 Communication session with the Device 6 “OUT_POMPA_B”, type: KpModbus, address: 6
    No elements for request

    2021-04-01 15:47:18 Communication session with the Device 1 “IN_TEMP”, type: KpModbus, address: 1
    Request element group “TEMPERATURE”
    Send (8): 01 03 11 93 00 0A 30 DC
    Receive (5/5): 01 03 14 08 38
    Receive (20/20): 08 2E 00 0A 00 0A 00 14 00 2D 00 28 00 32 00 3C 00 46 D2 14
    OK!

    2021-04-01 15:47:18 Communication session with the Device 2 “IN_FLOW”, type: KpModbus, address: 2
    Request element group “Flow”
    Send (8): 02 04 0D AB 00 05 43 76
    Receive (5/5): 02 04 0A 04 0F
    Receive (10/10): 03 7B 03 65 03 6F 03 79 E2 F9
    OK!

    2021-04-01 15:47:19 Communication session with the Device 3 “IN_PRESSURE”, type: KpModbus, address: 3
    Request element group “PRESSURE”
    Send (8): 03 03 09 C3 00 05 77 8B
    Receive (5/5): 03 03 0A 03 52
    Receive (10/10): 03 5C 03 66 03 70 03 7A 62 3F
    OK!

    2021-04-01 15:47:19 Communication session with the Device 4 “OUT_SENECA_DO”, type: KpModbus, address: 4
    No elements for request

    2021-04-01 15:47:19 Communication session with the Device 5 “OUT_POMPA_A”, type: KpModbus, address: 5
    No elements for request

    2021-04-01 15:47:20 Communication session with the Device 6 “OUT_POMPA_B”, type: KpModbus, address: 6
    No elements for request

    if you observe, Device 1 data come for 15:47:15 then 15:47:18, 2 seconds are missing.

    #8631
    MikhailMikhail
    Moderator

    For instance, Device 1 “IN_TEMP” is polled every 3 seconds. To increase data refresh rate, you need to increase polling speed. Check delays in Communicator settings.

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