0xC20A

Status codes with diagnosis class "operational state" (0xC20A)

-

0xC20A6404

Successful activation of a language file

A language file which was written to the slave was successfully loaded. See also Loadable languages.

0xC20AA010

The device has been restarted (Power on)

See FG State Machine

0xC20AA100

Wrong password entered

See FG Administration

0xC20AA110

Password write protection deactivated

See FG Administration

0xC20AA120

Password changed

See FG Administration

0xC20AA200

Diagnostic trace started

See FG Diagnosis

0xC20AA210

Diagnostic trace stopped

See FG Diagnosis

0xC20AA220

Diagnostic trace buffer overrun

See FG Diagnosis

0xC20AA300

Test IDN written

See FG Conformance Test SCP, FG Conformance Test GDP, FG Conformance Test FSP_IO

0xC20C0200

S-0-0422 Exit parameterization level procedure command

See FG State Machine

0xC20C0201

S-0-0422: Incorrect or incomplete set of parameters (See S-0-0423 IDN-list of invalid data for parameterization level)

See FG State Machine

0xC20C0202

S-0-0422: Parameter limit violation (See S-0-0423 IDN-list of invalid data for parameterization level)

See FG State Machine

0xC20C0203

S-0-0422: Parameter conversion error (See S-0-0423 IDN-list of invalid data for parameterization level)

See FG State Machine

0xC20C0400

S-0-0420 Activate parameterization level procedure command (PL)

See FG State Machine command in process

0xC20C0401

S-0-0420: Switching to parameterization level is not possible

See FG State Machine

Device refuses to switch to PM, for example as outputs are currently enabled, disable first

0xC20C0500

S-0-0099 Reset class 1 diagnostic

See FG Diagnosis, command in process

0xC20C0700

S-0-0262 Load defaults procedure command

See FG Archiving, command in process

0xC20C0702

S-0-0262: Default parameters not available

No data memory is available, for example, at connected motors. See also FG Archiving Error handling (FG Archiving)

0xC20C0703

S-0-0262: Default parameters invalid

Default parameters are read from a remanent data memory (for example, internal flash memory). At least one of these parameters is invalid or the whole parameters are invalid (for example, due to a incorrect checksum). See also FG Archiving Error handling (FG Archiving)

0xC20C0704

S-0-0262: Parameters not copiable

It was impossible to load default values to respective parameters. This may happen if, for example, the Sercos slaves firmware version is incompatible to connected devices with default parameter storages (for example, motors) or if the read default parameters do not match the parameters in the working memory. See also FG Archiving Error handling (FG Archiving)

0xC20C0706

S-0-0262: Error when reading the default parameter values

This may happen if during the read access to the default parameter set was unsuccessful (for example, due to a defective flash memory circuit). See also FG Archiving Error handling (FG Archiving)

0xC20C2200

S-0-0264 Backup working memory procedure command

See FG Archiving, command in process

0xC20C2202

S-0-0264: Error when writing data to non-volatile memory

It was impossible to write to the non-volatile memory (for example, internal flash memory) without error. See also FG Archiving Error handling (FG Archiving)

0xC20C2300

S-0-0263 Load working memory procedure command

See FG Archiving, command in process

0xC20C2301

S-0-0263: Error when reading non-volatile memory

It was impossible to read from the non-volatile memory (for example, internal flash memory) without error. See also FG Archiving Error handling (FG Archiving)

0xC20C2302

S-0-0263: Error when converting parameters

During the processing of the read default values to the volatile memory, an error occurred. See also FG Archiving Error handling (FG Archiving)

0xC20C2400

S-0-0293 Selectively backup working memory procedure command

See FG Archiving, command in process

0xC20C2402

S-0-0293: Error when saving parameters

It was impossible to write to the non-volatile memory (for example, internal flash memory) without error. See also FG Archiving Error handling (FG Archiving)

0xC20C5000

S-0-1322.0.0 Procedure Command Change Energy Mode

See FG Energy, command in process

0xC20C5003

S-0-1322.0.0: Target Energy Mode ID not valid

The selected Target Energy Mode ID (S-0-1322.0.3 Target EM for Procedure Command Change Energy Mode) is, for example, not existent in case of change energy mode Direct Mode. This will, for example, lead to an S-0-0390 = 0xC20F5003. See also FG Energy Error Handling (FG Energy)

0xC20C5004

S-0-1322.0.0: Energy Mode Change not possible

The energy mode change from the Actual Energy Mode (S-0-1323.0.1 Actual Energy Mode) and the Target Energy Mode (S-0-1322.0.3 Target EM for Procedure Command Change Energy Mode) is not possible (for example, if Actual EM and Target EM are not EM Operational and transition between both modes is not implemented). This will, for example, lead to an S-0-0390 = 0xC20F5004. See also FG Energy Error Handling (FG Energy)

0xC20C5005

S-0-1322.0.0: Energy Mode Change locked by external control

The energy mode change from the Actual Energy Mode (S-0-1323.0.1 Actual Energy Mode) and the Target Energy Mode (S-0-1322.0.3 Target EM for Procedure Command Change Energy Mode) is not possibly caused by a lock of an external energy mode control (for example, if Actual EM is set externally, for example, EM ID 0xF0 and the transition via command is not possible. In this case, the Actual Energy Mode needs to be EM ID 0xEF before switching via S-0-1322.0.0 Procedure Command Change Energy Mode). This will, for example, lead to an S-0-0390 = 0xC20F5005. See also FG Energy Error Handling (FG Energy)

0xC20C6400

S-0-1350 Reboot Device

See Reboot_function, command in process (See FG State Machine)

0xC20C6401

S-0-1350: Reboot not possible

The execution of the procedure command is inhibited internally by the slave.

For example, a drive could be enabled and running or a reboot is actually in progress (See FG State Machine)

0xC20C6500

S-0-1351 Generate archive data procedure command

See Device backup and restore, command in process (See FG Archiving)

0xC20C6501

S-0-1351: Error when creating backup data files

During the creation of the backup data files, an error occurred. This, for example, may happen, if the write access to a non-volatile storage fails. See also Device backup and restore. Depending on the features of the Sercos device, a log file may be present in the backup directory (See FG Archiving)

0xC20C6503

S-0-1351: Inconsistent backup data files

The generation of the backup data files ended with inconsistent data. This may happen due to a change of one or several system files (for example, retain data) during the execution of procedure command S-0-1351 Generate archive data procedure command. See also Device backup and restore. Depending on the features of the Sercos device, a log file may be present in the backup directory (See FG Archiving)

0xC20C6700

S-0-1352 Activate restore data procedure command

See Device backup and restore, command in process (See FG Archiving)

0xC20C6701

S-0-1352: Error when reading the restore data

During the execution of the procedure command, the Sercos device tries to read the directory with the restore data. This read access was erroneous. This may, for example, happen if files to be restored (signaled via RestInfo.xml) are not present or have errors. As a result the restore process could not be executed completely. Depending on the features of the Sercos device, a log file may be present in the restore directory. See also Device backup and restore and FG Archiving

0xC20C6702

S-0-1352: Error when restoring the device data

During the execution of the procedure command, the Sercos device tries to restore data given via files in the restore directory. This restore access was erroneous. This may, for example, happen if files to be restored (signaled via RestInfo.xml) cannot be written to the memory of the device. As a result the restore process could not be executed completely. Depending on the features of the Sercos device, a log file may be present in the restore directory. See also Device backup and restore or FG Archiving

0xC20E0000

Reserved

-

0xC20E6402

Device not fully initialized

During the execution of the reboot procedure (IDN <S-0-1350>), the Sercos slave may reboot several times. During these reboot procedures, the slave shall signal this state using this diagnostic.

0xC20F5001

Time Min Stay violation

The change energy mode was executed too soon. In this case, the device remains in its actual energy mode. This will, for example, lead to an S-0-0390 = 0xC20F5001. See also FG Energy Error Handling. The change energy mode was executed too soon (FG Energy)

0xC20F5002

Time Max Stay exceeded

The change energy mode was not executed within desired time. In this case, the device remains in its actual energy mode. This will, for example, lead to an S-0-0390 = 0xC20F5002. See also FG Energy Error Handling. The change energy mode was not executed within desired time (FG Energy)

0xC20F6403

Failure detected during activation of a language file

A language file which was written to the slave could not be loaded. See also Loadable languages.