4416.526 Rev.2

Instruction manual series 880 CIU Plus Page 1

Instruction manualseries 880 CIU Plus

January 2003Part no.: 4416.526_Rev2 PO-40032537PPAG-300-RI-K-148

Enraf B.V.P.O. Box 8122600 AV DelftNetherlands

Tel. : +31 15 2698600Fax : +31 15 2619574E-mail : [email protected] page : http://www.enraf.com

Page 2

Copyright 2000 - 2003 Enraf B.V. All rights reserved.

Reproduction in any form without the prior consent of Enraf B.V. is not allowed.This instruction manual is for information only. The contents, descriptions and specifications aresubject to change without notice. Enraf B.V. accepts no responsibility for any errors that mayappear in this instruction manual.

The warranty terms and conditions for Enraf products applicable in the country of purchase areavailable from your supplier. Please retain them with your proof of purchase.

Preface


A Caution draws attention to an action which may damage (theoperation of) the equipment.

A Note points out a statement deserving more emphasis than thegeneral text.

PrefaceThis manual has been written for the technicians involved with thecommunication with the Enraf series 880 CIU Plus via Modbus .TM

For installation and commissioning of the CIU Plus, please refer to therelated installation guide and instruction manual Ensite Pro.

This manual describes the communication between a CIU Plus andhigher layered systems. The communication is based on emulation ofthe Modbus protocol (Gould Modicon Modbus Protocol ReferenceTM

Guide, PI-MBUS-300, Rev. B).

Safety and prevention of damage‘Cautions’ and ‘Notes’ have been used throughout this manual tobring special matters to the immediate attention of the reader.

Legal aspects The information in this instruction manual is copyright property of EnrafB.V., Netherlands.Enraf B.V. disclaims any responsibility for personal injury or damage toequipment caused by:

• Deviation from any of the prescribed procedures;• Execution of activities that are not prescribed;

Additional informationPlease do not hesitate to contact Enraf or its representative if yourequire additional information.

Table of contents

Page 4

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Safety aspects of the CIU Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Personal safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Safety conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Description and operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Default communication settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Read tank data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Write tank data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Tank data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18CIU data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Gauge commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Validity byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Status byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Modbus number representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Scaling and offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Maintenance / trouble shooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Appendix A Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Appendix B Article and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Appendix C Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Introduction


IntroductionThe configuration of the new tank inventory system consists ofmodular parts:• Entis Pro• CIU Plus• CIU Prime• field instrumentation

Entis Pro This system displays calculated data from the CIU Plus. It is aWindows NT or Windows 2000 Professional based program,®

displaying data in windows, boxes, tables, graphs, etc.

CIU Plus This unit calculates volume, standard volume, mass, density, flow rate,etc. It requests data from the CIU Prime and calculates all other data.It presents data to higher layered systems like Entis Pro, SCADA,DCS, ENSITE, etc.

Host ports Up to four RS-232C/RS485 host ports can be installed to interfacehost communication (Modbus) to Entis Pro, SCADA, DCS, ENSITE,etc. For a description of the Modbus protocol, refer to the relatedinstruction manual.

Field ports Two fixed RS-232C/RS-485 field ports interface to a CIU Prime.

Automatic calculation After configuration, the CIU Plus automatically calculates data andstores the information in a database. For a description of theconfiguration and programming, refer to the instruction manual EnsitePro.

CIU Prime This unit is an interface between the field instrumentation andinventory systems. It receives data from the field and converts it todigital signals (Modbus) for systems like CIU Plus, PLC, ENSITE, etc.

Field instrumentationThe instruments in the field collect data like level, temperature, densityand/or pressure. The instruments are based on several principles:mechanical, servo, radar, hydrostatic and capacitive or a combination.The instruments measure the data and transmit it upon request ofhigher layered systems.

Introduction

Page 6

Safety


Do not use the CIU Plus other than originally intended.

Modification to the CIU Plus may only be carried out by authorizedpersonnel.Failure to adhere to this will invalidate the approval certificate.

Take all necessary personal protection measures and apply to thesafety regulations, valid for the working area.

Never start working before the work permit is signed by all parties.

Safety

Safety aspects of the CIU Plus

The protection class for the CIU Plus housing is IP30 (NEMA 1), whichmeans that the CIU Plus can only be installed indoor in an explosionsafe area or in a protective cabinet.

Other environmental parameters are:- ambient temperature: 0...60 °C- relative humidity: 5...90 % (non condensing)- over voltage category: II- pollution degree: II

The host ports of the CIU Plus are galvanically separated. The fieldports of the CIU Plus do not have galvanic separation.

Personal safetyThe technician must have basic technical skills to be able to safelyoperate the equipment and work in accordance with the (local)requirements for electrical equipment.

Safety

Page 8

A Note points out a statement deserving more emphasis than thegeneral text.

A Caution draws attention to an action which may damage (theoperation of) the equipment.

Safety conventions‘Cautions’ and ‘Notes’ have been used throughout this manual tobring special matters to the immediate attention of the reader.

0

1

111

1

1

0

Mains

block

slot

9

slot

8

slot

7

slot

6

slot

5

slot

4

slot

3

slot

2

slot

1

host po

rt 4 rec

eive

host po

rt 3 rec

eive

host po

rt 2 rec

eive

host po

rt 1 rec

eive

field p

ort 2 re

ceive

field p

ort 1 re

ceive

power

alive

host po

rt 2 tra

nsmit

host po

rt 3 tra

nsmit

host po

rt 4 tra

nsmit

host po

rt 1 tra

nsmit

field p

ort 2 t

ransm

it

field p

ort 1 t

ransm

it

Description and operation



DescriptionThe CIU Plus consists of the following parts:- Front panel- Rear connectors- Internal circuitry

Front panel The front panel holds LEDS, indicating power and communication:

Rear connectors The CIU Plus is delivered with two fixed field ports at slots 2 and 3.The lay-out of the other slots is as follows:

Slot Description

1 not used

2 field ports (fixed)3

4 not used

5 Up to four host ports can be installed. These ports can be:6 - RS-232C / RS-485 with modbus communication (IP-7 RS232/485)8

Keyswitch 2(write protect key)

Switch closed (sealable position):- write protection enabled- W&M protection enabled

Switch open (equivalent to ‘no key switch installed’):- write protection disabled- W&M protection disabled

Keyswitch 1(W&M key)


Slot Description

Page 10

Do not re-adjust any setting inside, this will negatively influence theoperation of the CIU Plus.

9 Used when key switches are to be installed:

Internal circuitry The internal circuitry consists of the following parts:- Power supply- Service port- 2 fixed field communication ports- 4 optional host communication ports- Real time clock- Digital inputs (key switches)

OperationThe CIU Plus calculates volume, standard volume, mass, density, flowrate, etc. It requests data from the CIU Prime and calculates all otherdata. It presents data to higher layered systems like Entis Pro,SCADA, DCS, ENSITE, etc.

After configuration, the CIU Plus automatically calculates data andstores the information in a database. The next chapters describe theprogramming of the CIU Plus.

Default communication settingsThe CIU Plus has maximum four optional host ports with followingdefault settings:Interface: RS-232Protocol: ModbusRTU address: 41Baudrate: 19200Parity: OddStop bits: 1

Commissioning


CommissioningThe CIU Plus is a user-configurable multi-processor unit and can betotally programmed at site, or remotely, without opening the CIU Plus.

Commissioning is done in the following steps:

Check installation - Examine the mechanical installation- Examine the electrical installation

Select tools - Use ‘Ensite’ to collect the data from the field instruments- Use ‘Ensite Pro’ to configure the CIU Prime and Plus- Use a spreadsheet program to generate strapping files

Prepare files - Ensite: make a log file of each field instrument- Spreadsheet: make a strapping table for each tank. (The filename shall be ‘<tankname>.TXT’, in which <tankname> isthe name of the tank. The next page shows an example of what the file should look like)

Program configuration - Ensite Pro: configure data inputs (use log files from Ensite)- Ensite Pro: configure tanks (use strap files from spreadsheet)- Ensite Pro: configure CIU Primes- Ensite Pro: configure CIU Plus’s- Ensite Pro: link data inputs, tanks, CIU Primes and CIU Plus’s

Download configuration - Ensite Pro: set communication parameters- Ensite Pro: select physical communication path- Ensite Pro: download all CIU Primes- Ensite Pro: download all CIU Plus’s

Commissioning

Page 12

All text, ‘=’-signs and numbers must be separated by one or morespaces or Tabs.Digit separators are not allowed.Decimal separator must be the same as set in regional settings of yourwindows system (and Ensite Pro).

Tank strap fileExample strap file ‘TNK-03.TXT’:

[TANK_ID] [Tank identification]Name = TNK-03 ASCII string: the name of the tankDate = 15-Feb-99 ASCII string: the date this file is generatedTime = 12:34 ASCII string: the time this file is generatedLevel = 2 1 = m xxx.xxxx

2 = mm xxxxxx.x3 = ft xxx.xxxx4 = in xxxx.xxx5 = in/16 xxxxxx.x

Volume = 51 50 = l xxxxxxxxx51 = m xxxxxx.xxx3

52 = USgal xxxxxxxx.x53 = bbls xxxxxxx.xx

Ullage = 0 0 = innage1 = ullage

Straps = 6 Number of straps

[STRAPS] [Strap data (level vs. volume)]1 = -233.0 0.000 first (and lowest) strap2 = 100.0 0.213 .3 = 1006.3 5631.000 .4 = 2001.7 10732.000 .5 = 10032.0 52721.000 .6 = 20531.4 98321.000 last (and highest) strap

[EOF] [End Of File]

Read tank data


Read tank dataData can be read from the CIU Plus.Statusses can be read via discrete inputs.Data can be read via holding registers and input registers.See manual ´Instruction manual Modbus Protocol´ chapter EnrafTM

implementation.

General Entities Some general CIU Plus entities are available to the user via modbusregisters. These entities are available on fixed modbus addresses.

Column name DescriptionName The name of the entity. For a detailed description,

refer to Appendix A, Glossary.ID The unique identifier of the entityDimension Category of dimensional units. For a detailed

description, refer to chapter ‘Dimensions’.

Name ID Comment(s)Year (real-time clock) 521 Time (YYYY)Month (real-time clock) 522 Time (MM)Day of month (real-time clock) 523 Time (dd)Hour (real-time clock) 524 Time (h)Minute (real-time clock) 525 Time (min)Seconds (real-time clock) 526 Time (s)DayLightSaving (real-time clock) 527 0 = off; 1 = on

Available tank entities The CIU Plus is delivered with a pre-programmed Tank Record lay-out(list of tank entities) for communication with Entis Pro. The lay-out forcommunication with Entis Pro is fixed, however it is possible to alterthe lay-out to fit other requirements.A selection can be made which data must be presented in the userdefined tank data area. This because of the lot of information whichcan be retrieved.One tank data reply packet is selected which is used for all tanksavailable to the modbus host.The sequence how the tanks are organized in the user definedmodbus map is programmable.

Read tank data

Page 14

There are two methods possible to organize the user defined modbusmemory map:1. Tank oriented.Data in the modbus memory map is grouped per tank.Start address of memory map is programmable. Default start addressis 0000.The start address-interval between the tank records is programmable.2. Data oriented.Data in the modbus memory map is grouped per selected entity.Start address of memory map is programmable. Default start addressis 0000.

The table below displays all entities, available to the user.

Column name DescriptionName The name of the entity. For a detailed description,

refer to Appendix A, Glossary.ID The unique identifier of the entityDimension Category of dimensional units. For a detailed

description, refer to chapter ‘Dimensions’.

Name ID DimensionTankName 1 Text (ASCII or Unicode)TankStatus 2 Bit codedMovingStatus 3 IndexTankType 4 Bit codedGaugeType 5 NodimGaugeStatus 6 IndexTempElementType 8 IndexHotStandbyStatus 9 Bit codedCommStatus 10 Bit codedTankShape 16 IndexShellCapacity 17 VolumeLowTOV 18 VolumeHighTOV 19 VolumeHighLevel 20 LevelProductName 21 Text (ASCII or Unicode)GSVCalcType 22 IndexProductCode 23 IndexVolumeCorrections 24 IndexMassCalcType 25 Bit codedProductTRef 26 TemperatureDRef 30 DensityDRefStatus 31 StatusSedAndWater 32 PercentageProductTC 33 Temperature coefficientProductTCStatus 34 StatusLiqVolRatio 35 NodimGaugeLevelAlarms 36 Bit codedExternalContacts 37 Bit codedDisplacerPosition 38 Level

Read tank data

Name ID Dimension


DisplacerPositionStatus 39 StatusProductLevel 40 LevelProductLevelStatus 41 StatusWaterLevel 42 LevelWaterLevelStatus 43 StatusProductTemp 44 TemperatureProductTempStatus 45 StatusVapRoomTemp 46 TemperatureVapRoomTempStatus 47 StatusVapRoomPress 48 PressureVapRoomPressStatus 49 StatusDObs 50 DensityDObsStatus 51 StatusForegroundTimeStamp 52 Absolute timeBackgroundTimeStamp 53 Absolute timeTOV 54 VolumeTOVStatus 55 StatusWaterVol 56 VolumeWaterVolStatus 57 StatusGOV 58 VolumeGOVStatus 59 StatusGSV 60 VolumeGSVStatus 61 StatusNSV 62 VolumeNSVStatus 63 StatusLiqInVap 64 VolumeLiqInVapStatus 65 StatusTGSV 66 VolumeTGSVStatus 67 StatusMassLiq 68 MassMassLiqStatus 69 StatusMassVap 70 MassMassVapStatus 71 StatusTotalMass 72 MassTotalMassStatus 73 StatusFlowTOV 74 FlowAvailableRoom 75 VolumeAvailableTOV 76 VolumeVerificationSignature 77 NodimConfigurationStatus 78 Bit codedMolarWeight 79 Molar Weight valueAutomaticMeasurableValues 80 Bit codedHydroMeterCorr 88 NodimTankShellTRef 90 TemperatureTankShellExpansionCoefficient 91 TankShellCoefficientTankAirDensity 92 DensityVapRoom 93 VolumeTankConfigurationCRC 94 NodimCIUPrimeGeneralConfiguratonCRC 95 NodimCIUPlusGeneralConfigurationCRC 96 Nodim

Read tank data

Name ID Dimension

Page 16

LowLevel 97 LevelFlowStatus 99 StatusAvailableRoomStatus 100 StatusAvailableTOVStatus 101 StatusVapRoomStatus 102 StatusAmbientTemperature 103 TemperatureAmbientTemperatureStatus 104 StatusCIUPlusTankID 105 NodimCIUPrimeTankID 106 NodimCTSh 107 CTShCTShStatus 108 StatusInsulationFactor 109 Insulation FactorTObs 118 TemperatureTObsStatus 119 StatusVolumeCorrectionFactor 124 VCFVolumeCorrectionFactorStatus 125 StatusTemperatureCorrectionFactor 126 TCFTemperatureCorrectionFactorStatus 127 StatusDensityCorrectionFactor 128 DCFDensityCorrectionFactorStatus 129 StatusTankStatusStatus 131 NodimMovingStatusStatus 132 NodimTankTypeStatus 133 NodimShellCapacityStatus 134 NodimLowTOVStatus 135 NodimHighTOVStatus 136 NodimProductNameStatus 137 NodimGSVCalcTypeStatus 138 NodimProductCodeStatus 139 NodimVolumeCorrectionStatus 140 NodimMassCalcTypeStatus 141 NodimProductTRefStatus 142 NodimSedAndWaterStatus 143 NodimLiqVolRatioStatus 144 NodimMolarWeightStatus 145 NodimAutomaticMeasurableValuesStatus 146 NodimHydroMeterCorrStatus 154 NodimTankTRefStatus 155 StatusTankTCStatus 156 NodimAirDensityStatus 157 StatusInsulationFactorStatus 158 NodimAlarms* 200 Nodim

(gauge level alarms) (36) (bit coded)(external contacts) (37) (bit coded)

Dynamic tank status* 201 Nodim(gauge status) (6) (index)(moving status) (3) (index)(tank status) (2) (bit coded)

Read tank data

Name ID Dimension


A * behind the entity name indicates that this is a combined entity. Theentities requested with this combined entity are in the above tablewritten between brackets. Entities available in a combined entity arenot available as individual entity.

A more detailed description of all entities can be found in Appendix A,Glossary.

Static tank definitions* 202 Nodim(tank type) (4) (bit coded)(tank shape) (16) (index)

Field instrument details* 203 Nodim(gauge type) (5) (nodim)(temperature element type) (8) (index)

Combined volume corrections* 204 Nodim(GSV calculation type) (22) (index)(product code) (23) (index)

Mass and volume corrections* 205 Nodim(volume corrections) (24) (index)(mass calculation type) (25) (bit coded)

Comm. and conf. status* 206 Nodim(configuration status) (78) (bit coded)(hot standby status) (9) (bit coded)(comm status) (10) (bit coded)

Write tank data

Page 18

Write tank data

Please refer to the ’Instruction manual Modbus Protocol’ chapterTM

Enraf implementation

Tank dataEntities can be (over-)written using direct overwrite mechanism.On the same modbus address as where data is read this data can beoverwritten.The following entities can be overwritten:

Name ID DimensionProductName 21 Text (ASCII or Unicode)GSVCalcType 22 IndexProductCode 23 IndexVolumeCorrections 24 IndexDRef 30 DensitySedAndWater 32 PercentageProductTC 33 Temperature CoefficientLiqVolRatio 35 NodimProductLevel 40 LevelWaterLevel 42 LevelProductTemp 44 TemperatureVapRoomTemp 46 TemperatureVapRoomPress 48 PressureDObs 50 DensityMolarWeight 79 Molar Weight valueHydroMeterCorr 88 NodimAmbientTemperature 103 TemperatureTObs 118 TemperatureVolumeCorrectionFactor 124 VCFTemperatureCorrectionFactor 126 TCFDensityCorrectionFactor 128 DCF

E.g. in case gas temperature for a tank is read on address 0034. Thenthe gas temperature for the related tank can be overwritten by a hoston address 0034 by using the Pre-set single register command.Provided that the gas temperature is not automatically measured theoverwritten value is used for calculations.

Write tank data


CIU dataThe internal date and time can be overwritten by writing holdingregisters.

Gauge commandsGauge commands can be issued with the ‘Force single coil’ command.

Dimensions

Page 20

DimensionsThe CIU Plus has a specified set of dimensions. The dimension sethas to be the same for the whole combination of CIU Prime, CIU Plusand Entis Pro. The used dimension sign and scaling factor are set-upparameters and will be entered using Ensite Pro.

Unit Format Minimum MaximumLevel m ±xxx.xxxx -999.9999 +999.9999

mm ±xxxxxx.x -999999.9 +999999.9ft ±xxx.xxxx -999.9999 +999.9999in ±xxxx.xxx -9999.999 +9999.999in/16 ±xxxxxx.x -999999.9 +999999.9fis ±xxx’xx”xx -999'11"15 +999'11"15in/256 ±xx’xx”xxx -99'11"255 +99'11"255

Temperature °C ±xxx.xx -300.00 +300.00°F ±xxx.xx -400.00 +572.00

Pressure kgf/cm +xx.xxx +00.000 +65.5352

Pa +xxxxxxx +0000000 +6553500kPa +xxxx.x +0000.0 +6553.5psi (lbf/in ) +xxx.xx +000.00 +655.352

Volume l +xxxxxxxxx +000000000 +999999999m +xxxxxx.xxx +000000.000 +999999.9993

USgal +xxxxxxxx.x +00000000.0 +99999999.9bbls +xxxxxx.xxx +000000.000 +999999.999

Density kg/m +xxxx.xx +0000.00 +9999.993

°API ±xxx.xx -050.00 +600.00lbs/ft +xxx.xxx +000.000 +999.9993

dens60/60 +x.xxxxx +0.00000 +9.99999lbs/USgal +xx.xxxx +00.0000 +99.9999

Flow m /min ±xxxx.xx -9999.99 +9999.993

m /h ±xxxxx.x -99999.9 +99999.93

l/min ±xxxxxx -999999 +999999l/h ±xxxxxx -999999 +999999bbls/min ±xxxx.xx -9999.99 +9999.99bbls/h ±xxxxx.x -99999.9 +99999.9USgal/min ±xxxxxx -999999 +999999USgal/h ±xxxxxx -999999 +999999

Acceleration m/s +xx.xxxxx +00.00000 +99.999992

Mass kg +xxxxxxxxx +000000000 +999999999metric ton +xxxxxx.xxx +000000.000 +999999.999USton +xxxxxx.xxx +000000.000 +999999.999lbs +xxxxxxxxxx +0000000000 +999999999long ton +xxxxxx.xxx +000000.000 +999999.999

Dimensions

Unit Format Minimum Maximum


Time s xx 00 59min xx 00 59h xx 00 23AbsTime xx:xx:xx 00:00:00 23:59:59dd xx 01 31MM xx 01 12YYYY xxxxx 00000 16383saving active x 0 1

Text ASCII 1 char = 1 byteUnicode 1 char = 2 bytes

Molar Value kg/kmol +xx.xxxx +00.0000 +99.9999

Percentage % +xx.xx +00.00 +99.99

TempCoefficient 10 /°C +xxxxx.xxx +00000.000 +99999.999-7

10 /°F +xxxxx.xxx +00000.000 +99999.999-7

Nodim no dim., unsigned value 0 2#bits

Bit coded separate bits 0 2#bits

Index row number in table 0 2#bits

Status see chapter ‘Statuses’

VCF - +x.xxxxx +0.00000 +9.99999

Statuses

Page 22

StatusesEach measured and each calculated entity in the CIU Plus contains a16 bits status register.

High byte The high byte, the validity byte, is used to indicate if the data of thisentity is available (valid) and, if not valid, to indicate why the data is notavailable (invalid).

Low byte The low byte is used to indicate the status of the data.

Validity byteThe data validity byte is a hexadecimal number.If the validity byte is >=80 , the related data is invalid. If the data ofHEX

an entity is invalid, all derived data shows the same code in its datavalidity byte and the status indicates how the data field should bedisplayed (‘FFFF’, blanks, etc.).If the validity byte is <80 , the related data is valid. Then additionalHEX

information is given.

Some examples are listed below. If the complete list is requiredcontact Enraf BV.

Validity Description Actionbyte0x00 Valid data -0x6F Reduced accuracy in -

ambient temperature0x70 Stored because of -

water dip

0x81 No data available For derived data it is necessary tocheck all input parameters for thiscode

0x82 Killed data For derived data it is necessary tocheck all input parameters for thiscode

0xA4 General conversion Check input and output valueerror dimensions

.

.

.

Statuses


Validity < 80 represents valid data.HEX

Suggested characters to display depending on the contents of thestatus byte:- uncalibrated = ‘#’- manual = ‘&’- stored = ‘S’- reduced accuracy = ‘?’

The data status basically exists of two parts which should be displayedin tabular data in two separate columns:- bit 7, which indicates whether the data is calibrated or not- bit 6...0, which (in decreasing priority) tell something about thephysical status of the data.

Validity >= 80 represents invalid data.HEX

Suggested characters to display: ‘FFFF’ or ‘blanks’

Status byteThe data status byte is bit coded. The meaning of the bits depends onthe validity byte (<80 or >=80 )HEX HEX

Status Validity < 80 Validity >= 80Bit Description (bit set) Description (bit set)

HEX HEX

7 Uncalibrated Generate Alarm6 Manual No Data Available5 Killed4 Over Range3 Under Range2 Un-initialised1 Stored0 Reduced Accuracy

Modbus number representation

Page 24

Modbus number representationThe CIU Plus will be delivered with a pre-programmed Tank Recordlay-out for communication with Entis Pro. The lay-out forcommunication with Entis Pro is fixed. However in case ofcommunication to another system the customer is able to alter the lay-out to fit his own requirements.

This chapter describes the way data can be represented in themodbus registers:

ID Data type Nr. of Descriptionregisters

used0 Not a number 1...5 Data is represented according the

(just data) item definition (status, index, bitcoded, etc.)

15 ASCII string 1...10 Data represents a string of two ASCIIcharacters per register. Emptyregisters contain ‘0'.

25 Unicode 1...10 Data represents a string of onecharacters Unicode character per register.

Empty registers contain ‘0'.40 16 bit 1 Data is transmitted as contents of the

unsigned register. Value FFFF (65535 ) isinteger seen as failure

HEX DEC

41 16 bit signed 1 Represented in 2's complement.integer bit 15: sign

bit 14...0: datae.g. 0000 = 0HEX

e.g. 0001 = 1HEX

e.g. 7FFF = failureHEX

e.g. 8000 = -32768HEX

e.g. FFFF = -1HEX

42 16 bit 1 Mostly used for scaling and offset.decimal float bit 15: sign, 0 = pos., 1 = neg.

bit 14...11: exponent power of 10bit 10...0: mantissae.g. 0000 = 0HEX

e.g. 2001 = 0.001HEX

e.g. 4801 = 100HEX

e.g. 5A16 = 5340000HEX

e.g. 73E8 = 1·10HEX10

e.g. 7BFF = failureHEX

e.g. 9001 = -1HEX

43 12 bit signed 1 bit 15...13: if not 000 see further:bit 12: sign, 0 = pos., 1 = neg.bit 11...00: analogue valuee.g. EF FF = invalidHEX



used


51 32 bit signed 2 Binary data, covering data rangeinteger between -2147483647 and

+2147483647e.g. 00 00 00 00 = 0HEX

e.g. 00 00 00 01 = 1HEX

e.g. 7F FF FF FF = invalidHEX

e.g. FF FF FF FF = -1HEX

52 32 bit floating 2 Data in two registers. Data is codedpoint into four bytes floating point, covering

data range between-3.402823·10 and +3.402823·1038 38

byte 1: sign + 7 bit exponentbyte 2: 8 bit exponent + 7 bitth

mantissabyte 3: 8 bits of mantissabyte 4: rest of mantissae.g. 40 80 00 00 = 4HEX

e.g. 40 A0 00 00 = 5HEX

e.g. 7F 80 00 00 = invalidHEX

53 32 bit floating 2 Data in two registers. Data is codedpoint into four bytes floating point, covering(swapped) data range between

-3.402823·10 and +3.402823·1038 38

byte 1: 8 bits of mantissabyte 2: rest of mantissabyte 3: sign + 7 bit exponentbyte 4: 8 bit exponent + 7 bitth

mantissae.g. 00 00 40 80 = 4HEX

e.g. 00 00 40 A0 = 5HEX

e.g. 00 00 7F 80 = invalidHEX

60 Unsigned 2 1 register = integer valuedouble 2 register = fraction*1register e.g. 19 70 00 00 = 6512

st

nd

HEX

Value FFFF FFFF is seen asHEX

failure61 Unsigned 2 1 register = integer value

double 2 register = fraction*10register e.g. 19 70 00 06 = 6512.6

st

nd

HEX



double 2 register = fraction*100register e.g. 19 70 00 43 = 6512.67

st

nd

HEX


failure



used

Page 26

ID53,60,61,62,63 and 64 are available in CIU Plus firmware version1.003 and higher.In CIU Plus firmware versions up to 1.002 ID50 was available. ID50 isidentical to ID64 in CIU Plus firmware versions 1.003 and higher.

63 Unsigned 2 1 register = integer valuedouble 2 register = fraction*1000register e.g. 19 70 02 A6 = 6512.678

st

nd

HEX



double 2 register = fraction*10000register e.g. 19 70 1A 85 = 6512.6789

st

nd

HEX


failure

Scaling and offsetScaling and offset are defined as follows:• The value of the data that will be available for the user is

calculated as follows:Register value = (data * scaling) + offset

• Per selected data entity a scaling and offset value can beentered. These entered values are used for calculating theregister value.

• The original data measured or calculated by the CIU Plus isavailable in the dimension and resolution as defined by thedimension table.

• This data is represented in the requested representation in theoutput registers.



Example 1: Level : 22316.2 mmDimension : mmScaling : 0.01Offset : 0Data type : unsigned double register (ID=63)Calculation : (22316.2 * 0.01) + 0 = 223.162Data in reg. 1 : 223DEC

Data in reg. 2 : 162DEC

Example 2: Temperature : -8.23 °CDimension : °CScaling : 10Offset : 100Data type : 16 bit unsigned integer (ID=40)Calculation : (-8.23 * 10) + 100 = 17.7Data in reg. : 18 (rounded)

Example 3: Volume : 87654.321 m3Dimension : m3Scaling : 0.1Offset : 0Data type : unsigned double register (ID=64)Calculation: : (87654.321 * 0.1) + 0 = 8765.4321Data in reg. 1 : 8765DEC

Data in reg. 2 : 4321DEC

Example 4: Mass : 87654321 kgDimension : kgScaling : 1Offset : 0Data type : 32 bit signed integer (ID=52)Calculation : (87654321 * 1) + 0 = 87654321Data in reg. : 05 39 7F B1HEX

Maintenance / trouble shooting

Page 28

Cleaning of the housing of the CIU Plus should be done with a moistcloth only.

After switching on the CIU Plus it will take approximately 1 minutebefore it will be able to communicate via the host ports.

The ´Alive´ LED (green LED under the red power LED) gives anindication if the CIU Plus is in healthy condition.In case healthy the LED is on for 2 seconds and off for 1 second etc.Note that the healthy flash rhythm is different from the flash rhythm ofthe Alive LED on the CIU Prime.

Maintenance / trouble shooting

Maintenance The CIU Plus requires neither preventive nor periodical maintenance.

Trouble shooting If something appears to be wrong, proceed as follows:1. Check mains voltage; OK: yes -> step 2

no -> check/replacefuses

2. Check cabling: not connected -> connectconnected -> step 3

3. Check communication: yes -> finishno -> step 4

4. Start ‘Ensite Pro’5. Go to ‘Diagnostic data’6. Press the ‘Update’-button to have the current values.7. Press the ‘Print...’-button to print the data.8. Contact Enraf with diagnostic data.

Appendix


Because of the representation as combined entity the length of eachindividual entity (#36 and #37) is fixed to 8 bits.

Bits 14 and 15 are for internal use of the CIU Plus.The length is fixed to 16 bits.

Appendix A Glossary

A

Alarms ID#200; Combined entity which represents the ExternalContacts(ID#37) and the GaugeLevelAlarms (ID#36).High byte ID#37; Indicates (bit coded) the ExternalContacts:- Bit 0 = 1 External contact 1 active- Bit 1 = 1 External contact 2 active- Bit 2 = 1 External contact failure- Bit 3 = 1 External contact not available in this instrumentLow byte ID#36; Indicates (bit coded) GaugeLevelAlarms:- Bit 0 = 1 Low Level alarm tripped- Bit 1 = 1 High Level alarm tripped- Bit 2 = 1 Alarm failure- Bit 3 = 1 Gauge alarms not available in this instrument

AmbientTemperature ID#103; Value of the tank’s ambient temperature.AmbientTemperatureStatus ID#104; Status of ID#103, AmbientTemperature.AutomaticMeasurableValues

ID#80; Indicates (bit coded) which values can be automaticallymeasured (this doesn't necessarily mean that they are actuallymeasured). Bit n = 1: value can be measured automatically:- Bit 0 = 1 Level [ID#38, ID#40]- Bit 1 = 1 Temperature [ID#44]- Bit 2 = 1 Water level [ID#42]- Bit 3 = 1 Density [ID#50]- Bit 4 = 1 Vapour temperature [ID#46]- Bit 5 = 1 Vapour pressure [ID#48]- Bit 6 = 1 Ambient Temperature [ID#103]- Bit 7 = 1 Dummy scan (now used for FDI scan)- Bit 14 ProductTC calc. mode: 0 = manual, 1 = calculated- Bit 15 VCF calc. mode: 0 = manual, 1 = calculated

AutomaticMeasurableValuesStatusID#146; Status of ID#80, AutomaticMeasurableValues.

AvailableRoom ID#75; Value of the tank’s spare capacity.AvailableRoomStatus ID#100; Status of ID#75, AvailableRoom.AvailableTOV ID#76; Value of the available product volume.AvailableTOVStatus ID#101; Status of ID#76, AvailableTOV.

Appendix

Page 30

Value FFFF: tank/port not used.

Value FFFF: tank/port not used.

Because of the representation as combined entity the useful length isfixed to 3 bits.

Because of the representation as combined entity the length is fixed to8 bits.

BBackgroundTimeStamp ID#53; (Absolute) time when, in the background scan, the most recent

item was scanned.CCIUPlusGeneralConfigurationCRC

ID#95; Checksum, calculated over general CIU Plus configurationparameters (for W&M purposes).

CIUPlusTankID ID#106; Holds (bit coded) the CIU Plus tank identifier:- Bit 0..7 Tank number between 1 and 50- Bit 8..15 RTU Address of the CIU Plus host port

CIUPrimeGeneralConfigurationCRCID#95; Checksum, calculated over general CIU Prime configurationparameters (for W&M purposes).

CIUPrimeTankID ID#106; Holds (bit coded) the CIU Prime tank identifier:- Bit 0..7 Tank number between 1 and 50- Bit 8..15 RTU Address of the CIU Prime host port

CommStatus ID#10; Indicates (bit coded) the communication status:- Bit 0 = 1 CIU Prime to Gauge comm. OK. (Future) (Bit 0 does

not change when bit 1=0)- Bit 1 = 1 CIU Plus to (active or passive) CIU Prime comm. OK- Bit 2 = 1 FieldPort on (active) CIU Prime OK

ConfigurationStatus ID#78; Indicates (bit coded) the CIU and tank configuration status:- Bit 0 = 1 Gauge configuration mismatch (Future)- Bit 1 = 1 CIU Prime general configuration mismatch- Bit 2 = 1 CIU Prime tank configuration mismatch- Bit 3 = 1 CIU Plus general configuration mismatch- Bit 4 = 1 CIU Plus tank configuration mismatch for this tank- Bit 5 = 1 Ensite Pro general configuration mismatch- Bit 6 = 1 Ensite Pro tank configuration mismatch- Bit 7 = 1 CIU Prime record contains invalid verification

signature

Appendix



These 2 bytes are configured in the CIU Prime by Ensite Pro. The dataextraction of Ensite Pro takes care of the configuration of this entity.

CorrectionFactor ID#124; Value of the VCF.CorrectionFactorStatus ID#125; Status of ID#124, CorrectionFactor.CTSh ID#107; The correction for the expansion of the shell.CTShStatus ID#108; Status of ID#107, CTSh.

DDCF ID#128; Value of the DCF.DCFStatus ID#129; Status of ID#129, DCF.DisplacerPosition ID#38; Value of the physical servo displacer position.DisplacerPositionStatus ID#39; Status of ID#38, DisplacerPosition.DObs ID#50; Value of the product density.DObsStatus ID#51; Status of ID#50, DObs.DRef ID#30; Value of the reference density.DRefStatus ID#31; Status of ID#30, DRef.

EExternalContacts ID#37; Indicates (bit coded) the external contacts:

- Bit 0 = 1 External contact 1 active- Bit 1 = 1 External contact 2 active- Bit 2 = 1 External contact failure- Bit 3 = 1 External contact not available in this instrument

FFlowTOV ID#74; Value of the total product volume (TOV) per time unit.FlowStatus ID#99; Status of ID#74, FlowTOV.ForegroundTimeStamp ID#52; (Absolute) time when, in the foreground scan, the most recent

item was scanned.GGaugeCommands ID#7; Indicates (bit coded) the allowed gauge commands:

- Bit 0 = 1 Test not allowed- Bit 1 = 1 Lock test not allowed- Bit 2 = 1 Block not allowed- Bit 3 = 1 Calibration not allowed- Bit 4 = 1 Alarm test not allowed- Bit 5 = 1 Tank profile not allowed- Bit 6 = 1 Interface profile not allowed- Bit 7 = 1 Water dip not allowed- Bit 8 = 1 Reset Gauge not allowed- Bit 9 = 1 Interface 2 command not allowed

Appendix

Page 32


Statuses 2048 and 2304 can only be detected when the ZLQ requestis used for the level measurement.Because of the representation as combined entity the length is fixed to16 bits.


GaugeLevelAlarms ID#36; Indicates (bit coded in the high order byte) gauge level alarms(firmware version >2.000):- Bit 8 = 1 Low Level alarm tripped- Bit 9 = 1 High Level alarm tripped- Bit 10 = 1 Alarm failure- Bit 11 = 1 Gauge alarms not available in this instrument

GaugeStatus ID#6; Indicates (in the high order byte) the (servo) gauge status.Following modbus values represents a status (firmware version>2.000):- 0 = Level gauge is measuring level- 256 = Level gauge is in test- 512 = Level gauge is in lock test- 768 = Level gauge is blocked- 1024 = Level gauge is busy with a density profile measurement- 1280 = Level gauge is searching water level- 1536 = Level gauge end switch reached- 2560 = Level gauge has found water level and is measuring it- 65280 = Level gauge is in failure

GaugeType ID#5; Type of level measuring instrument. To get the instrument typenumber, add 800 (decimal) to the GaugeType value. Example: Gaugetype value = 54 -> instrument 854. This entity is configured by EnsitePro.

GOV ID#58; Value of the Gross Observed Volume.GOVStatus ID#59; Status of ID#58, GOV.GSV ID#60; Value of the Gross Standard Volume.GSVCalcType ID#22; Indicates (indexed) the GSV calculation method:

- 0 = No GSV calculation- 1 = VCF/Dref calc. acc. to ASTM D1250 (1980) table 6/5- 2 = VCF/Dref calc. acc. to ASTM D1250 (1980) table 24/23- 3 = VCF/Dref calc. acc. to ASTM D1250 (1980) table 54/53- 4 = DCF calculation- 5 = TCF calculation

Appendix


If index 0 = 0, Dref is not calculated.Because of the representation as combined entity the length is fixed to8 bits.

Because of the representation as combined entity the useful length isfixed to 5 bits.

- 6 = VCF calc. acc. to ASTM D4311 (1990) table 1- 7 = VCF calc. acc. to ASTM D4311 (1990) table 2- 8 = M - manual entry of VCF- 9 = VCF calc. acc. to ASTM D4311 (1996) table 1 (implemented

using formula)- 100...255 GSV calculation according defined chemical formulas

(future implementation)

GSVCalcTypeStatus ID#138; Status of ID#22, GSVCalcType.GSVStatus ID#61; Status of ID#60, GSV.

HHighLevel ID#20; Level corresponds to HighTOV (for graphical purposes only).HighTOV ID#19; The maximum volume the tank may safe contain.HighTOVStatus ID#136; Status of ID#19, HighTOV.HotStandbyStatus ID#9; Indicates (bit coded) the hot standby status:

- Bit 0 = 1 Primary CIU Prime is scanning this tank- Bit 1 = 1 Primary CIU Prime is available for this tank- Bit 2 = 1 Secondary CIU Prime is scanning this tank- Bit 3 = 1 Secondary CIU Prime is available for this tank- Bit 4 = 1 CIU Plus is passive member of a Hot-Standby pair

HydroMeterCorr ID#88; ‘0' is false, ‘1' means true.HydroMeterCorrStatus ID#154; Status of ID#88, HydroMeterCorr.

IInsulationFactor ID#109; The insulation factor of the tank shell.InsulationFactorStatus ID#158; Status of ID#109, InsulationFactor.

LLiqInVap ID#64; Value of the vapour volume in the tank, if it was ‘liquefied’.LiqInVapStatus ID#65; Status of ID#64, LiqInVap.LiqVolRatio ID#35; Factor by which a product in gaseous form reduces in volume

when converted to a liquid.LiqVolRatioStatus ID#144; Status of ID#35, LiqVolRatio.LowLevel ID#97; Level corresponds to LowTOV (for graphical purposes only).LowTOV ID#18; The minimal volume under which no pumping is allowed.LowTOVStatus ID#135; Status of ID#18, LowTOV.

Appendix

Page 34



To disable the range checking, add 128 to above numbers. Because of the representation as combined entity the length is fixed to8 bits.

MMassCalcType ID#25; Indicates (bit coded) the method of mass calculation:

- Bit 0 = 1 Liquid mass directly calculated from GOV * DObs- Bit 1 = 1 Liquid mass calculated from NSV- Bit 2 = 1 Liquid mass calculated in air- Bit 3 = 1 Vapour mass calculated in air

MassCalcTypeStatus ID#141; Status of ID#25, MassCalcType.MassLiq ID#68; Value of the product volume weight.MassLiqStatus ID#69; Status of ID#68, MassLiq.MassVap ID#70; Value of the vapour volume weight.MassVapStatus ID#71; Status of ID#70, MassVap.MolarWeight ID#79; Molar weight of the gas composition.MolarWeightStatus ID#145; Status of ID#79, MolarWeight.MovingStatus ID#3; Indicates (indexed) the level moving status:

- 0 = Tank level is stable- 1 = Tank level is moving up- 2 = Tank level is moving down- 3 = No valid movement status can be detected (e.g. manual level)

MovingStatusStatus ID#132; Status of ID#3, MovingStatus.

NNSV ID#62; Value of the Net Standard Volume.NSVStatus ID#63; Status of ID#62, NSV.

PProductCode ID#23; Indicates (indexed) the product code:

- 0 = Not applicable- 1 = A (use subsection A of the table specified in ID#22)- 2 = B (use subsection B of the table specified in ID#22)- 3 = C (use subsection C of the table specified in ID#22)- 4 = D (use subsection D of the table specified in ID#22)- 5 = E (use subsection E of the table specified in ID#22)

Appendix


These values are used to display a picture of the tank by Entis Pro orScada systems.Because of the representation as combined entity the length is fixed to8 bits.

ProductCodeStatus ID#139; Status of ID#23, ProductCode.ProductLevel ID#40; Value of the product level.ProductLevelStatus ID#41; Status of ID#40, ProductLevel.ProductName ID#21; 20 characters ASCII or 10 characters UNICODE.ProductNameStatus ID#137; Status of ID#21, ProductName.ProductTC ID#33; Value of the product temperature coefficient.ProductTCStatus ID#34; Status of ID#33, ProductTC.ProductTemp ID#44; Value of the product temperature.ProductTempStatus ID#45; Status of ID#44, ProductTemp.ProductTRef ID#26; Value of the product reference temperature.ProductTRefStatus ID#142; Status of ID#26, ProductTRef.

SSedAndWater ID#32; Volume of emulsified water in the product. The absolute

volume is calculated from the sediment and water percentage (S&W%)and is used when calculating NSV. S&W% is a manual entry.

SedAndWaterStatus ID#143; Status of ID#32, SedAndWater.ShellCapacity ID#17; Value of the tank shell volume (used for gas calculations).ShellCapacityStatus ID#134; Status of ID#17, ShellCapacity.

TTankConfigurationCRC ID#94; Checksum, calculated over tank related configuration

parameters by the CIU Plus (for W&M purposes).TankName ID#1; 10 characters ASCII or 5 characters Unicode.TankNameStatus ID#130; Status of ID#1, TankName.TankShape ID#16; Indicates (indexed) the shape of the tank:

- 0 = No shape defined- 1 = Cylindrical fixed roof- 2 = Cylindrical with floating roof- 3 = Cylindrical with internal floater- 4 = Spherical tank- 5 = Bullet- 6 = Underground bullet- 7 = Irregular cavern- 8...99 Reserved (future)- 100...255 Free configurable by the user.

Appendix

Page 36

Default: 6 (bit 2+3). Because of the representation as combined entitythe length is fixed to 4 bits.



TankStatus ID#2; Indicates (bit coded) the status of the tank:- Bit 0 = 1 Tank shell is calibrated by W&M (Treated as General

Tank calibrated Flag)- Bit 1 = 1 Maintenance (future)- Bit 2 = 1 Tank is disabled- Bit 3 = 1 Tank is not available

TankStatusStatus ID#131; Status of ID#2, TankStatus.TankType ID#4; Indicates (bit coded) the type of the tank:

- Bit 0 = 1 Ullage if bit is set, otherwise Innage- Bit 1 = 1 WAP tank (Water Above Product) (future)- Bit 2 = 1 Liquid mass calculated in air- Bit 3 = 1 Vapour mass calculated in air- Bit 4 = 1 HIMS calculation not allowed. If bit is set then mass

may NOT be calculated from GOV * Dobs.

TankTypeStatus ID#133; Status of ID#4, TankType.TCF ID#126; Value of the TCF.TCFStatus ID#127; Status of ID#126, TCF.TempElementType ID#8; Indicates (indexed) the type of temperature element:

- 0 = No element available- 1 = MRT- 2 = MRT with bottom spot- 3 = MRT with bottom and top spot- 4 = One Spot element- 5 = Two spot elements- 8 = MTT

TGSV ID#66; Value of the Total Gross Standard Volume.TGSVStatus ID#67; Status of ID#66, TGSV.TotalMass ID#72; Value of the product plus vapour volume weight.TotalMassStatus ID#73; Status of ID#72, TotalMass.TObs ID#118; Value of the observed temperature.TObsStatus ID#119; Status of ID#118, TObs.TOV ID#54; Value of the Total Observed Volume.TOVStatus ID#55; Status of ID#54, TOV.

Appendix


*) Liquid Mass calculated from GSV*Dref or Dobs*TOV Vapour Mass = Not valid**) Liquid Mass calculated from NSV Vapour Mass = Not valid***) Liquid Mass calculated from GSV*Dref or Dobs*TOV Vapour Mass = According vapour calculationsBecause of the representation as combined entity the length is fixed to8 bits.

VVapRoom ID#93; Vapour room.VapRoomPress ID#48; Value of the product vapour pressure.VapRoomPressStatus ID#49; Status of ID#48, VapRoomPress.VapRoomStatus ID#102; Status of ID#93, VapRoom.VapRoomTemp ID#46; Value of the product vapour temperature.VapRoomTempStatus ID#47; Status of ID#46, VapRoomTemp.VerificationSignature ID#77; Calculated over all entities in the default tank record. The

patented calculation algorithm verifies the contents of the transmittedtank records.

VolumeCorrections ID#24; Indicates (indexed) the volume correction method:- 0 = NONE *)- 1 = S&W correction applied **)- 2 = Vap. calc. acc. Liq/Vol Ratio ISO/TC28/SC 3 N ***)- 3 = Vap. calc. acc. Molar Method acc. to ISO/TC28/SC 3 N ***)- 4 = Vap. calc. acc. Molar Method acc. to API research proj. 44 ***)- 5 = Vap. calc. acc. Molar Method acc. to ISO 6578 ***)- 6...255 Other vapour calculations (reserved, future) ***)

VolumeCorrectionsStatus ID#140; Status of ID#24, VolumeCorrections.

WWaterLevel ID#42; Value of the water level.WaterLevelStatus ID#43; Status of ID#42, WaterLevel.WaterVol ID#56; Value of the water volume.WaterVolumeStatus ID#57; Status of ID#56, WaterVol.

Appendix

Page 38

Appendix B Article and part numbers

Article description Part no.

Indication stickers 2075.998Carrier board 0880.601Newt 80165 0880.602IP-232/485 complete (Modbus) 0880.811IP-BPM complete 0880.812IP-232/485 complete (858 CIU) 0880.813Key switch complete 0880.822Power supply complete 0880.830Serial driver (DIL) 2518.120ROM serial carrier board 2518.941RTC clock chip carrier board 2518.942Serial driver (DIL) 2519.105BPM connector 2522.110 + 2524.968Micro jumpers (RS232) 2522.130Jumpers carrier board 2523.922Mains connection cable 2570.238Mains fuse 2655.337Net entry 2670.202Fuse T1A carrier board 2829.978

Appendix


Appendix C Related documents

API Manual of Petroleum Measurement Standards(Annex to chapter 1, ‘Vocabulary’, released in January 1982)

ISO/TC 28/Section 3 - Terms relating to the calculation of oil quantity

Installation guide 880 CIU Prime/Plus

Instruction manual 880 CIU Prime

Instruction manual Modbus ProtocolTM

Instruction manual Ensite Service ToolInstruction manual Ensite Pro Configuration Tool

Page 40

Documents

4416.526 Rev.2