SCADA Client API Command not Working

Forum Home Forums New Ideas SCADA Client API Command not Working

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #18062

    Rapid SCADA Test Client
    Server is ready = True
    User is logged in = True

    Connected to localhost
    Session ID = 682001045626589992
    Server name = Server 6.2.2.1

    Select action:
    0 – exit
    1 – get status
    2 – terminate session
    *** File Operations ***
    3 – get file info
    4 – download file
    5 – upload file
    *** Access Archive ***
    6 – get current data
    7 – get trend
    8 – get timestamps
    9 – get slice
    10 – get last write time
    11 – write current data
    12 – write historical data
    *** Access Events ***
    13 – get event by ID
    14 – get events
    15 – write event
    16 – acknowledge event
    *** Commands ***
    17 – send command
    18 – get command
    17
    Enter channel number: 104
    Enter command value: 1
    Command sent successfully

    Select action:
    0 – exit
    1 – get status
    2 – terminate session
    *** File Operations ***
    3 – get file info
    4 – download file
    5 – upload file
    *** Access Archive ***
    6 – get current data
    7 – get trend
    8 – get timestamps
    9 – get slice
    10 – get last write time
    11 – write current data
    12 – write historical data
    *** Access Events ***
    13 – get event by ID
    14 – get events
    15 – write event
    16 – acknowledge event
    *** Commands ***
    17 – send command
    18 – get command
    6
    Enter channel number: 104
    Channel data = 0 (0)
    Channel list ID = 7644628203401034737

    Select action:
    0 – exit
    1 – get status
    2 – terminate session
    *** File Operations ***
    3 – get file info
    4 – download file
    5 – upload file
    *** Access Archive ***
    6 – get current data
    7 – get trend
    8 – get timestamps
    9 – get slice
    10 – get last write time
    11 – write current data
    12 – write historical data
    *** Access Events ***
    13 – get event by ID
    14 – get events
    15 – write event
    16 – acknowledge event
    *** Commands ***
    17 – send command
    18 – get command

    Source Code :

    https://drive.google.com/file/d/1fS5HAM9HH_c6ca1He9L2uYQ_ruhAhn0Z/view?usp=sharing

    #18063
    #18064

    Exe Files

    #18065

    Hi Team,

    I am testing command write functionality using the Rapid SCADA Test Client.

    Environment:

    * Rapid SCADA Server Version: 6.2.2.1
    * Connected successfully to localhost
    * User login successful

    Test performed:

    1. Selected “Send Command” (Option 17)
    2. Channel Number: 104
    3. Command Value: 1

    Result:

    * Test Client response: “Command sent successfully”

    However, when I read the channel value afterward using “Get Current Data” (Option 6), the channel value remains 0 and the command does not appear to be executed by my driver.

    Test Client Output:

    * Channel: 104
    * Command Value Sent: 1
    * Response: Command sent successfully
    * Current Channel Value after command: 0

    Could you please guide me on the following points?

    1. How should an external application/API send commands to this driver?
    2. Which Rapid SCADA server API should be used for command write operations?
    3. Does the driver need to implement a specific command handling interface or method to receive commands?
    4. Is there any configuration required in Communicator, Server, or Webstation to enable command forwarding?
    5. How can I verify whether the command reaches the driver but is not processed?

    Any sample code or API documentation for writing commands from an external application would be greatly appreciated.

    Regards,

    Prabhu N

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