CM592-DP PROFIBUS DP Slave View

Note

The PROFIBUS Slave diagnosis must be enabled explicit by the user every time he opens this view (the enabled state will not be saved). This has the following reason:

Each time, when a diagnosis read request is sent to a Slave which has actual diagnostic data, the diagnosis data is automatically acknowledged. Thus, an alarm handling Function Block running on PLC, will possibly miss this alarm. So enabling this view should only be done, if no Function Blocks are used to handle alarms/diagnosis data.

The meaning of Station Status 1:

Station Status 1	Activated by	Description and Remedy
Master Lock (Bit 7)	Master	Description: The Slave has been parameterized by another Master, and is locked for accesses by the selected Master.
		Remedy: This is a safety mechanism of PROFIBUS DP. Firstly, you should decide which Master should have access to the Slave. After that, the Slave has to be added into the configuration of that Master, which should have access to the Slave. Finally, the Slave must be deleted in the configuration of the other Master(s).
Parameter Error (Bit 6)	Slave	Description: This bit is set by the Slave automatically, if the parameter, which the Master has output, is wrong or incomplete. Each received partner telegram is checked completely by the Slave. If the Slave recognises an error, it will report an parameter error. Furthermore, the Slave verifies its ident number with the ident number the Master has sent.
		Remedy: Firstly, verify the ident number inside the device with the ident number inside the GSD file. They must me equal. If they are different, there is either a the wrong GSD file used or a wrong device has been connected to the bus. If both ident numbers are equal, check the parameter data.
Invalid Slave answer (Bit 5)	Master	Description: This bit is set by the Master, if an invalid reply from the Slave has been received. The physical connection to the Slave has been established, but the logical answer could not be understood.
		Remedy: There can be an error on the physical cable line, e. g. interchanged wires, missing bus termination or missing shield connection. Use a PROFIBUS DP Slave, which is corresponding to the norm. This error can also happen, if a PROFIBUS-FMS Slave is connected instead of a PROFIBUS DP Slave to the DP Master. Then the Slave cannot understand the TP telegram and returns it to the sender. It will be recognized by the Master as an invalid Slave reply.
Function not supported (Bit 4)	Slave	Description: This bit is set by the Slave, if it should process a function it does not support. No version of Slaves normally support Sync- and Freeze commands. This is mentioned inside the GSD file and is read by Automation Builder and sent as parameter telegram to the Slave.
		Remedy: If this error occurs, the GSD file contains at least 1 function, which is not supported by the Slave. Ask the device vendor for the correct GSD file which belongs to the Slave.
Enhanced device diagnosis available (Bit 3)	Slave	Description: This bit is set by the Slave, if enhanced diagnosis data have been read. These data are optional and are used by the Slave to output vendor-specific diagnosis messages.
		Remedy: Activate the enhanced diagnosis to display the enhanced diagnosis data and read the manual of the device vendor for the meaning. If the GSD file contains information about the enhanced device diagnosis, the evaluation can also be threatened by the DTM.
Configuration error (Bit 2)	Slave	Description: During the PROFIBUS DP initialization, the Slave compares its internal I/O configuration to the configuration of the Master. If the Slave recognises a difference, it will report a configuration error. This means the master has an other I/O constellation than the Slave.
		Remedy: Firstly, check each I/O Module of the Slave if they are equal to the really connected modules. Pay attention that also the sequence of the modules must be identically. Some Slaves need at the beginning virtual I/O Modules or empty modules to achieve an even number of modules. This Slave-specific behaviour should be mentioned in the vendor manual as it cannot be read inside the GSD file. Pay attention to the configuration hints of the device vendor.
Station not ready (Bit 1)	Slave	Description: The PROFIBUS DP Slave is not ready for data exchange yet.
		Remedy: The reason or point of time a Slave sets this bit, is not specified inside the norm, i. e. several causes could be happened. Mostly this error occurs combined with other errors. Verify the parameters and the configuration. The error Station not ready is often a consecution of a parameter or configuration error. Eventually, the power supply of the Slave has just been turned on. Wait until the device has started.
Station is not existing (Bit 0)	Master	Description: This bit is set automatically by the Master if the Slave in the bus does not reply or is not reachable.
		Remedy: Check the PROFIBUS cable. Both signal lines must be connected correctly between all devices. Additionally, both cable ends must be equipped with terminators. Check the power supply connection of the Slave. Check the Slave station address and the configuration of the Master. Verify, whether the Slave supports the configured baudrate. Some older Slaves will only work up to 1.5 MBaud or must be set to a special PROFIBUS DP conform behaviour.

The meaning of Station Status 2:

Station Status 1	Activated by	Description
Slave deactivated (Bit 7)	Master	This bit is set by the Master, if the parameterization of the Slave marks itself as inactive. Thus, it will be excluded from the cyclically data exchange.
Reserved (Bit 6)	-	-
Sync Mode (Bit 5)	Slave	This bit is set by the Slave, if a Sync command has been received.
Freeze Mode (Bit 4)	Slave	This bit is set by the Slave, if a Freeze command has been received.
Watchdog active (Bit 3)	Slave	This bit is set by the Slave, if time monitoring is activated for controlling the communication with the associated Master.
Slave device (Bit 2)	Slave	This bit is always set by the Slave.
Static diagnosis (Bit 1)	Slave	This bit is set by the Slave to signal the Master, that it has a general error and is out of order. Typically, the Slave is not available for the exchange of user data. In this case, the Master should request diagnosis data as long as the bit is set to 0 again. The event or point of time the bit is set, is not described in the norm and cannot be specified more precisely.
Re-parameterization requested (Bit 0)	Slave	This bit is set by the Slave to signal the Master, that it asks for a new parameterization. The bit stays set until the parameterization is processed. If this error occurs, firstly compare the ident number of the device with the ident number inside the GSD file. These numbers must match. Additionally, check the parameter data.

The meaning of Station Status 3:

Station Status 1	Activated by	Description
Overflow enhanced diagnosis (Bit 7)	Master Slave	This bit is set, if more enhanced diagnosis data are sent to the Master than match into a diagnosis telegram. For example, the Slave sets this bit, if more diagnosis data are pending than fit into its buffer.
Reserved (Bit 6)	-	-

Note

The display of the extended diagnosis of a PROFIBUS Slave is not supported.

Diagnosis	Description
Assigned to master address	At Assigned to master address, the address of the Master, which has parameterized and configured the Slave, is displayed. The value 255 shows that the Slave is neither parameterized nor configured or the received parameterization and configuration information was rejected with errors.
Slave station ident number	At Slave station ident number, the (real) ident number of the used Slave is displayed. If the value 0000 is shown, the Master has no connection to the PROFIBUS DP Slave yet.
Update	Updates the displayed diagnosis conditions.

Note

The ident number, deposited in the device, must match to the ident number in the GSD file. If they are different, either a wrong GSD file is used or the wrong device is connected to the PROFIBUS.