Schneider Electric LUFP7 Appendix E Profibus-DP Data and Diagnostics, Bytes Structure Description

12. Appendix E: Profibus-DP Data and Diagnostics

The various elements presented here are detailed in the documentation of the Profibus-DP master you will have to use. In the case of the TSX PBY 100 coupler of the Premium automatic controls, for example, these elements are detailed in the Implementation Manual – TSX PBY 100 – PROFIBUS-DP(ref.: TSX DM PBY 100E), and in the PL7 PRO on line help (help path: Communication Æ Profibus-DP).

However, the most important elements are reproduced here in order to make the LUFP7 gateway easier to use.

12.1. Gateway Profibus-DP Diagnostics

These diagnostics are the gateway's response to a specific command generated by a Profibus-DP master. This command enables the master to check the status of one of its slaves.

In the case of the LUFP7 gateway, the response length is equal to 6 bytes, i.e. the minimum standard and mandatory length for a response to a diagnostic command.

Under PL7 PRO, this response can be viewed in two different ways:

•In the “Debug” screen of the TSX PBY 100 coupler, when the slave whose address corresponds to the gateway's is selected. The gateway Profibus-DP diagnostics are then displayed in the "PROFIBUS-DP diagnostic data". An example is given on the right. It is an excerpt from the screen represented in chapter 4.2.13 Using and Monitoring the TSX PBY 100 Coupler Configuration, page 36.

•Using the SEND_REQ function, the 16#0031 command code, and requesting specifically a diagnostic from the slave concerned.

The table below describes the structure and content of the gateway response to a Profibus-DP diagnostic command sent to it:

Bytes	Structure		Description
0	x0: not_reachable		x0=1 if the slave is non connected or switched off
	x1: not_ready		x1=1 if the slave is not ready for data exchange
	x2	: config_fault	x2=1 if there is a slave configuration error upon test request
	x3	: ext_diag	x3=1 if extended diagnostic (bytes 7-255); x3=0 for the LUFP7 gateway
	x4	: not_supported	x4=1 if the function is not supported by the slave
	x5	: invalid_rsp	x5=1 if there is an error in the slave's first response
	x6	: param_fault	x6=1 if there is an error in the slave's last setting message
	x7	: master_lock	x7=1 if the slave is already set up by another master module
1	x0: prm_required		x0=1 if the slave should be configured and set up again
	x1	: diag_data_rdy	x1=1 if the slave generated a diagnostic to be processed by the master
	x2	: is_slave_diag	x2=0/1 if the diagnostic was created by the master / by the slave
	x3	: wdt_active	x3=1 if the slave's watchdog is active
	x4	: freeze_mode	x4=1 if the selected slave inputs are frozen
	x5	: sync_mode	x5=1 if the selected slave outputs are frozen
	x6	(non utilisé)	——
	x7	: inactive	x7=1 if the slave is inactive (excluded from the processing)
2	x0..x6 (unused)		——
	x7: diag_overflow		x7=1 if the number of diagnostic bytes exceeds the size of the reception words
3	master_address		Address of the master module that sets up the slave
4-5	PNO_identifier		Slave's identification code
6-244	specific_diag (unused)		Optional specific diagnostic data (none for the LUFP7 gateway)

105