Burkert 8717 User Manual [en, de, fr]

Type XXXX

MFC Family

- Digital Communication

Fieldbus devices and serial communication (RS 232 / RS 485) Feldbusgeräte und serielle Kommunikation (RS 232 / RS 485) Appareils bus terrain et communication sérielle (RS 232 / RS 485)

Supplement to Operating Instructions

Ergänzung zur Bedienungsanleitung Complément aux instructions de service

We reserve the right to make technical changes without notice. Technische Änderungen vorbehalten!

Sous réserve de modifications techniques.

© 2009 - 2011 Bürkert Werke GmbH

Operating Instructions 1107/08_EU-ML_00804553 / Original DE

MFC Family

Description of Communication with MFC Family Devices

Contents

1.	Supplementary Operating Instructions...............................................................................................................		5
	1.1.	Symbols.......................................................................................................................................................................................	5
2.	General Information................................................................................................................................................................		6
	2.1.	Contact Addresses................................................................................................................................................................	6
	2.2. Information on the Internet...............................................................................................................................................		6
	2.3.	English terms............................................................................................................................................................................	6
3.	Serial Communication.............................................................................................................................................................		7
	3.1.	General Information..............................................................................................................................................................	7
	3.2.	Commands..............................................................................................................................................................................	12
	3.3.	Error messages....................................................................................................................................................................	26
4.	PROFIBUS DP Start-up ...........................................................................................................................................................		30
	4.1. Address setting for BUS devices...............................................................................................................................		30
	4.2.	Technical Data.......................................................................................................................................................................	31
	4.3.	DP alarm mode.....................................................................................................................................................................	31
	4.4.	PROFIBUS PDI/PDOs.......................................................................................................................................................	31
	4.5. Explanation of variables used in cyclic data traffic...........................................................................................		32
	4.6.	Acyclic data.............................................................................................................................................................................	33
5.	DeviceNet Start-up..................................................................................................................................................................		34
	5.1.	Terms.........................................................................................................................................................................................	34
	5.2. Configuration of Process Data.....................................................................................................................................		35
	5.3.	Acyclic data.............................................................................................................................................................................	35

3

english

MFC Family

6.	CANopen Start-up.....................................................................................................................................................................		36
	6.1.	CANopen general................................................................................................................................................................	36
	6.2.	CANopen emergency........................................................................................................................................................	39
	6.3. CANopen – Service Data Transfer.............................................................................................................................		43
	6.4. CANopen – Process Data Transfer............................................................................................................................		44
	6.5. CANopen – Communication Object..........................................................................................................................		50
	6.6.	Acyclic data.............................................................................................................................................................................	50
7.	Acyclic Data Transfer with PROFIBUS, DeviceNet and CANopen...................................................		51
	7.1.	CANopen-Manufactory Object.....................................................................................................................................	51
	7.2.	CANopen-Identity Object................................................................................................................................................	51
	7.3.	DeviceNet S-Identity Object..........................................................................................................................................	52
	7.4.	S-Analog Sensor Object..................................................................................................................................................	53
	7.5.	S-Analog Actuator Object...............................................................................................................................................	54
	7.6. S-Single Stage Controller Object...............................................................................................................................		56
	7.7. Bürkert General Description Object..........................................................................................................................		57
	7.8. Bürkert MFC Family Object............................................................................................................................................		57
8.	Starting up the Modbus.....................................................................................................................................................		66
	8.1.	General Information...........................................................................................................................................................	66
	8.2.	Modbus in general..............................................................................................................................................................	66
	8.3. Modbus register and communication objects.....................................................................................................		70
9.	Annex....................................................................................................................................................................................................		79
	9.1. Description of bit fields....................................................................................................................................................		79
	9.2.	Table of units.........................................................................................................................................................................	83

4

english

MFC Family

SupplementaryOperatingInstructions

1.Supplementary Operating Instructions

The Supplementary Operating Instructions describe communication with MFC family devices.

Safety Information!

Safety instructions and information for using the device may be found in the corresponding operating instructions.

• The operating instructions must be read and understood.

1.1.Symbols

Danger!

Warns of an immediate danger!

• Failure to observe the warning may result in a fatal or serious injury.

Warning!

Warns of a potentially dangerous situation!

• Failure to observe the warning may result in serious injuries or death.

Caution!

Warns of a possible danger!

• Failure to observe this warning may result in a moderate or minor injury.

Note!

Warns of damage to property!

• Failure to observe the warning may result in damage to the device or the equipment.

indicates important additional information, tips, and recommendations which are important for your safety and the flawless functioning of the device.

refers to information in these operating instructions or in other documentation.

→→designates a procedure that must be carried out.

5

english

MFC Family

General Information

2.General Information

2.1.Contact Addresses

Germany

Contact address:

Bürkert Fluid Control System

Sales Center

Chr.-Bürkert-Str. 13-17

D-74653 Ingelfingen

Phone: 07940 - 10 91 111

Fax: 07940 - 10 91 448

E-mail: [e-mail]

International

Contact addresses can be found on the final pages of the printed operating instructions.

And also on the Internet at:

www.burkert.com

2.2. Information on the Internet

The operating instructions and data sheets for device types can be found on the Internet at:

www.burkert.com

Complete documentation is also available on CD and can be ordered under ID number 804625.

2.3. English terms

English technical terms and proper nouns appear just as they were in the original German version (i.e. in English). The English variables and function names, etc. that were used in the German version are also unchanged in the English version.

6

english

MFC Family

Serial Communication

3.Serial Communication

3.1.General Information

3.1.1.RS232 - Driver included in the device

(e.g. for types 8626/8006, 8716/8706, 8712/8702)

MFC / MFM	PC (SUB-D 9-pin plug)
RS232 TxD (pin 6 SUB-HD socket)	Pin 2
RS232 RxD (pin 14 SUB-HD socket)	Pin 3
RS232 GND (pin 15 SUB-HD socket)	Pin 5

3.1.2.RS232 - Driver not included in the device

(e.g. for type 8711/8701)

MFC / MFM

TxD	From device	(pin 15 SUB-D plug)
RxD	From device	(pin 14 SUB-D plug)
GND	From device	(pin 11 SUB-D plug)

3.1.3.Transfer protocol

Transfer channels

The following lines are used for the serial interface:

Wire-conducted communication

GND	Ground
RxD	Reception line (as seen by MFC)
TxD	Transmission line (as seen by MFC)

Data format

The layout of the serial interface protocol is as follows:

Transfer rate	Standard 9600 Bd (differs from HART)
Data bits	8
Parity	None (differs from HART)
Stop bits	1
Hardware handshake	No

7

english

MFC Family

Serial Communication

Telegram

General Information

The layout of the transmission telegram is based on the HART protocol. HART is a master slave protocol, i.e. each transmission is started by a master device (PC or manual operating unit). The slave device (field device, MFC / MFM) responds only to a master telegram if the device was addressed by the telegram.

Exception: Burst message

Additional information about the HART protocol may be found under: http://www.hartcomm.org/

http://www.romilly.co.uk/

A distinction is drawn between short frame and long frame telegrams. They consist of the following characters:

Short frame
Preamble	2 – 20 bytes 0xFF
Delimiter	1 byte
	Master	→ Slave			0x02
	Slave	→ Master			0x06
	Burst message				0x01
Address	1 byte
	(Master address + Burst info + Polling address)
Command	1 byte
Byte count	1 byte
Status	2 bytes, for slave			Master
	(for meaning see “3.3. Error messages” )
Data	0 – 255 bytes
Checksum	1 byte
Long frame
Preamble	2 – 20 bytes 0xFF
Delimiter	1 byte
	Master	→ Slave			0x82
	Slave	→ Master			0x86
	Burst message				0x81
Address	5 bytes
Command	5 bytes
Byte count	1 byte
Status	2 bytes, for slave			Master
	(for meaning see “3.3. Error messages”)
Data	0 – 255 bytes
Checksum	1 byte

8

english

MFC Family

Serial Communication

Preamble

The preamble consists of 2 to 20 0xFF characters (differs from HART). It is used to synchronize the data transfer.

Delimiter

Telegrams are distinguished from each other mainly by the delimiter:

Message type		Short frame	Long frame
Master → Slave		0x02	0x82
Slave → Master		0x06	0x86
Burst message from slave		0x01	0x81
Master:	PC or manual operating unit
Slave:	Field device, MFC/MFM

Address

The address field contains both the master address and the slave address of the message. One byte is used for this purpose in a short frame, while 5 bytes are used in a long frame. Each device must respond to a long frame address of 0 (= broadcast address), i.e. bit 0/1=X, bits 0 – 37=0.

The highest-order bit in both formats indicates which master is involved in communication.

(1: Primary master, continuously connected hosts; 0: Secondary master, manual operating units)

Short frame address (1 byte)

Bit 7	0	Secondary master
	1	Primary master
Bit 6	0	Not in burst mode
	1	In burst mode (not supported)
Bits 0 – 5	Polling address (0 – 32), bit 5 = MSB, bit 0 = LSB
m b x x x x x x
	x	Polling address
	b Burst info
	mMaster address

9

english

MFC Family

Serial Communication

Long frame address (5 bytes)

Bit 39	0: Secondary master
	1: Primary master
Bit 38	0: Not in burst mode
	1: In burst mode (not supported)
Bits 32 – 37	Manufacturer's ID code (0x78 = Buerkert),
	Bit 37 = MSB, bit 32 = LSB
Bits 24 – 31	Device type code (0xEE = Mass flow controller/meter),
	Bit 31 = MSB, bit 24 = LSB
Bits 0 – 23	Device ID number,
	Bit 23 = MSB, bit 0 = LSB
	(matches the device serial number)
	Each field unit must respond to address 0 (bits 0 – 23 = 0).
	Bit 37		Bit 23	Bit 0
	|		|	|
mb x x x x x x x		y y y y y y y y	z z z z z z z z	z z z z z z z z z z z z z z z z
		z	Device ID number
		y	Device type code
		x	Manufacturer's
			ID code
		b	Burst info
		m	Master address

Command

Commands are divided into the following categories in conformity with HART:

Universal commands Commands 0 – 30

Standard commands Commands 32 – 126

Device-specific	Commands 128 – 253
command
	(reserved: 31, 127, 254, 255)

Byte count

The byte count indicates how many more bytes come before the checksum, i.e. the number of status bytes + number of data bytes. This results in a maximum total number of 255 status and data bytes.

Response code

Transferred only from the slave to the master in a response telegram. Consists of 2 bytes. The status bytes are used to detect communication errors or for the operating status of the slave device.

Data

Data bytes, depending on the command. A maximum of 255 data bytes can be transferred.

• Float – IEEE 754 single precision (4 bytes) float

10

english

MFC Family

Serial Communication

Checksum

The checksum is an XOR (exclusive OR, anticoincidence) combination of all bytes from the starting byte (delimiter) up to and including the last data byte.

An XOR combination is the logical combination function of two logical values ("0" and "1"). It yields a result of "1" if one but not both of the two values is "1".

11

english

MFC Family

Serial Communication

3.2.Commands

Command number	0x00
Command name	ReadUniqueldentifier
Request
Command	0x00
Byte count	0
Data	-
Response
Command	0x00
Byte count	14 (18)
Status	2 bytes, device status
Data	12 (16) bytes
	0	"254" (expansion)
	1	manufacturer identification code
	2	manufacturer‘s device type code
	3	number of preambles required
	4	universal command revision
	5	device-specific command revision
	6	software revision
	7	hardware revision
	8	device function flags
	9 – 11 device ID number 1)
	(12	common-practice command revision) 1)
	(13	common tables revision) 2)
	(14	data link revision) 2)
	(15	device family code) 2)

Description

HART-Universal Command 0.

1)First byte transferred: MSB

2)Reserved for later versions

12

english

MFC Family

Serial Communication

Command number	0x01
Command name	ReadPrimaryVariable
Request
Command	0x01
Byte count	0
Data	-
Response
Command	0x01
Byte count	7
Status	2 bytes, device status
Data	5 bytes
	0	PV units code

1 – 4 primary variable (float) 1)

Description

HART-Universal Command 1.

PV Unit	0 x 39 %
PV	Actual flow X (±)

(see also “3.3.3. Codings and units”)

Example:

All data as hexadecimal numbers (prefix 0x) short frame

Primary master

Short address 0

Data sent

Data received

•Read Primary Variable

0xFF 0xFF 0x02 0x80 0x01 0x00 0x83

0xFF 0xFF 0x06 0x80 0x01 0x07 0x00 0x00 0x39 0x41 0xC8 0x00 0x00 0x30 0x39 for PV Unit = %

0x41C80000 = 25.0 IEEE 754 floating point

1) First byte transferred: MSB

13

english

MFC Family

Serial Communication

Command number	0x03
Command name	ReadCurrentAndFourDynamicVariables
Request
Command	0x03
Byte count	0
Data	-
Response
Command	0x03
Byte count	26
Status	2 bytes, device status
Data	24 bytes
	0 – 3	current (mA) (float) 1)
	4	PV units code
	5 – 8	primary variable (float) 1)
	9	SV units code
	10 – 13 secondary variable (float) 1)
	14	TV units code
	15 – 18 third variable (float) 1)
	19	FV units code
	20 – 23 fourth variable (float) 1)

Description

HART-Universal Command 3.

New variable assignment as of firmware version A.00.28.09:

current	Actual flow scaled to 4 – 20 mA
PV Unit	%
PV	Actual flow X (±)
SV Unit	%
SV	Set-point value flow W
TV Unit	%
TV	Positioning set-point value y 2 (valve duty cycle)
FV Unit	sec
FV	device sampling time,
	since power-on or SyncTA command

1) First byte transferred: MSB

14

english

MFC Family

Serial Communication

Command number	0x06
Command name	WritePollingAddress
Request
Command	0x06
Byte count	1
Data	1 byte
	0	polling address
Response
Command	0x06
Byte count	3
Status	2 bytes, device status
Data	1 byte
	0	polling address

Description

HART-Universal Command 6:

Command for changing the HART polling address.

15

english

MFC Family

Serial Communication

Command number	0x27
Command name	EepromControl
Request
Command	0x27
Byte count	1
Data	1 byte
	0	= Write to EEPROM
	1	= Copy content of EEPROM to RAM
Response
Command	0x27
Byte count	3
Status	2 bytes, device status
Data	1 byte
	0	= Write to EEPROM
	1	= Copy content of EEPROM to RAM

Description

HART-Universal Command 39.

Command to write/read parameters (for example the polling address) to/from EEPROM.

16

english

MFC Family

Serial Communication

Command number	0x80
Command name	ReadVersion
Request
Command	0x80
Byte count	0
Data	-
Response
Command	0x80
Byte count	36 2) 3) 4) 5)
Status	2 bytes, device status
Data	34 bytes
	0	– 1	Device type (unsigned int), e.g. 8626
	2		Device number, z. B. 1
	3	– 6	Device ID number (unsigned long) 1)
	7	– 10 Device serial number (unsigned long) 1)
	11 – 14 Software ID number (unsigned long) 1)

15Software version x (x.y.z.cc): A – Z

16Software version y (x.y.z.cc): 0 – 99

17Software version z (x.y.z.cc): 0 – 99

18Software version cc (x.y.z.cc): 0 – 99

19EEPROM layout version x (x.y): A – Z 2)

20EEPROM layout version y (x.y): 0 – 99 2)

21Table_x version (x.y): A – Z 3)

22Table_y version (x.y): 0 – 99 3)

23– 26 Bios ID number (unsigned long) 4)

27Bios version x (x.y.z.cc): A – Z 4)

28Bios version y (x.y.z.cc): 0 – 99 4)

29Bios version z (x.y.z.cc): 0 – 99 4)

30Bios version cc (x.y.z.cc): 0 – 99 4)

31MFi software version x (x.y): A – Z 5)

32MFi software version y (x.y): 0 – 99 5)

33MFi software version x (x.y): A – Z 5)

Description

Command to read device information and the software version.

1)	First byte transferred: LSB
2)	Version-dependent – available with firmware version A.00.29.02 or later
3)	Version-dependent – available with firmware version A.00.63.00 or later
4)	Version-dependent – available with firmware version A.00.64.00 or later
5)	Version-dependent – available with firmware version A.00.83.03 or later	17

english

MFC Family

Serial Communication

Command number	0x92
Command name	ExtSetpoint
Request
Command	0x92
Byte count	5
Data	1 byte
	0	Internal set-point value settings
	1	External set-point value settings
	4 bytes
	0 – 3 Set-point value [%] (float) 1)
Response
Command	0x92
Byte count	7
Status	2 bytes, device status
Data	1 byte
	0	Internal set-point value settings
	1	External set-point value settings
	4 bytes
	0 – 3 Set-point value [%] (float) 1)

Description

Available as of firmware version A.00.28.09.

Determines the set-point value settings and describes the external set-point value as a percentage:

Internal	=	analog - the set-point value settings is assigned by the analog set-point value signal that is
created
External	=	digital via serial interface

Do not use this command if you are using a bus device (PROFIBUS, DeviceNet, etc.). The digital set-point value settings via the serial interface has a higher priority.

1) First byte transferred: MSB

Example:

All data as hexadecimal numbers (prefix 0x) short frame

Primary master

Short address 0

Data sent

Data received

•Set-point value settings digital 0.0% ( 0x00000000 IEEE 754)

0xFF 0xFF 0x02 0x80 0x92 0x05 0x01 0x00 0x00 0x00 0x00 0x14

0xFF 0xFF 0x06 0x80 0x92 0x07 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x12

•Set-point value settings digital 50.0% ( 0x42480000 IEEE 754)

0xFF 0xFF 0x02 0x80 0x92 0x05 0x01 0x42 0x48 0x00 0x00 0x1E

18	0xFF 0xFF 0x06 0x80 0x92 0x07 0x00 0x00 0x01 0x42 0x48 0x00 0x00 0x18

english

MFC Family

Serial Communication

•Set-point value settings digital 100.0% ( 0x42C80000 IEEE 754)

0xFF 0xFF 0x02 0x80 0x92 0x05 0x01 0x42 0xC8 0x00 0x00 0x9E

0xFF 0xFF 0x06 0x80 0x92 0x07 0x00 0x00 0x01 0x42 0xC8 0x00 0x00 0x98

•Switch set-point value settings to analog set-point value settings:

0xFF 0xFF 0x02 0x80 0x92 0x05 0x00 0x00 0x00 0x00 0x00 0x15

FF FF 06 80 92 07 00 00 00 .............

19

english

MFC Family

Serial Communication

Command number	0x93
Command name	GetAddDeviceInfo
Request
Command	0x93
Byte count	0
Data	-
Response
Command	0x93
Byte count	10
Status	2 bytes, device status
Data	8 bytes
	0 – 1 Bit field ERRORS 1)
	2 – 3 Bit field OTHERS 1)
	4 – 5 Bit field LIMITS 1)
	6 – 7 Reserved (bit field) 1)

Description

Available as of firmware version A.00.28.09.

Command for reading additional device information such as error bits, operating states (AutoTune, Safepos, etc.), states of threshold values and binary inputs/outputs.

1) First byte transferred: LSB

20

english

MFC Family

Serial Communication

Command number	0x94
Command name	GetBusAddress
Request
Command	0x94
Byte count	0
Data	-
Response
Command	0x94
Byte count	4
Status	2 bytes, device status
Data	2 bytes
	0 – 1	Bus address (unsigned int) 1)

Description

Available as of firmware version A.00.28.09.

Command for reading the bus address (PROFIBUS, DeviceNet, etc.). If the connected device is not a bus device, the error "Access denied" is returned in the response.

1) First byte transferred: LSB

21

english

MFC Family

Serial Communication

Command number	0x95
Command name	SetBusAddress
Request
Command	0x95
Byte count	2
Data	2 bytes
	0 – 1	Bus address (unsigned int) 1)
Response
Command	0x95
Byte count	4
Status	2 bytes, device status
Data	2 bytes
	0 – 1	Bus address (unsigned int) 1)

Description

Available as of firmware version A.00.28.09.

Command for setting the bus address (PROFIBUS, DeviceNet, etc.). If the connected device is not a bus device, the error "Access denied" is returned in the response.

1) First byte transferred: LSB

22

english

MFC Family

Serial Communication

Command number	0x96
Command name	GetTotalizer
Request
Command	0x96
Byte count	1
Data	1 byte
	0	Index of calibration gases
Response
Command	0x96
Byte count	8
Status	2 bytes, device status
Data	1 byte
		Index of calibration gases
		0	Gas 1
		1	Gas 2
	5 bytes
	1	Unit
	2 – 5 Totalizer value (Float)

Description

Available as of firmware version A.00.28.09.

Reads the totalizer value for the gas with the selected index in the unit that was transferred (167 = Nl; in reference to 1013 mbar, 273 K).

23

english

MFC Family

Serial Communication

Command number	0x97
Command name	ClearTotalizer
Request
Command	0x97
Byte count	1
Data	1 byte
	0 index of calibration gases
Feedback
Command	0x97
Byte count	3
Status	2 bytes, device status
Data	1 byte

Index of calibration gases

0	Gas 1
1	Gas 2

Description

Available as of firmware version A.00.28.09.

Deletes the totalizer value of the corresponding gas.

24

english

MFC Family

Serial Communication

Command number	0x98
Command name	ExtSetpointWithoutAnswer
Device types	0xEE
Request
Command	0x92
Byte count	5
Data	1 byte
	0	Set-point value settings, internal
	1	Set-point value settings, external
	4 bytes
	1 – 4	Set-point value [%] (float) 1)
Response
Command	-
Byte count	-
Status	-
Data	-
Description

Available as of firmware version A.00.51.06.

Determines the set-point value settings and describes the external set-point value as a percentage:

Internal	=	analog - the set-point value settings is assigned by the analog
		set-point value signal that is created
External	=	digital via serial interface

Do not use this command if you are using a bus device (PROFIBUS, DeviceNet, etc.). The digital set-point value settings via the serial interface has a higher priority.

No response is sent for this command.

1) First byte transferred: MSB

25

english

MFC Family

Serial Communication

3.3.Error messages

2 bytes, device status

Error messages are saved in the device status. If the device status is 0, no error occurred.

3.3.1.First status byte

Communication error

Error code	0x82
Error name	overflow
Description	UART error, receive buffer, overflow was detected.
Error code	0x88
Error name	checksum
Description	An incorrect checksum was received.
Error code	0x90
Error name	framing
Description	UART error, framing error was detected.
Error code	0xA0
Error name	overrun
Description	UART error, overrun error was detected.
Error code	0xC0
Error name	parity
Description	UART error, parity error was detected.

26

english

MFC Family

Serial Communication

Command error

	Error code	0x02
	Error name	invalid_selection
	Description	An invalid data range was selected.
	Error code	0x03
	Error name	parameter_too_large
	Description	Transfer parameter too large. It may be a table or array index from the data range, i.e. an
		incorrect value range.
	Error code	0x04
	Error name	parameter_too_small
	Description	Transfer parameter too small. It may be a table or array index from the data range, i.e. too low
		for the value range.
	Error code	0x05
	Error name	too_few_data_bytes
	Description	Not enough data bytes were received.
	Error code	0x07
	Error name	write_protected
	Description	Device is write-protected.
	Error code	0x10
	Error name	access_restricted
		The command that was sent cannot be executed (currently). Access was denied. The cause
	Description	could be, for example, that the necessary access rights are lacking or the command is not
		permitted in the current operating mode.
	Error code	0x40
	Error name	no_command
	Description	Invalid/incorrect command, i.e. the command that was received is not supported by the
		device.

27

english

MFC Family

Serial Communication

Device status

Error code	0x20
Error name	device_busy
Description	Device is busy.

Internal device-specific error messages

	Error code	0x01
	Error name	timeout
	Description	The time limit was exceeded, i.e. too much time passed between a valid received delimiter
		and a complete command.
	Error code	0x41
	Error name	wrong_command
	Description	Incorrect command structure, i.e. the command is valid and exists, but the number of bytes
		transferred does not match. Only 1 byte was transferred for a 2-byte variable.

28

english

MFC Family

Serial Communication

3.3.2.Second status byte

Second status byte

Bit 7 Field device malfunction

Bit 6 reserved for future purposes

Bit 5 reserved for future purposes

Bit 4 reserved for future purposes

Bit 3 reserved for future purposes

Bit 2 reserved for future purposes

Bit 1 reserved for future purposes

Bit 0 reserved for future purposes

UART errors take precedence in error detection.

Multiple UART errors cannot be detected simultaneously.

3.3.3.Codings and units

Manufacturer coding (HART standard)

Hex	Dec	Description
0x78	120	Buerkert
0xFA	250	not used
0x FB	251	none
0xFC	252	unknown
0xFD	253	special
Units (HART standard)
Hex	Dec	Unit	Description
0x33	51	sec	Seconds
0x39	57	%	Percent
0xA7	167	Nl	Normalized liters (reference condition p = 1015 mbarabs, T = 273,15 K
0xFA	250	-	not used
0xFB	251	-	none
0xFC	252	-	unknown
0xFD	253	-	special

29

english

MFC Family

PROFIBUS DP Start-up

4.PROFIBUS DP Start-up

4.1.Address setting for BUS devices

4.1.1.Devices without rotary switch for address setting

The BUS address of devices can be set either with the Bürkert configuration tool MassFlowCommunicator in the "Views" → "PROFIBUS/DeviceNet/CANopen" view or directly with the BUS master.

After an address is changed, it must be initialized on the slave and also on the master. Depending on the BUS, it may be necessary to send an appropriate telegram.

To ensure the setting was made without problems, a device reset should be performed (turn the electrical power off and back on).

4.1.2. Devices with rotary switch for address setting

When the device is turned on, the address set as the slave address on the rotary switches is applied. Valid addresses are:

• PROFIBUS	0	… 126
• DeviceNet	0	… 63
• CANopen	1	… 127

If the address has been set outside the permissible range, the address setting has the validity as described in section “4.1.1”.

LBS	Ones place, x 1
	0 – 9	The number	→ 0 – 9
		multiplied by 1
MBS	Tens place, x 10
	0 – 9	The number	→ 0 – 90
		multiplied by 10
	A		→ 100
	B		→ 110
	C		→ 120
	D		→ 130
	E		→ 140
	F		→ 150

Thus the address consists of LSB + MSB.

MSB	LBS	Address
0	1	1
6	3	63
A	0	100
C	7	127

If you want to make an address setting with the BUS master and there are rotary switches available, set

the address to a value outside the valid range.

30

english