IEC 61850 Station control on P139

[ManuelTrebilcock]

Dear community, 

I am having problems integrating an Easergy MiCOM P139 via IEC 61850. Everything works fine but the control of objects. When you try to control objects via a simulator using remote-control, it works fine. But when you try to control objects using a GE RTU we have problems because first, you have to active the Loc.StaOper and then activate the command. 

We want to avoid the use of this sequence and do it directly with one command. Hoe can we set up the configuration to work using station control with just one command?

Best regards,

Manuel Trebilcock

[AndreMelo · Accepted solution]

Hi @ManuelTrebilcock 

You can use the MAIN: Inp.asg.interl.deact -  221.007 to disable the Local Remote interlock of the Controllable Object. However, the relay is working properly for the application.

A command via protocol is a remote command so the GE Rtu shall be configured to send the originator category (orCat) = remote-control or station-control. 

The orCat is a mandatory parameter and most of the RTU can configure that, I am pretty sure it is possible in the GE RTU as well or you can change it directly in the SCD.

OrCat value meanings:

Here is one example in Saitel:

Best Regards

[ManuelTrebilcock]

Thank you @AndreMelo for saving me one more time. I really appreciate your help.

[ManuelTrebilcock]

I have another doubt: according to the manual the signal "MAIN:Inp.asg.interl.deact" disables interlocking of control commands
for switchgear. So, does it mean that every interlock is going to be disabled, not only the local/remote?

[AndreMelo]

Hi @ManuelTrebilcock ,

Yes, if it doesn't fit your application you can set a DROP OFF to disable just while the command is executing using logic. another way is for the GE person to send a by-pass interlock with the command. But if they are able to do that they might be able to configure the orCat.

I'm happy it helped you.

Best Regards

[Michael_H]

All

If interlocking checking is enabled in the device configuration, then it is in the interest of the user to have controls been checked. It is not an acceptable solution to just disable interlocking checking for the acceptance of controls in general. If an erroneous control was executed and damage was created, SE will be held responsible for not having rejected that control.

Bypassing checks can only be provided exception based on the responsiblitiy of the user. If the configuration is modified as proposed below, a user statement is needed - in written - that he approves operation of switchgear without checks.

Easergy P30 firmware defaults to LocSta="false" meaning the acceptance of controls from remote (e.g. control center). For un-manned substations remote controls are the typical mode of operation. Personnel entering the site will need log in and force LocSta to "true" in order to control switchgear from an operator workplace at station level. The forcing of LocSta is part of the automation system. For controls locally from the P30 front panel, the IED can be set to local. All control are permanently executed under interlocking checking.

In order to facilitate the engineering of the automation system re. forcing of LocSta, an application oriented enhancement of the IED firmware has been proposed. This solution is not yet implemented in Easergy P30.

Best regards,

Michael