Code 380001: PROFIBUS/PROFINET: Startup error, reason %1 parameter %2 %3 %4.

Parameters: %1 = Cause of the error %2 = Parameter 1 %3 = Parameter 2 %4 = Parameter 3 Drives alarms Definitions: An error occurred during startup of the PROFIBUS/PROFINET master. Overview: Cause of the error, Par 1, Par 2, Par 3: - 01 = DPM version, DPM version, DPA version, -- 02 = DPM ramp-up timeout, DPM actual value status, DPM setpoint value status, -- 03 = DPM ramp-up status, DPM actual value stat us, DPM setpoint value status, DPM error code - 04 = DPM ramp-up error, DPM actual value stat us, DPM setpoint value status, DPM error code - 05 = DPM-PLL sync error, --, --, -- 07 = Alarm queue too long, Actual number, Setpoint number, -- 08 = Unknown client, Client ID, --, -- 09 = Client version, Client ID, Client version, DPA version - 10 = Too many clients, Client number, max. number of clients, -- 11 = Log.basic address used several times; bus no.; slot no.; log.basic address -- 20 = Slave/device address used seve ral times, slave/device address -- 21 = Slave/device address un known, slave/device address, -- 22 = Erroneous configuration telegram, slave/device address, error code, -- 23 = OMI incompatible (data), drive version, CDA version, --, -- 24 = OMI incompatible (driver), drive version, CDA version, --, -- 25 = CPI initialization failed, error code, --, --, -- 26 = DMA not active - 27 = Reserved - 28 = Reserved - 29 = Reserved - The 1000s digit of the error cause = number of the affected bus Clients are the following components of the c ontrol system that use the PROFIBUS/PROFINET: Client ID = 1: PLC Client ID = 2: NCK Possible causes are: - Error in contents of SDB - Corruption of parts of the system program - Hardware defect on NC component Reaction: Channel not ready. NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Remedy for 1-11 1. Check the control project, check MD11240 $MN_PROFIBUS_SDB_NUMBER, and reload it when using a user-specific SDB. 2. If the error still occurs, back up data, and restar t the control with the standard values as per the asdelivered condition. 3. In case of correct ramp-up, reload the user data stage by stage. 4. If the error still occurs during ramp-up with stand ard values, reboot the system from the PC card or update the software. 5. If the error still occurs, replace the hardware. Remedy for 20-21 1. Check/correct the addresses of the connected slaves/devices. Remedy for 22 See SINAMICS warning 1903 for a descripti on of the meaning behind the error codes. 1. Control the SDB - Check the type and length of the message frame - Match slot assignment with P978 2. Evaluate the drive alarms/warnings Remedy for 23-24 1. Software replacement required Remedy for 25 1. Change the message frame type 2. Reduce the number of slots 3. Reduce the number of slaves/devices 4. Create a new SDB 5. Software must be replaced If the error has still not been able to be rectified afte r this procedure, send the error text to the control manufacturer. Program Continuation: Switch control OFF - ON. Drives alarms Diagnostics Manual (DAsl), 03/2009