| • 1: Invalid parameter ID |
| • 2: Data block for upload is not available |
| • 3: Write access for a read-only parameter |
| • 4: Read access for a write-only parameter |
| • 8: Data block read access already initialized |
| • 9: Data block write access already initialized |
| • 10: Data block read access not initialized |
| • 11: Data block write access not initialized |
| • 16: The data segment is already the last when reading the data block |
| • 17: The data segment is already the last when writing the data block |
| • 18: The data segment is not yet the last when reading the data block |
| • 19: The data segment is not yet the last when writing the data block |
| • 21: Checksum after data block write is invalid |
| • 23: Parameter ID in data block is invalid (data block write) |
| • 25: Burn system module only allowed immediately after download |
| • 27: Operating system not able to be started (operating system is not on the FPROM) |
| • 40: Value of parameter higher than maximum value |
| • 41: Value of parameter higher than maximum value |
| • 42: Value of parameter higher than maximum value |
| • 52: Value of parameter lower than minimum value |
| • 53: Value of parameter lower than minimum value |
| • 54: Value of parameter lower than minimum value |
| • 64: Hardware ID in BR module is invalid (data block write) |
| • 65: Hardware version in BR module is invalid (data block write) |
| • 66: The operating system on the drive is incompatible to the existing network |
| • 67: Necessary parameter is missing or is invalid |
| • 68: Data block length invalid |
| • 69: Command interface is occupied |
| • 70: Value of a necessary parameter too high |
| • 71: Value of a necessary parameter too low |
| • 72: firmware version less than minimal necessary firmware version |
| • 73: Invalid R4 floating point format |
| • 1001: Error-FIFO overflow |
| • 1002: Parameter outside the valid range |
| • 1003: Parameter cannot be written while loop control is active |
| • 1004: Timeout in network life sign monitor |
| • 1005: Parameter cannot be written while a movement is active |
| • 1006: Invalid parameter for trigger event (digital input + edge) |
| • 1007: Master for network coupling deactivated – one master is already sending |
| • 1008: Master for network coupling deactivated – Encoder error |
| • 1009: Error during memory allocation |
| • 1011: Quickstop input active |
| • 1012: Breakdown of cyclic network communication |
| • 1013: Station is not available for network communication |
| • 1014: Network command interface is occupied |
| • 1016: Maximum cycle time exceeded – CPU load too high |
| • 1017: Invalid parameter ID for cyclic read access |
| • 1018: Invalid parameter ID for cyclic write access |
| • 1021: Parameter cannot be written: Function block active |
| • 1022: Timeout in life sign monitoring of cyclic data to drive |
| • 1023: Network coupling with the cyclic communication mode not allowed |
| • 1024: Cyclic communication mode with current network configuration not possible |
| • 1025: Value of parameter in connection with holding brake not allowed |
| • 1026: Value of parameter in connection with SAFETY modules not allowed |
| • 1027: Function is not available for this hardware |
| • 2001: Upload of trace data not allowed: Recording active |
| • 2003: Trace start not allowed: Recording active |
| • 2006: Initialization of trace parameters not allowed: Recording active |
| • 4005: Controller cannot be switched on: Drive in error state |
| • 4007: Lag error stop limit exceeded |
| • 4008: Positive limit switch reached |
| • 4009: Negative limit switch reached |
| • 4010: Controller cannot be switched on: Both limit switches are closed |
| • 4011: Controller cannot be switched off: Movement active |
| • 4012: Controller cannot be switched on: Init parameters missing or not valid |
| • 4014: Two encoder control: Stop limit of positions difference exceeded |
| • 5001: Target position exceeds positive SW limit |
| • 5002: Target position exceeds negative SW limit |
| • 5003: Positive SW limit reached |
| • 5004: Negative SW limit reached |
| • 5005: Start of movement not possible: Position controller inactive |
| • 5006: Start of movement not possible: Axis not referenced |
| • 5010: Move in pos. direction not possible: Pos. limit switch is closed |
| • 5011: Move in neg. direction not possible: Neg. limit switch is closed |
| • 5012: Start of movement not possible: Stop ramp active |
| • 5013: Cyclic set value mode cannot be switched on: Movement active |
| • 5015: Start of movement not possible: Homing procedure active |
| • 5016: Parameter cannot be written: Homing procedure active |
| • 5017: Homing procedure mode not possible: Position controller inactive |
| • 5018: Homing procedure not possible: Movement active |
| • 5019: Homing parameter outside the valid range |
| • 5020: Homing procedure not possible: Both limit switches are closed |
| • 5021: Limit switch closed: No direction change for this homing mode |
| • 5022: Second limit switch signal received: Reference switch not found |
| • 5023: Incorrect limit switch signal received for current movement direction |
| • 5024: Cyclic set value mode aborted: Set positions missing |
| • 5025: Homing offset with counting range correction cannot be set |
| • 5026: Basis movement parameters (with override) exceed speed limit value |
| • 5027: Basis movement parameters (with override) exceed acceleration limit value |
| • 5028: Current movement is not a basis movement |
| • 5029: Trigger ignored – remaining distance exceeds SW limit |
| • 5030: Homing procedure mode not possible: Position controller active |
| • 5031: Homing procedure mode not possible: Cyclic set values mode is off |
| • 5032: Acceleration too low – braking distance exceeds positive SW limit |
| • 5033: Acceleration too low – braking distance exceeds negative SW limit |
| • 5034: Homing procedure not possible: Encoder error |
| • 5035: Reference marks not detected |
| • 5036: Acceleration stop limit exceeded |
| • 5037: Homing procedure mode not possible: Wrong encoder type |
| • 5038: Homing procedure mode not possible: Restore data invalid |
| • 5039: Function not possible: Encoder error |
| • 5101: Cam profile compensation gears: Limit values exceeded |
| • 5102: Too many changes of cam profile per cycle (master period too short) |
| • 5103: Slave trigger FIFO full |
| • 5104: Slave trigger FIFO empty |
| • 5105: Master trigger FIFO full |
| • 5106: Master trigger FIFO empty |
| • 5107: Cam coupling cannot be started: Parameter outside the valid range |
| • 5108: Master compensation trigger FIFO full |
| • 5109: Master compensation trigger FIFO empty |
| • 5110: Cam coupling aborted: Cyclic set positions missing |
| • 5111: Cam coupling aborted: Encoder error |
| • 5112: Command not allowed: Cam profile coupling not active |
| • 5113: Command not allowed: Controller is already active |
| • 5114: Parameter cannot be written: Cam coupling active |
| • 5115: Restart command not possible: The cam automat is not active |
| • 5201: Parameter cannot be written: Drumsequencer active |
| • 5202: Cam Control: Switch positions not in ascending order |
| • 5300: Data block for upload is not available |
| • 5301: Start cam automat linkage not possible: Parameter outside the valid range |
| • 5302: Parameter cannot be written: Cam automat active |
| • 5303: Cam profile data not available at index |
| • 5304: Format error in cam profile data |
| • 5311: Cam automat: Event leads to non initialized state |
| • 5315: Download error: Cam profile data in use by cam automat or function block |
| • 5316: Event type is not possible for entry in compensation gears |
| • 5319: Cam profile data not allowed for state 0 |
| • 5329: No valid cam profile data or state deactivated |
| • 6000: Master sampling time is not a multiple of position controller sampling time |
| • 6001: Sync controller: Timeout for sync telegram occurred |
| • 6002: Sync controller: Error tolerance of system time difference exceeded |
| • 6008: Controller is already active |
| • 6011: Controller is not in speed mode |
| • 6014: Drive initialization active |
| • 6015: CAN controller: CAN bus disturbance (receive error counter greater 96) |
| • 6016: CAN controller: CAN bus disturbance (transmit error counter greater 96) |
| • 6017: Software: Watchdog active |
| • 6018: Hardware: 15V power supply fail |
| • 6019: ACOPOS: Overcurrent |
| • 6020: Hardware: 24V power supply fail |
| • 6021: Low level at controller enable input |
| • 6023: Voltage sag at controller enable input |
| • 6024: Current was latched before conversion (OpSys error in ABLS) |
| • 6025: Temperature was latched before conversion (OpSys error in ABLS) |
| • 6026: Holding brake: Stator current limit exceeded during release |
| • 6027: Holding brake: Manual operation not permitted |
| • 6028: Holding brake: Undervoltage/-current (wire breakage, check 24V supply) |
| • 6029: Holding brake: Control signal on and output status off |
| • 6030: Holding brake: Brake output is active, but no brake entered in motor data |
| • 6031: System module already deleted |
| • 6032: Interface: FPGA configuration error |
| • 6033: Type of servo amplifier is not supported by ACOPOS-firmware |
| • 6034: Cyclic set value mode aborted: Set speeds missing |
| • 6036: Motor parameters missing or invalid |
| • 6038: Torque limit higher than peak motor torque |
| • 6040: Operating system version is less than allowed minimum version |
| • 6041: Operating system version is greater than allowed maximum version |
| • 6042: Operating system version is not in the allowed range |
| • 6043: PHASING_MODE is not valid |
| • 6044: Phasing: Rotational direction or position not valid |
| • 6045: Power stage: Connection X5: No current flow |
| • 6046: Phasing: No rotor movement |
| • 6047: Holding brake: Control signal off and output status on |
| • 6048: Motor holding brake movement monitor: Position error too large |
| • 6049: Power stage: Connection X5: Current measurement faulty |
| • 6050: Write parameter not allowed: Set current filter or notch filter active |
| • 6051: Phasing: Speed to high |
| • 6052: Power stage: High-side: Overcurrent |
| • 6053: Power stage: Low-side: Overcurrent |
| • 6054: Power stage: Overcurrent |
| • 6055: Holding brake: Low voltage |
| • 6056: Holding brake: Low current |
| • 6057: Position loop controller: Load encoder error |
| • 6058: Enable1: Voltage sag |
| • 6059: Enable2: Voltage sag |
| • 6060: Power stage: Limit speed exceeded |
| • 6061: CTRL Speed controller: Limit speed exceeded |
| • 6062: CTRL Speed controller: Speed error stop limit exceeded |
| • 6063: Holding brake: External voltage on output over 24V |
| • 6064: Parameter cannot be written: Repetitive Control active |
| • 6065: Initialization active |
| • 6066: Index overflow while initilization of matrices |
| • 6067: Error during initialization of the dynamical system |
| • 7012: Encoder: Hiperface error bit |
| • 7013: Encoder: Status message |
| • 7014: Encoder: CRC error during parameter transfer |
| • 7015: Encoder: Timeout error during parameter transfer |
| • 7016: Encoder: Busy error during parameter transfer |
| • 7017: Encoder: Error while reading encoder parameter |
| • 7020: OEM data: Data write error |
| • 7021: Encoder: Timeout error while reading absolute position |
| • 7022: Encoder: Initialization is active |
| • 7023: Encoder: Parameter transfer is active |
| • 7029: Encoder: Incremental signal amplitude too small |
| • 7030: Encoder: Incremental signal amplitude too large |
| • 7031: Encoder: Incremental signal amplitude too large (Disturbance) |
| • 7032: Encoder: Incremental signal amplitude too small (Disturbance, no connection) |
| • 7033: Encoder: Incremental position step too large |
| • 7036: Encoder: Interface ID invalid (Check slot and Interface EEPROM data) |
| • 7038: Encoder: Position value not synchronous with absolute value |
| • 7039: Incremental encoder: Cable disturbance track A |
| • 7040: Incremental encoder: Cable disturbance track B |
| • 7041: Incremental encoder: Cable disturbance track R |
| • 7042: Incremental encoder: Edge distance of quadrature signal too small |
| • 7043: Encoder: Cable disturbance track D |
| • 7044: Encoder: Parity |
| • 7045: Resolver: Signal disturbance (plausibility check) |
| • 7046: Resolver: Cable disturbance |
| • 7047: Invalid distance of reference marks |
| • 7048: Error during the reading of encoder memory |
| • 7049: Abnormal encoder current consumption |
| • 7050: Incremental encoder: Illegal AB signal change |
| • 7051: Encoder: Acceleration too large (Disturbance) |
| • 7052: Encoder: Encoder is not Supported |
| • 7053: Encoder: Power failure |
| • 7054: Encoder: Position in channel already defined |
| • 7055: Encoder: Invalid content type ‘frame end’ |
| • 7056: Encoder: Register read forbidden or not implemented |
| • 7057: Encoder: Register write forbidden or not implemented |
| • 7058: Encoder: Alarm bit is set |
| • 7059: Virtual Encoder: Error state |
| • 7060: Virtual Encoder: Transition error |
| • 7061: Virtual Encoder: stall detection |
| • 7100: Parameter function not supported. (Module ?) |
| • 7200: DC bus: Overvoltage |
| • 7210: DC bus: Charging: Voltage unstable |
| • 7211: DC bus: Voltage dip |
| • 7212: DC bus: Large voltage dip |
| • 7214: DC bus: Charging resistor hot (too many power line fails) |
| • 7215: Power mains: At least one phase of the power line failed |
| • 7217: DC bus: Nominal voltage detection: Voltage too high |
| • 7218: DC bus: Nominal voltage detection: Voltage too low |
| • 7219: DC bus: Charging: Voltage too low |
| • 7220: DC bus: Nominal voltage detection: Voltage not allowed |
| • 7221: Mains: Failure |
| • 7222: Power stage: Summation current connection X5: Overcurrent (Ground fault) |
| • 7223: DC bus: Overvoltage DC-GND |
| • 7224: Connector to back plane: 24V-GND contact monitoring: Voltage too low |
| • 7225: DC bus: Overvoltage |
| • 7226: DC bus: Overcurrent |
| • 7227: Bleeder: Overcurrent |
| • 7300: Digital IO: IO Configuration invalid |
| • 7401: Parameter position exceeds maximum data length |
| • 7402: Processing of parameter sequence aborted: Write error |
| • 7403: Processing of parameter sequence is still active |
| • 7404: Parameter sequence not available at index |
| • 8001: EEPROM select not valid |
| • 8003: Table index not valid |
| • 8004: EEPROM variable type not valid |
| • 8005: EEPROM type not valid |
| • 8006: Value of EEPROM parameter is zero |
| • 8007: Value of EEPROM parameter is not valid |
| • 8011: EPROM: Data not valid |
| • 8020: Invalid switch frequency |
| • 9000: Heatsink temperature sensor: Overtemperature – Movement stopped |
| • 9001: Heatsink temperature sensor: Overtemperature – Limiter active |
| • 9002: Heatsink temperature sensor: Not connected or damaged |
| • 9003: Heatsink temperature sensor: Not connected or destroyed |
| • 9010: Temperature sensor (Motor|Choke|External): Overtemperature |
| • 9011: Temperature sensor (Motor|Choke|External): Overtemperature – Limiter active |
| • 9012: Temperature sensor (Motor|Choke|External): Not connected or destroyed |
| • 9013: Temperature sensor (Motor|Choke|External): Short circuit |
| • 9030: Junction temperature model: Overtemperature – Movement stopped |
| • 9031: Junction temperature model: Overtemperature – Limiter active |
| • 9040: Bleeder temperature model: Overtemperature – Movement stopped |
| • 9041: Bleeder temperature model: Overtemperature – Limiter active |
| • 9050: ACOPOS peak current: Overload – Movement stopped |
| • 9051: ACOPOS peak current: Overload – Limiter active |
| • 9060: ACOPOS continuous current: Overload – Movement stopped |
| • 9061: ACOPOS continuous current: Overload – Limiter active |
| • 9070: Motor temperature model: Overload – Movement stopped |
| • 9071: Motor temperature model: Overload – Limiter active |
| • 9075: ACOPOS continuous power: Overload – Movement stopped |
| • 9076: ACOPOS continuous power: Overload – Limiter active |
| • 9078: Power stage: Temperature sensor 1: Overtemperature – Movement stopped |
| • 9079: Power stage: Temperature sensor 1: Overtemperature – Limiter active |
| • 9080: Charging resistor: Overtemperature |
| • 9081: Power stage temperature model: Overtemperature – Movement stopped |
| • 9082: Power stage temperature model: Overtemperature – Limiter active |
| • 9083: Power stage: Temperature sensor 2: Overtemperature – Movement stopped |
| • 9084: Power stage: Temperature sensor 2: Overtemperature – Limiter active |
| • 9085: Power stage: Temperature sensor 3: Overtemperature – Movement stopped |
| • 9086: Power stage: Temperature sensor 3: Overtemperature – Limiter active |
| • 9087: Power stage: Temperature sensor 4: Overtemperature – Movement stopped |
| • 9088: Power stage: Temperature sensor 4: Overtemperature – Limiter active |
| • 9089: Motor encoder temperature sensor: Overtemperature |
| • 9090: Motor encoder temperature sensor: Temperature value not valid |
| • 9300: Current controller: Overcurrent |
| • 10000: Identification parameter(s) missing |
| • 10001: Parameter identification: Invalid sub-mode |
| • 10100: Parameter identification: Quality factor not fulfilled |
| • 10101: No ISQ-filter free |
| • 10102: No resonance-frequency for ISQ-filter (band-stop) found |
| • 10103: Autotuning: Maximum lag error exceeded |
| • 10500: Induction stop was terminated |
| • 31201: Di/Do Interface: Drive not ready |
| • 31220: Encoder error: Encoder not configured |
| • 31221: Encoder error: Cable disturbance or signal disturbance |
| • 31224: Encoder Interface: HW Module not OK |
| • 31240: Homing procedure mode not allowed with current HW Type |
| • 31247: Drive Interface: DrvOK not set from HW Module |
| • 31248: Trigger Interface: HW Module not OK |
| • 31249: Drive Interface: HW Module not OK |
| • 31250: Di/Do Interface: HW Module not OK |
| • 31260: Current axis configuration only possible in simulation mode |
| • 31261: Change mode for servo drive adjustment not allowed |
| • 32001: Error calling CAN_xopen() |
| • 32002: Error defining Write COB for Broadcast Command |
| • 32003: Error defining Write COB for Parameter Read Request |
| • 32004: Error defining Write COB for Parameter Write Request |
| • 32005: Error defining Read COB for Parameter Read Response |
| • 32006: Error defining Read COB for Parameter Write Response |
| • 32007: Error defining Read COB for Monitor Data from the drive |
| • 32008: Error sending Read Request (network error ?) |
| • 32009: Error sending Write Request (network error ?) |
| • 32010: Drive not responding to Read Request (is the drive in the network ?) |
| • 32011: Drive not responding to Write Request (is the drive in the network ?) |
| • 32012: Error reading module description of system module |
| • 32013: No operating system present on the drive |
| • 32014: Operating system version on the drive not compatible with NC manager version |
| • 32015: Error creating message queue |
| • 32016: Error sending an idle time command to the NC Manager Task |
| • 32017: Wrong boot state after start of operating system |
| • 32018: Invalid Parameter ID in system module |
| • 32019: Download of NC system module not allowed (the module is on the PLC) |
| • 32020: System module data could not be read from the drive during NC manager INIT |
| • 32021: System module data could not be read from the drive after download |
| • 32022: Error aborting data block access before download |
| • 32023: Error reading boot state before download |
| • 32025: Wrong boot state after SW Reset before download |
| • 32026: Error during INIT of data block write access for download |
| • 32027: Error sending data segment for download |
| • 32029: Response error after sending data segment for download |
| • 32030: Error at command for system module burn after download |
| • 32031: Error reading status for system module burn after download |
| • 32032: Error while burning system module after download |
| • 32033: Timeout while burning system module after download |
| • 32034: Error at SW Reset before download |
| • 32035: Error at SW Reset after download |
| • 32036: Different system module data after download |
| • 32037: Error message(s) lost because of FIFO overflow (acknowledge errors) |
| • 32038: Error searching for INIT parameter module |
| • 32039: Error reading INIT parameter module |
| • 32040: Version of INIT parameter module is not compatible to NC manager |
| • 32041: The module acp10cfg does not exist |
| • 32042: The module acp10cfg is not an NC data module |
| • 32043: The NC module type of the module acp10cfg is invalid |
| • 32044: The NC module type of the module acp10cfg cannot be read |
| • 32045: The data address in module acp10cfg cannot be read |
| • 32046: The data section of module acp10cfg is empty |
| • 32047: A CAN node number in module acp10cfg is invalid |
| • 32048: A CAN node number in module acp10cfg is used repeatedly |
| • 32049: This NC action is not allowed during Trace is active |
| • 32050: A Trace Data Upload is already active |
| • 32051: Invalid Trace Status for Trace Data Upload |
| • 32053: Error defining Write COB for Parameter Read Request 2 |
| • 32054: Error defining Write COB for Parameter Write Request 2 |
| • 32055: Error defining Read COB for Parameter Read Response 2 |
| • 32056: Error defining Read COB for Parameter Write Response 2 |
| • 32057: Error accessing HS task class table |
| • 32058: Error accessing task class table |
| • 32059: Parameter tk_no invalid for access to task class table |
| • 32060: Timeout for cyclic data from drive – Indications invalid (network error ?) |
| • 32061: Timeout sending a Read Request telegram (network error ?) |
| • 32062: Timeout sending a Write Request telegram (network error ?) |
| • 32063: Data address zero (set/read parameter via service interface) |
| • 32064: Convert text into binary data is not possible for this parameter data type |
| • 32065: Convert binary data into text is not possible for this parameter data type |
| • 32066: Parameter ID zero (set/read parameter via service interface) |
| • 32067: Parameter ID invalid (set/read parameter with option ncDATA_TEXT) |
| • 32069: The data address of the ACOPOS parameters in module acp10cfg cannot be read |
| • 32070: Drive for ACOPOS parameters in module acp10cfg not found |
| • 32071: The ACOPOS parameters are invalid (an update of AutomationStudio is necessary) |
| • 32072: Wrong boot state after SW Reset |
| • 32073: Download of NC system module: Error reading NC hardware version of BsLoader |
| • 32074: Incompatible NC hardware version: Download of BsLoader not possible |
| • 32075: Incompatible NC hardware version: Download of operating system not possible |
| • 32076: FIFO for messages with high priority to NC Manager Task is full |
| • 32077: A POWERLINK node number in module acp10cfg is invalid |
| • 32078: A POWERLINK node number in module acp10cfg is used repeatedly |
| • 32079: With this version one CAN interface must be in module acp10cfg |
| • 32080: With this version one POWERLINK interface must be in module acp10cfg |
| • 32081: With this version only one POWERLINK interface is allowed in module acp10cfg |
| • 32082: Module acp10cfg contains a CAN interface without any drive node |
| • 32083: Module acp10cfg contains a POWERLINK interface without any drive node |
| • 32084: The NC configuration does not contain any ACOPOS module |
| • 32085: Module acp10cfg invalid (AutomationStudio V2.2 or higher necessary) |
| • 32086: With this version no CAN interface is allowed in module acp10cfg |
| • 32087: With this version no POWERLINK interface is allowed in module acp10cfg |
| • 32088: The INIT parameter module specified in the NC Mapping Table does not exist |
| • 32089: NC-HW-ID of INIT parameter module is not compatible to NC manager |
| • 32090: NC object type of INIT parameter module is not equal to NC object |
| • 32091: Invalid block data in INIT parameter module (data range exceeded) |
| • 32092: Error sending a command to the NC Idle Task |
| • 32093: NcManCtrl is defined repeatedly with different values |
| • 32094: NetworkInit is defined repeatedly for ncMANAGER with different values |
| • 32095: Value of drive group in CAN-CFG-Module higher than maximum value |
| • 32096: Size of data buffer for trace data upload in module acp10cfg too small |
| • 32097: All counts of used network interfaces in module acp10cfg are zero |
| • 32098: Version of the module acp10cfg is not compatible with NC manager |
| • 32099: Length of data section of module acp10cfg is too small |
| • 32100: Memory for NC error text management cannot be allocated |
| • 32101: Error accessing NC error text module in BR module table |
| • 32102: Version ID of error text module not equal to that of NC manager |
| • 32103: Data section of error text module cannot be read |
| • 32104: Data section of error text module is empty |
| • 32105: Length of data section of error text module is too small |
| • 32106: Error list of error text module not equal with that of NC manager |
| • 32107: Parameter list of error text module not equal with that of NC manager |
| • 32108: The last error number of error text module is not equal to 65535 |
| • 32109: The last parameter ID of error text module is not equal to 65535 |
| • 32110: Length of data section of CAN-CFG-Module cannot be read |
| • 32111: Length of data section of CAN-CFG-Module is too small |
| • 32112: The data address in the CAN-CFG-Module cannot be read |
| • 32113: The enable code in the CAN-CFG-Module is invalid |
| • 32114: Values not equal to zero in reserved area of CAN-CFG-Module |
| • 32115: The basis CAN ID for WR/RD channel1 in the CAN-CFG-Module is invalid |
| • 32116: The basis CAN ID for WR/RD channel2 in the CAN-CFG-Module is invalid |
| • 32117: The basis CAN ID for WR/RD channel3 in the CAN-CFG-Module is invalid |
| • 32118: The basis CAN ID for monitor data in the CAN-CFG-Module is invalid |
| • 32119: Invalid basis CAN ID for cyclic data to the drive in CAN-CFG-Module |
| • 32120: Invalid basis CAN ID for cyclic data from the drive in CAN-CFG-Module |
| • 32121: The CAN ID for the SYNC telegram in the CAN-CFG-Module is invalid |
| • 32122: The CAN ID for the broadcast command in the CAN-CFG-Module is invalid |
| • 32123: Error defining Read COB for WR2 Request (external set position mode) |
| • 32124: Error defining Read COB for WR2 Response (external set position mode) |
| • 32125: Error defining Read COB for RD2 Request (external set position mode) |
| • 32126: Error defining Read COB for RD2 Response (external set position mode) |
| • 32127: Error deleting Write COB for Broadcast Command (external set position mode) |
| • 32128: Error defining Read COB for Broadcast Command (external set position mode) |
| • 32129: Error defining Read COB for cyclic user data from drive (ext. set pos. mode) |
| • 32130: This external set position mode is only allowed with one CAN interface |
| • 32131: The specified NC data module does not exist |
| • 32132: The specified module is not an NC data module |
| • 32133: The NC module type of the specified NC data module is invalid |
| • 32134: The NC module type of the specified NC data module cannot be read |
| • 32135: The data address of the specified NC data module cannot be read |
| • 32136: The Data section of the specified NC data module is empty |
| • 32137: Data address of structure for a data block operation is zero |
| • 32138: Data address zero (user data for data block operation) |
| • 32139: Data length zero (user data for data block operation) |
| • 32140: Data block operation: Data module name or data address must be zero |
| • 32141: Invalid data format in a parameter sequence |
| • 32142: ID or type of a parameter invalid in parameter sequence with text format |
| • 32143: Data of a parameter in a parameter sequence longer than 6 bytes |
| • 32144: Error for an ACOPOS Parameter Table specified in the NC Mapping Table |
| • 32145: The ACOPOS Parameter Table does not exist |
| • 32146: The ACOPOS Parameter Table is not an NC data module |
| • 32147: The NC module type of the ACOPOS Parameter Table is invalid |
| • 32148: The NC module type of the ACOPOS Parameter Table cannot be read |
| • 32149: The data address in the ACOPOS Parameter Table cannot be read |
| • 32150: The data section of the ACOPOS Parameter Table is empty |
| • 32151: Error initializing memory buffer for XML parser |
| • 32152: No XML elements present in an ACOPOS Parameter Table |
| • 32153: The first XML element is invalid in the ACOPOS Parameter Table |
| • 32154: The ACOPOS Parameter Table does not contain any ACOPOS parameters |
| • 32155: Nesting depth for ACOPOS parameter groups exceeded |
| • 32156: ID or type of an ACOPOS parameter invalid for text conversion |
| • 32157: Length of parameter data too large for ACOPOS parameter in XML data |
| • 32158: ACOPOS parameter: An attribute is not defined (ID) |
| • 32159: ACOPOS parameter: An attribute is not defined (Value) |
| • 32160: Basis movements with mode ncTRG_STOP are not allowed for ncV_AXIS |
| • 32161: ncNC_SYS_RESTART,ncACKNOWLEDGE is not allowed (network.init=ncFALSE) |
| • 32162: Internal task class number wrong (from now on operation is blocked !!!) |
| • 32163: A system module download to all drives is not possible with SwNodeSelect |
| • 32164: The text defined with NetworkInit (global) is invalid |
| • 32165: A CAN node number is equal to NodeNr_SwNodeSelect |
| • 32166: Network initialization during active network initialization not allowed |
| • 32167: The text defined with NetworkInit is invalid |
| • 32168: NodeNr_SwNodeSelect is defined repeatedly with different values |
| • 32169: The node number defined with NodeNr_SwNodeSelect is invalid |
| • 32170: A data module name has to be entered for this data block operation |
| • 32171: Index zero is not allowed (user data for data block operation) |
| • 32172: The specified data module name is not valid for a BR module |
| • 32173: Memory for data module creation cannot be allocated |
| • 32174: Error with installation of data module into BR module table |
| • 32175: Error with installation of data module into BR module table |
| • 32176: Text for parameter data too large for parameter sequence with text format |
| • 32177: Text for parameter data too large for parameter list with text format |
| • 32178: This NC object is not enabled for this ACOPOS (channel number too high) |
| • 32179: ID or type of a parameter invalid in parameter list with text format |
| • 32180: Data address of structure for a parameter list operation is zero |
| • 32181: Data address zero (user data for parameter list operation) |
| • 32182: Data length zero (user data for parameter list operation) |
| • 32183: Data length invalid (user data for parameter list operation) |
| • 32184: Invalid data format in a parameter list |
| • 32185: Data of a parameter in a parameter list longer than 6 bytes |
| • 32186: NetBasisInitNr is defined repeatedly for ncMANAGER with different values |
| • 32187: Error for synchronization of network initialization (details in Logger) |
| • 32188: This NC object is defined in hardware configuration and NC Mapping Table |
| • 32189: Timeout for cyclic data from drive – Indications invalid (network error ?) |
| • 32190: Error defining Write COB for selection of node number via software |
| • 32191: This parameter ID is reserved for the PLCopen MC library |
| • 32192: The specified data module is not an INIT Parameter module |
| • 32193: For this NC object type no INIT parameter module is present |
| • 32194: This function is not implemented for this NC object type |
| • 32195: Error downloading BsLoader to ACOPOS |
| • 32196: Error downloading operating system to ACOPOS |
| • 32197: Error downloading BsLoader to ACOPOS (additional info in Logger) |
| • 32198: Error downloading operating system to ACOPOS (additional info in Logger) |
| • 32200: Error calling plAcycWrite() (read parameter) |
| • 32201: Error calling plAcycWrite() (write parameter) |
| • 32202: Error calling plAcycRead() (read parameter) |
| • 32203: Error calling plAcycRead() (write parameter) |
| • 32204: Timeout while reading par. via acyclic channel (is the drive in the network ?) |
| • 32205: Timeout while writing par. via acyclic channel (is the drive in the network ?) |
| • 32206: Cyclic channel: Read Request in spite of Wait for Response |
| • 32207: Cyclic channel: Write Request in spite of Wait for Response |
| • 32208: Error using plAction(DEVICE_TO_BUS_NR) (additional info in Logger) |
| • 32209: Error using plAction(GET_IDENT) (additional info in Logger) |
| • 32210: Wrong interface ident when calling plState() (additional info in Logger) |
| • 32211: Interface not available when calling plState() (additional info in Logger) |
| • 32212: Fatal interface error when calling plState() (additional info in Logger) |
| • 32213: Timeout for POWERLINK interface (additional info in Logger) |
| • 32214: Error calling plAcycOpen() (additional info in Logger) |
| • 32215: Error calling plCECreate() (additional info in Logger) |
| • 32216: Error using plAction(GET_IF_PAR) (additional info in Logger) |
| • 32217: Broadcast channel: Error calling plAcycWrite() (read parameter) |
| • 32218: Broadcast channel: Error calling plAcycWrite() (write parameter) |
| • 32219: Error using plAction(GET_IF_MUXPRESCALE) (additional info in Logger) |
| • 32220: Error using plAction(GET_IF_CYCLE_TIME) (additional info in Logger) |
| • 32221: Error using plAction(GET_IF_PRESCALE) (additional info in Logger) |
| • 32222: Error using plAction(GET_STATIONFLAG) (additional info in Logger) |
| • 32223: Error calling plGetNodeInfo() (additional info in Logger) |
| • 32224: Error calling plAction(GET_PROTOCOL_VERSION) (additional info in Logger) |
| • 32225: This ACOPOS POWERLINK node does not exist in the AR Configuration |
| • 32226: A SDC node number in module acp10cfg is invalid |
| • 32227: A SDC node number in module acp10cfg is used repeatedly |
| • 32228: There is no network interface (POWERLINK or SDC) contained in acp10cfg |
| • 32229: The object acp10sdc does not exist (necessary for SDC NC objects) |
| • 32230: Error at initialization of ACP10SDC or ACP10SIM (see Logger) |
| • 32231: Error at SDC configuration (see Logger) |
| • 32232: The object acp10sim does not exist (necessary for ACOPOS simulation) |
| • 32233: The object acp10bsl contains no NC system module |
| • 32234: The object acp10sys contains no NC system module |
| • 32235: Data address zero for parameter in parameter sequence |
| • 32236: Data address zero for parameter in parameter list |
| • 32237: Channel index for ACOPOS parameters in module acp10cfg is invalid |
| • 32238: This function is not implemented at this time |
| • 32239: Basic memory for INIT parameter modules could not be allocated |
| • 32240: NC object data invalid (PV with INIT value in variable declaration ?) |
| • 32241: Data block operation: Data module name must be zero |
| • 32242: Conditions for cam profile transfer via Systick-Task are not fullfilled |
| • 32243: Error using plAction(GET_PDO_INFO) (additional info in Logger) |
| • 32244: No PDO defined in the cyclic frame for this channel: NC object is disabled |
| • 32245: The Memory for operating the broadcast channel cannot be allocated |
| • 32246: ‘Direction’ of the POWERLINK broadcast channel is not ‘Output’ |
| • 32247: Error using plAction(GET_TC_INFO) (additional info in Logger) |
| • 32251: NcNetCyc: Response timeout |
| • 32252: NcNetCyc: Unexpected Response (invalid counter value) |
| • 32253: The task class for POWERLINK output cycle trigger is invalid |
| • 32259: There are currently no trace data to be saved |
| • 32260: Trace: No valid test data point is defined |
| • 32261: Trace trigger: The NC object is invalid |
| • 32262: Trace test data point: The NC object is invalid |
| • 32263: Trace trigger: The NC object is not enabled for this ACOPOS |
| • 32264: Trace test data point: The NC object is not enabled for this ACOPOS |
| • 32265: Trace trigger: Trace for this NC object already active at trace start |
| • 32266: Trace test data point: Trace for this NC object already active at trace start |
| • 32267: Trace trigger: The NC object is not enabled for trace commands |
| • 32268: Trace test data point: The NC object is not enabled for trace commands |
| • 32269: Trace: Too many test data points defined for one trace channel |
| • 32270: ACOPOS coupling: The channel number of the send data is invalid |
| • 32271: ACOPOS coupling: The channel number of the receive data is invalid |
| • 32272: ACOPOS coupling: Send data with this channel number are not configured |
| • 32273: ACOPOS coupling: The NC object of the send data is invalid |
| • 32274: Network coupling: The broadcast channel was not configured |
| • 32275: Network coupling: The broadcast channel was not successfully initialized |
| • 32276: Network coupling: Cycle times not equal (network interfaces, NC task class) |
| • 32277: Network coupling: In the broadcast channel no more data record has place |
| • 32278: ACOPOS coupling: Zero as Parameter ID of the send data is not allowed |
| • 32279: Service interface: Data address zero |
| • 32280: Timeout for enable of acyclic network communication |
| • 32281: Version of SafeMC lower than minimum version (see Logger) |
| • 32282: Network coupling: Incompatible cycle times (network interfaces, NC task class) |
| • 32283: INIT broadcast data point: Call of NC action only allowed in NC Manager TC |
| • 32284: Ext. coupling data: With this AR/NC version only for TC1 with synchr. output |
| • 32285: INIT broadcast data point: Incompatible cycle times (POWERLINK, NC manager) |
| • 32286: Network coupling: Incompatible cycle times (network interfaces, NC task class) |
| • 32287: Extended coupling data not possible (OutTime difference too large) |
| • 32288: Extended coupling data not possible (task class tolerance is not zero) |
| • 32302: Start setup not possible: A setup operation is already active |
| • 32322: Data block upload/download: The data object name is zero |
| • 32323: Data block upload/download: The data block parameter ID is invalid |
| • 32324: Data block upload/download: The parameter ID of data block index 1 is invalid |
| • 32325: Data block upload/download: The parameter ID of data block index 2 is invalid |
| • 32326: Data block upload/download: Address of data buffer is zero |
| • 32327: Data block upload/download: Length of data buffer is zero |
| • 32328: Data block upload: Length of data buffer lower than length of data block |
| • 32398: acp10sys does not contain an operating system for this ACOPOS hardware type |
| • 32399: Manual ACOPOS restart (POWER-OFF/-ON) after NCSYS download necessary |
| • 32400: Memory cannot be allocated |
| • 32401: No file name specified |
| • 32402: The specified file cannot be opened |
| • 32403: The specified file cannot be created |
| • 32404: Error at writing into a file |
| • 32405: Error at reading from a file |
| • 32406: The specified file cannot be created |
| • 32407: Error at writing into a file |
| • 32408: Error at closing a file |
| • 32409: The specified file cannot be deleted |
| • 32410: The data object type is invalid |
| • 32411: The address of the data object structure is zero |
| • 32412: The name in the data object structure is zero |
| • 32413: The data address in the data object structure is zero |
| • 32414: The data length in the data object structure is zero |
| • 32415: No File Device specified |
| • 32416: The FileIO functions do not exist (is library FileIO existing ?) |
| • 32417: Error at writing into an NC data module |
| • 32418: No XML elements present in MTC data |
| • 32419: MTC data: XML elements invalid or in wrong order |
| • 32420: The MTC data contain an invalid configuration |
| • 32421: The MTC data contain no configuration for Multi Axes Trace |
| • 32422: The MTC data contain more than one configuration for Multi Axes Trace |
| • 32423: MTC-Daten: Trigger.NcObject ist invalid |
| • 32424: MTC-Daten: Trigger.Condition ist invalid |
| • 32425: MTC-Daten: Channel.NcObject ist invalid |
| • 32426: Trace trigger: The event is invalid |
| • 32427: Trace trigger: Parameter ID zero not allowed if event unequal to OFF |
| • 32428: The data object format is invalid |
| • 32492: ACOPOS Simulation: TC for cyclic PLCopen data not equal to NC Manager TC |
| • 32494: AcoposSimulation=Off for one channel although activated for the other channel |
| • 32495: AcoposSimulation: Different values defined for real and virtual axis |
| • 32496: Error creating cyclic task for PLCopen MC (details in Logger) |
| • 32497: Task class for handling of cyclic data with PLCopen in acp10cfg is invalid |
| • 32498: PLCopen_CyclicData_TaskClass is lower than zero or higher than maximum value |
| • 32499: PLCopen_CyclicData_TaskClass: Values for real and virtual axis are not equal |
| • 32500: The Message FIFO already exists |
| • 32501: Error creating Message FIFO |
| • 32502: The Critical Section for Command Semaphore already exists |
| • 32503: Error creating Critical Section for Command Semaphore |
| • 32504: The NC Manager Idle Task already exists |
| • 32505: Error creating NC Manager Idle Task |
| • 32506: Error reading Taskclass Cycle Time |
| • 32507: Error reading Taskclass Tolerance |
| • 32508: Error sending an idle time command to the NC Manager Task |
| • 32509: The Critical Section for Network Command Trace already exists |
| • 32510: Error creating Critical Section for Network Command Trace |
| • 32511: The Critical Section for messages with high priority already exists |
| • 32512: Error creating Critical Section for messages with high priority |
| • 32513: The Critical Section for global variables already exists |
| • 32514: Error creating Critical Section for global variables |
| • 32738: Error writing into SDM Motion FIFO |
| • 32739: Error creating SDM Motion FIFO (see Logger) |
| • 32740: Error deleting SDM Motion FIFO (see Logger) |
| • 32741: Error creating SDM Motion task (see Logger) |
| • 32742: Error deleting SDM Motion task (see Logger) |
| • 32743: SDM_Motion_Action: ncaction() did not return with ncOK |
| • 32744: SDM_Motion_Action not allowed (still no Trace configuration loaded) |
| • 32745: SDM_Motion_Action not allowed (Motion Trace already started by application) |
| • 32746: SDM_Motion_Action not allowed (Motion Trace already started by SDM) |
| • 32747: SDM_Motion_Action: DataAddress is zero or defined |
| • 32748: SDM_Motion_Action: DataLen is zero or defined |
| • 32749: SDM_Motion_Action: BrModName is too long |
| • 32750: SDM_Motion_Action: BrModName is not defined |
| • 32751: SDM_Motion_Action: FileName is not defined |
| • 32752: SDM_Motion Action not possible: AR function does not exist (see Logger) |
| • 32753: SDM_Motion_Action: CREATE_NCOBJ_LIST must be called before this action |
| • 32754: SDM_Motion_Action: The NC object type is invalid for this action |
| • 32755: SDM_Motion_Action: Memory free error |
| • 32756: SDM_Motion_Action: Memory alloc error |
| • 32757: SDM_Motion_Action: This action is not yet implemented |
| • 32758: SDM_Motion_Action: The NC object ident is invalid for this action |
| • 32759: SDM_Motion_Action: The NC object ident must be zero for this action |
| • 32760: SDM_Motion_Action: Pointer of exit function arguments is zero or not defined |
| • 32761: SDM_Motion_Action: Pointer of exit function is zero or not defined |
| • 32762: SDM_Motion_Action: The first XML element in input data is invalid |
| • 32763: SDM_Motion_Action: No XML element in input data |
| • 32764: SDM_Motion_Action: Error initializing memory buffer for XML parser |
| • 32765: SDM_Motion_Action: Length of XML input data is zero |
| • 32766: SDM_Motion_Action: Pointer of XML input data is zero |
| • 32767: SDM_Motion_Action: Invalid actionID |
| • 33000: Master cycle time is not a multiple of communication cycle time |
| • 33002: Floating-Point exception |
| • 33003: Address error exception |
| • 33004: Bus error exception |
| • 33005: Exception |
| • 33006: Access violation Exception |
| • 33007: Violation address |
| • 33008: FPGA: CRC error: Address |
| • 33009: FPGA: CRC error: Byte |
| • 35000: SMC Fail Safe: Internal error, Program flow |
| • 35001: SMC Fail Safe: Internal error, NULL pointer access |
| • 35002: SMC Fail Safe: Internal error, SPI transfer |
| • 35003: SMC Fail Safe: Internal error, MFW NVM data memory |
| • 35004: SMC Fail Safe: Internal error, Communication EnDat Master |
| • 35005: SMC Fail Safe: Internal error, Communication ACOPOS |
| • 35006: SMC Fail Safe: Internal error, Communication Encoder |
| • 35016: SMC Fail Safe: Internal error, Cross communication of checkpoints |
| • 35017: SMC Fail Safe: Internal error, Cross communication of statusword |
| • 35018: SMC Fail Safe: Internal error, Cross communication of output state |
| • 35019: SMC Fail Safe: Internal error, Cross communication of EnDat position |
| • 35020: SMC Fail Safe: Internal error, Cross communication of EnDat error register |
| • 35021: SMC Fail Safe: Internal error, Cross communication of EnDat state machine |
| • 35022: SMC Fail Safe: Internal error, Cross communication of EnDat state machine |
| • 35023: SMC Fail Safe: Internal error, Cross communication of EnDat state machine |
| • 35024: SMC Fail Safe: Encoder configuration – Units per number of revolution invalid |
| • 35025: SMC Fail Safe: Encoder configuration – Normalized maximal speed invalid |
| • 35026: SMC Fail Safe: Encoder configuration – Encoder resolution too low |
| • 35027: SMC Fail Safe: Encoder configuration – Encoder resolution too high |
| • 35028: SMC Fail Safe: Encoder configuration – Units resolution too high |
| • 35029: SMC Fail Safe: Encoder configuration – One unit is shorter than one nm |
| • 35030: SMC Fail Safe: Encoder mismatch – Configuration data changed several times |
| • 35031: SMC Fail Safe: Encoder mismatch – Configuration data changed |
| • 35032: SMC Fail Safe: Wrong parameterization |
| • 35033: SMC Fail Safe: Modul cycle time is not valid |
| • 35034: SMC Fail Safe: Parameterization – Deceleration ramp is too steep |
| • 35035: SMC Fail Safe: Internal state machine is in Fail Safe State |
| • 35036: SMC Fail Safe: Deactivated safety function was requested |
| • 35037: SMC Fail Safe: SMS – Speed limit is out of range |
| • 35038: SMC Fail Safe: SLS1 – Speed limit is out of range |
| • 35039: SMC Fail Safe: SLS2 – Speed limit is out of range |
| • 35040: SMC Fail Safe: SLS3 – Speed limit is out of range |
| • 35041: SMC Fail Safe: SLS4 – Speed limit is out of range |
| • 35042: SMC Fail Safe: Standstill speed limit is out of range |
| • 35043: SMC Fail Safe: SLS1 – Speed limit violates the configuration instruction |
| • 35044: SMC Fail Safe: SLS2 – Speed limit violates the configuration instruction |
| • 35045: SMC Fail Safe: SLS3 – Speed limit violates the configuration instruction |
| • 35046: SMC Fail Safe: SLS4 – Speed limit violates the configuration instruction |
| • 35047: SMC Fail Safe: Standstill Speed limit violates the configuration instruction |
| • 35048: SMC Fail Safe: Violation of parameter limits |
| • 35049: SMC Fail Safe: SMP is used but Homing was not configured |
| • 35050: SMC Fail Safe: SMP – Lower position limit is greater or equal than upper limit |
| • 35051: SMC Fail Safe: SLP is used but Homing was not configured |
| • 35052: SMC Fail Safe: SLP – Lower position limit is greater or equal than upper limit |
| • 35053: SMC Fail Safe: SLP – Position window outside SMP position window |
| • 35054: SMC Fail Safe: SMP – Tolerance is greater than SMP position window |
| • 35055: SMC Fail Safe: SLP – Tolerance is greater than SLP position window |
| • 35056: SMC Fail Safe: Value of Deceleration ramp is out of range |
| • 35068: SMC Fail Safe: Homing – Max. trigger speed is out of range |
| • 35069: SMC Fail Safe: Homing – Ref Switch: No reference switch connected |
| • 35070: SMC Fail Safe: Homing – Home Offset: No absolute encoder connected |
| • 35071: SMC Fail Safe: Homing – Home Offset with Correction: SMP not configured |
| • 35072: SMC Fail Safe: Homing – SMP window is greater than safe absolute encoder range |
| • 35073: SMC Fail Safe: Homing – SLP window is greater than safe absolute encoder range |
| • 35074: SMC Fail Safe: Homing – Encoder doesn’t support a safe reference pulse |
| • 35075: SMC Fail Safe: Homing – Speed tolerance is out of range |
| • 35076: SMC Fail Safe: Homing – reference pulse : Max. trigger speed is too big |
| • 35077: SMC Fail Safe: Homing – Function is requested but not configured |
| • 35078: SMC Fail Safe: Homing – RefSwitch bit is set but not configured |
| • 35079: SMC Fail Safe: Homing – Position is out of SMP window |
| • 35080: SMC Fail Safe: Homing – Direct with reference pulse: Not supported |
| • 35081: SMC Fail Safe: Internal error, Cross communication of output signals |
| • 35082: SMC Fail Safe: Internal error, Cross communication of output state machine |
| • 35084: SMC Fail Safe: Program error in PreOperational state |
| • 35085: SMC Fail Safe: Safe output – Stuck at high detected |
| • 35086: SMC Fail Safe: Safe output – Test state has changed |
| • 35087: SMC Fail Safe: Encoder – Speed limit exceeded |
| • 35088: SMC Fail Safe: Encoder – Acceleration limit exceeded |
| • 35091: SMC Fail Safe: Encoder mismatch detected |
| • 35092: SMC Fail Safe: Internal error, Lockbit set |
| • 35093: SMC Fail Safe: Velocity error tolerance too large |
| • 35094: SMC Fail Safe: Lag error tolerance too large |
| • 35095: SMC Fail Safe: Encoder – Configuration error |
| • 35096: SMC Fail Safe: Homing – Configuration error |
| • 35153: SMC: Interner error, CUnit test |
| • 35161: SMC Fail Safe: Incompatible parameter structure |
| • 35162: SMC Fail Safe: Incompatible axis type |
| • 35163: SMC Fail Safe: Error in PreOperational function |
| • 35197: SMC Functional Fail Safe: SS2, SOS Violation of standstill position tolerance |
| • 35198: SMC Functional Fail Safe: Encoder error was detected |
| • 35199: SMC Functional Fail Safe: SDI – Violations of the safe direction |
| • 35200: SMC Functional Fail Safe: SDI – Violation of the positive direction |
| • 35201: SMC Functional Fail Safe: SDI – Violation of the negative direction |
| • 35202: SMC Functional Fail Safe: SLI – Violation of standstill speed limit |
| • 35203: SMC Functional Fail Safe: SLI – Violation of position window (increments) |
| • 35204: SMC Functional Fail Safe: Violation of the actual speed limit |
| • 35205: SMC Functional Fail Safe: Violation of the deceleration ramp |
| • 35206: SMC Functional Fail Safe: SMS – Violation of the speed limit |
| • 35207: SMC Functional Fail Safe: SOS – Violation of the speed limit |
| • 35208: SMC Functional Fail Safe: SS2 – Violation of the speed limit |
| • 35209: SMC Functional Fail Safe: SLS1 – Violation of the speed limit |
| • 35210: SMC Functional Fail Safe: SLS2 – Violation of the speed limit |
| • 35211: SMC Functional Fail Safe: SLS3 – Violation of the speed limit |
| • 35212: SMC Functional Fail Safe: SLS4 – Violation of the speed limit |
| • 35213: SMC Functional Fail Safe: Alive test of set position was not executed |
| • 35214: SMC Functional Fail Safe: Warning on output was not acknowledged |
| • 35215: SMC Functional Fail Safe: Alive test – Monitoring timeout |
| • 35216: SMC Functional Fail Safe: SMP – Homing timeout exceeded |
| • 35217: SMC Functional Fail Safe: SMP – Violation of the deceleration ramp |
| • 35218: SMC Functional Fail Safe: SLP – Violation of the deceleration ramp |
| • 35219: SMC Functional Fail Safe: SMP – Violation of lower SMP limit |
| • 35220: SMC Functional Fail Safe: SMP – Violation of upper SMP limit |
| • 35221: SMC Functional Fail Safe: SLP – Violation of lower SLP limit |
| • 35222: SMC Functional Fail Safe: SLP – Violation of upper SLP limit |
| • 35223: SMC Functional Fail Safe: SMP – Movement in neg. direction outside SMP limit |
| • 35224: SMC Functional Fail Safe: SMP – Movement in pos. direction outside SMP limit |
| • 35225: SMC Functional Fail Safe: SLP requested, axis is not homed yet |
| • 35226: SMC Functional Fail Safe: SMP, SLP – Internal error |
| • 35227: SMC Functional Fail Safe: SMP, SLP – INT32 overflow of absolute position |
| • 35228: SMC Functional Fail Safe: Homing – Timeout elapsed |
| • 35229: SMC Functional Fail Safe: Homing – Standstill Speed tolerance violated |
| • 35230: SMC Functional Fail Safe: Homing reference pulse – Max. trigger speed exceeded |
| • 35231: SMC Functional Fail Safe: Homing – Movement invalid |
| • 35232: SMC Functional Fail Safe: Homing offset – Position outside INT32 range |
| • 35233: SMC Functional Fail Safe: Homing offset – Violation of safe encoder range |
| • 35234: SMC: Encoder mismatch – Length of encoder configuration data changed |
| • 35235: SMC: Encoder mismatch – Serial number of encoder changed |
| • 35236: SMC: Encoder mismatch – Version changed or no encoder data stored |
| • 35237: SMC: Encoder mismatch – EnDat master configuration register changed |
| • 35238: SMC: Encoder – EnDat Master state error register is set |
| • 35239: SMC Functional Fail Safe: Homing failed |
| • 35240: SMC Functional Fail Safe: Violation of safety function |
| • 35241: SMC Functional Fail Safe: Function block switched back into IDLE state |
| • 35243: SMC Functional Fail Safe: Safe output – Teststate has changed |
| • 35244: SMC: Encoder – Received position not valid |
| • 35245: SMC: Encoder mismatch detected |
| • 35246: SMC: Encoder – Initialization error |
| • 35247: SMC: Encoder – Debug information |
| • 35248: SMC: Internal error, Lockbit set |
| • 35249: SMC: Encoder – SafeSpeed exceeded INT16 range |
| • 35250: SMC: Encoder – EnDat Master encoder error register is set |
| • 35251: SMC: Velocity error limit exceeded |
| • 35252: SMC: Position lag error limit exceeded |
| • 35253: SMC: Encoder – Rounding error due to parametrization |
| • 35254: SMC: Encoder – Length of physical reference system too large |
| • 35255: SMC Fail Safe: Encoder – Acceleration limit exceeded |
| • 36001: Parameter limited to valid range |
| • 36002: Total time for the position loop controller limited to prediction time |
| • 37101: Calculated compensation distance on slave axis limited to maximum |
| • 37102: Calculated compensation distance on slave axis limited to minimum |
| • 37103: Slave trigger outside of window |
| • 37104: Slave trigger missing |
| • 37105: Master compensation trigger outside of window |
| • 37107: Displacement actual/set position too high during ‘controller switch on’ |
| • 37108: Calculated compensation distance of master axis limited to minimum |
| • 37109: Master trigger outside of window |
| • 37110: Master position at start higher than first trigger position |
| • 37111: Cam profile data: Difference between polynomial value y(xn) and slave period |
| • 37112: Polynomial within cam profile data exceeds limit value |
| • 37113: Cam profile compensation gears: Limit values exceeded |
| • 38000: Current controller: Motor speed is too high during switching on |
| • 38001: Torque limiter: Limit value too high |
| • 38003: Motor holding brake: Test torque was limited |
| • 38004: Motor holding brake: Test torque less than load torque |
| • 38005: Motor test: Speed is too high during switch on |
| • 38006: Current controller: Permissible current offset values exceeded |
| • 38007: System administration: BsLoader activ: Jumper plugged |
| • 38008: Bleeder: No current flow |
| • 38100: Memory test: Read error |
| • 38101: Memory test: Write error |
| • 39001: Encoder: Position correction active |
| • 39002: Resolver: Speed limit for 14 bit resolution exceeded |
| • 39003: EnDat encoder: Alarm bit is set |
| • 39004: EnDat encoder: Alarm bit – Lighting failure |
| • 39005: EnDat encoder: Alarm bit – Signal amplitude too small |
| • 39006: EnDat encoder: Alarm bit – Position value contains an error |
| • 39007: EnDat encoder: Alarm bit – Overvoltage |
| • 39008: EnDat encoder: Alarm bit – Undervoltage |
| • 39009: EnDat encoder: Alarm bit – Overcurrent |
| • 39010: EnDat encoder: Alarm bit – Battery change required |
| • 39011: EnDat encoder: Warning bit – Frequency too high |
| • 39012: EnDat encoder: Warning bit – Temperature too high |
| • 39013: EnDat encoder: Warning bit – Lighting reserve reached |
| • 39014: EnDat encoder: Warning bit – Battery charge too low |
| • 39016: Incremental encoder emulation: Frequency too high |
| • 39017: Encoder: CRC error while reading position |
| • 39018: Reference pulse monitoring: Faulty position, resolution, or reference pulse |
| • 39019: Serial encoder interface: Stop bit error |
| • 39020: Serial encoder interface: Receive data overrun |
| • 39021: Serial encoder interface: Send data error |
| • 39022: EnDat encoder: Warning bit is set |
| • 39023: EnDat encoder: CRC error while reading EnDat2.2 additional information |
| • 39024: EnDat encoder: Operating status error sources: M ALL Power down |
| • 39025: EnDat encoder: Operating status error sources: M Overflow / Underflow |
| • 39026: EnDat encoder: Type 3 error while reading EnDat2.2 additional information |
| • 39027: Encoder Emulation: 5V power supply fail |
| • 39028: Encoder: Multiturn failure |
| • 39029: Encoder: Battery charge too low |
| • 39030: Encoder: Warning bit is set |
| • 39031: Encoder: Timeout error during parameter transfer |
| • 39032: EnDat encoder: Operating status error sources: Lighting |
| • 39033: EnDat encoder: Operating status error sources: Signal amplitude |
| • 39034: EnDat encoder: Operating status error sources: S Pos 1 |
| • 39035: EnDat encoder: Operating status error sources: Overvoltage |
| • 39036: EnDat encoder: Operating status error sources: Undervoltage |
| • 39037: EnDat encoder: Operating status error sources: over current |
| • 39038: EnDat encoder: Operating status error sources: Temperature exceeded |
| • 39039: EnDat encoder: Operating status error sources: S Pos |
| • 39040: EnDat encoder: Operating status error sources: S sytem |
| • 39041: EnDat encoder: Operating status error sources: S ALL power down |
| • 39042: EnDat encoder: Operating status error sources: M Pos 1 |
| • 39043: EnDat encoder: Operating status error sources: M Pos 2 |
| • 39044: EnDat encoder: Operating status error sources: M System |
| • 39045: EnDat encoder: Operating status error sources: M battery |
| • 39301: Digital IO: 24V power supply fail |
| • 39302: Digital IO 1-4: Diagnose bit active (current, 24V supply) |
| • 39303: Digital IO 5-8: Diagnose bit active (current, 24V supply) |
| • 39305: Digital IO 10: Diagnose bit active (current, temperature) |
| • 39306: Digital IO 9: Diagnose bit active (current, temperature) |
| • 39307: Digital IO: outputs deactivated by output mask after network error |
| • 40000: Parameter ID only for tests |
| • 41001: Heatsink temperature sensor: Overtemperature |
| • 41011: Temperature sensor (Motor|Choke|External): Overtemperature |
| • 41031: Junction temperature model: Overtemperature |
| • 41041: Bleeder temperature model: Overtemperature |
| • 41051: ACOPOS peak current: Overload |
| • 41061: ACOPOS continuous current: Overload |
| • 41070: Motor temperature model: Overtemperature |
| • 41075: ACOPOS continuous power: Overload |
| • 41078: Power stage: Temperature sensor 1: Overtemperature |
| • 41080: Charging resistor: Overtemperature |
| • 41081: Power stage temperature model: Overtemperature |
| • 41083: Power stage: Temperature sensor 2: Overtemperature |
| • 41085: Power stage: Temperature sensor 3: Overtemperature |
| • 41087: Power stage: Temperature sensor 4: Overtemperature |
| • 41089: Motor encoder temperature sensor: Overtemperature |
| • 64002: Delay before SW Reset (network with ascending node numbers ?) |
| • 64003: Delay before NC System Start (network with ascending node numbers ?) |
| • 64004: The following boot error could be entered here with a delay |
| • 64005: Timeout for parameter enable after start of operating system |
| • 64006: Drive did not become synchronous with network master |
| • 64007: Timeout for enable of acyclic network communication |
| • 64008: Timeout for enable of cyclic network communication |
| • 64009: Acp10cfg contains a POWERLINK interface, for which no axis is defined |
| • 64010: NC software test version (validity period in Logger) |
| • 64011: Timeout for completion of encoder initialization |
| • 64012: acp10sys does not contain an operating system for this ACOPOS hardware type |
| • 64500: Positive speed limiter active |
| • 64501: Negative speed limiter active |
| • 64502: Positive direction acceleration torque limiter active |
| • 64503: Negative direction acceleration torque limiter active |
| • 64504: Positive direction deceleration torque limiter active |
| • 64505: Negative direction deceleration torque limiter active |
| • 64506: Recovery power limiter active (deceleration too high) |
| • 65535: Response error |
Servomotions Elektrik Motor Bakım Teknolojileri A.Ş. 