We have Citect Scada 2018 R2, we want to read some parameters from P3 protection relays by using the Easergy protocol normally found on The Power SCADA. is there a way of including the Easergy driver into Citect 2018 R2?
We have Citect Scada 2018 R2, we want to read some parameters from P3 protection relays by using the Easergy protocol normally found on The Power SCADA. is there a way of including the Easergy driver into Citect 2018 R2?
Hi Simon Mungwira ,
Can you share more details about the I/O Device > Protocol configured within Power SCADA?
From what I can comprehend from the user manual (https://www.se.com/au/en/download/document/P3TDSxxxxxEN/) this device appears to support two protocols, namely:
DNP
IEC 60870-5-103
Plant SCADA does have the DNPR driver (DNP protocol) and a IEC870IP (IEC 60870-5-104 protocol).
I think the DNPR driver might be your best option. Unfortunately there aren't any device templates like you have in Power SCADA, but you could easily export the variable tag configuration from Power SCADA and use it within Plant SCADA.
Here is a video of Power SCADA configuring Easergy with DNP: https://vimeo.com/311195484
Hi Olivier
Thank you for the reply.
Within Power SCADA the I/O Device protocol is Easergy which does not exist in Plant SCADA. I however used MODNET protocol to retrieve the data. I had to get the modbus mapping for the P3 relays though. It was going to be easier if the Easergy protocol was readily available in Plant SCADA.
Hi Simon,
You could copy the driver installer from the Power SCADA installation media. The Easergy driver could have a separate installer, or it could be bundled in the "PowerLogic" or "PowerConnect" driver suite.
However, your standard Citect SCADA server license most likely does not allow this driver in runtime. You might have to contact your Sales representative for an additional license. If it is for sale then it will be added to your server license(s) as a feature.
Hi Patrick
Thank you very much. I copied the installer from the Power SCADA installation media and changed the installation path to Citect 2018 R2 Bin folder.
It works.
It could be that Easergy is licensed from Power SCADA. Please be aware that it may behave strange at runtime since it is not fully supported by Plant SCADA.