Status Codes of the Generic Device Profile (GDP)

-

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

-

-

-

-

-

-

-

-

-

-

-

-

Command in process

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

Command in process

Command in process

No data memory is available, for example, at connected motors.

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).

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.

This may happen if during the read access to the default parameter set was unsuccessful.

Command in process

It was impossible to write to the non-volatile memory (for example, internal flash memory) without error.

Command in process

It was impossible to read from the non-volatile memory (for example, internal flash memory) without error.

During the processing of the read default values to the volatile memory, an error occurred.

Command in process

It was impossible to write to the non-volatile memory (for example, internal flash memory) without error.

Command in process

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.

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.

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.

Command in process

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.

Command in process

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 is not successful. See also Device backup and restore. Depending on the features of the Sercos device, a log file may be present in the backup directory.

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.

Command in process

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.

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.

-

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.

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).

The change energy mode was not executed within defined 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).

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