Ba00065sen 0516

BA00065S/04/EN/05.
16 Products Solutions Services

71320736
Operating Instructions
Tutorial for FieldCare projects
Connection of HART, PROFIBUS, FOUNDATION Fieldbus,
Ethernet/IP and Modbus devices with FieldCare via
Modem, Fieldgate and Remote I/O
Order code: XXXXX-XXXXXX
1. Ser. no.: XXXXXXXXXXXX
Ext. ord. cd.: XXX.XXXX.XX
Serial number
2. www.endress.com/deviceviewer Endress+Hauser Operations App
3.
2 Endress+Hauser
Revision history
Revision history
Product Operating changes Comments
version Instructions
2.09.xx BA00065S/04/EN/ Original Operating Instructions

01.12
2.09.xx BA00065S/04/EN/ New Chapter about WirelessHART, NI card, FFusb modem;

02.13 MACTek Bluetooth modem Appendix D: Installing the
DTM Appendix E: Updating the DTM catalog Appendix F:
Replacing the iDTM
Editorial USB installation in Appendix C, Procedure in Windows 7
Layout New CD
2.10.xx BA00065S/04/EN/ Layout New CMS

03.15
New Chapter 7: HART via Rockwell Automation ControlLogix,
Chapter 12: PROFIBUS PA via Rockwell Automation
ControlLogix, Appendix G: User roles, Appendix H:
Verifying the network
2.10.xx BA00065S/04/EN/ New Chapter 8: HART via RSG45

04.15 chapters and Chapter 20: Fieldgate SFG500 and Siemens ET200M/iSP
changes Chapter 37: PROFIBUS DP via PROFIBUS Modem and
WAGO Remote I/O
Chapter 38: PROFIBUS DP via PROCENTEC ProfiCore
Chapter 39: Plant view
Appendix K: SFG500 error information
2.11.xx BA00065S/04/EN/ New Chapter 3 Introduction to FieldCare

05.16 chapters and Chapter 8 Pepperl+Fuchs LB/FB Remote I/O
changes Chapter 15 HIMA
Chapter 20 PROFINET - PROFIBUS Gateway
Chapter 32 PBI-Plus
Chapter 33 Heartbeat Verification
Chapter 38 I/O Link Networks
Chapter 48 Interface to W@M
Endress+Hauser 3
Table of contents
Table of contents
1 Document information . . . . . . . . . . . . . . 9 6.1.2 Loop power from the transmitter

power supply . . . . . . . . . . . . . . . . . . . 29
1.1 Document function . . . . . . . . . . . . . . . . . . . . . 9 6.2 Installing the Commubox FXA195 driver . . . . 31
1.2 Symbols used . . . . . . . . . . . . . . . . . . . . . . . . . . 9 6.3 Connection procedure . . . . . . . . . . . . . . . . . . 31
1.2.1 Safety symbols . . . . . . . . . . . . . . . . . . 9
1.2.2 Symbols for certain types of
information . . . . . . . . . . . . . . . . . . . . 9 7 HART via Fieldgate FXA520 and
1.2.3 FieldCareIcons . . . . . . . . . . . . . . . . . . 10 Pepperl+Fuchs multiplexer . . . . . . . . . 34
1.3 Text emphasis . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.4 Acronyms used . . . . . . . . . . . . . . . . . . . . . . . 11
7.1.1 Parallel access to HART control loop
1.5 Registered trademarks . . . . . . . . . . . . . . . . . . 12
with 4 to 20 mA . . . . . . . . . . . . . . . . 34
7.1.2 Direct/remote access to a HART
2 Basic safety instructions . . . . . . . . . . . 13 monitoring system . . . . . . . . . . . . . . 35
2.1 Requirements for personnel . . . . . . . . . . . . . . 13 7.2 Connection procedure . . . . . . . . . . . . . . . . . . 36
2.2 Designated use . . . . . . . . . . . . . . . . . . . . . . . 13 7.2.1 Connecting and configuring
2.3 Operational safety . . . . . . . . . . . . . . . . . . . . . 13 Fieldgate FXA520 . . . . . . . . . . . . . . . 36
2.4 Installation, commissioning and operation . . . 14 7.2.2 Commissioning the Pepperl+Fuchs
2.5 Technical improvements . . . . . . . . . . . . . . . . 14 multiplexer . . . . . . . . . . . . . . . . . . . . 39
2.6 IT security . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8 HART via Pepperl+Fuchs LB/FB
3 Introduction to FieldCare . . . . . . . . . . 15 Remote I/O . . . . . . . . . . . . . . . . . . . . . . . 42
3.1 General information . . . . . . . . . . . . . . . . . . . 15 8.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.2 Main dialog . . . . . . . . . . . . . . . . . . . . . . . . . . 15 8.2 Connection procedure . . . . . . . . . . . . . . . . . . 42
3.2.1 General functions . . . . . . . . . . . . . . . 15
3.2.2 Optional settings . . . . . . . . . . . . . . . . 15
3.3 Project administration . . . . . . . . . . . . . . . . . . 16 9 HART via RS232 to RS485 converter
3.3.1 Creating a project . . . . . . . . . . . . . . . 16 and Pepperl+Fuchs multiplexer . . . . . 45
3.3.2 Saving a project . . . . . . . . . . . . . . . . . 17 9.1 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.3.3 Opening a project . . . . . . . . . . . . . . . 18 9.1.1 Direct/remote access to a HART
3.4 CSV export and import . . . . . . . . . . . . . . . . . . 18 monitoring system . . . . . . . . . . . . . . 45
3.5 Network view . . . . . . . . . . . . . . . . . . . . . . . . 19 9.2 Connection procedure . . . . . . . . . . . . . . . . . . 46
3.6 Plant view . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 9.2.1 Connecting and configuring
3.6.1 Creating a plant view . . . . . . . . . . . . . 20 Fieldgate SFG500 . . . . . . . . . . . . . . . 46
3.7 DTM catalog . . . . . . . . . . . . . . . . . . . . . . . . . 20
10 HART via Rockwell Automation

4 FieldCare administration . . . . . . . . . . 22
ControlLogix . . . . . . . . . . . . . . . . . . . . . . 49
4.1 User administration . . . . . . . . . . . . . . . . . . . . 22
10.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 49
10.2 Connection procedure . . . . . . . . . . . . . . . . . . 49
5 HART point-to-point connection via 10.3 Access to device data . . . . . . . . . . . . . . . . . . . 51
Commubox FXA191 . . . . . . . . . . . . . . . 23
5.1 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 11 HART via RSG45 . . . . . . . . . . . . . . . . . . . 52
5.1.1 Loop power from controller/field 11.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 52
device . . . . . . . . . . . . . . . . . . . . . . . . 23 11.2 Connection procedure . . . . . . . . . . . . . . . . . . 52
5.1.2 Loop power from a transmitter
power supply . . . . . . . . . . . . . . . . . . . 24
5.2 Connection procedure . . . . . . . . . . . . . . . . . . 25 12 HART Multidrop or HART point-to-
point connection via Fieldgate
6 HART point-to-point connection via FXA520 . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Commubox FXA195 . . . . . . . . . . . . . . . 28 12.1 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.1 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 12.1.1 HART Multidrop . . . . . . . . . . . . . . . . 56
6.1.1 Loop power from controller/field 12.1.2 HART point-to-point connection . . . . 56
device . . . . . . . . . . . . . . . . . . . . . . . . 28 12.2 Connection procedure . . . . . . . . . . . . . . . . . . 57
Endress+Hauser 5
Table of contents
13 HART point-to-point or HART 22.2 Commissioning the Fieldgate FXA720 . . . . . . 87

22.2.1 Basic configuration . . . . . . . . . . . . . . 87
Multidrop via MACTek Bluetooth 22.2.2 Connection procedure . . . . . . . . . . . . 88
modem . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 22.3 Connection procedure . . . . . . . . . . . . . . . . . . 91
13.1 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
13.1.1 Point-to-point connection . . . . . . . . . 61 23 PROFIBUS DP/PA via Fieldgate
13.1.2 Multidrop connection . . . . . . . . . . . . 61 SFG500 . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
23.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 94
14 HART via IFAK Ethernet gateway . . . 65
14.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 65 24 PROFIBUS DP/PA via multiple
Fieldgate SFG500 devices . . . . . . . . . . 98
15 HART via HIMA multiplexer 24.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 98
HIMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
15.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 68 25 PROFIBUS DP/PA via Fieldgate
SFG500 and Siemens link . . . . . . . . . 100
16 WirelessHART Adapter SWA70 via 25.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 100
25.2 Connection procedure . . . . . . . . . . . . . . . . . 100
HART modem . . . . . . . . . . . . . . . . . . . . . 70
16.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 70 26 PROFIBUS-DP/PA and HART via
Fieldgate SFG500 and Siemens
17 WirelessHART Fieldgate SWG70 via ET200M/iSP . . . . . . . . . . . . . . . . . . . . . 103
Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . 73 26.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 103
17.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 73
27 PROFIBUS DP/PA and HART via
18 Modbus via RS485 Modbus . . . . . . . . . 77 Fieldgate SFG500 and Turck
18.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Remote I/O . . . . . . . . . . . . . . . . . . . . . . 105
18.2 Connection procedure . . . . . . . . . . . . . . . . . . 77 27.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 105
19 EtherNet/IP via Ethernet . . . . . . . . . . . 79
19.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 79 28 PROFIBUS DP/PA and HART via
19.2 Connection procedure . . . . . . . . . . . . . . . . . . 79 Fieldgate SFG500 and Stahl Remote
I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
20 PROFINET - PROFIBUS PA Softing
28.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 109
Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . 81 28.2 Connection procedure . . . . . . . . . . . . . . . . . 110
20.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 81
20.2 Setting up the gateway . . . . . . . . . . . . . . . . . . 81 29 PROFIBUS DP/PA via Softing
PBproUSB modem . . . . . . . . . . . . . . . . 113
21 PROFIBUS PA via Rockwell 29.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 113
Automation ControlLogix . . . . . . . . . . 83 29.3 Connection procedure . . . . . . . . . . . . . . . . . 115
21.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 83
21.2 Connection procedure . . . . . . . . . . . . . . . . . . 83 30 PROFIBUS DP via PROFIBUS modem
and WAGO Remote I/O . . . . . . . . . . . 117
22 PROFIBUS DP/PA via Fieldgate
30.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 117
FXA720 . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 30.2 Connection procedure . . . . . . . . . . . . . . . . . 117
22.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6 Endress+Hauser
Table of contents
31 PROFIBUS DP via PROCENTEC 36 FOUNDATION Fieldbus H1 via the

ProfiCore . . . . . . . . . . . . . . . . . . . . . . . . 120 National Instruments FBUS card . . 145
31.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 120 36.1 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
31.2 Connection procedure . . . . . . . . . . . . . . . . . 120 36.1.1 Connection to a FOUNDATION
Fieldbus H1 segment . . . . . . . . . . . . 145
32 PROFIBUS via modem PBI-Plus/ 36.1.2 Point-to-point connection in Bench
mode . . . . . . . . . . . . . . . . . . . . . . . 145
smar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 36.2 Connection procedure . . . . . . . . . . . . . . . . . 146
32.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 123
32.2 Connection procedure . . . . . . . . . . . . . . . . . 124 37 FOUNDATION Fieldbus H1 via
Softing FFusb modem . . . . . . . . . . . . 148
33 PROFIBUS via SFG500 with the
37.1 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Heartbeat VerificationDTM . . . . . . . 126 37.1.1 Connection to a FOUNDATION
33.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 126 Fieldbus H1 segment . . . . . . . . . . . . 148
33.2 Connection procedure . . . . . . . . . . . . . . . . . 126 37.1.2 Point-to-point connection in Bench
33.2.1 Scanning the network . . . . . . . . . . . 126 mode . . . . . . . . . . . . . . . . . . . . . . . 148
33.2.2 Adding/configuring the 37.2 Connection procedure . . . . . . . . . . . . . . . . . 149
VerificationDTM . . . . . . . . . . . . . . . 127
33.2.3 Reading out the heartbeat data . . . . 129 38 I/O Link networks . . . . . . . . . . . . . . . . 152
33.2.4 Uploading the heartbeat data to
38.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 153
W@M . . . . . . . . . . . . . . . . . . . . . . . 129
34 FOUNDATION Fieldbus H1 via Field

39 ISS interface via FXA193 modem . . 156
Controller SFC162 . . . . . . . . . . . . . . . . 131 39.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 156
34.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 131 39.2 Connection procedure . . . . . . . . . . . . . . . . . 156
34.2 Commissioning the Field Controller SFC162 131
34.2.1 Setting up the IP address of the Field
Controller SFC162 . . . . . . . . . . . . . . 131
40 ISS interface via FXA291 modem . . 159
34.2.2 Select Visitor mode . . . . . . . . . . . . . 133 40.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 159
34.2.3 Selecting the network card for 40.2 Installing the FXA291 modem driver . . . . . . 159
FieldCare . . . . . . . . . . . . . . . . . . . . 134 40.3 Connection procedure . . . . . . . . . . . . . . . . . 159
34.4 Upload the project . . . . . . . . . . . . . . . . . . . . 136 41 IPC interface for level/pressure via
FXA193 modem . . . . . . . . . . . . . . . . . . 160
35 FOUNDATION Fieldbus H1 Bench
41.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 160
mode via Field Controller SFC162 . 137 41.2 Connection procedure . . . . . . . . . . . . . . . . . 160
35.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 137
35.2 Commissioning the Field Controller SFC162 138 42 IPC interface for level/pressure via
35.2.1 Setting up the IP address of the Field
Controller SFC162 . . . . . . . . . . . . . . 138 FXA291 modem . . . . . . . . . . . . . . . . . . 163
35.2.2 Select Visitor mode . . . . . . . . . . . . . 139 42.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 163
35.2.3 Selecting the network card for 42.2 Installing the FXA291 modem driver . . . . . . 163
FieldCare . . . . . . . . . . . . . . . . . . . . 140 42.3 Connection procedure . . . . . . . . . . . . . . . . . 163
35.3.1 Connection with the Field Controller 43 CDI interface via FXA291 modem . . 164
SFC162 CommDTM . . . . . . . . . . . . . 141
43.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 164
35.3.2 Assigning the device tag and/or H1
43.2 Installing the FXA291 modem driver . . . . . . 164
address . . . . . . . . . . . . . . . . . . . . . . 142
35.3.3 Creating a FOUNDATION Fieldbus
network . . . . . . . . . . . . . . . . . . . . . 143
35.3.4 Opening the DeviceDTM . . . . . . . . . 143 44 CDI interface via TXU10 modem . . . 167
35.4 Upload the project . . . . . . . . . . . . . . . . . . . . 144 44.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 167
44.2 Installing the TXU10 modem driver . . . . . . . 167
Endress+Hauser 7
Table of contents
45 CDI interface via direct USB

connection . . . . . . . . . . . . . . . . . . . . . . . 170
45.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 170
46 CDI interface via Ethernet TCP/IP . 172

46.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 172
46.2 Setting up the computer . . . . . . . . . . . . . . . . 172
47 PCP interfaces via the FXA291/

TXU10 modem . . . . . . . . . . . . . . . . . . . 176
47.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . 176
47.2 Installing the FXA291 or TXU10 modem
driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
48 Interface to W@M . . . . . . . . . . . . . . . . 179

48.1 Recording the W@M URL . . . . . . . . . . . . . . 179
48.2 Recording the W@M User . . . . . . . . . . . . . . 179
48.3 W@M settings . . . . . . . . . . . . . . . . . . . . . . 179
48.4 W@M functions . . . . . . . . . . . . . . . . . . . . . 180
49 Appendix . . . . . . . . . . . . . . . . . . . . . . . . 181
49.1 Appendix A - Setting a computer IP address . 181
49.2 Appendix B - Windows firewall . . . . . . . . . . 181
49.3 Appendix C - Installing a USB modem driver 182
49.4 Appendix D - Installing the DTM or
CommDTM . . . . . . . . . . . . . . . . . . . . . . . . . 182
49.5 Appendix E - Updating the FieldCare DTM
catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
49.6 Appendix F - Replacing the iDTM with a
DeviceDTM . . . . . . . . . . . . . . . . . . . . . . . . . 184
49.7 Appendix G - User roles . . . . . . . . . . . . . . . . 184
49.8 Appendix H - Verifying the network . . . . . . . 185
49.9 Appendix I - PROFIBUS PA Profile . . . . . . . . 186
49.10 Appendix J - Generic HART . . . . . . . . . . . . . 186
49.11 Appendix K - Fieldgate SFG500 error
information . . . . . . . . . . . . . . . . . . . . . . . . . 186
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
8 Endress+Hauser
Tutorial for FieldCare projects Document information
1 Document information
1.1 Document function

These Operating Instructions contain all the information that is required to use the
software: from product description, installation and use to system integration, operation,
diagnosis and troubleshooting through to software updates and disposal.
1.2 Symbols used
1.2.1 Safety symbols
Symbol Meaning
DANGER!
DANGER This symbol alerts you to a dangerous situation. Failure to avoid this situation will result in
serious or fatal injury.
WARNING!
WARNING This symbol alerts you to a dangerous situation. Failure to avoid this situation can result in
serious or fatal injury.
CAUTION!
CAUTION This symbol alerts you to a dangerous situation. Failure to avoid this situation can result in
minor or medium injury.
NOTE!
NOTICE This symbol contains information on procedures and other facts which do not result in
personal injury.
1.2.2 Symbols for certain types of information
Symbol Meaning
Permitted
Procedures, processes or actions that are permitted.
Preferred
Procedures, processes or actions that are preferred.
Forbidden
Procedures, processes or actions that are forbidden.
Tip
Indicates additional information.
Reference to documentation
A Reference to page
Reference to graphic
Notice or individual step to be observed
1. , 2. , 3. Series of steps
Result of a step
Help in the event of a problem
Visual inspection
Endress+Hauser 9
Document information Tutorial for FieldCare projects
1.2.3 FieldCareIcons
Previous symbol Current symbol Meaning
Start new project.
Open existing project.
Save open project.
Print open project.
Open clipboard.
Show DTM catalog.
Open documentation for selected device or detailed device

information.
Open inventory.
Activate protocol.
Add new device to the network.
Remove device from the network.
Create new network topology using CommDTM and DeviceDTMs.
Compares the network topology in the field with the actual

physical network, and devices are added to the existing network.
Scans the preconfigured topology and shows the report with the
scanned device information.
Indicates whether there is a connection with the device.
Transfer information from the device to FieldCare.
Transfer information from FieldCare to the device.
Device-specific functions for the selected device.
Add plant level.
Add item.
Remove plant level.
Remove item.
Open device checklist to show selected devices in the plant.
Confirm replaced device.
10 Endress+Hauser
Tutorial for FieldCare projects Document information
Previous symbol Current symbol Meaning
New icons
Disconnected 1)
1)
Set up communication, ready for communication
Communication channel occupied or communication action

canceled. 1)
Connected 1)
W@M symbol, appears in the start bar on the bottom right if a

connection to W@M has been established.
Switch on touch mode
Switch off touch mode
1) Status indicator: online/offline status indication of devices in the plant and network view
1.3 Text emphasis

Emphasis Meaning Example
Bold Keys, buttons, program icons, Start Programs Endress+Hauser select Print option
tabs, menus, commands in the File menu.
Angle brackets Variables <DVD-ROM drive>
1.4 Acronyms used

Acronyms Meaning
CDI Common Data Interface
COM Communication Equipment
CommDTM Communication Device Type Manager
CSV Character Separated Value
DTM Device Type Manager
DP Decentralized Peripheral
FDT Field Device Tool
FIFO First In First Out
HART Highway Addressable Remote Transducer
I/O Input/Output
IP Internet Protocol
ISS Internal Service Interface
LAN Local Area Network
LAS Link Active Scheduler
MUX Muliplexer
NIC Network Interface Card
PA Process Automation
PC Personal Computer
PCD PROCENTEC Communication Driver
Endress+Hauser 11
Document information Tutorial for FieldCare projects
Acronyms Meaning
PCI Peripheral Component Interconnect
PCIe Peripheral Component Interconnect express
DCS Distributed Control System
PROFIBUS Process Field Bus
PROFINET Process Field Network
SPL Second Program Loader
PLC Programmable Logic Controller
TCP Transmission Control Protocol
UDP User Datagram Protocol
USB Universal Serial Bus
1.5 Registered trademarks

PROFINET is a registered trademark of the PROFIBUS User Organization, Karlsruhe/
Germany.
PROFIBUS is a registered trademark of the PROFIBUS User Organization, Karlsruhe/
Germany.
FOUNDATIONTM Fieldbus is the trademark of the FieldComm Group, Austin, TX 78759,
USA.
HART, WirelessHART is the registered trademark of the FieldComm Group, Austin, TX
78759, USA.
Ethernet/IP is the registered trademark of ODVA, Michigan USA.
Modbus is the registered trademark of Modicon, Incorporated.
Microsoft, Windows 8.1, Windows XP, Windows 2008 Server, Windows 7,
Windows 10, Internet Explorer and the Microsoft logo are registered trademarks of the
Microsoft Corporation.
Acrobat Reader is a registered trade mark of Adobe Systems Incorporated.
All other brand and product names are trademarks or registered trademarks of the
companies and organizations in question.
12 Endress+Hauser
Tutorial for FieldCare projects Basic safety instructions
2 Basic safety instructions
2.1 Requirements for personnel

Physical and electronic access to field devices, networks, computers and systems must be
restricted to an authorized group of individuals. Use a role-based access system. Establish
detailed guidelines and processes to only allow authorized persons access to the PC or
other equipment.
2.2 Designated use

FieldCare is an FDT-based (Field Device Tool) Plant Asset Management tool which,
depending on the version, can be used for device parametrization, instrument
management or condition monitoring. By use of the appropriate Device Type Managers
(DTMs), it is able to operate field devices and system components independent of
communication protocol.
Use a properly configured firewall that blocks all data that do not meet the security
specifications. Deactivate ports that are not in use and use a demilitarized zone or an
intrusion detection system to improve security. Introduce an organized, real-time patch
management process for all products, such as operating systems, Internet browsers,
programs, apps, databases and drivers and run an anti-virus software on the PC. Only use
hardware, software, firmware and other electronic content from trusted sources.
Use a secure password for electronic access to the programs, e.g. for the PC, FieldCare, SQL
server and field devices.
A secure password should:
Be at least 8 characters long
Never contain the user name, personal names or company name
Never contain a whole word
Differ significantly from earlier passwords
Comprise upper-case letters, lower-case letters, a number and a symbol
Be changed regularly
2.3 Operational safety

DEP - Data Execution Prevention
DEP is a security tool that helps keep viruses, damage and security threats away from your
computer. By monitoring programs, DEP can help protect the computer and ensure that
applications use system memory safely. As soon as an application attempts to access a
program, DEP closes the program.
Open the system by clicking the Start button, right-click Computer and then select
System Properties.
Click Advanced System Settings. When prompted, enter the Administrator Password
by way of confirmation.
Click Performance and then Properties.
Click the Data Execution Prevention tab and then select Switch to DEP for All
Programs and Services.
To select Switch to DEP for All Programs and Services click the check box. If the
program is not listed, click Add. Select the program and click Open.
Click OK. When the System Properties screen appears, click OK.
The computer might need to be restarted for the changes to take effect.
Endress+Hauser 13
Basic safety instructions Tutorial for FieldCare projects
Number Explanation Status
Always Off DEP is switched off for all the processes.
1 Always On DEP is switched on for all the processes.
2 Opt In DEP is switched on for the main Windows programs and services, default setting.
3 Opt Out DEP is possible for all processes, apart from programs and services.
2.4 Installation, commissioning and operation

This tutorial assumes that FieldCare has been correctly installed according to the
instructions in the Getting Started manual, (BA00027S/04/A2), and that the
appropriate DTM catalog has been installed and updated. The manual describes a number
of use cases with various system architectures. It is assumed that all devices and system
components have been installed and connected according to the instructions in the
associated Operating Instructions.
Where equipment is to be configured in explosion hazardous areas, it must be ensured all
components, including computer, have the appropriate certification.
2.5 Technical improvements

Endress+Hauser reserves the right to make technical improvements to the hardware and
software at any time and without prior notification. If such improvements have no effect
on the operation of the equipment, they are not documented. If the improvements affect
operation, a new version of the Operating Instructions is created and issued.
2.6 IT security
We only provide a warranty if the device is installed and used as described in the
Operating Instructions. The device is equipped with security mechanisms to protect it
against any inadvertent changes to the device settings.
IT security measures in line with operators' security standards and designed to provide
additional protection for the device and device data transfer must be implemented by the
operators themselves.
14 Endress+Hauser
Tutorial for FieldCare projects Introduction to FieldCare
3 Introduction to FieldCare
3.1 General information

This manual describes how FieldCare can be used to establish a connection to Modbus,
HART, PROFIBUS, FOUNDATION Fieldbus and EtherNet/IP devices using modems,
gateways and remote I/Os. Each chapter describes a particular use case together with the
associated connection procedure. These Operating Instructions assume that FieldCare and
the appropriate DTM library are installed on the computer.
3.2 Main dialog
1 Main dialogFieldCare
1 Menu bar
2 Toolbar
3 Network view
4 Plant view
5 DTM/parameter view
6 Optional dialogs
7 Status bar
3.2.1 General functions

Plant/network view
The view can be customized via the Context Menu Customize View
The dialog is displayed
Columns can be displayed and hidden and the order of the columns can be modified
List function
The sorting of the lists in ascending or descending order can be modified by clicking the
title bar of a column
Change the column width
Change the column order with drag and drop
3.2.2 Optional settings

A number of FieldCare functions are determined by the preferences set within FieldCare in
the dialog Extra Options. In the descriptions which follow, FieldCare has been set up to
prompt for projects on the Project tab.
Endress+Hauser 15
Introduction to FieldCare Tutorial for FieldCare projects
Under the Scanning tab it is possible to show or hide the Scan Result after the network
has been created. For the procedures described in these Operating Instructions, the option
has been selected which hides the Scan Result if only one device is found.
In general, if only one device is found, FieldCare will automatically make the connection
with the DTM and put it on-line. Where more than one device is found, each DTM must be
connected separately. Depending upon the DTM, a double-click on an unconnected device
will also prompt the connection. If this is not the case, the Connect option must be used.
The configuration of individual devices is not described in these Operating Instructions.
This information can be found in the Operating Instructions for the device in question.
3.3 Project administration

The project-related data are saved in a database or in files, depending on the project
storage mode, see Chapter 4 22.
3.3.1 Creating a project

In all cases the first steps in creating a project are identical. The FieldCare window appears
by default, but can be suppressed in the FieldCare window under Extra Options
Project. The FieldCare window is no longer displayed if the None check box is checked.
16 Endress+Hauser
Creating a project
1. If the Startup screen appears:
Click Next.
The FieldCare window opens.
2. On the New tab, select the Create project item.

3. Click Open.
FieldCare opens a new project with a host PC.
3.3.2 Saving a project

FieldCare projects are stored in a database but are not accessible as files on the hard
disk. It is possible to access these files by using FieldCare in file mode.
All projects are saved in the same manner.
Endress+Hauser 17
Saving a project
1. Select File Save in the menu.
The Save Project As dialog appears.
2. Enter a project name and click Save.

The project is saved.
3.3.3 Opening a project

Opening a saved project
1. In the FieldCare dialog, click the Existing tab.
The Open Project dialog opens. The projects that were recently opened are
displayed.
2. Select Project and click Open.

The project is displayed.
If the project does not appear on the screen, click View Network.
3.4 CSV export and import

The structural information of the plant and network view (plant/network topology) can be
exported to a CSV file and imported from a CSV file to a FieldCare project.
Importing CSV
1. Create a project as described in Chapter 3.3.1. 16
18 Endress+Hauser
2. In the menu, click Import CSV.

The CSV Import dialog opens.
3. Tap a file and click Open.
A message is displayed.
4. Optionally select Plant/Network Topology.
Depending on the option selected, the data are imported from the CSV file to the
plant view and/or the network view.
Exporting CSV
1. Click the top level of the plant topology.
2. In the menu, click Export CSV.
The CSV Export dialog opens.
3. Select a storage location and a name and click Save.
A dialog opens.
4. Optionally select Plant/Network Topology.
The network view is exported to a CSV file.
3.5 Network view

The network view is a graphical representation of the device network belonging to a
FieldCare project.
Column Use
Network TAG Network TAG of the device
Connections Symbol indicating the online/offline status
Slave Indicates the channel via which the device is connected
Address Unique network address of the device
Device type (DTM) Indicates the type of device for each of the individual devices
Physical device Identifies the physical device at the particular point in the network
3.6 Plant view

The network view must first be created before the plant view can be created. The
plant view corresponds to the actual plant topology. The technology view is a
hierarchical representation of the layout process. Any user with the role of plant
engineer or higher can create new plant views or modify existing ones.
The items can be shifted in the plant view. The elements in the plant view can be
renamed, added or deleted.
Column Use
Plant TAG Plant tag for every plant position
Connections Symbol indicating the online/offline status
Status Currently not used
Monitored Currently not used
Critical Indicates whether the device is in a critical position
Slave Indicates the channel via which the device is connected
Address Indicates the address of the device that is assigned to this plant position
Endress+Hauser 19
Column Use
Device type (DTM) Indicates what type of device the device is
Physical device Identifies the physical device at the particular point in the network
3.6.1 Creating a plant view

Changes to the network view are automatically synchronized with the plant view. Manual
changes to the plant view do not affect the network view. Therefore it is possible to design
a plant independently of the network topology.
Adding a new level

1. Right-click an item.
2. Click Plant View Add Plant Level.
A new plant level can be selected.
2 Structure of the plant view
In the plant view:

There is only one Enterprise item type at the top level 0
The Site, Area, Process Cell and Unit types are on level 1.
The Area, Process Cell and Unit types can be created under a Site
The Process Cell and Unit types can be created under an Area
The Unit type can be created under a Process Cell
The Analysis, Digital, Pressure, Special, Flow, Level and Temperature measuring
device types as well as a valve and an unknown device can be created under a Unit
The type at the lower position level can be changed subsequently using the Change
Position function. This is not subsequently possible for all other types. To do so, the type
must first be deleted and then created again.
An entry can be logically linked to a device in the network view with the Assign
function. The link is deleted with Undo Assignment
The caption texts for all the entries can be modified subsequently
A note can be entered for every entry via the context menu, or every entry can be linked
to a file or website URL
3.7 DTM catalog

All the DTMs currently in the device management system can be displayed in the DTM
catalog.
Displaying the DTM catalog
20 Endress+Hauser
The DTM Catalog dialog contains the list of all the DTMs that are currently in the device
management system. The DTMs can be grouped by category, manufacturer or protocol.
3 Displaying the DTM catalog
Updating the DTM catalog

The DTM catalog can be updated by users with administrator rights, see Appendix E.
183
4 Updating the DTM catalog
All the DTMs that are not included in the DTM catalog are listed in the dialog on the left-
hand side. These DTMs have either been removed or have been installed on the PC but not
yet been added to the DTM catalog. All the DTMs that are included in the DTM catalog are
listed on the right-hand side.
DTM information
The Information dialog contains a summary of all the relevant DTM information.
Displaying DTM information

1. Right-click a DTM.
A context menu appears.
2. Select the entry DTM information.
The Information dialog appears.
5 DTM information
Possible options in the Information dialog

Display all the device types of the DTM:
Displays the basic information for all the device types that are supported by the DTM
Display advanced information:
Displays additional information about the DTM: Manufacturer ID, Device Type ID,
SubdeviceType ID, Device Type Information
Endress+Hauser 21
FieldCare administration Tutorial for FieldCare projects
4 FieldCare administration
Functions:
User administration
The storage mode of the FieldCare project is set with the Project Storage Configuration
function: database or individual project files (binary format *.fcprj)
W@M configuration, basic settings for W@M connection, see also Chapter 48
179
4.1 User administration

User login is initially disabled after installing FieldCare so that FieldCare can be started
without having to log in. User login can be enabled in FieldCare Administrator under User
and User Groups Configuration User Login Active.
There is no restriction on the number of users that can be created:

Optional settings can be assigned to the user account; the user must change his/her
password the next time he/she logs in
The user may change his/her password
The user password is valid for a predefined period and must then be changed
The user account can be disabled
Each user is assigned a user role according to the FDT standard
The user groups are listed in Appendix G. 184
22 Endress+Hauser
Tutorial for FieldCare projects HART point-to-point connection via Commubox FXA191
5 HART point-to-point connection via

Commubox FXA191
5.1 Use cases

The Commubox FXA191 provides a direct connection between a HART device (4 to
20 mA) and the RS232C port (COM port) of a computer. To establish communication with
the HART device, a resistor of at least 250 must be provided in the circuit. The way in
which this is done depends upon the system architecture and power source used.
To see the HART device, FieldCare requires:
HART CommDTM
HART DeviceDTMs
Observe the maximum total load of the smart transmitter!
Once Commubox FXA191 has been used in a non-Ex installation, it should never be
used in an Ex installation, as there is a danger that the protective circuits have been
inadvertently overloaded and no longer function correctly.
NOTICE
Overloaded protective circuits can cause a malfunction!
Never use a Commubox FXA191 in an Ex installation if it has already been used in a
non-Ex installation
See document XA058F/00/a3
5.1.1 Loop power from controller/field device
1 2 3 4 5
+ +
6 Operation of Commubox FXA191 in a control loop (I/O card active/device passive or vice versa) Via a
resistor 250 (recommended 270 to 330 ) in the control loop
1 I/O card PLC/DCS passive or active
2 Commubox FXA191
3 RS232C
4 FieldCare
5 Field device passive or active
Endress+Hauser 23
HART point-to-point connection via Commubox FXA191 Tutorial for FieldCare projects
1 2 3 4 5
+ +
7 Operation of a Commubox FXA191 in a control loop (I/O card active/device passive or vice versa). In the
control loop (loop-resistance 250 )
2 Commubox FXA191
3 RS232C
4 FieldCare
5.1.2 Loop power from a transmitter power supply
1 2 3 4 5 6
+
+ +
8 Operation of Commubox FXA191 in a control loop powered by a transmitter power supply. From the
control room via the communication sockets of the transmitter power supply.
1 Active power supply (RNS221, RN221N-A, RN221N-B (Ex), RMA422, RMA42)
2 Commubox FXA191
3 RS232C
4 FieldCare
5 I/O card PLC/DCS passive
6 Field device (passive)
1 2 3 4 5 6
+
+ +
9 Operation of Commubox FXA191 in a control loop powered by a transmitter power supply. Via the resistor
250 (recommended 270 to 330 ) in the control loop (communication resistor of Commubox FXA191
off)
2 Commubox FXA191
3 RS232C
4 FieldCare
24 Endress+Hauser
1 2 3 4 5 6
+
+ +
10 Operation of Commubox FXA191 in a control loop powered by a transmitter power supply. In the control
loop (loop-resistance 250 )
2 Commubox FXA191
3 RS232C
4 FieldCare
5.2 Connection procedure

Normally, the Commubox FXA191 connects to the COM1 port when it is plugged
into the computer.
It is recommended that only a native serial port be used. The use of USB/Serial
converters is not recommended.
Deactivate the FIFO buffer in the serial port settings.
When working with a modem that is connected to the COM1 port of the computer, you
can also select the HART (Point-to-Point) item in the FieldCare dialog. This
automatically sets up the project and the program scans for a device with the HART
address 0 (standard for non-Multidrop mode).
Establishing a connection
2. In the Network dialog, right-click Host PC.
A drop-down list opens.
3. Select Add Device.

The Add New Device dialog opens.
Endress+Hauser 25
4. In the Add New Device dialog, select the HART Communication item and click OK.
The HART CommDTM is added to the network.
5. In the Network dialog, right-click HART Communication.
6. Select Configuration.
The HART Communication (Configuration) dialog appears.
7. Set the parameters in the HART Communication (Configuration) dialog.

Communication interface: HART modem
Serial interface: COM1 (communication port), the port can be selected from the
drop-down menu if the computer has a second RS232C port (COM2) and the
Commubox is connected to this port
HART protocol master: 5
HART protocol preamble: 3
HART protocol number of communication retries: 0
Address scan start address: 0
Address scan end address: 0 (highest station address for HART Multidrop)
8. Click OK.
FieldCare returns to the Network dialog.
26 Endress+Hauser
10. Select Create Network.

FieldCare now scans the network and indicates the result.
The DeviceDTM is added to the network tree and the DTM opens.
11. The DTMs are opened as follows if the Commubox FXA191 is connected to a HART
Multidrop network and several devices are found:
In the Network dialog, right-click the device and select Connect or Online
Parameterize.
12. Save the project as described in Chapter 3.3.2. 17
The project is saved.
If FieldCare cannot find the correct DTM, it will offer alternative versions, graded
according to their suitability in the Scan Result dialog. The user has the choice of
accepting a DTM of less quality, or canceling the scan.
If no new DTM is available, the user can still integrate the device by using the HART
iDTM.
Endress+Hauser 27
6 HART point-to-point connection via

Commubox FXA195
6.1 Use cases

The Commubox FXA195 provides a direct connection between a HART device (4 to
20 mA) and the USB port of a computer. To establish communication with the HART
device, a resistor of at least 250 must be provided in the circuit. The way in which this is
done depends upon the system architecture and power source used.
HART CommDTM
HART DeviceDTMs
Please observe the max. total load of the Smart transmitter!
The communication resistor (250 ) integrated in the Commubox should not be
connected in parallel to a power supply point greater than 15 V. If the
communication resistor is used, it must always be incorporated into the 4 to 20 mA
circuit.
NOTICE
Overloaded protective circuits can cause a malfunction!
Never use a Commubox FXA195 in an Ex installation if it has already been used in a
non-Ex installation.
See document XA058F/00/a3.
6.1.1 Loop power from controller/field device
1 2 3 4 5
+ +
11 Operation of a Commubox FXA195 in a control circuit (I/O card active/device passive or vice versa). In the
control circuit (communication resistor of FXA195 on)
2 Commubox FXA195
3 USB
4 FieldCare
28 Endress+Hauser
1 2 3 4 5
+ +
12 Operation of a Commubox FXA195 in a control circuit (I/O card active/device passive or vice versa). Via a
resistor 250 (recommended 270 to 330 ) in the control circuit (communication resistor of FXA195
off)
2 Commubox FXA195
3 USB
4 FieldCare
1 2 3 4 5
+ +
13 Operation of a Commubox FXA195 in a control circuit (I/O card active/device passive or vice versa). In the
control circuit (loop-resistance 250 )
2 Commubox FXA195
3 USB
4 FieldCare
6.1.2 Loop power from the transmitter power supply
1 2 3 4 5 6
+
+ +
14 Operation of Commubox FXA195 in a control loop powered by a transmitter power supply. From the
control room via the communication sockets of the transmitter power supply.
2 Commubox FXA195
3 USB
4 FieldCare
Endress+Hauser 29
1 2 3 4 5 6
+
+ +
loop (communication resistor of FXA195 on)
2 Commubox FXA195
3 USB
4 FieldCare
1 2 3 4 5 6
+
+ +
16 Operation of Commubox FXA195 in a control loop powered by a transmitter power supply. Via a resistor
250 (recommended 270 to 330 ) in the control loop (communication resistor of FXA195 off)
2 Commubox FXA195
3 USB
4 FieldCare
1 2 3 4 5 6
+
+ +
loop (loop-resistance 250 )
2 Commubox FXA195
3 USB
4 FieldCare
30 Endress+Hauser
6.2 Installing the Commubox FXA195 driver

Normally the computer automatically recognizes the Commubox FXA195. If this is
not the case, the driver must be installed as described in Appendix C. 182
Installing the driver

1. Check the COM port:
Select Configuration Control Panel System.
2. Click Device Manager.
3. Open Ports (COM and LPT).
The COM port is displayed and assigned to the Commubox.


The HART CommDTM is added to the network.
Endress+Hauser 31

7. Set the parameters in the HART Communication (Configuration) dialog.

Serial interface: COMx, the interface is in the drop-down menu
HART protocol master: Secondary Master
8. Click OK.
32 Endress+Hauser

Parameterize.
Save the project as described in Chapter 3.3.2. 17
iDTM.
Endress+Hauser 33
HART via Fieldgate FXA520 and Pepperl+Fuchs multiplexer Tutorial for FieldCare projects
7 HART via Fieldgate FXA520 and

Pepperl+Fuchs multiplexer
7.1 Use cases

To see the HART devices in the use cases detailed below, FieldCare requires:
Fieldgate FXA520 CommDTM
HART multiplexer master KFD2-HMM-16 (FDT) CommDTM
HART DeviceDTMs
Fieldgate FXA520 must be commissioned and assigned a network IP address before
a connection can be established. See the Operating Instructions BA00051S/04/en
for this purpose.
Furthermore, the computer must be assigned to a network address in same domain
as Fieldgate FXA520 before it can connect with its CommDTM, see Appendix A.
181
7.1.1 Parallel access to HART control loop with 4 to 20 mA

In this use case, the HART devices are connected to an analog I/O card (4 to 20 mA) of a
programmable logic controller. Normally, the devices will be powered by the card, but in
the case of 4-wire devices an external power supply will be required. Two-wire devices can
also be used in active mode, in which case external power sources will also be required.
The HART signal is accessed via a multiplexer and Fieldgate FXA520.
34 Endress+Hauser
Tutorial for FieldCare projects HART via Fieldgate FXA520 and Pepperl+Fuchs multiplexer
1 2
3
7
Fieldgate
FXA520
5 4
18 Parallel access to HART control loops with 4 to 20 mA

1 FieldCare
2 Ethernet
3 FieldgateFXA520
4 Pepperl+Fuchs HART multiplexer
5 Pepperl+Fuchs HART Termination Board
6 RS485
7 Controller with I/O cards
When the Pepperl+Fuchs KFD2-HMM-16 multiplexer is used it is possible to connect

30 devices to one Fieldgate FXA520. They can be arranged as 15 + 15 or as 16 + 14.
7.1.2 Direct/remote access to a HART monitoring system

This use case is a typical Fieldgate FXA520 inventory monitoring application where the
process values are acquired via a HART multiplexer. The same architecture can be used to
give FieldCare access to the devices for parameterization.
Endress+Hauser 35
1 2
3
Fieldgate
FXA520
4 4
5 5
ENDRESS+HAUSER ENDRESS+HAUSER
RNS221 RNS221
ON 1 2 ON 1 2
CH2 CH2
CH1 CH1
6 7 6
19 Direct/remote access to a HART monitoring system

1 FieldCare
2 Ethernet
3 FieldgateFXA520
4 Pepperl+Fuchs HART multiplexer
5 Pepperl+Fuchs HART Termination Board
6 Power supply e.g. RN211N-B or RNS211
7 RS485
In this case, the devices must be powered, e.g. by a RNS221 or RN211N-B power unit
for non-hazardous and hazardous areas respectively. Each power supply can power
two devices. A maximum of 30 devices can be connected to one Fieldgate FXA520.

The following example shows how the Fieldgate FXA520 can be commissioned with
FieldCare. It is assumed that the FXA520 DTM is already installed.
7.2.1 Connecting and configuring Fieldgate FXA520

36 Endress+Hauser

4. In the Add New Device dialog, select the FXA520 item and click OK.
The FXA520 is added to the network.
5. In the Network dialog, right-click FXA520.
Endress+Hauser 37
The FXA520 (Configuration) dialog appears.
7. Enter the following parameters in the FXA520 (Configuration) dialog and press
Enter to confirm each entry.
If the user name and password of the FXA520 (default: super/super) have been
changed, the values must be entered in the appropriate fields.
Access Mode: Fieldgate direct
Connection Type: LAN Fieldgate
Communication Mode: Direct (pass-through-HART)
Remote IP Address: IP address of the Fieldgate (default: 192.168.252.1)
8. Close the FXA520 (Configuration) dialog by clicking X in the top right-hand corner.

The Select Communication Channel dialog appears.
11. Select the RS485CH option.
38 Endress+Hauser
12. Click OK.

The scan is started.
13. Click OK.
The multiplexer DTM is added to the network.
FieldCare is connected and configured.
If only one multiplexer is found, its DTM is added to the network. If there are two
multiplexers or if the DTM quality does not equal "1", the Scanning Result dialog opens
automatically.
7.2.2 Commissioning the Pepperl+Fuchs multiplexer

When the multiplexer is added to the network, the Configuration dialog of the
multiplexer opens automatically. If this is not the case or if two multiplexers are
connected to Fieldgate FXA520, you must invoke the Configuration dialog manually.
Commissioning the multiplexer

1. Right-click the KFD2-HMM-16 (FDT) item and select Configuration.
The Configuration dialog opens.
2. Enter all the necessary information, e.g. the tag and description.
3. Click the X in the top right-hand corner.
The multiplexer DTM closes.
4. In the Network dialog, right-click Multiplexer.
Endress+Hauser 39
6. In the Add New Device dialog, select the KFD2-HMM-16 (FDT) item and click OK.
The multiplexer is added to the network.
Although from the hardware point of view only one unit exists, at least two DTMs are
required for the multiplexer head station. These comprise a master KFD2-HMM-16
(Master) and a slave KFD0-HMS-16 (Slave00). Additional slaves must be added
according to the number of multiplexer channels in use.
Assigning device to channel

1. In the Assign Device to Channel dialog, select the Slave00 item.

2. Click OK.
The slave is added to the Network dialog.
If a second master or additional slave is present, repeat Steps 1 and 2 to add it to the
Network View.
Fieldgate FXA520 can handle a maximum of 30 devices with its Web server. For
FieldCare the number is higher, but the FXA520 cannot be used to display the
measured values.
Creating a network
1. In the Network dialog, right-click a Slave.
40 Endress+Hauser

3. Click OK.
All the connected devices are scanned.
The project looks something like this:
4. In the Network dialog, right-click a device.

5. Select Online Parameterize.
The DeviceDTM opens. If the DeviceDTM is not connected, first select Connect.
The device can now be configured in accordance with the Operating Instructions.
Endress+Hauser 41
HART via Pepperl+Fuchs LB/FB Remote I/O Tutorial for FieldCare projects
8 HART via Pepperl+Fuchs LB/FB Remote I/O
8.1 Application
This chapter describes how FieldCare should be configured for a plant that uses a Pepperl
+Fuchs LB/FB Remote IO. The PC with FieldCare installed is connected to a PLC (e.g. a
Melsec Q12 from Mitsubishi) via Ethernet. The PLC connected with the Remote IO via
PROFIBUS DP; Remote I/O is connected to several HART field devices.
The following software packages must be installed and configured on the PC:
Mitsubishi CommDTM: Download at http://www.mitsubishielectric.com
MXCommDTMPBDPsetup.exe
CommDTM Remote IO: Download at http://www.pepperl-fuchs.com
DTM_RemoteIO_LB_FB-setup-Vx.exe
5 3
20 Access via Pepperl+Fuchs LB/FB Remote I/O


42 Endress+Hauser
Tutorial for FieldCare projects HART via Pepperl+Fuchs LB/FB Remote I/O
4. In the Add New Device dialog, select the MXCommDTM-PBDP item and click OK.
MXCommDTM-PBDP is added to the network.
A different device-specific CommDTM must be used for other PLCs.
5. In the Network dialog, right-click MXCommDTM-PBDP.

7. In the Add New Device dialog, select the LB 8109 LB-DPV1 UNICOM Interface item
and click OK.
LB 8109 LB-DPV1 UNICOM Interface is added to the network.
8. In the LB 8109 LB-DPV1 UNICOM Interface dialog, right-click LB 8109 LB-DPV1

UNICOM Interface.

A dialog opens.
Endress+Hauser 43
HART via Pepperl+Fuchs LB/FB Remote I/O Tutorial for FieldCare projects
10. Select communication channels and slots that are scanned.

Cards are scanned.
11. In the Create Network - Scan Result dialog, select SLOT 03 and click Assign Device
Type (DTM).
The Assign Device Type (DTM) dialog opens.
12. Tick the box Show All Installed Device Types of this Protocol.
All the device types installed for this protocol are displayed.
13. Select the device DTM LB3106 HART Transmitter Power Supply and click OK.
The LB 3106 HART transmitter power supply is assigned to SLOT 03.
Repeat the previous step for all the DeviceDTMs found and press OK to confirm.
FieldCare can be used once all the DeviceDTMs have been assigned.
The Pepperl+Fuchs FB/LB can be used with a Fieldgate SFG500 in the same way.
44 Endress+Hauser
Tutorial for FieldCare projects HART via RS232 to RS485 converter and Pepperl+Fuchs multiplexer
9 HART via RS232 to RS485 converter and

Pepperl+Fuchs multiplexer
9.1 Use cases

RS232 to RS485 to converter (e.g. ExpertDAQ EX9520)
HART multiplexer master KFD2-HMM-16 (FDT) CommDTM
HART DeviceDTMs
9.1.1 Direct/remote access to a HART monitoring system

This use case is a typical application where the process values are acquired via a HART
multiplexer (MUX). The same architecture can be used to give FieldCare access to the
devices for parameterization.
1 2
3
Fieldgate
FXA520
ENDRESS+HAUSER
RNS221
ON 1 2
CH2
CH1
5 4
21 Direct/remote access to a HART monitoring system

1 FieldCare
2 RS232
3 RS232 to RS485 converter e.g. ExpertDAQ EX9520
4 Pepperl+Fuchs HART multiplexer (KFD2-HMM-16)
5 Pepperl+Fuchs HART termination board (FI-PFH-110469)
6 Power supply e.g. RN211N-B or RNS211
7 RS485
In this case, the devices must be powered, e.g. by a RNS221 or RN211N-B power unit
for non-hazardous and hazardous areas respectively.
Endress+Hauser 45
HART via RS232 to RS485 converter and Pepperl+Fuchs multiplexer Tutorial for FieldCare projects

The following example shows how the multiplexer can be commissioned with FieldCare.
As a prerequisite, the HART Comm DTM must be installed and the PC must have a serial
interface to COM1. In addition, the Pepperl+Fuchs drivers must be installed: DTM
Collection HART Multiplexer/DTM Collection HART Multiplexer on the Pepperl+Fuchs
homepage www.pepperl-fuchs.com
9.2.1 Connecting and configuring Fieldgate SFG500


The HART Communication DTM is added to the network.
7. The parameters must be recorded in the HART Communication (Configuration)

dialog.
Communication Interface: HART multiplexer
Serial Interface: COM1
Baud Rate: 9600
RTS Control: Disable
HART Protocol: Primary Master
Preamble and Number of Communication Retries: leave default setting
Address Scan: Start and end address set to 1
8. In the Network dialog, right-click the HART Communication item.
46 Endress+Hauser
Tutorial for FieldCare projects HART via RS232 to RS485 converter and Pepperl+Fuchs multiplexer

Scanning is performed.
If the message Automatic DTM identification of one or more devices failed
appears, click OK to confirm.
The KFD2-HMM-16(FDT) item is added to the network.
10. In the Network dialog, right-click the KFD2-HMM-16(FDT) item.

11. Select Add New Devices.
12. In the Add New Device dialog, select the KFD0-HMS-16 item and click OK.
The Assign Device to Channel dialog appears.
13. Select Slav00 as the channel because the KFD2-HMM-16 is the master and slave and
the slave automatically and unalterably has 0 as its address.
The KFD0-HMS-16 is added to the network.
Endress+Hauser 47
HART via RS232 to RS485 converter and Pepperl+Fuchs multiplexer Tutorial for FieldCare projects
14. In the Network dialog, right-click the KFD0-HMS-16 item.

The channels correspond to the ports on the KFD0-HMS-16 termination board.

15. Typically select all the channels to which HART devices are connected and press OK
to confirm.
All the connected devices are displayed and can be changed.
A successful connection is not possible via USB serial converter and RS232/RS485
interface converter.
48 Endress+Hauser
Tutorial for FieldCare projects HART via Rockwell Automation ControlLogix
10 HART via Rockwell Automation ControlLogix
10.1 Application
The PlantPAx is a system to which different Rockwell Automation modules can be
appended. The following range of I/O modules can be used:
HART I/O 1756sc-IF8H, 1756sc-IF16H, 1756sc-OF8H
FLEX I/O 1794sc-IF8IH
POINT I/O 1734sc-IE4CH, 1734sc-IE2CH, 1734sc-OE2CIH
COMPACT I/O 1769sc-IF4IH, 1769sc-IF20H
HART CommDTM
HART DeviceDTMs
RSLinx Classic
4
5
6
22 Access via ControlLogix to a HART network

1 FieldCare
2 Ethernet
3 ControlLogix HART I/O
4 Flex I/O
5 Point I/O
6 Compact I/O

The FieldCare catalog must be updated before you can start connecting, see
Appendix E. 183
The following example shows how to establish a connection with ControlLogix.
Endress+Hauser 49
HART via Rockwell Automation ControlLogix Tutorial for FieldCare projects

4. Select RSLinx 1756 Backplane and click OK.

The RSLinx 1756 Backplane is added to the network.
5. In the Network dialog, double-click RSLinx 1756 Backplane in the
Device Type (DTM) column.
The RSLinx 1756 Backplane (Configuration) dialog appears.
6. Click Select Path.

The Select 1756 Backplane dialog opens.
7. Open the AB-ETHIP-1, Ethernet item. (This name can be selected individually)
8. Select a device and click OK.
The device is added to the network.
9. Enter the slot number and press Enter to confirm.
10. In the Network dialog, right-click the RSLinx 1756 Backplane item.

FieldCare scans the network and indicates the result. The DeviceDTM is added to
the network.
50 Endress+Hauser
Tutorial for FieldCare projects HART via Rockwell Automation ControlLogix

If no DeviceDTM is installed, FieldCare states that proper communication can only
be ensured after the DTM has been installed.
There is no possibility to connect to the device, if the matching DTM is not installed.
Right-click Device and select Connect.
Right-click Device and select Online Parameterize.
10.3 Access to device data

Device access
2. Select Connect.
The DeviceDTM is connected and all the arrows appear green.
3. In the Network dialog, double-click the connected device in the Device Type (DTM)
column.
The device data are displayed.
5. Click Observe.
The measured values are displayed.
FieldCare offers additional functions, such as:

Switching device mode to connected or not connected
Reading data from the device
Writing data to the device
Device-specific functions
Endress+Hauser 51
HART via RSG45 Tutorial for FieldCare projects
11 HART via RSG45
11.1 Application
1 2 3 4
23 Connection with RSG45 HART communication

1 FieldCare
2 Ethernet
3 Memograph M RSG45
4 Slot
To see all the devices on the HART segment, FieldCare requires:

RSG45 HART CommDTM
HART DeviceDTMs


4. In the Add New Device dialog, select the RSG45 HART Communication item and
click OK.
RSG45 HART Communication is added to the network.
52 Endress+Hauser
Tutorial for FieldCare projects HART via RSG45
5. In the Network dialog, right-click RSG45 HART Communication.

The RSG45 HART Communication (Configuration) dialog appears.
7. On the Configuration tab, enter the RSG45 IP address, the RSG45 port and the
address range for scanning the Memograph M RSG45, and then click Apply.
8. In the Network dialog, right-click RSG45 HART Communication.
Endress+Hauser 53
HART via RSG45 Tutorial for FieldCare projects

10. Select the channels to be scanned and click OK.

FieldCare scans the selected channels and adds the devices found to the network.
12. Select Connect.

The arrows next to the device appear green.
54 Endress+Hauser
Tutorial for FieldCare projects HART via RSG45


The DeviceDTM opens.
The device can now be configured as described in BA00096S/04/en.

Endress+Hauser 55
HART Multidrop or HART point-to-point connection via Fieldgate FXA520 Tutorial for FieldCare projects
12 HART Multidrop or HART point-to-point

connection via Fieldgate FXA520
12.1 Use cases

HART CommDTM
HART DeviceDTMs
Fieldgate FXA520 must be commissioned and assigned a network IP address before
a connection can be established. See the Operating Instructions BA00051S/04/en.
The computer must be assigned to a network address in same domain as Fieldgate
FXA520 before it can connect with its CommDTM, see Appendix A. 181
12.1.1 HART Multidrop

This use case is a typical Fieldgate FXA520 inventory monitoring application where the
process values are acquired via a HART Multidrop bus. The same architecture can be used
to give FieldCare access to the devices for parameterization.
1 2
3
ENDRESS+HAUSER
RNS221
6 Fieldgate
FXA520 ON 1 2
CH2
CH1
5 4
24 HART Multidrop via Fieldgate FXA520

1 FieldCare
2 Ethernet
3 Fieldgate FXA520 Multidrop power supply
4 Channel 0 with maximum 8 devices
5 Channel 1 with maximum 8 devices
6 FieldgateFXA520
12.1.2 HART point-to-point connection

The two HART channels (4 to 20 mA) of the Fieldgate FXA520 can also be used to make
point-to-point connections to individual HART devices.
56 Endress+Hauser
Tutorial for FieldCare projects HART Multidrop or HART point-to-point connection via Fieldgate FXA520
1 2
ENDRESS+HAUSER
3
RNS221
6 Fieldgate
FXA520 ON 1 2
CH2
CH1
5 4
25 HART point-to-point connection via Fieldgate FXA520

1 FieldCare
2 Ethernet
3 HART power supply
4 Channel 0
5 Channel 1
6 FieldgateFXA520

The following example shows how the Fieldgate FXA520 can be commissioned with
FieldCare. It is assumed that the FXA520 DTM is already installed.

4. In the Add New Device dialog, select the FXA520 item and click OK.
The FXA520 is added to the network.
Endress+Hauser 57

The FXA520 (Configuration) dialog appears.
7. Enter the following parameters in the FXA520 (Configuration) dialog and press
Enter to confirm each entry.
If the FieldCare user name and password have been changed, the values must be
entered in the appropriate fields.
Access Mode: Fieldgate direct
Connection Type: LAN Fieldgate
Communication Mode: Direct (pass-through-HART)
Remote IP Address: IP address of the Fieldgate (default: 192.168.252.1)
8. Close the FXA520 (Configuration) dialog by clicking X in the top right-hand corner.
58 Endress+Hauser
Tutorial for FieldCare projects HART Multidrop or HART point-to-point connection via Fieldgate FXA520

11. Select the HARTCH0 and/or HARTCH1 option (select both in this case) and click OK.
The scan is started. The devices found are assigned to their DTMs and added to
the project.

13. Select Connect.

The connection to the DeviceDTM is established.
Endress+Hauser 59

60 Endress+Hauser
Tutorial for FieldCare projects HART point-to-point or HART Multidrop via MACTek Bluetooth modem
13 HART point-to-point or HART Multidrop via

MACTek Bluetooth modem
13.1 Use cases

HART CommDTM
HART DeviceDTMs
Bluetooth must be enabled on the computer.
The Bluetooth modem must be installed on the computer and the Bluetooth
connection set up. The number of the COM port to which the modem is connected is
required for this purpose. This appears during setup or in the Properties window.
The Endress+Hauser HART CommDTM can be used as the HART communication
DTM.
13.1.1 Point-to-point connection

In a point-to-point connection, the MACTek modem is connected in parallel to the
measuring device or in parallel to the communication resistor.
1 2 3 3 4 5
+ +
1 2 3 3 4 5
+ +
26 Operation of a MACTek modem in a control loop (I/O card active/device passive or vice versa)
1 I/O card PLC/DCS active or passive
2 MACTek modem
3 Bluetooth
4 FieldCare
13.1.2 Multidrop connection

In a Multidrop connection, the MACTek modem is connected to the bus line.
Endress+Hauser 61
HART point-to-point or HART Multidrop via MACTek Bluetooth modem Tutorial for FieldCare projects
1 2 3 3 4
5 5 5
27 Operation of a MACTek modem with the HART Multidrop bus

1 I/O card PLC/DCS active or passive
2 MACTek modem
3 Bluetooth
4 FieldCare
5 Passive field device (0-15 devices)

1. Switch on the MACTek modem.
2. In the Bluetooth Settings dialog, select Bluetooth New Connect.


62 Endress+Hauser
Tutorial for FieldCare projects HART point-to-point or HART Multidrop via MACTek Bluetooth modem

HART Communication is added to the network.
The COM40 (Configuration) dialog appears.
Endress+Hauser 63
HART point-to-point or HART Multidrop via MACTek Bluetooth modem Tutorial for FieldCare projects
9. Set the parameters in the COM40 (Configuration) dialog.

Serial interface: COMx, the interface is in the drop-down menu
HART protocol master: 5
10. Click OK.

Parameterize.
iDTM.
64 Endress+Hauser
Tutorial for FieldCare projects HART via IFAK Ethernet gateway
14 HART via IFAK Ethernet gateway
14.1 Application
1 2 3 4
28 Connection with IFAK HART Ethernet gateway

1 FieldCare
2 Ethernet
3 RNS221
4 HART IFAK Ethernet gateway
Before a connection can be established between FieldCare and the device it is

necessary to check whether the gateway is accessible in the network.


4. In the Add New Device dialog, select the isNet Lite item and click OK.
isNet Lite is added to the network.
Endress+Hauser 65
HART via IFAK Ethernet gateway Tutorial for FieldCare projects
5. In the Network dialog, right-click isNet Lite.

The isNet Lite (Configuration) dialog appears.
7.
Enter the IP address, select channel and click OK.

8. In the Add New Device dialog, select the isNet H@rt(8 channels) item and click OK.
isNet H@rt(8 channels) is added to the network.
9. In the Network dialog, right-click isNet H@rt(8 channels).
10. Select Offline Parameterize.
The isNet H@rt(8 channels) (Offline Parameterize) dialog is displayed.
66 Endress+Hauser
Tutorial for FieldCare projects HART via IFAK Ethernet gateway

The configuration can now be made.
Endress+Hauser 67
HART via HIMA multiplexer HIMAX Tutorial for FieldCare projects
15 HART via HIMA multiplexer HIMAX
15.1 Application
A PC with FieldCare is connected via Ethernet to a HIMA multiplexer HIMAX to which
several HART devices are connected.
1 2 3
29 Connection with HIMAX HART multiplexer

1 FieldCare
2 Ethernet
3 HIMA multiplexer HIMAX
To see all the devices on the HART segment, FieldCare requires three DTMs:
HIMA HART IP CommDTM
HIMA X ComDTM
HIMA HART DeviceDTM
In addition, two setups must be downloaded from the HIMA website (www.hima.com) and
executed:
HIMAX_DTM_SETUP_1_0_0_1
EMUXCommDTM_HIMA_Setup_1_1_0_6


4. In the Add New Device dialog, select the HART IP Communication item and click
OK.
HART IP Communication is added to the network.
5. In the Network dialog, right-click HART IP Communication.
68 Endress+Hauser
Tutorial for FieldCare projects HART via HIMA multiplexer HIMAX
6. Select Other Functions DTM Addresses.

The HART IP Communication configuration window opens.
7. The IP address of the multiplexer must be configured in the UDP Address field.
10. In the Add New Device dialog, select the X-COM-DTM item and click OK .
X-COM-DTM is added to the network.
11. In the Network dialog, right-click X-COM-DTM.
12. Select Connect.
The connection is established.
13. In the Network dialog, right-click Additional Functions HART Modules.
The available modules are added under the X-COM-DTM (X-HART-DTM items).
14. In the Network dialog, right-click X-HART-DTM.
16. In the Add New Device dialog, select the Create Network item and click OK.
A dialog appears in which all the available HART channels are displayed.
In this dialog it is possible to disable HART channels that are not used and are
excluded from subsequent scanning in order to speed up the process. After scanning,
all the HART devices found are displayed in the network view and can be configured.
Endress+Hauser 69
WirelessHART Adapter SWA70 via HART modem Tutorial for FieldCare projects
16 WirelessHART Adapter SWA70 via HART

modem
16.1 Application
With regard to operation with FieldCare, the WirelessHART Adapter SWA70 acts like all
other HART devices. The connection can be established with a standard HART modem,
such as Commubox FXA191, Commubox FXA195 or MACTek.
1 2 2 3 4
1 6 5 4
30 Connection of a HART modem with the WirelessHART Adapter SWA70

1 FieldCare
2 Bluetooth
3 MACTek modem
4 WirelessHART Adapter terminals 7 and 8
5 HART Modem
6 USB or RS232
The HART modem can be connected either to terminals 5 and 6 or to terminals 7 and 8
of the WirelessHART Adapter.
A 250 communication resistor must be used for communication via the MACTek
modem, see Chapter 5.1 and 13.1. 23 61
A 250 communication resistor must be used or switched on for communication via
Commubox FXA195.
If the WirelessHART Adapter is operated in a control loop with a communication resistor
no additional resistor is needed.
The COM port number is assigned when installing the Commubox FXA195 or MACTek
modem. This number is required later on.
To establish the connection via FieldCare, the COM port must be configured for the
selected HART modem. The HART CommDTM and the SWA70 DTM are needed for
the SWA70.

Check whether the WirelessHART Adapter is connected to a power supply unit and is
in the communication mode, see BA00061S/04/en.
70 Endress+Hauser
Tutorial for FieldCare projects WirelessHART Adapter SWA70 via HART modem


HART Communication is added to the network.
Endress+Hauser 71
WirelessHART Adapter SWA70 via HART modem Tutorial for FieldCare projects
7. Enter the following parameters in the HART Communication (Configuration)

dialog and press Enter to confirm each entry.
Serial port: e.g. COMx (port the modem is connected to)
HART protocol master: Secondary Master
Address scan start address: 14 since scanning is quicker
Address scan start address: 15 since this is the default address of the
WirelessHART Adapter
8. Click OK.
9. In the Network dialog, right-click COM8.

The WirelessHART Adapter is added to the network and the WirelessHART
Adapter DTM opens.
More information about configuring the adapter can be found in the Operating
Instructions BA00061S/04/en.
72 Endress+Hauser
Tutorial for FieldCare projects WirelessHART Fieldgate SWG70 via Ethernet
17 WirelessHART Fieldgate SWG70 via Ethernet
17.1 Application
The WirelessHART Fieldgate SWG70 is configured via its Ethernet interface.
1 2 3
31 Connection with the WirelessHART Fieldgate SWG70 via Ethernet

1 FieldCare with address 192.168.1.xxx
2 Ethernet
3 Fieldgate SWG70 with address 192.168.1.1
Fieldgate SWG70 is supplied with the default address of 192.168.1.1. This matches the
default address of the HART IP CommDTM.
The computer and the SWG70 must be in the same address domain (IP address, subnet
mask). This must be taken into consideration if the address of the computer or SWG70 is
changed.
To see the Fieldgate SWG70, FieldCare requires:
HART IP CommDTM
SWG70 DTM
The HART IP CommDTM and the SWG70-DTM are needed to connect via FieldCare.

Endress+Hauser 73
WirelessHART Fieldgate SWG70 via Ethernet Tutorial for FieldCare projects

4. In the Add New Device dialog, select the HART IP Communication item and click
OK.
HART IP Communication is added to the network.

7. Select WirelessHART Fieldgate and click OK.

FieldCare automatically recognizes and selects the right DTM and the Add New
Device dialog closes.
74 Endress+Hauser
Tutorial for FieldCare projects WirelessHART Fieldgate SWG70 via Ethernet
8. If the configured IP address (192.168.1.1) or the Ethernet port (5094) of the

Fieldgate SWG70 has been changed or a new Fieldgate address must be entered,
proceed as follows:
In the Network dialog, right-click HART IP Communication.
9. Select Other Functions Set DTM Addresses.

The HART IP Communication (Set DTM Addresses) dialog opens.
10. Enter the new IP address and/or Ethernet UDP port number.
11. Click Update Changed Data.
12. Close the HART IP Communication (Set DTM Addresses) dialog.
13. Right-click on the WirelessHARTFieldgate entry in the Network dialog.
14. Select Connect.

The HART IP CommDTM and WirelessHART Fieldgate are connected and all
the arrows appear green.
15. In the Network dialog, click WirelessHART Fieldgate.
Endress+Hauser 75
WirelessHART Fieldgate SWG70 via Ethernet Tutorial for FieldCare projects

The WirelessHART Fieldgate (Online Parameterize) dialog opens.
17. In the WirelessHART Fieldgate dialog, expand all the submenus of the directory tree
to reveal the parameter blocks.
Start the configuration as described in Operating Instructions BA00064S/04/en.
The WirelessHART Fieldgate DTM can also be used to scan for WirelessHART
Adapters and devices in the network. A full description is provided in Operating
Instructions BA00064S/04/en.
76 Endress+Hauser
Tutorial for FieldCare projects Modbus via RS485 Modbus
18 Modbus via RS485 Modbus
18.1 Application
1 2 3
32 Connection with Modbus via RS485 Modbus

1 FieldCare
2 RS485 Modbus
3 Field device
To see all the devices on the Modbus segment, FieldCare requires:

Modbus DTM
Modbus DeviceDTMs


4. In the Add New Device dialog, select the Modbus Serial Communication DTM item
and click OK.
The Modbus Serial Communication DTM is added to the network.
Endress+Hauser 77
Modbus via RS485 Modbus Tutorial for FieldCare projects
5. In the Network dialog, right-click Modbus Serial Communication DTM.

The Modbus Serial Communication DTM (Configuration) dialog opens.
7. On the Configuration tab, select COM3 for the COM port.

8. Select the Request tab.
9. For the request mode, select Single-point, enter the address 247 and click Apply.
The changes are accepted and saved.
10. In the Network dialog, right-click Modbus Serial Communication DTM.

FieldCare scans the network and indicates the result. The
MODBUS_SERIALCommChannel is added to the network.
The Online Parameterize dialog is displayed and the device can be
parameterized.
78 Endress+Hauser
Tutorial for FieldCare projects EtherNet/IP via Ethernet
19 EtherNet/IP via Ethernet
19.1 Application
1 2 3
33 Connection with EtherNet/IP via Ethernet

1 FieldCare
2 Ethernet
3 Field device
To see all the devices on the Ethernet segment, FieldCare requires:

EtherNet/IP CommDTM
EtherNet/IP DeviceDTMs


4. In the Add New Device dialog, select the EtherNet/IP Comm Adapter item and click
OK.
EtherNet/IP Comm Adapter is added to the network.
Endress+Hauser 79
EtherNet/IP via Ethernet Tutorial for FieldCare projects
5. In the Network dialog, right-click EtherNet/IP Comm Adapter.

The EtherNet/IP Comm Adapter (Configuration) dialog opens.
7. On the Configuration tab, enter the IP address of the PC under host address.
8. Select the Request tab.
9. For the request mode, select Multi-point, enter the IP address start address and
click Apply.
The changes are accepted and saved.
10. In the Network dialog, right-click EtherNet/IP Comm Adapter.

FieldCare scans the network and indicates the result. The device is added to the
network.
The Online Parameterize dialog is displayed and the device can be
parameterized.
80 Endress+Hauser
Tutorial for FieldCare projects PROFINET - PROFIBUS PA Softing Gateway
20 PROFINET - PROFIBUS PA Softing Gateway
20.1 Application
The Softing PROFINET PROFIBUS PA Gateway pnGATE PA allows a PROFINET network
to connect to a PROFIBUS PA segment. A PC with FieldCare is connected to the PROFINET
network via a switch.
To see all the devices on the PROFIBUS PA segment, FieldCare requires:
PROFIBUS DeviceDTMs
PROFIdtm DPV1 CommDTM
PROFIBUS driver PROFIboard
1 2 3
5
6
34 Connecting FieldCare with a PROFINET - PROFIBUS PA Gateway

1 FieldCare
2 Ethernet
3 Gateway
4 PROFINET
5 Gateway pnGATE PA
6 PROFIBUS PA
20.2 Setting up the gateway

Before establishing a connection with FieldCare, it is necessary to configure the
PROFIBUS Control Panel for the pnGATE and the IP address, see the User Manual
pnGate PA.
Endress+Hauser 81
PROFINET - PROFIBUS PA Softing Gateway Tutorial for FieldCare projects


4. In the Add New Device dialog, select the PROFIdtm DPV1 item and click OK.
The PROFIdtm DPV1 is added to the network.
5. The Node Name (default: Node0) entered previously in the PROFIBUS Control Panel
must be selected in the Board Name field. The other parameters must be checked
and modified as they can vary depending on the plant. The parameters in the Group
Runtime Performance are supplied by the PLC and cannot be modified.
6. In the Network dialog, right-click the PROFIdtm DPV1 item.
FieldCare now scans the network and adds all devices found to the network.
82 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS PA via Rockwell Automation ControlLogix
21 PROFIBUS PA via Rockwell Automation

ControlLogix
21.1 Application
The PlantPAx architecture provides a manufacturer and user technology such that the
input data and the output condition can be used by all ControlLogix controllers in the
system.
4
5
35 ControlLogix access to a PROFIBUS PA network

1 FieldCare
2 Ethernet
3 ControlLogix
4 1788HP-EN2PAR
5 PROFIBUS PA
To see the PROFIBUS-PA devices, FieldCare requires:

HS EtherNet/IP DTM
1788-EN2PAR DTM
PROFIBUS DeviceDTMs

The FieldCare catalog must be updated before you can start connecting, see Appendix
E. 183
Endress+Hauser 83
PROFIBUS PA via Rockwell Automation ControlLogix Tutorial for FieldCare projects

4. Select HS EtherNet/IP and click OK.

The HS EtherNet/IP is added to the network.
5. In the Network dialog, right-click HS EtherNet/IP.
7. Select 1788-EN2PAR and click OK.

8. In the Network dialog, double-click 1788-EN2PAR in the Device Type (DTM)
column.
The 1788-EN2PAR (Configuration) dialog appears.
9. Enter the Module IP Address and the Max Scan Address and press Enter to
confirm.
84 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS PA via Rockwell Automation ControlLogix
10. In the Network dialog, right-click the 1788-EN2PAR item.


FieldCare scans the network and indicates the result. The 1788-EN2PAR-DTM is
added to the network.
13. Select Connect.
All the arrows appear green.
The 1788-EN2PAR (Online Parameterize) dialog appears.
Endress+Hauser 85
PROFIBUS DP/PA via Fieldgate FXA720 Tutorial for FieldCare projects
22 PROFIBUS DP/PA via Fieldgate FXA720
22.1 Application
This use case is typical for the use of Fieldgate FXA720 to provide parallel access to a
PROFIBUS control system, e.g. for device set-up, device diagnosis or condition monitoring.
Fieldgate FXA720 operates as a Master Class 2 and uses non-cyclic communication.
A similar architecture, but not necessarily with a controller, could be used for the
monitoring of tank inventory in connection with SupplyCare software. In this case
FieldCare is used for set-up and diagnosis only.
To see the PROFIBUS DP/PA devices, FieldCare requires:
PROFIBUS CommDTM
PROFIBUS DeviceDTMs
A transparent coupler is one that does not require a CommDTM to connect to the
PROFIBUS PA devices beneath it. Pepperl+Fuchs DP/PA couplers are examples. If a
Siemens coupler or link is used, a CommDTM is required for it. The procedure for
connecting is analogous to that described in this chapter, the link being found during the
creation of the network after the Fieldgate FXA720 CommDTM has been added to the
FieldCare host.
1 2
ON FAIL DP
ETH RUN
L+
3
+24VDC
7
COM
PROFIBUS DP
ETHERNET
Fieldgate FXA720
36 Fieldgate FXA720 access to a PROFIBUS DP/PA network

1 FieldCare
2 Ethernet
3 Fieldgate FXA720
4 PROFIBUS DP
5 PROFIBUS PA
6 Transparent DP/PA coupler
86 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP/PA via Fieldgate FXA720
22.2 Commissioning the Fieldgate FXA720
22.2.1 Basic configuration

Fieldgate FXA720 must be assigned to an IP address and, when used with FieldCare, the
PROFIBUS scan function must be disabled. This is done in the Fieldgate FXA720 Web
server.
Before this procedure can be started, the IP address that Fieldgate is allocated
within the control network must be known.
If the Web browser does not find the Web server, it is essential to check whether a
proxy is in use and to switch it off if necessary.
Commissioning the Fieldgate FXA720

Set the IP address of the computer to the same domain as the Fieldgate FXA720's default
address 192.168.253.1. See Appendix A or consult your system administrator if this is
unclear. 181
1. Start the Web browser.

2. Enter the Fieldgate FXA720's default address 192.168.253.1 into the address field
of the browser and press Enter to confirm.
The browser makes a connection with the Fieldgate FXA720 and the Login
dialog opens.
3. Enter superb as the password and click Login.

The Fieldgate FXA720 Web server opens. (Devices are not necessarily visible at
this point).
4. Click Switch to Specialist Mode.

The Login dialog opens.
5. Enter admin as the user name and super as the password and click Login.
6. Click Information & Configuration PROFIBUS Setup.
Endress+Hauser 87
7. Scroll down to the Scan 1 dialog.

The Scan 1 dialog appears.
8. Set Scan Cycle Time to Off.

This disables the PROFIBUS scan.
9. Click Send.
Changes are downloaded to Fieldgate FXA720.
10. Click Information & Configuration Network Setup.
11. Scroll down to the Ethernet dialog.
The Ethernet dialog appears.
12. Enter the IP address and Subnet Mask.

13. Click Send.
Parameters are downloaded to Fieldgate FXA720.
14. Close the Web browser and reset the computer IP address to one in the same domain
as the new Fieldgate FXA720 IP address.
15. Enter the new IP address in the Web browser once more to check the connection to
Fieldgate FXA720.
16. Close the Web browser.
22.2.2 Connection procedure

Fieldgate FXA720 must be commissioned before it can be used. This is done by either
running the set-up program supplied on the accompanying DVD or calling the
PROFIBUS Control Panel Applet from the PROFIBUS DPV1 CommDTM.
The Fieldgate FXA720 set-up routine is described in Operating Instructions
BA00030S/04/en.
Starting the PROFIBUS Control Panel

1. Start the PROFIBUS Control Panel Applet.
88 Endress+Hauser
2. In the Network dialog, right-click PROFIBUS DPV1 CommDTM.

3. Select Other Functions PROFIBUS Control Panel Applet.

The PROFIBUS Control Panel dialog opens.
For this to happen, the PROFIBUS DVP1 CommDTM must have been added to the
HOST PC beforehand.
PROFIBUS set-up
1. In the PROFIBUS Control Panel dialog, select the FG series/PROFIgate item and
click Add.
The Select Node Name dialog opens.
Endress+Hauser 89
2. Enter a symbolic node name for the PROFIBUS DP channel (default value: Node 0)
and click Next.
The Select Addresses for FG series / PROFIgate dialog opens.
3. Enter the IP address of the Fieldgate, select Bus Connector and click Next.
The Select Timeouts for FG series / PROFIgate dialog opens and the user can
make the standard timeout setting.
4. Enter the Timeout for Connect. These settings should be made by PROFIBUS
specialists only. Click Finish.
The standard timeout settings are accepted and the configuration is completed.
The PROFIBUS Control Panel dialog returns and the symbolic name of the
Fieldgate is assigned to the FG series/PROFIgate item.
90 Endress+Hauser
5. Click Apply.
The configuration is saved. The Fieldgate FXA720 device is ready if a green tick
appears next to the symbolic name. If a red tick appears, check whether the
PROFIBUS scan is switched off.
6. For single-channel Fieldgates, click OK.

The configuration is saved and the configuration window closes.


If the Fieldgate FXA720 is not already set up it can be set up now, see Chapter
22.2.1. 87
Endress+Hauser 91

The PROFIdtm DPV1 (Configuration) dialog appears.
7. Check that the PROFIBUS bus parameters are exactly the same as those used in any
Master Class 1 in the network. The default parameters are the ones recommended
for use with a particular baud rate. They can be adjusted by deactivating the
automatic defaults.
Select Board-Name from the drop-down menu.
8. Enter the PROFIBUS Address of the Fieldgate FXA720.
9. Select the Baud Rate that is used by the PROFIBUS network.
10. Enter the Start and End Address for the scan range and click OK.
The changes are saved and FieldCare returns to the Network dialog.
92 Endress+Hauser


14. Select Connect.

The connection to the device is established.

Endress+Hauser 93
PROFIBUS DP/PA via Fieldgate SFG500 Tutorial for FieldCare projects
23 PROFIBUS DP/PA via Fieldgate SFG500
23.1 Application
When operating with a single segment with a Pepperl+Fuchs coupler, the component
architecture is as shown in Fig. 37, for example.
Fieldgate SFG500 is connected to the Ethernet backbone via the LAN 1 Ethernet socket
and the PROFIBUS DP segment. The segment itself is connected to a PLC or DCS, which
acts as Class 1 master. PROFIBUS PA devices are connected to the network via the coupler.
To see all the devices on the PROFIBUS DP/PA segment, FieldCare requires:
SFGNetwork DTM
PROFIBUS DeviceDTMs
1 2
Power PB DP RS485
Run PB Err LAN 1
3
Failure LAN 2
Reset
AB001CF2897L
7 SFG500
LAN 1
LAN 2
4
37 Fieldgate SFG500 access to a PROFIBUS DP network

1 FieldCare
2 Ethernet
3 FieldgateSFG500
4 PROFIBUS DP
5 PROFIBUS PA
6 Transparent DP/PA coupler

94 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP/PA via Fieldgate SFG500

4. In the Add New Device dialog, select the SFGNetwork item and click OK.
The SFGNetwork is added to the network.
5. In the Network dialog, right-click the SFG500 Network item.


The Ethernet network is scanned and all the available Fieldgate SFG500s and the
connected devices are added.
If there is only one Fieldgate SFG500 in the network, the connection is

established and the SFG500 (Configuration) dialog is displayed.
Endress+Hauser 95
PROFIBUS DP/PA via Fieldgate SFG500 Tutorial for FieldCare projects
7. If no DTM has been found, it is possible that the UDP ports are blocked. These ports
can be unblocked as described in Appendix B 181. Alternatively, the
CommDTM can be added manually.
In the Network dialog, right-click the SFG500 Network item.
8. Select Add Device and click OK.

The CommDTM is added to the network.
9. If several Fieldgate SFG500s and connected devices are found, these are
automatically added to the network.
If any of the devices has a DTM whose quality is less than 1, the Scanning Result
dialog opens. Click OK before the devices are added to the network.
10. If only one device is found, the DTM is opened automatically.
If more than one device is found, the Connect After Scanning message appears.
Click OK to acknowledge this message.


12. Select Connect.

The connection to the device is established. This is indicated by a green arrow.
96 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP/PA via Fieldgate SFG500


The device can now be configured.

Endress+Hauser 97
PROFIBUS DP/PA via multiple Fieldgate SFG500 devices Tutorial for FieldCare projects
24 PROFIBUS DP/PA via multiple Fieldgate

SFG500 devices
24.1 Application
When operating with multiple segments and Pepperl+Fuchs couplers the component
architecture can be as shown in Fig. 38, for example.
For simplicity the devices connected to segments 2 5 are not shown. All Fieldgate
SFG500s are connected to the Ethernet backbone via the LAN 1 Ethernet socket and share
a common Ethernet IP address domain. One Fieldgate SFG500 is connected to each
PROFIBUS DP segment. The PROFIBUS DP segments do not necessarily have to be
connected to a single PLC. PROFIBUS PA devices are connected to the PROFIBUS DP
segments via couplers.
SFGNetwork DTM
PROFIBUS DeviceDTMs
1 2
8
3
Power PB DP RS485 Power PB DP RS485
Power PB DP RS485 Power PB DP RS485 Power PB DP RS485 PB Err
Run PB Err LAN 1 Run PB Err LAN 1 Run PB Err LAN 1 Run LAN 1
Run PB Err LAN 1 Failure LAN 2
Failure LAN 2 Failure LAN 2 Failure LAN 2 Failure LAN 2
Reset
Reset Reset Reset Reset
AB001CF2897L
AB001CF2897L
AB001CF2897L
AB001CF2897L
AB001CF2897L
7 SFG500 SFG500 SFG500

SFG500 SFG500
LAN 1
LAN 1
LAN 1
LAN 1
LAN 1
LAN 2
LAN 2
LAN 2
LAN 2
LAN 2
5
6 6
38 Fieldgate SFG500 access to multiple PROFIBUS DP networks

1 FieldCare
2 Ethernet
3 FieldgateSFG500
4 PROFIBUS DP with segment 1-5
5 DP/PA coupler
6 PROFIBUS PA
7 PLC/DCS
8 Control network

The dialogs for this procedure are identical to those in Chapter 16.2. 70
98 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP/PA via multiple Fieldgate SFG500 devices

5. In the Network dialog, right-click SFGNetwork.
6. Select Connect.
7. The connection to the device is established and is indicated by a green arrow.
8. In the Network dialog, right-click the SFG500Network item.
FieldCare scans the Ethernet network.
10. If more than one device is found, the Connect After Scanning message appears.
Click OK.

FieldCare adds the Fieldgate SFG500s found and the connected devices to the
network.
If no DTM has been found, it is possible that the UDP ports are blocked. These
ports can be unblocked as described in Appendix B. 181 Alternatively, the
CommDTM can be added manually.
11. If any of the devices has a DTM whose quality is less than 1, the Scanning Result
dialog opens.
Click OK before the devices are added to the network.
The Network dialog opens.
Endress+Hauser 99
PROFIBUS DP/PA via Fieldgate SFG500 and Siemens link Tutorial for FieldCare projects
25 PROFIBUS DP/PA via Fieldgate SFG500 and

Siemens link
25.1 Application
When operating with a Siemens DP/PA coupler or link, the component architecture can be
as shown in Fig. 39, for example.
The Fieldgate SFG500 is connected to the Ethernet backbone via the LAN 1 Ethernet
socket. PROFIBUS PA devices are connected to the network via the Siemens coupler/link.
The same architecture can be used for Fieldgate FXA720 in combination with Siemens
DP/PA link.
SFGNetwork DTM
PROFIBUS CommDTM
PROFIBUS DeviceDTMs
1 2
Power PB DP RS485
Run PB Err LAN 1

Failure LAN 2
Reset
AB001CF2897L
7 SFG500
3
LAN 1
LAN 2
39 Fieldgate SFG500 access to a PROFIBUS DP network via Siemens coupler/link

1 FieldCare
2 Ethernet
3 FieldgateSFG500
4 PROFIBUS DP
5 PROFIBUS PA
6 Siemens link/ DP/PA coupler
7 PLC/DCS
8 Control network

100 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP/PA via Fieldgate SFG500 and Siemens link

6. Select Connect.
7. The connection to the device is established and is indicated by a green arrow.
FieldCare scans the PROFIBUS network for the Siemens link.
If only one Fieldgate is found, its DTM is opened automatically.
ports can be unblocked as described in Appendix B . 181
Alternatively, the CommDTM can be added manually.
The Create Network - Scanning Result dialog opens.
10. Click OK.

The CommDTM of the DP/PA link is added to the network.
11. In the Network dialog, right-click the DP/PA Link item.

The segment to which the DP/PA link is connected is scanned for devices.
Endress+Hauser 101
PROFIBUS DP/PA via Fieldgate SFG500 and Siemens link Tutorial for FieldCare projects
13. Click OK.

If the Connect After Scanning option is selected under Extra the Connect After
Scanning dialog opens.
The devices are added to the network.
The DeviceDTMs can be opened.

102 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS-DP/PA and HART via Fieldgate SFG500 and Siemens ET200M/iSP
26 PROFIBUS-DP/PA and HART via Fieldgate

SFG500 and Siemens ET200M/iSP
26.1 Application
This chapter describes how FieldCare should be configured for a plant that uses a Siemens
ET200M/iSP-type Remote I/O. The PC with FieldCare installed is connected to an SFG500
via Ethernet. The SFG500 is connected via Profibus DP to an ET200M/iSP, which is
connected to the field devices via HART. A cyclic master is required for the operation of the
plant.
1 2 3 4 5 6
40 Fieldgate SFG500 access to Siemens ET200M/iSP

1 FieldCare
2 Ethernet/IP
3 FieldgateSFG500
4 PROFIBUS DP
5 Master
6 Siemens ET200 Remote I/O

6. Select Connect.
The connection to the device is established and is indicated by a green arrow.
Endress+Hauser 103
PROFIBUS-DP/PA and HART via Fieldgate SFG500 and Siemens ET200M/iSP Tutorial for FieldCare projects

When you scan at the SFGNetwork level, all the SFG500s on the Ethernet are
found. Then scan again on the SFG500 level to see the ET200M/iSP.
FieldCare scans the Ethernet network and displays the available devices.
9. In the Network dialog, right-click CommDTM.

The Communication Channel dialog opens.
11. In the dialog, select all the channels to be scanned.

The channels are scanned. The HART devices connected to the ET200M/iSP are
displayed and can be used.
104 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP/PA and HART via Fieldgate SFG500 and Turck Remote I/O
27 PROFIBUS DP/PA and HART via Fieldgate

SFG500 and Turck Remote I/O
27.1 Application
When operating with a Turck EXCOM Remote I/O the component architecture can be as
shown in Fig. 41, for example. The Fieldgate SFG500 is connected to the Ethernet
backbone via the LAN 1 Ethernet socket. PROFIBUS PA devices are connected to the
network via e.g. a transparent coupler. The HART devices (4 to 20 mA) are connected
point-to-point to the Turck Remote I/O which in turn is connected to the PROFIBUS-DP
segment.
The same architecture can be used for Fieldgate FXA720 and a Turck Remote I/O. The
connection procedure for the Turck Remote I/O is analogous to that in Chapter 23.2.
94
SFGNetwork DTM
Licensed Turck CommDTM EXCOM
PROFIBUS DeviceDTMs
HART DeviceDTMs
1 2 3 4 5
Power PB DP RS485
Run PB Err LAN 1
Failure LAN 2
Reset
AB001CF2897L
SFG500
LAN 1
LAN 2
10 9 8 7 6
41 Fieldgate SFG500 access to HART devices via Turck Remote I/O

1 Control network
2 PLC/DCS
3 FieldCare
4 Fieldgate SFG500 Access Point
5 Ethernet
6 PROFIBUS DP
7 Turck EXCOM Remote I/O
8 HART 4 to 20 mA
9 DP/PA coupler
10 PROFIBUS PA
Endress+Hauser 105
PROFIBUS DP/PA and HART via Fieldgate SFG500 and Turck Remote I/O Tutorial for FieldCare projects

6. Select Connect.
7. In the Network dialog, right-click to select the SFGNetwork item.

9. In the Network dialog, right-click SFG500.
10. Select Connect.
FieldCare scans the PROFIBUS network for the Turck Remote I/O.
The CommDTM of the excom is added to the network.
If the message "Connect After Scanning" appears, this can be selected or not. It is
advisable to disable this option.
106 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP/PA and HART via Fieldgate SFG500 and Turck Remote I/O
42 Scan FieldCare/excom if there is a connection after scanning.
43 Scan FieldCare/excom if there is no connection after scanning.
13. If the Connect After Scanning option is selected under Extra the Connect After
Click OK.

14. In the Network dialog, right-click the excom DP-N item.

15. Select Connect.
The devices found are added to the network.
Click OK.

19. In the Network dialog, right-click an excom module.

20. Select Connection.
21. In the Network dialog, right-click an excom module.
Endress+Hauser 107
PROFIBUS DP/PA and HART via Fieldgate SFG500 and Turck Remote I/O Tutorial for FieldCare projects
Other functions via HART devices

2. Select Other Functions HART Devices.
The excom DP-N (HART-LiveList) dialog appears.
Excom does not have a HART LiveList as an additional function.

Turck excom Remote I/O is successfully tested with:
FieldCare SFE500
FieldCare version 2.11.00
DTM for Fieldgate SFG500 version 1.09.00
DTM for excom Remote I/O system version 1.12.4
FieldgateSFG500
Fieldgate SFG500 with firmware 01.09.00-03131
Turck excom Remote I/O system
Turck GPD-IS with Firmware 2.2
108 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP/PA and HART via Fieldgate SFG500 and Stahl Remote I/O
28 PROFIBUS DP/PA and HART via Fieldgate

SFG500 and Stahl Remote I/O
28.1 Application
When operating with a Stahl CPM 9440 Remote I/O the component architecture can be as
shown in Fig. 44, for example. The Fieldgate SFG500 is connected to the Ethernet
backbone via the LAN 1 Ethernet socket. PROFIBUS PA devices are connected to the
network via e.g. a transparent coupler. The HART devices (4 to 20 mA) are connected
point-to-point to the Stahl Remote I/O which in turn is connected to the PROFIBUS DP
segment.
The same architecture can be used for Fieldgate FXA720 and a Stahl Remote I/O. The
connection procedure for the Stahl Remote I/O is analogous to that in Chapter 23.2.
94
SFGNetwork DTM
PROFIBUS CommDTM
PROFIBUS DeviceDTMs
HART DeviceDTMs
1 2 3 4 5
Power PB DP RS485
Run PB Err LAN 1
Failure LAN 2
Reset
AB001CF2897L
SFG500
LAN 1
LAN 2
10 9 8 7 6
44 Fieldgate SFG500 access to HART devices via Stahl Remote I/O

1 Control network
2 PLC/DCS
3 FieldCare
4 Fieldgate SFG500 Access Point
5 Ethernet
6 PROFIBUS DP
7 Stahl CPM 9440 Remote I/O
8 HART 4 to 20 mA
9 DP/PA coupler
10 PROFIBUS PA
Endress+Hauser 109
PROFIBUS DP/PA and HART via Fieldgate SFG500 and Stahl Remote I/O Tutorial for FieldCare projects

6. Select Connect.
7. In the Network dialog, right-click to select the SFG500 Network item.

10. Select Connect.
FieldCare scans the PROFIBUS network for the Stahl Remote I/O.
110 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP/PA and HART via Fieldgate SFG500 and Stahl Remote I/O
13. Click OK.

The CommDTM of the Stahl Remote I/O is added to the network.
14. If more than one device is found, the Connect After Scanning message appears.
Click OK.
15. In the Network dialog, right-click to select the Stahl Remote I/O item.
The segment to which the Stahl Remote I/O is connected is scanned for devices.
17. Click OK.

The CommDTM is added to the network.
Click OK.

19. In the Network dialog, right-click to select the CPM 9440 item.
20. Select Connect.
Endress+Hauser 111
PROFIBUS DP/PA and HART via Fieldgate SFG500 and Stahl Remote I/O Tutorial for FieldCare projects

23. Select Communication Channel.

The devices found are added to the network.
Click OK.

Other functions via HART devices

2. Select Other Functions HART Devices.
The CPM 9440 (HART-LiveList) dialog appears.
112 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP/PA via Softing PBproUSB modem
29 PROFIBUS DP/PA via Softing PBproUSB

modem
29.1 Application
The Softing PBproUSB modem allows a computer or laptop to connect to a PROFIBUS DP
segment via USB
The PROFIBUS PA devices can be accessed via a DP/PA coupler.
To see all the devices on the segment of the PROFIBUS DP/PA, FieldCare requires:
PROFIBUS DeviceDTMs
PROFIBUS driver PROFIboard
1 2 3 4 5
45 Connection of a PBproUSB modem with a PROFIBUS PA segment

1 FieldCare
2 USB
3 PBproUSB modem
4 DP/PA coupler
5 PROFIBUS PA

PBproUSB must be commissioned before it can be used. For this, the user calls the
PROFIBUS Control Panel Applet from the PROFIBUS DPV1 CommDTM.
Starting the PROFIBUS Control Panel

1. Start the PROFIBUS Control Panel Applet.
Endress+Hauser 113
PROFIBUS DP/PA via Softing PBproUSB modem Tutorial for FieldCare projects
2. In the Network dialog, right-click PROFIBUS DPV1 CommDTM.

3. Select Other Functions PROFIBUS Control Panel Applet.

The PROFIBUS Control Panel dialog opens.
For this to happen, the PROFIBUS DVP1 CommDTM must have been added to the
HOST PC beforehand.
PROFIBUS set-up
1. In the PROFIBUS Control Panel dialog, select the PBproUSB item and click Add.
The Select Node Name dialog opens.
2. Enter a symbolic node name for the PROFIBUS DP channel (default value: Node 0)
and click Next.
114 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP/PA via Softing PBproUSB modem
3. Do not change the default settings (auto) for the serial number of the device.
Click Finish.
The PROFIBUS Control Panel dialog returns and the symbolic name of the
PBproUSB modem is assigned to the PBproUSB item.
4. Click Apply.
The configuration is saved. The device is ready if a green tick appears next to the
symbolic name. If a red tick appears, check whether the PROFIBUS scan is
switched off.
5. For single-channel Fieldgates, click OK.

The configuration is saved and the configuration window closes.

Endress+Hauser 115
PROFIBUS DP/PA via Softing PBproUSB modem Tutorial for FieldCare projects

5. In the Network dialog, click PROFIdtm DPV1.

The configuration dialog of the DTM is displayed.
The Node Name (default: Node0) entered previously in the PROFIBUS Control
Panel must be selected in the Board Name field. The other parameters must be
checked and modified as they can vary depending on the plant.

116 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP via PROFIBUS modem and WAGO Remote I/O
30 PROFIBUS DP via PROFIBUS modem and

WAGO Remote I/O
30.1 Application
This chapter describes how FieldCare should be configured for a plant that uses a WAGO
Remote I/O. The PC with FieldCare installed is connected to a PROFIBUS modem via
Ethernet. A Softing PBproUSB, for example, can be used for this. The modem is connected
to the WAGO Remote I/O via PROFIBUS DP. The WAGO Remote I/O is connected to HART
field devices by HART via one or more WAGO modules. A cyclic master is essential for the
operation of the plant. A PROCENTEC ProfiCore, for example, can be used for this.
1 2 3 4 5 6
46 Access to PROFIBUS DP via PROFIBUS modem and WAGO Remote I/O

1 FieldCare
2 Ethernet/IP
3 PROCENTEC ProfiCore
4 Softing modem
5 PROFIBUS DP
6 WAGO Remote I/O
The plant described in this chapter uses a Softing profiUSB with commDTM PROFIdtm
DPV1 as the PROFIBUS modem and a PROCENTEC ProfiCore as the cyclic master.
Alternatively, other suitable PROFIBUS devices can also be used.

If a Softing modem is used, it must be configured beforehand (see Chapter 28
109). Otherwise another modem-specific configuration must be performed.
Endress+Hauser 117
PROFIBUS DP via PROFIBUS modem and WAGO Remote I/O Tutorial for FieldCare projects

4. In the Add New Device dialog, select the DTM modem and click OK. If a Softing
modem is used, PROFIdtm DP-V1 is the correct DTM.
The modem is added to the network.
5. In the Network dialog, right-click PROFIdtm DPV1.

The Configuration dialog appears.
7. Adjust the configuration parameters of the modem individually.
In the case of the Softing modem, these are the timing parameter and the baud rate in
particular. These parameters can vary depending on the plant. If these parameters are
not correct, the following settings cannot be made correctly since the device list is
empty, for instance.
1. Select the modem in the Network dialog.

The Remote I/O is found and appears in the structure.
3. Select Remote I/O and click Disconnect in the context menu.
118 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP via PROFIBUS modem and WAGO Remote I/O
4. Select Remote I/O and click Configuration in the context menu.

The WAGO Configuration dialog appears.
5. Select the Module Configuration tab in the Configuration dialog. The first slot (1) is
occupied by the WAGO head module and cannot be edited. Set all the modules on the
head module.
6. Select Remote I/O and click Connect in the context menu.
Remote I/O is online: this is indicated by a green background.
7. Select Devicelist and click Additional function in the context menu.
The Devicelist of the Remote I/O appears.
Recursive scanning cannot be performed with the Wago Remote I/O. Therefore, all
the devices connected to the Remote I/O and displayed in the device list must be
added manually.
1. Click Add Device in the context menu.

The Add New Device dialog appears.
2. Select Device.
The Assign Device to Channel dialog appears.
3. Assign the channel to the device.

The device appears in the network structure and can be used.
Endress+Hauser 119
PROFIBUS DP via PROCENTEC ProfiCore Tutorial for FieldCare projects
31 PROFIBUS DP via PROCENTEC ProfiCore
31.1 Application
This chapter describes how FieldCare should be configured for a plant that uses a
PROCENTEC ProfiCore. The PC with FieldCare installed is connected to a PROCENTEC
ProfiCore via Ethernet. The ProfiCore is connected via PROFIBUS DP to a PROFIBUS DP/PA
coupler which is connected to the field devices via PROFIBUS PA.
PCD setup
CommDTM PROCENTEC DP-V1 master
ProfiTrace
These can be downloaded from the PROCENTEC site at www.procentec.com
1 2 3 4 5
47 Access to PROFIBUS DP via PROCENTEC ProfiCore

1 FieldCare
2 USB
3 PROCENTEC ProfiCore
4 PROFIBUS DP
5 DP/PA coupler

120 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS DP via PROCENTEC ProfiCore

The Profitrace and PCD icons are displayed in the start bar on the bottom right.
4. Press the PCD icon on the home page.

The PCD Server dialog opens.
5. Click Add in the PCD Server dialog.

The Interface Settings dialog opens.
6. In the Interface Settings dialog, enter values for the fields Interface name (user-
definable) , Driver = Profitrace/, serial number of the Procentec Device and
confirm.
The interface is created and can be assigned.
7. In the Network dialog, right-click PROFIdtm.
Endress+Hauser 121
PROFIBUS DP via PROCENTEC ProfiCore Tutorial for FieldCare projects
The Configuration dialog appears.
9. Click on the Bus Parameter tab.

The bus parameters appear.
10. In the Bord Name field, select the Interface Name entered and click Start.
The bus parameters are read and saved.
11. In the Network dialog, right-click PROFIdtm.
The network is scanned and all the field devices connected to the PROCENTEC ProfiCore
are displayed and can be used.
122 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS via modem PBI-Plus/smar
32 PROFIBUS via modem PBI-Plus/smar
32.1 Application
This chapter describes how FieldCare should be configured for a smar PBI-Plus PROFIBUS
modem. The PC with FieldCare installed is connected to a smar PBI-Plus PROFIBUS modem
via USB. The PROFIBUS modem is connected directly to the field devices by PROFIBUS
technology via PROFIBUS PA.
Device library CD smar Device Library v1_23 PROFIBUS
Device driver Driver_USB.rar
48 Access to PROFIBUS via smar modem PBI-Plus

1 FieldCare
2 USB
3 PROFIBUS modem smar PBI-Plus
4 PROFIBUS PA
The software packages can be downloaded from the manufacturer's website

www.smar.com or obtained through smar's support at support.smar.com.
Installation of the smar device library
Start setup as an administrator, default installation.
Connect PBI-Plus modem with PC
A popup appears.
The popup does not appear if the modem is not connected to a PROFIBUS device.
Installing the USB driver (Windows 7)

Unpack to Driver_USB.rar \Driver_USB\Windows 7 (64 or 32 bit version)
In Windows Device Manager, set the USB driver of the USB port: \Driver_USB\Windows 7
(64 or 32 bit version)
Endress+Hauser 123
PROFIBUS via modem PBI-Plus/smar Tutorial for FieldCare projects

In the Device Manager specify the port via which the PBI-Plus is connected to the PC
via USB (here COM2).
The picklists do not expand in the edit mode. The selected value is entered using the
keyboard. 1-9 for port, L/N for interface. Furthermore, the device must be offline
for these settings.
9 is the maximum value for the port. If the port in the Device Manager is higher, the
modem must be connected manually beforehand with another port via the
advanced port settings, permitted value range is 1 - 9.

4. Select PBI and click OK.

PBI is added to the network.
124 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS via modem PBI-Plus/smar
5. In the Network dialog, right-click PBI-Plus.

6. Select Offline Parameterize.
The PBI (Offline Parameterize) dialog appears.
7. Set the Port and Interface and click Write.

8. In the Network dialog, right-click PBI-Plus.
10. Select the suitable device DTM.
The device can now be connected and used.
The version number and parameter (bus address) must match as otherwise it might
not be possible to establish a connection to the device.
Endress+Hauser 125
PROFIBUS via SFG500 with the Heartbeat VerificationDTM Tutorial for FieldCare projects
33 PROFIBUS via SFG500 with the Heartbeat

VerificationDTM
33.1 Application
The following example shows how the VerificationDTM is used in FieldCare. In the plant, a
PROFIBUS device is directly connected to the PC via a Fieldgate SFG500. It is possible to
transfer the Heartbeat data from the PC to the W@M portal via the VerificationDTM
upload function.
Other areas of application of the VerificationDTM include plants in which:
HART devices are connected to the Fieldgate SFG500 via a PROFIBUS HART gateway
HART devices are connected to the PC/FieldCare via a gateway (e.g. IFAK IsNET)
or Ethernet/IP PROFINET networks are connected to the PC/FieldCare via CDI TCP/IP
DTM
Networks that communicate via FOUNDATION Fieldbus are not supported by the
VerificationDTM. Additional information can be found in the documentation for the
VerificationDTM.
3
5
4
49 Access to PROFIBUS via SFG500 with the Heartbeat VerificationDTM

1 FieldCare
2 W@M Portal
3 FieldgateSFG500
4 PROFIBUS DP
5 PLC

System requirements: The VerificationDTM must be installed on the PC, the setup for
the VerificationDTM can be found in the FieldCare Download Area of the
Endress+Hauser website. https://portal.endress.com/webdownload/
FieldCareDownloadGui/
33.2.1 Scanning the network

126 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS via SFG500 with the Heartbeat VerificationDTM

The SFGNetwork is scanned, all the Fieldgate SFG500s connected in the
network, along with the individual devices, are found and shown in the network
view.
In the example below, a Fieldgate SFG500 with a Promag 100 heartbeat device is
found at address 25. A VerificationDTM is assigned to this device. An additional,
separate VerificationDTM must be assigned in each case for every additional
Heartbeat device in the network. A unique DTM address guarantees the assignment.
33.2.2 Adding/configuring the VerificationDTM

The steps below are repeated for all the heartbeat devices in an SFG500 network:

3. Select VerificationDTM.
VerificationDTM is added to the network.

5. Select Other Functions Disconnect.
SFG500 is disconnected.
It is only possible to select the Set DTM Address item if you are disconnected from
the SFG500.
Endress+Hauser 127

7. Select Other Functions Set DTM Address.

The configuration dialog of the SFG500 opens on the right.
This contains a list of all the devices and verification DTMs that are assigned to
the Fieldgate SFG500.
8. Select the DTM that has just been added. Enter the DTM address and press Enter to
confirm. Then click Update.
The DTM is updated in the network.
Once a VerificationDTM has been added and configured for every heartbeat
device, they can be used to read out the heartbeat data.
The DTM address and device address must match (here = 25 / Promag100) to be
able to assign the VerificationDTM to a device.
The option "show archive tree" must be selected in the top left in the DTM toolbar so
that all the functions of the DTM are displayed, particularly the Verification and
Archive File tabs.
128 Endress+Hauser
Tutorial for FieldCare projects PROFIBUS via SFG500 with the Heartbeat VerificationDTM
33.2.3 Reading out the heartbeat data

1. In the Network dialog, right-click VerificationDTM for the device.
2. Select Connect Device.
The device is connected.
3. Double-click VerificationDTM.
VerificationDTM opens.
After selecting one of the data records 9-16, the heartbeat data are read automatically and
cached in the selected data record. In this way, different versions of the device parameters
can be stored in the data records for later use or analysis.
33.2.4 Uploading the heartbeat data to W@M

The stored heartbeat data of a data record can be transferred to the W@M Portal.
1.
In the VerificationDTM, switch to the Layout Options tab.

A list of data records is displayed.
2. Select the data records that should be transferred to W@M.
3. In the VerificationDTM, switch to the Print Options tab and select Print to W@M.
4. Click the Print Button in the title bar.
Upload to W@M starts.
The devices can be assigned between FieldCare and W@M via the TAG and the serial
number. These must be provided in W@M.
Verifying the upload

1. In the Network dialog, right-click the device to be verified.
Endress+Hauser 129
2. Select Device in Web Show Device-specific Details.

W@M is loaded and the device data are displayed. The Attachment tab contains
a list of the reports most recently transferred with the heartbeat data of the
device.
130 Endress+Hauser
Tutorial for FieldCare projects FOUNDATION Fieldbus H1 via Field Controller SFC162
34 FOUNDATION Fieldbus H1 via Field Controller

SFC162
34.1 Application
When operating as a visitor, the Field Controller SFC162 provides a parallel path to
devices in an existing system and is used to commission devices, to change their settings or
to monitor their condition. This assumes that the system is operating, i.e. a project has
been downloaded to the Field Controller and devices.
The Field Controller SFC162 is normally used to configure the transducer blocks only.
For some devices, the Field Controller SFC162 can also be used to configure the input
and output blocks, but normally not the logic and control blocks.
A full description of the use of the Field Controller SFC162 in bypass mode can be found
in BA00069S/04/en.
To see all the devices on the FOUNDATION Fieldbus H1 segment, FieldCare requires:
FOUNDATION Fieldbus CommDTM
FOUNDATION Fieldbus DeviceDTMs
For devices without native DTMs, the iDTM for FOUNDATION Fieldbus
1 2 3
ON
FRC HLD RUN FAIL
ETH
RS-232
RS-232 TX
ETH LNK
ETH TX
FF H1 - 1
ControlCare SFC162
FF H1 - 2
FF H1 - 3
FF H1 - 4
STDBY
!
See Manual
5 4
50 Field Controller SFC162 access to a FOUNDATION Fieldbus H1 network

1 FieldCare
2 Field Controller SFC162
3 Ethernet
4 FOUNDATION Fieldbus H1
5 DCS
34.2 Commissioning the Field Controller SFC162
34.2.1 Setting up the IP address of the Field Controller SFC162

For this procedure, it is necessary to know the IP address of the Fieldgate within the
control network.
Do not restart the Field Controller SFC162 with the new address before Visitor
mode has been selected.
Endress+Hauser 131
FOUNDATION Fieldbus H1 via Field Controller SFC162 Tutorial for FieldCare projects
Setting up the IP address of the Field Controller SFC162

1. Set the IP address of the computer to the same domain as the Field Controller
SFC162's default address 192.168.164.100. See Appendix A or consult your system
administrator for information on this procedure. 181
2. If you have Application Designer installed on your computer, call HSE Network
Setup:
Select Programs Endress+Hauser ControlCare Tools HSE Network Setup.
Otherwise call up the Web server and enter the address 192.168.164.100 . Then
proceed with Step 5.
HSE Network Setup is launched and searches for devices in the Ethernet
network.
All devices in the network appear, irrespective of their IP domain. If this is not
the case:
Check that the proxy server of the Web browser is switched off.
Check that the Windows firewall is not blocking the program (switch off the
firewall).
Check all cables and switches.
If two or more Field Controllers with the same IP address are found, disconnect
all but one from the network.
3. If the computer has more than one NIC, it is necessary to select the card you want to
use for communication with the Field Controllers.
Tick Active NIC and click Save.
4. Note the IP address of the active card as this is used by FieldCare.
5. Double-click the Field Controller whose address is to be changed or enter
192.168.164.100 in the Web browser.
The Field Controller Web browser opens.
The Web server will only open if the host computer and the Field Controller have
IP addresses in the same IP domain.
If the Web server still does not open, check that the proxy server on the browser
has been disabled.
6. Expand the Setup node and click Network.
132 Endress+Hauser
7. Enter pcps as the user name and pcps as the password.

The Network Configuration dialog opens.
8. Enter the required IP address (e.g. 10.125.35.190).

9. Enter a netmask (e.g. 255.0.0.0. usually 255.255.255.0).
10. If required, enter a default gateway (usually xxx.xxx.xxx.1, selected domain) and
click Update.
11. Confirm the message stating that the Field Controller SFC162 must be restarted.
The IP address is set up.
34.2.2 Select Visitor mode

There can be up to four Field Controller SFC162s in any one network. However, each
controller must be assigned a different H1 address by running the option under Step
2 above.
Selecting the Visitor mode

1. Return to the home page and click Change.
The frameware home screen appears.
2. Select the Factory Init in Visitor Mode (H1 Address 0xFC) option and click Restart.
3. Enter pcps as the user name and pcps as the password to confirm the Field
Controller SFC162 restart.
The Field Controller SFC162 changes its mode from Controller (default setting)
to Visitor.
The Field Controller restarts as a visitor with the IP address entered as described
in Chapter 30.2.1 and the H1 address selected from the drop-down menu.
4. Set the address of the host computer to the same domain as that of the Field
Controller SFC162 Visitor (e.g. 10.125.35.200).
Endress+Hauser 133
34.2.3 Selecting the network card for FieldCare

If the host computer has more than one NIC, the one used for the Ethernet connection
to the controller and visitor must be specified, otherwise the applications running on
Ethernet select the first they find by default. For Application Designer, ticking and
storing the active NIC in HSE Network Setup causes the associated .ini files to be
updated.
For FieldCare these changes have to be made by hand.
Selecting the network card for FieldCare

1. Navigate to Program Files Common Files Codewrights HSEsvr2
endressoleserver.ini.
2. Open the endressoleserver.ini file with Notepad.
3. Search for the NIC Adapter entry.
4. Set a ; in front of the line DEFAULT_NIC = NIC.
5. Remove the ; from the line NIC = and add the NIC address (e.g. NIC =
10.125.35.200).

6. Save and close the endressoleserver.ini file.

The Visitor Function can now be used.


4. In the Add New Device dialog, select the SFC162 CommDTM item and click OK.
134 Endress+Hauser
5. In the Network dialog, right-click SFC162 CommDTM.

FieldCare scans the network for all the Ethernet devices and displays them in the
list of HSE devices.
7. To connect the Field Controller SFC162 Visitor, click the appropriate line (e.g.
10.125.35.190).
A tick appears next to the Field Controller SFC162 Visitor and the entry appears
green.

The Select Communication Channel dialog opens.
10. Select the channels to be scanned. Deselect all other channels and click OK.
Endress+Hauser 135

12. Select Connect.


34.4 Upload the project

After the devices have been configured, their settings must be uploaded to the Field
Controller SFC162 and engineering tool. Depending upon the tool and the task
(commissioning or replacement) this can be normally done for the entire fieldbus or for
individual devices.
The Field Controller manual contains instructions on how the device parameters should be
uploaded.
136 Endress+Hauser
Tutorial for FieldCare projects FOUNDATION Fieldbus H1 Bench mode via Field Controller SFC162
35 FOUNDATION Fieldbus H1 Bench mode via

Field Controller SFC162
35.1 Application
In Bench mode operation, two scenarios exist:
The devices are configured prior to being installed in the plant
The devices are already installed in the plant but the Field Controller SFC162 is not in
operation
In the first case, the devices will normally be configured on a point-to-point basis, i.e. one
device at a time, unless a powered network structure exists. In the second case, the
network exists, but it must be powered before the devices can be configured.
As far as the Field Controller SFC162 is concerned, Bench mode operation requires that it
operates as a controller, since there will normally be no other LAS (link active scheduler)
in the network. Fig. 51 shows the Bench mode architecture.
2
ON
3
RUN FAIL
ETH
FRC HLD
RS-232
RS-232 TX
ETH LNK
ETH TX
FF H1 - 1
ControlCare SFC162
FF H1 - 2
FF H1 - 3
FF H1 - 4
STDBY
!
See Manual
51 Bench mode architecture showing point-to-point connection

1 FieldCare
2 Ethernet
3 Field Controller SFC162
This chapter describes the point-to-point scenario. It shows how a device tag and device
address can be assigned to a device. For information about the configuration of the
devices, please refer to the appropriate manual.
The DeviceDTMs differ from device to device in the functions which can be configured:
All DTMs allow the configuration of the resource and transducer blocks.
Some DTMs allow the configuration of the device input/output blocks.
To date, no DTM allows the configuration of the tag and address. This can only be done
with the Field Controller SFC162 CommDTM.
The upload to the control system may also differ depending upon the manufacturer, type
and condition of the device. Endress+Hauser devices delivered fresh from the factory will
usually upload all the function blocks they support including logic and control blocks,
although the latter cannot be configured via DTMs.
Should a device have been subject to a download from a control system, then any block not
instantiated by the engineering tool will not be part of the upload. For a TMT162
temperature transmitter, for example, if only one analog input block has been instantiated
Endress+Hauser 137
FOUNDATION Fieldbus H1 Bench mode via Field Controller SFC162 Tutorial for FieldCare projects
for a project, only this block will be uploaded, although three blocks are offered in the
DTM. Configuring the two other blocks in FieldCare will not cause them to be uploaded.
35.2 Commissioning the Field Controller SFC162
35.2.1 Setting up the IP address of the Field Controller SFC162

For this procedure, it is necessary to know the IP address of the Fieldgate within the
control network.
Do not restart the Field Controller SFC162 with the new address before Visitor
mode has been selected.
Setting up the IP address of the Field Controller SFC162

1. Set the IP address of the computer to the same domain as the Field Controller
SFC162's default address 192.168.164.100. See Appendix A or consult your system
administrator for information on this procedure. 181
2. If you have Application Designer installed on your computer, call HSE Network
Setup:
Select Programs Endress+Hauser ControlCare Tools HSE Network Setup.
Otherwise call up the Web server and enter the address 192.168.164.100 . Then
proceed with Step 5.
HSE Network Setup is launched and searches for devices in the Ethernet
network.
All devices in the network appear, irrespective of their IP domain. If this is not
the case:
Check that the proxy server of the Web browser is switched off.
Check that the Windows firewall is not blocking the program (switch off the
firewall).
Check all cables and switches.
If two or more Field Controllers with the same IP address are found, disconnect
all but one from the network.
3. If the computer has more than one NIC, it is necessary to select the card you want to
use for communication with the Field Controllers.
Tick Active NIC and click Save.
4. Note the IP address of the active card as this is used by FieldCare.
138 Endress+Hauser
5. Double-click the Field Controller whose address is to be changed or enter

192.168.164.100 in the Web browser.
The Field Controller Web browser opens.
The Web server will only open if the host computer and the Field Controller have
IP addresses in the same IP domain.
If the Web server still does not open, check that the proxy server on the browser
has been disabled.
6. Expand the Setup node and click Network.
7. Enter pcps as the user name and pcps as the password.
The Network Configuration dialog opens.
8. Enter the required IP address (e.g. 10.125.35.190).

9. Enter a netmask (e.g. 255.0.0.0. usually 255.255.255.0).
10. If required, enter a default gateway (usually xxx.xxx.xxx.1, selected domain) and
click Update.
11. Confirm the message stating that the Field Controller SFC162 must be restarted.
The IP address is changed.
35.2.2 Select Visitor mode

There can be up to four Field Controller SFC162s in any one network. However, each
controller must be assigned a different H1 address by running the option under Step
2 above.
Endress+Hauser 139
Selecting the Visitor mode

1. Return to the home page and click Change.
The frameware home screen appears.
2. Select the Factory Init in Visitor Mode (H1 Address 0xFC) option and click Restart.
3. Enter pcps as the user name and pcps as the password to confirm the Field
Controller SFC162 restart.
The Field Controller SFC162 changes its mode from Controller (default setting)
to Visitor.
The Field Controller restarts as a visitor with the IP address entered as described
in Chapter 34.2.1 and the H1 address selected from the drop-down menu.
131
4. Set the address of the host computer to the same domain as that of the Field
Controller SFC162 Visitor (e.g. 10.125.35.200).
35.2.3 Selecting the network card for FieldCare

If the host computer has more than one NIC, the one used for the Ethernet connection
to the controller and visitor must be specified, otherwise the applications running on
Ethernet select the first they find by default. For Application Designer, ticking and
storing the active NIC in HSE Network Setup causes the associated .ini files to be
updated.
For FieldCare these changes have to be made by hand.
Selecting the network card for FieldCare

1. Navigate to Program Files Common Files Codewrights HSEsvr2
endressoleserver.ini.
2. Open the endressoleserver.ini file with Notepad.
3. Search for the NIC Adapter entry.
4. Set a ; in front of the line DEFAULT_NIC = NIC.
5. Remove the ; from the line NIC = and add the NIC address (e.g. NIC =
10.125.35.200).

6. Save and close the endressoleserver.ini file.

The Visitor Function can now be used.
140 Endress+Hauser
35.3.1 Connection with the Field Controller SFC162 CommDTM


4. In the Add New Device dialog, select the SFC162 CommDTM item and click OK.
FieldCare scans the network for all the Ethernet devices and displays them in the
list of HSE devices.
7. To connect the Field Controller SFC162 Visitor, click the appropriate line (e.g.
10.125.35.190).
A tick appears next to the Field Controller SFC162 Visitor and the entry appears
green.
Endress+Hauser 141
35.3.2 Assigning the device tag and/or H1 address

Assigning the device tag or address
2. Select Connect.
4. Select Other Functions Set Device Tag/Address.

The list of H1 devices is displayed.
5. Click the device (e.g. TMT162).
The input boxes at the bottom edge of the page are activated.
6. Enter the device tag.
The tag is changed in the list and the entry is set to red.
7. Enter the device address.
The address is changed in the list and the entry is set to red.
8. Click Apply.
Changes are saved and downloaded to the device.
142 Endress+Hauser
The icon at the start of the line appears in full color if the changes have been accepted.
If there are more devices in the network, the tags and addresses of all participants
can be changed before Apply is pressed.
When all devices return to the network, the H1 list can be closed.
35.3.3 Creating a FOUNDATION Fieldbus network

Creating a FOUNDATION Fieldbus network

3. Select the channels to be scanned. Deselect all other channels and click OK.
35.3.4 Opening the DeviceDTM

Opening the DeviceDTM
2. Select Connect.
Endress+Hauser 143


35.4 Upload the project

After the devices have been configured, their settings must be uploaded to the Field
Controller SFC162 and engineering tool. Depending upon the tool and the task
(commissioning or replacement) this can be normally done for the entire fieldbus or for
individual devices.
The Field Controller manual contains instructions on how the device parameters should be
uploaded.
144 Endress+Hauser
Tutorial for FieldCare projects FOUNDATION Fieldbus H1 via the National Instruments FBUS card
36 FOUNDATION Fieldbus H1 via the National

Instruments FBUS card
36.1 Use cases

The National Instruments PCPC-FBUS card allows a computer or laptop with a PC interface
to connect to a FOUNDATION Fieldbus H1 segment.
The National Instruments software delivered with the card must be installed on the
computer, configured and ready for use.
If the PC-FBUS card is connected to an active FOUNDATION Fieldbus H1 segment, it
is important to read the manufacturer's instructions with regard to uploading
modified device settings to the controller.
36.1.1 Connection to a FOUNDATION Fieldbus H1 segment

To connect the PC-FBUS card to a FOUNDATION Fieldbus H1 segment, the positive and
negative signal cables from the NI adapter piece must be connected to the bus line, e.g. via
a bus distributor.
1 2 3 4 5 6
52 Connection of an NI-PC-FBUS card to a FOUNDATION Fieldbus H1 segment

1 DCS
2 Adapter
3 Adapter cable
4 NI-PC-FBUS card
5 FieldCare
36.1.2 Point-to-point connection in Bench mode

In Bench mode, the devices are connected to the NI-PC-NBS card one by one in order to
configure the device address and device parameters. This requires a bus distributor with a
fieldbus power supply.
Endress+Hauser 145
FOUNDATION Fieldbus H1 via the National Instruments FBUS card Tutorial for FieldCare projects
1 2 3 4 5 6
53 Use of the NI-PC-NBS card in Bench mode

2 Power conditioner/bus distributor
3 Adapter
4 Adapter cable
5 NI-PC-NBS card
6 FieldCare

1. Click Start Programs National Instruments NI-FBUS NI-FBUS
Communications Manager.
The NI card opens.

5. In the Add New Device dialog, select the FF H1 CommDTM item and click OK.
The FF H1 CommDTM is added to the network.
6. In the Network dialog, right-click FF H1 CommDTM.
146 Endress+Hauser
Tutorial for FieldCare projects FOUNDATION Fieldbus H1 via the National Instruments FBUS card
The FF H1 CommDTM dialog opens and FieldCare asks for the link to the
FOUNDATION Fieldbus network.
8. Select the NI Card Link from the drop-down menu and click OK.
9. In the Network dialog, right-click FF H1 CommDTM.

FieldCare now scans the network.
The DeviceDTM is added to the network and opened.

If no new DTM is available, the user can still integrate the device by using the
FOUNDATION Fieldbus iDTM.
1. The DTMs are opened as follows if the NI FBUS card is connected to a FOUNDATION
Fieldbus H1 segment and several devices have been found:
In the Network dialog, right-click Device Node.
2. Select Connect.
3. In the Network dialog, right-click Device Node.
More information about the configuration is available in the Operating Instructions.
Endress+Hauser 147
FOUNDATION Fieldbus H1 via Softing FFusb modem Tutorial for FieldCare projects
37 FOUNDATION Fieldbus H1 via Softing FFusb

modem
37.1 Use cases

The Softing FFusb modem allows a computer or laptop to connect to a
FOUNDATION Fieldbus H1 segment via USB.
Install the Softing FFusb software on the computer before the USB connection is
made (the software can also be downloaded from the Softing site).
The FFusb CommDTM must be licensed, otherwise it only runs for 15 minutes in
demonstration mode.
The FieldCare DTM catalog must be updated.
If the FFusb modem is connected to an active FOUNDATION Fieldbus H1 segment,
it is important to read the manufacturer's instructions with regard to uploading
modified device settings to the controller.
FFusb CommDTM
37.1.1 Connection to a FOUNDATION Fieldbus H1 segment

To connect the FFusb modem to a FOUNDATION Fieldbus H1 segment, the positive and
negative signal cables must be connected to the bus line, e.g. via a bus distributor.
1 2 3 4 5
54 Connection of an FFusb modem to a FOUNDATION Fieldbus H1 segment

1 DCS
2 FFusb modem
3 USB
4 FieldCare
37.1.2 Point-to-point connection in Bench mode

In Bench mode, the devices are connected to the FFusb modem one by one in order to
configure the device address and device parameters. This requires a bus distributor with a
fieldbus power supply.
148 Endress+Hauser
Tutorial for FieldCare projects FOUNDATION Fieldbus H1 via Softing FFusb modem
1 2 3 4 5
55 Use of the FFusb modem in Bench mode

2 Power conditioner/bus distributor
3 FFusb modem
4 USB
5 FieldCare

1. The FFusb software must already be installed.
Plug the FFusb modem into the USB port of the computer or laptop.
The modem is installed automatically and made ready for use.

5. Select FF USB and click OK.

The FF USB CommDTM is added to the network.
6. In the Network dialog, right-click FF USB.
Endress+Hauser 149
FOUNDATION Fieldbus H1 via Softing FFusb modem Tutorial for FieldCare projects
The standard parameters for a FOUNDATION Fieldbus Visitor are displayed.
8. Change the scan range to suit the addresses on the segment.

9. Other parameters should be changed by a fieldbus expert only.
Click OK.
The changes are accepted and the Network dialog opens.
10. In the Network dialog, right-click FF USB.

The DeviceDTM is added to the network and opened.

If no new DTM is available, the user can still integrate the device by using the
FOUNDATION Fieldbus iDTM.
1. The DTMs are opened as follows if the NI FBUS card is connected to a FOUNDATION
Fieldbus H1 segment and several devices have been found:
In the Network dialog, right-click Device Node.
150 Endress+Hauser
Tutorial for FieldCare projects FOUNDATION Fieldbus H1 via Softing FFusb modem
2. Select Connect.
3. In the Network dialog, right-click Device Node.
More information about the configuration is available in the Operating Instructions.
Endress+Hauser 151
I/O Link networks Tutorial for FieldCare projects
38 I/O Link networks

I/O Link networks typically consist of an IE network that is connected via the I/O Link
Master to a system of additional I/O Link Masters and I/O Link devices (sensors/
actuators). Every I/O Link device is connected to a port of an I/O Link Master. A PC with
FieldCare that allows the configuration of all the connected I/O Link devices can be
integrated in the IE network.
4
5
6
56 FieldCare access to I/O Link devices via an I/O Link Master

1 FieldCare
2 Ethernet
3 I/O Link Master
4 FOUNDATION Fieldbus
5 I/O Link Master
6 I/O Link Master
Support for I/O Link networks is guaranteed in FieldCare but is currently still being
optimized. For example, it is currently not possible to automatically scan complete I/O
Link topologies. Alternatively the topology must be configured manually. Therefore
this chapter describes how to create the topology manually based on a simple use case
with Turck I/O Link devices:
2
3
1 FieldCare
2 Ethernet
3 Power unit 24 V
4 Turck multiprotocol I/O module TBEN-52
Power supply
Connect 4-wire cable supplied to x1 (bus), x2 remains free! White cable (+24V), black
cable (Gnd)
152 Endress+Hauser
Tutorial for FieldCare projects I/O Link networks
38.1 Application
The example below describes the test setup using a Turck I/O Link Master TBEN-S2 4IOL
and a Turck IO-Link device TS400.
The following components must be installed beforehand:
DTMs:
Gateway DTM for IO-Link device TBEN-S2
BL device Ethernet CommDTM
Download from manufacturer www.turck.com (io_assistant_1_0_2205/
BL20_BL67_V1.00.2205_Setup.exe)
IODD Interpreter DTM
Tool used to integrate device-specific IODD description files into a generic device DTM.
Download from various sites, including www.ifm.com, www.mm-software.com
Device IODD
IODD of the specific IO-Link device, here the Turck TS400
Download from manufacturer www.turck.com
The necessary IODDs of the connected devices must be read once with the IODDInterpreter
(here TS-400-LI2UPN8X)
End FieldCare before the operation. Then start it and run a catalog update.


Endress+Hauser 153
I/O Link networks Tutorial for FieldCare projects
4. In the Add New Device dialog, select the BL Service Ethernet item and click OK.
BL Service Ethernet is added to the network.
5. Select BL Service Ethernet .

The BL Service Ethernet DTM dialog opens and displayed beside the network
view and the parameters can be configured offline.
6. The IP address of the host PC must be configured in the IP Address/URL field.

7. In the Network dialog, right-click BL Service Ethernet.
8. Select the TBEN-S2-4IOL item.
The Device Data dialog opens.
9. Enter the IP address of the I/O Link Master. The IP address can be changed after a
loading time of 30 seconds. The hourglass does not disappear.
The I/O Link Master is added to the network.
10. Add all the I/O Link Ports used.
Both Modulbus 1 (Port 1) and Modulbus 2 (Port 2) can be found in the network
view.
Repeat the procedure below for every occupied port.
11. In the Network dialog, right-click I/O Link Master.

154 Endress+Hauser
Tutorial for FieldCare projects I/O Link networks
12. Select the TBEN-S2-4IOL item. (Must be identical to the I/O Link Master type.)
TBEN-S2-4IOL is added to the network.
13. Select Port Number.

The Add Device/Internal DTM Type dialog opens.
14. Add the device to the channels that are linked to the device and assign the I/O Link
devices to a port.
In the Network dialog, right-click the Module2 02/Internal S2-4IOL item.
16. Assign the device to the port.

The IO-Link device is added to the network view and can be used after establishing a
connection.
Endress+Hauser 155
ISS interface via FXA193 modem Tutorial for FieldCare projects
39 ISS interface via FXA193 modem
39.1 Application
The FXA193 modem provides a direct connection to Proline flowmeters.
The connection socket for communication can either be found inside the electronic
housing or the connection housing. Please consult the appropriate Operating Instructions
for further details. Fig. 57 shows the necessary connections.
1 2 3 4 5 6
TX G
RX 5V
57 ISS interface connection using FXA193 modem

1 FieldCare
2 RS232
3 FXA193 modem
4 Cable and adapter
5 Proline flowmeter electronic compartment or connection compartment
6 Power supply
The FXA193 modem must be used with the so-called Proline cable, which comprises two
components: a cable and an adapter.
The FXA193 modem is a serial modem with a Sub-D9 connector. It is recommended that
only a native serial port be used. The use of USB/Serial converters is not recommended. If
the desktop computer has no RS232 serial port, it is recommended that either a PCI or a
PCIe card be used. For laptop computers either a PC or Express Card can be used.
To connect to flow devices via the protocol (ISS), FieldCare requires:
ISS CommDTM
ISS DeviceDTM library

156 Endress+Hauser
Tutorial for FieldCare projects ISS interface via FXA193 modem

4. Select Flow Communication FXA193/291 and click OK.

The Flow Communication FXA193/291 is added to the network.
5. In the Network dialog, right-click Flow CommDTM.
The Flow Communication FXA193/291 (Configuration) dialog appears.
7. Set the COM port to which the FXA193 modem is to be connected and then press
Enter.
8. Click X in the top right.
The Flow Communication FXA193/291 (Configuration) dialog closes and the
Network dialog appears.
Endress+Hauser 157
ISS interface via FXA193 modem Tutorial for FieldCare projects
9. In the Network dialog, right-click Flow CommDTM.


the network.
11. Configure the device according to its operating manual.

158 Endress+Hauser
Tutorial for FieldCare projects ISS interface via FXA291 modem
40 ISS interface via FXA291 modem
40.1 Application
Some older flowmeters do not use the service connector shown in Fig. 57.
In this case the FXA291 modem must be used to connect to FieldCare. The connection
socket for communication can either be found inside the electronic housing or the
connection housing. Please consult the appropriate Operating Instructions for further
details. Fig. 58 shows the necessary connections.
1 2 3 4 5 6
3 4
1 2
58 ISS interface connection using FXA291 modem

1 FieldCare
2 USB
3 FXA291 modem
4 Cable and adapter
6 Power supply
To connect to flow devices via the protocol (ISS), FieldCare requires:

CommDTM
DeviceDTM library
40.2 Installing the FXA291 modem driver

Normally the computer automatically recognizes the FXA291 modem. If this is not the
case, the driver must be installed, see Appendix C. 182
Installing the modem driver

1. Check the COM port.
3. Open Ports (COM and LPT) .
The COM port that is assigned to the modem is displayed.

FieldCare establishes a connection to the FXA291 modem as described in Chapter
41.2. 160
Endress+Hauser 159
IPC interface for level/pressure via FXA193 modem Tutorial for FieldCare projects
41 IPC interface for level/pressure via FXA193

modem
The IPC interface does not apply for all level devices. Information on this can be found
in the Operating Instructions for the device in question.
41.1 Application
For communication with level and pressure devices via the IPC protocol, connectivity is
provided with the FXA193 modem in combination with the so called ToF cable.
The connection socket for communication is the same as the one used to connect the
device display. Please consult the appropriate Operating Instructions for further details.
Fig. 59 shows the necessary connections.
1 2 3 4 5 6
59 IPC interface connection using FXA193 modem

1 FieldCare
2 RS232
3 FXA193 modem
4 Cable and adapter
5 Level or pressure device display connection compartment
6 Power supply
The FXA193 modem is a serial modem with a Sub-D9 connector. For this application it can
be connected to either a native serial port or a USB/serial converter. To connect to devices
via the IPC protocol, FieldCare requires:
IPC CommDTM
IPC DTM library

160 Endress+Hauser
Tutorial for FieldCare projects IPC interface for level/pressure via FXA193 modem

4. Select IPC FXA193/291 and click OK.

The IPC CommDTM is added to the network.
5. In the Network dialog, right-click IPC DTM.
The IPC FXA193/291 (Configuration) dialog appears.
7. Set the COM port to which the FXA193 modem is to be connected.

8. Press Enter and then click the X in the top right.
The IPC FXA193/291 (Configuration) dialog closes and the Network dialog
appears.
Endress+Hauser 161
IPC interface for level/pressure via FXA193 modem Tutorial for FieldCare projects
9. In the Network dialog, right-click IPC CommDTM.


the network.

162 Endress+Hauser
Tutorial for FieldCare projects IPC interface for level/pressure via FXA291 modem
42 IPC interface for level/pressure via FXA291

modem
The IPC interface does not apply for all level devices. Information on this can be found
in the Operating Instructions for the device in question.
42.1 Application
For communication with level and pressure devices via the IPC protocol, connectivity can
be provided with the FXA291 modem in combination with the so called ToF cable.
The connection socket for communication is the same as the one used to connect the
device display. Please consult the appropriate Operating Instructions for further details.
Fig. 60 shows the necessary connections.
1 2 3 4 5 6
60 IPC interface connection using FXA291 modem

1 FieldCare
2 USB
3 FXA291 modem
4 Cable and adapter
5 Level or pressure device display connection compartment
6 Power supply
To connect to devices via the IPC protocol, FieldCare requires:

IPC CommDTM
IPC DTM library

case, the driver must be installed, see Appendix D. 182


FieldCare establishes a connection to the FXA291 modem as described in Chapter
41.2. 160
Endress+Hauser 163
CDI interface via FXA291 modem Tutorial for FieldCare projects
43 CDI interface via FXA291 modem
43.1 Application
All new and projected Endress+Hauser field devices use CDI communication as standard
for the protocol. The FXA291 modem provides connectivity to all Endress+Hauser devices
using the so called CDI plug. Fig. 61 shows the necessary connections.
1 2 3 4 5 6
3 4
1 2
61 CDI interface connection using FXA291 modem

1 FieldCare
2 USB
3 FXA291 modem
4 Cable and adapter
6 Power supply
To connect to devices via the CDI protocol, FieldCare requires:

CDI CommDTM
CDI DTM library



164 Endress+Hauser
Tutorial for FieldCare projects CDI interface via FXA291 modem


4. Select CDI Communication FXA291 and click OK.

The CDI Communication FXA291 is added to the network.
5. In the Network dialog, right-click CDI Communication FXA291.
The CDI Communication FXA291 (Configuration) dialog appears.
Enter.
Endress+Hauser 165
CDI interface via FXA291 modem Tutorial for FieldCare projects
8. Do not change the baud rate unless this is explicitly required in the device operating
manual.
The CDI Communication FXA291 (Configuration) dialog closes and the
10. In the Network dialog, right-click CDI Communication FXA291 (Configuration).

the network.

If no CDI Communication FXA291 DTM is installed, FieldCare states that proper
communication can only be ensured after the DTM has been installed.
166 Endress+Hauser
Tutorial for FieldCare projects CDI interface via TXU10 modem
44 CDI interface via TXU10 modem
44.1 Application
The TXU10 modem is a USB/CDI modem that may be used with FieldCare for configuring
the following devices:
RIA45/46, RMA42, RIA14/16, all new and projected devices
Together with M12 adapter: TMR3x
Devices without digital communication such as TMT180/181/121, TTR3x, PTP3x, PTC31,
DTT3x, RIA452, RIA141, TMT111 and TMR31x (with M12 adapter) cannot be configured
by FieldCare but require the Readwin2000 software, which can be optionally purchased
with the modem. See the Readwin2000 BA137R/09/en manual for more information.
The FXA291 modem provides connectivity to all Endress+Hauser devices using the so
called CDI plug. Fig. 62 shows the necessary connections.
1 2 3 4 5 6
3 4
1 2
62 CDI interface connection using TXU10 modem

1 FieldCare
2 USB
3 TXU10 modem
4 Cable
5 Indicators, process transmitter or TMT3x (with M12 adapter)
6 Power supply
To connect to devices via the CDI interface, FieldCare requires:

CDI CommDTM
CDI DTM library
44.2 Installing the TXU10 modem driver


Only the hardware TXU Version 1.01.00 is indicated in the device manager as TXU10.
Endress+Hauser 167
CDI interface via TXU10 modem Tutorial for FieldCare projects


4. Select CDI Communication FXA291 and click OK.

The CDI Communication FXA291 is added to the network.
168 Endress+Hauser
Tutorial for FieldCare projects CDI interface via TXU10 modem
The CDI Communication FXA291 (Configuration) dialog appears.
Enter.
8. Do not change the baud rate unless this is explicitly required in the device operating
manual.
The CDI Communication FXA291 (Configuration) dialog closes and the

the network.

Endress+Hauser 169
CDI interface via direct USB connection Tutorial for FieldCare projects
45 CDI interface via direct USB connection
45.1 Application
A number of CDI capable field devices can be connected directly to a computer via an
standard USB (A-B) cable. Currently these are:
EngyCal
RA33
1 2 3 4 5
63 CDI interface connection via direct USB connection

1 FieldCare
2 USB
3 Cable
4 EngyCal, RA33
5 Power supply

CDI CommDTM
CDI DTM library

170 Endress+Hauser
Tutorial for FieldCare projects CDI interface via direct USB connection

4. Select CDI Communication USB and click OK.

The CDI Communication USB is added to the network.
5. Connect the CDI-USB to the computer or laptop.
When the USB device is connected for the first time, a driver (CDIUSB) is
installed.
This installation does not require administration rights.
6. In the Network dialog, right-click CDI Communication USB.

the network.

Endress+Hauser 171
CDI interface via Ethernet TCP/IP Tutorial for FieldCare projects
46 CDI interface via Ethernet TCP/IP
46.1 Application
A number of CDI capable field devices can be connected directly to a computer via a
standard Ethernet cross-cable with RJ45 connector. Examples include:
Promass 100
Promag 100
Promag 400
Fig. 64 shows the necessary connections. If the connection is made via a switch a straight-
through cable can be used. For the location of the Ethernet interface, please see the
Operating Instructions of the device concerned.
1 2 3 4 5
64 CDI interface via direct Ethernet connection

1 FieldCare
2 Ethernet
3 Category 5 cross-cable
4 Device e.g. Promass 100, Promag 400
5 Power supply

CDI CommDTM
CDI DTM library
46.2 Setting up the computer

When using the Ethernet TCP/IP connection it is important to note that the computer and
device must have IP addresses within the same domain.
Computer setup
Change the computer's IP address to the same IP address range and subnet mask as
the default address of the device. The procedure for Windows 7 is described in
Appendix A.
The computer is set up.
If the IP address of the device is changed during the configuration, FieldCare will lose
contact with the device. In this case, it is necessary to change the computer's address
to an address in the new domain and then restart the application.

172 Endress+Hauser
Tutorial for FieldCare projects CDI interface via Ethernet TCP/IP


4. Select CDI Communication TCP/IP and click OK.

The CDI Communication TCP/IP is added to the network.
5. In the Network dialog, right-click CDI Communication TCP/IP.

Endress+Hauser 173
CDI interface via Ethernet TCP/IP Tutorial for FieldCare projects
7. Select DeviceDTM and click OK.

The DeviceDTM is added to the network and the CDI Communication TCP/IP
(Configuration) dialog opens.
8. In the CDI Communication TCP/IP (Configuration) dialog, specify the IP address of

the device to which the computer is connected and then press Enter.
9. Change the port and then press Enter.
The changes are accepted.
10. Click X.
The CDI Communication TCP/IP (Configuration) dialog closes and the
11. Connect the device to the computer via the Ethernet cable.
12. In the Network dialog, right-click CDI Communication TCP/IP.
13. Select Connect.

14. In the Network dialog, right-click a device node.
15. Select Connect.

The DeviceDTM opens in online mode.
174 Endress+Hauser
Tutorial for FieldCare projects CDI interface via Ethernet TCP/IP

Check the following if the device does not connect to FieldCare:
Do the computer and device have IP addresses in the same range
Is the Ethernet cable suitable for the connection used
Is the right DTM being used
Endress+Hauser 175
PCP interfaces via the FXA291/TXU10 modem Tutorial for FieldCare projects
47 PCP interfaces via the FXA291/TXU10 modem
47.1 Application
The TXU10 or FXA291 modem may also be used with FieldCare for configuring the
following devices:
Thermophant
Ceraphant
Flowphant
RIA1x
1 2 3 4 5 6
3 4
1 2
65 PCP interface connection using a TXU10 modem

1 FieldCare
2 USB
3 TXU10 modem
4 Cable
5 Device
6 Power supply
1 2 3 4 5 6
3 4
1 2
66 PCP interface connection using an FXA291 modem

1 FieldCare
2 USB
3 FXA291 modem
4 Cable and adapter
5 Device
6 Power supply
To connect to devices via the PCP protocol, FieldCare requires:

PCP CommDTM
PCP DTM library
47.2 Installing the FXA291 or TXU10 modem driver

Normally the computer automatically recognizes the FXA291 or TXU10 modem. If this is
not the case, the driver must be installed, see Appendix C. 182
176 Endress+Hauser
Tutorial for FieldCare projects PCP interfaces via the FXA291/TXU10 modem



4. Select PCP TXU10/FXA291 and click OK.

The PCP TXU10/FXA291 is added to the network.
Endress+Hauser 177
PCP interfaces via the FXA291/TXU10 modem Tutorial for FieldCare projects
5. In the Network dialog, right-click PCP TXU10/FXA291.

The PCP TXU10/FXA291 dialog appears.
7. Set the COM port to which the TXU10/FXA291 modem is to be connected and then
press Enter.
8. Set the number of retries to 3, for example, and then press Enter.
9. Change the device address.
10. Change the baud rate if this is explicitly required in the device operating manual.
The PCP TXU10/FXA291 dialog closes and the Network dialog appears.
12. In the Network dialog, right-click PCP TXU10/FXA291.

the network.
If no PCP TXU10/FXA291 DTM is installed, FieldCare states that proper
178 Endress+Hauser
Tutorial for FieldCare projects Interface to W@M
48 Interface to W@M
FieldCare provides several functions for the data synchronization of FieldCare with W@M
Enterprise:
Upload offline parameter configuration to W@M
Upload online parameter configuration to W@M
Compare online and offline parameter configurations
Compare offline and historic parameter configuration
Compare online and historic parameter configuration
Compare historic parameter configurations
To be able to use W@M, FieldCare and W@M must be configured as described below.
In FieldCare Administrator, record the W@M URL, see Section 48.1
In FieldCare Administration, record the W@M User, see Section 48.2
In FieldCare, make the W@M settings, see Section 48.3
System requirements: FieldCare / FieldCare Administrator and W@M must be
installed.
W@M is typically installed on a server, while FieldCare / FieldCare Administrator is
installed on a PC.
48.1 Recording the W@M URL

1. Start FieldCare Administrator.
2. The W@M Connection dialog opens.
3. Enter the W@M Enterprise URL. Format=http:/<W@M Server IP or
DNS>:<Port>/WAI/services
48.2 Recording the W@M User

1. Start FieldCare Administrator.
2. Open the User dialog.
3. Enter the User Name and Password of the W@M Administrator account.
48.3 W@M settings

1. Start FieldCare.
2. Select Extra Options in the main menu.
The Options dialog opens.
3. Select the W@M tab.
4. W@M.
Endress+Hauser 179
Interface to W@M Tutorial for FieldCare projects
5. Select the Tag or Serial number identification method, depending on whether the
tag or serial number should be used to identify the device when exchanging data
between FieldCare and W@M. This is specified by the setting in the contract in
W@M.
48.4 W@M functions

A connection test with W@M can be performed in the context menu for a device via
Device in Web Show Device-specific Details.
In the context menu, all the functions available for the W@M functions can be called up in
the Documentation menu item.
180 Endress+Hauser
Tutorial for FieldCare projects Appendix
49 Appendix
49.1 Appendix A - Setting a computer IP address

Administration rights are required to perform this task.
The description applies for Windows 7
All Endress+Hauser devices with an Ethernet interface are supplied with a default IP
address. For example the IP address for Fieldgate FXA720 is 192.168.253.1.
For the host computer to be able to communicate with the Fieldgate FXA720 Web server,
it must be allocated an IP address in the same address domain, e.g. 192.168.253.99. For
more information, please contact your network administrator.
Setting the computer IP address

1. Click Start Control Panel Network and Internet Network and Sharing
Center.
Network Connections opens.
2. Click Manage Network Connections.
3. Right-click the connections that are to be changed.
4. If required:
Enter the Administrator password or confirmation.
5. Right-click the Network tab.
6. Under This connection uses the following items click Internet Protocol Version 4
(TCP/IPv4).
7. Click Properties.
8. Note the original values of the IP address and subnet mask of the computer to restore
them if necessary at end of the operation. A computer used in a company network
will normally obtain its address automatically.
Click Use the following IP addresses.
9. Enter the IP address, subnet mask and default gateway for TCP/IPv4.
The settings for the IP address are accepted.
10. Click OK and the dialog can be closed.
The procedure is completed.
49.2 Appendix B - Windows firewall

If firewalls are in use on the computers on which the servers and clients reside, they must
be programmed to allow mutual access. As firewall configuration is often a matter of
company IT security policy, your system administrator should be consulted before
proceeding. In addition, administration rights are required to perform this task.
The ports available for Fieldgate SFG500 are listed in the table below:
Port number ID
TCP 60010 TCP_PCPS2_SFG500_PORT
UDP 60015 UDP_IDENTIFY_PORT
UDP 60020 UDP_ANNUNC_PORT
Managing the Windows firewall

1. Press Start Control Panel Windows Firewall.
Endress+Hauser 181
Appendix Tutorial for FieldCare projects
2. In the left pane, click Allow a program or feature through Windows Firewall.
3. If required:
4. Tick the check box beside the program that should be allowed through the firewall
and click OK.
5. In the left pane, click Advanced Settings.
6. If required:
7. In the Windows Firewall with Advanced Security dialog, click Inbound Rules.
8. In the left pane, click New Rule.
9. Follow the instructions in the New Inbound Rule Wizard.
10. Switch to the Exceptions tab.
Two main levels open. Exceptions can be added on these levels.
Add Program specifies which applications are able to respond to unsolicited
requests.
Add Port specifies that the firewall should allow TCP traffic at ports used by the
servers.
11. On the General tab, tick the On (recommended) check box.
The firewall is now active.
49.3 Appendix C - Installing a USB modem driver

Before the modem can be used, the USB modem driver must be installed on the computer.

1. With the computer running, plug the connector of the modem into the appropriate
port.
The computer detects the modem as a new piece of hardware.
The Found New Hardware message is displayed.
2. Select the No, Not This Time option and click Next.
3. Click Next.
4. Insert the DVD delivered with the modem into the DVD drive and click Next.
Follow the instructions of the wizard to install the modem as external hardware.
5. Unplug the USB connector when the installation is finished.
6. Restart the computer.
When the USB connector is plugged into the computer again the modem will be
recognized.
7. To check the COM port, select Settings Control Panel System.
9. To display the COM port, open the Ports (COM and LPT) node.
The USB modem driver is installed.
49.4 Appendix D - Installing the DTM or CommDTM

The FieldCare DTM library is regularly updated with all the recently released DTMs. It can
be supplied on DVD as an update service. Alternatively the latest DTMs can be downloaded
from the website of the manufacturer or FDT group. A DTM can also be supplied on a DVD
182 Endress+Hauser
with a new device. The DTM must be installed and the DTM catalog updated before
FieldCare can work with a new DTM.
Installing the DTM or CommDTM

1. Either insert the DVD into the DVD drive of the computer or download the DTM from
the manufacturer's website.
Click the Setup.exe.
The installation is started. If AUTORUN is enabled the DVD will start
automatically.
The DTM Setup Wizard starts.
2. Follow the instructions in the Setup Wizard.
3. Click Next after each command.
4. If the installation was successful, a dialog appears with a message to this effect.
Click Finish.
The dialog is closed and the installation is completed.
If the DTM is licensed, the license key must be entered according to the
manufacturer's instructions.
49.5 Appendix E - Updating the FieldCare DTM catalog

The FieldCare DTM catalog must be updated if a new DTM is installed. You require
administrator rights to update the FieldCare DTM catalog.
1. Updating the DTM catalog

Start FieldCare and log in as the administrator.
2. In the startup screen click Continue and in the FieldCare dialog click Open.
3. Open DTM Catalog and click Update.
The Update DTM Catalog dialog appears. The left-hand pane is initially empty.
4. Click Update.
The search for DTMs is started. This can take a few minutes.
When the search is finished, the new DTM catalog appears.
5. Select new DTMs and click Move and OK.

The Update DTM Catalog dialog closes and the changes are accepted.
The DTM catalog is updated.
Endress+Hauser 183
49.6 Appendix F - Replacing the iDTM with a DeviceDTM

iDTM allows the integration of devices that have no appropriate DTM available. It has,
however, less functionality than a DTM.
If appropriate DTMs become available, the devices that were integrated into the FieldCare
project with the iDTM can be operated with this DTM. For this purpose, the iDTM must be
replaced with the DeviceDTM.
After replacement, the saved information of the iDTM must be entered again
manually in the new DTM.
Replacing an iDTM with a DeviceDTM

1. Install the DTM as described in Appendix D. 182
2. Update the FieldCare DTM Catalog as described in Appendix E. 183
4. Select Device Type (DTM) Info.

The Device Type (DTM) Information dialog opens.
A list of all the suitable DTMs appears.

5. Select the DeviceDTM.
6. If the DTM should be replaced for several devices:
Tick the Save Assignment for All Devices of Same Type check box and click OK.
The Assign Device Type (DTM) dialog opens.
7. Click Yes.
The Device Type (DTM) Information dialog opens.
8. Click OK.
The changes are accepted.
The iDTM has been replaced by the DeviceDTM.
49.7 Appendix G - User roles

Different user roles are available to ensure that only authorized persons have access to the
technology and functions. Every user can log in with a specific role he/she has been
assigned. The user receives authorization for certain functions. Furthermore, the rights
can be defined for a set period.
184 Endress+Hauser
The administrator has full authorization:

To perform all functions without restriction, such as development, commissioning and
run-time phases in FieldCare
For administrative tasks, such as assigning user accounts
To change or update the DTM catalog
The planning engineer has full authorization:
To perform all functions without restriction, such as development, commissioning and
run-time phases in FieldCare
The service engineer has full authorization:
To perform authorized commissioning and run-time phases
For device replacement, calibration and adjustment
To write parameters to the device, change them or read them, or to perform device-
specific operations in the online mode
The user has full authorization:
To perform authorized commissioning and run-time phases
To observe and manage the current process
To check the current device condition and change the target values to ensure the proper
functioning of the device
The observer has full authorization:
To observe the current process
To read device parameters and documents of connected devices
49.8 Appendix H - Verifying the network

The network topology in FieldCare can be compared against the actual physical network.
This is particularly useful if a device is added to an existing network. A project can be
prepared offline and then uploaded via FieldCare. In this way it is possible to verify the
current topology in the network and the physical topology to make any necessary changes.
Before verifying the network please note that only verified networks are verified for
communication devices that have at least one DTM. Otherwise the Verify Network
menu item is disabled.
Verifying the network

1. In the Network dialog select a device with at least one DTM.
2. In the tool bar, click the Verify Network icon .
The Communication Channel dialog opens.
3. Select the desired channel and click OK.
FieldCare scans the desired channel.
Once the network has been verified, the Scanning Result dialog opens.
A Live list is displayed and the Status column indicates how well the devices in
the pre-planned topology fit into the actual topology.
There are five different states in total:
The device types and serial numbers are identical.
The device types are identical.
The device types are different.
A new device has been found.
Unexpected device in the project.
4. Changes can be made in the context menu for the individual device, e.g. reading or
writing device data or replacing the device type.
Click OK once the necessary changes have been made.
The changes are saved.
Endress+Hauser 185
49.9 Appendix I - PROFIBUS PA Profile

If no native DeviceDTMs are available for devices up to PA Profile 3.0, it is possible to use a
PROFIBUS PA Profile. The following profiles are available for the devices:
Actuator Profile DTM
Discrete Input Profile DTM
Discrete Output Profile DTM
Flow Profile DTM
Level Profile DTM
Pressure Profile DTM
67 Pressure Profile DTM
49.10 Appendix J - Generic HART

If a native DeviceDTM is not available for HART/HART7, the Generic HART DTM can be
used.
The Generic HART DTM has the following options:
Identify device
Configure device
Trend values with archive function
Device diagnosis
Device calibration
For more details, please refer to the online help of the Generic HART DTM.
68 Generic HART DTMs
49.11 Appendix K - Fieldgate SFG500 error information

All the devices connected to the PROFIBUS are displayed in the Fieldgate SFG500 Web
application. Detailed information about the cause of the error can be displayed here. The
Web application can be started in FieldCare:
186 Endress+Hauser
1. In the Network dialog, right-click to select the SFG500 item. The SFG500 must be
online for this (green background)
2. Select the Additional Functions Embedded Webserver item.
The SFG500 Web application not only displays the PROFIBUS devices in a livelist but also
the HART devices behind Remote I/Os (ET200M/iSP, Stahl IS1, Turck excom, ABB S900)
and also PROFIBUS PA devices behind Siemens Link.
If HART/PA devices are not recognized when scanning or connecting, the user can check
here whether the devices are even on the bus or whether the Remote I/Os have been
configured.
Detailed information can be displayed for every entry.
Remote I/O devices

Remote I/O devices must generally be configured by a cyclic master for it to be possible to
scan for HART devices.
Multiple remote I/O devices cannot be operated on the bus with two acyclic masters.
Endress+Hauser 187
Index
Index
09 HART RSG45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
1788-EN2PAR DTM . . . . . . . . . . . . . . . . . . . . . . . . . 83 Heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
HIMA multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
B HS EtherNet/IP DTM . . . . . . . . . . . . . . . . . . . . . . . . . 83
Bench mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 HSE Network Setup . . . . . . . . . . . . . . . . . . . . . 132, 138
C I
CDI Communication TCP/IP . . . . . . . . . . . . . . . . . . . 172 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
CDI interface . . . . . . . . . . . . . . . . . . 164, 167, 170, 172 Installing the DTM . . . . . . . . . . . . . . . . . . . . . . . . . 182
CommDTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Installing the USB modem driver . . . . . . . . . . . . . . . 182
Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 IP address . . . . . . . . . . . . . . 87, 89, 114, 131, 138, 181
Commubox FXA191 . . . . . . . . . . . . . . . . . . . . . . . . . 23 IPC interface . . . . . . . . . . . . . . . . . . . . . . . . . . 160, 163
Commubox FXA195 . . . . . . . . . . . . . . . . . . . . . . . . . 28 ISS interface . . . . . . . . . . . . . . . . . . . . . . . . . . 156, 159
D M
Device tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 MACTek Bluetooth modem . . . . . . . . . . . . . . . . . . . . 61
Device USB interface . . . . . . . . . . . . . . . . . . . . . . . . 170 Modbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Document Modbus DTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Document function . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 N
NIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
E
Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 O
Ethernet TCP/IP interface . . . . . . . . . . . . . . . . . . . . 172 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
EtherNet/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Explosion protection . . . . . . . . . . . . . . . . . . . . . . . . . 14 P
Password . . . . . . . . 13, 36, 87, 131, 133, 138, 139, 181
F PBI-Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Field Controller SFC162 . . . . . . . . . . . . . . . . . . 131, 137 PCP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Field Controller SFC162 Web server . . . . . . . . . . . . . 138 Pepperl+Fuchs coupler . . . . . . . . . . . . . . . . . . . . . 94, 98
Field Controller Web server . . . . . . . . . . . . . . . . . . . 131 Pepperl+Fuchs HART multiplexer . . . . . . . . . . . . . . . 34
Fieldgate FXA720 . . . . . . . . . . . . . . . 86, 100, 105, 109 Pepperl+Fuchs LB/FB Remote I/O . . . . . . . . . . . . . . . 42
Fieldgate FXA720 Web server . . . . . . . . . . . . . . . . . . 87 Plant view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Fieldgate login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 PROCENTEC ProfiCore . . . . . . . . . . . . . . . . . . . . . . . 120
Fieldgate SFG500 error information . . . . . . . . . . . . . 186 PROFIBUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
FieldgateFXA520 . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 PROFIBUS CommDTM . . . . . . . . . . . . . . . . . . . . 86, 100
FieldgateSFG500 . . . . . . . . . 94, 98, 100, 103, 105, 109 PROFIBUS DeviceDTMs 83, 86, 94, 98, 100, 105,
FOUNDATION Fieldbus DeviceDTMs 131, 137, 145, 148 109, 113
FOUNDATION Fieldbus H1 . . . . . . . . . . . . . . . . . . . 131 PROFIBUS DP . . . . . . . . . . . . . . . . . . . . . . . . . 117, 120
FOUNDATION Fieldbus iDTM . . . . . . 131, 137, 145, 148 PROFIBUS DP/PA . . . . . . . . . . . . . 94, 98, 100, 105, 109
FXA193 modem . . . . . . . . . . . . . . . . . . . . . . . 156, 160 PROFIBUS PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
FXA291 modem . . . . . . . . . . . . . . . . . . . 159, 163, 176 PROFIBUS PA Profile . . . . . . . . . . . . . . . . . . . . . . . . 186
PROFIdtm DPV1 CommDTM . . . . . . . . . . . . . . . . . . . 86
G PROFINET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Generic HART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
R
H Replacing the iDTM with a DTM . . . . . . . . . . . . . . . 184
HART CommDTM . . . . . . . . . . . . . . . 23, 28, 34, 56, 61
HART DeviceDTMs . 23, 28, 34, 56, 61, 70, 73, 105, 109 S
HART iDTM . . . . . . . . . . . . . . . . . . . . . . . . . . 25, 31, 62 SFC162 CommDTM . . . . . . . . . . . . . . . . . . . . . . . . . 131
HART IP CommDTM . . . . . . . . . . . . . . . . . . . . . . . . . 73 SFGNetwork DTM . . . . . . . . . . . . 94, 98, 100, 105, 109
HART Multidrop . . . . . . . . . . . . . . . . . . . . . . . . . 56, 61 Siemens ET200M/iSP . . . . . . . . . . . . . . . . . . . . . . . 103
HART multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Siemens link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
HART multiplexer master KFD2-HMM-16 (FDT) smar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
CommDTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Stahl CommDTM CPM 9440 . . . . . . . . . . . . . . . . . . 109
HART point-to-point connection . . . . . . . . . . 23, 28, 56 Stahl Remote I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
HART Remote I/O . . . . . . . . . . . . . . . . . . . . . . 105, 109 SWA70 CommDTM . . . . . . . . . . . . . . . . . . . . . . . . . . 70
188 Endress+Hauser
Index
SWG70 CommDTM . . . . . . . . . . . . . . . . . . . . . . . . . . 73
T
Turck CommDTM EXCOM . . . . . . . . . . . . . . . . . . . . 105
Turck Remote I/O . . . . . . . . . . . . . . . . . . . . . . . . . . 105
TXU10 modem . . . . . . . . . . . . . . . . . . . . . . . . 167, 176
U
User roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
V
VerificationDTM . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Verifying the network . . . . . . . . . . . . . . . . . . . . . . . 185
W
WAGO Remote I/O . . . . . . . . . . . . . . . . . . . . . . . . . 117
Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Windows Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Endress+Hauser 189
www.addresses.endress.com

Ba00065sen 0516

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Ba00065sen 0516

Încărcat de

Drepturi de autor:

Formate disponibile

BA00065S/04/EN/05.

16 Products Solutions Services

2. www.endress.com/deviceviewer Endress+Hauser Operations App

2.09.xx BA00065S/04/EN/ Original Operating Instructions

2.09.xx BA00065S/04/EN/ New Chapter about WirelessHART, NI card, FFusb modem;

Editorial USB installation in Appendix C, Procedure in Windows 7

2.10.xx BA00065S/04/EN/ Layout New CMS

2.10.xx BA00065S/04/EN/ New Chapter 8: HART via RSG45

2.11.xx BA00065S/04/EN/ New Chapter 3 Introduction to FieldCare

1 Document information . . . . . . . . . . . . . . 9 6.1.2 Loop power from the transmitter

10 HART via Rockwell Automation

13 HART point-to-point or HART 22.2 Commissioning the Fieldgate FXA720 . . . . . . 87

31 PROFIBUS DP via PROCENTEC 36 FOUNDATION Fieldbus H1 via the

34 FOUNDATION Fieldbus H1 via Field

45 CDI interface via direct USB

46 CDI interface via Ethernet TCP/IP . 172

47 PCP interfaces via the FXA291/

48 Interface to W@M . . . . . . . . . . . . . . . . 179

1.1 Document function

1.2 Symbols used

1.2.1 Safety symbols

1.2.2 Symbols for certain types of information

Notice or individual step to be observed

Help in the event of a problem

Previous symbol Current symbol Meaning

Start new project.

Open existing project.

Save open project.

Print open project.

Show DTM catalog.

Open documentation for selected device or detailed device

Add new device to the network.

Remove device from the network.

Create new network topology using CommDTM and DeviceDTMs.

Compares the network topology in the field with the actual

Indicates whether there is a connection with the device.

Transfer information from the device to FieldCare.

Transfer information from FieldCare to the device.

Device-specific functions for the selected device.

Add plant level.

Remove plant level.

Open device checklist to show selected devices in the plant.

Confirm replaced device.

Previous symbol Current symbol Meaning

Communication channel occupied or communication action

W@M symbol, appears in the start bar on the bottom right if a

Switch on touch mode

Switch off touch mode

1.3 Text emphasis

Angle brackets Variables <DVD-ROM drive>

1.4 Acronyms used

CDI Common Data Interface

COM Communication Equipment

CommDTM Communication Device Type Manager

CSV Character Separated Value

DTM Device Type Manager

FDT Field Device Tool

FIFO First In First Out

HART Highway Addressable Remote Transducer

ISS Internal Service Interface

LAN Local Area Network

LAS Link Active Scheduler

NIC Network Interface Card