S7-400, M7-400 Programmable Controllers

Transcription

1 This Supplement contains additional information about the products. It is a separate component and should be considered more up-to-date than the information in the manuals and catalogs if uncertainties arise.

2 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. Siemens AG Bereich Automatisierungs- und Antriebstechnik Geschaeftsgebiet Industrie-Automatisierungssysteme Postfach 4848, D Nuernberg 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. Technical data subject to change.

3 Supplement to Manual S7-400, M7-400 Contents 1 Connecting the Central Rack (CR) and the Expansion Rack (ER) Special Features of STEP 7 Programming with CPUs 41x Special Features of Communication Behavior of S7-400 Signal Modules After Parameter Assignment PROFIBUS DP Master Interface IM

4 S7-400, M7-400 Supplement to Manual 1 Connecting the Central Rack (CR) and the Expansion Rack (ER) EXTF LED on the IM 461-x On an expansion rack (ER) connected to a central rack (CR) via an IM 460-3/IM (remote link), the EXTF LED on the receiving IM lights up when the CR is switched off. ON an ER connected to a CR via an IM 460-0/IM or IM 460-1/IM (local link), the EXTF LED on the receive IM does not light up when the CR is switched off. Interference Suppression Measures To conform to the requirements of the EC Directive 89/336/EEC Electromagnetic Compatibility (CE mark), you should take the following measures when connecting central racks and expansion racks: Remote connection of expansion rack to a central rack with mounting rack UR via IM 460-0/IM 461-0: Attach a ferrule (split ferrite core) close to each connector on the IM cable A suitable split ferrite core is that of the type SFC 10 by Thora, Winn 6, D Herrieden, Germany Tel or a comparable product. Figure 1 shows an IM cable with a ferrule (split ferrite core). Ferrule (Split Ferrite Core) Figure 1 IM Cable with Ferrule (Split Ferrite Core) 4

5 Supplement to Manual S7-400, M Special Features of STEP 7 Programming with CPUs 41x Addressing Modules The start address of modules and components in either a central configuration or in a distributed configuration must be a value that can be divided by 4 with no remainder (0, 4, 8, 12...). Starting a Timer If there is an instruction for starting a timer programmed in the user program, there must be a BCD number at this point in the program sequence in accumulator 1. This also applies if the timer is not started. Setting a Counter If there is an instruction for setting a counter programmed in the user program, there must be a BCD number at this point in the program sequence in accumulator 1. This also applies if the counter is not set. SLD and SRD Instructions If parameters 64, 96, 128, 160, 192, or, 224 are transferred to the SRD or SLD instructions in accumulator 2-L-L with the CPUs 41x, status bit CC1 is set. RND- and RND + Instructions If a value in the range 0 to 0.25 is present as a floating-point number, the instruction RND+ supplies the result 0 instead of 1. If a value in the range 0 to is present as a floating-point number, the instruction RND- supplies the result 0 instead of -1. Writing Bit Instructions In the case of a fault, writing bit instructions report a read error instead of a write error. This applies to the following: Area length errors (entry in the diagnostic buffer made with event ID W#16#2522 instead of W#16#2523) Area errors (entry in the diagnostic buffer made with event ID W#16#2524 instead of W#16#2525) I/O access errors (entry in the diagnostic buffer made with event ID W#16#2944 instead of W#16#2945) Access to DP Slaves A DP station ist connected to an S7-400 via an external DP interface module CP Extended. If you use word access to access a DP slave with one byte of user data (instructions L PIW, T PQW), the I/O access error organization block (OB122) is not called. After executing the instruction L PIW, accumulator 1 contains B#16#00 instead of the non-existent peripheral byte. 5

6 S7-400, M7-400 Supplement to Manual If you use double word access to access a DP slave with three bytes of user data (instructions L PID, T PQD), the I/O access error organization block (OB122) is not called. After executing the instruction L PID, accumulator 1 contains B#16#00 instead of the non-existent peripheral byte. Single Step With the STEP 7 function single step mode, the CPU requires more time than the execution time for the instruction. As a result of the scan cycle time monitoring, it is possible that the CPU may go into STOP mode because the cycle time was exceeded. You can avoid this by calling the SFC43 RE_TRIGR in the time error organization block (OB80). Breakpoints SFC 11 SYNC/ FREEZE If you have set a breakpoint at a jump instruction or a block end instruction and the CPU has reached this instruction, neither the function execute next statement nor the function execute call can be executed. Instead the error message D063: Resource error: the trigger event is occupied is displayed. If you have set a breakpoint at a UC or CC instruction and the CPU has reached this instruction, the function execute call cannot be executed. Instead the error message D063: Resource error: the trigger event is occupied is displayed. Remedy: Delete the current breakpoint or move it to the previous command line. SFC11 cannot be called in the startup OBs (OB100, OB101). A call in these OBs is rejected with the RET_VAL identifier 0x80C8. In the other priority classes, you can use SFC11 without restrictions. You can use SFC11 only for the plug in DP modules (CP extended, IM 467). SFC11 cannot be used for the integrated DP interfaces. ET 200M stations assigned to sync/freeze groups with STEP 7 during hardware configuration must not contain FM or CP modules. 6

7 Supplement to Manual S7-400, M Special Features of Communication Communication from PG/OP to Module without MPI If one of the programming devices or operator panels connected to a multipoint interface (MPI) communicates with an S7-400 module which does not have an MPI connection (for example, SINEC CPs, FM 456 etc.), this module can be reached via the CPU to whose MPI the programming device or operator panel is connected. In this case, the CPU simply acts as an intermediary for the transfer. This type of connection between a programming device or operator panel and a module only communicating via the communication bus occupies two connection resources in the CPU. CPU CP or FM PG or OP MPI C bus S7-400 station One connection resource occupied Two connection resources occupied in the CPU One connection resource occupied Figure 2 Communication between Programming Device/Operator Panel and a Module without MPI Maximum Number of Connections via MPI When configuring the connections of a CPU 416 via MPI, remember to include the PG connection in the maximum number of possible connections. 7

8 S7-400, M7-400 Supplement to Manual PG Access A CPU exchanges data with other systems using communication mechanisms, for example with other programmable controllers, with operator interface stations (OP, OS) or with programming devices (see Figure 3). PG OS PLC SIMATIC NET CPU MPI DP network PG OS PLC PG OS Slave Figure 3 Data Exchange Process communication, including communication services for data exchange between programmable controllers (PLC PLC) and between programmable controllers and operator interface stations (PLC OS/OP), has priority in CPUs over communication between programming devices and CPUs. The CPUs have different characteristics. One of these characteristics is their communication performance. If the communication resources of a CPU are occupied completely by process communication, this can severely hamper access to the CPU from the programming device. This can often be avoided by a slight reduction in process communication. The following table shows several examples of this. The values relate to a user data length of 200 bytes. Communication Mechanism PLC PLC communication with USEND/URCV PLC PLC communication with BSEND/BRCV PLC PLC communication with AGSEND/RCV * PLC-OP communication (single jobs) Max. No. of Frames CPU 412, CPU 413 CPU 414, CPU 416 Max. No. of Frames with Reliable PG Access Max. No. of Frames 140 / s 130 / s 150 / s 140 / s 100 / s 90 / s 100 / s 90 / s 70 / s 65 / s 70 / s 65 / s 65 / s 60 / s 60 / s 80 / s Maximum No. of Frames with Reliable PG Access * It is advisable to set a minimum scan cycle time of 10 ms or to locate the calls in a cyclic interrupt priority class. The number of frames per line reflects the performance of the CPU. 8

9 Supplement to Manual S7-400, M Behavior of S7-400 Signal Modules After Parameter Assignment Parameter Assignment of S7-400 Signal Modules S7-400 signal modules can be assigned parameters by the operating system of the CPU or by calling an SFC in your program. Parameters are assigned by the operating system of the CPU in the following cases: At startup (both complete restart and restart) After plugging a module into a configured slot After the return of a rack or station when using distributed I/Os S7-400 Input Modules After assigning parameters to an S7-400 input module, the data read by your program from the module are not immediately valid. You can only evaluate these when bit 2 ( operating status ) in byte 2 of diagnostic data record 0 has the value 0 ( RUN ). For this reason, all S7-400 input modules which can be assigned parameters provide diagnostic data record 0. You can read out diagnostic data record 0 with SFC51 RDSYSST (input parameter SZL_ID W#16#00B1) or with SFC59 RD_REC. S7-400 Output Modules After assigning parameters to an S7-400 output module, it is possible that the output data you have written to the module is not transferred immediately to the outputs. From the time that bit 2 ( operating status ) in byte 2 of diagnostic data record 0 is set to the value 0 ( RUN ), the module transfers the output data to the output terminals. For this reason, diagnostic data record 0 is provided by all S7-400 output modules which can be assigned parameters. You can read out diagnostic data record 0 with SFC51 RDSYSST (input parameter SZL_ID W#16#00B1) or with SFC59 RD_REC. 9

10 S7-400, M7-400 Supplement to Manual 5 PROFIBUS DP Master Interface IM 467 Order Number 6ES GJ00-0AB0 Use PROFIBUS DP, standardized according to EN 50170, allows fast communication in the field area between programmable logic controllers, PCs, and field devices. Field devices include distributed I/O devices (ET 200), drives, valve islands, switching devices, and many others. The IM 467 interface module is intended for use in an S7-400 programmable logic control system. It enables you to connect an S7-400 to PROFIBUS DP. Design Configuration according to the rules for an S pin sub-d female connector for attachment to PROFIBUS DP Can be operated without a fan A maximum of four IM 467 modules can be used in the central rack. No slot rules apply A total of four IM 467 and CP Extended modules can be used together Various transmission rates between 9.6 Kbps and 12 Mbps can be set in the software Configuration and programming are possible via PROFIBUS DP although- PROFIBUS parameters must not be changed! 10

11 Supplement to Manual S7-400, M7-400 LED displays Mode switch PROFIBUS DP interface 9-pin sub-d Figure 4 Configuration of the IM 467 Communication Services The IM 467 provides you with two possible means of communication: PROFIBUS DP The IM 467 is a PROFIBUS DP master which conforms to EN It is configured completely with STEP 7. In principle, its behavior is the same as that of the the integrated PROFIBUS DP interfaces on the CPU modules (for differences, refer to the technical data of the IM 467). No function calls are necessary in the STEP 7 user program for DP communication. S7 functions S7 functions ensure optimum, simple communication in a SIMATIC S7/M7/C7 automation system. For IM 467, the following S7 functions are used: Programming device functions via PROFIBUS DP Operator monitoring and control functions via PROFIBUS DP Communication requires no further configuration on the IM 467. The S7 functions can be used alone or parallel to the PROFIBUS DP protocol. If they are used parallel to DP communication, this will affect the PROFIBUS DP round-trip time. 11

12 S7-400, M7-400 Supplement to Manual Configuration The IM 467 is configured with STEP 7. The configuration data is also retained during power down without a submodule being necessary. With the S7 functions, all IM 467 modules atached to the network and all CPUs connected via the SIMATIC S7 400 backplane bus can be programmed/configured remotely. Technical Data The technical data of the IM 467 are listed below. Dimensions and Weight Dimensions WxHxD 25 x 290 x 210 mm (1.0 x 11.4 x 8.3 in.) Weight 700 g (28 oz) Ambient Conditions Ambient temperature Operation 0 to 60 C Transport and storage 40 to +70 C 3000 m above sea level Operating altitude PROFIBUS DP Standard PROFIBUS, EN Transmission rate 9.6 Kbps to 12 Mbps, Transmission method can be set to various rates RS 485 Ports 9-pin Sub-D female For use with Power supply Current consumption from 5 VDC Addressing volume Number of connectable I/Os (slaves) Number of connections for S7 functions for programming devices and operator interface devices Data volume per slave Consistency Configuration software Conditions for Use SIMATIC S7-400, max. 4 IM 467 in the central rack 5 V DC via the backplane bus 1.2 A max. 4 Kbytes for inputs and 4 Kbytes for outputs diagnostic connection max. 240 bytes max. 128 bytes STEP 7 Differences compared with the DP intercface integrated in the CPU Different system status list IDs for system diagnostics Extended SFC operating times (in some cases) Additional return codes for SFC14 and SFC15 Cable Lengths with PROFIBUS DP Transmission rate in Kbps Max. length of a bus segment in m Max number of bus segments 1) Max. length in m ) Bus segments are interconnected by an RS 485 repeater 12