Modbus TCP No sending command for write new value to slave device

Forum Home Forums Communicating with Devices Modbus Modbus TCP No sending command for write new value to slave device

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • #15154
    nakorn
    Participant

    Hello I’m a newbie for Rapidscada. after install and follow a quick guide on youtube. My project can receive information for a simulation device but It doesn’t have any sending command to a simulation device. Please suggest

    #15159
    Mikhail
    Moderator

    Hello,
    Could you clarify your question by providing screenshots?

    #15179
    nakorn
    Participant

    Thank you, Mikhail. Now I deleted the project and made a new one, which worked. Could the problem be from adding a new device on Device Polling?

    Add a new device under menu Line Option

    Result communication log

    No a new device in Devices Table

    • This reply was modified 3 weeks, 4 days ago by nakorn.
    • This reply was modified 3 weeks, 4 days ago by nakorn.
    • This reply was modified 3 weeks, 4 days ago by nakorn.
    #15183
    nakorn
    Participant
    #15193
    Mikhail
    Moderator

    Also check the communication line log after sending a command to get a error message.
    Please provide a screenshot of the Modbus template.

    #15196
    nakorn
    Participant

    Thank you, Mikhail. here is a short video. clip.https://drive.google.com/file/d/1MmwjoQg3lcLW2UWyoqEmXKP69ghybPqu/view
    I can’t find a command to send to the Modbus slave simulation.

    #15203
    Mikhail
    Moderator

    To check the communication line log, navigate to Line Stats – Line Log, or find the file lineXXX.log
    Then find in the log a moment when you send a command.

    #15208
    nakorn
    Participant

    This is information in the log file when I send a command.

    2024-08-22 17:18:18 [IMUM04][IMUM04$][ACT] Command with ID 7405906156018121508 to the device 2 from C:\Program Files\SCADA\ScadaComm\Cmd\cmd_7405906156018121508.dat
    2024-08-22 17:19:03 [IMUM04][IMUM04$][ACT] Command with ID 7405906350209285025 to the device 2 from C:\Program Files\SCADA\ScadaComm\Cmd\cmd_7405906350209285025.dat
    2024-08-22 17:19:50 [IMUM04][IMUM04$][ACT] Command with ID 7405906556098538204 to the device 2 from C:\Program Files\SCADA\ScadaComm\Cmd\cmd_7405906556098538204.dat
    2024-08-22 17:19:56 [IMUM04][IMUM04$][ACT] Command with ID 7405906580700786187 to the device 2 from C:\Program Files\SCADA\ScadaComm\Cmd\cmd_7405906580700786187.dat

    https://drive.google.com/file/d/1J5czW3e5s040Lglbo2GiegaZOPVVueUc/view

    #15210
    nakorn
    Participant

    Sory Mikhail, I found it.

    2024-08-22 22:03:02 Command 06 to the device [2] Tim-94n-4ch
    Error: invalid command

    2024-08-22 22:03:02 Session with the device [2] Tim-94n-4ch
    Request element group “Tim-94n-4CH”
    Send (12): 79 BD 00 00 00 06 02 03 00 00 00 0D
    Receive (7/7): 79 BD 00 00 00 1D 02
    Receive (28/28): 03 1A 02 EE 02 08 01 90 40 18 01 F4 00 C8 01 2C 01 90 00 00 00 00 00 00 00 00 00 00
    OK

    #15217
    Mikhail
    Moderator

    Now it’s more clear.
    When you send a command:
    Command number – keep by default, it’s not used when the command code is set.
    Command code – the code from the Modbus template.

    Could you make a screenshot of the Modbus template with the selected register to which you send commands?

    • This reply was modified 3 weeks, 1 day ago by Mikhail.
    #15225
    nakorn
    Participant

    Hi Mikail. I need to send a command to write updated data to register 6 of slave ID2. The command frame should be “2-byte transaction id, 0x00 0x00 0x00 0x06 0x02 0x06 0x00 0x06 0x01 0x2C”

    #15232
    Mikhail
    Moderator

    Hi,
    Please send a screenshot of the Modbus template that you created in the Rapid SCADA project.

    #15264
    nakorn
    Participant

    Hi Mikail, Thank you for your help. Now I can write data from the Webstation.

    #15267
    Mikhail
    Moderator

    Good 🙂

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