DiagnosticNumber

General

Type

AS

Devices supporting the parameter

Safety Logic Controller TM5CSLCx00FS,

Bus Interface TM5NS31,

Sercos I/O

Traceable

Yes

Functional Description

Displays a diagnostic number (IDN S-0-0390).

The DiagnosticNumber corresponds to the Sercos parameter S-0-0390. The structure of the IDN S-0-0390 is given in the following table.

Structure of the IDN S-0-0390

Bit No.

Value

Designation

Notes

31…30

–

Interpretation of bits 29…0

The bits 31…30 specify the interpretation of the group source type, the classes, and the status codes.

00

Manufacturer-specific status codes

The bits 29…16 (type and class) are specified by Sercos.

The bits 15…0 status codes are specified by the manufacturer.

01

Fully manufacturer specific

The bits 29…0 are specified by the manufacturer.

10

Reserved

The bits 29…0 are specified by Sercos.

11

Standard

–

29…24

–

Source type

–

0x00

FSP drive

–

0x01

FSP IO

Further detailed IO-specific information can be found in the following table S-0-1500.x.32.

0x02

GDP

–

0x03

SCP

–

0x04

CSoS

–

0x05

FSP encoder

–

0x06…0x3E

Reserved

–

0x3F

Unknown

–

23…20

–

Reserved

–

19…16

–

Class

–

0x00…0x09

Reserved

–

0x0A

Operational state

Priority 4 (lowest)

For information about the operational state, regarding messages, or other information (for example, Drive STOP or Compatible replacement).

0x0B

Reserved

–

0x0C

Procedure command specific state

Priority 3

For information about the diagnostic events, regarding messages, or other information (for example, Drive STOP or Compatible replacement).

0x0D

Reserved

–

0x0E

Warning (C2D)

Priority 2

0x0F

Error (C1D)

Priority 1 (highest)

Has to be confirmed/acknowledged when using the procedure command S-0-0099 Reset class 1 diagnostic

15…0

–

Status code

–

If diagnostic messages "C1D error" or "C2D warning" are triggered, this parameter can give a more precise explanation of what caused the detected error (also see diagnostic messages "8163 SERCOS: C1D error detected" and "8164 SERCOS: C1D manufacturer-specific error" as well as "8165 SERCOS: C2D warning" and "8166 SERCOS: C2D manufacturer-specific warning").

Example

Example: DiagCodes in the Sercos IDN 390 'Diagnosis Number' for TM5CSLCx00FS or TM5NS31

Safety Logic Controller TM5CSLCx00FS:

  • C10F 1000 hex: S3/BC(ERROR): General error detected

  • 010F 1801 hex: S3/BC(ERROR): General error (manufacturer-specific): Invalid bus controller firmware file

  • 010F 1802 hex: S3/BC(ERROR): General error (manufacturer-specific): Invalid bus controller configuration data

  • 010F 1803 hex: S3/BC(ERROR): General error (manufacturer-specific): Invalid IOM configuration data -> Slot

  • 010F 1804 hex: S3/BC(ERROR): General error (manufacturer-specific): Error detected reading nonvolatile memory

  • 010F 1805 hex: S3/BC(ERROR): General error (manufacturer-specific): Out of bus controller resources

  • 010F 1806 hex: S3/BC(ERROR): General error (manufacturer-specific): Unrecoverable error

  • C10F 6320 hex: S3/BC(ERROR): S3/BC(ERROR): Invalid Reg CFG Data -> Slot

  • 010F 1807 hex: S3/BC(ERROR): General error (manufacturer-specific): Error detected transmitting safe logger data (device was not able to send safe logger entries to the LMC)

  • C30F 0109 hex: Excessive CPU load. Tx and Rx processing overlap. Reduce number of safety-related devices or bus couplers with connected safety-related I/O modules.

Bus Interface TM5NS31: I/O status codes:

  • 0xC10F8100 "S3/BC(ERROR): Monitoring.Communications": Sercos communication error detected

  • 0xC10FB000 "S3/BC(ERROR): Local bus (System bus of the modular station)": General IOM module error detected -> Slot

  • 0xC10EB001 "S3/BC(WARNING): Local bus slave missing": Configured IOM unavailable on local bus -> Slot

  • 0xC10FB002 "S3/BC(ERROR): Incorrect local bus slave present": IOM mismatch -> Slot

  • 0xC10FB004 "S3/BC(ERROR): Local bus devices amount error": IOM unsupported -> Slot

  • 0xC10FB010 "S3/BC(ERROR): Device errors": IOM not successful -> Slot

NOTE: The parameter value is transferred from the slave to the master via the parameter channel of the Sercos by every access. Typically, this takes about 10 ms. However, up to 1 s can be realized if large amounts of data are transferred on the parameter channel. If the Sercos bus is in phase 0 or 1, then a default value is indicated here. If the Sercos bus is in phase 3 or 4, then the parameter value is transferred and indicated. In the Sercos phase 2, the parameter can be read through the application.