Monitoringsystem TAPGUARD 260

Transcription

1 Monitoringsystem TAPGUARD 260 Supplement /01 Protocol description IEC

2 All rights reserved by Maschinenfabrik Reinhausen Copying and distribution of this document and utilization and communication of its contents are strictly prohibited unless expressly authorized. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or ornamental design registration. The product may have been modified after this document went to press. We expressly reserve the right to make changes to the technical data, the design or the scope of delivery. Generally, the information provided and the arrangements agreed during processing of the relevant quotations and orders are binding. The original operating instructions were drawn up in German.

3 Table of contents Table of contents 1 General notes About this document Information about the standard Abbreviations used Voltage regulator connections Settings on the voltage regulator Communication interface RS Communication interface RS Fiber-optic cable (optional) Data points Message structure Function types Type codes Data types Monitoring direction Control direction Tabelle Steuerungsrichtung 103 TC230-1 von Sequences General query Maschinenfabrik Reinhausen /01 EN TAPGUARD 260 3

4 Table of contents 5.2 General command General query, generic data Generic command (write entry with version) Tap position telegram Structure of telegram Examples of messages for tap position telegrams TAPGUARD /01 EN Maschinenfabrik Reinhausen 2011

5 1 General notes 1 General notes 1.1 About this document This document describes implementation of the interface protocol IEC for the TAPGUARD 260. Read this description along with the technical file for the TAPGUARD Information about the standard The interface protocol IEC was originally developed for communication between protective devices. The pre-defined function types and associated information numbers are not suitable for the information that the Monitoring system has to transfer. A function type from the "private sphere" of the protocol is therefore used for all "non-generic data points". The information numbers for all general commands and messages with the function type from the "private sphere" are specific. Analog values are transferred in the control direction (command) and monitoring direction (message) using a generic message type. All measured values are assigned to class 2 and all parameters to class 1. In addition to the 9.6 and 19.2 kilobaud rates required by the standard, baud rates of 38.4 and 57.6 kilobauds can also be selected on the Monitoring system. Maschinenfabrik Reinhausen /01 EN TAPGUARD 260 5

6 1 General notes 1.3 Abbreviations used Abbreviation Definition ASDU Application Service Data Unit BCD Binary Coded Decimal CIC Communication Interface Card GQ General query GPI General Purpose Input GPO General Purpose Output Fiber-optic cable Fiber-optic cable MR Maschinenfabrik Reinhausen RTC Real Time Clock TAPCON -trol PC software for displaying regulator data Table 1 Abbreviations 6 TAPGUARD /01 EN Maschinenfabrik Reinhausen 2011

7 2 Voltage regulator connections 2 Voltage regulator connections The physical interfaces RS232, RS485 and optional fiber-optic cables are provided on the Monitoring system for data transfer via the IEC protocol. Figure 1 CIC card 1 RS232 (9 pin female SUB-D connector) 2 RS485 3 Ethernet RJ45 (optional) 4 FH-ST or F-SMA fiber-optic cable in 850 nm or 660 nm (optional) 5 Reset key 6 TxD LED for transmit signal 7 RxD LED for receive signal 8 Clk LED for operating mode (flashes for 2 seconds) 9 Clip for connecting cable shield with functional ground Maschinenfabrik Reinhausen /01 EN TAPGUARD 260 7

8 2 Voltage regulator connections RS232 RS485 Fiber-optic cable (optional) 9 pin female SUB-D connector Pin 2: TxD Pin 3: RxD Pin 5: GND 3 pin connector from Phoenix (MC1.5/3 GF 3.5) Pin 1: GND (100 Ω ground resistance) Pin 2: B (inverted) Pin 3: A (not inverted) Polarity: A > B by 200 mv corresponds to 1. A < B by 200 mv corresponds to 0. An interrupted communication line corresponds to 1. The start bit has the designation 0. Recommended terminating resistor 120 Ω. FH-ST (850 nm or 660 nm) F-SMA (850 nm or 660 nm) Table 2 Interfaces available Transfer on physical plane: Asynchronous with 8 data bits, even parity, 1 stop bit (8E1) 8 TAPGUARD /01 EN Maschinenfabrik Reinhausen 2011

9 3 Settings on the voltage regulator 3 Settings on the voltage regulator The following chapters describe how to set the parameters for communication at the relevant interface on the TAPGUARD 260. > Configuration > Next* > Comm. interface Depending on the product version and software, you will need to press "Next" a varying number of times to reach the "Comm. interface" menu. You will find more information on how to set the parameters in the technical file for TAPGUARD Communication interface RS232 Communication interface RS232 Baud rate communication Fiber-optic cable light ON/OFF Local SCADA address 9.6/19.2/38.4/57.6 kbaud not used (0 = broadcast message) ms (e.g 2 ms, in order to compensate for the response time of an external Send delay time converter RS485/RS232 when switching between transmit and receive operation) Table 3 Interface settings RS232 Maschinenfabrik Reinhausen /01 EN TAPGUARD 260 9

10 3 Settings on the voltage regulator 3.2 Communication interface RS485 Communication interface RS485 Baud rate communication 9.6/19.2/38.4/57.6 kbaud Fiber-optic cable light ON/OFF not used Local SCADA address (0 = Broadcast-Meldung) ms (e.g 2 ms, in order to compensate Send delay time for the response time of an external converter RS485/RS232 when switching between transmit and receive operation) Table 4 Interface settings RS Fiber-optic cable (optional) Communication interface Baud rate communication Fiber-optic cable light ON/OFF Local SCADA address FOC 9.6/19.2/38.4/57.6 kbaud ON (1 corresponds to light On) or OFF (1 corresponds to light Off) (0 = Broadcast-Meldung) Send delay time Table 5 not used Interface settings FOC In addition to the 9.6 and 19.2 kilobaud rates required by the standard, baud rates of 38.4 and 57.6 kilobauds can also be selected on the Monitoring system. 10 TAPGUARD /01 EN Maschinenfabrik Reinhausen 2011

11 4 Data points 4 Data points 4.1 Message structure The function types, type codes and data types which are listed in the data tables are explained below Function types Type codes Data types 110 = function type from the private sphere (can be defined specifically) 254 = generic function type 255 = global function type 1 = message with time stamp 6 = time synchronization 7 = general query 10 = generic data 20 = general command 21 = generic command 7 = short real Maschinenfabrik Reinhausen /01 EN TAPGUARD

12 4 Data points 4.2 Monitoring direction All spontaneous messages (in the event of changes) are transmitted with a time stamp. The time stamp always relates to when the message is sent. A message caused by a general query is sent without a time stamp. Type code Function type Info number Description SI command 1 active SI command 2 active SI command 3 active Motor-drive unit running Message no Message no Message no Message no Details of SI commands 1/2/3 can be found in the "General commands" section. Parametrizable messages The TAPGUARD 260 has 4 messages which can be parametrized. These can be put on an input or relay. The messages are ON when there is a signal at the parameterized input or the parameterized relay is activated. Parameter setting error TAPGUARD 260. ON when an error has occurred in the parameterization Local / remote message The TAPGUARD 260 does not have a local / remote switch. The local/remote operation function can however be parameterized on an input Tap position Green Event yellow Event red On-site event yellow On-site event red Table 6 Data points in monitoring direction 12 TAPGUARD /01 EN Maschinenfabrik Reinhausen 2011

13 4 Data points With some firmware versions of the, most signals can be transmitted to the SCADA system at the digital input terminals. When triggered, the interface addresses to the corresponding inputs behave as follows: Type code Function type Info number Description Card type Specification IO X1/ IO X1/ UC1 X1/ UC1 X1/ UC1 X1/ UC1 X1/ UC1 X1/ UC1 X1/ UC1 X1/ UC1 X1/ UC1 X1/ UC1 X1/ UC2 X2/ UC2 X2/ UC2 X2/ UC2 X2/ UC2 X2/ UC2 X2/ UC2 X2/ UC2 X2/ UC2 X2/ UC2 X2/12 Table 7 Data points in monitoring direction Maschinenfabrik Reinhausen /01 EN TAPGUARD

14 4 Data points Type code Function type GIN LSB GIN MSB Data type Class Description Tap position Desired voltage value Desired voltage value Desired voltage value Operation counter The following GIN numbers have been reserved for customer-specific changes or future extensions Reserve Reserve Reserve Actual voltage (in V) Control deviation (in %) Active current (in %) Reactive current (in %) Apparent current (in %) Frequency Table 8 Generic data in monitoring direction 14 TAPGUARD /01 EN Maschinenfabrik Reinhausen 2011

15 4 Data points 4.3 Control direction The remote mode must be set for commands from the control system on TAPGUARD 260 to be executed on the Monitoring system Tabelle Steuerungsrichtung 103 TC230-1 von 3 Type code Info no. Byte 2 Info no. Byte 1 Class Description 7 Start of general query 21 Start of general query for generic data Höher (Ein = höher, Aus = tiefer, nur bei Handbetrieb) Lower (On = lower, Off = no function; only during manual mode) SI command SI command SI command 3 Each of these SI commands sets a corresponding flag in the TAPGUARD 260. The status of the flags can be used like an input of the I/O or UC module to activate or deactivate a TAPGUARD 260 function. Table 9 Data points in control direction Maschinenfabrik Reinhausen /01 EN TAPGUARD

16

17 5 Sequences 5 Sequences 5.1 General query Sample command for general query (GQ): ff 0 0 d5 16 Code (hexadecimal) Definition Start message 7 Type code = 7 (decimal) General query 9 Reason for transmission 0 = not used Function type (or address of information object 1st ff octet) = 255 (decimal) = global function type Info number (or address of information object 2nd octet) = General query initiation 0 d5 16 End message Table 10 Sample command for general query (GQ) After the last data message from the general query cycle, the "GQ complete" message is issued with type code 8 and reason for transmission 10. Maschinenfabrik Reinhausen /01 EN TAPGUARD

18 5 Sequences 5.2 General command Sample command for general query: 68 a a e d 16 Code (hexadecimal) Definition 68 a a Start message 14 Type code = 20 (decimal) = general command 14 Reason for transmission = 20 (decimal) = general command 6e Function type (or address of information object 1st octet) = 110 (decimal) = Private sphere 10 Info number (or address of information object 2nd octet) = 16 (decimal) = Auto/Manual 1 Value = OFF 6d 16 End message Table 11 Example of general command Once it has received a valid command, the Monitoring system returns the command message as positive confirmation. The reason for transmission is set to 20. If the command cannot be performed, the transfer cause is 21. Once it has received a valid command, the Monitoring system returns the command message as positive confirmation. The reason for transmission is set to 8. If the command cannot be performed, the reason for transmission is TAPGUARD /01 EN Maschinenfabrik Reinhausen 2011

19 5 Sequences 5.3 General query, generic data Sample command for general query, generic data: 68 a a fe f5 0 0 d7 16 Code (hexadecimal) Definition 68 a a Start message 15 Type code = 21 (decimal) = General query 9 Reason for transmission = 9 (decimal) = not used fe Function type (or address of information object 1st octet) = 254 (decimal) = generic function type f5 Info number (or address of information object 2nd octet) = 245 (decimal) = General query generic data d7 16 End message Table 12 Example General query, generic data After the last data transfer for the "General query", a message entitled "GQ complete" is transferred with type code 10, info number 245 and reason for transmission 10. After the last data transfer for the "General query", a message entitled "GQ complete" is transferred with type code 10, info number 245 and reason for transmission 10. Maschinenfabrik Reinhausen /01 EN TAPGUARD

20 5 Sequences 5.4 Generic command (write entry with version) Sample command for general query, generic data: a fe fa ca Code (hexadecimal) Definition Start message a Type code = 10 (decimal) = generic data 28 Reason for transmission = 40 (decimal) = generic write command fe Function type (or address of information object 1st octet) = 254 (decimal) = generic function type fa Info number (or address of information object 2nd octet) = 250 (decimal) = Write entry 37 1 GIN LSB = 55 (decimal), GIN MSB = 1; 55 = Desired voltage value 1 7 Data type = 7 = Short real 0 0 ca 42 4 bytes of data End message Table 13 Example of generic command (write entry with version) Once it has received a valid command, the Monitoring system returns the command message as positive confirmation. The reason for transmission is set to 40. If the command cannot be performed, the reason for transmission is 41. The generic command "Write entry with confirmation" (info number 249) is not implemented. Once it has received a valid command, the Monitoring system returns the command message as positive confirmation. The reason for transmission is set to 8. If the command cannot be performed, the reason for transmission is 21.. The generic command "Write entry with confirmation" (info number 249) is not implemented. 20 TAPGUARD /01 EN Maschinenfabrik Reinhausen 2011

21 6 Tap position telegram 6 Tap position telegram 6.1 Structure of telegram The structure of the individual telegrams is described in the tables below. Message type Variable structure code Reason for transmission Shared address of ASDU Function type Information number RII NGD GIN LSB GIN MSB KOD Data type Number of data bytes Quantity 10 0x81 1 or 9 Address set For tap position 54 For tap position message (short real) 4 1 Data (4 bytes, short real) Table 14 Structure of type 10 telegram Maschinenfabrik Reinhausen /01 EN TAPGUARD

22 6 Tap position telegram Message type Variable structure code Reason for transmission Shared address of ASDU Function type Information number Data (4 bytes, short real) Relative time ms (2 bytes) Error number (2 bytes) 4 0x81 1 or 9 Address set 110 For tap position 118 Tap position not used, always 0 not used, always 0 Time (2 bytes) Table 15 Structure of type 4 telegram Message type Variable structure code Reason for transmission Shared address of ASDU Function type Information number 204 0x81 1 or 9 Address set 110 For tap position 54 Tap position Data (4 bytes, short real) Time (4 bytes) SIN (1 byte) Table 16 Structure of type 204 telegram 22 TAPGUARD /01 EN Maschinenfabrik Reinhausen 2011

23 6 Tap position telegram 6.2 Examples of messages for tap position telegrams The examples were taken from various log files which recorded the telegram traffic between a PC and the Monitoring system. The Monitoring system address was set to 1. Some of the tap positions in the sample telegrams selected are different in order to show examples with different values. The same tap position is normally reported in all three telegrams. Telegram Comments ff 0 0 d5 16 General query command from PC 68 a a fe f5 0 0 d7 16 General query command for generic data from PC e f3 9b 82 0 d a fe f d cc e c d e f fd a4 27 8b a a fe f f ad cc e d5 27 8b 0 db 16 Table 17 Type 4 telegram, sent during general query Type 10 telegram, sent during general query Tap position 0 is reported in bytes Type 204 telegram, sent during general query Tap position 0 is reported in bytes Type 4 telegram, end due to a change in tap position Tap position 1 is reported in bytes f Type 10 telegram, sent due to a change in tap position Tap position 1 is reported in bytes f Type 204 telegram, sent due to a change in tap position Tap position 2 is reported in bytes Examples of messages for tap position message telegram Maschinenfabrik Reinhausen /01 EN TAPGUARD

24 /01 EN 03/11 Maschinenfabrik Reinhausen GmbH Falkensteinstrasse Regensburg Phone: Fax: sales@reinhausen.com