Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
General
Points can be inbound or outbound. The entry points, that is the points that are acquired by the client protocol, basically have two main parameters: the type of point and its address. The output points, used for remote controls, have in addition to the type and address a parameter to specify the output operation. In the address map of an IED, addresses are never repeated. Addresses are unique regardless of the type of the point.
Types of points
The communication module in Slave mode implements:
Receipt of date and time for timing;
Response to a request for general question
Sending information frames, unsolicited, due to changes of data in memory.
Time tag of 56 bits in length;
Reception of single and double digital dot commands;
Reception of Command select before operate;
Treatment of spot quality (QDS);
The types of implemented points are defined by the data objects themselves defined in the IEC standard, the following.
M_SP_NA: 1 - Single-point information
Simple binario entry point, value 0 or 1. The variants with "timetagtime tag" M_SP_TA(=2) and M_SP_TB(=30) if sent by the FDI are also treated, but in the registration, only this type is used.
M_DP_NA: 3 - Double-point information ;
Double entry inputtimeinput time tag point, which can assume states 0 through 3. Typically used in signaling key states and circuit breakers. The variants with "timetag" M_DP_TA(=4) and M_DP_TB(=31) if sent by the FDI are also treated, but in registration, only this type is used.
M_ST_NA: 5 - Step position;
Step or step value, in the faiza range from -64 to +63, is mainly used for transformer tap position or other position information. The variants with "timetagtime tag" M_ST_TA(=6) and M_ST_TB(=32) if sent by the IED are also treated, but in the registration, only this type is used.
M_BO_NA: 7 - Bitstring with 32 bits ;
Information from binario binary states as a 32-bit chain. No manipulation is done by the driver. The configuration is treated as a long number. The variants with "timetag" time tag M_BO_TA(=8) and M_BO_TB(=33) if sent by the IED are also treated, but in the registration, only this type is used.
M_ME_NA: 9 - Measured value, normalized ;
Normalized 16-bit analog measurement with signal. Value between -32768 and + 32767. It is calculated as a real number between 0 and 1 before being assigned to the tag in real timereal-timetime. You must use scaling"scalling" to reproduce the value in engineering engithe neering unit. The variants with "timetagtime tag" M_ME_TA(=10) and M_ME_TD(=34) if sent by the FDI IED are also treated, but in the registration, only this type is used.
M_ME_NB: 11 - Measured value, scaled value ;
Scalar The scalar analog measurement used for transmission of anal[ogic) quantities. Also 16-bit, value between -32768 and 32767. The variants with "timetagtime tag" M_ME_TB(=12) and M_ME_TE(=35) if sent by the FDI are also treated, but in the registration, only this type is used.
M_ME_NC: 13 - Measured value short floating-point;
Analog measurement in fractional real number format, used for transmission of anal[ogic) quantities. Measures are 32-bit fields in the IEEE STD 754 format, which implements floating-point numbers. The variants with "timetagtimetagtime tag" M_ME_TC(=14) and M_ME_TF(=36) if sent by the IED are also treated, but in the registration, only this type is used.
M_IT_NA: 15 - Integrated totals ;
Full analog measurement with signalsignalthe . Measures with integer 32 bits. The variants with "timetagtime tag" M_IT_TB(=16) and M_ME_TC(=37) if sent by the FDI are also treated, but in the registration, only this type is used.
C_SC_NA: 45 - Single command ;
Command for simple point (1 bit). Command details can be chosen by clicking the button to the right of the field. You can also enter directly the number that is the command code resulting from the choice of details. Each point will be statically parameterized in the POINTS table , so that one point for opening and one for closing one-bit keys must be configured.
C_DC_NA: 46 - Double command ;
Command for double point (2 bits). Command details can be chosen by clicking the button to the right of the field. You can also enter directly the number that is the command code resulting from the choice of details. Each point will be statically parameterized in the POINTS table , so that one point for opening and one for closing keys with two-bit signaling must be configured.
C_RC_NA: 47 - Regulating step command ;
Step adjustment control is commonly used for sending pulses up or down transformer tap switches. Command details can be chosen by clicking the button to the right of the field. You can also enter directly the number that is the command code resulting from the choice of details. Each point will be statically parameterized in the POINTS table , so that one point must be set up to climb and another to lower the tap position.
C_SE_NA: 48 - Set point Setpoint command, normalized value ;
For sending 16-bit set points, normalized to IEDS IEDSIEDs that support this type of command.
The value to be sent is what is currently as the value of the "tag" whose address was sent in the command.
C_SE_NC: 50 - Set point Setpoint command, short floating-point value;
For sending 32-bit set points, in Floating-point format IEEE STD 764, to IEDs that support this type of command. The value to be sent is what is currently as a the value of the "tag" whose address was sent in the command.
C_BO_NA: 51- Write Bitstring 32-bit
For writing on the server IED a binario binary state information as a 32-bit string. No manipulation is done by the driver. The configuration is treated as a long number without a signal. The value to be sent is what is currently as a the value of the "tag" whose address was sent in the command. The tag type must be "long" or AnalogInt, i.e. a 32-bit integer.
Point address
The field Address to be filled in the point registration is what the standard calls "Information Object Address". This is a 3-byte number.
Command parameter
The command parameter is for the types of commands implemented in one-byte code, which details what and how the command should be executed by the IED. In this implementation, when a point with output command type is registered, this field appears to be filled in. If you already know the code you want to use, just type it in the field. If it is not known, click the button to the right of the field to show a window with the actions and details that can be chosen.
Parameter Setting
The codes generated by choosing items in the command parameter definition window are formed by calculating the sum of two installments (A and B), the first indicative of the action, and the second of the details of the operation, as defined below:
For Simple Command C_SC_NA:
0 = Off (A)
1 = Connect (A)
0 = No detail (B)
4 = Short Pulse (B)
8 = Long Pulse (B)
12= Persistent Signal (B)
For Dual Command C_DC_NA:
1 = Off (A)
2 = Call(A)
0 = No detail (B)
4 = Short Pulse (B)
8 = Long Pulse (B)
12= Persistent Signal (B)
For Setting Command (Tap) C_RC_NA:
1 = Go down (A)
2 = Climb (A)
0 = No detail (B)
4 = Short Pulse (B)
8 = Long Pulse (B)
12= Persistent Signal (B)
The remaining option is whether the command will be of type Select - just to select the device to be commanded, or if it is Run - this is to send the action command properly. In the case of Select should add 128 to the code so far obtained by the sum of plots A and B.
Example: code = 9, in a simple command, means Long wrist towards Connect device;
Using the parameter in the Server protocol (Slave)
The server when receiving a command from the master (client) performs it according to the parameter coming in the message. The parameter set in the server database is not used, can be configured in any way.
The behavior of the server in executing the command is explained below.
Select / Run
SELECT - there will be no execution properly, that is, there will be no change in the memory of the server. A message will be sent to the log (Trace), indicating the SELECT mode, if the exit point was actually found on the server. If the dot does not have a "POINT NOT FOUND" error message, it will appear in the log.
EXECUTE- The command will run normally and will appear in the log, the fact-indicating message with the INDICATION EXECUTE.
Detail Options - Option B
0 - None - Only a toggle will be done in the target point state of the command. (if zero goes to 1 if 1 goes to zero), whatever the value of portion A.
4 - Short Pulse - The value of parcel A will be placed at the destination point, thus maintained for 100 ms, and then the original value will be restored.
8 - Long Pulse - The value of parcel A will be placed at the destination point, thus maintained for 1000 ms, and then the original value will be restored.
12 - Persistent - The value of parcel A will be placed at the destination point and left like this.
Access Type
Because it is a communication module in slave mode (server) there is a need for some characteristics suitable for parameterization of the field Access Type of the table Points:
For points with types that are read:
M_SP_NA: 1 - Single-point information ;
M_DP_NA: 3 - Double-point information ;
M_ST_NA: 5 - Step position;
M_BO_NA: 7 - Bitstring with 32 bits ;
M_ME_NA: 9 - Measured value, normalized ;
M_ME_NB: 11 - Measured value, scaled value ;
M_ME_NC: 13 - Measured value Float;
M_IT_NA: 15 - Integrated totals ;
The Access Type should be set with:
ReadOnStartup= On;
ReadPooling= Always;
ReadPoolongRate: 500 mili
WriteEnable = On
WriteEvent= Changed;
AccepUnsolictited = On;
For points with types that are commands:
C_SC_NA: 45 - Single command ;
C_DC_NA: 46 - Double command ;
C_RC_NA: 47 - Regulating step command ;
C_SE_NA: 48 - Set point pointSetpoint command, normalized value ;
C_SE_NC: 50 - Set point pointSetpoint command, 32-bit floating point;
C_BO_NA: 51- Write Bitstring 32-bit
The Access Type should be set with:
ReadPooling = Never;
WriteEnable = On
WriteEvent= Changed;
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
On this page:
|