FCO7xx

Fieldbus Interface
(PROFINET, EtherNet/IP)

Copyright  2019 Furness Controls Ltd

All information within this document is for use with Furness Controls instrumentation
and software only. This protocol is not to be used by any third-party software package
without written permission from Furness Controls Ltd.

Manufactured by:

FURNESS CONTROLS LIMITED

Beeching Road, Bexhill, East Sussex, TN39 3LG, England.
Telephone +44 (0)1424 819980
Email: sales@furness-controls.com
Web Site: http://www.furness-controls.com
 TABLE OF CONTENTS
TABLE OF CONTENTS ..................................................................................................................................... 1
REVISION RECORD .......................................................................................................................................... 2
INTRODUCTION ................................................................................................................................................ 3
GENERAL DESCRIPTION ....................................................................................................................................... 3
PROFINET IO ...................................................................................................................................................... 4
GENERAL............................................................................................................................................................. 4
IP ADDRESS ASSIGNMENT ................................................................................................................................... 4
I/O CONFIGURATION ........................................................................................................................................... 4
GSDML FILE ...................................................................................................................................................... 4
CONNECTOR PIN ASSIGNMENTS .......................................................................................................................... 5
ETHERNET/IP ..................................................................................................................................................... 6
GENERAL............................................................................................................................................................. 6
IP ADDRESS ASSIGNMENT ................................................................................................................................... 6
I/O CONFIGURATION ........................................................................................................................................... 6
EDS FILE............................................................................................................................................................. 7
CONNECTOR PIN ASSIGNMENTS .......................................................................................................................... 7
INPUT / OUTPUT REGISTERS ........................................................................................................................ 8
INPUT REGISTERS (288 BYTES) ............................................................................................................................ 8
OUTPUT REGISTERS (256 BYTES) ......................................................................................................................... 9
EXTERNAL ANYBUS MODULE .................................................................................................................... 11
RS232 CONFIGURATION .................................................................................................................................... 11
RS485 CONFIGURATION .................................................................................................................................... 12
ASCII CODES .................................................................................................................................................... 13

Page 1 Issue 6 FCO7xx Fieldbus Interface

 REVISION RECORD
Issue Date Summary of changes

1 23/04/19 First release.

1a 29/4/19 Input registers 0x011C – 0x01FF now used for status
2 16/7/19 Ethernet/IP information added.
NAK response code corrected
2a 13/8/19 Ethernet/IP EDS file download information added
3 24/10/19 External Module use added and RS485 info.
3a 28/2/2020 I/O bytes revised to show actual bytes allocated.
4 18/8/20 Input register total bytes used and addresses corrected.
5 2/11/20 Link to IP Config added
6 1/12/20 Product number example corrected

FCO7xx Fieldbus Interface Issue 6 Page 2

 INTRODUCTION
General Description
NOTE: This document is applicable to all Furness Controls FCO7xx instruments that are fitted with a Fieldbus
interface.

Furness Controls production-line test equipment can be supplied with different communication interfaces for
interfacing with PLCs. These interfaces can be used to implement the F-BUS protocol over fieldbus such
PROFIBUS, PROFINET and EtherNet/IP.

As F-BUS is made available within all Furness equipment, it is easy to connect Leak Detectors, Flow Meters
and Pressure Indicators to a PC.

Whilst the F-BUS protocol defines the way that information is transferred between a master controller (PC or
PLC) and one or more slave devices, the physical connection method between instruments is defined by the
PROFIBUS, PROFINET or EtherNet/IP standard.

Page 3 Issue 6 FCO7xx Fieldbus Interface

 PROFINET IO
General
The PROFINET interface is implemented using the AnyBus Communicator for PROFINET (Part number:
AB7013)

The PROFINET IO interface provides PROFINET IO Soft Real-Time Communication. PROFINET is the open
Industrial EtherNet standard for Automation from PROFIBUS International.

Supported Features
• Soft Real-Time (RT) communication
• Cyclic data exchange (10 ms cycle time)
• Acyclic Data exchange (Record Data Requests)
• Up to 64 slots / 1 subslot
• Up to 512 bytes of I/O in each direction
• TCP/IP Configuration via DCP (Discovery and Configuration Protocol)

IP Address assignment
For Profinet, it is usually possible to assign an IP address from the Profinet Controller. However, the IP address
can also be assigned manually using the PC utility, IPConfig.exe

The IPConfig Setup program can be downloaded from: www.furness.com/info

Select “Downloads”, “Utilities” and then select “IPConfig”.

I/O Configuration
PROFINET makes a distinction between fast cyclical data, a.k.a. “IO data”, and acyclical data, called “Record
Data”. By default, all data in the input and output data areas are exchanged as IO data. It is however possible to
specify how much data to exchange as IO data, and how much data to exchange using acyclic Record Data
read/write requests.
On PROFINET, the IO data is built up by I/O modules. The actual I/O module configuration is adopted from the
I/O controller/supervisor. The modules are mapped to the input and output data areas in the order of their slot
number.

The interface has 288 inputs and 256 outputs. These can be mapped to the Profinet slots as:

Slot 01: Input 256 bytes

Slot 02: Input 016 bytes
Slot 03: Input 008 bytes
Slot 04: Input 004 bytes
Slot 05: Input 004 bytes
Slot 06: Output 256 bytes

GSDML File
On PROFINET, all devices are associated with a GSDML file. The GSDML file is the equivalent of the
PROFIBUS GSD file, and is based on the EXtensible Markup Language (XML). This file holds information
about the device (in this case the Anybus Communicator), its features, and possible I/O configurations.
The latest version of the GSDML file for the Anybus Communicator can be downloaded from the HMS website,
“www.anybus.com”.
Alternatively, it can be downloaded from: https://www.furness.com/info
Select “Downloads”, “Drivers” and then select “Profinet GSDML files.zip”.

FCO7xx Fieldbus Interface Issue 6 Page 4

Connector Pin Assignments

Page 5 Issue 6 FCO7xx Fieldbus Interface

 ETHERNET/IP
General
The EtherNet/IP interface is implemented using the AnyBus Communicator for EtherNet/IP (Part number:
AB7072)

EtherNet/IP is based on the Control and Information Protocol (CIP), which is also the application layer
for DeviceNet and ControlNet. The Anybus Communicator acts as a Group 2 or 3 server on the
EtherNet/IP network.
Input and output data is accessed using I/O connections towards the assembly object.

IP Address assignment
For Ethernet/IP, it is usually possible to assign an IP address from the Ethernet/IP Controller. However, the IP
address can also be assigned manually using the PC utility, IPConfig.exe

The IPConfig Setup program can be downloaded from: www.furness.com/info

Select “Downloads”, “Utilities” and then select “IPConfig”.

I/O Configuration
Data Types
The input and output data (I/O data) is exchanged on change of value, and can be accessed using I/O
connections towards the assembly object.

Assembly Object, Class 04h

General Information
Object Description
This object provides access to the I/O Data in the input and output data areas in the Anybus Communicator.

Supported Services
Class services: Get Attribute Single
Instance services: Get Attribute Single
Set Attribute Single

Class Attributes
# Access Name Type Value Description
1 Get Revision UINT 0002h Revision 2
2 Get Max Instance UINT - The highest initiated instance no.

Instance 64h (100) Attributes

This instance corresponds to I/O data (input) in the gateway.
# Access Name Type Value Description
3 Get Data Array of BYTE - Data produced by the gateway

Instance 96h (150) Attributes

# Access Name Type Value Description
3 Set Data Array of BYTE - Data consumed by the gatewaya

FCO7xx Fieldbus Interface Issue 6 Page 6

a. Rockwell Automation PLCs have the first four bytes consumed by a device defined as status information.
This behaviour is specific to devices from Rockwell Automation and is not defined in the EtherNet/IP
specification.
However, since all known PLCs are implemented this way, the Anybus Communicator adopts this behaviour
and strips off the corresponding four bytes from the consumed data.

Instance C6h (198) Attributes (Heartbeat Input-Only)

This instance is used as heartbeat for input-only connections, and does not carry any data.

Instance C7h (199) Attributes (Heartbeat, Listen-Only)

This instance is used as heartbeat for listen-only connections, and does not carry any data.

EDS File
The latest version of the EDS (Electronic DataSheet) file for the Anybus Communicator can be downloaded
from the HMS website, “www.anybus.com”.
Alternatively, it can be downloaded from: https://www.furness.com/info
Select “Downloads”, “Drivers” and then select “Ethernet-IP EDS file.zip”.

Connector Pin Assignments

Page 7 Issue 6 FCO7xx Fieldbus Interface

 Input / Output Registers
The following tables show the PROFINET I/O or EtherNet/IP register assignments that are used to implement
the F-BUS protocol. The AnyBus Communicator implements the protocol so that the checksum calculations etc
are not required by the PLC.

Commands:
Any change to the command register will automatically issue that command to the Leak Detector. E.g. changing
the value of register 0203H will issue the start command to the leak detector. The PLC can then interrogate
register 0003H to ensure that the command has been acknowledged.

Refer to the appropriate “Fbus Commands” user guide for details of the F-BUS commands for your instrument.

Input registers (288 bytes)

Address
0x0000 – 0x0002 (3 chars)
0x0003 (1 char)
0x0004 – 0x003F (60 chars)
0x0040 – 0x011B (220 chars)
0x011C (1 char)
0x011D – 0x011F (3 chars)
0x0120 – 0x01FF (224 chars)
Function
RESERVED
ACK/NAK response for any 06h = ACK
command 15h = NAK
Status string received From M000 E.g. a2b4c0.02<null>
command. Updated approximately
every 200ms
Data string received from last E.g. a2b4c0.02<null>
command.
e.g. Last result string as received
From L002 command
Results available flag 30h = no result
Parameter “d” from status 31h = Result available
command.
Updated approximately every 100ms
Status Eg. 30h = Ready to start
Parameter “f” from status command Unused locations filled
Updated approximately every 100ms with null character
Unused (DO NOT MAP)

FCO7xx Fieldbus Interface Issue 6 Page 8

Output registers (256 bytes)
Address Function
0x0200 – 0x0201 (2 chars) reserved reserved
0x0202 (1 char) For external AnyBus modules only fbus id in ASCII
Instrument id. E.g. for id=1, 0x0202 = 31
Support id 1 to 9
0x0203 (1 char) Command: Start (G000) Any change to this address
will start the instrument.
0x0204 (1 char) Command: Reset (H000) Any change to this address
will reset the instrument.
0x0205 (1 char) Command: Select Product Any change to this address
number (Fxxx) will change the product
number.
Uses product number from
addresses 0x0221 – 0x0223
0x0206 (1 char) Command: Reset Counters (J000) Any change to this address
will reset the instruments
counters.
0x0207 (1 char) Command: Self check (K000) Any change to this address
will instigate a self-check.
0x0208 (1 char) Command: Zero Pressure (O000) Any change to this address
will zero the pressure sensor.
0x0209 (1 char) Command: Auto Zero trigger Any change to this address
(O001) will trigger an automatic zero.
0x020A (1 char) Command: Calibration Check Any change to this address
(V000) will instigate the calibration
check function.
0x020B (1 char) Command: Calibration Learn Any change to this address
(V001) will instigate the calibration
learn function.
0x020C (1 char) Command: Learn Offset (V002) Any change to this address
will instigate the Learn offset
function.
0x020D – 0x020E (2 chars) unused
0x020F (1 char) Command: send command Any change to this address
specified by 0x0220 – 0x02FF will send the command
defined by:
0x0220 = Command letter
0x0221 – 0x0223 = product
number
0x0224 – 0x02FF = data
parameters.
0x0210 (1 char) Enquiry: Get Results (L002) Any change to this address
will send the enquiry to get
the latest results. The result
data is then available from
inputs 0x0040 – 0x011B
Note: This command can only
be used if the result data does
not exceed 220 bytes.

Page 9 Issue 6 FCO7xx Fieldbus Interface

Output registers cont.
Address
0x0211 (1 char)
0x0212 – 0x0213 (2 chars)
0x0214 – 0x021E (11 chars)
0x021F (1 char)
0x0220 (1 char)
0x0221 – 0x0223 (3 chars)
0x0224 – 0x02FF (220 chars)
0x0300 – 0x03FF (256 chars)
FCO7xx Fieldbus Interface
Function
Enquiry: Get Results (L1xx)
Result step
0x0212 = MSD (x10)
0x0213 = LSD (x1)
Global result = step 00
unused
Enquiry: send enquiry specified
by 0x0220 – 0x0223
Command letter
Product number
0x0221 = MSD (x100)
0x0222 = (x10)
0x0223 = LSD (x1)
Fbus data parameters terminated
by a Null character
Unused (DO NOT MAP)
Issue 6
Any change to this address
will send the enquiry to get
the latest results for each test
step. The result data is then
available from inputs 0x0040
– 0x011B
Two digit step number in
ASCII
E.g. for step=05
0x0212 = 30
0x0213 = 35
Any change to this address
will send the enquiry defined
by:
0x0220 = Command letter
0x0221 – 0223 = product
number.
The result data is then
available from inputs 0x0040
– 0x011B
Fbus command letter for
0x020F Command or 0x021F
enquiry.
Three digit product number in
ASCII
E.g. for Product=027
0x0221 = 30
0x0222 = 32
0x0223 = 37
E.g. a2b4c0.02<null>
Page 10
 External AnyBus Module
If the AnyBus Communicator module is to be used externally of the FCO7xx instrument, the module will
require programming to suit the interface type to be used. This can be either RS232 or RS485.

Note that the external instrument id will need to be programmed into register 0x0202. This value needs to be in
ASCII, so id 1 = 31, id 2=32 etc

RS232 configuration
The AnyBus communicator will need to have been programmed to use its RS232 interface.

The Fbus Communication parameters programmed into the FCO7xx instrument need to be:

Port: RS232
ID Number: (as specified by output registers 0x0200 and 0x0201)
Baud: 57600
Parity: 8,none
Response Delay: 0

7xx Series
instrument
9 way D Socket

9 way D Plug
Rx Tx
2 3
AnyBus
Module Tx Rx RS232
3 2

Gnd Gnd
5 5

Cable Shield

RS232 connection to FCO7xx equipment.

Page 11 Issue 6 FCO7xx Fieldbus Interface

RS485 configuration
The AnyBus communicator will need to have been programmed to use its RS485 interface.

The Fbus Communication parameters programmed into the FCO7xx instrument need to be:

Port: RS485
ID Number: (as specified by output registers 0x0200 and 0x0201)
Baud: 57600
Parity: 8,none
Response Delay: 0

7xx series 7xx series

instrument instrument
RS485 RS485
Screw terminals Screw terminals
1 2 3 4 5 1 2 3 4 5
RX A
RX B

RX A
RX B
TX A

TX B

TX A
TX B
GND

GND
+5v
1

470R
9 way D Socket

T x+
8
AnyBus
120R
Module T x-
9

470R
Gnd
5
Cable Shield

RS485 connection to FCO7xx equipment.

Bias Resistors
When idle, RS485 enters an indeterminate state, which may cause the serial receivers to pick up noise
from the serial lines and interpret this as data. To prevent this, the serial lines should be forced into a
known state using pull-up and pull-down resistors, commonly known as bias resistors.
The bias resistors form a voltage divider, forcing the voltage between the differential pair to be higher
than the threshold for the serial receivers, typically >200 mV.
Note that bias resistors shall only be installed on one node; installing bias resistors on several nodes may
compromise the signal quality on the network and cause transmission problems.

Termination Resistor
As the baud rate is limited to 57600 baud and the cable lengths are expected to be relatively short, a termination
resistor at the end node it not required.

FCO7xx Fieldbus Interface Issue 6 Page 12

 ASCII CODES

Name Control Char Hex Dec Char Hex Dec Char Hex Dec Char Hex Dec
null ctrl @ NUL 00 0 SPC 20 32 @ 40 64 ` 60 96
start of heading ctrl A SOH 01 1 ! 21 33 A 41 65 a 61 97
start of text ctrl B STX 02 2 “ 22 34 B 42 66 b 62 98
end of text ctrl C ETX 03 3 # 23 35 C 43 67 c 63 99
end of xmit ctrl D EOT 04 4 $ 24 36 D 44 68 d 64 100
enquiry ctrl E ENQ 05 5 % 25 37 E 45 69 e 65 101
acknowledge ctrl F ACK 06 6 & 26 38 F 46 70 f 66 102
bell ctrl G BEL 07 7 ‘ 27 39 G 47 71 g 67 103
backspace ctrl H BS 08 8 ( 28 40 H 48 72 h 68 104
horizontal tab ctrl I HT 09 9 ) 29 41 I 49 73 I 69 105
line feed ctrl J LF 0A 10 * 2A 42 J 4A 74 j 6A 106
vertical tab ctrl K VT 0B 11 + 2B 43 K 4B 75 k 6B 107
form feed ctrl L FF 0C 12 , 2C 44 L 4C 76 l 6C 108
carriage return ctrl M CR 0D 13 - 2D 45 M 4D 77 m 6D 109
shift out ctrl N SO 0E 14 . 2E 46 N 4E 78 n 6E 110
shift in ctrl O SI 0F 15 / 2F 47 O 4F 79 o 6F 111

data line escape ctrl P DLE 10 16 0 30 48 P 50 80 p 70 112

device control 1 ctrl Q DC1 11 17 1 31 49 Q 51 81 q 71 113
device control 2 ctrl R DC2 12 18 2 32 50 R 52 82 r 72 114
device control 3 ctrl S DC3 13 19 3 33 51 S 53 83 s 73 115
device control 4 ctrl T DC4 14 20 4 34 52 T 54 84 t 74 116
negative ack ctrl U NAK 15 21 5 35 53 U 55 85 u 75 117
synchronous idle ctrl V SYN 16 22 6 36 54 V 56 86 v 76 118
end of tx block ctrl W ETB 17 23 7 37 55 W 57 87 w 77 119
cancel ctrl X CAN 18 24 8 38 56 X 58 88 x 78 120
end of medium ctrl Y EM 19 25 9 39 57 Y 59 89 y 79 121
substitute ctrl Z SUB 1A 26 : 3A 58 Z 5A 90 z 7A 122
escape ctrl [ ESC 1B 27 ; 3B 59 [ 5B 91 { 7B 123
file separator ctrl \ FS 1C 28 < 3C 60 \ 5C 92 | 7C 124
group separator ctrl ] GS 1D 29 = 3D 61 ] 5D 93 } 7D 125
record separator ctrl ^ RS 1E 30 > 3E 62 ^ 5E 94 ~ 7E 126
unit separator ctrl _ US 1F 31 ? 3F 63 _ 5F 95 DEL 7F 127

Page 13 Issue 6 FCO7xx Fieldbus Interface