kirjono mudiarto

Forum Replies Created

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • May 18, 2020 at 3:57 am in reply to: unable to connect localhost/scada #6846
    kirjono mudiarto
    Participant

    it solved now, i recreate the default web site in IIS

    May 18, 2020 at 3:12 am in reply to: unable to connect localhost/scada #6845
    kirjono mudiarto
    Participant

    my OS is windows 10

    January 27, 2020 at 6:02 am in reply to: Remote Procedure Call (RPC) #6444
    kirjono mudiarto
    Participant

    I did not find the OPC server software, it looks like the manufacturer no longer supports it. What about the other option as you said creating native drivers?

    January 22, 2020 at 1:02 am in reply to: Remote Procedure Call (RPC) #6438
    kirjono mudiarto
    Participant

    Could you guide me step by step how to implement this OPC Server, and also i want to integrate with other devices like PLC, meter, MV Switchgear?

    January 21, 2020 at 1:18 am in reply to: Sending JSON text to Rapid SCADA #6431
    kirjono mudiarto
    Participant

    Thanks Mikhail, I will start a new topic

    January 20, 2020 at 4:49 am in reply to: Sending JSON text to Rapid SCADA #6428
    kirjono mudiarto
    Participant

    Hi,

    I seem to have the same problem.
    I have several devices communicating using Modbus protocol and I have sucessfully communicated with them except for one that communicates with the Remote Procedure Call (RPC) protocol and it said that the data format is JSON.
    How can I communicate with RPC through rapidscada?

    Thanks
    kirjono

    January 20, 2020 at 4:37 am in reply to: Slave Device Failure #6427
    kirjono mudiarto
    Participant

    Thank you very much Mikhail

    January 3, 2020 at 3:28 am in reply to: Slave Device Failure #6302
    kirjono mudiarto
    Participant

    Hi Mikhail,

    thank you for the replies, now it works.
    I have changed the address to 30006-30007.
    I’ve realized that the address must be added by 1 since rapidscada address starting from 1 and device address starting from 0.

    December 20, 2019 at 1:42 am in reply to: Slave Device Failure #6227
    kirjono mudiarto
    Participant

    2019-12-20 08:04:18 Communication session with the Device 1 “Test device”, type: KpModbus, address: 1, call number: 192.168.0.152
    Request element group “gateway”
    Error writing data: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
    Receive (0/7):
    Communication error!
    Unable to request because connection is not established
    Unable to request because connection is not established

    2019-12-20 08:04:20 Establish a TCP connection with 192.168.0.152:502

    2019-12-20 08:04:20 Communication session with the Device 1 “Test device”, type: KpModbus, address: 1, call number: 192.168.0.152
    Request element group “gateway”
    Send (12): 00 00 00 00 00 06 01 04 75 34 00 02
    Receive (7/7): 00 00 00 00 00 03 01
    Receive (2/2): 84 04
    Device error: [04] SLAVE DEVICE FAILURE!
    Request element group “gateway”
    Send (12): 00 00 00 00 00 06 01 04 75 34 00 02
    Receive (7/7): 00 00 00 00 00 03 01
    Receive (2/2): 84 04
    Device error: [04] SLAVE DEVICE FAILURE!
    Request element group “gateway”
    Send (12): 00 00 00 00 00 06 01 04 75 34 00 02
    Receive (7/7): 00 00 00 00 00 03 01
    Receive (2/2): 84 04
    Device error: [04] SLAVE DEVICE FAILURE!

    2019-12-20 08:04:21 Disconnect from 192.168.0.152

    December 20, 2019 at 1:34 am in reply to: Slave Device Failure #6222
    kirjono mudiarto
    Participant





    https://ibb.co/ZMcGyz8
    https://ibb.co/cC5DD88
    https://ibb.co/H218Bqm
    https://ibb.co/mG7RRJ8
    https://ibb.co/T2DMmS5

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)