Siemens Spares SIMATIC. Process Control System PCS 7 Communication Blocks Contents. Communication blocks 1 Index.

Transcription

1 SIMATIC Contents 1 Index Process Control System PCS 7 Communication Blocks Reference Manual Edition 08/2001 A5E Siemens Spares

2 Safety Guidelines This manual contains notices intended to ensure personal safety, as well as to protect the products and connected equipment against damage. These notices are highlighted by the symbols shown below and graded according to severity by the following texts:!!! Danger indicates that death, severe personal injury or substantial property damage will result if proper precautions are not taken. Warning indicates that death, severe personal injury or substantial property damage can result if proper precautions are not taken. Caution indicates that minor personal injury can result if proper precautions are not taken. Caution indicates that property damage can result if proper precautions are not taken. Notice draws your attention to particularly important information on the product, handling the product, or to a particular part of the documentation. Qualified Personnel Only qualified personnel should be allowed to install and work on this equipment. Qualified persons are defined as persons who are authorized to commission, to ground and to tag circuits, equipment, and systems in accordance with established safety practices and standards. Correct Usage Note the following:! Warning This device and its components may only be used for the applications described in the catalog or the technical description, and only in connection with devices or components from other manufacturers which have been approved or recommended by Siemens. This product can only function correctly and safely if it is transported, stored, set up, and installed correctly, and operated and maintained as recommended. Trademarks SIMATIC, SIMATIC HMI and SIMATIC NET are registered trademarks of SIEMENS AG. Third parties using for their own purposes any other names in this document which refer to trademarks might infringe upon the rights of the trademark owners. Copyright Siemens AG 2001 All rights reserved 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. Disclaimer of Liability We have checked the contents of this manual for agreement with the hardware and software described. Since deviations cannot be precluded entirely, we cannot guarantee full agreement. However, the data in this manual are reviewed regularly and any necessary corrections included in subsequent editions. Suggestions for improvement are welcomed. Siemens AG Bereich Automatisierungs- und Antriebstechnik Geschaeftsgebiet Industrie-Automatisierungssysteme Postfach 4848, D Nuernberg Siemens Aktiengesellschaft Siemens AG 2001 Technical data subject to change. A5E

3 Contents FR_BSEND FR_BSEND: Call frame for BSEND Connections of FR_BSEND FR_BRCV FR_BRCV: Call frame for BRCV Connections of FR_BRCV FR_USEND FR_USEND: Call frame for USEND Connections of FR_USEND FR_URCV FR_URCV: Call frame for URCV Connections of FR_URCV FR_AGSEN FR_AGSEN: Call frame for AG_SEND Connections of FR_AGSEN FR_AGRCV FR_AGRCV: Call frame for AG_RECV Connections of FR_AGRCV SEND_BO SEND_BO: Send 128 BOOL values with BSEND Connections of SEND_BO REC_BO REC_BO: Receive 128 BOOL values with BRCV Connections of REC_BO SEND_R SEND_R: Send 32 BOOL and 32 REAL values driven by changes with BSEND Connections of SEND_R REC_R REC_R: Receive 32 BOOL and 32 REAL values with BRCV Connections of REC_R Siemens Spares A5E iii

4 Contents iv A5E

5 1 1.1 FR_BSEND FR_BSEND: Call frame for BSEND Object name (Type + Number) FB 201 Area of Application The block forms a simple interface to the block SFB12 BSEND for the user. It sends data via an MPI, PROFIBUS or Industrial Ethernet connection to a further S7 CPU that has to call the function block type "BRCV" (FC_BRCV or SFB13 BRCV) in order to receive the data. Only data blocks are allowed as data sources or data targets. In STEP7, a homogeneous transport connection is to be installed on both sides and is to be transferred into the automation device. The FR_BSEND should be used instead of the FR_USEND if the extent of data exceeds 440 bytes, or if a secured transmission is required for an extent of data below 440 bytes (acknowledgment is not carried out until the data are entered in the receiver-db - the acknowledgment is signaled by a signal change to 0 at the output CIW). Since data transmission is carried out in segmented form, the data are only available consistently in the receiver-db after the job has been completed (meaning after the acknowledged has arrived). If the parameter FAST is interconnected with 1, the FB allows the sending of one message per function block call possible, because it then internally calls the SFB12 BSEND twice (the SFB12 requires an edge change from 0 to 1 at the control input REQ to be activated). However, it is only advisable to use such frequent send job assignment placing if there is enough time to transfer the message between two FB calls. Siemens Spares A5E

6 Calling OBs The watchdog interrupt OB into which the block is installed (for example OB35). Operating principle Function block FR_BSEND Transmitter Acknowledgement Order with ID, Send-DB-No., Data length max 32kb Operating system Receiver Order with ID, Receive-DB-NO., Data length max. 32kb Operating system Function block FR_BRCV Send-DB read Receive-DB Buffer max. 440 byte MPI or Ethernet/ point-to-point Buffer max 440 byte Sequence of a telegram It is possible to transport a greater data quantity (up to 32 Kbytes) between the communication partners with the internally used SFB12 BSEND than with all other communication SFBs for configured connections. This is because the data range to be sent is segmented. Each segment is sent separately from the CPU operating system to the partner when it is entered automatically by the operating system into the receive-db. Before the next segment is sent the system waits for the operatingsystem-internal acknowledgment of the segment just sent. The send process is activated by the block being called with the value 1 at the control input COM. The block must be called at least once (independently of the cycle) to carry out complete transfer of the parameterized data range. The block transfers the job to the CPU operating system which carries out the job completely. Further calls of the block with the same ID and the same R_ID during the transmission are allowed. However, they have no function (i.e. the block can be called once per cycle). Instead, the value 11 is displayed at the output STAT. Reading of the data from the user memory (corresponds to the "Send-DB" in the figure above) is carried out asynchronously to the processing of the user program. The smallest continuous data quantity that is read consistently by the operating system from the user memory is 32 bytes for the CPUs 4xx. If consistency is also required at the 32-byte limit, the data in the send-db may not be modified after the FR_BSEND has been called as long as the job is running (CIW=1). If the job is completed without errors and a pulse was supplied to the input COM (0 -> 1 -> 0), CIW is set to 0. (In case of an error a new job is triggered automatically with the current data until the transfer has been successful). If the input COM is supplied 1-2 A5E

7 statically with the value 1 (continuous sending), the value 0 will never appear at CIW since each job is immediately followed by a new job). The ID parameter is the connection number which is to be taken from the connection configuration. It is only taken over at the first call after a cold restart. The R_ID parameter is a random number (suggestion: message identification). However, it must be identical for the corresponding send and receive blocks. The parameter is only taken over at the first call after a cold restart. The initial address of the data to be sent is specified by DB_S (data block number) and AD_S (byte start address in the send DB), the length of the data block in bytes by LE_S. If the value 1 is supplied to the parameter FAST, a new message can be sent whenever the FB is called. The FB then internally calls the SFB12 BSEND twice, since the SFB12 requires an edge change from 0 to 1 at the control input REQ to be activated. If the FB is called per cycle, then one message can be sent per cycle. However, it is only advisable to use such frequent send job assignment placing if 1. There is enough time to transfer the message between two FB calls. 2. The call of the FR_BRCV in the receive CPU is faster than that of the FR_BSEND in the send CPU (the receive CPU requires two calls (=2 cycles) for each message of the FR_BRCV). If the value 0 is supplied to the parameter FAST, a new send job can only be carried out at every second FB call. Transfer sequence, FAST = 1 (from sending to receiving) Send order to BESY1 (FR_BSEND) Receive order to BESY2 (FR_BRCV possible normal without function NDR = 1 Data consistent overwriting receive-db disabled NDR = 0 Receive-order to BESY2 overwriting receive-db enabled Data from send-db to buffer BESY1 (block-wise) Block1 Block2 last block Block1 Transmit BESY1 to BESY2 Data from buffer BESY2 in Receive-DB (block-wise) Block1 440 byte Block1 Block2 Block2 Block1 Block1 BESY1: Operating system of the CPU1 BESY2: Operating system of the CPU2 Transmission sequence (1 to n blocks) receive data can be evaluated next trans. sequ. t Siemens Spares A5E

8 Transfer sequence, FAST = 0 (from sending to receiving) Send order to BESY1 (FR_BSEND) Receive order to BESY2 (FR_BRCV) Second call of the FR_BSEND possible without function normal NDR = 1, NDR = 0, receive order to BESY2, Data consistent, overwriting receive-db enabled overwriting second call of receive-db disabled first call the FR_BSEND Data from send-db to buffer BESY1 (block-wise) Block1 Block2 Block1 Transmit BESY1 to BESY2 Data from send-db to buffer BESY1 (block-wise) Block1 Block2 440 byte Block1 Block2 Block1 Block1 BESY1: Operating system of the CPU1 BESY2: Operating system of the CPU2 Transmission sequence (1 to n blocks) Receive next Data can transm. sequ. be evaluated t The outputs ERR (Error) and STAT (Status) indicate specific error information that corresponds to the SFB12 (refer to error handling). (In case of an error a new job is triggered automatically with the current data until the transfer has been successful). Error handling The blocks error handling is limited to the error information of the outputs ERR and STAT of the subordinate SFB12 BSEND (refer to the "System software for S7-300/400 - System and standard functions" manual). (In case of an error a new job is triggered automatically with the current data until the transfer has been successful). Start-up characteristics Do not exist. Time response Does not exist. Message characteristics Do not exist. Operator control and monitoring Does not exist. 1-4 A5E

9 1.1.2 Connections of FR_BSEND The state of delivery of the block display in the CFC is marked in the "Connection" column: Connection name bold = Connection displayed, normal = Not displayed. Connection (parameter) Meaning Data type Initial I/O AD_S Start address in the send DB in bytes INT 0 I CIW Job being executed BOOL 0 O COM Send command Static 1: Send continuously Pulse 1: Send once BOOL 0 I DB_S Send data block number INT 0 I ERR Error (for error type see STAT) BOOL 0 O FAST Transfer type 1 = One message can be transferred per FB call 0 = One message can be transferred with two FB calls BOOL 0 I ID Connection ID WORD 0 I LE_S Send data length in bytes INT 0 I R_ID Message ID DWORD 0 I STAT Error ID WORD 0 O Siemens Spares A5E

10 1.2 FR_BRCV FR_BRCV: Call frame for BRCV Object name (Type + Number) FB 202 Area of Application The block forms a simple interface to the block SFB13 BRCV for the user. It receives data via an MPI, PROFIBUS or Ethernet connection from a further S7 CPU that has to call the function block type "BSEND" (FC_BSEND or SFB12 BSEND) in order to send the data. Only data blocks are allowed as data targets. In STEP7, a homogeneous transport connection is to be installed on both sides and is to be transferred into the automation device. The FR_BRCV should be used instead of the FR_URCV if the extent of data exceeds 440 bytes, or if a secured transmission is required for an extent of data below 440 bytes (acknowledgment is not carried out until the data are entered in the receiver-db - the acknowledgment is signaled by a signal change to 1 at the output NDR). Since data transmission is carried out in segmented form, the data are only available after the job has been completed (meaning after the signal change of the output NDR from 0 to 1). Calling OBs The watchdog interrupt OB into which the block is installed (for example OB35). 1-6 A5E

11 Operating principle Function block FR_BSEND Transmitter Acknowledgement Order with ID, Send-DB-No., Data length max 32kb Operating system Receiver Order with ID, Receive-DB-NO., Data length max. 32kb Operating system Function block FR_BRCV Send-DB read Receive-DB Buffer max. 440 byte MPI or Ethernet/ point-to-point Buffer max 440 byte Sequenceof a telegram It is possible to transport a greater data quantity (up to 32 Kbytes) between the communication partners with the internally used SFB13 BRCV than with all other communication SFBs for configured connections. This is because the data range to be sent is segmented. Each segment is received separately by the CPU operating system and is entered in the receive-db. Before the next segment can be received an operating-system-internal acknowledgment of the segment just received has to be sent. Entering of the data into the user memory (corresponds to the "Receive DB" in the figure above) is carried out asynchronously to the processing of the user program. The smallest continuous data quantity that is written consistently by the operating system into the user memory is 32 bytes for the CPUs 4xx. If consistency is also required at the 32-byte limit, the data in the receive DB may not be modified after the FR_BRCV has been called as long as the job is running (NDR = 1). If the job has been completed without errors, the output NDR is set to 1 for one cycle. In the subsequent cycle the FB automatically provides the receive enable to the CPU operating system (NDR is 0 again from and including this call). The receive enable can already be effective before the first receive job arrives. In this case it is stored by the operating system. The ID parameter is the connection number which is to be taken from the connection configuration. It is only taken over at the first call after a cold restart. The R_ID parameter is a random number (suggestion: message identification). However, it must be identical for the corresponding send and receive blocks. The parameter is only taken over at the first call after a cold restart. Siemens Spares A5E

12 A call of the FR_BRCV must be carried out for each ID/R_ID pair in each program cycle (cyclically or also via time interrupts) Two calls of the FR_BRCV are required for each message. The initial address of the target area of the received data is specified by DB_R (data block number) and AD_R (initial address in the receive DB in bytes). The parameter LE_MAX specifies the maximum number of receivable data in bytes. The parameter LE_R specifies the number of data already received in bytes at every cycle. The outputs ERR (Error) and STAT (Status) indicate specific error information that corresponds to the SFB13 (refer to error handling). Error handling The blocks error handling is limited to the error information of the outputs ERR and STAT of the subordinate SFB13 BRCV (refer to the "System software for S7-300/400 - System and standard functions" manual). Start-up characteristics Do not exist. Time response Does not exist. Message characteristics Do not exist. Operator control and monitoring Does not exist. 1-8 A5E

13 1.2.2 Connections of FR_BRCV The state of delivery of the block display in the CFC is marked in the "Connection" column: Connection name bold = Connection displayed, normal = Not displayed. Connection (parameter) Meaning Data type Initial I/O AD_R Start address in the receive DB in bytes INT 0 I DB_R Receive data block number INT 0 I ERR Error (for error type see STAT) BOOL 0 O ID Connection ID WORD 0 I LE_MAX Maximum receive data length in bytes INT 0 I LE_R Currently received data length in bytes INT 0 O NDR 1 = New data in the receive DB Data are consistent BOOL 0 O R_ID Message ID DWORD 0 I STAT Error ID WORD 0 O Siemens Spares A5E

14 1.3 FR_USEND FR_USEND: Call frame for USEND Object name (Type + Number) FB 203 Area of Application The block forms a simple interface to the block SFB8 USEND for the user. It sends data via an MPI, PROFIBUS or Industrial Ethernet connection to a further S7 CPU (with MPI also M7 or M7-S7) that has to call the function block type "URCV" (FC_URCV or SFB8 URCV) in order to receive the data. Only data blocks are allowed as data sources or data targets. In STEP7, a homogeneous transport connection is to be installed on both sides and is to be transferred into the automation device. The FR_USEND can be used instead of the FR_BSEND if the data range is smaller than 440 bytes, data consistency is required consistently across the complete send data area and no secured transmission is demanded. On "Data consistency": The data are constantly consistent in the receive DB (in contrast to the FR_BSEND). This is ensured by the fact that the data are already copied completely and directly into the buffer - resp. from the buffer - of the operating system when the function blocks FR_USEND and FR_UREC are called by these function blocks. Inconsistency can only occur if the copy procedure is interrupted by an interrupt program (corresponds to interruption of the subordinate SFB8 USEND or SFB9 URCV) and if the send/receive data are modified in the interrupt program. On "No secured transfer": In the case of FR_URCV/URCV the acknowledgment is generated on the operating-system-level without constant coordination. This means that the acknowledgment also arrives at the FR_USEND when the data could not be entered into the receive DB, for example when the receive CPU is in STOP. The acknowledgment can be recognized by the fact that the signal changes to 0 at the output CIW. If the parameter FAST is interconnected with 1, the FB allows the sending of one message per function block call possible, because it then internally calls the SFB8 USEND twice (the SFB8 requires an edge change from 0 to 1 at the control input REQ to be activated). However, it is only advisable to use such frequent send job assignment placing if there is enough time to transfer the message between two FB calls A5E

15 Calling OBs The watchdog interrupt OB into which the block is installed (for example OB35). Operating principle Function block FR_USEND Transmitter Acknowledgement Receiver Function block FR_URCV Copy data consistently Order with ID, R_ID, data length Order with ID, R_ID, data length Copy data consistently Operating system Operating system Send-DB Receive-DB max. 440 byte Buffer max. 440 byte MPI, Ind.Ethernet, PROFIBUS Buffer max. 440 byte Sequence of a telegram A data quantity of 440 bytes can be transferred consistently between the communication partners by means of the SFB8 USEND used internally. The send procedure is carried out with regard to the acknowledgment without coordination with the receive function block. This means that the acknowledgment is generated by the operating system of the receiver without waiting for the call of the receive block. The send process is activated by the block being called with the value 1 at the control input COM. The block must be called at least once (independently of the cycle) to carry out complete transfer of the parameterized data range. The block copies the complete data from the send DB consistently into the buffer of the CPU operating system and transfers the send job to the operating system. Further calls of the block with the same ID and the same R_ID during the transmission are allowed. However, they have no function (i.e. the block can be called once per cycle). Instead, the value 11 is displayed at the output STAT. The value 1 is displayed at the state parameter CIW as long as the sending process is running. If the job is completed without errors and a pulse was supplied to the input COM (0-> 1 -> 0), CIW is set to 0. (In case of an error a new job is triggered automatically with the current data until the transfer has been successful). If the input COM is supplied statically with the value 1 (continuous sending), the value 0 will never appear at CIW since each job is immediately followed by a new job). Siemens Spares A5E

16 The ID parameter is the connection number which is to be taken from the connection configuration. It is only taken over at the first call after a cold restart. The R_ID parameter is a random number (suggestion: message identification). However, it must be identical for the corresponding send and receive blocks. The parameter is only taken over at the first call after a cold restart. The initial address of the data to be sent is specified by DB_S (data block number) and AD_S (byte start address in the send DB), the length of the data block in bytes by LE_S. After a cold restart the lengths can only be reduced (since the operating system reserves a buffer in the then specified length after a cold restart), whereby the send length always has to be smaller than the receive length. If the value 1 is supplied to the parameter FAST, a new message can be sent whenever the FB is called. The FB then internally calls the SFB8 USEND twice, since the SFB8 requires an edge change from 0 to 1 at the control input REQ to be activated. If the FB is called per cycle, then one message can be sent per cycle. However, it is only advisable to use such frequent send job assignment placing if there is enough time to transfer the message between two FB calls. If the value 0 is supplied to the parameter FAST, a new send job can only be carried out at every second FB call. Transfer sequence, FAST = 1 (from sending to receiving) Copy data from send-db from FR_USEND intobesy1 buffer BESY1 kopieren NDR = 1, copy new data (data in the receive-db always consistent) Transmit BESY1 to BESY2 Copy data from buffer BESY2 Into receive-db from FR_URCV max. 440 byte new copy order: without function (no new data exist in the buffer, NDR = 0) BESY1: Operating system of the CPU1 BESY2: Operating system of the CPU2 Transmission sequence Transmission sequence t 1-12 A5E

17 Transfer sequence, FAST = 0 (from sending to receiving) Copy data from send-db into buffer BESY1 from FR_USEND 2nd call NDR = 1, new data copied (data in the receive-db always consistent) 2nd call Transmit BESY1 to BESY2 max. 440 byte new copy order: without function (no new data exist in the buffer, NDR = 0) Copy data from buffer BESY2 into the receive-db from FR_URCV BESY1: Operating system of the CPU1 BESY2: Operating system of the CPU2 Transmission sequence Transmission sequence t The outputs ERR (Error) and STAT (Status) indicate specific error information that corresponds to the SFB8 (refer to error handling). Error handling The blocks error handling is limited to the error information of the ERR and STAT outputs of the subordinate SFB8 USEND (refer to the "System software for S7-300/400 - System and standard functions" manual). (In case of an error a new job is triggered automatically with the current data until the transfer has been successful). Start-up characteristics Do not exist. Time response Does not exist. Message characteristics Do not exist. Operator control and monitoring Does not exist. Siemens Spares A5E

18 1.3.2 Connections of FR_USEND The state of delivery of the block display in the CFC is marked in the "Connection" column: Connection name bold = Connection displayed, normal = Not displayed. Connection (parameter) Meaning Data type Initial I/O AD_S Start address in the send DB in bytes INT 0 I CIW Job being executed BOOL 0 O COM Send command Static 1: Send continuously Pulse 1: Send once BOOL 0 I DB_S Send data block number INT 0 I ERR Error (for error type see STAT) BOOL 0 O FAST Transfer type 1 = One message can be transferred per FB call 0 = One message can be transferred with two FB calls BOOL 0 I ID Connection ID WORD 0 I LE_S Send data length in bytes INT 0 I R_ID Message ID DWORD 0 I STAT Error ID WORD 0 O 1-14 A5E

19 1.4 FR_URCV FR_URCV: Call frame for URCV Object name (Type + Number) FB 204 Area of Application The block forms a simple interface to the block SFB9 URCV for the user. It receives data via an MPI, PROFIBUS or Ethernet connection from a further S7 CPU (with MPI also M7-M7 or M7-S7) that has to call the function block type "USEND" (FC_USEND or SFB8 USEND) in order to receive the data. Only data blocks are allowed as data targets. In STEP7, a homogeneous transport connection is to be installed on both sides and is to be transferred into the automation device. The FR_URCV can be used instead of the FR_BRCV if the data range is smaller than 440 bytes, data consistency is required consistently across the complete send data area and no secured transmission is demanded. On "Data consistency": The data are constantly consistent in the receive DB (in contrast to the FR_BRCV). This is ensured by the fact that the data are already copied completely and directly into the buffer - resp. from the buffer - of the operating system when the function blocks FR_USEND and FR_UREC are called by these function blocks. Inconsistency can only occur if the copy procedure is interrupted by an interrupt program (corresponds to interruption of the subordinate SFB8 USEND or SFB9 URCV) and if the send/receive data are modified in the interrupt program. On "No secured transfer": In the case of FR_URCV/URCV the acknowledgment is generated on the operating-system-level without constant coordination with the user program. This means that the acknowledgment is generated immediately after the data have arrived without waiting for the call of the receive block. The existence of new receive data can be recognized by the fact that the signal changes to 1 at the output NDR. If new receive data arrive before the block has been called, these overwrite the old data in the buffer. The value 9 is then output at the output STAT at the next block call (refer to error handling). Calling OBs The watchdog interrupt OB into which the block is installed (for example OB35). Siemens Spares A5E

20 Operating principle Function block FR_USEND Transmitter Acknowledgement Receiver Function block FR_URCV Copy data consistently Order with ID, R_ID, data length Order with ID, R_ID, data length Copy data consistently Operating system Operating system Send-DB Receive-DB max. 440 byte Buffer max. 440 byte MPI, Ind.Ethernet, PROFIBUS Buffer max. 440 byte Sequence of a telegram A maximum of 440 bytes can be transported between the communication partners by means of the SFB9 URCV used internally. The block must be called at least once (independently of the cycle) to carry out complete transfer of the parameterized data range. Entering the data into the user memory (corresponds to the "Receive DB" in the figure above) is carried out synchronously to the processing of the user program. This means that he data are also consistent when NDR equals 0. If the job has been completed without errors, the output NDR is set to 1 for one cycle. The ID parameter is the connection number which is to be taken from the connection configuration. It is only taken over at the first call after a cold restart. The R_ID parameter is a random number (suggestion: message identification). However, it must be identical for the corresponding send and receive blocks. The parameter is only taken over at the first call after a cold restart. A call of the FR_URCV must be carried out for each ID/R_ID pair in each program cycle (cyclically or also via time interrupts) The initial address of the target area of the received data is specified by DB_R (data block number) and AD_R (initial address in the receive DB in bytes). The parameter LE_MAX specifies the maximum number of receivable data in bytes. The outputs ERR (Error) and STAT (Status) indicate specific error information that corresponds to the SFB9 (refer to error handling) A5E

21 Error handling The blocks error handling is limited to the error information of the ERR and STAT outputs of the subordinate SFB9 URCV (refer to the "System software for S7-300/400 - System and standard functions" manual). Start-up characteristics Do not exist. Time response Does not exist. Message characteristics Do not exist. Operator control and monitoring Does not exist Connections of FR_URCV The state of delivery of the block display in the CFC is marked in the "Connection" column: Connection name bold = Connection displayed, normal = Not displayed. Connection (parameter) Meaning Data type Initial I/O AD_R Start address in the receive DB in bytes INT 0 I DB_R Receive data block number INT 0 I ERR Error (for error type see STAT) BOOL 0 O ID Connection ID WORD 0 I LE_MAX Maximum receive data length in bytes INT 0 I NDR 1 = New data in the receive DB Data are consistent BOOL 0 O R_ID Message ID DWORD 0 I STAT Error ID WORD 0 O Siemens Spares A5E

22 1.5 FR_AGSEN FR_AGSEN: Call frame for AG_SEND Object name (Type + Number) FB 205 Area of Application The FB forms a simple interface to the block FC5 AG_SEND for the user. The FC5 is integrated in the FB and therefore does not have to be loaded separately. It sends data via a PROFIBUS CP443-5 Extended (FDL) or Industrial Ethernet CP443-1 connection (ISO or ISO-on-TCP) to a further S7 CPU, an S5 CPU, a PC/programming device or an external device. At an S7-S7 connection the receive side must call the block FR_AGRCV/AG_RCV in order to receive the data. The receive side in an S7-S5 connection must call the handling blocks RECEIVE. Only data blocks are allowed as data sources or data targets. The FR_AGSEN can be used to transfer data with the CP443-1 or CP443-5 Extended. It can transfer a maximum of 240 bytes per message unsecured and consistently. On "Data consistency": The data are constantly consistent in the receive DB. This is ensured by the fact that the data are already copied completely and directly into the CP443 - resp. from the CP443 - when the function blocks FR_AGSEN and FR_AGRCV are called. Inconsistencies cannot arise because the subordinate blocks FC5 AG_SEND and FC6 AG_RCV cannot be interrupted by higher-priority OBs. On "No secured transfer": In the case of FR_AGRCV/AG_RCV the acknowledgment is generated on the operating-system-level without constant coordination. This means that the acknowledgment also arrives at the FR_AGSEN when the data could not be entered into the receive DB, for example when the receive CPU is in STOP. The acknowledgment can be recognized by the fact that the signal changes to 0 at the output CIW. Calling OBs The watchdog interrupt OB into which the block is installed (for example OB35) A5E

23 Operating principle Function block FR_AGSEN Transmitter Acknowledgement Receiver Function block FR_AGRCV Copy data consistently Order with ID and data length Order with ID and data length Copy data consistently Operating system Operating system Send-DB Receive-DB max. 240 byte CP443-1 MPI, Ind.Ethernet, PROFIBUS CP443-1 Sequence of a telegram A data quantity of 240 bytes can be transferred consistently between the communication partners by means of the FC5 AG_SEND used internally. The send procedure is carried out with regard to the acknowledgment without coordination with the receive function block. This means that the acknowledgment is generated by the operating system of the receiver without waiting for the call of the receive block. The send process is activated by the block being called with the value 1 at the control input COM. The block must be called at least once (independently of the cycle) to carry out complete transfer of the parameterized data range. The block copies the complete data from the send DB consistently to the CP443-1 or CP443-5 Extended and transfers the send job to the CP. Further calls of the block during the transmission are allowed. However, they have no function (i.e. the block can be called once per cycle). Instead, the value 11 is displayed at the output STAT. The value 1 is displayed at the state parameter CIW as long as the sending process is running. If the job is completed without errors and a pulse was supplied to the input COM (0-> 1 -> 0), CIW is set to 0. (In case of an error a new job is triggered automatically with the current data until the transfer has been successful). If the input COM is supplied statically with the value 1 (continuous sending), the value 0 will never appear at CIW since each job is immediately followed by a new job). The parameter LADDR is the module starting address of the CP443-1 or CP443-5 Extended via which the data are to be sent. It is to be taken from the HW-Config. The parameter is only taken over at the first call after a cold restart. Siemens Spares A5E

24 The ID parameter is the connection number which is to be taken from the connection configuration. It is only taken over at the first call after a cold restart. The initial address of the data to be sent is specified by DB_S (data block number) and AD_S (byte start address in the send DB), the length of the data block in bytes by LE_S. Transfer sequence (from sending to receiving) Copy data from send-db into CP1 from FR_AGSEN NDR = 1, new data copied (data in the receive-db always consistent) Transmit CP1 to CP2 Copy data from buffer CP2 into receive-db from FR_AGRCV max. 440 byte new copy order: without function (no new data exist in CP: NDR = 0) Transmission sequence Transmission sequence t The outputs ERR (Error) and STAT (Status) indicate specific error information that corresponds to the FC5 (refer to error handling). Error handling The blocks error handling is limited to the error information of the outputs ERR and STAT of the subordinate FC5 AG_SEND (refer to the "SIMATIC NET NCM S7 for PROFIBUS" manual). (In case of an error a new job is triggered automatically with the current data until the transfer has been successful). Note In the case of entries with the coding 8FxxH under STATUS also refer to the information in the "System Software for S7-300/400 - Standard and System Functions" reference manual. The information can be found in the chapter "Error evaluation with the output parameter RET_VAL" A5E

25 Start-up characteristics Do not exist. Time response Does not exist. Message characteristics Do not exist. Operator control and monitoring Does not exist Connections of FR_AGSEN The state of delivery of the block display in the CFC is marked in the "Connection" column: Connection name bold = Connection displayed, normal = Not displayed. Connection (parameter) Meaning Data type Initial I/O AD_S Start address in the send DB in bytes INT 0 I CIW Job being executed BOOL 0 O COM Send command Static 1: Send continuously Pulse 1: Send once BOOL 0 I DB_S Send data block number INT 0 I ERR Error (for error type see STAT) BOOL 0 O ID Connection ID INT 0 I LADDR CP module start address (in hex) WORD 0 I LE_S Send data length in bytes INT 0 I STAT Error ID WORD 0 O Siemens Spares A5E

26 1.6 FR_AGRCV FR_AGRCV: Call frame for AG_RECV Object name (Type + Number) FB 206 Area of Application The block forms a single interface to the block FC6 AG_RECV for the user. The FC6 is integrated in the FB and therefore does not have to be loaded separately. It receives data via a PROFIBUS (FDL) CP443-5 Extended or Industrial Ethernet CP443-1 connection (ISO or ISO-on-TCP) from a further S7 CPU, an S5 CPU, a PC/programming device or an external device. At an S7-S7 connection the send side must call the block FR_AGSEN/AG_SEND. The send side in an S7-S5 connection must call the handling block SEND. Only data blocks are allowed as data targets. The FR_AGRCV can be used to transfer data with the CP443-1 or CP443-5 Extended. It can transfer a maximum of 240 bytes per message unsecured and consistently. On "Data consistency": The data are constantly consistent in the receive DB. This is ensured by the fact that the data are already copied completely and directly into the CP443 - resp. from the CP443 - when the function blocks FR_AGSEN and FR_AGRCV are called. Inconsistencies cannot arise because the subordinate blocks FC5 AG_SEND and FC6 AG_RCV cannot be interrupted by higher-priority OBs. On "No secured transfer": In the case of FR_AGRCV/AG_RCV the acknowledgment is generated on the operating-system-level without constant coordination with the user program. This means that the acknowledgment is generated immediately after the data have arrived without waiting for the call of the receive block. The existence of new receive data can be recognized by the fact that the signal changes to 1 at the output NDR. Calling OBs The watchdog interrupt OB into which the block is installed (for example OB35) A5E

27 Operating principle Function block FR_AGSE Transmitter Acknowledgement Receiver Function block F_AGRCV Copy data consistently Order with ID, R_ID, data length Order with ID, R_ID, data length Copy data consistently Operating system Operating system Send-DB Receive-DB max. 440 byte Buffer max. 440 byte MPI, Ind.Ethernet, PROFIBUS Buffer max. 440 byte Sequence of a telegram A data quantity of 240 bytes can be transferred consistently between the communication partners by means of the FC6 AG_RECV used internally. The block must be called at least once (independently of the cycle) to carry out complete transfer of the parameterized data range. Entering the data into the user memory (corresponds to the "Receive DB" in the figure above) is carried out synchronously to the processing of the user program. This means that he data are also consistent when NDR equals 0. If the job has been completed without errors, the output NDR is set to 1 for one cycle. The parameter LADDR is the module starting address of the CP443-1 or CP443-5 Extended via which the data are to be sent. It is to be taken from the HW-Config. The parameter is only taken over at the first call after a cold restart. The ID parameter is the connection number which is to be taken from the connection configuration. It is only taken over at the first call after a cold restart. The initial address of the target area of the received data is specified by DB_R (data block number) and AD_R (initial address in the receive DB in bytes). The parameter LE_R specifies the number of data received in bytes. The outputs ERR (Error) and STAT (Status) indicate specific error information that corresponds to the FC6 (refer to error handling). Siemens Spares A5E

28 Error handling The blocks error handling is limited to the error information of the ERR and STAT outputs of the subordinate FC6 AG_RECV (refer to the "SIMATIC NET NCM S7 for PROFIBUS" manual). Note In the case of entries with the coding 8FxxH under STATUS also refer to the information in the "System Software for S7-300/400 - Standard and System Functions" reference manual. The information can be found in the chapter "Error evaluation with the output parameter RET_VAL". Start-up characteristics Do not exist. Time response Does not exist. Message characteristics Do not exist. Operator control and monitoring Does not exist Connections of FR_AGRCV The state of delivery of the block display in the CFC is marked in the "Connection" column: Connection name bold = Connection displayed, normal = Not displayed. Connection (parameter) Meaning Data type Initial I/O AD_R Start address in the receive DB in bytes INT 0 I DB_R Receive data block number INT 0 I ERR Error (for error type see STAT) BOOL 0 O ID Connection ID INT 0 I LADDR CP module start address (in hex) WORD 0 I LE_R Receive data length in bytes INT 0 O NDR 1 = New data in the receive DB Data are consistent BOOL 0 O STAT Error ID WORD 0 O 1-24 A5E

29 1.7 SEND_BO SEND_BO: Send 128 BOOL values with BSEND Object name (Type + Number) FB 207 Area of Application The block forms a simple interface to the block SFB12 BSEND for the user. It sends up to 128 BOOL values via an MPI, PROFIBUS or Industrial Ethernet connections to a further S7 CPU which has to call up the "REC_BO" (FB 208) function block type of the PCS7 Communication library in order to receive the data. The data are not available consistently in the REC_BO until after the job has been completed (meaning after the acknowledgment DONE = TRUE has arrived). The acknowledgment can be recognized by the fact that the signal changes to 0 at the output CIW. If the parameter FAST is interconnected with 1, the FB allows the sending of one message per function block call possible, because it then internally calls the SFB12 BSEND twice (the SFB12 requires an edge change from 0 to 1 at its control input REQ to be activated). However, it is only advisable to use such frequent send job assignment placing if there is enough time to transfer the message between two FB calls. Calling OBs The watchdog interrupt OB into which the block is installed (for example OB35). Operating principle A maximum of 128 BOOL values can be transported between the communication partners by means of the SFB12 BSEND used internally. They are sent to the partner by the operating system of the CPU where it is entered automatically into the instance DB of the receiving FB (REC_BO) by the operating system. Before the new 128 BOOL values are sent, the system waits for the operating-system internal acknowledgment of the values just sent. The send process is activated by the block being called with the value 1 at the control input COM. The block must be called at least once (independently of the cycle) to carry out complete transfer of the data. The block transfers the job to the CPU operating system which carries out the job completely. Further calls of the Siemens block with the same ID and the same Spares R_ID during the transmission are allowed. A5E

30 However, they have no function (i.e. the block can be called once per cycle). Instead, the value 11 is displayed at the output STAT. Reading of the data from the user memory is carried out asynchronously to the processing of the user program. CIW is set to 0 if the job is terminated without errors. (In case of an error, ERR = 1, a new job is triggered automatically with the current data until the transfer has been successful). If the value 0 is supplied to the input COM, a transfer which has not been completed yet is aborted and no longer sent. CIW is then equal to 0. The ID parameter is the connection number which is to be taken from the connection configuration. It is only taken over at the first call after a cold restart. The R_ID parameter is a random number (suggestion: message identification). However, it must be identical for the corresponding send and receive blocks. The parameter is only taken over at the first call after a cold restart. If the value 1 is supplied to the parameter FAST, a new message can be sent whenever the FB is called. The FB then internally calls the SFB12 BSEND twice, since the SFB12 requires an edge change from 0 to 1 at the control input REQ to be activated. If the FB is called per cycle, then one message can be sent per cycle. However, it is only advisable to use such frequent send job assignment placing if there is enough time to transfer the message between two FB calls. In addition using a frequent send job is only advisable if the call of the REC_BO in the receive CPU is faster than that of the SEND_BO in the send CPU (the receive CPU requires two calls (=2 cycles) for each message of the REC_BO). If the value 0 is supplied to the parameter FAST, a new send job can only be carried out at every second FB call. Error handling The blocks error handling is limited to the error information of the subordinate SFB12 BSEND (refer to the "System software for S7-300/400 - System and standard functions" manual). The outputs ERR and STAT are described there. (In case of an error a new job is triggered automatically with the current data until the transfer has been successful). Start-up characteristics Do not exist. Time response Does not exist. Message characteristics Do not exist. Operator control and monitoring Does not exist A5E

31 1.7.2 Connections of SEND_BO The state of delivery of the block display in the CFC is marked in the "Connection" column: Connection name bold = Connection displayed, normal = Not displayed. Connection (parameter) Meaning Data type Initial I/O BO_00 Input_00 BOOL 0 I... BO_15 Input_15 BOOL 0 I BO_16 Input_16 BOOL 0 I BO_127 Input_127 BOOL 0 I CIW 1 = Job being executed BOOL 0 O COM 1 = Send Continuously, 0 = Do not send BOOL 1 I DONE Command is Done BOOL 0 O ERR Error (for error type see STAT) BOOL 0 O FAST Transfer type: 1 = One message can be transferred per FB call 0 = One message can be transferred with two FB calls BOOL 0 I ID Connection ID WORD 0 I R_ID Message ID DWORD 0 I STAT Error ID WORD 0 O Siemens Spares A5E

32 1.8 REC_BO REC_BO: Receive 128 BOOL values with BRCV Object name (Type + Number) FB 208 Area of Application The block forms a simple interface to the block SFB13 BRCV for the user. It receives 128 BOOL values via an MPI, PROFIBUS or Ethernet connections from a further S7 CPU which has to call up the "SEND_BO" function block type of the PCS7 Communication library (FB207) in order to send the data. In STEP7, a homogeneous transport connection is to be installed on both sides and is to be transferred into the automation device. The data are only available after the command has been completed at a signal change of the NDR output from 0 to 1. Calling OBs The watchdog interrupt OB into which the block is installed (for example OB35). Operating principle A maximum of 128 BOOL values can be transported between the communication partners by means of the SFB13 BRCV used internally. The data are received by the operating system of the CPU and entered in the instance DB of the receive FB (REC_BO). Before new data are received, an operating-system internal acknowledgment of the data just received has to be sent. Entering the data in the data block is carried out asynchronously to the processing of the user program. After the REC_BO has been called, the data in the instance DB may not be processed as long as the command is running (NDR = 0). If the job has been completed without errors, the output NDR is set to 1 for one cycle. In the subsequent cycle the FB automatically provides the receive enable to the CPU operating system (NDR is 0 again from and including this call). The receive enable can already be effective before the first receive job arrives. In this case it is stored by the operating system. The ID parameter is the connection number which is to be taken from the connection configuration. It is only taken over at the first call after a cold restart A5E

33 The R_ID parameter is a random number (suggestion: message identification). However, it must be identical for the corresponding send and receive blocks. The parameter is only taken over at the first call after a cold restart. A call of the REC_BO must be carried out for each ID/R_ID pair in each program cycle (cyclically or also via time interrupts). Two calls of the REC_BO are required for each message. The outputs ERR (Error) and STAT (Status) indicate specific error information that corresponds to the SFB13 (refer to error handling). In case of an error substitute values can optionally be output as received data (refer to error handling). Error handling The blocks error handling is limited to the error information of the subordinate SFB13 BRCV (refer to the "System software for S7-300/400 - System and standard functions" manual). The outputs ERR and STAT are described there. If the input SUBS_ON = TRUE, substitute values are output at receipt errors or after new data are not received after REC_MON (number of cycles). Start-up characteristics Do not exist. Time response Does not exist. Message characteristics Do not exist. Operator control and monitoring Does not exist. Siemens Spares A5E

34 1.8.2 Connections of REC_BO The state of delivery of the block display in the CFC is marked in the "Connection" column: Connection name bold = Connection displayed, normal = Not displayed. Connection (parameter) Meaning Data type Initial I/O ERR 1 = Error (for error type see STAT) BOOL 0 O ID Connection ID WORD 0 I NDR 1 = New Data Received BOOL 0 O QNO_REC 1 = No Data Received BOOL 0 I QSUBS_ON 1 = Substitute Values BOOL 0 I R_ID Message ID DWORD 0 I RD_BO_00 Received Value_00 BOOL 0 O... RD_BO_15 Received Value_15 BOOL 0 O RD_BO_16 Received Value_16 BOOL 0 O... RD_BO_127 Received Value_127 BOOL 0 O REC_MON Receive Monitoring (cycles) INT 3 I STAT Error ID WORD 0 O SUBBO_00 Substitute Value_00 BOOL 0 I... SUBBO_15 Substitute Value_15 BOOL 0 I SUBBO_16 Substitute Value_16 BOOL 0 I... SUBBO127 Substitute Value_127 BOOL 0 I SUBS_ON 1 = Substitute Values On by Error BOOL 0 I 1-30 A5E