Issue Date: 28-DEC-2012 Rev.

Date: 03-JAN-2013 Revision: 01

Author: Jose Alberto Leon Page 1 of 15 Content ID: 6100356

Schlumberger Private
UniConn Modbus Master in LiftWatcher
DATASHEET AND CONTROLLER SETUP

Revision History
Rev.
No. Effective Date Description
01 03-JAN-2013 First release

 Copyright Statement This document remains the property of Schlumberger and is Confidential
and Trade Secret. Do not disclose, use, or reproduce without written approval from
Schlumberger
 Page 2 of 15

Introduction .................................................................................................................................... 3
When Modbus Master should be used? ................................................................................................... 3
How does it work? ......................................................................................................................................... 3
Limitations ....................................................................................................................................................... 6
UniConn configuration .................................................................................................................................. 6
Comm card Modbus Master setup............................................................................................................. 8
MBM Channel Configuration ....................................................................................................................... 9
LiftWatcher Datasheet configuration ...................................................................................................... 12
Appendix........................................................................................................................................ 15
Modbus master telemetry Map ................................................................................................................ 15

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 3 of 15

INTRODUCTION

UniConn Modbus Master was a feature released as part of firmware 1.405r1 in 2010 but was
recently included as part of standard devices in LiftWatcher.

Modbus Master will let UniConn to communicate with other devices using Modbus protocol but
like a master or initiator instead of only answer queries from an acquisition system (SCADA or
LiftWatcher).

This document will focus on how to configure UniConn and how to prepare LiftWatcher datasheet
to work with UniConn Modbus Master.

WHEN MODBUS MASTER SHOULD BE USED?

There is a standard list of devices that can be configured and connected in LiftWatcher and you
can choose from it in the LiftWatcher Datasheet. If you are trying to connect a new device and it
is not part of the list, it could be a potential candidate to use Modbus Master as solution.

If a device is not part of standard list, there are two options. One is to contact InTouch and ATL
Real Time team to get the new device implemented as part of the standard list. This could take
some time, testing and development to have a new version of the datasheet released.

Other solution will be to use Modbus Master. Of course the limitation is that you need to have
one UniConn and one free slot to install a new Com Card in. The advantage is almost any device
could be connected and you do not need to wait to get that device to be included in LiftWatcher.

HOW DOES IT WORK?

Currently if you need to connect a device to LiftWatcher, it has to be defined in the datasheet.
Once the datasheet is created, a “template” with the variables/points is uploaded into the PAC as
part of commissioning process. Basically if you need to connect a Phoenix ISP, SoloConn or a
competitor controller, the datasheet create the proper template to read/write information for that
particular device.

As you can imagine more and more often there are cases where field users need to connect a
new type of device to LiftWatcher. There are too many different controllers, PLCs, transmitters
and controller to have all of them in the datasheet. Also if you are going to use it only once in a

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 4 of 15

specific project probably make no sense to have it available for all other LiftWatcher users.

Figure 1 – Wellsite with UniConn and standard RTUs

Above there is an example where UniConn, RTU X and RTU Y are connected to a SCB. In this
case RTU X and RTU Y must be part of the datasheet in order to be connected in LiftWatcher

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 5 of 15

But what happened if RTU X and RTU Y are not part of the datasheet? In that case you can
configure UniConn as Modbus Master and read the values from the RTUs. Once the information
from RTU X and RTU Y is in UniConn, the PAC will be able to read those values from UniConn and
send into LiftWatcher server.

Figure 2 – Wellsite with UniConn Master

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 6 of 15

Using UniConn Modbus Master you can configure up to 16 channels (Input or Holding registers)
and up to 8 digitals (coil or input status).

Once UniConn has been configured as Modbus Master, the values read from the RTUs will be
moved into UniConn memory map and they will be available as any other internal parameter.

Please refer to Appendix A for UniConn Modbus Master Map.

LIMITATIONS

We already mentioned in previous sections that one limitation is that you need to have a UniConn
in the location. Also it has to have a free slot and an additional Com Card to work as Master.

There are other limitations:

• UniConn only 8 of 16 channels are alarmable

• UniConn Modbus Master can only read 16bits Integer Registers. You cannot configure to
read IEE Floating point or 32bits registers

UNICONN CONFIGURATION
Using StarView you should configure the proper slot where you have the Comm Card as Modbus
Master:

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 7 of 15

Figure 3 – Configuration of Comm Card as Master

In this example, there is one Com Card installed in slot #2 that will be used as Modbus Master and
in slot #3 there is another Com card that is used to connect UniConn with LiftWatcher PAC/SCB

Once a Modbus Master card has been configured, it should be visible on the main screen in
similar way that a DHT or VSD is displayed (if configured)

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 8 of 15

Figure 4 – Modbus Master in main screen

COMM CARD MODBUS MASTER SETUP

Modbus Master Screen can be access from “Database” menu bar or doing double click on MBM
section at main screen:

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 9 of 15

Figure 5 – Modbus Master Configuration screen

It has 3 sections:

• Main Configuration: Where you can set polling, space, timeout and retries

• Channel Configuration: Here is where you will configure which registers to be read and
from which Slave. More details in next section of this document

• Channel Status: If will display if there is an error and which channel

MBM CHANNEL CONFIGURATION

As discussed in previous sections, there are 16 analog and 8 discrete status registers than can be
read and configured in LiftWatcher using UniConn MBM option.
 Copyright Statement: This document remains the property of Schlumberger. It is Confidential
and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 10 of 15

The first 8 channels are alarmable as you can see in picture below:

Figure 6 – Alarmable Registers Configuration

Alarm settings as Action, Setpoint, Trip Time, etc., are the same as any other alarm in UniConn
and will not be discussed in this document. For other settings an example will be used.

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 11 of 15

Figure 7 – Channel configuration

Each channel has the option to enter a Name or Label. In order to read the channel from the
slave device it has to been enabled. Site ID is the Modbus Slave ID for the device. In this case
the RTU X has a slave ID 5 and RTU Y has slave ID 6.

Modbus Register is the memory address from where the value has to be read. In Modbus
protocol there are two types of registers. Holding Registers are also known as 4X registers. In
some nomenclature are also referred as 40,000 registers. Input Registers are also known as 3X or
30,000 registers.

For UniConn Modbus Master you need to use 6 digits, so the first Holding Registers will be
entered as 40001 and the first Input Registers will be 30001.

Resolution will tell UniConn how many “bits” of the register will be used to calculate the final
value of the channel. In LiftWatcher you should use 1:1. It tells you that the same value read from
the Slave device will be moved and write as channel value. Also using 1:1 as resolution will
ignore the configuration entered in “raw” and “scale” settings.

You can use a different setting for resolution. In that case you need to also configure raw and
scale. You can choose to use 16, 15, 14 etc., bits as max resolution. Use following table as
reference:

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 12 of 15

Resolution Bits Maximum Value

16 65535
15 32767
14 16383
13 8191
12 4095
11 2047
10 1023
9 511
8 255

For LiftWatcher application, please use a Resolution of 1:1

For Discrete registers there are two types of status registers in Modbus. Coils are also known as
0X registers. The other type of status is the Input Status also known as 1X or 10,000 register.
Since status is a discrete/Boolean value, it does not use resolution or scaling. A value of “0” is
displayed as LOW and “1” is HIGH in StarView.

Since Modbus Master will read registers as 16 bits Integer, it is likely that a scaling is
needed to get decimal places. Some cases the registers need to be divided by 10 or 100
to match engineering units. For example, a frequency of 52.25Hz could be read as 5225
and will require scaling. In LiftWatcher this can be done in the datasheet. Please read
next section.

LIFTWATCHER DATASHEET CONFIGURATION

Once Modbus Master has been configured then LiftWatcher datasheet has to be filled up and
send to ProSer for commissioning of the well site.

UniConn Modbus Master is now part of the devices and it can be selected from the datasheet
device drop down menu. In similar way as any other device, you need to click “Add…” and then
from the list chose “UniConn Modbus Master”

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 13 of 15

Figure 8 – UniConn Modbus Master selection in datasheet

Once Modbus Master is selected, there are some other settings that need to be entered.

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 14 of 15

Figure 9 – UniConn Modbus Master Configuration in Datasheet

Modbus Address should be the same ID of UniConn slave Comm card. This could be confusing
but remember that PAC/SCB will read the values of Master channels using the slave Comm Card.
Even though in this example channel 1 is read from RTU X (Slave ID 5) and from RTU Y (slave ID 6)
in the datasheet you need to use UniConn ID and not RTUs ones.

If scaling is needed in one channel or IO point, you need to first enable it and then enter Raw and
Scaled values.

In Figure 9, for Chanel 1, the value read from the RTU will be divided by 100. If the value
read was 5678 the value in LiftWatcher will be displayed as 56.78

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.
 Page 15 of 15

APPENDIX
MODBUS MASTER TELEMETRY MAP

DESCRIPTION REGISTER UNITS TYPE READ/WRITE MIN MAX

Modbus Master Input 9 32557 unitless Unsigned Integer R 0 65,535
Modbus Master Input 1 32558 unitless Unsigned Integer R 0 65,535
Modbus Master Input 10 32559 unitless Unsigned Integer R 0 65,535
Modbus Master Input 2 32560 unitless Unsigned Integer R 0 65,535
Modbus Master Input 11 32561 unitless Unsigned Integer R 0 65,535
Modbus Master Input 3 32562 unitless Unsigned Integer R 0 65,535
Modbus Master Input 12 32563 unitless Unsigned Integer R 0 65,535
Modbus Master Input 4 32564 unitless Unsigned Integer R 0 65,535
Modbus Master Input 13 32565 unitless Unsigned Integer R 0 65,535
Modbus Master Input 5 32566 unitless Unsigned Integer R 0 65,535
Modbus Master Input 14 32567 unitless Unsigned Integer R 0 65,535
Modbus Master Input 6 32568 unitless Unsigned Integer R 0 65,535
Modbus Master Input 15 32569 unitless Unsigned Integer R 0 65,535
Modbus Master Input 7 32570 unitless Unsigned Integer R 0 65,535
Modbus Master Input 16 32571 unitless Unsigned Integer R 0 65,535
Modbus Master Input 8 32572 unitless Unsigned Integer R 0 65,535
Modbus Master Discrete Input 1 10369 unitless Discrete R 0 1
Modbus Master Discrete Input 2 10370 unitless Discrete R 0 1
Modbus Master Discrete Input 3 10371 unitless Discrete R 0 1
Modbus Master Discrete Input 4 10372 unitless Discrete R 0 1
Modbus Master Discrete Input 5 10373 unitless Discrete R 0 1
Modbus Master Discrete Input 6 10374 unitless Discrete R 0 1
Modbus Master Discrete Input 7 10375 unitless Discrete R 0 1
Modbus Master Discrete Input 8 10376 unitless Discrete R 0 1
Modbus Master Output 1 32579 unitless UNSIGNED INT R 0 65,535
Modbus Master Output 2 32580 unitless UNSIGNED INT R 0 65,535
Modbus Master Output 3 32581 unitless UNSIGNED INT R 0 65,535
Modbus Master Output 4 32582 unitless UNSIGNED INT R 0 65,535
Modbus Master Output 5 32583 unitless UNSIGNED INT R 0 65,535
Modbus Master Output 6 32584 unitless UNSIGNED INT R 0 65,535
Modbus Master Output 7 32585 unitless UNSIGNED INT R 0 65,535
Modbus Master Output 8 32586 unitless UNSIGNED INT R 0 65,535
Channel Comms status 1-16 32573 unitless UNSIGNED INT R 0 65,535
Channel Comms status 17-32 32574 unitless UNSIGNED INT R 0 65,535
Channel Comms status 33-40 32575 unitless UNSIGNED INT R 0 65,535

 Copyright Statement: This document remains the property of Schlumberger. It is Confidential

and Trade Secret and not to be disclosed, used, or reproduced without written approval from
Schlumberger.