For the Sepam 10 relay, as shown in the attached image, Remote Indication bits are provided that indicate when a trip occurs. These Remote Indication bits can be read using Modbus communication.
However, it is important to note that these Remote Indication bits are not latched. In other words, after the Sepam 10 sends a trip order to the circuit breaker and once the fault has been cleared, these remote indication bits will reset back to zero.
Even if the trip relay output on the Sepam 10 relay is set to Latching Mode, the Modbus Remote Indication bit will not remain latched.
In order to be sure to capture all the events from the Sepam 10, especially Protection Trips, it is essential to modify your SCADA device driver to read the time-tagged events from the Sepam relay. Using the Remote Indication bits is not reliable, and you run the risk of missing events if a fault occurs during a communications outage.
AEDL3
However, it is important to note that these Remote Indication bits are not latched. In other words, after the Sepam 10 sends a trip order to the circuit breaker and once the fault has been cleared, these remote indication bits will reset back to zero.
Even if the trip relay output on the Sepam 10 relay is set to Latching Mode, the Modbus Remote Indication bit will not remain latched.
In order to be sure to capture all the events from the Sepam 10, especially Protection Trips, it is essential to modify your SCADA device driver to read the time-tagged events from the Sepam relay. Using the Remote Indication bits is not reliable, and you run the risk of missing events if a fault occurs during a communications outage.
AEDL3
Released for:Schneider Electric Australia
