Command Signaling

Description

Typically when a command is sent, it is intended to change the state of an equipment connected to an IED.
For example: A change in the state of a tag that is addressed to send a command message is performed on the Action.NET, and this command is sent. Another tag, which receives data acquisition from the circuit breaker state, is expected to change and contain the representative state of the disconnected circuit breaker.
The feature should check, if within an expected time, there has been a change of state of the circuit breaker, to the expected state.
For this verification to be done, the Action.NET system needs to be informed, which tag will contain the signaling, the state that is expected, and the acceptable time for the arrival of the information, from the sending of the command.

Feature configuration

SignallingCommand Class

The class is available in DefaultNewProject and contains the method described below:
Method SendCmd - This is the only method that needs to be called by the user in the command windows.

public void SendCmd(string outTag, string inTag, int oper, int resultVal,int timeout, uint password
                    , string resultTag=””)

Objetivo:
Monta um string com os parâmetros para que com eles a task SendCommands possa fazer o envio correto do comando.

Onde:
outTag – Nome do tag de saída. Ex: Tag.TagOff 
inTag - Nome do tag em sinalizará o comando. EX: Tag.Disj
oper –   Operação a ser feita no tag da saída, com os códigos:
		0-Toggle;
		1-Latch one;
		2-Latch zero;
		3-Pulse on;
		4-Pulse Off	
resultVal – Estado esperado para o tag de sinalização.
	timeout – Tempo máximo em seg. para a confirmação da sinalização.
password – Password para comandos, definida na configuração do canal
resultTag – Nome de um tag para receber o resultado da verificação: 0=Sucesso; 1=Falha

Use of Master Protocols

To use the Command Signaling Check feature through protocols, simply do code behind routines to change the output tags as it has been done until this release. For example toggle of value. In fact, you don't need to change any of these existing routines or Actions.
You will only need to configure the POINTS table of new specific entries to define Command Signaling for each of these protocols. These configurations are available for the DNP3, IEC104 and IEC61850 protocols in Master modes. For information about these settings refer to the appropriate protocol manual.

Event Messages

As a result of command signaling functionality, the methods themselves generate or change command failure or success indication messages.

Success Case

The following figure shows a success case in the command signaling.

The message "POWER COMMAND" is generated within the An_Cmd_Disj Command Window when sending the command when the command send button is pressed. If the expected signaling arrives normally within the expected time, the signaling tag will receive in its attribute PrefixAlarmMessage the acronym **SCM{}, This attribute is placed in the next alarm message generated by changing the state of the circuit breaker.

Unsuccessful Case

The following figure shows a case of NOT success in command signaling.

In this figure are shown the messages in the case of an unsuccessful command. That is, the expected state within the expected time, for the flag tag did not arrive. From within the AN_Commands class, the message indicating, the output tag, and in the message part the COMMAND UNSUCCESSFUL indication and the tag in which the flag was expected is generated.

Configuration

The acronym **SCM** is used by default, prefixing the alarm to change the state of the key state signaling tag. If you want another acronym, simply place the preferred text in the StartValue attribute of the text tag: zz_system. PrefixForCommandSignal.StartValue.