There are lot of reasons to delays of responding Modbus requests:
- - In network
- - Coordination between different clients systems.
- - In SATEC device.
- - Instable power supply of SATEC devices/s and the network equipment.
If terminal voltage input V4 is not used you can use it for monitoring power supply voltage.
Reset Min/Max registers and then when you will see not answered requests, check MAX V4.
Reasons in SATEC device is a small part of the troubleshooting.
- Upload and check following logs:
- Event log. Especially pay attention to Errors and Power Down events.
- PQ log
- SOE
- Faut log
Check for events in time period when Modbus request was not answered.
-> If terminal voltage input V4 is not used you can use it for monitoring power supply voltage.
Reset Min/Max registers and then when you will see not answered requests, check MAX V4.
2. PM180 is able to handle several tasks simultaneously, but resourced for the device are still limited.
Upload all Waveform logs which were recorded in that specific times range.
The first thing that must be checked - is the SATEC device responding PING requests without gaps.
That point we are asking you to check every your request for such issues.
The important to know is the SATEC device responding ping when it doesn't respond Modbus request.
If SATEC device responses PING requests stably without gaps
a) Even if exists only one system that is requesting SATEC device continuously is should manage opening and creating connection correctly.
There are two ways of correct managing connections:
- If the SCADA system is creating new connection each time, the SCADA must close the connection each time after receiving response of after a delay.
- SCADA is using previously created connection, and creating a new connection only when the previously connection was interrupted.
When a SCADA system is creating new connection to device every request and may cause of available TCP sockets busy very quickly.
b) If there are several clients system simultaneously managing connection became more critically and complicated.
c) Is ExpertPower Client enabled?
d) Is TCP Notification Client Enabled?
c) Is used PMU in the device?
If PING responses are not stable, with gaps:
a) Communicate to the device from nearest to the device Ethernet switch and rerun the PING test.
b) Check correctness of the Ethernet cable and equipment
- what is the cable length?
- Is the cable shielded?
- Is the corresponding Ethernet switch grounded?
- Is the ethernet cable installed separately from power and current measuring cables?
c) In the time period when the SATEC device doesn't response ping, check are other devices responding correctly.
d) Check overloading the network when SATEC device doesn't response PING.
Is there some new equipment connected casually in the network? Just for example: video cameras.