STEP 7 中的错误代码(xxxx：yyyy)是什么意思？_engl

STEP 7 Error Codes Version 07/2007 Error number: Text: Cause: Remedy: 1:2063 TBI error 2063 Error during the function chdir TBI can occur with the call AUTgetlinkedObjects. There should be an AUT API tracer in the meantime. 7:6160 CPUs can only be connected via K bus or MPI bus (line 1) Split the desired path of the global data into several circuits. Make sure that you only use on bus per circuit. 11:103 Cannot read CPU information on module, such as rated type, actual type and status of the module. Module might not be configured. Check the logical address of the module. Check the slot and the configured slot. 13:31 The online connection from the PG to the module (SDB addressee) could not be set up. Connection hardware is faulty (e.g. connection cable removed). Clear the fault in the connection to the module (SDB addressee) and you can then repeat the attempt to set up the connection in this dialog. The online connection from the PG to the module (SDB addressee) could not be set up. The module (SDB addressee) is in the wrong operating mode. Change the operating mode of the module (SDB addressee) and you can then repeat the attempt to set up the connection in this dialog. The online connection from the PG to the module (SDB addressee) could not be set up. You have specified an incorrect MPI address with STEP 7. If you have specified an incorrect MPI address, then: 1. Acknowledge this dialog 2. Correct the MPI address with STEP 7 3. Restart the "Load" function 13:32 There is a problem with the connection to the receiver of the HW configuration The online connection from the PG to the module (SDB addressee) could not be set up. The module recognized an error with the next communications call. Clear the fault in the connection, change the operating mode of the module or clear the storage bottleneck on the module and then you can repeat the attempt to set up the connection in this dialog. Connection hardware is faulty (e.g. connection cable removed) Plug the cable in. Module is in the wrong operating mode Check the operating mode. Storage bottleneck on the module Inconsistent HW configuration in the PG If the HW configuration is inconsistent in the PG, then: 1. Acknowledge this dialog 2. Correct the HW configuration in the configuration table 3. Restart the "Load" function When loading the system data on to the memory card, this message is displayed if there are invalid SDBs in the SDB folder. Delete the system data in the SIMATIC Manager and then restart the HW Config. 13:48 Internal error 0400 Station cannot be generated. The station cannot be created in the selected project because ... The project directory is write-protected Remove the write-protection for the project directory The project directory is on a network drive and the connection cannot be set up Set up the connection to the network drive No more storage capacity on the target drive Delete any data no longer needed on the target drive Page 1 / 37 STEP 7 Error Codes Version 07/2007 Error number: Text: Cause: Remedy: 13:76 Inconsistent hardware configuration in the programming device. Inconsistent HW configuration in the PG In HW Config analyze the HW configuration via the menu "Station\Check consistency". Folder "...\SIEMENS\STEP7\S7TMP" is missing or write-protected Missing authorization or an options package that generates the SDBs for a specific module. "Error in generating the system data" when downloading or saving a station in HW Config The environment tag S7TMP is not set. The path c:\\SDBDATA\s7hwcnfk\down\r00s02\sdb0.dat is completely or partly invalid Check that the paths in your Autoexec.bat are set as follows: SET PATH="C:\SIEMENS\COMMON\SQLANY" SET SQLANY=C:\SIEMENS\Common\sqlany SET S7TMP=C:\SIEMENS\STEP7\S7TMP 13:77 While interpreting the system data blocks (SDBs) uploaded from the module, an error was recognized in the programming device and processing halted. Inconsistent HW configuration in module, occurs when previous loading of SDBs into the module was incomplete or faulty. Options package for configuring specific modules (e.g. CPs) is not installed 13:136 The maximum possible number of slots within all inserted slaves has been exceeded by %1 slot(s)." More slaves have been configured than permitted by the master system Split the slaves across different segments if possible or reduce the number of slaves for the master system concerned. 13:181 Internal error:Multicomputig cannot have the type "inhomogenous" Error in HW Config of first 4.02.x version Add another CPU and then deleted it. The CPU is then automatically set to single-computing again 13:422 No master system is assigned to the DP slave. Missing object Right-click for pop-up menu, select "Add master system" and then configure the CP again as slave 13:520 The address entered is already occupied. STEP 7 has already calculated the next free address. Confirm the address suggested by STEP 7 or enter a new address. 13:4003 Module cannot be inserted here. You can use only DP slaves in a master system. An attempt was made to connect a device directly to the DP bus, which does not have its own interface. In the HW catalog insert a hierarchy level for this device as DP slave 13:4040 The number of slots of the CPU or the master system has been exceeded or exhausted. Maximum number of modules already configured. New modules can only be slotted after deleting slaves or their modules. 13:4241 The offline configuration (%2) differs from the hardware configuration of the PLC (%3). Do you still want to continue? An external module (interbus interfacing) from the Phoenix company was slotted Remove external module (error can be ignored) 13:4337 Unable to set up connection to module %1 (R%3!d!/S%4!d!). The online connection from the PG to the module (SDB addressee) could not be set up. Connection hardware is faulty. Make physical check of connections (cable break,...). Repeat attempt to set up connection. Module (SDB addressee) is in the wrong operating mode. Check operating mode. Repeat attempt to set up connection. Page 2 / 37 STEP 7 Error Codes Version 07/2007 Error number: Text: Cause: Remedy: You have specified an incorrect MPI address in the dialog box when loading to a PLC. If you have specified an incorrect MPI address in the dialog box, then proceed as follows: 1. Acknowledge this dialog 2. Correct the MPI address and trigger the Load function again. PG/PC with PROFIBUS interface is connected directly with an intelligent DP slave (e.g. ET 200X BM147/CPU) and the PG/PC interface is set incorrectly. Proceed as follows if the PG/PC interface is set incorrectly: 1. Navigate from the Windows Start bar (Start button) to SIMATIC > Step7 > Set PG-PC interface. 2. In the Access Path tab mark the PROFIBUS CP and click the Properties button. 3. In the Station Parameters group, deactivate the check box "Do not activate as only master". 13:4343 An update is presently not possible. In one or more STEP 7 applications at least one GSE file or type file is being referenced. In the different S7 applications there are objects (stations) open in which DP slaves are used. Thus it is no longer possible to install new GSD or type files, or even to update them. Please close the station window in the hardware configuration and all other STEP7 applications (such as NETPRO, for example) that could access the GSD file . The Hardware Configuration application remains open however without content. Then you can install the GSD file. 13:4341 The GSE file (type file) %1 contains syntax errors. For this reason it cannot be interpreted. STEP7 V5 + SP3 does a strict check of the GSD files. Some are not accepted, e.g. when the name is longer than 23 characters Create a backup copy of the GSD files; open file (e.g. with Wordpad) and edit excerpt from the file Vendor_Name = "1234567890123456789012345678901234567890Machine Factory". The name is longer than the max. 23 characters permitted. Correct to: Vendor_Name = " xxxxx Machine Factory". Save the file and re- incorporate it. 13:4366 Error during complete restart of the module. An error has occurred when attempting to start the module (restart). Possibly not all the CPUs of the multicomputing station have been started. Start the module or all the modules of the multicomputing station from the SIMATIC Manager via PLC and Operating Status. An error has occurred when attempting to start the module (restart). The key switch of the CPU/FM is in the STOP position Set the key switch of the CPU/FM to RUN or RUN-P. An error has occurred when attempting to start the module (restart). The operating mode switch of the CP is in the STOP position Set the operating mode switch of the CP to RUN. 13:4589 Details: (D221); cannot load SDB 7XX". H connections are configured in your project. The configuration of high-availability S7 connections has changed in STEP 7 V5.1. There are individual old configurations whose system data after a change can no longer be assigned to the latest configured high-availability S7 connections. This then leads to abortion of the download. In the SIMATIC Manager delete the "System Data" folder in "CPU > S7 program > Blocks". Then regenerate the system data in "NetPro". 15:20533 The maximal length of debug info (max. 64 Kbyte) is reached. The maximal length of debug info of 64 Kbyte is dependent of the system and can not be added. The debug info will be increased very fast if there is a lot of accesses to data blocks. We recommend in refer to the debug info to reduce the access of only few data blocks. Page 3 / 37 STEP 7 Error Codes Version 07/2007 Error number: Text: Cause: Remedy: 16:5016 Parameter can not be controlled You are trying to control an operand whose address is outside the permitted range of the controlling CPU. Comment out the relevant line in the VAT. You are trying to control an operand outside the process image for which there is no module available. It is possible to control of the operand inside the process image even if no module is slotted for the operand. The data block (DB) that is to be controlled is not in the CPU to be controlled. The data block (DB) is write-protected. Load the DB into the relevant CPU. The data block (DB) is write-protected. You have no write access to this DB. You must disable the READ- ONLY attribute for this DB to have write access to it. You are trying to control a periphery input (PI). Direct write access to an input module is not permitted. With the function "Release PQ" you can only control peripheral outputs (PQ). Direct write access to an input module is not permitted. 16:5053 In "Process Mode" it is not permitted to control or monitor I/Os. Consider whether you achieve the desired result by monitoring the process image. Otherwise parameterize the CPU for Test Mode (Configure Hardware / "CPU Properties" dialog box / "Protection" tab). 30:13 The interface of a called block has been changed. This means that the parameters are not transferred properly to the changed block. The block call is expanded and then displayed marked as faulty. STEP 7 up to V4.02.x: In the case of expanded block calls you delete the complete call sequence (all statements between the limiting PICTURE commands, including the red CALL / END_CALL lines) and then re-enter the CALL. STEP 7 V5.x and higher: In the case of incorrectly marked block calls you position the cursor in the CALL line and select the menu Edit>Block Call>Update. This adapts the block call to the new interface. Then check the new assignment of parameters. 30:15 The type object has a different time stamp to the opened block. The local symbols are displayed as pseudosymbols. Blocks have been opened either by available users or the blocks have been copied with the SIMATIC Manager from the CPU into the OFFLINE database. However, since the CPU knows no symbols, the variable names are replaced by default names. 30:50 Error while generating the STL source. The STL source cannot be generated, e.g. because it exists already and is write-protected, or because there is no more memory available on the drive. Generate a source with a new name or make sure that there is enough memory available for the source to be generated. Page 4 / 37 STEP 7 Error Codes Version 07/2007 Error number: Text: Cause: Remedy: 30:484 The displayed block cannot be monitored because it does not match the block in the CPU. Do you want to download the displayed block to the CPU and then monitor it? This is found to be caused by a discrepancy in the time stamps between the online block and the offline block and means that the blocks are different. Since the online information relating to the block sequence cannot be assigned to the individual program elements of the offline block, the block status cannot be displayed. The programs which are generated with CFC must be downloaded from the CFC to the PLC because only this loading function guarantees that the configuration data will be consistent with the PLC data. The same loading function is also used if you compile and load the "PLC > Objects" menu command in the SIMATIC Manager or highlight the chart folder and select the "PLC > Load" function. You may not, however, highlight the block folder or individual blocks and PLC > Load, as well as copy the blocks in the "Block folder offline" in order to insert them into the "Block folder online". 30:504 There are no parameter and local variable names available because there is a time stamp conflict between the interface of the block and the description of the parameter and local variable names. The description of the parameter and local variable names has a different time stamp to the interface of the opened block. This is why the parameters and local variables are displayed as pseudosymbols without comments. This conflict first arises when you open a block and interface changes made online have not been stored in the S7 user program offline and now the online block is being opened. Interface changes made offline have not been loaded into the CPU and now the online block is being opened. The interface of a function block or UDT has been changed and now the associated instance data block or the data block derived from the UDT is being opened. An online block that already has a time stamp conflict is copied offline into the S7 user program and now the offline block is being opened. The cause for this can be an actual hardware fault, or an interrupt conflict with another module. In this case the customer can check whether the MPI LED lights on the CP5611 during this time. - If the LED does not light, the module could be defective or there is an address conflict on the PCI bus (though unlikely). - If the LED lights, then there is an interrupt conflict. - NT Diagnostics ->Resources. - Warning: with some modules you have to switch the computer off/on after BIOS changes. A possible remedy could also be to plug the CP5611 into a different PCI slot. 30:53 Problems occurred during the automatic generation of STL sources. See Details! There are protected blocks in the selection list of the STL source to be generated. Remake the selection list, but without the protected blocks. Press the Details button in the error message to obtain a Detailed List of the protected blocks. 30:202 The test that "strikes" should check whether the block is there online and offline. Save the project under a different name. 30:473 This operation is not possible in this position. Programming error. Correct the code. 30:503 The type object of the block is not available, so the variable description is missing. The local symbols are displayed as pseudosymbols. User error. Page 5 / 37 STEP 7 Error Codes Version 07/2007 Error number: Text: Cause: Remedy: The block is available online in the automation system, but not offline in the S7 user program. The block has been copied from the automation system into an S7 user program and now this S7 user program is to be opened where it did not exist before. A block is opened via "Available Users". In this case there is no S7 user program linked with the automation system. The associated function block of an instance data block to be opened does not exist. 32:282 PG Resourcen Error, by program status of a longer FB in PLCSIM In Step7 V5.0 SP2 with PLCSIM V4.0 under NT, project and block were opened online. This probably led to high internal use of resources. In Step7 V5.0 SP2 with PLCSIM V4.0 do not open the project online, but select the status function from the offline project. Setting the virtual memory to 256MB does not help 33:11 33:384 The triggered action cannot be executed at this time. Check all other STEP 7 applications and exit them where necessary. The communications module is probably already being operated with other settings (e.g. with a different transmission rate). Please check the baud rate on the PG/PC via "Set PG/PC interface" and the baud rate of the CPU configured. There might be other online functions active. Close any other active online functions (e.g. by closing the relevant windows) and try again. Attempt to run the firmware update of a CPU directly via STEP 7 on a CPU. Firmware update is only possible via flash card. 33:496 The called function is not available in S7-DOS or in the CPU. Deinstallation and reinstallation of STEP7 33:498 Internal error: Function '%1' not implemented. Delete metafiles 33:501 System error! Attempt to get online as normal user under WinNT. 33:511 System error! Mixed installation Manual deinstallation of STEP 7 and S7 options packages NT: insufficient access rights. You must have at least main user access rights! NT: main user access rights already assigned! Check that the domain user with the main user rights has also been transferred into the Main User group on the local computer. EPROM: Memory card is missing Page 6 / 37 STEP 7 Error Codes Version 07/2007 Error number: Text: Cause: Remedy: The CP 1413 occupies the memory area 000D 0000 to 000D FFFF (complete D segment) or 000E 0000 to 000E FFFF (complete E segment). Normally MPI boards also use address areas in the D segment (from 000D C000) meaning they interfere with communication with the CP 1413. Can occur if the new connection to the database is not set up; for example when closing and opening available users, S7db_close and open is executed. Sometimes these do not match the current connection. With laptops, disable the power-save mode. Under WinNT check the user rights (only with Administrator rights in V3.x). Bus monitor Amprolyzer has been installed. Manual deinstallation of STEP 7 and S7 options packages according to FAQ. 30:527 The interface of the multi instance call can only be updated, if the declaration of the multi instance is valid in the tag declaration table. If you click "Yes" in the dialog box, the system corrects the corresponding entry in the detailed variable view for you. In case it is impossible to acknowledge the dialog box with "Yes" and, hence to have the corresponding entry corrected by the system in the tag detail view, verify the system da