Preview only show first 10 pages with watermark. For full document please download

Acp 1703 • Ax 1703 Common Functions - Center

Rating
Date

October 2018
Size

2MB
Views

9,698
Categories

Home Domestic appliances Climate control Temperature & humidity sensors

Transcript

______________________________________________________________________________ Preface, Table of Contents ______________________________________________________________________________ Introduction 1 2 ______________________________________________________________________________ ACP 1703 • Ax 1703 Protocol Description ______________________________________________________________________________ Literature Common Functions ABB RP570/571 MPT-S (Unbalanced Multipoint Slave) Protocol Element DC0-105-2.00 ______________________________________________________________________________ Hint Please observe Notes and Warnings for your own safety in the Preface. Disclaimer of Liability Although we have carefully checked the contents of this publication for conformity with the hardware and software described, we cannot guarantee complete conformity since errors cannot be excluded. The information provided in this manual is checked at regular intervals and any corrections that might become necessary are included in the next releases. Any suggestions for improvement are welcome. Copyright Copyright © Siemens AG 2011 The reproduction, transmission or use of this document or its contents is not permitted without express written authority. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Subject to change without prior notice Document Label: SIC1703-HBGFPREABBGVS-ENG_V2.00 Release date: 12.01.11 Siemens Aktiengesellschaft Bestellnr.: DC0-105-2.00 Preface This document is applicable to the following product: • AK 1703 ACP, TM 1703 ACP, BC 1703 ACP, TM 1703 emic, AK 1703 und AMC 1703 Purpose This manual describes the functioning of the ABB RP570/571 slave protocol and essentially contains: • Functional descriptions Target Group and Safety Instructions The document you are reading right now is addressed to users, who are in charge of the following engineering tasks: • Conceptual activities, as for example design and configuration • Creation of the assembly technical documentation using the designated engineering tools • System parameterization and system diagnostic, using the designated engineering tools • Technical system maintenance Hint The functions which are described in this manual are illustrated with screenshots from TOOLBOX II. These pictures show exemplary the usage of the protocol element in product AK 1703 ACP. Considering the product specific differences – these pictures are also valid for other products. ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Notes on Safety This manual does not constitute a complete catalog of all safety measures required for operating the equipment (module, device) in question because special operating conditions might require additional measures. However, it does contain notes that must be adhered to for your own personal safety and to avoid damage to property. These notes are highlighted with a warning triangle and different keywords indicating different degrees of danger. Danger means that death, serious bodily injury or considerable property damage will occur, if the appropriate precautionary measures are not carried out. Warning means that death, serious bodily injury or considerable property damage can occur, if the appropriate precautionary measures are not carried out. Caution means that minor bodily injury or property damage could occur, if the appropriate precautionary measures are not carried out. Hint is important information about the product, the handling of the product or the respective part of the documentation, to which special attention is to be given. Qualified Personnel Commissioning and operation of the equipment (module, device) described in this manual must be performed by qualified personnel only. As used in the safety notes contained in this manual, qualified personnel are those persons who are authorized to commission, release, ground, and tag devices, systems, and electrical circuits in accordance with safety standards. Use as Prescribed The equipment (device, module) must not be used for any other purposes than those described in the Catalog and the Technical Description. If it is used together with third-party devices and components, these must be recommended or approved by Siemens. Correct and safe operation of the product requires adequate transportation, storage, installation, and mounting as well as appropriate use and maintenance. During operation of electrical equipment, it is unavoidable that certain parts of this equipment will carry dangerous voltages. Severe injury or damage to property can occur if the appropriate measures are not taken: • Before making any connections at all, ground the equipment at the PE terminal. • Hazardous voltages can be present on all switching components connected to the power supply. • Even after the supply voltage has been disconnected, hazardous voltages can still be present in the equipment (capacitor storage). • Equipment with current transformer circuits must not be operated while open. • The limit values indicated in the manual or the operating instructions must not be exceeded; that also applies to testing and commissioning. Consider obligatory the safety rules for the accomplishment of works at electrical plants: 1. Switch off electricity all-pole and on all sides! 2. Ensure that electricity cannot be switched on again! 3. Double check that no electrical current is flowing! 4. Discharge, ground, short circuit! 5. Cover or otherwise isolate components that are still electrically active! 4 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Table of Contents 1 Introduction ........................................................................................................................7 1.1 1.1.1 1.2 2 Application ............................................................................................................8 Availibility of the protocol.................................................................................8 Features and Functions........................................................................................9 Protocol Description........................................................................................................11 2.1 2.1.1 2.2 Overview.............................................................................................................12 Short Description...........................................................................................12 Technical Specifications .....................................................................................13 2.2.1 Limitations .....................................................................................................15 2.2.2 Configuration .................................................................................................15 2.2.3 Transmission Rates.......................................................................................16 2.2.4 Interface Lines Used .....................................................................................16 2.2.5 2.3 2.3.1 2.3.1.1 PCMBA – Modulation Method .......................................................................17 Protocol description ............................................................................................18 Transmission protocol ...................................................................................18 Message formats......................................................................................18 2.3.1.1.1 Message format fixed block length .....................................................19 2.3.1.1.2 Rules for formats with variable block length .......................................21 2.3.2 Length-, Address- and Function Field ...........................................................22 2.3.2.1 Assignment of the Length-(L)-Field..........................................................22 2.3.2.2 Assignment of the Address- (A)-Field ......................................................22 2.3.2.3 Assignment of the F-Field in Command Direction ...................................23 2.3.2.4 Assignment of the F-field in signaling direction – type 1..........................25 2.3.2.5 Assignment of the f-Field in signaling direction - type 2 ..........................27 2.3.2.6 RP571 Router Station Number ................................................................28 2.4 Data Communication Control .............................................................................30 2.5 General Protocol Functions................................................................................32 2.5.1 Process Image ..............................................................................................32 2.5.2 Data Transmission Procedure and Preparation ............................................33 2.5.3 General Interrogation ....................................................................................34 2.5.4 QOC – preadjustment commands.................................................................36 2.5.5 “Terminal Status” – message (TSTA) ...........................................................38 2.5.6 “Terminal-Event” – message (TEV) ..............................................................39 2.5.7 Actival RTU ...................................................................................................39 2.5.8 Conversion of measured values....................................................................40 2.5.8.1 General.....................................................................................................40 2.5.8.2 Value Conversion without Linear Adaptation ...........................................42 2.5.8.3 Value Conversion with Linear Adaptation ................................................43 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 5 Table of Contents 2.6 2.6.1 Data Request Messages .............................................................................. 45 2.6.1.1 Request A (RA) ....................................................................................... 45 2.6.1.2 Request B (RB) ....................................................................................... 45 2.6.1.3 2.6.2 Request X (RX) ....................................................................................... 46 System commands ....................................................................................... 47 2.6.2.1 Status Check Instruction (SCI) ................................................................ 47 2.6.2.2 Function Command (FCOM) ................................................................... 48 2.6.2.3 Reset Sequence Number (RSEQ) .......................................................... 50 2.6.2.4 Time Synchronization Instruction (TSI) ................................................... 51 2.6.2.5 Function Table (FTAB) ............................................................................ 52 2.6.3 Process information...................................................................................... 54 2.6.3.1 „Direct“ commands (Immediate Execute Command) .............................. 54 2.6.3.2 „Select before execute“ commands......................................................... 57 2.6.3.3 Indications in command direction ............................................................ 61 2.6.3.4 Setpoints, measured values in command direction................................. 64 2.7 2.7.1 Message conversion in monitoring direction (SICAM 1703 → RP570/571)...... 69 Response...................................................................................................... 70 2.7.1.1 Cycle Complete Response, Priority Level 1 (CCR1)............................... 70 2.7.1.2 Cycle Complete Response, Priority Level 2 (CCR2)............................... 70 2.7.1.3 Positive acknowledge (ACK) ................................................................... 71 2.7.1.4 Negative acknowledge (NACK)............................................................... 71 2.7.1.5 Executed response (EXR)....................................................................... 72 2.7.1.6 Executed response, RTU restarted (EXRR) ........................................... 72 2.7.1.7 Not Executed Response (NXR)............................................................... 73 2.7.1.8 Check Back Response (CBR) ................................................................. 73 2.7.2 Process information...................................................................................... 74 2.7.2.1 Indications (IDS/IDM, ERMI) ................................................................... 74 2.7.2.2 Measured value analog (AVS/AVM)........................................................ 81 2.7.2.3 Measured values digital (DVM) ............................................................... 86 2.7.2.4 Integrated totals (Puls Counter) .............................................................. 90 2.7.2.5 Fault distance – Measured value ............................................................ 95 2.7.3 6 Message conversion in command direction (RP570/571 SICAM 1703)....... 44 System messages ........................................................................................ 99 2.7.3.1 Terminal Status Message (TSTA) ........................................................... 99 2.7.3.2 Terminal Event Message (TEV) ............................................................ 101 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 1 Introduction Contents 1.1 Application ............................................................................................................8 1.2 Features and Functions........................................................................................9 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 7 Introduction 1.1 Application The ABB RP570/571 slave protocol is used in automation units of the systems AK 1703 ACP, TM 1703 ACP, BC 1703 ACP, TM 1703 emic, AK 1703 and AMC 1703. It is deployed in the field of telecontrol and automation. A protocol element is used for the exchange of data - and thereby for the transmission of rd messages - over a communication interface to other automation units or devices of 3 party manufacturers using ABB RP570/571 protocol. GDK ↓ AMC 1703 (lokale SS) (nur CP-4000) TM1 703 mic ↓ BC 1703 (lokale SS) (only CP-5000,14) SM-2556 ↓ TM 1703 emic SM-2546 (only CP-5000,14) Protocol SM-0551, SM-2551 Availibility of the protocol SM-2545 1.1.1 ↓ ↓ ↓ RP570/571 (Unbalanced Slave) ↓ ↓ System AK 1703 AMC 1703 AK 1703 ACP TM 1703 ACP TM 1703 mic TM 1703 emic BC 1703 ACP Legend: .........available 8 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Introduction 1.2 Features and Functions General Functions • Unbalanced multi-point slave according to RP570/571 specification in "leased line" mode. RP5UA1 is remote station (secondary station) • Data acquisition by polling • General interrogation, interrogation of integrated totals (counter values) • spontaneous transmission of commands and set points in command direction • spontaneous transmission of indications, measured values and integrated totals (counter values) in monitoring direction • multi-hierarchical configurations possible (RP571 – Mode) • time synchronization over communication line The operating mode of the interface is determined by parameters and optional equipment (refer System Element Manual) Hint The above mentioned functions are described in detail in the chapter protocol description. This protocol element for interfacing 3rd party systems supports only restricted functionality and only a sub set of the possible data formats. For using this protocol element in your project you have to verify if the supported functionality and supported data formats of the protocol element will be compatible to the required functionality and data formats for interfacing a specific 3rd party system. ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 9 Introduction 10 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 2 Protocol Description Contents 2.1 Overview.............................................................................................................12 2.2 Technical Specifications .....................................................................................13 2.3 Protocol description ............................................................................................18 2.4 Data Communication Control .............................................................................30 2.5 General Protocol Functions................................................................................32 2.6 Message conversion in command direction (RP570/571 SICAM 1703) .......44 2.7 Message conversion in monitoring direction (SICAM 1703 → RP570/571) ......69 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 11 Protocol Description 2.1 Overview 2.1.1 Short Description The protocol element is used for interfacing of AK 1703, ACP 1703 and AMC 1703 to telecontrol centers, front-ends and control systems by using the ABB RP570/571 protocol in the multi-point traffic. The protocol element emulates one RP570/571 slave in the dedicated line operation. Hint As non-SICAM system adaptation, this protocol element implements only part of the functionality and the data formats of the third-party interface. For a concrete application case therefore, it should be verified to what extent the actual requirements correspond with the functionali. 12 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.2 Technical Specifications rd The Firmware is designed for the communication of SICAM 1703 system components and 3 party systems with the RP570/571 protocol, whereby SICAM 1703 emulates the functionality of one slave (= one RTU) Transmission rate 50 110 150 200 300 600 1200 1800 2000 2400 4800 9600 Modulation PCM Byte asynchronous Transmission method Half-duplex Character frame • • • • 1 Start bit 8 Data bit 1 Parity bit (even) 1 Stop bit Character representation see DIN 66022 Bit transmit sequence LSB (least significant bit) is transmitted first Message protection • HA = 4 Message structure DIN19244 (issue January 1986) with modifications ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 13 Protocol Description Message formats in monitoring direction (=SICAM 1703 transmit direction) • INDICATION MESSAGE (IDM) • INDICATION MESSAGE WITH STATUS (IDS) • ANALOG VALUE MESSAGE (AVM) • ANALOG VALUE MESSAGE WITH STATUS (AVS) • DIGITAL VALUE MESSAGE (DVM) • EVENT RECORDING MESSAGE FOR INDICATION (ERMI) • EVENT RECORDING MESSAGE FAULT DISTANCE (ERMFD) • PULSE COUNTER MESSAGE (PCM) • PULSE COUNTER TELEGRAM (PCT) • TERMINAL STATUS (TSTA) • TERMINAL EVENT (TEV) • CYCLE COMPLETE RESPONSE PRIORITY LEVEL 1 (CCR 1) • CYCLE COMPLETE RESPONSE PRIORITY LEVEL 2 (CCR 2) • POSITIV ACKNOWLEDGE (ACK) • EXECUTED RESPONSE (EXR) • EXECUTED RESPONSE, RESTARTED (EXRR) • NOT EXECUTED RESPONSE (NXR) • CHECK BACK RESPONSE (CBR) Message formats in command direction (=SICAM 1703 receive direction) • REQUEST B (RB) • REQUEST X (RX) • STATUS CHECK INSTRUCTION (SCI) • RESET SEQUENCE NUMMER (RSEQ) • FUNCTION COMMAND #1, #2, #3, #13 (FCOM) • FUNCTION TABLE #0, #10 (FTAB) • IMMEDIATE EXECUTED COMMAND (IXC) • CHECK BACK BEFORE EXECUTE COMMAND (CBXC) • INHIBIT COMMAND (IHC) • EXECUTE COMMAND (EXC) • SET POINT MESSAGE (SPM) • GENERAL OUTPUT MESSAGE (GOM) QOC-Voreinstellbefehl (projektspezifisch) 14 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.2.1 Limitations • Spontaneous information is not chained. • CCRX-identifier in the function field is not supported. • Ax redundancy not supported. • ADLP-180 is not supported. • Load share operation not possible. • “RA” is always responded with “CCR1”; information is never reported. • “FTAB” – messages are not evaluated – but they are confirmed (EXR). • Operation mode with “main line” and “backup line” is not supported. • Negative acknowledge (NACK) is not supported. • Only a subset of “function Commands” is supported. Hint As adaptation to 3rd party system, this protocol element implements only a part of the functionality and the data formats of the non-SICAM interface. For a concrete case of application it is therefore to be checked, how far the real requirements correspond with the functionality implemented here and to what extent additional expansions or adaptations are necessary. 2.2.2 Configuration ABB Master Computer RP570/RP571 SICAM 1703 SICAM 1703 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 SICAM 1703 15 Protocol Description 2.2.3 Transmission Rates The following baud rates are provided and can be selected by means of configuration parameters: 50 1200 2.2.4 110 1800 150 2000 200 2400 300 4800 600 9600 Interface Lines Used The following V.24 interface lines are used: CCITT USA Line Designation V.24 16 Direction Rem. 102 GND Signal Ground Signal Ground 103 TD Transmit Data Transmit Data → DCE 104 RD Receive Data Receive Data ← DCE 105 RTS Switch on transmitter Request to send → DCE 106 CTS Clear to send Clear to send ← DCE 109 DCD Receive signal level Data carrier detect ← DCE 107 DSR Data Set Ready Data Set Ready ← DCE ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.2.5 PCMBA – Modulation Method The data are pulse code modulated in groups each of 8 bits and transmitted asynchronous. A UART-module in the asynchronous mode thereby provides each byte with a byte frame (BF). This byte frame contains: 1 Start bit 8 Data bits 1 Parity bit (even parity) 1 Stop bit The synchronization of the receiver takes place afresh with each byte by means of the Startand Stop bits of the byte frame. A FB 8 BIT INFORMATION B C FB D LSB D1 E MSB D2 D3 D4 D5 D6 D7 D8 T A: B: C: D: E: T: FB: Idle state of the line (binary information "1") between two messages at least 33 bit (in case of error) Start bit ("0") 8 bit data (possibly frame data or message data), LSB (Least Significant Bit) is transmitted first Parity bit (even parity) 1 Stop bit ("1") Time for the transmission of a bit (1/transmission rate) Framing bits of the USART module ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 17 Protocol Description 2.3 Protocol description 2.3.1 Transmission protocol Each message basically consists of two parts • • a protocol-dependent part (message frame) a protocol-independent part (message data) The message structure is based on the DIN-standard 19244 (transmission protocol for the format class F 1.2), issue January 1986. The transmission protocol prescribes the rules for the message structure and the transmission procedure. The telecontrol message is so structured, that on the one hand the assignment to the ISO-layers, see DIN ISO 7498, Connection, Network and Transport, can be recognized as well as the higher levels on the other. Basic message format: Header for communication unit (KE) (Connection-, Network- and Transport layer) Header for process unit (PE) (Higher levels) Information part End part for communication unit (KE) 2.3.1.1 Message formats The message formats and rules are based on the standard: Telecontrol Equipment and Systems Part 5: Transmission Protocols Format Class FT 1.2. There are formats defined for fixed and variable message lengths as well as single characters. The formats are distinguished, amongst other things, by different start characters. 18 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.3.1.1.1 Message format fixed block length a) Block length <> 0 For RP570/571 the format has a fixed block length of 5 bytes and consists of a start character, 2 user bytes, a check byte and a stop byte. Bit sequence on the line Data bits (D) 1 Start character 0 User data Byte No. 0 and No. 1 Checksum 0 0 Stop character 0 2 3 4 5 6 7 8 9 10 11 USART character D1 D2 D3 D4 D5 D6 D7 D8 0 0 1 1 A-field P 1 F-field P 1 P 1 1 1 0 0 0 0 1 0 0 CS 0 1 1 0 1 0 0 0 = 10H = 16H Stop bit Info byte Start bit Parity bit (even Parity) Remark: D1 basically represents the least significant bit (LSB). Representation of a byte (LSB shown right-aligned): D8 27 D1 26 25 24 23 22 21 20 Following RP5707571 messages use the “message format with fixed block length”: RP570: RA, RB, SCI, RSEQ, CCR1, CCR2, EXR, EXRR, NXR RP571: RA, RB, SCI, RSEQ, CCR1, CCR2, ACK b) Single character (block length = 0) This message format is not used on RP570/571protocol! Transmission rules for formats with fixed block length 1. Idle state on the line represents 1-Signal. 2. Each UART-character consists of start bit (0), 8 info bits, parity bit (even) and stop bit (1). 3. No idle states are allowed between the UART-characters of a format block (i.e. no idle bits). This is necessary (according to DIN) due to the required hamming distance = 4. 4. In case of a loss of synchronization, a minimum number of 33 bits idle becomes necessary between the formats (blocks) Note: If switching on the carrier (in the master station) causes faulty characters in the RTU, the setup time must be set greater than 33 bits. ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 19 Protocol Description 5. The user data bytes are monitored by the checksum. The checksum is the arithmetical sum, without consideration of the values carried over, over all user data bytes (without Start and Stop). 6. The receiver checks: • • per UART-character: Start bit, Stop bit and Parity bit (even). per Format: Start character, Checksum and Stop character If one of these checks leads to a negatives result, then the entire message is to be discarded. The further procedure is as described for loss of synchronization under Point 4, i.e. the message is not acknowledged (by the RTU) and must be repeated. With a positive check result the information is forwarded. 20 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.3.1.1.2 Rules for formats with variable block length The format consists of an initial start character, two similar characters in which the number L of the user data is transmitted, a second start character, the checksum and the stop character. The number L of user data bytes lies within the range 0 ... 255. Bit sequence on the line Data bits Start character Start character Checksum Stop character 1 0 0 0 0 0 0 2 3 4 5 6 7 8 9 10 D1 D2 D3 D4 D5 D6 D7 D8 0 0 0 1 0 1 1 0 1 L P L repeated P 0 0 0 1 0 1 1 0 1 A-field P F-field P 0 0 0 1 Start bit CS 1 0 1 11 USART character 1 = 68H 1 1 1 1 1 1 2 3 4 1 2 . . . L Header with fixed length User data bytes P 1 0 0 0 1 1 = 16H Byte Stop bit Parity bit (even Parity) Transmission rules for formats with variable block length The rules and regulations 1 ... 5 listed under "Formats with fixed block length" are also applicable here. 6. The receiver checks: • • per UART-character: per Format (TG): Start bit, Stop bit and Parity bit (even) - the defined start character at the beginning and after the two L-bytes - the identity of the two length bytes L - whether the number of characters received (Byte) is the same as L + 6. - the checksum - the stop character If one of these checks leads to a negatives result, then the entire message is to be discarded. The further procedure is as described for loss of synchronization under Point 4 "Formats with fixed block length", i.e. the message is not acknowledged (by the RTU) and must be repeated. With a positive check result the information is forwarded and the message is acknowledged to the transmitting station. ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 21 Protocol Description 2.3.2 Length-, Address- and Function Field 2.3.2.1 Assignment of the Length-(L)-Field The length field defines the number of user data bytes, see "Record Formats Used". Values between (0) and 255 are possible. D8 27 2.3.2.2 D1 26 25 24 23 22 21 20 L-Field Assignment of the Address- (A)-Field The address field defines the RP570 station address. Values between 0 and 255 are possible. Address field equals 0 means, that the message from the master station is transmitted to all remote terminal units. In this case the message must not be acknowledged or responded by any RTU. D8 27 D1 26 25 24 23 22 21 20 A-Field Remark concerning the identification of the participant: On a line, each station must know which messages are directed to it and from where they originate. One makes use of the fact, that messages cannot be exchanged between any two stations, but rather only between the master and a slave. It is therefore sufficient to state in all messages of the slave concerned, whether it is now transmitter or receiver. 22 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.3.2.3 Assignment of the F-Field in Command Direction D8 D1 SFK M/D Function RB F-Field in command direction Meaning of the fields in the F-Field in command direction: RB = 1 Function M/D SFK Direction bit of the information (= 1 command direction) Message type Message acknowledgement 0 = Monolog Mode (no acknowledgement) 1 = Dialog Mode (with acknowledgement) Record sequence identifier A message in Monolog Mode (M/D = 0) must not be acknowledged by the remote terminal unit (e.g. commands "to all"). A message in Dialog Mode (M/D = 1) must be acknowledged by the remote terminal unit. There are message formats that may be transmitted in Monolog- and Dialog Mode, as well as messages that may only be transmitted in Dialog Mode. The following table lists the message formats implemented and their transmission mode in command direction. Function code Message Format Mnemonic M D 0 REQUEST A Request for data of Priority 1 RA X 8 REQUEST B Request for data of Priority 1, 2 or 3 RB X 4 REQUEST X Request of a certain variable (test) RX X 15 STATUS CHECK INSTRUCTION General interrogation SCI X X 7 RESET SEQUENCE NUMBER Resetting of the record sequence identifier RSEQ X X 6 FUNCTION COMMAND System-internal commands FCOM X X 5 CHECK BACK BEFORE EXECUTE COMMAND Selection command pulse command Type-1 CBXC X 13 EXECUTE COMMAND Execution pulse command Type-1 EXC X 3 INHIBIT COMMAND Inhibit pulse command Type-1 IHC X X 9 IMMEDIATE EXECUTED COMMAND Pulse command Type 1/Type 2 IXC X X 1 SET POINT MESSAGE Setpoint command, setpoint value SPM X X 11 GENERAL OUTPUT MESSAGE Setpoint value, binary information GOM X X 12 TIME SYNC INSTRUCTION TSI X X ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 23 Protocol Description Record sequence identifier (SFK) The record sequence identifier (SFK) protects the communication against information loss and -duplication. With the SFK in the request control code of the F-field in command direction, a retransmission of the last message can be achieved in case of information loss. The record sequence identifier is handled by the master station (Master) for each RTU. Handling of “SFK” in the master station If no valid answer is received with a specified timeout the sent message is repeated with the same sequence number again. This is repeated until the “maximum number of retransmissions” is reached. After that the RTU is marked as “faulty”, the only message sent to a faulty RTU is “SCI” until it answers correctly again. Handling of “SFK” in the secondary station (RTU) The secondary station (slave, RTU) interprets a record sequence identifier increased by 1 compared with the previous request as positive acknowledgement for the information it has transmitted. Otherwise, with this mechanism a repeat of the last three sequence numbers can be requested from the master station. The RTU always stores the “function-byte” (F-field) of the last correct received message in “dialog mode” with the sequence numbers 0, 1, 2 and 3 and the whole corresponding answer which the RTU has sent. sequence number = 0 received function byte sent answer sequence number = 1 received function byte sent answer sequence number = 2 received function byte sent answer sequence number = 3 received function byte sent answer If the RTU receives a message in dialog mode with an unexpected sequence number (expected is: (last received + 1) modulo 4) it checks the received function-byte with stored. If they match, it retransmits the stored answer again without performing the command again. If they do not match, the RTU keeps quiet; the received message is discarded. Note: The messages “SCI” and “RSEQ” initializes the sequence number (to “0”, next expected is “1”). Further the stored “function byte” and “sent answer” are erased. (as described before) 24 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.3.2.4 Assignment of the F-field in signaling direction – type 1 D8 AZ D1 Function Ü PRI RB Meaning of the fields in the F-field in signaling direction Type 1: RB = 0 PRI Ü AZ Function Direction bit of the information (= 0 monitoring direction) Priority 0 = Priority 1 1 = Priority 2, 3 Transmission 0 = without status 1 = with status Interrogation cycle 0 = Cycle not completed 1 = Cycle completed Message type ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 25 Protocol Description The following table lists the message formats implemented, that are transmitted with the Ffield Type 1. Message Format ANALOG VALUE MESSAGE Measured values ANALOG VALUE MESSAGE WITH STATUS Measured values (with status) INDICATION MESSAGE WITH STATUS Binary information (with status) with CCRx F-Field P1 no yes 00101000 10000000 P2, P3 no yes 00101010 10000010 P1 no yes 00101100 10000100 P2, P3 no yes 00101110 10000110 P1 no yes 00110000 10001000 P2, P3 no yes 00110010 10001010 P1 no yes 00110100 10001100 P2, P3 no yes 00110110 10001110 P1 no yes 00111000 10010000 P2, P3 no yes 00111010 10010010 P1 no yes 00111100 10010100 P2, P3 no yes 00111110 10010110 P1 no yes 01001110 10011100 P2, P3 no yes 01010000 10011110 ERMI P2, P3 no 01010110 ERMFD P2, P3 no 01000000 AVS IDS DVM DIGITAL VALUE MESSAGE Digital value PCM PULSE COUNTER MESSAGE Count message PULSE COUNTER TELEGRAMM Count message EVENT RECORDING MESSAGE FOR INDICATION Binary information with time tag EVENT RECORDING MESSAGE FOR FAULT DISTANCE measured value from protection unit-fault distance 26 Priority AVM IDM INDICATION MESSAGE Binary information Note: Mnemonic PCT The message types, listed above, are only support without CCRx (CCRx-no). CCRx indicates that further information is available for this priority level (P1 or P2/P3). ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.3.2.5 Assignment of the f-Field in signaling direction - type 2 D8 D1 Free Function RB Meaning of the fields in the F-field in signaling direction Type 2: RB = 0..............Direction bit of the information (= 0 monitoring direction) Function ...........Message type The following table lists the message formats implemented, that are transmitted with the Ffield Type 2. Message Format Mnemonic F-Field CYCLE COMPLETE RESPONSE PRIORITY LEVEL 1 Cycle Priority 1 complete CCR1 00000000 CYCLE COMPLETE RESPONSE PRIORITY LEVEL 2 Cycle Priority 2 complete CCR2 00000010 EXECUTED RESPONSE, RESTARTED Positive acknowledgement; first acknowledgement after POWER/UP EXRR 00000100 EXECUTED RESPONSE Positive acknowledgement to various messages EXR 00000110 NOT EXECUTED RESPONSE Negative acknowledgement to various messages NXR 00001000 TERMINAL STATUS Station status TSTA 00001010 TERMINAL EVENT MESSAGE Station information TEV 00001110 POSITIV ACKNOWLEDGE Positive acknowledgement ACK 00011010 NEGATIV ACKNOWLEDGE Negative acknowledgement NACK 00011110 1) 1) currently not supported ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 27 Protocol Description 2.3.2.6 RP571 Router Station Number In order to handle multi-hierarchical configurations (= RTU with subordinate RTU’s) the protocol type “RP571” is used. The “RTU-No” is now replaced by a dual address scheme: - Router-RTU-No. and - Process-RTU-No. The Router-RTU communicates directly with the master station. The “Process-RTU-No.” is used for addressing of information (destination address in command direction, source address in monitoring direction). If Router-RTU-No. = Process-RTU-No. information is directed to the Router-RTU or the information is from the Router-RTU (originator). D7 0 D0 1 START CHARACTER 1 0 1 0 0 0 0 0 LENGTH LENGTH 0 1 START CHARACTER 1 0 1 0 ROUTER RTU NO FCODE CMD PROCESS RTU NO Nutzdaten CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 1 0 If no further subordinate RTU’s are connected to a RTU, then Process-RTU-No = Router-RTU-No. 28 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Sub-RTU-Handling Masterstation RP571 RTU# = 10 RTU# = 20 Router-RTU (= SICAM 1703) RTU 1) 1) RTU RTU RTU# = 11 RTU# = 12 Router-RTU = Prozess-RTU Command to Router-RTU (Process-RTU-No = 10): Master Station RB 10 Router RTU IXC 10 CCR 2 RB10 EXR CCR2 Command to Process-RTU# 11: Master Station Router RTU RB 10 IXC 11 CCR 2 RB10 ACK ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 RB 10 EXR CCR 2 29 Protocol Description 2.4 Data Communication Control General The remote terminal units are requested cyclically by the master station (polling-procedure). The polling-procedure is based on transmitting information on event from the RTU, but each request must be responded by the RTU, expected the request is directed to all RTU’s. (broadcast) Within the polling cycle user data messages (commands, setpoint values,…) can be inserted in the command direction. In monitoring direction the data are subdivided into 3 priority levels, Priority 1, 2 and 3, whereby Priority 1 is regarded as the highest priority level. The master station uses two different requests to collect information of different priority levels from the RTU: Request A (RA): information of priority 1, TSTA, TEV Request B (RB): information of priority 1, 2, 3, TSTA, TEV Attention: Request A is always respond with „CCR1“ (no information available) Typical message sequences: Polling procedure: Master RA Slave RB RB CCR 1 IDM CCR2 Command to RTU: Master RB Slave IXC RB CCR 2 EXR RB CCR2 IDM Restart of RTU: Master Slave RB RB SCI CCR 2 SCI RB EXRR RB TSTA TEV RTU Restart 30 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description If the master station detects the failure of a RTU, then this station is always requested with “SCI” (-status check instruction) Note: The firmware accepts only “SCI” and “RSEQ” after restart or after establishing communication. All other messages are discarded. After the master station has received a certain “Terminal Event” – message it can start a “parameter download” – procedure, which is performed with “FTAB” – messages. During the parameter downloading the RTU must no transmit any information (neither spontaneous nor because of the received “SCI” before). The parameter download is concluded with the function command “Activate RTU”. (= FCOM2) After the reception of “FCOM2” the RTU enables transmission of information. Note: messages in command direction (i.e. commands, setpoints) are converted correctly and executed during “parameter download”, if the master station would send this messages. ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 31 Protocol Description 2.5 General Protocol Functions 2.5.1 Process Image The firmware manages a process image (= data base), in order to • Monitor indications and measured values for change, and • Transmit indications and measured values directly from the image in case of „status check instruction“ (general interrogation). The process image is structured to RP570/RP571 – block number (1 block-no = 1 measured value or 16 binary information). The process image contains beside the state “invalid”identifier (= status). SICAM 1703 information objects contain the following data point quality identifiers: • • • • NT-Bit (not topical) IV-Bit (invalid) BL-Bit (blocked – descriptor only for “bouncing” signal) OV-Bit (Overflow – only for measured values) In the RP570/571 - protocol there is only one "IV"-identifier (= invalid). IV (RP570/571) = NT v IV v OV Counter values are not recorded in the process image. After a firmware restart, the process image is initialized with the state = 0 and “invalid”, as well as the startup delay started (= parameter-settable). The startup delay serves to update the process image. During this time, no communication takes place to the master (receiver is disabled). Changes in process state that occur are not stored. 32 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.5.2 Data Transmission Procedure and Preparation The RP570/571 protocol uses two different requests (Request A, Request B) to collect information of different priority levels (P1, P2, P3): Request A (RA): - information of priority 1 (=P1) - one “Terminal Status” – message - one “Terminal Event” – message Request B (RB): - all information As the priority control of all information takes places on the basic system element (= BSE) and the firmware has no influence to the priority control, a received “Request A” is always confirmed with “CCR1” (no information available). The protocol element (PRE) may only send events to the master if it has received a corresponding call (request). If the PRE is allowed to transmit data to the master, then it requests data from the BSE ("give me data"). The BSE now decides based on the priority control, which data are sent to the PRE. If the PRE receives an SICAM 1703 message, then • • • • a change comparison is performed the process image is updated if a change is detected a RP570/571 message is generated, the parameterized priority is added and sent to the master station. Chaining of spontaneous events is not done (only one block-no. in one message) if no change is detected, then a further chaining operation (give me data) is initiated, unless the parameterized number of chaining operations has also been reached. If the number of chaining operations has been reached a “CCR2” – message is sent to the master station. ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 33 Protocol Description 2.5.3 General Interrogation The master station causes with the “status check instruction” (SCI) the remote terminal unit to transmit the current process state. If the “SCI” is forwarded to the remote terminal, then the general interrogation is answered directly from the process image of the firmware. The firmware however also sends a GI-request (= Image-GI) to the BSE, in order to keep the process image guaranteed synchronous between BSE and firmware. The “GI-data” sent by the BSE are only forwarded to the master on change (status or state). GA-Daten SCI GA-Anweisung GA-Beh. GA-Daten PA B PRE BSE FIFO GA-Anf. PA B CASDU of the internal GI-request During startup the firmware generates an assignment between CASDU and RP570-ProcessRTU-No. If up to 2 CASDU’s are assigned to one RP570-Process-RTU-No, then the internal GI-request (Ti = 100) is always executed “selectively”, otherwise the GI-request is always addressed broadcast. Every received GI-request is always converted to th SICAM 1703 system message “General Interrogation Request”. Processing The “status check instruction” (SCI) is always directed to a Process-RTU-No. The firmware transmits the information of the Process-RTU, requested in the “SCI”-message. Exception: 34 - After restart or after recept of “FCOM2” the whole data base is transmitted. - RP571: After recept of “SCI” directed to the Router-RTU, the transmission of the whole data base can be enabled. (Parameter: “SCI to Router RTU”) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Transmission of information after “status check instruction” ─ Information is transmitted after a “status check instruction” to a certain Process-RTU as follows: ─ Terminal-Status (TSTA) ─ Terminal-Event (TEV) ─ Information of priority 1 ─ Information of priority 2 ─ Information of priority 3 ─ The order of “TSTA”- and “TEV”-messages is determined by the parameters “priorityTSTA-message” and “priority-TEV-message” ─ “TSTA”- and “TEV”-messages to be transmitted must be parameterized Parameter: “System messages (TSTA, TEV) after SCI” ─ Information are transmitted in increasing order of “process-RTU-No” and “block-no” Indications and analog measured values are always transmitted in the message format with status (IDS and AVS) Order of data types: ─ Indications (IDS) ─ Analog measured values (AVS) ─ Digital measured values (DVM) ─ The message length at general interrogation is configurable (blocked transmission of indications and analog measured values) ─ SCI to Router-RTU transmission of information of all RTU’s ─ Terminal-Status (Router-RTU) ─ Terminal-Event (Router-RTU) ─ Terminal-Status (Process-RTU-No = x) ─ Terminal-Event (Process-RTU-No = x) ─ Terminal-Status (Process-RTU-No = y) ─ Terminal-Event (Process-RTU-No = y) ─ Information of priority 1 ─ Information of priority 2 ─ Information of priority 3 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 35 Protocol Description 2.5.4 QOC – preadjustment commands The “Quality of Command” (Command output duration) to be added on received commands can be preadjusted by “preadjustment commands”. This function was implemented for a special project (RWE) There exists two different “QOC-preadjustment commands”: • preadjustment commands - PSG • preadjustment commands – interlocking The “QOC-preadjustment commands” are identified by the parameterized “RP570-QOC”: • preadjustment PSG commands (RWE) • preadjustment interlocking commands (RWE) All commands which should to be added on with the preadjusted QOC must be defined in the SIP address message conversion with “RP570-QOC = QOC acc. preadjustment (RWE)” Add on QOC: Circuit breaker : CTYPE=0 disconnector: CTYPE=4 Interlocking PSG QOC ON ON 0 Interlocking ON QOC 10 OFF ON 9 OFF 11 ON OFF 10 OFF OFF 11 Attention: The QOC- preadjustment commands (PSG and interlocking) must be defined only once. 36 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description The state of both QOC- preadjustment commands can be confirmed with “double point information” to the master station. For this purpose two double point information must be defined in the SIP address message conversion as follows: Note: • ERMI_(time tag): always “no” • RP570 – indication type: possible: - QOC-RI PSG - QOC-RI interlocking ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 37 Protocol Description 2.5.5 “Terminal Status” – message (TSTA) “Terminal Status” messages are system information of the RTU itself which are transmitted spontaneous (on event) or at “status check instruction”. The firmware handles 8 TSTA-messages for each Process-RTU-No. These messages are initialized after restart as follows: RP570-message reference Ident-Nr. Bit 15-12 Bit 11-8 Bit 7-4 Bit 3-0 message 0 1 1000 0001 0000 0000 message 1 2 0000 0000 0000 0000 message 2 3 0000 0000 0000 0010 message 3 1 1000 0011 0000 0010 message 4 2 0000 0000 0000 0000 message 5 3 0000 0000 0000 0000 message 6 4 0000 0000 0000 0000 message 7 15 0000 0000 0000 0000 Ident = 1, Bit-No = 8 … „RTU is active“ Ident = 1, Bit-No = 9 … „RTU is synchronized“ These indications are handled automatically by the firmware itself (only for the “own RTU-No”) These 8 predefined “TSTA”-messages can be changed or updated with single point information (TI = 30) of the SIP address message conversion (also the Ident-No itself, see chap. 4.7.3.1) The “RP570-messgae reference” is used for access between data base and SIP address message conversion. The transmission of “TSTA”-messages must be enabled in the system technical parameterization: Parameter: 38 - system messages (TSTA, TEV) after SCI - system messages (TSTA, TEV) after FCOM 13 (chapter: advanced parameters / RP570/571 specific settings) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.5.6 “Terminal-Event” – message (TEV) “Terminal-Event” – messages are system internal events of the RTU itself (i.e. RTU restarted), which are only transmitted on event. Several master stations need “TEV”-messages of the RTU for correct operation, other master stations do not need any “TEV” messages. The firmware handles 8 TEV-messages for each Process-RTU-No. These messages are initialized after restart as follows: RP570- message reference Event-Nr. INFO 1 INFO 2 INFO 3 INFO 4 INFO 5 INFO 6 message 0 23 0 0 0 0 0 0 message 1 24 0 0 0 0 0 0 message 2 25 0 0 0 0 0 0 message 3 1 0 0 0 0 0 0 message 4 1 0 0 0 0 0 0 message 5 1 0 0 0 0 0 0 message 6 1 0 0 0 0 0 0 message 7 1 0 0 0 0 0 0 These 8 predefined “TEV”-messages can be changed or updated with “bit string 32 bit” (TI = 33) of the SIP address message conversion (also the Event-No itself, see chap. 4.7.3.2) The “RP570- message reference” is used for access between data base and SIP address message conversion. The transmission of “TEV”-messages must be enabled in the system technical parameterization: Parameter: 2.5.7 - system messages (TSTA, TEV) after SCI - system messages (TSTA, TEV) after FCOM 13 (chapter: advanced parameters / RP570/571 specific settings) Actival RTU Several master stations do not expect process information after restart of the RTU. The master station only accepts process information after it has activated the RTU, by using the “function command No. 2”. This behavior must be configured in the firmware with the parameter “Enable of user data” (general settings/protocol enabling) • Enable of user data: - immediately after start up - wait for FCOM-No 2 Wait for FCOM-No. 2 After restart of the firmware (and start up delay has been expired) all parameterized „TSTA“and „TEV“-messages are transmitted. (System messages after SCI). Then the firmware is waiting for “FUNCTION COMMAND-NO 2” (=“Activate RTU”). After the firmware has received “Activate RTU” the transmission of information is enabled. (Terminal status: RTU is active). Further, after reception of an “Activate RTU” (to the own RP570-RTU-No) the transmission of the whole data base is initiated. ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 39 Protocol Description 2.5.8 Conversion of measured values 2.5.8.1 General RP570/571-protocol uses two different message formats for measured values: • analog measured values (AVM/AVS) range: -2048 … 0 … +2047 full-scale (100%): 2000 • digital measured values (DVM) The coding of digital measured values is determined in the SIP-address message conversion: - 16 bit bipolar range: -32768 .. 0 .. 32767 full-Scale (100%): 32000 - 16 bit BCD This coding is only valid for step position information (TI = 32). range: 0 - 9999 - 16 bit transparent This coding is only valid for „bit string 32 bit“ (TI = 33). range: 0 – 65535 The following type identifications can be converted to RP570/571 measured values: • • • • • Step position information (TI = 32) Bit string 32 bit (TI = 33) Measured value– normalized (TI = 34) Measured value – scaled (TI = 35) Measured value – short float (TI = 36) The data point quality identifier "NT" (not topical), "IV" (invalid) and "OV" (Overflow) are converted to “status = invalid/faulty” 40 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description A linear adaptation can be parameterized for each measured value (only TI = 34, 35, 36). The linear adaptation is defined through the following parameters: X_0% Value adaptation: Lower limit of the used measuring range in the external (protocol-specific) format. The corresponding internal value is defined at Y_0%. X_100% Value adaptation: Upper limit of the used measuring range in the external (protocol-specific) format. The corresponding internal value is defined at Y_100%. Y_0% Value adaptation: Lower limit of the used measuring range in the selected internal format. The internal format is defined at TI (type identification). The corresponding external value is defined at X_0%. Y_100% Value adaptation: Upper limit of the used measuring range in the selected internal format. The internal format is defined at TI (type identification). The corresponding external value is defined at X_100%. As only two measured value formats are defined in the RP570/571 protocol, the parameters X_0% and X_100% are defined in the range: analog measured value (AVS/AVM): - 2048 … + 2047 digital measured value (AVS/AVM): - 32768 … + 32767 Also valid: Y_100% > Y_0% The parameters Y_0% and Y_100% are defined by the internal type identification. Measured value - normalized: Measured value - scaled: Measured value - short floating point: -1…+1 - 32768 … + 32767 no check The linear adaptation is activated, if Y_0% or Y_100% is parameterized unequal to "0". ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 41 Protocol Description 2.5.8.2 Value Conversion without Linear Adaptation • Step position information (TI = 32) ─ Value range: - 64 … + 63 Value RP570 = Value SICAM 1703 • Measured value - normalized (TI = 34) ─ Value range: - 1 … + 1 Value RP570 = Value SICAM 1703 * full scale • Measured value – scaled (TI = 35) ─ Value range: - 32768 … + 32767 Value RP570 = Value SICAM 1703 • Measured value – short float (TI = 36) 38 ─ Value range: - 3.4.10 38 … + 3.4.10 Value RP570 = Value SICAM 1703 If the measured value to be converted (=Value RP570) is not in the valid range of the RP570/571-format or the measured value is already marked as “overflow” (OV = 1) the RP570/571 measured value is set to its positive maximum value (+ 2047, + 32767) or negative maximum value (- 2047, - 32767) and “status = invalid” (=0x07) 42 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.5.8.3 Value Conversion with Linear Adaptation The adaptation is activated, if "Y_0%" or "Y_100%" are parameterized to unequal "0". Value RP570 = k * Value SICAM 1703 + d whereby k = (X100 – X0) / (Y100 – Y0) d = X0 – k * Y0 Attention: Value SICAM 1703 < Y0 Value SICAM 1703 > Y100 → Value RP570 = X0 and Status = invalid → Value RP570 = X100 and Status = invalid Example: Bipolar measured values Value RP570 X100 Y0 Y100 Value Sicam1703 X0 Status = Invalid X0, X100 Value RP570 (e.g.: X0 = -2000, X100 = +2000) Y0, Y100 Value SICAM 1703 (e.g.: normalized, Y0 = - 1, Y100 = 1) For unipolare measured values, "X0" and "Y0" must be parameterized to "0". ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 43 Protocol Description 2.6 Message conversion in command direction (RP570/571 SICAM 1703) Supported message formats: ABB RP570/571 Func. code Message SICAM 1703 Message Designation Message Designation Data Request Messages: 0 RA REQUEST A _ 8 RB REQUEST B _ 4 RX REQUEST X Request of a certain block number AVS, IDS, DVM supported. System commands: 15 SCI 7 RSEQ RESET SEQUENCE NUMBER 6 FCOM FUNCTION COMMAND 12 TSI 2 FTAB STATUS CHECK INSTRUCTION general interrogation (from data base) _ #1 #2 #3 #13 restart RTU activate RTU counter interrogation message set RTU in/out of service TIME SYNC INSTRUCTION time synchronization FUNCTION TABLE indications analog measured values #0 #10 Process information: 44 9 IXC IMMEDIATE EXECUTED COMMAND Single command TI = 45 (execute) Double command TI = 46 (execute) Regulating step command TI = 47 (execute) 5 CBXC CHECK BACK BEFORE EXECUTE COMMAND Single command TI = 45 (select) Double command TI = 46 (select) Regulating step command TI = 47 (select) 3 IHC INHIBIT COMMAND Single command TI = 45 (cancel) Double command TI = 46 (cancel) Regulating step command TI = 47 (cancel) 13 EXC EXECUTE COMMAND Single command TI = 45 (execute) Double command TI = 46 (execute) Regulating step command TI = 47 (execute) 1 SPM SET POINT MESSAGE Measured value 15 Bit + VZ normalized TI = 34 Measured value 15 Bit + VZ scaled TI = 35 Measured value short floating point TI = 36 Setpoint command normalized TI = 48 Setpoint command scaled TI = 49 Setpoint command short floating point TI = 50 11 GOM GENERAL OUTPUT MESSAGE Measured value 15 Bit + VZ normalized TI = 34 Measured value 15 Bit + VZ scaled TI = 35 Measured value short floating point TI = 36 Setpoint command normalized TI = 48 Setpoint command scaled TI = 49 Setpoint command short floating point TI = 50 Single command TI = 30 Double command TI = 31 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.6.1 2.6.1.1 Data Request Messages Request A (RA) RP570/571-message format D7 0 0 RP 570 START CHARACTER 0 1 0 0 0 RTU NO D0 RP 571 0 ROUTER RTU NO SEQ.NO X X 0 0 M/D 1 FCODE 0 0 0 CHECK SUM STOP CHARACTER 1 0 1 0 0 CMD 1 1 0 The master station uses the service “Request A” for requesting of information of priority level 1 from the RTU. If no information is available the RTU responds with “CCR1”. Attention: The firmware responses “Request A” always with “CCR1”. 2.6.1.2 Request B (RB) RP570/571- message format D7 0 0 RP 570 START CHARACTER 0 1 0 0 0 RTU NO D0 RP 571 0 ROUTER RTU NO SEQ.NO X X 0 0 M/D 1 FCODE 1 0 0 CHECK SUM STOP CHARACTER 1 0 1 0 0 CMD 1 1 0 The master station uses the service “Request B” for requesting of information of priority levels (= 1, 2, 3) and all events from the RTU. If no information is available the RTU responds with “CCR2”. ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 45 Protocol Description 2.6.1.3 Request X (RX) The service “Request x” allows the master station to request a certain information object from the RTU – specified by data type and block number. RP570/571- message format D7 0 1 0 0 0 0 0 1 SEQ.NO X X RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 0 1 LENGTH 0 0 0 1 START CHARACTER 1 0 1 0 RTU NO M/D 1 0 SPARE FCODE 1 0 D0 RP 571 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0 0 1 0 1 0 0 ROUTER RTU NO CMD 0 1 DTYPE PROCESS RTU NO BLOCK NUMBER CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 1 0 DTYPE: 0 0 0 = Indications 0 0 1 = Pulse Counter Values, not supported 0 1 0 = Analog Values 0 1 1 = Digital Values 1 0 0 = SUB-RTU polling status , not supported 1 0 1 = SUB-RTU polling acknowledgement , not supported BLOCK NUMBER: Block number of the request point. If the requested information object does not exist in the data base or “DTYPE” is not supported, the firmware responds with “NXR” (not execute response). If the requested information object exists in the data base, the firmware responds with the corresponding message format (with parameterized priority level; indications and analog measured values always with “status”). 46 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.6.2 2.6.2.1 System commands Status Check Instruction (SCI) The service “Status Check Instruction” (= general interrogation) always uses the master station to update its data base. If the “SCI” is directed to the “own RP570-RTU-No” it can be defined, if only information of the request RTU-NO. or of all RTU-No (only in RP571-mode) should be transmitted. RP570/571-message format D7 0 RP 570/571 START CHARACTER 0 0 1 0 0 0 RTU NO / ROUTER RTU NO SEQ.NO X X 0 0 M/D X FCODE 1 1 1 CHECK SUM STOP CHARACTER 0 1 0 1 1 1 D0 0 CMD 1 D7 0 1 0 0 0 0 0 1 RP 571 START CHARACTER 1 0 1 0 LENGTH 0 0 0 0 LENGTH 0 0 0 0 START CHARACTER 1 0 1 0 ROUTER RTU NO D0 0 0 1 1 1 1 0 0 1 CMD 1 1 0 0 SEQ.NO X X M/D FCODE 1 1 1 X PROCESS RTU NO CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 Response: - „EXR“ resp. „EXRR“ - „NXR“: SCI to an unknown process-RTU-No. (only at RP571-mode) Attention: „EXRR“ is only responded if the „SCI“ was received in the message format with fixed block length. ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 47 Protocol Description 2.6.2.2 Function Command (FCOM) “Function Commands” are RP570/571-specific system commands; only a subset of the defined “FCOM”-messages is supported. Not supported “FCOM”-messages are responded with “NXR”. RP570/571-message format D7 0 1 0 0 0 0 0 1 RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 1 0 LENGTH 0 0 1 0 START CHARACTER 1 0 1 0 RTU NO SEQ.NO M/D X X X FCODE 0 1 1 FCOM NO D0 RP 571 0 0 1 1 0 0 0 0 1 1 0 0 1 1 0 0 0 0 1 1 0 0 0 0 0 CMD 1 1 0 ROUTER RTU NO PROCESS RTU NO SATELLITE LINE SATELLITE RTU NO INFO 1 INFO 2 INFO 3 INFO 4 INFO 5 INFO 6 CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 FCOM NO SATELLITE LINE SATELLITE RTU NO INFO1 – INFO6 48 Function Command Number Satellite Line number: not evaluated Satellite RTU number: not evaluated additional information of FCOM ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Supported FCOM-messages: Designation FCOMNo. Additional information Cold Start 1 Activate RTU 2 Reading of puls counters 3 INFO1 = 1: intermediate (= transmit) INFO1 = 2: end of period (= freeze + transmit) Subordinate RTU in/out of Service 13 INFO1 = 1: In service INFO1 = 2: Out of service Cold Start (FCOM-No = 1) • Perform a restart of the automation unit Restart is only performed if the “FCOM”-message is addressed to the “own RP570-RTUNo” or “broadcast”. • If the “FCOM”-message is not addresses to the “own RP570-RTU-No” (only in RP571 mode) the firmware responds with “NXR”. Activate RTU (FCOM-No = 2) “Activate RTU” is used to activate the RTU after concluding parameter download of original ABB-RTU’s. The firmware does not evaluate the parameter messages (FTAB), but in some cases this behavior must be evaluated. (see chap. 4.5.7 – Activate RTU) Response: always “EXR” Reading of puls counters (FCOM-No = 3) • INFO1 = 1: • INFO1 = 2: transmit (FRZ=0) • Conversion: SICAM 1703 internal counter request message, broadcast address (CASDU=FF, FF), request counter group parameterizeable (group 1-4, all groups) • • intermediate reading = read, transmit (FRZ=0) end of period reading = freeze(FRZ=1) + read, Response: always “EXR” Process-RTU-No. is not evaluated in RP571-mode. Subordinate RTU in/out of Service (FCOM-No = 13) “FCOM = 13” – commands are only responded by the firmware; however no further actions are performed. The transmission of “Terminal-Status” – messages (TSTA) and “TerminalEvent” – messages (TEV) can be performed. System technical parameterization: “system messages (TSTA, TEV) after FCOM 13” Response: - “EXR” - “NXR” (unknown Process-RTU-No at RP571-mode) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 49 Protocol Description 2.6.2.3 Reset Sequence Number (RSEQ) RP570/571-message format D7 0 0 RP 570 START CHARACTER 0 1 0 0 0 RTU NO D0 RP 571 0 ROUTER RTU NO SEQ.NO X X 0 0 M/D 1 FCODE 0 1 1 CHECK SUM STOP CHARACTER 1 0 1 0 1 CMD 1 1 0 The RTU initializes the sequence number (to “0”) und confirms the last sent message negatively (only AU internal). 50 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.6.2.4 Time Synchronization Instruction (TSI) RP570/571-message format D7 0 1 0 0 0 0 0 1 SEQ.NO X X MSB RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 1 0 LENGTH 0 0 1 0 START CHARACTER 1 0 1 0 RTU NO M/D X 1 D0 FCODE 1 0 0 0 0 0 0 0 0 0 0 CMD 1 0 DATE LSB MSB TIME LSB CHECK SUM 0 DATE TIME 0 STOP CHARACTER 0 1 0 1 1 0 day since 1.1.1980 (= 1. day) time since 0 intervals of 0,1 ms The firmware corrects the received time by the transmission delay of the message. Response: always “EXR” ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 51 Protocol Description 2.6.2.5 Function Table (FTAB) “Function table” – messages are used for parameter download of the RTU. The firmware does not evaluate this message but responds it with “EXR”. For “blocking” of indications and analog measured values it is necessary to evaluate certain FTAB-messages. FTAB TYPE 0 0 0 0 0 BLOCK NO 0 0 0 BOARD TYPE ADDRESS 1 ADDRESS 2 ADDRESS 3 ADDRESS 4 SPARE PRI MSB START CH FOR BLOCK LSB MSB BLOCKED LSB 1) MSB INDICATION TYPE LSB MSB SUPPRESS MOM MIDPOS LSB MSB SEQ EVENT REC 01 LSB MSB SEQ EVENT REC 10 LSB FILTER TIME MSB TRANSM. TO CS LSB CONN TYPE 1) „Blocked” - information; 1 (2) bits for each indication within the block number; 0 = normal, 1 (11) = blocked Only „BLOCK NO“ and „BLOCKED“ is evaluated. 52 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Parameter – analog measured value (FTAB-Type = 10; 13 Byte Parameter) 0 0 0 FTAB TYPE 0 1 BLOCK NO 0 1 0 BOARD TYPE ADDRESS CHANNEL WITHIN BOARD BACKGR. CYCLE CONV. CATEGORY CONV. PARAM CS LPB FREQ LP SER BLK ADB DBU PRI SCAN CYCLE FILTER FACTOR MSB DEADBAND LSB CONN TYPE Only „BLOCK NO“ and the bit „BLK“ is evaluated. BLK = 0 … normal BLK = 1 … blocked Response of FTAB-Type = 0 and 10 • EXR: Block-No exists in data base • NXR: Block-No and/or Process-RTU-No does not exists in data base Response of all other FTAB-Types • EXR: Process-RTU-No exists in data base • NXR: Process-RTU-No exists in data base ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 53 Protocol Description 2.6.3 2.6.3.1 Process information „Direct“ commands (Immediate Execute Command) RP570/571-message format D7 0 1 0 0 0 0 0 1 RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 0 1 LENGTH 0 0 0 1 START CHARACTER 1 0 1 0 RTU NO SEQ.NO M/D X X X 1 STO CTYPE FCODE 0 0 MSB OBJECT NUMBER D0 RP 571 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0 0 1 0 1 0 0 ROUTER RTU NO 1 CMD 1 PROCESS RTU NO LSB ON/ OFF CHECK SUM STOP CHARACTER 0 0 0 1 OBJEKT NUMBER CTYPE STO ON/OFF 0 1 1 0 object number of command 0 = object command with short time 1 = regulating command with long time 2 = not used 3 = not used 4 = object command with long time 5 = not used 6 = not used 7 = not used 1 = stop running regulating command (valid only for CTYPE = 1) not evaluated 0 = OFF 1 = ON Response: • • EXR: command address (process-RTU-No and object-No) is defined in SIP address message conversion and command address is not selected on a Back before Execute command”. “Check NXR: - command address is not defined in SIP address message conversion - Process-RTU-No unknown . - CTYPE not supported Spontaneous forwarding 54 • cause of transmission = activation (=6) • command state (SCS, DCS) = ON/OFF from received message • quality of command (QOC) = parameterizeable • Select/Execute (S/E) = always „0“ (= execute) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Address conversion RP570/571 SICAM 1703 The address conversion is parameterized with the OPM (object-orientated process data manager). For this, in the SIP message address conversion the detailed routing type firmware / Rec_binary_information is provided with the following entries. RP570-Address: RP570-Process-RTU-No: possible: 1-255 RP570-Format: possible: commands RP570-Object-No: possible: 0-2047 RP570-QOC: Command output duration to be added on possible: - Command output time from messages (CTYPE) - Pulse command with short output time - Pulse command with long output time - Pulse command without output time - QOC acc to preadjustment (RWE) - Preadjustment interlocking command (RWE) - Preadjustment PSG command (RWE) DPI_DC-Inverting: Inverting of double point information, double command or regulating step command possible: - no - yes ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 55 Protocol Description SICAM 1703-Address: CASDU1 CASDU2 IOA1 IOA2 IOA3 TI: 56 5-stage freely parameterized SICAM 1703 address possible: 0 - 255 Type identification: possible: single command (TI = 45) double command (TI = 46) regulating step command (TI = 47) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.6.3.2 „Select before execute“ commands For „select before execute“ commands 3 message formats are used: • check back before execute command (CBXC; FCode = 5) • execute command (EXC; FCode = 13) • inhibit command (IHC; FCode = 3) The message formats “check back before execute command” and “inhibit command” do not include the command state (ON/OFF), therefore these messages must be handled by the firmware specially. RP570/571-message format D7 0 1 0 0 0 0 0 1 RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 0 1 LENGTH 0 0 0 1 START CHARACTER 1 0 1 0 RTU NO RP 571 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0 0 1 0 1 0 0 ROUTER RTU NO SEQ.NO X X SPA RE M/D FCODE 1 MSB CTYPE 0 0 0 OBJECT NUMBER D0 CMD 1 PROCESS RTU NO LSB ON/ OFF CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 OBJECT NUMBER CTYPE ON/OFF 1 0 object number of command 0 = object number with short time 4 = object number with long time only at „Execute Command“ 0 = OFF 1 = ON The “select” – command (CBXC) can not be forwarded immediately to the automation unit (= AU = SICAM 1703) because CBXC does not contain the command state. Therefore the firmware stores the command address (RP570-Process-RTU-No and block number) and is waiting for the “execute” – command (timeout = 10 sec). If the “execute” – command is received within timeout and the command address (of execute) is equal to the “select” – command, then the “select” – command is forwarded with the command state of the “execute” – command to the automation unit; after a parameterizeable delay the “execute” – command is forwarded. Note: Up to 5 “select before execute” – command can be handled simultaneously. ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 57 Protocol Description Spontaneous forwarding: • cause of transmission = activation (=6) • command state (SCS, DCS) = ON/OFF from received message • quality of command (QOC) = parameterizeable • select/execute (S/E) = “1” … select command = “0” -… execute command” Block diagram (OK-case) RP570-Master RP570-Protocol Firmware Select-command CB Check Back Response XC CBR t1 Execute-command Command (select) Command (select) (S/E = 1, COT = 6) (S/E = 1, COT = 6) EX C EX Execute-Response R t2 Command (execute) (S/E = 0, COT = 6) t1 = Timeout CBXC/EXR = 10 sec (fix) t2 = Delay Select/Execute – Command (parameterizeable) Response of CBXC • • CBR: Command address (RP570-Process-RTU-No und block number) is defined in SIP-address message conversion and command is not selected till now. NXR: - Command address unknown - Process-RTU-No unknown (protocol type = RP571) - Command is already selected Response of EXC and IHC 58 • EXR: • NXR: - Command address unknown - Command address is not selected (timeout already expired) - RP570-Process-RTU-No unknown (protocol type = RP571) - CTYPE not supported - Command address is equal to the address of CBXC ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Address conversion RP570/571 SICAM 1703 The address conversion is parameterized with the OPM (object-orientated process data manager). For this, in the SIP message address conversion the detailed routing type firmware / Rec_binary_information is provided with the following entries. RP570-Address: RP570-Process-RTU-No: possible: 1-255 RP570-Format: possible: commands RP570-Object-No: possible: 0-2047 RP570-QOC: Command output duration to be added on possible: - Command output time from messages (CTYPE) - Pulse command with short output time - Pulse command with long output time - Pulse command without output time - QOC acc to preadjustment (RWE) - Preadjustment interlocking command (RWE) - Preadjustment PSG command (RWE) DPI_DC_Inverting: Inverting of double point information, double command or regulating step command possible: - no - yes ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 59 Protocol Description SICAM 1703-Address: CASDU1 CASDU2 IOA1 IOA2 IOA3 TI: 60 5-stage freely parameterized SICAM 1703 address possible: 0 - 255 Type identification: possible: single command (TI = 45) double command (TI = 46) regulating step command (TI = 47) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.6.3.3 Indications in command direction GENERAL OUTPUT MESSAGE (GOM) RP570/571-message format D7 0 1 0 0 0 0 0 1 SEQ.NO X X RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 0 1 LENGTH 0 0 0 1 START CHARACTER 1 0 1 0 RTU NO M/D X FCODE 1 0 1 OBJECT NO D0 RP 571 0 0 0 1 0 0 0 0 0 1 1 0 0 1 0 0 0 0 0 1 1 0 0 0 ROUTER RTU NO 1 CMD 1 PROCESS RTU NO MSB DATA LSB CHECK SUM STOP CHARACTER 0 0 0 1 0 OBJEKT NO 1 1 0 object number D7 D0 x x x x x x x x x x x x x x IND Ind: State of Indication Spontaneous forwarding: • Cause of transmission = spontaneous (=3) • State of single point information = “LSB” of “Ind” • State of double point information = “Ind” ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 61 Protocol Description Address conversion RP570/571 SICAM 1703 The address conversion is parameterized with the OPM (object-orientated process data manager). For this, in the SIP message address conversion the detailed routing type firmware / Rec_binary_information is provided with the following entries. RP570-Address: RP570-Process-RTU-No: possible: 1-255 RP570-Format: possible: GOM RP570-Object-No: possible: 0-255 RP570-QOC: Command output duration to be added on possible: not used DPI_DC_Inverting: 62 Inverting of double point information, double command or regulating step command possible: - no - yes ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description SICAM 1703-Address: CASDU1 CASDU2 IOA1 IOA2 IOA3 TI: 5-stage freely parameterized SICAM 1703 address possible: 0 - 255 Type identification: possible: single point information (TI = 30) double point information (TI = 31) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 63 Protocol Description 2.6.3.4 Setpoints, measured values in command direction For transmission of stetpoints or measured values (in command direction) two different RP570-message formats are used: • Setpoint message SPM (FCode = 1) • General output message GOM (FCode = 11) Both message formats allows the transmission of analog values (12 bit bipolar) or digital values (16 bit bipolar). RP570/571-message format D7 0 1 0 0 0 0 0 1 SEQ.NO X X RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 0 1 LENGTH 0 0 0 1 START CHARACTER 1 0 1 0 RTU NO M/D X D0 RP 571 0 0 0 1 0 0 0 0 0 1 1 0 0 1 0 0 0 0 0 1 1 0 0 0 ROUTER RTU NO FCODE CMD 1 PROCESS RTU NO OBJECT NO MSB DATA LSB CHECK SUM STOP CHARACTER 0 0 0 OBJECT NO 64 1 0 1 1 0 Object number ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Setpoint coding: analog (12 bit bipolar) D7 S D0 S S S MSB VALUE LSB Coding happens in 12 bit “2’-complement”, sign “s” is extended to 16 bit. Setpoint coding: digital (16 bit bipolar) D7 S D0 MSB VALUE LSB Coding happens in 16 bit “2’-complement”. Response: • EXR: - RP570-Address (process-RTU-No and block number) in SIP-address message conversion defined and conversion of value ok • NXR: - RP570-process-RTU-No unknown - RP570-Address unknown (protocol type = RP571) - Conversion of value not possible (i.e. setpoint to large) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 65 Protocol Description Address conversion RP570/571 SICAM 1703 The address conversion is parameterized with the OPM (object-orientated process data manager). For this, in the SIP message address conversion the detailed routing type firmware / Rec_value is provided with the following entries. RP570-Address: RP570-Process-RTU-No: possible: 1-255 RP570-Format: possible: - SPM - GOM RP570-Object-No: possible: 0-255 RP570-Setpoint-coding: possible: - 12 bit bipolar (analog) - 16 bit bipolar (digital) SICAM 1703-Address: CASDU1 CASDU2 IOA1 IOA2 IOA3 TI: 66 5-stage freely parameterized SICAM 1703 address possible: 0 - 255 Type identification: possible: Setpoint value 15 bit + sign normalized (TI = 48) Setpoint value 15 bit + sign scaled (TI = 49) Setpoint value short floating point (TI = 50) measured value 15 bit + sign normalized (TI = 34) measured value 15 bit + sign scaled (TI = 35) measured value short floating point (TI = 36) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description X_0% Value adaptation: Lower limit of the used measuring range in the external (protocol-specific) format. The corresponding internal value is defined at Y_0%. possible: - 32768 … + 32767 (16 Bit bipolar) - 2048 … + 2047 (12 Bit bipolar) X_100% Value adaptation: Upper limit of the used measuring range in the external (protocol-specific) format. The corresponding internal value is defined at Y_100%. possible: - 32768 … + 32767 (16 Bit bipolar) - 2048 … + 2047 (12 Bit bipolar) Y_0% Value adaptation: Lower limit of the used measuring range in the selected internal format. The internal format is defined at TI (type identification). The corresponding external value is defined at X_0%. possible: TI 34, 48: - 1 … + 1 TI 35, 49: - 32768 … + 32767 TI 36, 50: no check Y_100% Value adaptation: Upper limit of the used measuring range in the selected internal format. The internal format is defined at TI (type identification). The corresponding external value is defined at X_100%. possible: TI 34, 48: - 1 … + 1 TI 35, 49: - 32768 … + 32767 TI 36, 50: no check ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 67 Protocol Description Value conversion: The conversion of the received setpoints resp. measured values can be done with or without linear adaption. Conversion without linear adaption: • X_0 = 0 and X_100 = 0 • TI = 34, 48: 12 bit analog 2000 = 100% 16 bit digital 32000 = 100% Conversion with linear adaption: 68 • X_0 <> 0 or X_100 <> 0 • X_0 < X_100 • X_0 ≤ received value ≤ X_100 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.7 Message conversion in monitoring direction (SICAM 1703 → RP570/571) Supported message formats: SICAM 1703 Designation ABB RP570/571 Fkt.-Code Message Designation Responses (kink layer): 0 CCR1 CYCLE COMPLETE RESPONSE PRIORITY LEVEL 1 1 CCR 2 CYCLE COMPLETE RESPONSE PRIORITY LEVEL 2 13 ACK POSITIVE ACKNOWLEDGE 15 NACK NEGATIVE ACKNOWLEDGE 3 EXR 2 EXRR 4 NXR NOT EXECUTED RESPONSE 10 CBR CHECK BACK RESPONSE 13 ACK POSITIVE ACKNOWLEDGE 15 NACK NEGATIVE ACKNOWLEDGE 3 EXR 2 EXRR 4 NXR NOT EXECUTED RESPONSE 10 CBR CHECK BACK RESPONSE 24,25 IDM INDICATION MESSAGE/ 26,27 IDS INDICATION MESSAGE with STATUS 32 ERMI 24,25 IDM INDICATION MESSAGE/ 26,27 IDS INDICATION MESSAGE with STATUS 32 ERMI EVENT RECORDING Message for Indication Measured value 15 Bit + VZ normalized 20,21 AVM ANALOG VALUE MESSAGE/ TI = 34 22,23 AVS ANALOG VALUE MESSAGE with STATUS 28, 29 DVM DIGITAL VALUE MESSAGE Measured value 15 Bit + VZ scaled 20,21 AVM ANALOG VALUE MESSAGE/ TI = 35 22,23 AVS ANALOG VALUE MESSAGE with STATUS 28, 29 DVM DIGITAL VALUE MESSAGE Measured value short floating point 20,21 AVM ANALOG VALUE MESSAGE/ TI = 36 22,23 AVS ANALOG VALUE MESSAGE with STATUS 28, 29 DVM DIGITAL VALUE MESSAGE Set position information TI = 32 28,29 DVM DIGITAL VALUE MESSAGE Integrated total 31 Bit + VZ TI = 37 30, 31 PCM PULSE COUNTER MESSAGE 39, 40 PCT PULSE COUNTER TELELGRAM 43 ERMFD EVENT RECORDING MESSAGE EXECUTED RESPONSE EXECUTED RESPONSE RESTARTED EXECUTED RESPONSE EXECUTED RESPONSE RESTARTED Process information: Single point information TI = 30 Double point information TI = 31 Measured value short floating point TI = 36 EVENT RECORDING Message for Indication FAULT DISTANCE System messages: Single point information TI = 30 5 TSTA Bit string 32 Bit TI = 33 7 TEV TERMINAL STATUS TERMINAL EVENT MESSAGE ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 69 Protocol Description 2.7.1 2.7.1.1 Response Cycle Complete Response, Priority Level 1 (CCR1) RP570/571-message format D7 0 0 RP 570 START CHARACTER 0 1 0 0 0 RTU NO D0 RP 571 0 ROUTER RTU NO 0 0 0 0 FCODE 0 0 0 0 CHECK SUM STOP CHARACTER 0 1 0 1 0 CMD 0 1 0 This message is always sent to the master station when a “request A” is received (see chap. 4.5.2) 2.7.1.2 Cycle Complete Response, Priority Level 2 (CCR2) RP570/571-message format D7 0 0 RP 570 START CHARACTER 0 1 0 0 0 RTU NO D0 RP 571 0 ROUTER RTU NO 0 0 0 0 FCODE 0 0 0 0 CHECK SUM STOP CHARACTER 0 1 0 1 1 CMD 0 1 0 This message is sent to the master station when a “request B” is received and no information (i.e. measured values, indications) is available to be transmitted. 70 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.7.1.3 Positive acknowledge (ACK) RP570/571-message format D7 D0 RP 571 START CHARACTER 0 1 0 0 0 RTU NO 0 0 0 0 0 0 0 STOP CHARACTER 0 1 0 1 FCODE 1 1 0 CHECK SUM 0 1 CMD 0 1 0 This message serves as a positive response to a message sent by the master station (in command,…) if it is not directed to the Router-RTU but to a subordinate RTU in the RP571mode. 2.7.1.4 Negative acknowledge (NACK) RP570/571-message format D7 0 1 0 0 0 0 0 1 0 0 RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 0 1 LENGTH 0 0 0 1 START CHARACTER 1 0 1 0 ROUTER RTU NO FCODE 0 1 1 1 PROCESS RTU NO D0 0 0 0 0 0 0 0 0 1 CMD 0 1 0 STATUS CODE CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 Note: This message is not supported currently by the firmware. ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 71 Protocol Description 2.7.1.5 Executed response (EXR) RP570/571-message format D7 0 0 0 0 0 0 RP 570 START CHARACTER 0 1 0 0 RTU NO FCODE 0 0 0 CHECK SUM 1 STOP CHARACTER 0 1 0 1 D0 0 0 1 CMD 0 1 D7 0 1 0 0 0 0 0 1 0 0 0 RP 571 START CHARACTER 1 0 1 0 LENGTH 0 0 0 0 LENGTH 0 0 0 0 START CHARACTER 1 0 1 0 ROUTER RTU NO FCODE 0 0 0 1 PROCESS RTU NO D0 0 0 1 1 1 1 0 0 1 CMD 0 1 0 CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 This message serves as a positive response to a message sent by the master station. (i.e. command, setpoint value, …) to the RTU. 2.7.1.6 Executed response, RTU restarted (EXRR) RP570/571-message format D7 0 0 0 0 0 0 RP 570 START CHARACTER 0 1 0 0 RTU NO FCODE 0 0 0 CHECK SUM 1 STOP CHARACTER 0 1 0 1 D0 0 0 0 CMD 0 1 D7 0 1 0 0 0 0 0 1 0 0 0 RP 571 START CHARACTER 1 0 1 0 LENGTH 0 0 0 0 LENGTH 0 0 0 0 START CHARACTER 1 0 1 0 ROUTER RTU NO FCODE 0 0 0 1 PROCESS RTU NO D0 0 0 1 1 1 1 0 0 0 CMD 0 1 0 CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 This message serves as a positive response to the “status check instruction” (SCI) in “RP570-format” on start up of the RTU. 72 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.7.1.7 Not Executed Response (NXR) RP570/571-message format D7 0 0 0 0 0 0 RP 570 START CHARACTER 0 1 0 0 RTU NO FCODE 0 0 1 CHECK SUM 0 STOP CHARACTER 0 1 0 1 D0 0 0 0 CMD 0 1 D7 0 1 0 0 0 0 0 1 0 0 RP 571 START CHARACTER 1 0 1 0 LENGTH 0 0 0 0 LENGTH 0 0 0 0 START CHARACTER 1 0 1 0 ROUTER RTU NO 0 FCODE 0 1 0 0 PROCESS RTU NO D0 0 0 1 1 1 1 0 0 0 CMD 0 1 0 CHECK SUM STOP CHARACTER 0 0 0 1 0 1 This message serves as a negative response to a message sent by the master station (i.e. command, setpoint, …) to the RTU. 2.7.1.8 Check Back Response (CBR) RP570/571-message format D7 0 1 0 0 0 0 0 1 0 SPA RE RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 0 1 LENGTH 0 0 0 1 START CHARACTER 1 0 1 0 RTU NO FCODE 0 1 0 MSB CTYPE 0 0 0 OBJECT NUMBER 0 1 D0 RP 571 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0 0 1 0 1 0 0 ROUTER RTU NO 0 CMD 0 PROCESS RTU NO LSB SPA RE CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 1 0 OBJECT NO object number of the received command CTYPE 0 = object command ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 73 Protocol Description This message serves as the positive response to the “check back before execute command” (CBXC) sent by the master station of the RTU. 2.7.2 2.7.2.1 Process information Indications (IDS/IDM, ERMI) Indication message without status (IDM) RP570/571-message format D7 0 1 X X X X 0 1 D0 RP 570 START CHARACTER 1 0 1 0 LENGTH X X X X LENGTH X X x X START CHARACTER 1 0 1 0 RTU NO RP 571 0 0 X X X X X X X X X X+1 X X X X X X X X X X+1 0 0 ROUTER RTU NO FCODE CMD 0 PROCESS RTU NO BLOCK NO 1. SUB-ENTRY MSB VALUE LSB BLOCK NO N’TH SUB-ENTRY MSB VALUE LSB CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 FCODE: 1) 0 D7 D6 D5 D4 D3 D2 D1 Priority with CCR 0 0 1 1 0 0 0 1 no 0 0 1 1 0 0 1 2, 3 no 1 0 0 0 1 0 0 1 yes 1 0 0 0 1 0 1 2, 3 yes 1) 1) not supported BLOCK NO VALUE 74 1 block number 16 bit information ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Indication message with status (IDS) RP570/571-message format RP 570 START CHARACTER 1 0 1 0 LENGTH X X X X LENGTH X X x X START CHARACTER 1 0 1 0 RTU NO D7 0 1 X X X X 0 1 RP 571 D0 0 0 X X X X X X X X X X+1 X X X X X X X X X X+1 0 0 ROUTER RTU NO FCODE CMD 0 PROCESS RTU NO BLOCK NO 1. SUB-ENTRY MSB STATUS LSB MSB VALUE LSB BLOCK NO N’TH SUB-ENTRY MSB STATUS LSB MSB VALUE LSB CHECK SUM STOP CHARACTER 0 0 FCODE: 1) 0 1 0 1 1 0 D7 D6 D5 D4 D3 D2 D1 Priority with CCR 0 0 1 1 0 1 0 1 no 0 0 1 1 0 1 1 2, 3 no 1 0 0 0 1 1 0 1 yes 1 0 0 0 1 1 1 2, 3 yes 1) 1) not supported BLOCK NO STATUS VALUE block number status flags of information 1 (11 for double point information) = invalid 16 bit information ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 75 Protocol Description Conversion IDS/IDM • The maximum message length is configurable; therefore the number of blocks of indications is limited. Attention: This parameter is only active for transmission caused by „status check instruction“, if spontaneous transmission (event) happens, the message contains only one block of indications. • Double point information: the bit position of a double point information within a block number is always an even number (0, 2, 4, …14). The even bit number (0, 2, 4, …14) represents the “ON” – state (in normal case). The representation can be inverted by a parameter (selective for each double point information). • Message format with status (IDS) The use of the format “indication message with status” (IDS) can be determined by a parameter: - at status check instruction (SCI), status change - at status check instruction (SCI), status < > 0 (= block number is invalid) • 76 Invalid-Bit IV (RP570) = NT (SICAM 1703) v IV (SICAM 1703) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Event recording message for indications (ERMI) RP570/571-message format D7 0 1 0 0 0 0 0 1 0 1 RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 1 0 LENGTH 0 0 1 0 START CHARACTER 1 0 1 0 RTU NO 0 FCODE 0 0 BLOCK NO 0 D0 RP 571 0 0 1 1 0 0 0 0 1 1 0 0 1 1 0 0 0 0 1 1 0 0 0 0 ROUTER RTU NO CMD 0 0 PROCESS RTU NO SEQUENCE NO BIT NO SPARE SPA TYP RE T QUALITY VAL NS OF DAY OF MONTH MSB TIME LSB CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 1 0 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 77 Protocol Description BLOCK NO SEQUENZ NO block number sequence number The sequence number (0 – 255) is incremented for each event recording message ERMxx. The first value is transmitted with 0; then, the sequence number is incremented from 255 to 1. VAL single point information: 01 = ON 10 = OFF double point information: 01 = ON 10 = OFF 00 = intermediate position 11 = faulty position TYP 0 = single point information 1 = double point information BIT NO bit number within the binary information block OF 1 = FIFO overflow not supported by the; always 0 NS 1 = clock of RTU is not synchronized if time of the indication (TI = 30, 31) is marked as “invalid” T QUALITY time quality 000 time is valid 001 ms and lower is not valid 010 ms x 10 and lower is not valid 011 ms x 100 and lower is not valid 100 second and lower is not valid 101 second x 10 and lower is not valid is set if an error occurs on conversion to RP570-time format DAY OF MONTH day of current month TIME time since midnight in intervals of 0,1 ms Note: „Indication with time tag“ (ERMI) is always transmitted additionally to „indication without time tag“ (IDS/IDM), if transmission of ERMI is enabled. Parameter = ERMI-(time tag) A transmission occurs only on event (state has been changed) and the indication itself is valid. (NT = 0 and IV = 0) 78 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Address conversion SICAM 1703 RP570/571 The address conversion is parameterized with the OPM (object-orientated process data manager). For this, in the SIP message address conversion the detailed routing type firmware / Trans_binary_information is provided with the following entries. SICAM 1703-Address: CASDU1 CASDU2 IOA1 IOA2 IOA3 5-stage freely parameterized SICAM 1703 address possible: 0 - 255 TI: Type identification: possible: single point information (TI = 30) double point information (TI = 31) RP570-Address: RP570-Prozess-RTU-No: possible: 1-255 RP570-Format: possible: IDSP570-Block-No: possible: 0-255 RP570-Bit-No: bit position within the block number possible: - single point information: 0 - 15 - double point information: 0, 2, 4, … 14 RP570-Priority: possible: ERMI-(time tag): Enabling of transmission with time tag (additional to IDS/IDM) possible: - no - yes DM-Inverting: Possibility to invert the state of double point information; but only „ON“ and „OFF“ is inverted. possible: - no ON: Bit-No. = 0, 2, 4, … 14 OFF: Bit-No. = 1, 3, 5, … 15 - yes ON: Bit-No. = 1, 3, 5, … 15 OFF: Bit-No. = 0, 2, 4, … 14 Definition of type of indication is used for special function „QOC-predjustment“ – return indication. possible: - process indication - QOC – RI PSG - QOC – RI interlocking RP570-Indication type: - Priority 1 - Priority 2 - Priority 3 Attention: - all indications of a block number must have the same priority. ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 79 Protocol Description 80 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.7.2.2 Measured value analog (AVS/AVM) Analog value message without status (AVM) RP570/571-message format D7 0 1 X X X X 0 1 RP 570 START CHARACTER 1 0 1 0 LENGTH X X X X LENGTH X X x X START CHARACTER 1 0 1 0 RTU NO 0 0 X X X X X X X X X X+1 X X X X X X X X X X+1 0 0 ROUTER RTU NO FCODE 0 0 0 0 0 0 0 0 BLOCK NO 1 0 1 MSB 0 VALUE 20 0 NCB 0 1 CMD 0 BLOCK NO 0 1 0 MSB 1 VALUE 10 NCB 0 MSB RP 571 D0 1 PROCESS RTU NO 0 LSB 0 0 LSB VALUE 21 LSB MSB LSB VALUE 22 MSB VALUE 23 SPARE LSB CHECK SUM 0 0 FCODE: 1) STOP CHARACTER 0 1 0 1 1 0 D7 D6 D5 D4 D3 D2 D1 Priority with CCR 0 0 1 0 1 0 0 1 no 0 0 1 0 1 0 1 2, 3 no 1 0 0 0 0 0 0 1 yes 1 0 0 0 0 0 1 2, 3 yes 1) 1) not supported BLOCK NO VALUE NCB block number of the 1. measured value measured value in 12 bit 2’ complement number of consecutive block numbers ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 81 Protocol Description Analog value message with status (AVS) RP570/571-message format D7 0 1 X X X X 0 1 D0 RP 570 START CHARACTER 1 0 1 0 LENGTH X X X X LENGTH X X x X START CHARACTER 1 0 1 0 RTU NO RP 571 0 0 X X X X X X X X X X+1 X X X X X X X X X X+1 0 0 ROUTER RTU NO FCODE CMD 0 PROCESS RTU NO BLOCK NO 1. SUB-ENTRY SPARE STATUS LIM SPA CHK RE MSB VALUE LSB BLOCK NO N’TH SUB-ENTRY SPARE STATUS LIM SPA CHK RE MSB VALUE LSB CHECK SUM STOP CHARACTER 0 0 FCODE: 1) 1 0 1 1 0 D7 D6 D5 D4 D3 D2 D1 Priority with CCR 0 0 1 0 1 1 0 1 no 0 0 1 0 1 1 1 2, 3 no 1 0 0 0 0 1 0 1 yes 1 0 0 0 0 1 1 2, 3 yes 1) 1) not supported BLOCK NO STATUS LIM CHK VALUE 82 0 measured value block number 000 normal 001 lower alarm zone (not supported) 010 upper alarm zone (not supported) 011 lower alarm zone (not supported) 100 upper alarm zone (not supported) 101 not used 110 not used 111 invalid or blocked 1 = measured value subject to limit monitoring (not supported) 0 = no limit monitoring measured value in 12 bit 2’ complement format, the sign is extended to 16 bits ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Conversion AVS/AVM • The maximum message length is configurable; therefore the number of blocks of measured values is limited. Attention: This parameter is only active for transmission caused by „status check instruction“, if spontaneous transmission (event) happens, the message contains only one measured value. • Message format with status (IDS) The use of the format “measured value with status” (AVS) can be determined by a parameter: - at status check instruction (SCI), status change - at status check instruction (SCI), status < > 0 (=measured value is invalid) • Status Only “normal” (=0) and “invalid/blocked” is supported Status (RP570) = NT (not topical) v IV (invalid) v OV (overflow) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 83 Protocol Description Address conversion SICAM 1703 RP570/571 The address conversion is parameterized with the OPM (object-orientated process data manager). For this, in the SIP message address conversion the detailed routing type firmware / Trans_mesured_value is provided with the following entries. SICAM 1703-Address: CASDU1 CASDU2 IOA1 IOA2 IOA3 5-stage freely parameterized SICAM 1703 address possible: 0 - 255 TI:Type identification: possible: measured value 15 bit + sign-normalized (TI = 34) measured value 15 bit +sign-scaled (TI = 35) measured value short floating point (TI = 36) RP570-Address: 84 RP570-Prozess-RTU-No: possible: 1-255 RP570-Format: possible: AVS/AVM RP570-Block-No: possible: 0-255 RP570-DVM-coding: coding of “digital measured values”, irrelevant for analog measured values RP570-Priority: possible: - Priority 1 - Priority 2 - Priority 3 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description X_0% Value adaptation: Lower limit of the used measuring range in the external (protocol-specific) format. The corresponding internal value is defined at Y_0%. possible: - 2048 … + 2047 (12 Bit bipolar) X_100% Value adaptation: Upper limit of the used measuring range in the external (protocol-specific) format. The corresponding internal value is defined at Y_100%. possible: - 2048 … + 2047 (12 Bit bipolar) Y_0% Value adaptation: Lower limit of the used measuring range in the selected internal format. The internal format is defined at TI (type identification). The corresponding external value is defined at X_0%. possible: TI 34: -1 … + 1 TI 35: - 32768 … + 32767 TI 36: no check Y_100% Value adaptation: Upper limit of the used measuring range in the selected internal format. The internal format is defined at TI (type identification). The corresponding external value is defined at X_100%. possible: TI 34: -1 … + 1 TI 35: - 32768 … + 32767 TI 36: no check Conversion of measured value: refer chap. 4.5.8 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 85 Protocol Description 2.7.2.3 Measured values digital (DVM) Digital values message DVM RP570/571-message format D7 0 1 0 0 0 0 0 1 RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 0 1 LENGTH 0 0 0 1 START CHARACTER 1 0 1 0 RTU NO RP 571 D0 0 0 1 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 1 1 1 0 0 ROUTER RTU NO FCODE CMD 0 PROCESS RTU NO BLOCK NO SPARE LIM SPA CHK RE STATUS MSB VALUE LSB CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 FCODE: 1) 0 D7 D6 D5 D4 D3 D2 D1 Priority with CCR 0 0 1 1 1 0 0 1 no 0 0 1 1 1 0 1 2, 3 no 1 0 0 1 0 0 0 1 yes 1 0 0 1 0 0 1 2, 3 yes 1) 1) not supported BLOCK NO STATUS LIM CHK VALUE 86 1 measured value block number 000 normal 001 lower alarm zone (not supported) 010 upper alarm zone (not supported) 011 lower alarm zone (not supported) 100 upper alarm zone (not supported) 101 not used 110 not used 111 invalid or blocked 1 = measured value subject to limit monitoring (not supported) 0 = no limit monitoring measured value according RP570-DVM-Codierung - 16 bit bipolar (digital): 16 bit 2’-complement - 16 bit BCD - 16 bit transparent ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Address conversion SICAM 1703 RP570/571 The address conversion is parameterized with the OPM (object-orientated process data manager). For this, in the SIP message address conversion the detailed routing type firmware / Trans_mesured_value is provided with the following entries. SICAM 1703-Address: CASDU1 CASDU2 IOA1 IOA2 IOA3 5-stage freely parameterized SICAM 1703 address possible: 0 - 255 TI: Type identification: possible: step position information (TI = 32) measured value 15 bit + sign-normalized (TI = 34) measured value 15 bit +sign-scaled (TI = 35) measured value short floating point (TI = 36) bit string of 32 bit (TI = 33) RP570-Address: RP570-Prozess-RTU-No: possible: 1-255 RP570-Format: possible: DVM RP570-Block-No: possible: 0-255 RP570-DVM-coding: coding of “digital measured values”, possible: - 16 bit bipolar (digital) - 16 bit BCD - 16 bit transparent RP570-Priority: possible: - Priority 1 - Priority 2 - Priority 3 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 87 Protocol Description 88 X_0% Value adaptation: Lower limit of the used measuring range in the external (protocol-specific) format. The corresponding internal value is defined at Y_0%. possible: - 32768 … + 32767 X_100% Value adaptation: Upper limit of the used measuring range in the external (protocol-specific) format. The corresponding internal value is defined at Y_100%. possible: - 32768 … + 32767 Y_0% Value adaptation: Lower limit of the used measuring range in the selected internal format. The internal format is defined at TI (type identification). The corresponding external value is defined at X_0%. possible: TI 34: - 1 … + 1 TI 35: - 32768 … + 32767 TI 36: no check Y_100% Value adaptation: Upper limit of the used measuring range in the selected internal format. The internal format is defined at TI (type identification). The corresponding external value is defined at X_100%. possible: TI 34: - 1 … + 1 TI 35: - 32768 … + 32767 TI 36: no check ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Note: • Status Only normal (=0) and „invalid/blocked“ (=7) is supported. status (RP570) = NT (not topical) v IV (invalid) v OV (overflow) • No value adaption of “step position information” (TI = 32) and “bit string 32 bit“ (TI = 33): X_0 = X_100 = Y_0 = Y_100 = 0 • At „bit string 32 bit“ (TI = 33) only the least significant two bytes are converted into the DVM-message. • Conversion of measured value: ref. chap. 4.5.8 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 89 Protocol Description 2.7.2.4 Integrated totals (Puls Counter) Puls counter message (PCM) RP570/571-message format D7 0 1 0 0 0 0 0 1 RP 570 START CHARACTER 1 0 1 0 LENGTH RP 571 D0 0 0 1 0 LENGTH 0 0 1 0 START CHARACTER 1 0 1 0 RTU NO 0 0 1 0 0 0 0 0 1 0 1 1 1 0 0 0 0 0 1 0 1 1 0 0 ROUTER RTU NO FCODE CMD 0 PROCESS RTU NO BLOCK NO RC IV CT IT LS IR EPR SPA RE MSB VALUE LSB 24 DAY OF MONTH HOUR 2 0 25 20 2 2 4 HOUR 2 20 MINUTE CHECK SUM STOP CHARACTER 0 0 FCODE: 1) 90 0 1 0 1 1 0 D7 D6 D5 D4 D3 D2 D1 Priority with CCR 0 0 1 1 1 1 0 1 no 0 0 1 1 1 1 1 2, 3 no 1 0 0 1 0 1 0 1 yes 1 0 0 1 0 1 1 2, 3 yes 1) 1) not supported ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Pulse counter telegram (PCT) RP570/571-message format RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 1 0 LENGTH 0 0 1 0 START CHARACTER 1 0 1 0 RTU NO D7 0 1 0 0 0 0 0 1 RP 571 D0 0 0 1 1 0 0 0 0 1 1 0 0 1 1 0 0 0 0 1 1 0 0 0 0 ROUTER RTU NO FCODE CMD 0 PROCESS RTU NO BLOCK NO RC IV CT IT LS IR EPR SPA RE MSB VALUE LSB 2 16 DAY (of month) SPARE 2 15 28 SECONDS (since midnight) 27 20 CHECK SUM 0 0 FCODE: 1) STOP CHARACTER 0 1 0 1 1 0 D7 D6 D5 D4 D3 D2 D1 Priority with CCR 0 0 1 0 1 1 1 1 no 0 0 1 1 0 0 0 2, 3 no 1 0 0 1 1 1 0 1 yes 1 0 0 1 1 1 1 2, 3 yes 1) 1) not supported ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 91 Protocol Description BLOCK NO RC IV CT IT LS IR EPR block number restart counter not supported by firmware; always „0“. invalid value IV = 1 if NT = 1 (not topical) or IV = 1 (invalid) changed time not supported by firmware; always „0“. invalid time IT = 1 if time tag of the integrated total (=count value) is „invalid” local storage 1 = transmission caused by an „intermediate reading“ the quality bits „LS“, „IR“ and „EPR“ are set because of the parameter „PCM_PCT-quality bits”. 1 = transmission caused by an „intermediate reading“ the quality bits „LS“, „IR“ and „EPR“ are set because of the parameter „PCM_PCT-quality bits”. count in 32 bit binary value 2’-complement VALUE DAY, HOUR, MINUTE, SECOND: current time 92 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Address conversion SICAM 1703 RP570/571 The address conversion is parameterized with the OPM (object-orientated process data manager). For this, in the SIP message address conversion the detailed routing type firmware / Trans_counter_value is provided with the following entries. SICAM 1703-Address: CASDU1 CASDU2 IOA1 IOA2 IOA3 5-stage freely parameterized SICAM 1703 address possible: 0 - 255 TI: Type identification: possible: counter value 31 bit sign with sequence number (TI = 37) RP570-Address: RP570-Process-RTU-No: possible: 1-254 RP570-Format: possible: - PCM - PCT RP570-Block-No: possible: 0-255 RP570-Priority: possible: PCM-PCT-quality bits: quality bits to be set in the PCM/PCT - message 1) possible: - form bits on the most recent count interrogation - EPR = 1; IR = 0, LS = 0 - EPR = 0; IR = 1; LS = 0 - EPR = 1; IR = 1, LS = 0 - EPR = 1; IR = 0; LS = 1 - EPR = 0; IR = 1, LS = 1 - EPR = 1; IR = 1; LS = 1 1) - Priority 1 - Priority 2 - Priority 3 Ir = 1 …„intermediate-reading“ (FCOM # 3 EPR = 1…„end of period-reading“(FCOM # 3) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 93 Protocol Description 94 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.7.2.5 Fault distance – Measured value Event recording message fault distance (ERMFD) RP570/571-message format D7 0 1 0 0 0 0 0 1 0 1 D0 RP 570 START CHARACTER 1 0 1 0 LENGTH 0 1 0 1 LENGTH 0 1 0 1 START CHARACTER 1 0 1 0 RTU NO 0 FCODE 1 0 BLOCK NO RP 571 0 0 0 0 0 0 0 1 0 1 0 1 0 0 0 0 0 1 0 1 0 1 0 0 ROUTER RTU NO 1 1 CMD 0 PROCESS RTU NO SEQUENCE NO SPARE FORMAT MSB VALUE LSB T QUALITY SPARE 0 0 0 NS OF DAY OF MONTH MSB TIME LSB MSB RELATIVE TIME (ms) LSB MSB NUMBER LSB CAUSE OF TRANSMISSION CHECK SUM 0 0 STOP CHARACTER 0 1 0 1 1 0 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 95 Protocol Description BLOCK NO SEQUENZ NO block number sequence number The sequence number (0 – 255) is incremented for each event recording message ERMxx. The first value is transmitted with 0; then, the sequence number is incremented from 255 to 1. FORMAT coding of “VALUE”: 000 32 bit unsigned integer; not supported 001 32 bit signed integer; not supported 010 short real number (IEEE STD 754) VALUE 32 bit value coding according “FORMAT” OF 1 = buffer overflow not supported by the firmware; always 0 NS 1 = clock of RTU is not synchronized if time tag of the information is marked as “invalid” T QUALITY time quality 000 time is valid 001 ms and lower is not valid, not supported by the firmware 010 ms x 10 and lower is not valid, not supported by the firmware 011 ms x 100 and lower is not valid, not supported by the firmware 100 second and lower is not valid, not supported by the firmware 101 second x 10 and lower is not valid, not supported by the firmware is set if an error occurs on conversion to RP570-time format DAY OF MONTH day of current month TIME time since midnight in intervals of 0,1 ms NUMBER fault number; always “1” RELATIVE TIME relative time since general start of operation (n* 1ms); always “0” CAUSE OF TRANSMISSION spontaneous = „1“ Conversion: 96 • Each event is transmitted (value has been changed or not) but the value must be valid (NT = 0, IV = 0, OV = 0). • No transmission of the event if cause of transmission is “background scan” (= 02) or “interrogated by station interrogation” in the normal case. • Value adaption also possible ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Address conversion SICAM 1703 RP570/571 The address conversion is parameterized with the OPM (object-orientated process data manager). For this, in the SIP message address conversion the detailed routing type firmware / Trans_mesured_value is provided with the following entries. SICAM 1703-Address: CASDU1 CASDU2 IOA1 IOA2 IOA3 5-stage freely parameterized SICAM 1703 address possible: 0 - 255 TI: Type identification: possible: measured value 15 bit + sign-normalized (TI = 34) measured value 15 bit +sign-scaled (TI = 35) measured value short floating point (TI = 36) RP570-Address: RP570-Prozess-RTU-No: possible: 1-255 RP570-Format: possible: ERMFD RP570-Block-No: possible: 0-255 RP570-Priority: irrelevnt for fault distance RP570-DVM-coding: coding of “digital measured values”, irrelevant for fault distance ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 97 Protocol Description X_0% Value adaptation: Lower limit of the used measuring range in the external (protocol-specific) format. The corresponding internal value is defined at Y_0%. X_100% Value adaptation: Upper limit of the used measuring range in the external (protocol-specific) format. The corresponding internal value is defined at Y_100%. Y_0% Value adaptation: Lower limit of the used measuring range in the selected internal format. The internal format is defined at TI (type identification). The corresponding external value is defined at X_0%. possible: TI 34: - 1 … + 1 TI 35: - 32768 … + 32767 TI 36: no check Y_100% Value adaptation: Upper limit of the used measuring range in the selected internal format. The internal format is defined at TI (type identification). The corresponding external value is defined at X_100%. possible: TI 34: - 1 … + 1 TI 35: - 32768 … + 32767 TI 36: no check Conversion of measured value: refer chap. 4.5.8 98 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.7.3 2.7.3.1 System messages Terminal Status Message (TSTA) TSTA messages are system information of the RTU itself. 8 different TSTA messages are handled for each process-RTU-No, which are initialized after restart with predefined values (refer chap. 4.5.5). If these predefined messages are not acceptable, the TSTA messages can be updated with “single point information” (TI = 30). The access to the internal process image happens with the “RP570 message reference”. (refer address conversion) The transmission of the TSTA message happens only on change on state. Terminal status message (TSTA) RP570/571-message format D7 0 1 0 0 0 0 0 1 0 RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 0 1 LENGTH 0 0 0 1 START CHARACTER 1 0 1 0 RTU NO 0 0 SPARE FCODE 0 1 D0 RP 571 0 0 0 1 0 0 0 0 0 1 1 0 0 1 0 0 0 0 0 1 1 0 0 0 ROUTER RTU NO 0 1 IDENT CMD 0 PROCESS RTU NO D15 RTU STATE D0 CHECK SUM STOP CHARACTER 0 0 0 1 0 1 1 0 IDENT identification of status information RTU STATE status flags of RTU (= Inf. 0 – 15) ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 99 Protocol Description Address conversion SICAM 1703 RP570/571 The address conversion is parameterized with the OPM (object-orientated process data manager). For this, in the SIP message address conversion the detailed routing type firmware / Trans_TSTA is provided with the following entries. SICAM 1703-Address: CASDU1 CASDU2 IOA1 IOA2 IOA3 5-stage freely parameterized SICAM 1703 address possible: 0 - 255 TI: Type identification: possible: single point information (TI = 30) RP570-Address: RP570-Prozess-RTU-No: possible: 1-255 RP570-Ident-No: possible: 0-15 RP570-Bit-No: bit number within the Ident-No. possible: 0-15 RP570-Message reference: The message reference is used for access to the data base of the different TSTA messages possible: 0-7 100 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description 2.7.3.2 Terminal Event Message (TEV) TEV messages are system information of the RTU itself. 8 different TEV messages are handled for each process-RTU-No, which are initialized after restart with predefined values (refer chap. 4.5.6). If these predefined messages are not acceptable, the TSTA messages can be updated with “bit string 32 bit” (TI = 33). The access to the internal process image happens with the “RP570 message reference”. (refer address conversion) The transmission of the TEV message happens only on change on state. RP570/571-message format D7 0 1 0 0 0 0 0 1 0 0 RP 570 START CHARACTER 1 0 1 0 LENGTH 0 0 1 0 LENGTH 0 0 1 0 START CHARACTER 1 0 1 0 RTU NO 0 FCODE 0 1 EVENT NO 1 D0 RP 571 0 0 0 1 0 0 0 0 1 0 1 0 0 1 0 0 0 0 1 0 1 0 0 0 ROUTER RTU NO 1 CMD 0 1 0 PROCESS RTU NO INFO 1 INFO 2 INFO 3 INFO 4 INFO 5 INFO 6 CHECK SUM STOP CHARACTER 0 0 EVENT NO 0 1 0 1 Terminal Event Number ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 101 Protocol Description Address conversion SICAM 1703 RP570/571 The address conversion is parameterized with the OPM (object-orientated process data manager). For this, in the SIP message address conversion the detailed routing type firmware / Trans_TEV is provided with the following entries. SICAM 1703-Address: CASDU1 CASDU2 IOA1 IOA2 IOA3 5-stage freely parameterized SICAM 1703 address possible: 0 - 255 TI: Type identification: possible: bit string 32 bit (TI = 33) RP570-Address: RP570-Prozess-RTU-No: possible: 1-255 RP570-Event-No: possible: 0-31 RP570-Message reference: The message reference is used for access to the data base of the different TSTA messages possible: 0-7 102 TEV-INFO-OFFSET: Byte offset in the TEV message from which the data bytes of the information object (= bits ring of 32 bit) are inserted possible: 0-5 TEV-INFO-byte-count: number of bytes of the information object (= bit string of 32 bit) which are inserted in the TEV message possible: 1-4 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Protocol Description Example: RP570-Process-RTU-Nr RP570-Event-No RP570-Message reference TEV-INFO-Offset TEV-INFO-byte count =x = 23 =3 =1 =4 Terminal event message (after restart) EVENT-NO = 1 EVENT-NO = 1 INFO 1 = 0 INFO 1 = 0 INFO 2 = 0 INFO 2 = 0 INFO 3 = 0 INFO 3 = 0 INFO 4 = 0 INFO 4 = 0 INFO 5 = 0 INFO 5 = 0 INFO 6 = 0 INFO 6 = 0 Terminal event message (updating) Bitstring 32 Bit Bitstring 32 Bit Byte 0 Byte 0 Terminal Event Message Terminal Event Message EVENT-NO = 23 EVENT-NO = 23 Byte 1 Byte 1 INFO 1 INFO 1 Byte 2 Byte 2 INFO 2 INFO 2 Byte 3 Byte 3 INFO 3 INFO 3 INFO 4 INFO 4 INFO 5 INFO 5 INFO 6 INFO 6 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 103 Protocol Description 104 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 Literature ACP 1703 Common Functions System and Protocol Elements DC0-022-2 ACP 1703 Common Functions System and Basic System Elements DC0-014-2 ACP 1703 Platforms Configuration Automation Units and Automation Networks DC0-020-2 TM1703 emic Protocol Elements System Element Manual DC6-048-2 AMIS DC Protocol Elements System Element Manual D23-047-1 Documents for Interoperability ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011 105 Literaturverzeichnis 106 ACP 1703 Ax 1703, Protocol Element Common Functions ABB RP570/571 MPT-S DC0-105-2.00, Ausgabedatum 01.2011

Acp 1703 • Ax 1703 Common Functions - Center

Rating

Date

Size

Views

Categories

Share

Transcript

Forgot your password?.