Forum Home › Forums › Communicating with Devices › Modbus › No Communication now
Tagged: IP address range
- This topic has 24 replies, 3 voices, and was last updated 8 months, 1 week ago by Mikhail.
-
AuthorPosts
-
January 22, 2021 at 4:53 pm #8145joeh6966Participant
I guess not; as you have already refused to help me run Rapid SCADA on Linux Mint.
My communication problems happened by Windows updates, and it took me 13 days to get it figured out. The system restore feature is awesome when it works. I just need to remember to close all running programs first to reduce errors.January 24, 2021 at 7:30 am #8150MikhailModeratoras you have already refused to help me run Rapid SCADA on Linux Mint
I don’t. Despite it’s more difficult to configure Rapid SCADA on Linux, Linux has significant benefits:
– No licenses fees;
– Reliability
– Many people just love it.July 20, 2023 at 11:10 am #13013mmParticipantI need to take readings from a meter using Rapid Scada. As a test, I used Rapid Scada installed on a laptop and established communication with the device having IP address 172.40.0.10). After verifying that it works, I installed Rapid Scada on a virtual machine (having IP address 10.142.92.135), repeated the same programming process of Rapid Scada and tried to read measurements from the device but it is not working. Communication line is running normal according to the log, but device goes from “undefined” to “error” a few seconds after uploading configuration. I tried pinging the device from the virtual machine and all packets are received so it is definitely on the same network.
When I used the laptop, its IP address was in the same range of the meter. Should the virtual machine have an IP address within the same range of the physical meter to establish communication? i.e. if the device is 172.40.0.10, should the virtual machine have an IP address in the range of 172.40.0.1 – 172.40.0.255 ?
July 20, 2023 at 11:32 am #13015MikhailModeratorShould the virtual machine have an IP address within the same range of the physical meter to establish communication?
This is not obligatory, and depends on the router settings. Could you copy a part of communication line log?
Ctrl + C
works in the Administrator app.July 20, 2023 at 11:37 am #13016mmParticipant——————————————————————————–
——————————————————————————–
2023-07-20 13:36:46 Initialize communication line 1 “SG1 H11 Line”
2023-07-20 13:36:46 Load device template from file KpModbus_FiscalMeters.xml
2023-07-20 13:36:46 Start communication line 1 “SG1 H11 Line”2023-07-20 13:36:46 Establish a TCP connection with 172.40.0.10:502
Error establishing TCP connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 172.40.0.10:5022023-07-20 13:37:07 Unable to communicate with Device 1 “SG1 H11 FM” because connection is not established
2023-07-20 13:37:07 Attempt to establish TCP connection can not be earlier than 5 seconds after the previous.
2023-07-20 13:37:07 Unable to communicate with Device 1 “SG1 H11 FM” because connection is not established
2023-07-20 13:37:08 Attempt to establish TCP connection can not be earlier than 5 seconds after the previous.
2023-07-20 13:37:08 Unable to communicate with Device 1 “SG1 H11 FM” because connection is not established
2023-07-20 13:37:08 Attempt to establish TCP connection can not be earlier than 5 seconds after the previous.
2023-07-20 13:37:08 Unable to communicate with Device 1 “SG1 H11 FM” because connection is not established
2023-07-20 13:37:08 Attempt to establish TCP connection can not be earlier than 5 seconds after the previous.
2023-07-20 13:37:08 Unable to communicate with Device 1 “SG1 H11 FM” because connection is not established
2023-07-20 13:37:08 Attempt to establish TCP connection can not be earlier than 5 seconds after the previous.
2023-07-20 13:37:08 Unable to communicate with Device 1 “SG1 H11 FM” because connection is not established
July 20, 2023 at 11:38 am #13017mmParticipantAnd the line state indicates that the communication line is running:
Line 1 “SG1 H11 Line”
———————
State : running
Action : 20/07/2023 13:38:05 Communication with Device 1 “SG1 H11 FM”Connection Channel
——————
Type: TcpClientCustom Parameters
—————–
TransMode = TCPCommon Properties
—————–
Modbus.Templates = Dictionary of 1 templatesActive Devices
————–
1. Device 1 “SG1 H11 FM” : errorJuly 20, 2023 at 12:02 pm #13018MikhailModeratorLooks like 172.40.0.10:502 is not available from the VM.
You could also download Hercules utility and try to connect by TCP client. I expect that result will be similar.July 20, 2023 at 12:11 pm #13019mmParticipantBut is this a Rapid Scada issue? Because when I ping 172.40.0.10 from the VM, packets are received.
July 20, 2023 at 1:04 pm #13020MikhailModeratorIt’s a network issue. Ping uses another protocol than TCP.
You should check a network configuration. Something like this.July 20, 2023 at 1:06 pm #13021MikhailModeratorAs a result you should be able to open a TCP connection to IP 172.40.0.10 port 502 by any application: Communicator, Hercules, Telnet, etc.
-
AuthorPosts
- You must be logged in to reply to this topic.