Siemens G120C Drive Fault Codes:
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| F01003 Acknowledgment delay when accessing the memory | Cause: A memory area was accessed that does not return a “READY”. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| N01004 (F, A) Internal software error | Cause: An internal software error has occurred. Fault value (r0949, hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01005 File upload/download error | Cause: The upload or download of EEPROM data was unsuccessful. Fault value (r0949, interpret hexadecimal): yyxxxx hex: yy = component number, xxxx = fault cause xxxx = 000B hex = 11 dec: Power unit component has detected a checksum error. Remedy:
|
| A01009 (N) CU: Control module overtemperature | Cause: The temperature on the control module (Control Unit) has exceeded the specified temperature limit value. Remedy:
Note: The alarm is automatically withdrawn once the limit value has been fallen below. |
| F01010 Drive type unknown | Cause: An unknown drive type was found. Remedy:
|
| F01015 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy:
|
| A01016 (F) Firmware changed | Cause: At least one firmware file in the directory was illegally changed on the non-volatile memory (memory card/device memory) with respect to the version when shipped from the factory. Alarm value (r2124, interpret decimal): 0: Checksum of one file is incorrect. 1: File missing. 2: Too many files. 3: Incorrect firmware version. 4: Incorrect checksum of the back-up file. Remedy:
Note: The file involved can be read out using parameter r9925. The status of the firmware check is displayed using r9926. |
| A01017 Component lists changed | Cause: On the memory card, one file in the directory /SIEMENS/SINAMICS/DATA or /ADDON/SINAMICS/DATA has been illegally changed with respect to that supplied from the factory. No changes are permitted in this directory. Alarm value (r2124, interpret decimal): zyx dec: x = Problem, y = Directory, z = File name Remedy: For the file on the memory card involved, restore the status originally supplied from the factory. |
| F01018 Booting has been interrupted several times | Cause: Module booting was interrupted several times. As a consequence, the module boots with the factory setting. Possible reasons for booting being interrupted:
Remedy:
|
| A01019 Writing to the removable data medium unsuccessful | Cause: The write access to the removable data medium was unsuccessful. Remedy:
|
| A01020 Writing to RAM disk unsuccessful | Cause: A write access to the internal RAM disk was unsuccessful. Remedy: Adapt the file size for the system logbook to the internal RAM disk (p9930). |
| A01021 Removable data medium as USB data storage medium from the PC used | Cause: The removable data medium is used as USB data storage medium from a PC. As a consequence, the drive cannot access the removable data medium. When backing up, the configuration data cannot be saved on the removable data medium. Remedy: Deactivate the USB connection to the PC and back up the configuration data. |
| F01023 Software timeout (internal) | Cause: An internal software timeout has occurred. Remedy:
|
| A01028 (F) Configuration error | Cause: The parameterization that was downloaded was generated with a different module type (Order No., MLFB). Remedy: Save parameters in a non-volatile fashion (p0971 = 1). |
| F01030 Sign-of-life failure for master control | Cause: For active PC master control, no sign-of-life was received within the monitoring time. Remedy: Set the monitoring time higher at the PC or, if required, completely disable the monitoring function. |
| F01033 Units changeover: Reference parameter value invalid | Cause: When changing over the units to the referred representation type, it is not permissible for any of the required reference parameters to be equal to 0.0 Remedy: Set the value of the reference parameter to a number different than 0.0. |
| F01034 Units changeover: Calculation parameter values after reference value change unsuccessful | Cause: The change of a reference parameter meant that for an involved parameter the selected value was not able to be re-calculated in the per unit representation. The change was rejected and the original parameter value restored. Remedy: Select the value of the reference parameter such that the parameter involved can be calculated in the per unit representation. |
| A01035 (F) ACX: Parameter back-up file corrupted | Cause: When the Control Unit is booted, no complete data set was found from the parameter back-up files. The last time that the parameterization was saved, it was not completely carried out. Remedy:
|
| F01036 (A) ACX: Parameter back-up file missing | Cause: When downloading the device parameterization, a parameter back-up file PSxxxyyy.ACX associated with a drive object cannot be found. Remedy: If you have saved the project data using the commissioning software, carry out a new download for your project. Save using the function “Copy RAM to ROM” or with p0971 = 1. |
| F01038 (A) ACX: Loading the parameter back-up file unsuccessful | Cause: An error has occurred when downloading PSxxxyyy.ACX or PTxxxyyy.ACX files from the non-volatile memory. Remedy: If you have saved the project data using the commissioning software, download the project again. Save using the function “Copy RAM to ROM” or with p0971 = 1. |
| F01039 (A) ACX: Writing to the parameter back-up file was unsuccessful | Cause: Writing to at least one parameter back-up file PSxxxyyy.*** in the non-volatile memory was unsuccessful. Remedy:
|
| F01040 Save parameter settings and carry out a POWER ON | Cause: A parameter has been changed that requires the parameters to be backed up and the Control Unit to be switched OFF and ON again. Remedy:
|
| F01042 Parameter error during project download | Cause: An error was detected when downloading a project using the commissioning software (e.g. incorrect parameter value). Remedy:
|
| F01043 Fatal error at project download | Cause: A fatal error was detected when downloading a project using the commissioning software. Remedy:
|
| F01044 CU: Descriptive data error | Cause: An error was detected when loading the descriptive data saved in the non-volatile memory. Remedy: Replace the memory card or Control Unit. |
| A01045 Configuring data invalid | Cause: An error was detected when evaluating the parameter files saved in the non-volatile memory. Remedy:
|
| A01049 It is not possible to write to file | Cause: It is not possible to write into a write-protected file. Remedy: Check whether the “write protected” attribute has been set for the files and remove it if required. |
| F01054 CU: System limit exceeded | Cause: At least one system overload has been identified. Remedy: Reduce the computing time load of the drive unit. |
| A01064 (F) CU: Internal error (CRC) | Cause: A checksum error (CRC error) has occurred in the Control Unit program memory. Remedy:
|
| A01066 Buffer memory: 70% fill level reached or exceeded | Cause: The non-volatile buffer memory for parameter changes is filled to at least 70%. Remedy: If required, deactivate and clear the buffer memory. |
| A01067 Buffer memory: 100 % fill level reached | Cause: The non-volatile buffer memory for parameter changes is filled to 100%. Remedy: If required, deactivate and clear the buffer memory. |
| F01068 CU: Data memory memory overflow | Cause: The utilization for a data memory area is too large. Remedy:
|
| A01069 Parameter backup and device incompatible | Cause: The parameter backup on the memory card and the drive unit do not match. Remedy:
|
| F01072 Memory card restored from the backup copy | Cause: The Control Unit was switched-off while writing to the memory card. Remedy: Check that the firmware and parameterization is up-to-date. |
| A01073 (N) POWER ON required for backup copy on memory card | Cause: The parameter assignment on the visible partition of the memory card has changed. Remedy:
|
| N01101 (A) CU: memory card not available | Cause: The memory card is not available for the drive. Remedy:
|
| F01105 (A) CU: Insufficient memory | Cause: Too many data sets are configured on this Control Unit. Remedy: Reduce the number of data sets. |
| F01107 Save to memory card unsuccessful | Cause: A data save to the memory card was not able to be successfully carried out. Remedy:
|
| F01112 CU: Power unit not permissible | Cause: The connected power unit cannot be used together with this Control Unit. Remedy: Replace the power unit that is not permissible by a component that is permissible. |
| F01120 (A) Terminal initialization has failed | Cause: An internal software error occurred while the terminal functions were being initialized. Remedy:
|
| F01122 (A) Frequency at the measuring probe input too high | Cause: The frequency of the pulses at the measuring probe input is too high. Remedy: Reduce the frequency of the pulses at the measuring probe input. |
| F01152 CU: Invalid constellation of drive object types | Cause: It is not possible to simultaneously operate drive object types SERVO, VECTOR and HLA. Remedy:
|
| F01205 CU: Time slice overflow | Cause: Insufficient computation time. Remedy: Contact Technical Support. |
| F01250 CU: CU-EEPROM incorrect read-only data | Cause: Error when reading the read-only data of the EEPROM in the Control Unit. Remedy:
|
| A01251 CU: CU-EEPROM incorrect read-write data | Cause: Error when reading the read-write data of the EEPROM in the Control Unit. Remedy:
|
| F01257 CU: Firmware version out of date | Cause: The Control Unit firmware is too old. Remedy:
|
| F01340 Topology: Too many components on one line | Cause: For the selected communications clock cycle, too many DRIVE-CLiQ components are connected to one line of the Control Unit. Remedy:
|
| F01505 (A) BICO: Interconnection cannot be established | Cause: A PROFIdrive telegram has been set (p0922). An interconnection contained in the telegram was not able to be established. Remedy: Establish another interconnection. |
| F01510 BICO: Signal source is not float type | Cause: The requested connector output does not have the correct data type. Remedy: Interconnect this connector input with a connector output having a float data type. |
| F01511 (A) BICO: Interconnection with different scalings | Cause: The requested BICO interconnection was established. However, a conversion is made between the BICO output and BICO input using the reference values. Remedy: Not necessary. |
| F01512 BICO: No scaling available | Cause: An attempt was made to determine a conversion factor for a scaling that does not exist. Remedy: Apply scaling or check the transfer value. |
| F01513 (N, A) BICO: Interconnection cross DO with different scalings | Cause: An interconnection is made between different drive objects and the BICO output has different normalized units than the BICO input or the normalized units are the same but the reference values are different. Remedy: Not necessary. |
| A01514 (F) BICO: Error when writing during a reconnect | Cause: During a reconnect operation a parameter was not able to be written to. Remedy: Not necessary. |
| F01515 (A) BICO: Writing to parameter not permitted as the master control is active | Cause: When changing the number of CDS or when copying from CDS, the master control is active. Remedy: If required, return the master control and repeat the operation. |
| A01590 (F) Drive: Motor maintenance interval expired | Cause: The selected service/maintenance interval for this motor was reached. Remedy: Carry out service/maintenance and reset the service/maintenance interval. |
| F01600 SI P1 (CU): STOP A initiated | Cause: The drive-integrated “Safety Integrated” function on processor 1 has detected an error and initiated a STOP A. Remedy:
|
| F01611 (A) SI P1 (CU): Defect in a monitoring channel | Cause: The drive-integrated “Safety Integrated” function on processor 1 has detected a fault in the data cross-check between the two monitoring channels and has initiated a STOP F. Remedy: Check the cross data comparison that resulted in a STOP F. |
| N01620 (F, A) SI P1 (CU): Safe Torque Off active | Cause: The “Safe Torque Off” (STO) function has been selected on processor 1 using the input terminal and is active. Remedy: Not necessary. |
| F01625 SI P1 (CU): Sign-of-life error in safety data | Cause: The drive-integrated “Safety Integrated” function on processor 1 has detected an error in the sign-of-life of the safety data and initiated a STOP A. Remedy:
|
| F01640 SI P1 (CU): component replacement identified and acknowledgment/save required | Cause: The “Safety Integrated” function integrated in the drive has identified that a component has been replaced. It is no longer possible to operate the drive. Remedy:
|
| F01641 SI P1 (CU): component replacement identified and save required | Cause: The “Safety Integrated” function integrated in the drive has identified that a component has been replaced. No additional fault response is initiated, therefore operation of the particular drive is not restricted. Remedy:
|
| F01649 SI P1 (CU): Internal software error | Cause: An internal error in the Safety Integrated software on processor 1 has occurred. This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F01650 SI P1 (CU): Acceptance test required | Cause: The drive-integrated “Safety Integrated” function on processor 1 requires an acceptance test. This fault results in a STOP A that can be acknowledged. Remedy:
|
| F01651 SI P1 (CU): Synchronization safety time slices unsuccessful | Cause: The “Safety Integrated” function requires synchronization of the safety time slices between processor 1 and processor 2. This synchronization routine was unsuccessful. Remedy:
|
| F01653 SI P1 (CU): PROFIBUS/PROFINET configuration error | Cause: There is a PROFIBUS/PROFINET configuration error for using Safety Integrated monitoring functions with a higher-level control. For safety functions that have been enabled, this fault results in a STOP A that cannot be acknowledged. Remedy:
|
| A01654 (F) SI P1 (CU): Deviating PROFIsafe configuration | Cause: The configuration of a PROFIsafe telegram in the higher-level control (F-PLC) does not match the parameterization in the drive. Remedy:
|
| F01655 SI P1 (CU): Align monitoring functions | Cause: An error has occurred when aligning the Safety Integrated monitoring functions on processor 1 and processor 2. No common set of supported SI monitoring functions was able to be determined. Remedy:
|
| F01656 SI P1 (CU): Parameter processor 2 error | Cause: When accessing the Safety Integrated parameters for the processor 2 in the non-volatile memory, an error has occurred. Remedy:
|
| F01658 SI P1 (CU): PROFIsafe telegram number not suitable | Cause: The PROFIsafe telegram number in p60022 is unsuitable for the enabled safety functions. Remedy:
|
| F01659 SI P1 (CU): Write request for parameter rejected | Cause: The write request for one or several Safety Integrated parameters on processor 1 was rejected. Remedy:
|
| F01660 SI P1 (CU): Safety-related functions not supported | Cause: The Power Module does not support the safety-related functions. Safety Integrated cannot be commissioned. Remedy:
|
| F01662 Error internal communications | Cause: A module-internal communication error has occurred. Remedy:
|
| F01663 SI P1 (CU): Copying the SI parameters rejected | Cause: In p9700, the value 208 is saved or was entered offline. This is the reason that when booting, an attempt is made to copy Safety Integrated parameters from processor 1 to processor 2. However, no safety-relevant function has been selected on processor 1 (p9601 = 0). Remedy:
|
| F01665 SI P1 (CU): System is defective | Cause: A system defect was detected before the last boot or in the actual one. The system might have been rebooted (reset). Remedy:
|
| A01678 (F) SI: Test stop for STO via terminals required at the PM | Cause: The time (p9661) set to monitor the forced checking procedure (test stop) for the “STO via the terminals at the Power Module” function has been exceeded. A new forced checking procedure is required. Remedy:
|
| A01693 (F) SI P1 (CU): Safety parameter setting changed, POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a POWER ON. Remedy:
|
| A01698 (F) SI P1 (CU): Commissioning mode active | Cause: The commissioning of the “Safety Integrated” function is selected. Remedy:
|
| A01699 (F) SI P1 (CU): Test stop for STO required | Cause: The time set in p9659 for the forced checking procedure (test stop) for the “STO” function has been exceeded. A new forced checking procedure is required. Remedy:
|
| A01788 SI: Automatic test stop waits for STO deselection via motion monitoring functions | Cause: The automatic test stop (forced checking procedure) was not able to be carried out after powering up. Remedy:
|
| A01790 SI: Power up stopped due to STO via terminals | Cause: When powering up, the automatic internal self test of the Control Unit was not able to be completed as the pulses were not enabled. It is possible that the “STO via terminals at the Power Module” function is being used. Remedy:
|
| A01796 (F, N) SI P1 (CU): Wait for communication | Cause: The drive waits for communication to be established to execute the safety-relevant motion monitoring functions. Remedy:
|
| A01900 (F) PROFIBUS: Configuration telegram error | Cause: A PROFIBUS master attempts to establish a connection using an incorrect configuring telegram. Remedy:
|
| F01910 (N, A) Fieldbus interface setpoint timeout | Cause: The reception of setpoints from the fieldbus interface has been interrupted. Remedy:
|
| A01920 (F) PROFIBUS: Interruption cyclic connection | Cause: The cyclic connection to the PROFIBUS master is interrupted. Remedy:
|
| A01945 PROFIBUS: Connection to the Publisher failed | Cause: For PROFIBUS peer-to-peer data transfer, the connection to at least one Publisher has failed. Remedy:
|
| F01946 (A) PROFIBUS: Connection to the Publisher aborted | Cause: The connection to at least one Publisher for PROFIBUS peer-to-peer data transfer in cyclic operation has been aborted. Remedy:
|
| F01951 CU SYNC: Synchronization application clock cycle missing | Cause: Internal synchronization of the application cycles unsuccessful. Remedy:
|
| A01953 CU SYNC: Synchronization not completed | Cause: After the drive system was switched on, synchronization between the basic clock cycle and application clock cycle was started but was not completed within the selected time tolerance. Remedy:
|
| A02050 Trace: Start not possible | Cause: The trace has already been started. Remedy:
|
| A02051 Trace: recording not possible as a result of know-how protection | Cause: TRACE recording is not possible as at least one signal or trigger signal being used is under know-how protection. Remedy:
|
| A02055 Trace: Recording time too short | Cause: The trace duration is too short. Remedy:
|
| A02056 Trace: Recording cycle too short | Cause: The selected recording clock cycle is lower than the basic clock cycle 500µs. Remedy:
|
| A02057 Trace: Time slice clock cycle invalid | Cause: The time slice clock cycle selected does not match any of the existing time slices. Remedy:
|
| A02058 Trace: Time slice clock cycle for endless trace not valid | Cause: The selected time slice clock cycle cannot be used for the endless trace. Remedy:
|
| A02059 Trace: Time slice clock cycle for 2 x 8 recording channels not valid | Cause: The selected time slice clock cycle cannot be used for more than 4 recording channels. Remedy:
|
| A02060 Trace: Signal to be traced missing | Cause: A signal to be traced was not specified. Remedy:
|
| A02061 Trace: Invalid signal | Cause: The specified signal does not exist. Remedy:
|
| A02062 Trace: Invalid trigger signal | Cause: A trigger signal was not specified. Remedy:
|
| A02063 Trace: Invalid data type | Cause: The specified data type to select a signal using a physical address is invalid. Remedy:
|
| A02070 Trace: Parameter cannot be changed | Cause: The trace parameter settings cannot be changed when the trace is active. Remedy:
|
| A02075 Trace: Pretrigger time too long | Cause: The selected pretrigger time must be shorter than the trace time. Remedy:
|
| F02080 Trace: Parameterization deleted due to unit changeover | Cause: The trace parameterization in the drive unit was deleted due to a unit changeover or a change in the reference parameters. Remedy:
|
| A02095 MTrace 0: multiple trace cannot be activated | Cause: The following functions or settings are not permissible in conjunction with a multiple trace (trace recorder 0): measuring function, long-time trace, trigger condition “immediate recording start”, trigger condition “start with function generator”. Remedy:
|
| A02096 MTrace 0: cannot be saved | Cause: It is not possible to save the measurement results of a multiple trace on the memory card (trace recorder 0). A multiple trace is not started or is canceled. Remedy:
|
| A02097 MTrace 1: multiple trace cannot be activated | Cause: The following functions or settings are not permissible in conjunction with a multiple trace (trace recorder 1): measuring function, long-time trace, trigger condition “immediate recording start”, trigger condition “start with function generator”. Remedy:
|
| A02098 MTrace 1: cannot be saved | Cause: It is not possible to save the measurement results of a multiple trace on the memory card (trace recorder 1). A multiple trace is not started or is canceled. Remedy:
|
| A02099 Trace: Insufficient Control Unit memory | Cause: The memory space still available on the Control Unit is no longer sufficient for the trace function. Remedy:
|
| A02150 OA: Application cannot be loaded | Cause: The system was not able to load an OA application. Remedy:
|
| F02151 (A) OA: Internal software error | Cause: An internal software error has occurred within an OA application. Remedy:
|
| F02152 (A) OA: Insufficient memory | Cause: Too many functions have been configured on this Control Unit (e.g. too many drives, function modules, data sets, OA applications, blocks, etc.). Remedy:
|
| F03000 NVRAM fault on action | Cause: A fault occurred during execution of action p7770 = 1 or 2 for the NVRAM data. Remedy:
|
| F03001 NVRAM checksum incorrect | Cause: A checksum error occurred when evaluating the non-volatile data (NVRAM) on the Control Unit. The NVRAM data affected was deleted. Remedy:
|
| F03505 (N, A) Analog input wire breakage | Cause: The wire-break monitoring for an analog input has responded. The input value of the analog input has undershot the threshold value. Remedy:
|
| A03510 (F, N) Calibration data not plausible | Cause: During booting, the calibration data for the analog inputs is read and checked with respect to plausibility. At least one calibration data point was determined to be invalid. Remedy:
|
| A05000 (N) Power unit: Overtemperature heat sink AC inverter | Cause: The alarm threshold for overtemperature at the inverter heat sink has been reached. Remedy:
|
| A05001 (N) Power unit: Overtemperature depletion layer chip | Cause: Alarm threshold for overtemperature of the power semiconductor in the AC converter has been reached. Remedy:
|
| A05002 (N) Power unit: Air intake overtemperature | Cause: The alarm threshold for the air intake overtemperature has been reached. Remedy:
|
| A05004 (N) Power unit: Rectifier overtemperature | Cause: The alarm threshold for the overtemperature of the rectifier has been reached. Remedy:
|
| A05006 (N) Power unit: Overtemperature thermal model | Cause: The temperature difference between the chip and heat sink has exceeded the permissible limit value. Remedy:
|
| A05065 (F, N) Voltage measured values not plausible | Cause: The voltage measurement does not supply any plausible values and is not used. Remedy:
|
| F06310 (A) Supply voltage (p0210) incorrectly parameterized | Cause: The measured DC voltage lies outside the tolerance range after precharging has been completed. Remedy:
|
| A06921 (N) Braking resistor phase asymmetry | Cause: The three resistors of the braking chopper are not symmetrical. Remedy:
|
| F06922 Braking resistor phase failure | Cause: A phase failure for the brake resistor was detected. Remedy:
|
| F07011 Drive: Motor overtemperature | Cause: The motor temperature has exceeded the fault threshold (p0605). Possible causes: motor is overloaded, motor ambient temperature too high, wire breakage or sensor not connected. Remedy:
|
| A07012 (N) Drive: Motor temperature model 1/3 overtemperature | Cause: The motor temperature model 1/3 identified that the alarm threshold was exceeded. Remedy:
|
| A07014 (N) Drive: Motor temperature model configuration alarm | Cause: A fault has occurred in the configuration of the motor temperature model. Remedy:
|
| A07015 Drive: Motor temperature sensor alarm | Cause: An error was detected when evaluating the temperature sensor set in p0601. Possible causes: wire breakage or sensor not connected, measured resistance too low. Remedy:
|
| F07016 Drive: Motor temperature sensor fault | Cause: An error was detected when evaluating the temperature sensor set in p0601. Possible causes: wire breakage or sensor not connected, measured resistance too low. Remedy:
|
| F07080 Drive: Incorrect control parameter | Cause: The closed-loop control parameters have been parameterized incorrectly (e.g. p0356 = L_spread = 0). Remedy:
|
| F07082 Macro: Execution not possible | Cause: The macro cannot be executed. Fault causes can include an invalid file, incorrect data type, or writing to a read-only parameter. Remedy:
|
| F07083 Macro: ACX file not found | Cause: The ACX file (macro) to be executed was not able to be found in the appropriate directory. Remedy:
|
| F07084 Macro: Condition for WaitUntil not fulfilled | Cause: The WaitUntil condition set in the macro was not fulfilled in a certain number of attempts. Remedy:
|
| F07086 Units changeover: Parameter limit violation due to reference value change | Cause: A reference parameter was changed in the system. This resulted in the fact that for the parameters involved, the selected value was not able to be written in the per unit notation. Remedy:
|
| F07088 Units changeover: Parameter limit violation due to units changeover | Cause: A changeover of units was initiated. This resulted in a violation of a parameter limit. Remedy:
|
| A07089 Changing over units: Function module activation is blocked | Cause: An attempt was made to activate a function module. This is not permissible if the units have already been changed over. Remedy:
|
| A07092 Drive: moment of inertia estimator still not ready | Cause: The moment of inertia estimator still has no valid values. The acceleration cannot be calculated. Remedy:
|
| A07094 General parameter limit violation | Cause: As a result of the violation of a parameter limit, the parameter value was automatically corrected. Remedy:
|
| A07200 Drive: Master control ON command present | Cause: The ON/OFF1 command is present (no 0 signal). The command is influenced via binector input p0840 or control word bit 0. Remedy:
|
| F07220 (N, A) Drive: Master control by PLC missing | Cause: The “master control by PLC” signal was missing in operation. Remedy:
|
| F07300 (A) Drive: Line contactor feedback signal missing | Cause: The line contactor was not able to be closed/opened within the specified time, or it dropped out during operation. Remedy:
|
| F07320 Drive: Automatic restart interrupted | Cause: The specified number of restart attempts (p1211) has been completely used up because the faults were not able to be acknowledged within the monitoring time. Remedy:
|
| A07321 Drive: Automatic restart active | Cause: The automatic restart (AR) is active. When the line supply returns and/or faults are removed, the drive automatically restarts. Remedy:
|
| F07330 Flying restart: Measured search current too low | Cause: During a flying restart, it was identified that the search current reached is too low. It is possible that the motor is not connected. Remedy:
|
| F07331 Flying restart: Function not supported | Cause: It is not possible to power up with the motor rotating (no flying restart). In some cases, the “flying restart” function is not supported (e.g., PMSM with U/f control). Remedy:
|
| F07332 Flying restart: maximum speed reduced | Cause: The maximum speed that can be reached is reduced; at very high speeds problems associated with the flying restart can be encountered. Remedy:
|
| A07352 Drive: Limit switch signals not plausible | Cause: Limit switch signals are not plausible. Possible causes: BICO interconnections are not OK, or sensors are not supplying a valid signal. Remedy:
|
| A07400 (N) Drive: DC link voltage maximum controller active | Cause: The DC link voltage controller has been activated because the upper switch-in threshold has been exceeded. Remedy:
|
| A07401 (N) Drive: DC link voltage maximum controller deactivated | Cause: The Vdc_max controller can no longer maintain the DC link voltage below the limit and was therefore switched out. Remedy:
|
| A07402 (N) Drive: DC link voltage minimum controller active | Cause: The DC link voltage controller has been activated as the lower switch-in threshold has been undershot. The kinetic energy of the motor is used to buffer the DC link. Remedy:
|
| F07404 Drive: DC link voltage monitoring Vdc_max | Cause: The monitoring of the DC link voltage p1284 has responded (only U/f control). Remedy:
|
| F07405 (N, A) Drive: Kinetic buffering minimum speed fallen below | Cause: During kinetic buffering the speed fell below minimum speed and the line supply did not return. Remedy:
|
| F07406 (N, A) Drive: Kinetic buffering maximum time exceeded | Cause: The maximum buffer time has been exceeded without the line supply having returned. Remedy:
|
| A07409 (N) Drive: U/f control, current limiting controller active | Cause: The current limiting controller of the U/f control was activated because the current limit was exceeded. Remedy:
|
| F07410 Drive: Current controller output limited | Cause: The condition “I_act = 0 and Uq_set_1 longer than 16 ms at its limit” is present. This can be caused by the motor not being connected or the power unit being defective. Remedy:
|
| F07426 (A) Technology controller actual value limited | Cause: The actual value for the technology controller, interconnected via connector input p2264, has reached a limit. Remedy:
|
| A07428 (N) Technology controller parameterizing error | Cause: The technology controller has a parameterizing error (upper output limit is lower than the lower output limit). Remedy:
|
| F07435 (N) Drive: Setting the ramp-function generator for sensorless vector control | Cause: During operation with sensorless vector control, the ramp-function generator was stopped (p1141). Remedy:
|
| A07444 PID autotuning is activated | Cause: Automatic setting of the PID controller parameters (PID autotuning) was activated (p2350). Remedy:
|
| F07445 PID autotuning canceled | Cause: The PID autotuning was canceled as a result of an error. Remedy:
|
| A07530 Drive: Drive Data Set DDS not present | Cause: The selected drive data set is not available. The drive data set was not changed over. Remedy:
|
| A07531 Drive: Command Data Set CDS not present | Cause: The selected command data set is not available. The command data set was not changed over. Remedy:
|
| F07754 Drive: Incorrect shutoff valve configuration | Cause: An incorrect shutoff valve configuration was detected. Remedy:
|
| F07800 Drive: No power unit present | Cause: The power unit parameters cannot be read or no parameters are stored in the power unit. Remedy:
|
| F07801 Drive: Motor overcurrent | Cause: The permissible motor limit current was exceeded. Remedy:
|
| F07802 Drive: Infeed or power unit not ready | Cause: After an internal switch-on command, the infeed or drive does not signal ready. Remedy:
|
| A07805 (N) Drive: Power unit overload I2t | Cause: Alarm threshold for I2t overload of the power unit exceeded. Remedy:
|
| F07807 Drive: Short-circuit/ground fault detected | Cause: A phase-phase short-circuit or ground fault was detected at the motor-side output terminals of the converter. Remedy:
|
| F07810 Drive: Power unit EEPROM without rated data | Cause: No rated data are stored in the power unit EEPROM. Remedy:
|
| A07850 (F) External alarm 1 | Cause: The condition for “External alarm 1” is satisfied. Remedy:
|
| F07860 (A) External fault 1 | Cause: The condition for “External fault 1” is satisfied. Remedy:
|
| A07891 Drive: Load monitoring pump/fan blocked | Cause: The load monitoring is configured for a pump or fan and detects when it is blocked. Remedy:
|
| A07892 Drive: Load monitoring pump/fan no load condition | Cause: The load monitoring detects when the pump/fan is operating under no load conditions. Remedy:
|
| A07893 Drive: Load monitoring pump leakage | Cause: The monitoring function detects a leak in the pump circuit. Remedy:
|
| F07894 Drive: Load monitoring pump/fan blocked | Cause: The load monitoring is configured for a pump or fan and detects when it is blocked. Remedy:
|
| F07895 Drive: Load monitoring pump/fan no load condition | Cause: The monitoring function detects when the pump/fan is operating under no load conditions. Remedy:
|
| F07896 Drive: Load monitoring pump leakage | Cause: The monitoring function detects a leak in the pump circuit. Remedy:
|
| F07900 (N, A) Drive: Motor blocked | Cause: Motor has been operating at the torque limit at a low speed for a longer period of time. Remedy:
|
| F07901 Drive: Motor overspeed | Cause: The maximum permissible speed was either positively or negatively exceeded. Remedy:
|
| F07902 (N, A) Drive: Motor stalled | Cause: The system has identified that the motor has stalled for a time longer than is set. Remedy:
|
| A07910 (N) Drive: Motor overtemperature | Cause: The measured motor temperature or the temperature of the motor temperature model 2 has exceeded the alarm threshold (p0604). Remedy:
|
| A07927 DC braking active | Cause: The motor is braked with DC current. DC braking is active. Remedy:
|
| A07929 (F) Drive: No motor detected | Cause: The absolute current value is so small after enabling the inverter pulses that no motor is detected. Remedy:
|
| F07950 (A) Motor parameter incorrect | Cause: The motor parameters were incorrectly entered while commissioning (e.g. p0300 = 0, no motor). Remedy:
|
| A07960 Drive: Incorrect friction characteristic | Cause: The friction characteristic is incorrect. Remedy:
|
| A07961 Drive: Friction characteristic record activated | Cause: The automatic friction characteristic record is activated. The friction characteristic is recorded at the next switch-on command. Remedy:
|
| F07963 Drive: Friction characteristic record interrupted | Cause: The conditions to record the friction characteristic are not fulfilled. Remedy:
|
| F07967 Drive: Incorrect pole position identification | Cause: A fault has occurred during the pole position identification routine. Remedy:
|
| F07968 Drive: Lq-Ld measurement incorrect | Cause: A fault has occurred during the Lq-Ld measurement. Remedy:
|
| F07969 Drive: Incorrect pole position identification | Cause: A fault has occurred during the pole position identification routine. Remedy:
|
| A07980 Drive: Rotating measurement activated | Cause: The rotating measurement (automatic speed controller optimization) is activated. The measurement is carried out at the next switch-on command. Remedy:
|
| A07981 Drive: Enable signals for the rotating measurement missing | Cause: The rotating measurement cannot be started due to missing enable signals. Remedy:
|
| F07983 Drive: Rotating measurement saturation characteristic | Cause: A fault has occurred while determining the saturation characteristic. Remedy:
|
| F07984 Drive: Speed controller optimization, moment of inertia | Cause: A fault has occurred while identifying the moment of inertia. Remedy:
|
| F07985 Drive: Speed controller optimization (oscillation test) | Cause: A fault has occurred during the vibration test. Remedy:
|
| F07986 Drive: Rotating measurement ramp-function generator | Cause: During the rotating measurements, problems with the ramp-function generator occurred. The positive and negative directions are inhibited. Remedy:
|
| F07988 Drive: Rotating measurement, no configuration selected | Cause: When configuring the rotating measurement (p1959), no function was selected. Remedy:
|
| F07990 Drive: Incorrect motor data identification | Cause: A fault has occurred during the identification routine. This can be due to various reasons like current limit reached, incorrect motor connection, or ground fault. Remedy:
|
| A07991 (N) Drive: Motor data identification activated | Cause: The motor data identification routine is activated and will be carried out at the next switch-on command. Remedy:
|
| A07994 (F, N) Drive: motor data identification not performed | Cause: The “Vector control” mode has been selected, but a motor data identification has still not been performed. Remedy:
|
| F08010 (N, A) CU: Analog-to-digital converter | Cause: The analog-to-digital converter on the Control Unit has not supplied any converted data. Remedy:
|
| F08501 (N, A) PROFINET: Setpoint timeout | Cause: The reception of setpoints from PROFINET has been interrupted due to a bus connection interruption or the controller being switched off or in a STOP state. Remedy:
|
| F08502 (A) PROFINET: Monitoring time sign-of-life expired | Cause: The monitoring time for the sign-of-life counter has expired because the connection to the PROFINET interface was interrupted. Remedy:
|
| A08511 (F) PROFINET: Receive configuration data invalid | Cause: The drive unit did not accept the receive configuration data. This could be due to too many PZD data words or a PROFIsafe parameter error. Remedy:
|
| A08526 (F) PROFINET: No cyclic connection | Cause: There is no connection to a PROFINET controller. Remedy:
|
| A08564 PN/COMM BOARD: syntax error in the configuration file | Cause: A syntax error has been detected in the ASCII configuration file for the Communication Board Ethernet. Remedy:
|
| A08565 PROFINET: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration for the PROFINET interface (e.g., error in IP configuration, station name, or DHCP issue). Remedy:
|
| F08700 (A) CAN: Communications error | Cause: A CAN communications error has occurred (e.g., bus off, life time expired). Remedy:
|
| F08701 CAN: NMT state change | Cause: A CANopen NMT state transition from “operational” to “pre-operational” or “stopped” occurred. Remedy:
|
| F08702 (A) CAN: RPDO Timeout | Cause: The monitoring time of CANopen RPDO telegrams has expired as the bus connection was interrupted or the CANopen Manager was shut down. Remedy:
|
| A08751 (N) CAN: Telegram loss | Cause: The CAN controller has lost a receive message (telegram). Remedy:
|
| A08752 CAN: Error counter for error passive exceeded | Cause: The error counter for the send or receive telegrams has exceeded the value 127. Remedy:
|
| A08753 CAN: Message buffer overflow | Cause: A message buffer overflow has occurred (SDO or PDO buffer). Remedy:
|
| A08754 CAN: Incorrect communications mode | Cause: In the “operational” mode, an attempt was made to change parameters p8700 … p8737. Remedy:
|
| A08755 CAN: Object cannot be mapped | Cause: The CANopen object is not provided for the Process Data Object (PDO) Mapping. Remedy:
|
| A08756 CAN: Number of mapped bytes exceeded | Cause: The number of bytes of the mapped objects exceeds the telegram size for net data. A max. of 8 bytes is permissible. Remedy:
|
| A08757 CAN: Set COB-ID invalid | Cause: For online operation, the appropriate COB-ID must be set invalid before mapping. Remedy:
|
| A08759 CAN: PDO COB-ID already available | Cause: An existing PDO COB-ID was allocated. Remedy:
|
| A08760 CAN: maximum size of the IF PZD exceeded | Cause: The maximum size of the IF PZD was exceeded. Remedy:
|
| A08800 PROFlenergy energy-saving mode active | Cause: The PROFIenergy energy-saving mode is active. Remedy:
|
| F13009 Licensing OA application not licensed | Cause: At least one OA application which is under license does not have a license. Remedy:
|
| F13100 Know-how protection: Copy protection error | Cause: An error has occurred when checking the memory card with copy protection active (e.g., invalid card, card used in another unit). Remedy:
|
| F13101 Know-how protection: Copy protection cannot be activated | Cause: An error occurred when attempting to activate the copy protection for the memory card (e.g., no card inserted or invalid card). Remedy:
|
| F13102 Know-how protection: Consistency error of the protected data | Cause: An error was identified when checking the consistency of the protected files. As a consequence, the project on the memory card cannot be run. Remedy:
|
| F30001 Power unit: Overcurrent | Cause: The power unit has detected an overcurrent condition. This can be due to incorrect control parameterization, motor short-circuit, or power cables exceeding the maximum length. Remedy:
|
| F30002 Power unit: DC link voltage overvoltage | Cause: The power unit has detected an overvoltage condition in the DC link. Possible causes include the motor regenerating too much energy or the line supply voltage being too high. Remedy:
|
| F30003 Power unit: DC link voltage undervoltage | Cause: The power unit has detected an undervoltage condition in the DC link, possibly due to line supply failure. Remedy:
|
| F30004 Power unit: Overtemperature heat sink AC inverter | Cause: The temperature of the power unit heat sink has exceeded the permissible limit value due to insufficient cooling, overload, or high ambient temperature. Remedy:
|
| F30005 Power unit: Overload I2t | Cause: The power unit was overloaded (permissible rated current was exceeded for too long). Remedy:
|
| F30011 Power unit: Line phase failure in main circuit | Cause: At the power unit, the DC link voltage ripple has exceeded the permissible limit value, possibly due to a failed line phase. Remedy:
|
| F30012 Power unit: Temperature sensor heat sink wire breakage | Cause: The connection to a heat sink temperature sensor in the power unit is interrupted. Remedy:
|
| F30013 Power unit: Temperature sensor heat sink short-circuit | Cause: The heat sink temperature sensor in the power unit is short-circuited. Remedy:
|
| F30015 (N, A) Power unit: Phase failure motor cable | Cause: A phase failure in the motor feeder cable was detected. Remedy:
|
| A30016 (N) Power unit: Load supply switched off | Cause: The DC link voltage is too low. Under certain circumstances, the AC line supply is not switched on. Remedy:
|
| F30017 Power unit: Hardware current limit has responded too often | Cause: The hardware current limitation in the relevant phase has responded too often. Remedy:
|
| F30021 Power unit: Ground fault | Cause: The power has detected a ground fault in the power cables or at the motor. Remedy:
|
| F30022 Power unit: Monitoring U_ce | Cause: In the power unit, the monitoring of the collector-emitter voltage (U_ce) of the semiconductor has responded. Possible causes are fiber-optic cable interruption or a defective semiconductor. Remedy:
|
| F30024 Power unit: Overtemperature thermal model | Cause: The temperature difference between the heat sink and chip has exceeded the permissible limit value due to an inappropriate load duty cycle, insufficient cooling, or overload. Remedy:
|
| F30025 Power unit: Chip overtemperature | Cause: The chip temperature of the semiconductor has exceeded the permissible limit value due to an inappropriate load duty cycle, insufficient cooling, or overload. Remedy:
|
| F30027 Power unit: Precharging DC link time monitoring | Cause: The power unit DC link was not able to be precharged within the expected time. This could be due to no line supply voltage, low line supply, or a defective precharging circuit. Remedy:
|
| A30030 Power unit: Internal overtemperature alarm | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit. Remedy:
|
| A30031 Power unit: Hardware current limiting in phase U | Cause: Hardware current limit for phase U responded. The pulsing in this phase is inhibited for one pulse period. Remedy:
|
| A30032 Power unit: Hardware current limiting in phase V | Cause: Hardware current limit for phase V responded. The pulsing in this phase is inhibited for one pulse period. Remedy:
|
| A30033 Power unit: Hardware current limiting in phase W | Cause: Hardware current limit for phase W responded. The pulsing in this phase is inhibited for one pulse period. Remedy:
|
| A30034 Power unit: Internal overtemperature | Cause: The alarm threshold for internal overtemperature has been reached. Remedy:
|
| F30035 Power unit: Air intake overtemperature | Cause: The air intake in the power unit has exceeded the permissible temperature limit. Remedy:
|
| F30036 Power unit: Internal overtemperature | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit. Remedy:
|
| F30037 Power unit: Rectifier overtemperature | Cause: The temperature in the rectifier of the power unit has exceeded the permissible temperature limit. Remedy:
|
| A30042 Power unit: Fan has reached the maximum operating hours | Cause: The maximum operating time of at least one fan will soon be reached, or has already been exceeded. Remedy:
|
| A30049 Power unit: Internal fan faulty | Cause: The internal fan has failed. Remedy:
|
| F30051 Power unit: Motor holding brake short circuit detected | Cause: A short-circuit at the motor holding brake terminals has been detected. Remedy:
|
| F30052 EEPROM data error | Cause: EEPROM data error of the power unit module. The EEPROM data is inconsistent or not compatible with the firmware. Remedy:
|
| A30054 (F, N) Power unit: Undervoltage when opening the brake | Cause: When the brake is being opened, it is detected that the power supply voltage is less than 21.4 V. Remedy:
|
| F30055 Power unit: Braking chopper overcurrent | Cause: An overcurrent condition has occurred in the braking chopper. The braking resistor may have a short circuit or may be dimensioned too small. Remedy:
|
| A30057 Power unit: Line asymmetry | Cause: Frequencies have been detected on the DC link voltage that suggest line asymmetry or failure of a line phase. It is also possible that a motor phase has failed. Remedy:
|
| F30059 Power unit: Internal fan faulty | Cause: The internal power unit fan has failed and is possibly defective. Remedy:
|
| A30065 (F, N) Voltage measured values not plausible | Cause: The voltage measurement is not supplying any plausible values. Remedy:
|
| F30068 Power unit: undertemperature inverter heat sink | Cause: The actual inverter heat sink temperature is below the permissible minimum value. This could be due to a very low ambient temperature or a defective temperature sensor. Remedy:
|
| F30071 No new actual values received from the Power Module | Cause: More than one actual value telegram from the power unit module has failed. Remedy:
|
| F30072 Setpoints can no longer be transferred to the Power Module | Cause: More than one setpoint telegram was not able to be transferred to the power unit module. Remedy:
|
| F30074 (A) Communication error between the Control Unit and Power Module | Cause: Communications between the Control Unit (CU) and Power Module (PM) via the interface are no longer possible. The CU may have been withdrawn or is incorrectly inserted. Remedy:
|
| F30075 Configuration of the power unit unsuccessful | Cause: A communication error has occurred while configuring the power unit using the Control Unit. The cause is not clear. Remedy:
|
| F30080 Power unit: Current increasing too quickly | Cause: The power unit has detected an excessive rate of rise in the overvoltage range. This can be caused by incorrectly parameterized closed-loop control, a motor short-circuit, or power cables exceeding the maximum length. Remedy:
|
| F30081 Power unit: Switching operations too frequent | Cause: The power unit has executed too many switching operations for current limitation. This can be due to incorrectly parameterized closed-loop control or a motor short-circuit. Remedy:
|
| F30105 PU: Actual value sensing fault | Cause: At least one incorrect actual value channel was detected on the Power Stack Adapter (PSA). Remedy:
|
| A30502 Power unit: DC link overvoltage | Cause: The power unit has detected overvoltage in the DC link on a pulse inhibit, due to high device connection voltage or an incorrectly dimensioned line reactor. Remedy:
|
| F30600 SI P2: STOP A initiated | Cause: The drive-integrated “Safety Integrated” function on processor 2 has detected an error and initiated a STOP A. Remedy:
|
| F30611 (A) SI P2: Defect in a monitoring channel | Cause: The “Safety Integrated” function on processor 2 has detected a fault in the data cross-check between the two monitoring channels and has initiated a STOP F. Remedy:
|
| N30620 (F, A) SI P2: Safe Torque Off active | Cause: The “Safe Torque Off” (STO) function has been selected on processor 2 using the input terminal and is active. Remedy:
|
| F30625 SI P2: Sign-of-life error in safety data | Cause: The “Safety Integrated” function on processor 2 has detected an error in the sign-of-life of the safety data and initiated a STOP A. Remedy:
|
| F30649 SI P2: Internal software error | Cause: An internal error in the Safety Integrated software on processor 2 has occurred. This fault results in a STOP A that cannot be acknowledged. Remedy:
|
| F30650 SI P2: Acceptance test required | Cause: The drive-integrated “Safety Integrated” function on processor 2 requires an acceptance test. Remedy:
|
| F30651 SI P2: Synchronization with Control Unit unsuccessful | Cause: The “Safety Integrated” function requires synchronization of the safety time slices on processor 1 and processor 2. This synchronization routine was unsuccessful. Remedy:
|
| F30655 SI P2: Align monitoring functions | Cause: An error has occurred when aligning the Safety Integrated monitoring functions on processor 1 and processor 2. No common set of supported SI monitoring functions was able to be determined. Remedy:
|
| F30656 SI P2: Parameter processor 2 parameter error | Cause: When accessing the Safety Integrated parameters for the processor 2 in the non-volatile memory, an error has occurred (e.g., parameters corrupted, internal software error). Remedy:
|
| F30659 SI P2: Write request for parameter rejected | Cause: The write request for one or several Safety Integrated parameters on processor 2 was rejected (e.g., attempt to enable an unsupported function). Remedy:
|
| F30662 Error in internal communications | Cause: A module-internal communication error has occurred. Remedy:
|
| F30664 Error while booting | Cause: An error has occurred during booting. Remedy:
|
| F30665 SI P2: System is defective | Cause: A system defect was detected before the last boot or in the actual one. Remedy:
|
| A30693 (F) SI P2: Safety parameter settings changed, POWER ON required | Cause: Safety parameters have been changed; these will only take effect following a POWER ON. Remedy:
|
| A30788 Automatic test stop: wait for STO deselection via SMM | Cause: The automatic test stop was not able to be carried out after powering up, possibly because the STO function is selected via Safety Extended Functions. Remedy:
|
| N30800 (F) Power unit: Group signal | Cause: The power unit has detected at least one fault. Remedy:
|
| F30802 Power unit: Time slice overflow | Cause: A time slice overflow has occurred. Remedy:
|
| F30804 (N, A) Power unit: CRC | Cause: A checksum error (CRC error) has occurred for the power unit. Remedy:
|
| F30805 Power unit: EEPROM checksum error | Cause: Internal parameter data is corrupted. Remedy:
|
| F30809 Power unit: Switching information not valid | Cause: For 3P gating unit, the last switching status word in the setpoint telegram is identified by the end ID. Such an end ID was not found. Remedy:
|
| A30810 (F) Power unit: Watchdog timer | Cause: When booting it was detected that the cause of the previous reset was an SAC watchdog timer overflow. Remedy:
|
| F30850 Power unit: Internal software error | Cause: An internal software error has occurred in the power unit. Remedy:
|
| F30903 Power unit: I2C bus error occurred | Cause: Communications error with an EEPROM or an analog/digital converter. Remedy:
|
| A30920 (F) Temperature sensor fault | Cause: When evaluating the temperature sensor, an error occurred (wire breakage or measured resistance too low). Remedy:
|
| F30950 Power unit: Internal software error | Cause: An internal software error has occurred. Remedy:
|
| A30999 (F, N) Power unit: Unknown alarm | Cause: An alarm occurred on the power unit that cannot be interpreted by the Control Unit firmware, possibly because the component firmware is more recent. Remedy:
|
| F35950 TM: Internal software error | Cause: An internal software error has occurred. Remedy:
|
| A50001 (F) PROFINET configuration error | Cause: A PROFINET controller attempts to establish a connection using an incorrect configuring telegram. The “Shared Device” function has been activated (p8929 = 2). Remedy:
|
| A50010 (F) PROFINET: Consistency error affecting adjustable parameters | Cause: A consistency error was detected when activating the configuration for the PROFINET interface (e.g., error in IP configuration, station names, or DHCP settings). Remedy:
|
| A50011 (F) Ethernet/IP: configuration error | Cause: An EtherNet/IP controller attempts to establish a connection using an incorrect configuring telegram. The telegram length set in the controller does not match the parameterization in the drive device. Remedy:
|
| A50020 (F) PROFINET: Second controller missing | Cause: The PROFINET function “Shared Device” has been activated (p8929 = 2). However, only the connection to a PROFINET controller is present. Remedy:
|
| F50510 FBLOCKS: Logon of the runtime group rejected | Cause: When the runtime groups of the free function blocks attempted to log on, the logon of at least one group was rejected, possibly due to too many different hardware sampling times. Remedy:
|
| F50511 FBLOCKS: Memory no longer available for free function blocks | Cause: When the free function blocks were activated, more memory was requested than was available on the Control Unit. Remedy:
|
| A50513 (F) FBLOCKS: Run sequence value already assigned | Cause: An attempt was made to assign a run sequence value already assigned to a function block on this drive object to another additional function block on the same drive object. Remedy:
|
| A50517 FBLOCKS: Int. meas. active | Cause: A Siemens internal measurement has been activated. Remedy:
|
| F50518 FBLOCKS: Sampling time of free runtime group differs at download | Cause: In the downloaded project, the hardware sampling time of a free runtime group was set to a value that was either too low or too high. Remedy:
|
| F01000 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|
| F01001 FloatingPoint exception | Cause: An exception occurred for an operation with the FloatingPoint data type. The error may be caused by the basic system or an OA application (e.g. FBLOCKS, DCC). Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Note: Refer to r9999 for further information about this fault. r9999[0]: Fault number. r9999[1]: Program counter at the time when the exception occurred. r9999[2]: Cause of the FloatingPoint exception. Bit 0 = 1: Operation invalid Bit 1 = 1: Division by zero Bit 2 = 1: Overflow Bit 3 = 1: Underflow Bit 4 = 1: Inaccurate result Remedy:
|
| F01002 Internal software error | Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy:
|