Nov.

2022

Sofrel DL4W – User manual

This document describes the general instructions for the installation and use of SOFREL products.
LACROIX Sofrel and its subsidiaries accept no liability whatsoever in the event of the user’s non-compliance with any of the following
instructions or with the recommendations contained in the various instructions.

LACROIX Sofrel and its subsidiaries shall in no way be held liable in the event of the user’s non-compliance with any of the following
instructions or with the recommendations contained in the various technical documents associated with the products.

Support / Repair

LACROIX Sofrel is solely authorised to carry out electronic troubleshooting operations for its products.
For any request for technical support, please contact your partner or LACROIX Sofrel’s after-sales service,

LACROIX – Environment
2 rue du Plessis, 35770 Vern-sur-Seiche, France
 +33 (0)2 99 04 89 94 / or by email [email protected]

All Rights Reserved

It is strictly forbidden to reproduce all or part of this manual or to distribute it in any form whatsoever, without the prior permission
of LACROIX Sofrel. The information contained in this manual has been carefully checked and is deemed to be correct. However,
LACROIX Sofrel cannot be held responsible for any errors or inaccuracies that may exist in this manual, nor for any resulting direct
or indirect damage, even if it has been informed of the possibility of such damage. Due to ongoing product development, LACROIX
Sofrel withholds the right to make any modifications to this manual and to related products at any time, with no prior notification of
concerned individuals.

User Guide
(V 6.31 – Nov. 2022)
 DL4W: Functional description
Nov. 2022

General Overview
Data Loggers in the SOFREL DL4W range are fully watertight (IP68) products that are suited to the climatic
constraints of their surroundings: especially when installed underground or in wet or flood-prone areas.

They also make it possible to automatically read meter, flow, and pressure measurements across drinking
water or waste water networks, and send data at least once a day over 2G/4G LTE-M & NB-IoT, to one or
more centralisation systems (“SCADA - remote control and monitoring Central Station” or “Web Server”).

Each DL4W Data Logger is powered by a battery; it is energy self-sufficient for several years.

1 DL4W range

1.1 Fields of application

Each Data Logger in the range is designed to meet a specific application.
Thus, for each model, there is a DL4W product corresponding to a LS/LT device with, as a key
difference, the ability to communicate across LTE-M / NB-IoT networks.
Each application area can have its own type of data logger:

Remote reading District metering Pressure

monitoring

Permanent
Rain Gauge Diagnostic
Self-monitoring

 The Data Loggers send their data via 2G/4G LTE-M & NB-IoT to one or two centralisation systems.
In addition, users can transmit SMS commands (data status read request, meter indexing, etc.) from a mobile phone
and / or receive alert messages on their phones.

DL4W-doc_01-Descri
 DL4W: Functional description
Nov. 2022

1.2 Models and product types

Description
Model Application
Product Type
DL4W / LS10 Remote reading for simple metering
District metering of water networks and remote reading of
DL4W / LS42
meters
DL4W-S Remote monitoring of waste water networks (storm overflows,
(Standard) DL4W / LT42 etc.), telemetry of various facilities (meters, tank levels, etc.),
remote reading in irrigation, etc.
DL4W / LS-P Pressure Monitoring on the water network

District metering and remote reading for major consumers

DL4W / LS-Flow
(ABB, SIEMENS, KROHNE, ARAD flow meters).
DL4W-LP Level measurement with a radar sensor
(Low Power) Flow measurement with a level sensor
DL4W / LP-OpenSensor
Water quality measurement with MODBUS sensors
(temperature, conductivity, pH, chlorine, turbidity, etc.)

DL4W / LT-US Ultrasonic level or flow measurement.

DL4W-HP Level measurement with a radar sensor

(High Power)
Flow measurement with a level sensor + Ultrasonic sensor
DL4W / HP-OpenSensor
Water quality measurement with MODBUS sensors
(temperature, conductivity, pH, chlorine, turbidity, etc.)
Normally energy self-sufficient thanks to their built-in battery,
they can be offered in a “EPS” specific version powered by an
external source (battery, power supply, solar panel,
DL4W-HP EPS DL4W / HP-OpenSensor EPS
microturbine, etc.). With an external power supply, this Data
(External Power Supply) Logger makes it possible to communicate at a frequency of
less than five minutes, either between sites with a remote
terminal unit, or when transmitting data to one or two SCADA
Central Station(s).

DL4W-doc_01-Descri
 DL4W: Functional description
Nov. 2022

2 User interfaces
3 Centralisation System:
2 SOFTOOLS : (SCADA Central Station and/or Web Server)
Bluetooth Communication

 Configuration read/write
 Diagnostics
 Network data centralisation
 Read/write configuration on the Web Server
 Updating configurations remotely

4
1
Key:
Mobile telephone:
Local wake-up on key
SMS alerts

 Local wake-up for indexing,

communication diagnostics, etc.  Warning messages received
on the user’s mobile phone
 Command SMS sent by the user (data
status read request, meter indexing, etc.).

Legend :

Bluetooth Communication

2G/4G LTE-M & NB-IoT Communication

SMS Communication (∗)

(∗) : Depending on the telephone operator, SMS communication via 4G M2M is not always supported.

DL4W-doc_01-Descri
 DL4W: Functional description
Nov. 2022

3 DL4W Material characteristics

Case

Dimensions in mm: H = 261 x W = 155 x D = 176

(the case can be wall-mounted using 2 screws)
Input cable connector: watertight bayonet connector (military grade)

Watertightness
With its IP68 protection rating, this Data Logger can be fitted in a wet or flood-prone
environment.
The case is protected against the effects of prolonged immersion, up to 200 days in
2 metres of water.

Battery Life
The Data Logger evaluates its own remaining battery life every day and sends this
information to the Centralisation System.
• The "934" battery (or standard battery) is optimised to provide the Data Logger with an
operating autonomy of several years.
• The "933" battery (or high capacity battery) can be used to significantly increase the Data
Logger's autonomy.

Antenna
The built-in GSM antenna has been specifically designed to improve communication quality
over GSM networks in difficult environments (particularly in buried manholes).
The Data Logger’s FLEX offers users a choice of device with a built-in antenna and the option
to connect an external antenna.

Key
The key enables the user to wake up the Data Logger to write the configuration and to run the
operating diagnostics (communication tests, meter indexing, GSM reception level check, etc.).
These operating tests can be performed using either the indicator lights, or the SOFTOOLS in
Bluetooth communication mode, or by means of a mobile phone via SMS.

Tool

The case can only be opened under optimal conditions by means of this specific tool, which
ensures proper operation of the locking system and helps maintain the product’s seal.

Electrical safety
Directive 2014/53/EU “RED”:
(Protection of human health and safety, Electromagnetic compatibility, Telecommunication)
In accordance with current European regulations, this device is intended for use in an industrial
environment. It presents no hazardous voltage pursuant to the Low Voltage Directive (for further
details, see the section on “Environmental standards and conditions”).

DL4W-doc_01-Descri
 DL4W: Functional description
Nov. 2022
4 Functional Characteristics
Configuration
Read/Write for configuration update:
• using Bluetooth communication mode via SOFTOOLS
• or communicating remotely with the Web Server via SOFTOOLS
• or communicating remotely via the “CS-Configuration” (Supervisor or SCADA) choice
associated with a Front-end processor (FR1000 / FR4000 / PCcom / PCcom4 / OPC-UA) for updating via SOFTOOLS.

Diagnostics
Data Logger operating checks and communications tests using indicator lights, with SOFTOOLS in Bluetooth
communication mode, via a mobile phone in SMS communication mode.

Data acquisition
4 DIs are used to manage meters or signalling:
• Meters: (input characteristics)
- minimum pulse timing: 2 ms (max. frequency: 250 Hz).
- for meters with an open collector transistor output (capacity <220 pF).
• Signalling:
- CSV overflow sensors (two maximum)
- DI data for connected device operations;
their status change can trigger a communication.
2 AIs for acquiring “4-20 mA” measurements:
- 2 optional AIs: “4-20 mA” measurements converted to 10 bits (sensors are remotely powered by the Data Logger)

Data Calculations
The Data Logger periodically calculates data for:
- average flows on meters.
- thresholds on AI measurements and/or average flows on meters.
- nighttime flow to monitor flow rate over a user-configurable time period.
- AI flow (Height/Flow conversion).
- daily balances: for each meter, DI, threshold or AI flow rate

Archiving Values
Large storage capacity: up to 100,000 values archived.
Archiving of meter index values, average flows on meters, AI measurements and DI status changes.
Based on two user-configurable time periods: for example, archiving every 15 minutes during the day and on the hour for
a specific time period or according to the value for the activation period of a DI or Threshold.

Daily Balances
The Data Logger generates daily balances for:
- the values of each meter (index value at the time of the balance, daily volume).
- average flows on meters (min., max. and nighttime flow).
- AI flow rates (daily volume from the Height/Flow conversion).
- the active status count of each DI and threshold.
- the total active status time of each DI and threshold.

Communication with the Centralisation System

The Data Logger connected to the 4G LTE-M & NB-IoT GPRS network with a private (dedicated) or public (standard)
APN is always the source of communication to 1 or 2 Centralisation Systems.
It transmits the archived values for the data retained, daily balances, and diagnostic data.
The Data Logger will generally communicate once a day with the centralisation system, but for some applications, or
particular situations, the user can temporarily inhibit communication or, conversely, program up to six transmissions per
day according to user-configurable times, or periodically (for example, every four hours).
The Data Logger can also trigger instant communication, if there is a change in the status of a logical data point (such as
a level or flow being exceeded).
Lastly, if a threshold is exceeded or an overflow is detected, or on DI, the Data Logger is able to trigger calls at
a user-configurable frequency and transmit current data statuses and archived values to a SCADA Central Station
(for example, every 15 minutes during an overflow).

Communication with a mobile phone

The Data Logger can send warning messages via SMS to the user’s mobile phone.
The user can issue diagnostic commands via SMS messages.

DL4W-doc_01-Descri
 DL4W: Functional description
Nov. 2022

Functional Characteristics (Cont.)

Inter-RTU Communications
On a private (or dedicated) APN, Data Loggers can communicate via 4G LTE-M & NB-IoT with a local station
or an RTU: the choice of RTU is configurable (S500, S4, etc.).
In this way, in a periodic or event-triggered manner (if the status of a DI input changes, or a threshold is
detected, or a sensor is down, or an overflow is detected), the current data values (DI, AI, meter readings,
flows, thresholds, and sensor failures) are sent to the remote terminal unit.

4G LTE-M & NB-IoT

These inter-site communications ensure slave control between remote sites: exchange of current data and
set-point values is thereby ensured between structures (water towers, pumping stations, etc.), making it
possible to automate and secure the processes.

Analogue Sensor Monitoring

The Data Logger can detect and archive 4-20 mA measurement anomalies; this function enables users to be
highly responsive in terms of their maintenance (disconnected sensor or faulty sensor).

Instant detection
The Data Logger runs an “Instant detection” DI to immediately trigger, upon change of status:
• Data transmission
• SMS alerts
Changes in the status of this DI can be archived. This function can be used, for example, to immediately detect
an intrusion on the site.

Rain Gauge
The Data Logger manages one or more “rain gauge” DIs to activate:
• Calculation and archiving of rainfall intensity: the user specifies the pulse weight (in mm) and
the unit of time for the rainfall intensity calculated (in seconds, minutes or hours).
• Pulse archive: the rising edges sent by the rain gauge are time-stamped.

Connecting a third-party sensor to the AI

The customization of a third-party sensor can be configured for an “Other Sensor” AI on a Data Logger
communicating via 4G LTE-M & NB-IoT.
Its measurement range is user-configurable: the minimum and maximum values corresponding to the
4–20 mA may be between [-99,999.99; 99,999.99].

OpenSensor Data Loggers

The Data Loggers DL4W/LP-OpenSensor and DL4W/HP-OpenSensor can be connected to one or more
MODBUS communicating Equipments (remotely powered or not) such as sensors, flowmeters, etc.
These Data Loggers allow the configuration of standard MODBUS registers and each of these registers
becomes an exchanged information.
This "OpenSensor" functionality offers wide communication possibilities for different use cases (Radar
measurement, Water quality: pH, conductivity, turbidity, chlorine, etc.).

DL4W-doc_01-Descri
 Standards and conditions of use
June 2021

1 General Precautions
UN
Recommendations This device is powered by a lithium battery; only the batteries specified by the product manufacturer can ensure its safety and
performance. The installation of any other power supply is at the user’s own risk.
The presence of the lithium battery places this device in “UN Category 3091 – Class 9” of the UN nomenclature governing hazardous
materials. As such, its transportation must comply with the rules in force which are specific to the means of transport used, whether in
terms of packing, identification and accompanying documents. In all cases, the carrier must be notified of the precise contents of
the package.
The warning label opposite (Danger label for Class 9 – Miscellaneous Dangerous Goods) must be stuck to the packaging and remain
visible from the outside of the package. This type of label is available from carriers and packaging suppliers.

2 Directive 2014/53/EU “RED”

Protection of Human Health and Safety
Electric shock, energy transfer hazard, fire, mechanical and thermal hazards

EN 61010-1 Safety rules for electrical measuring, regulation and laboratory devices

EN 62311 Evaluation of electronic devices in relation to the restrictions on human exposure to electromagnetic fields

Electromagnetic Compatibility
Standard Nature Method Level
Emission from measuring, control or laboratory devices comprising a radio function
ETSI EN 301489-1
ESTI EN 301489-17 EN 55011
Conducted and radiated disturbances
ESTI EN 301489-52 EN 55032
EN 61326-1
Immunity from measuring, control or laboratory devices comprising a radio function
4 kV on contact
Electrostatic discharges EN 61000-4-2
8 kV in the air

ETSI EN 301489-1 Electromagnetic field EN 61000-4-3 10 V/m

ETSI EN 301489-17
ETSI EN 301489-52 Transients in bursts EN 61000-4-4 2 kV
EN 61326-1
Shock waves EN 61000-4-5 +/- 500 V under 2 Ω (EPS version only)

Conducted disturbances EN 61000-4-6 6 V/m

Telecommunications
GSM 850, E-GSM 900, (2,000 mW)
ETSI EN 301 511 Mobile stations (2G)
DCS 1800, PCS 1,900 MHz, (1,000 mW)

ETSI EN 301 908 Cellular networks (4G) NB-IoT: LTE B1, B2, B3, B4, B5, B8, B12, B13, B18, B19, B20, B25, B28, B66, B71, B85

LTE-M: LTE B1, B2, B3, B4, B5, B8, B12, B13, B18, B19, B20, B25, B26, B27, B28, B66, B85

ETSI EN 300 328 Data transmission devices on the 2.4 GHz Bluetooth band (100 mW)

ETSI EG 203 367 Multi-radio devices

01-01-DL4W-doc_Normes
 Standards and conditions of use
June 2021

3 Technical Characteristics
Case dimensions: 176 × 155 × 261 mm

Storage and use conditions

Operating temperature -20°C – +55°C

Storage temperature -25°C – +70°C

Watertightness level IP68 (for 200 days in 2 metres of water) EN 60529 (2000)
Can be chosen according to the type of device, number of communications, etc.:
Power supply • One 934 battery (standard battery)
• or one 933 battery (high-capacity battery)
Local connection Bluetooth with Softools Central Station – 2,400 MHz

Remote Communications 2G/4G LTE-M & NB-IoT with SCADA Central Station and/or Web Server

Maximum altitude 3,000 metres

Pollution level 2
Outdoor use subject to conditions (protection from the sun’s rays, protection from
Indoor/outdoor use
draughts, etc.)

Environmental Protection
2002/96/CE Collection and sorting of Waste Electrical and
WEEE Guidelines Electronic Equipment (WEEE), treatment, recovery and
2003/108/CE non-polluting disposal

For the sake of the environment, an out-of-use product will have to be returned to its supplier, who will take care of waste recycling.

01-01-DL4W-doc_Normes
 Opening/Closing The Case
June 2021

Watertightness rules
When properly installed, the Data Logger is fully protected against the effects of immersion and can be
fitted to a manhole in a wet or flood-prone environment.
To guarantee that the case is IP68 waterproof, the closing ring must be fully tightened (up to the locking
clip) and the connection cable connectors must be locked. The case will only be opened to insert the SIM
card or change the battery.

1. Storage
When the product is delivered, the ring is not tightened: if stored for a long period in a wet
environment, the case must be properly closed.

2. Closing the Case

 Silica gel:
The sachet of silica gel that comes with the product absorbs any residual dampness
within the product. Simply remove the plastic packaging and place the sachet at the bottom
of the case.

 Watertight seals:
Before closing, ensure that the surfaces in contact with the O-ring seals are clean
(one seal in the neck of the lower shell section and one around the upper shell section of the case).

 Locking:
Use the tool to tighten the ring until the clip locks.
To do this:
• Use the gripping tool to securely hold the base of the housing,
• Insert the clamping tool into the notches provided and turn the housing until it reaches the
clip. If necessary, apply silicone grease to the threads to make it easier to close the case.

Clamping

Case
locking clip

Holding

⚠ Do not tighten beyond the clip.

3. Installation
Following these instructions will ensure the product’s IP68 waterproof protection.
The product is then ready to be installed: connect the cables, attach the case to the bracket,
run diagnostics, etc. (see user manual).

⚠ Whenever the case is opened, the sachet of silica gel and the two seals must
be replaced.

02-00-Instal-DL4W-doc_Lock
 Installation
June 2021

Installation Precautions
1 Watertightness
The Data Logger has an IP68 waterproof protection rating; it is fully protected against the effects of
temporary immersion and can be fitted to a manhole in a wet or flood-prone environment.
Compliance with these installation rules ensures that the product is perfectly sealed. The
conditions for opening and closing the case and the method for ensuring perfectly watertight
connections are described in this user manual.

2 Case Features
2.1 Position and dimensions

The mounting bracket must be securely attached by two screws and two pegs (not provided) with the
following characteristics:

 Minimum resistance to pulling 150 N.

DL4W-doc_02-01-Instal
 DL4W : Installation
June 2021

2.2 Battery Power

The Lithium battery can be potentially dangerous; it is therefore imperative to follow the
following usage recommendations:
• Do not recharge, short-circuit, crush or disassemble the battery (or any other action that
does not comply with the product’s warranty conditions).
• Do not heat or incinerate it: risk of flame, explosion and burns.

 In order to protect the environment, dead batteries should be returned to your supplier, who will
handle waste recycling.

⚠ Regarding transport conditions, abide by the UN standards outlined in the “Standards and
conditions of use” UN 3091 - Class 9 devices.

2.3 Location of the case

To improve or optimise GSM communications, the position of the Data Logger in the
manhole needs to be examined; it is usually best to remove it from the cover.
Then, attach the case vertically to its bracket with Up and Down in the correct position.

⚠ Checks should be performed in a real-life situation with the manhole cover closed.

2.4 Connecting DI/AI Inputs

The DI/AI input cable can easily be disconnected from the case to make it easier to connect various
devices. All inputs are protected up to a maximum voltage of 12 Volts.

• “Standard” meter:
DI 1: metering pulses (LF signal)

or
• “In/Out” meter:
DI 1: metering pulses (HF signal)
(1) DI 2: water flow direction in = 0
out = 1

or
• Logical data point (signalling)

Check that the connectors

for the different connection
• 4-20 mA measurement
(sensor powered by the unit) cables are locked.

(2)
or

• 4-20 mA measurement
(autonomous sensor)

(1) The connection of an “In–Out meter” is compatible with DL4W / LS42

and DL4W / LS-Flow OpenSensor products;

(2) The power supply voltage of the 4-20 mA sensor is 12VDC or 20VDC .

DL4W-doc_02-01-Instal
 Inserting the SIM card
June 2021

Accessing the SIM card

The Data Logger must remain completely watertight.

⚠️ Refer to the section “Opening/Closing the case”.

The SIM Card is a 2FF Mini-SIM card When setting up the SIM card, it is imperative to follow the procedure
described below:

Tool  On the SIM card, the PIN code request must be

deactivated and the SMS Server Centre number
registered; if not, insert the card in a mobile phone
and change these two parameters.

In France, the main SMS servers used are:

 ORANGE: +33689004000,
 SFR: +33609001390,

Two seals  BOUYGUES: +33660003000.

Data Logger
Case

02-02-Instal-DL4W-doc-SIM
 IP68 watertight connection
June 2021

General
Since Data Loggers are generally installed in wet or even flood-prone environments, it is essential to
make watertight connections for the connection of input–output cables or extension cables.
LACROIX Sofrel offers two easy-to-use IP68 watertight connection kits:
Watertight connection of two ∅4–17 mm cables (two cable glands) for a maximum of five
• 2PE-5C conductors
Watertight connection of four ∅4–14 mm cables (four cable glands) for a maximum of eight
• 4PE-8C conductors
The user must select the corresponding kit according to the number and diameter of the cables to
be connected (refer to the installation guide supplied with each kit).

1 Conducting Wires
Strip the wires before screwing in
the cable glands, as shown
opposite:

2 IP68 Connection of Two Cables

2PE-5C

Assembly order of end caps

Cable diameters: Ø 4–5 mm:

Ø 5–7 mm:

Ø 7–9 mm:

Ø 9–14 mm:

Ø 14–17 mm:

02-03-Instal-DL4W-doc-IP68
 IP68 watertight connection
June 2021

3 IP68 Connection of Four Cables

4PE-8C

Three-screw-point
Five-screw-point terminal strip
terminal strip

Assembly order of end caps

Cable diameters: Ø 4–5 mm:

Ø 5–7 mm:

Ø 7–9 mm:

Ø 9–14 mm:

4 Screwing the Cable Glands

Use two 24-mm wrenches and screw each cable gland with a maximum force of 2.5 Nm:

(or two 29 mm wrenches if cable with Ø 14–17 mm)

⚠ In order to avoid disturbances, the “low current” cables (DI/AI) must be separated from the power
components (mains power supply cable, transmission support line, etc.).

02-03-Instal-DL4W-doc-IP68
 Built-in or external antenna
June 2021

General
The FLEX version of the Data Logger offers users a choice of product with a built-in antenna and the
option to connect an external antenna.
The installation of an external antenna is recommended when reception levels are insufficient, for
example in buried manholes. This solution allows the antenna to be installed in an open environment and
remotely deployed outside the manhole to obtain better GSM reception.
Before being permanently attached to a bracket (preferably a non-metallic one), the installer can test
different antenna positions.

1 Description
The external antenna, cable and connector are watertight.
Various solutions for hiding the external antenna can be offered.
For information, contact your supplier’s technical support team.

2 Fitting the antenna

• Dimensions (in mm):

Example of a bollard on the ground

to hide the antenna:
Two holes for mounting
(∅ 5 mm screws maximum)

Cable length = 4 m

Buried manhole:

02-04-Instal-DL4W-doc-EA
 Hiding the external antenna
June 2021

Overview
For better GSM reception, it is necessary to install an external antenna in an open environment.
Different antenna positions must be tested before permanently fixing the antenna to a preferably
non-metallic base.
Several possibilities are available for hiding this external antenna.

 In all cases, the tests recommended in the user manual are assumed to have been previously
performed (start-up diagnostics, reception level test with SOFTOOLS, GSM communication test, etc.).

1. Examples of Potential Locations

1.1. Antenna Embedded in the Road Surface
A recess can be created in the asphalt (maximum 5 cm deep) in which the antenna is placed.

External antenna
covered with asphalt

1.2. Surface-Fitted Antenna

Surface-fitted antennae must be protected and hidden.
• in a standardised bollard: • in a conventional bollard:

To insert the antenna, cut the base and the bollard as shown below,
then slide the antenna into the marker, running the connector and cable through the base.

Cutting zones

Next, assemble the bollard and the base, and push the antenna up using the rigid cable.
The base can be affixed to concrete or simply buried.

02-05-Instal-DL4W-doc-Hide-EA
 Replacing the Battery
June 2021

General
SOFREL DL4W range Data Loggers are traditionally energy self-sufficient thanks to their built-in battery.
Only the two battery types 934 (standard battery) or 933 (high-capacity battery) referenced for this
device can ensure its safety and performance.
Replacing this battery with any other type of battery or power supply is at the user’s own risk.

⚠️ Configuring an exception is recommended before replacing the battery: this will avoid the loss of the Data
Logger’s archives, which can then be sent to the Centralisation System.

See the section on “Opening/Closing the Case” (replacement kit for seals and silica gel sachet).

⚠️ The Lithium battery can be potentially dangerous; it is therefore imperative to respect the
following usage recommendations:
 Do not recharge, short-circuit, crush or disassemble the battery, do not heat it beyond 100°C, and
do not incinerate it.
 Risk of flame, explosion and burning.

 In order to protect the environment, dead batteries should be returned to your supplier, who will
handle waste recycling.

Replacement Procedure
 Remove the electronic board from the case and
disconnect the power supply wire:

Tool
Then, pinch the two tabs
to remove the battery fastening

Sachet of
silica gel

 Remove the used battery and insert the new battery in

the direction shown below: Clip the fastening in this
direction to mount the
TOP battery in the case.

Two seals:
DOWN
(one for the upper shell
section, one for the lower For the 933 battery, insert
shell section)  Connect the battery connector to the this
electronic board
and return it to its original position.

l ⚠️ At the end of the operation, log in to perform a “Diagnostics – Power Management”: the “New Battery”
function allows you to reset all product activity indices.

02-06-DL4W-doc_Instal_Pile
 Data Loggers DL4W
Nov.-22

Range

03-08-DL4W-Range
 Data processing
Nov. 2022

General
SOFREL DL4W range Data Loggers make it possible to automatically collect metering, flow and pressure
measurement values across drinking water or waste water networks and send the data at least once
a day, via 2G/4G LTE-M & NB-IoT, to one or more centralisation systems (Web Server or Remote Control
and Monitoring Central Station).

In addition to the installation precautions, this DL4W user manual describes:

• the general features common to standard Data Loggers, more specifically

the DL4W/LS42 and DL4W/LT42 product types,

• the specific characteristics that clarify the main features

of the DL4W/LS-P, DL4W/LS-Flow, and DL4W/LT-US product types.

 Each type of Data Logger is designed to correspond to a specific application

(see the chapter “Functional description”).

⚠ Data exchanges between devices require a telecommunication network for which the Customer assumes full responsibility
in terms of both data security and operating costs. The use of private telecommunication networks offers a high degree of
exchange security. However, as public networks are not intrinsically secure, all necessary precautions should be taken
when using them. LACROIX Sofrel cannot be held accountable for any malfunctions caused by flaws, shortcomings, or
even the intrinsic characteristics of the telecommunication system.

1 DI inputs
The Data Logger runs a maximum of 4 DIs that can be configured for Signalling, Meters,
or Instant Detection.

1.1 Signalling
For each signalling DI event, it is possible to define a positioning logic (Normally Open/Normally
Closed) as well as appearance and disappearance timers. Following a status change, the Data
Logger can trigger a communication to the centralisation system.

1.2 Meters
Each meter DI can be configured to represent a counted number of pulses for this input. The
value of the meter pulse is user-configurable; this parameter defines the meter’s index unit.

1.3 Instant detection

If there is a status change, each DI configured as “Instant Detection” immediately triggers data
transmission and an SMS alert. This makes it possible to immediately detect an intrusion on the
site, for example.

DL4W-doc_03-01-Infos
 Data processing
Nov. 2022

2 AI Inputs
Two “Measurement – AI” data points are available for connecting two 4–20 mA sensors (a CPR or
CNPR sensor, or an “Other sensor” when using other types of sensor).
For these measurements, it is possible to report a negative maximum value if the user wants to display
values below level 0 (ground level reference), for example in the case of a borehole or well.
The Data Logger provides the power supply for each of the sensors solely during the time required to
acquire the measurement. The wait time between sensor power-up and measurement acquisition can be
configured by the user according to the sensor connected.

3 Calculated Data
Based on the values of the “Meter” and “AI” data, the Data Logger generates calculated data with user-
definable parameters:

3.1 Average Flows

For each meter, the Data Logger can calculate and archive the average flow, e.g.: the number of
m3 per hour, minute or second.

3.2 Night-time Flow

This data point is used to monitor the flow for a user-configurable time period. The flow is
calculated based on the difference between the indices read at the start and end of the time
period. This value is available at the time of the following daily balance.

3.3 Calculations of daily flows and volumes

The Data Logger calculates the flow rate in a pipe simply from the height of the water inside the
pipe, via 2 conversion tables.
Using a water height sensor, the Data Logger can calculate 2 flow rates: via an initial conversion
table, for the flow rate in the main water pipe and, based on a second level (overflow for
example), it calculates the flow rate in a secondary pipe.
The Data Logger automatically infers the daily volume passing through each pipe. The flow
rate is calculated and archived as the meters are archived.

3.4 Threshold Detection

Four thresholds can be configured: to monitor AI measurements, to check the average flow
rates calculated on the basis of the meters or to check the flow rates through one or
two water pipes (via conversions).
Two time periods can be associated with each threshold during which the threshold values are
monitored; an upper or lower calculation logic is applied to each time period.

3.5 Metering of Indexes on AI – Flow

Based on the 2 “AI – Flow” data points (Nos. 68 and 69), the index calculation is stored and the
results are accrued in the 2 metering data points (Nos. 78 and 79).

3.6 Daily Balances

At the user-defined reporting time, the Data Logger calculates and archives the data values
recorded (daily index, daily volume, night time flow, minimum and maximum daily flow; see the
section on “Archiving and Reports”).

DL4W-doc_03-01-Infos
 Data processing
Nov. 2022

4 Diagnostic Data
This data provides the user with real-time information regarding the Data Logger’s operating status,
i.e.:
• the GSM reception level,
• the number of kilobytes exchanged with the centralisation system or systems,
• the electrical capacity consumed since the battery was fitted,
• an estimate of the remaining battery life (in number of days),
• and the internal temperature of the case.

This diagnostic data is archived daily when the daily report is sent; it is systematically updated and sent
to the Centralisation System once a day.

DL4W-doc_03-01-Infos
 Data processing
Nov. 2022

List of data
In any given configuration, the number of each data point is fixed, irrespective of the amounts or types of data used.
This data is sent to the Centralisation System via LACBUS-RTU:

No. Data name No. Data name

1 Metering 1 (on DI 1) 50 Default overflow sensor 1
2 Metering 2 (on DI 2) 51 Default overflow sensor 2
3 Metering 3 (on DI 3)
4 Metering 4 (on DI 4) 52 Number of daily DI 1 activations
53 Number of daily DI 2 activations
5 AI 1 54 Number of daily DI 3 activations
6 AI 2 (or Pressure for LS-Flow) 55 Number of daily DI 4 activations

7 Threshold 1 56 Daily number of activations Threshold 1

8 Threshold 2 57 Daily number of activations Threshold 2
9 Threshold 3 58 Daily number of activations Threshold 3
10 Threshold 4 59 Daily number of activations Threshold 4

11 DI 1 or DI 1 / Overflow 1 60 DI 1 daily active status time

12 DI 2 or DI 2 / Overflow 2 61 DI 2 daily active status time
13 DI 3 62 DI 3 daily active status time
14 DI 4 (Detection/Signalling) 63 DI 4 daily active status time

15 Flow 1 64 Daily time Threshold 1 enabled

16 Flow 2 65 Daily time Threshold 2 enabled
17 Flow 3 66 Daily time Threshold 3 enabled
18 Flow 4 (or Instant Flow) 67 Daily time Threshold 4 enabled

19 Daily metering 1 68 AI – Flow rate 1

20 Daily metering 2 69 AI – Flow rate 2
21 Daily metering 3 70 AI – Daily volume 1
22 Daily metering 4 71 AI – Daily volume 2

23 Daily volume 1 72 Ext. - Fault

24 Daily volume 2 LT-US : US sensor link fault
25 Daily volume 3 LS-Flow : flow meter link fault
26 Daily volume 4
73 Ext – AI
27 Min. daily flow 1 LT-US : US sensor measurement LT-US
28 Min. daily flow 2 LS-Flow : flow meter temperature (depending on the model)
29 Min. daily flow 3
30 Min. daily flow 4 74 EXT - DO

31 Max. daily flow 1 75 AI 1 – Default sensor

32 Max. daily flow 2 76 AI 2 – Default sensor
33 Max. daily flow 3
34 Max. daily flow 4 77 Inter-RTU communication fault

35 Night time flow 1 78 Metering on AI – Flow 1

36 Night time flow 2 79 Metering on AI – Flow 2
37 Night time flow 3
38 Night time flow 4 80 Modbus Sensor - Default
81 Modbus Sensor - AI
39 Reception level 82 Modbus Sensor – Diagnostics Code
40 SCADA CS communication meter 83 Modbus Sensor – Signal Quality
41 Energy consumption
42 Diagnostics overflow sensor 1
43 Diagnostics overflow sensor 2
44 Remaining battery life

45 EXT - Status
46 Internal temperature
47 Number of communications triggered per day (daily transmissions, transmissions upon change of status of a logical data point, user–
controlled transmissions (exceptions). Its value is reset at the daily reporting time.
48 Communications reliability (percentage of successful communications calculated once a day, at the daily reporting time).
49 Flow meter battery level (for LS-Flow)

 The Web Server automatically calculates the average flows and daily balances of the meters (no configuration
required in the Data Logger).

DL4W-doc_03-01-Infos
 DL4W: Archiving and Balances
Nov. 2022

Archiving
1 Principle of precautions
⚠ The archiving period of each sensor must be configured with a value greater than the total
duration of acquisition of measurements.
This total duration of acquisition of measurements corresponds to the "cumulative duration of remote
feeding" configured for the following sensors (sensors available according to the Data Logger model):
a. Sensor connected to the AI1 (fixed remote powering time equal to 0.2s for a CPR or CNPR
sensor, configurable time for another type of sensor)
b. Sensor connected to AI2 (fixed remote power supply time equal to 0.2s for a CPR or CNPR
sensor, configurable time for another sensor type)
c. Modbus sensors (configurable delay after remote power-up)
d. US sensor (fixed remote power supply time equal to 5s)

Non-functional examples of configuration:

• Archiving period configured to 1 min for AI1 input and 40 s power supply duration for AI1 and AI2 inputs,
i.e. a total duration of the acquisition sequence that exceeds 80 s and therefore prevents archiving of AI1
with a 1 min period.
• Archiving period configured at 1 min for the registers of a Modbus sensor and the sum of the power
supply durations of the AI1 input (50 s), of the Modbus sensor (5 s) and of the ultrasonic sensor (5 s)
which is 60 s (50 + 5 + 5). The total duration of the sequence exceeds this sum because it includes the
times necessary to change the power source and the acquisitions themselves.

2 Archiving
2.1 DIs and Thresholds
Some types of Data Loggers(1) archive changes in the status of the DIs and Thresholds after appearance
or disappearance timeout; however, the user must set this “Archiving” parameter in the configuration.

2.2 Meters, Average Flows, Meter Readings on AIs

2.2.1 Archiving Periods
The values obtained are archived based on user-configurable periods:
• Every 1, 2, 3, 5, 6, 10, 15, 30 or 60 minutes (if 0, no archiving).
Separate archiving periods can be defined based on the data (2):
• A main period and a secondary period
for archiving meters on DI and archiving average flows,
• A main period and a secondary period for archiving
each AI1 and AI2 (for calculated or terminal strip inputs).
Thus, each main period configured can be replaced by a new secondary one (2):
• During a user-configurable time period.
• If a DI is present.
• If a threshold is exceeded.

 For example, the Data Logger can archive the meter indices every 10 minutes during the “Day rate”
period and every 30 minutes during the “Night rate” period.

DL4W-doc_03-02-Archiv
 DL4W: Archiving and Balances
Nov. 2022

2.3 Synchronisation of value archiving

The Data Logger synchronizes archiving operations by means of its internal clock. Synchronizing
archiving operations makes it possible to compare the values of the various sites at the Central
Station.

 For example, for a 15-minute period, archiving is performed at 2:15, 2:30, 2:45, etc. (sub-multiples of the hour).

2.4 Archiving Capacity

The Data Logger’s maximum archiving capacity has been extended to 100,000 values.
This large archiving capacity provides the contract operator with more extensive facility diagnostics:
it thus has local access to data during field operations. Moreover, this avoids the risk of losing data in the
event of communication problems with the SCADA Central Station over longer or shorter periods (GSM
reception level too low).

Configuration Example
For a 15-minute archiving period
- 1 AI: acquisition of a 4-20 mA measurement - 96 values per day
- 1 Meter: acquisition of a meter - 96 values per day
Total:
- 1 Average flow: Calculation of the flow rate on the meter - 96 values per day
- Daily balance calculation: meter and flow - equivalent to 100 values per day
488 values per day
- 1 to 18 DI-Signaling and Threshold status changes - equivalent to 100 values per day

i.e. a capacity of 200 days’ archiving (beyond this, new values overwrite old ones)

(1) Archiving the changes in the status of DIs and Thresholds is available for DL4W / LT42 and DL4W / LT-US.
(2) These two types of Data Loggers also offer the possibility to replace a main archiving period with a secondary one.

Daily Balances
The user must configure whether or not the Data Logger performs the calculation of daily balances.
Daily balances and diagnostic data are sent once per day during the first transmission following the
calculation of the daily balances (independently of the configured transmissions mode).
Every 24 hours, at the time of the daily balance defined by the user, the Data Logger calculates and
archives the data balance values for “DIs”, “Meters” and “Average Flows”, i.e.:
• the active status count of each DI or each threshold.
• the total active status time of each DI or threshold (in seconds).
• the daily index of each meter (index calculated at the time of the balance).
• the daily volume (difference between current and previous day indices).
• the minimum and maximum flows (daily).
• the nighttime flow.
• the daily volume calculated by the Height / Flow conversion.

DL4W-doc_03-02-Archiv
 DL4W: Archiving and Balances
Nov. 2022

Data Logger autonomy

In order to limit power consumption, the Data Logger only activates its GSM modem during data
communication phases.
Two types of battery can be used to power the Data Logger; only the batteries specified by the device’s
supplier can guarantee its safety and performance.
The estimated battery life below takes into account the following conditions of use:
 Ambient temperature between 5°C and 25°C,
 Average GSM reception level.

Communication Battery Life Battery life

Data Logger Acquisitions and Archiving via 2G/4G with Pack 934 with Pack 933
LTE-M & NB-IoT, (Standard battery) (High-Capacity battery)

- Acquisition of 2 meters archived every 15 minutes,

- Acquisition of one AI measurement archived every five 1 call

5 years 10 years
minutes, per day
with a CPR, CNPR or CNPI sensor.

 To preserve the Data Logger’s battery life, it is important to limit the archiving period
and the number of daily transmissions.

⚠ The battery life of the various types of Data Loggers is specified in their respective
documentation (see the section on “Specific characteristics”).

For example, the battery life of the DL4W / LT-US varies according to whether it is used with an
ultrasound sensor or an overflow sensor.

Conversely, controlling a sampler has only minimal effect on overall battery life.

DL4W-doc_03-02-Archiv
 DL4W : Communications
June 2021

Data Centralisation
1 Communication with a SCADA Central Station
The Data Loggers are always the source of the communication; the IP addresses are assigned to the
connection. The IP address of each receiving SCADA Central Station must be fixed. Port 502 is used to
communicate with the SCADA Central Station.
The identity card of a Data Logger in the DL4W range lists:
 The following reference for communication: “2G - NB-IoT - LTE-M”
 The Serial number from: “01-816-NNNNN” (N corresponds to the device number)

1.1 Network Description

 On a Private (or Dedicated) APN
The 2G/4G network is considered an extension of the company’s local network; this
enables devices to be attached to it:
 The IP address of each Data Logger is a local network address.
 The configured SCADA Central Stations belong to the same local network.
 The company’s DNS server knows the names of the network’s SCADA Central Stations.

 On a Public (or Standard) APN

The 2G/4G network is linked to the company’s local network via the internet.
 The IP address of each Data Logger is dynamically allocated by the operator.
 The IP address of the SCADA Central Station, viewed from the Data Loggers, is the public
address of the entry point for the local network.

1.2 Data Transmitted

The Data Logger sends the following to the Web Server or the SCADA Central Station:
• the archived values.
• daily balances (once daily).
• and the diagnostic data (once, when the system wakes up each day),
even if the Data Logger does not calculate balances.

DL4W-doc_03-03-Comm
 DL4W : Communications
June 2021

1.3 Daily Transmission Time

The data transmission time of each Data Logger to the centralisation system is user-configurable
(default: 6:00).

1.4 Time Synchronisation

The Data Logger time is automatically synchronised with the time of the SCADA Central Station
or the Web Server once a day at the configured transmission time.

1.5 Triggering Communications

The data is sent to one or two Centralisation Systems (Web Server and/or Central Station) in
the following cases:
• Once a day, at the configured transmission time.
But the user can also configure it to "no transmissions" (no centralisation),
or configure “up to 6 daily transmissions” (6 different transmission times).
or
• Periodically with a Central Station according to a user-configurable transmission
period that can be set to 8h, 4h, 2h, 1h, 30 min or 15 min, calculated from the daily
transmission time.
In the case of double centralisation, the Web Server will call only once at the time of the
first programmed transmission.
and
• Immediately, upon change of status of a logical data point (for example, if a threshold
is exceeded).
 In the event of failed transmission (problem connecting with the network, no reply from the SCADA
Central Station, etc.), 3 further attempts are made to communicate with the Centralisation System; there
is a 15-minute interval between each attempt.

1.6 Volume of data exchanged

The following formula is used to estimate the volume of data exchanged with the Centralisation
System:

Number of records per day X 0.15 = Number of Kb per month

• For a typical configuration (§ Archiving): 488 values x 0.15 = 73 Kb per month

• For a maximum setting (4 DIs/meters, 2 AIs, 2 Average flows, Daily balances), for a 1-
minute archiving period, the volume of data would be 1.3 MB per month.
 This formula is an estimate: different criteria may be selected by the telephone operator.
Thus it is not possible to know the actual cost that will be invoiced to the Client.

1.7 Battery life monitoring

Every day, the Data Logger transmits its "Remaining battery life", estimated in number of days,
to the SCADA Central Station.

DL4W-doc_03-03-Comm
 DL4W : Communications
June 2021

Event-triggered communication to the SCADA Central Station

When a data point appears, a DL4W-LT42 Data Logger (*) can trigger calls at a user-configured
frequency to a Centralisation System.
The data sent in these event-triggered communications are current and archived values. The maximum
number of transmissions can be configured (1-300).
This occurs, in exceptional events, when the operator needs to monitor how the situation develops in real
time in order to decide on what action to take (in the case of major floods, monitoring changes in river
levels enables preventive and/or corrective action to be taken in advance). Similarly, in a waste water
network, monitoring variations in network level or when an overflow has occurred enables predictions to
be made on how the occurrence will develop.

Exception

Data Logger Calls

Day 1 Day 2 Day 3

The user configures a DI, Threshold or Overflow-type data point, which, as soon as it appears,
triggers a series of calls: transmissions can be configured to a frequency of 5, 15, 30, 60 or 240 minutes.
The Data Logger returns to “normal operation” once this information is no longer active.
 If several call exceptions arrive simultaneously, the Data Logger will memorise them and act on the
shortest frequency.

Inter-site communications
On a private (or dedicated) APN, Data Loggers can communicate with a remote terminal unit (or RTU):
the type of remote terminal unit can be configured (S500, S4, etc.).
In this way, in a periodic or event-triggered manner (if there is a change in the status of a DI input, threshold,
overflow, or a sensor fault), the current values of the user-defined data points (DI, AI, Meter Readings, Flows,
and Thresholds) are sent to the remote terminal unit.
 For example, the “no sensor” signal can be sent when this data point appears; the remote terminal unit
is then immediately alerted and can trigger immediate operation in degraded mode, and not in the
event of a potentially erroneous value.

4G LTE-M & NB-IoT

These inter-RTU communications make it possible to ensure slave control between remote sites: the
exchange of current data and setpoint values is thereby ensured between structures (water towers,
pumping stations, etc.), making it possible to automate and secure the processes.
Uses: If a sensor connected to the Data Logger is down, the pump continues its action based on a
false value. The diagnostic is only known at the next communication.

* Feature not available on DL4W-LS42 Data Loggers.

( )

DL4W-doc_03-03-Comm
 DL4W : Communications
June 2021

SMS alerts sent to a phone

Two “Signalling” or “Threshold” data points can be configured to trigger
SMS alert messages “with time-stamped event”.
When one of these data points appears and/or disappears, the Data Logger sends an SMS to the
operator’s phone; the phone number and the content of this message are user-configurable.
If DI 4 appears, the Data Logger sends an SMS to a specific mobile phone.
“ 2019/03/28 14:55 VERN site – Spillage.”
Site name 16-character text
associated with the data point

 The disappearance of the alert (end of spillage, for example) also triggers a “with time-stamped event”
SMS to be sent.

DL4W-doc_03-03-Comm
 DL4W : Configuration
Nov. 2022

Using SOFTOOLS
SOFTOOLS is the LACROIX Sofrel software for configuring and running Data Logger diagnostics. The
main SOFTOOLS features are as follows:
• Configuration: defining and storing Data Logger parameters,
• Bluetooth connection for Diagnostics (communications test, energy management, etc.).
• Bluetooth connection for Configuration Read and Write operations.
• Meter indexing.
• Automatic Data Logger time setting.
• Connection for configuration update on the Web Server.
• Printing the configuration to a PDF file.
After installing and starting SOFTOOLS, the user creates the Data Logger in the directory that
corresponds to their product.
♦ SOFTOOLS Options:

1 Creating a Data Logger

• RC select “New device”

• or RC and select “Import device” from an export file (∗.pl).

1.1 General Properties

The user enters the name of the site where the product is installed, any comments, its GPS coordinates and the image.

DL4W-doc_03-04-Config
 DL4W : Configuration
Nov. 2022

1.2 ID Card
This SOFTOOLS display describes the Data Logger’s features:
• Serial number
• Configuration: version – update date and time
• Software version
• Installed software options
• Hardware: version – battery type

2 Configuring the Data Logger

2.1 General view
1 2 3 4 5 6

10

(1) Exit and return to the directory

(2) Save configuration
(3) Convert: after downloading and updating the software, this action allows you to access
and configure new features
(4) Export configuration for a SCADA Central Station
(5) Display online help
(6) Configure data
(7) Communications parameters
(8) Archives and Reports
(9) SMS alert input
(10) Processing: Thresholds and Height/Flow conversions

DL4W-doc_03-04-Config
 DL4W : Configuration
Nov. 2022

2.2 Communications
2.2.1 Central Station Centralisation: Web Server and/or SCADA
The FLEX version offers users the option to configure the built-in antenna or the external antenna.
By default, the modem is in "Automatic" mode, i.e. in 4G communication with 2G fallback.
• "Network" : choose the network according to the SIM subscription and the GSM operator
technologies of the GSM operator. In automatic mode, the Data Logger will test the
3 technologies: NB-IoT, LTE-M and 2G.
• "4G frequency bands" : The user has to select the available frequency band(s) according to his
country available according to his country and operator.

If the user configures the "Automatic" choice, the Data Logger modem searches for the frequency
bands to be used. However, this search may in some cases increase the communication time
significantly, which may be detrimental to the autonomy of the Data Logger.

 The Data Logger communicates periodically only with a Central Station. In the case of double centralisation, the Web Server
will call only once at the time of the first programmed transmission. On networks with several devices, the daily transmission
times of each Data Logger are automatically offset.

• Passcode and site number: The user enters the passcode to communicate with the SOFTOOLS Operator
Dialogue. The site number allows the SCADA Central Station to identify the Data
Logger that is calling.
• Scheduled or periodic transmissions: A scheduled transmission time is defined by default (up to six transmissions can
be configured per day).
• Safeguards: Limit the number of communications sent per day to avoid possible billing
problems.
• Phone operator subscription: Enter the APN name, user name and password given to you by the operator with
your DATA subscription.
• IP address: Enter the IP address of the SCADA Central Station: either the local network
address (if using a private APN) or the public address of the entry point for the
local network (if using a public APN).
• Automatic offset: Check the automatic daily transmission offset when more than 20 Data Loggers
are configured with the same daily transmission time; in this case, the transmission
from the Data Loggers will be carried out over a slot of 15 minutes from the
programmed time.

DL4W-doc_03-04-Config
 DL4W : Configuration
Nov. 2022

2.2.2 Inter-site communication to local station / RTU

On a private (or dedicated) APN, Data Loggers can communicate between sites with a local station or an
RTU. Transmissions take place periodically, if a DI or Threshold data point is present or upon the
appearance/disappearance of a configured data point.
The user must simply:
• define the IP address of the RTU and its APN,
• configure the data from the Data Logger that will be transmitted periodically and/or in an event-
triggered manner to the RTU (and define the data point numbers for the RTU in which these
values will be stored).

2.3 Defining archiving and balances

The Data Logger archives previous data values based on one or two user-configurable periods (primary
and secondary periods); each AI can be configured with a primary period and a secondary period based
on the types of measurements to be taken. In addition, during a user-configurable time period or if there
is a DI or a Threshold, the archiving period for meters, average flow rates and AIs can be replaced by
a new period.
The user defines the time of the “Daily balance” and the time period for the “Night flow rate” period.

DL4W-doc_03-04-Config
 DL4W : Configuration
Nov. 2022

2.4 Processing - Thresholds

In the following example, if Flow rate 1 exceeds the upper or lower threshold, the “Threshold 3” data point
is activated and can trigger communication with the Centralisation System.
A timer can be optionally set for the appearance and/or disappearance of this “Threshold 3” information
point: the timer duration depends on the monitored data point’s archiving period.

Example: for a 2-minute archiving period, in the example above, the threshold appearance is effective
after (4x2) minutes, i.e. after 8 minutes of consecutive overrun.

 To configure a constantly valid time period, enter from 00:00 to 24:00.

To invalidate a time period invalid, enter a period end time
identical to the start time: for example, 00:00 to 00:00.

2.5 Processing – Conversions

Two conversion tables can be configured to calculate flow rate from a height measurement provided by
an analogue sensor. Up to 20 points can be defined for each curve; in the event of a linear relationship
between Height and Flow rate, only 2 values are required (minimum and maximum).

The flow rates and volumes thus calculated by the Data Logger are transmitted in data points
Nos. 68 to 71. A daily volume is automatically calculated from the flow rate.

DL4W-doc_03-04-Config
 DL4W : Configuration
Nov. 2022

2.6 SMS alerts

The appearance of a DI or a threshold can trigger the transmission of warning messages to a mobile phone.

⚠ Please check to see if SMS are supported by your network!

Upon the appearance/disappearance of DI 4, the Data Logger sends an SMS to the specified mobile phone.
"VERN site – Open manhole".
Site name 16-character text
associated with the data point

2.7 Configuration of data

2.7.1 DI – Meter
The meter index is multiplied by the pulse weight before data transmission and display. The unit of
measurement used is the one read by the sensor. The unit of time used for average flow rate calculation
is user-configurable.

2.7.2 DI - Instant detection

An “Instant detection” DI enables detection of an anomaly or failure on the monitored site (without any
timeout).

• Normally open: the logical data point is inactive when the digital input loop is open,
• Normally closed: the logical data point is inactive when the digital input loop is closed.

DL4W-doc_03-04-Config
 DL4W : Configuration
Nov. 2022

2.7.3 DI – Rain gauge

A “DL4W / LT42” or “DL4W / LT-US” Data Logger can calculate rainfall intensity based on
pulses received on the DI connected to the rain gauge (see the chapter “Using a rain gauge”).

2.7.4 AI – Type of sensor

It is possible to configure a “CPR (10 bar or 20 bar)” or “CNPR (16 bar)” sensor, or an “Other
sensor” (for CNPI or CNPA sensors, for example) and to also define the archiving and
transmission of any failures in this sensor.

If “Other sensor” is chosen, the following fields must be configured:

• Power supply voltage: 12 VDC or 20 VDC (∗)

or “Sensor not powered” by the Data Logger,
• Power supply time before measurement: from 0.2 to 60 seconds,
• Minimum and maximum sensor values: from -99,999.000 to 99,999.990
• Offset: if the sensor is not located at the bottom of the reservoir, the offset is able to
compensate for the difference between the measured and actual levels.

 CNPI sensor case, set "Time Power = 0.2 seconds”.

CNPA sensor case, set "Time Power = 1 second”.

Measured level Actual level

Offset

DL4W-doc_03-04-Config
 DL4W : Configuration
Nov. 2022

3 Updating the Configuration

3.1 Bluetooth Connection
The user must perform a “wake-up on key” of the Data Logger, then trigger, from SOFTOOLS,
a “Bluetooth connection”. At login, the user selects the operation to be performed on the Data Logger.

 Writing the configuration of the Data Logger causes the archives to be deleted; however, the user can still log
in to the product and configure an exception in order to send the archives to the Centralisation System
before writing the configuration.

Passcode: 0 to 9999
(0 by default)

SOFTOOLS compares its configuration with the one downloaded to the product. The configuration
can be updated with a single click: the Data Logger’s parameters are then immediately modified and
its time is automatically synchronised with that of the PC-SOFTOOLS. The user must wait around
20 seconds before logging in to the operator dialogue.

3.2 Updating Configurations Remotely

All Data Loggers can be configured to communicate with one or two centralisation systems, chosen from
among the following types: Web Server (SCADA 1 only), CS-Configuration (SCADA 1 only), SCADA
Central Station (SCADA 1 and SCADA 2).
♦ Local update: with Bluetooth connection via SOFTOOLS.
♦ Remote update using the Web Server:
Configuration read/write is performed from the SOFTOOLS directory, via the Web Server
connection. From the SOFTOOLS directory, click on this button to “receive” the Web Server
reports (after the configuration update).

 On the first daily wake-up, the Data Logger reads its

configuration in the WEB server.

♦ Remote update with “CS-Configuration” type:

This function makes it possible to write a configuration for a Data Logger, by placing the Softools Central
Station configuration file on the OPC UA server, or on a front-end processor (PCcom/PCcom4,
FR1000/FR4000) which then ensures that this configuration is transferred to the recipient device.
See documentation: “Updating Data Logger Configurations Remotely”.

DL4W-doc_03-04-Config
 DL4W : Configuration
Nov. 2022

3.3 Data Logger Status in the Directory

After first writing the configuration via Bluetooth, SOFTOOLS identifies the Data Logger and stores its
configuration version, modification date and serial number.
♦ The status is active if the configuration saved in SOFTOOLS differs from that of the device.

Status

Name: Name of configured Data Logger

Type:
Comment:
Status: The configuration has been changed (13/07/2021 11:00:01), awaiting transmission.

At the next login, if the status is active, SOFTOOLS will suggest

updating the configuration:
- either to the Data Logger, via Bluetooth,
- or to the Web Server.

3.4 Configuration for SCADA Central Station

3.4.1 Configuration by file export
From SOFTOOLS, it is possible to export the configuration of each device to a file in tab-
separated text format, for example to process the data using external software.
From the SCADA Central Station, if the latter possesses this feature, you can directly import this
configuration; this function enables automatic configuration of the stations and requires no
manual conversion.
Example of a configuration exported in TXT format:
60001 60002 60003 60004 60005 60006 60101 60102 60103 60104 60105 60106 60107 60108 60109 60110 60111 60112 60113 60114 60115 60116 60117 60119 60120
1 1 0 01 - Count 1 (on DI 1) 1 0 1 1 unit(s) 2 1 0 1 3 6
1 1 0 02 - Count 2 (on DI 2) 2 0 1 1 unit(s) 2 1 0 1 3 6
1 1 0 05 - AI 1 5 0 1 0 0 0 1 3 6
1 1 0 06 - AI 2 6 0 1 0 0 0 1 3 6
1 1 0 13 - DI 3 13 0 0 0 STATUS 0 STATUS 1 0 0 1 3 6
1 1 0 14 - DI 4 14 0 0 0 STATUS 0 STATUS 1 0 0 1 3 6
1 1 0 19 - Daily Count 1 19 0 1 0 unit(s) 2 1 0 1 3 6
1 1 0 20 - Daily Count 2 20 0 1 0 unit(s) 2 1 0 1 3 6
1 1 0 23 - Daily Volume 1 23 0 1 0 unit(s) 2 1 0 1 3 6
1 1 0 24 - Daily Volume 2 24 0 1 0 unit(s) 2 1 0 1 3 6
1 1 0 27 - Min. daily flow 1 27 0 1 0 units/h 0 0 1 3 6
1 1 0 28 - Min. daily flow 2 28 0 1 0 units/h 0 0 1 3 6
1 1 0 31 - Max. daily flow 1 31 0 1 0 units/h 0 0 1 3 6
1 1 0 32 - Max. daily flow 2 32 0 1 0 units/h 0 0 1 3 6
1 1 0 35 - Nighttime flow 1 35 0 1 0 units/h 0 0 1 3 6
1 1 0 36 - Nighttime flow 2 36 0 1 0 units/h 0 0 1 3 6
1 1 0 39 - Reception level 39 0 1 0 0 0 1 3 6
1 1 0 40 - SCADA Central Station communication meter 40 0 1 0 2 1 0 1 3 6
1 1 0 41 – Energy consumed 41 0 1 0 2 1 4 41 1 3 6
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . .
 For the code references used in these columns, refer to SOFTOOLS documentation: “Configuration export”.

3.4.2 Auto-configuration by communication

The Centralisation Systems compatible with the LACBUS protocol automatically configure their posts
by communication: each Data Logger supplies a description of its data.

DL4W-doc_03-04-Config
 DL4W : Diagnostic
Nov. 2022

Principal tests
When the Data Logger has been started up, the user must plug in the battery connector and carry out
some visual tests (the Data Logger’s energy is saved during storage and transportation).

1 Diagnostics with indicator lights

V J
GREEN Indicator light: YELLOW Indicator light:
GSM network registration and SIM Card OK: + + High signal strength
Lit and steady for a modem connected to the 2G
network Flashing for a modem connected to the 4G
network

B
BLUE Indicator light: ORANGE indicator light:
Data Logger awake for tests and communications + Adequate signal strength

Key
Lock

♦ Is the Data Logger running?

To determine this, hold the key in front of the “Lock” symbol for 2 seconds:
• The blue indicator is flashing  the device is running.
• The green and yellow indicator lights come on  the device is not running.
♦ Start-up:
• If the Data Logger is not running, hold the key for 8 seconds until
the green and yellow indicator lights are flashing and to start the Data Logger, then
release the key (all lights go out).
♦ Data Logger wake-up for tests and communications:
• Hold the key in front of the lock printed on the case: the blue indicator light comes on,
flashes, and then stabilises. Tests and communications can now begin.
♦ GSM Reception level:
• After Data Logger wake-up + network registration time
(a few seconds). If the orange and yellow indicator lights do not come on,
there is insufficient reception.
♦ GSM communication diagnostics
• During the tests, the blue indicator light flashes.

 After remaining idle for five minutes, the Data Logger automatically switches to “Standby”
mode (if there is no communication with SOFTOOLS, or when no SMS is received,
or if there is no user action): the four indicator lights are turned off.

Maintaining the key in place for 8 seconds puts the Data Logger in “Down” mode;
this action is useful for saving its energy, for example during storage and transportation.

DL4W-doc_03-05-Diag
 DL4W : Diagnostic
Nov. 2022

2 Diagnostics using SOFTOOLS

By default, the Bluetooth connection to the Data Logger proposes running a "Diagnostic" for various operating tests.

⚠ Connecting locally via Bluetooth inhibits data archiving and threshold calculations.

2.1 “Installation” screen

Meter indexing
♦ Meter indexing

LC on the meter’s value,

modify it and validate 

♦ DI values. This screen is used to check:

• that the number of pulses increments correctly for Meter DIs,
• the active status or inactive of the DI-Signalling.
♦ AI values
For AIs, the “Permanent power supply” parameter allows a measurement instrument to be connected in
order to check the value of the analogue measurement.
♦ Reception level test
SOFTOOLS allows you to test the reception level in order to determine the best location for the Data
Logger and thus optimise communications; this test takes approximately one minute. The reception level
is within a range of 0 to 31:

 To run diagnostics under actual conditions of use, it is recommended to fit the case inside the manhole and close the cover.
When the manhole is closed, if the Bluetooth connection does not work, running the "Delayed test" allows the user to enable
diagnostics when near the Data Logger; the user then has 2 minutes to exit the manhole and close the cover before the test
starts. Next, to retrieve the test result, simply wait a few minutes (eight minutes maximum) and log on again with SOFTOOLS.
The test result is stored in this Diagnostics screen.

DL4W-doc_03-05-Diag
 DL4W : Diagnostic
Nov. 2022

♦ Mobile communications test

To check if the GSM communications are working correctly, the user enters his mobile telephone
number so that the Data Logger can call it immediately.

♦ SCADA Central Station Communication Test

Each Centralisation System must have a fixed IP address; the port number used to
communicate with the Web Server or the Central Station is port 502.
After checking the communication parameters and subscription details (APN, user name,
password, and IP address of the SCADA Central Station), the user can trigger a communication
test between the Data Logger and the centralisation system.

 During a communications test, the Data Logger systematically sends its data configuration to the
Centralisation System.

2.2 “Data” screen

This choice displays the list of the Data Logger’s current data values and, from this list, allows users to
select certain data to view the values archived over one month, one week or one day:

• to display the curve chart

• to export the values to an Excel file

DL4W-doc_03-05-Diag
 DL4W : Diagnostic
Nov. 2022

2.3 “Exceptions” screen

Exceptions, which can be configured in SOFTOOLS or using the Web Server, replace the main
periods configured:
• for periodic transmissions to the centralisation system.
• for archiving AI measurements, metering and average flow rates.
Example: periodic transmissions to the Server every 5 minutes for 1 hour.
When the time period for this exception has elapsed, the Data Logger resumes the normal
operation defined in its configuration parameters.

 For example, it is recommended to configure an exception before updating the configuration or before
replacing the battery: this will avoid the loss of the Data Logger's archives, which can be sent to the
Centralisation System.

Parameters Modifiable via Exceptions

Web Server Values

Function
Parameter
Allowed Values
No.
5, 15, 30, 60 or 240 mins
Frequency of periodic transmissions 1

60, 240, 480, or 1,440 min (∗)

Cycle length of periodic transmissions 2
Periodic Transmissions 0 to stop current cycle
1 for Central Station 1 or Web
Server, 2 for Central Station 2, 3
Choice of Centralisation System (1, 2, or 3) 7
for Central Station 1 and Central
Station 2
Meter and flow archiving period 3 1, 2, 3, 5 or 10 mins
Length of application of this 24, 48, 72, etc. Up to 720 hours (∗)
4
meter and flow archiving period 0 to stop current cycle
Archives
AI archiving period (analogue measurements) 5 1, 2, 3, 5 or 10 min
24, 48, 72, etc. Up to 720 hours (∗)
Length of application for this AI archiving period 6
0 to stop current cycle

(∗) Please note: The "Softools” and “Web Server” interfaces do not use the same values to measure timing.

DL4W-doc_03-05-Diag
 DL4W : Diagnostic
Nov. 2022

2.4 Central Station Communication Screen

This choice makes it possible to display the status of the Data Logger’s communication with the
Centralisation System.

2.5 Energy Management

SOFTOOLS displays the device’s remaining energy capacity and a summary of total SMS communication
time, Data Logger wake-up time, and the time required for measurement acquisition and sensor power supply.
The remaining energy capacity (given in number of days) is transmitted to the Centralisation System.

2.6 Replacing the battery

For this operation, see the section on “Installation – Replacing the Battery”. Next, the user must click on the
following button to reset all of the product’s activity indicators.

New battery

 Before replacing the battery, to avoid deletion of the archives, the user can configure an exception in order to transmit the
data to the Centralisation System. After replacing the battery, it is also necessary to ensure the Data Logger’s time is
synchronised to enable time-stamping for new values.

DL4W-doc_03-05-Diag
 DL4W : Diagnostic
Nov. 2022

3 Diagnostics with a telephone

A mobile telephone allows diagnostic tests to be run by sending command SMS messages. The Data
Logger processes its messages on wake-up; to obtain an immediate response, the user can perform a
“wake-up on key”.

3.1 Test procedure

To run tests, the case must be mounted in a real-life situation; it is even advisable to exit the manhole
and close the cover. On your mobile telephone, dial the number for the Data Logger and send the SMS
message that must use the following syntax:
“AccessCode#Command#Attribute”

1 to 4 numerical characters Data point number, value, etc,

Number 2, 6, 7 or 8
(default: 0) (see following table)

Command Attribute Data Logger’s SMS response

Meter no# Meter value# Meter no# Meter value ANSWER OK: <SMS received>-OK
Meter 2 Meter No.: 1 to 4 Or
indexing Meter value: 0 to 99999999,999 ANSWER NOT OK: <SMS received>-NOT OK
Example of indexing for meter No.1 to 523.674m3 using access code 1234: 1234#2#1#523,674
ANSWER OK:
When issued without an attribute, this command
Syntax of the answer SMS message:
is used to view the current count, measurement
“1Value1#2Value2#3Value3#, etc.”
and average flow values.
Viewing 6
To view the value for a single data point, specify
1 : data point No. 1,
data 2 : data point No. 2, etc.
its number along with the command. Example:
Or
For data point #1: 1234#6#1
ANSWER NOT OK: <SMS received>-NOT OK
Example of viewing all current data statuses using the access code 1234: 1234#6
ANSWER OK: “Operator’s name: Reception level”
(level from 0 to 31) (2)
Immediate reception level 7 No attribute
For levels < 7, move the Data Logger to a new location in order to improve
test GSM reception.
Example using access code 1234: 1234#7
ANSWER OK:
“39GSMReceptionLevelDataPointValue
#40CSCommunicationsMeterDataPointValue
#41ConsumedEnergyDataPointValue
#etc. (1)
Communications 8 No attribute
#PC1*OK / NOT OK,
and power diagnostics
#PC2*OK / NOT OK,
#SMS*NumberofSMSssentthisday/ MaxnumberofSMSssentperday"
Or
ANSWER NOT OK: <SMS received>-NOT OK
Example using access code 1234: 1234#8
ANSWER OK:
<SMS received>-OK
Sending data configuration to
Sent in response to the configuration SMS or connection to write the
the Centralisation System 10 No attribute
configuration for the given Central Stations.
(SCADA Central Stations ANSWER NOT OK:
and/or Web Server) <SMS received>-NOT OK
Example of a command to send the configuration using access code 1234: 1234#10
- “New battery” command: ANSWER OK: <SMS received>-OK
- 99#934 for a No. 934 pack Or
- 99#933 for a No. 933 pack ANSWER NOT OK: <SMS received>-NOT OK
(2)
9
Maintenance diagnostics
- Start-up command with data save: 100 No answer for these commands
- Start-up command without data save: 101

Example of a start-up command with access code 1234: 1234#9#100

(1)
The Diagnostics data (No. 39-48) described in the table on page 6 are transmitted via SMS by the Data Logger.
(2)
The Data Logger responds OK to the command only if the user performed a "wake-up on key" option.

DL4W-doc_03-05-Diag
 DL4W : Remote configuration
June 2021

Description
Each Data Logger can be configured to communicate with one or two centralisation systems:
 Web Server (choice possible in CS No. 1 only),
or
 CS-Configuration (choice possible in CS No. 1 only),
and
 Central Station (choice possible in CS No. 1 and/or CS No. 2),
The “CS-Configuration” choice corresponds to a Central Station (Supervisor or SCADA) associated with
a front-end processor(FR1000/FR4000/PCcom/PCcom4/OPC-UA) for the remote updating of each
configuration of the Data Logger.
The Data Loggers are always the originators of the communication to the centralisation system; their IP
addresses are assigned to the connection.
The IP address of each receiving SCADA Central Station must be fixed. Port 502 is used to communicate
with the SCADA Central Station.

1. Compatibility
Serial number of the Data Minimum Version
Logger: from SOFTOOLS FR1000/PCcom FR4000/PCcom4 OPC-UA
01-816-NNNNN V 4.21.10 V 2.40.11 V 3.10.10 V 2.20.10

1.1 Schematic Diagram

Web Server SCADA Central Station (Communication)
Centralisation – Operation Centralisation – Operation - Configuration
Equipment
configuration
storage
Communication Frontend

Public
Public APN or Private
APN

Configuration
Transfer
Updating for
configurations Remote Update
remotely

Softools
Local Connection for
SOFREL Data Logger Network Configuration Reading
Configuration
and Writing
Export File
 DL4W: Remote configuration
June 2021

2. Configuration
2.1 Softools – Communication
In SOFTOOLS:

 Click on “Communication” to select the communication medium

between the Data Logger and the centralisation system.
 In CS No. 1, configure a “CS-CONFIGURATION” to transfer the Frontend
configuration to the Data Logger.

Enter the Data Logger

access code to
communicate with
the SOFTOOLS Operator
Dialogue.

Data Logger’s ID in the

SCADA Central Station

Enter the APN name, user name and

password given to you by the phone
operator with your subscription.

Enter the IP address of the SCADA

Central Station: either the local
network address (if using a private Scheduled or
APN) or the public address of the periodic transmissions
entry point for the local network (if Check the Data Logger’s
using a public APN). transmission time
and the period for
Check the automatic daily transmissions
transmission interval when more to the Central Station
than 20 Data Loggers are set up with
the same daily transmission time; in
this case the transmission from the
devices will be carried out over a slot Limit the number of SMS
of 15 minutes from the programmed alerts sent during the day to
time. avoid billing problems

3. Updating the Configuration

There are three ways to update Data Logger configurations:

1) Locally, using SOFTOOLS via Bluetooth.

2) Remotely, for Data Loggers communicating with the Web Server via the Mobile Phone Network:
the configuration is read/written with SOFTOOLS, via the Web Server connection.
3) Remotely, for Data Loggers communicating via the Mobile Phone Network with a Frontend:
Prerequisites: The ID card of the Data Logger must be updated in SOFTOOLS; this requires having written or read
the configuration via the Bluetooth connection. Then, perform an update of the device and convert the
configuration to version 4.21 at minimum, and configure “CS-CONFIGURATION” for CS No. 1 in the
“Communication” menu.
a. In SOFTOOLS, export the configuration in “.lx” format.
b. From the Frontend, the “Operation” menu can be used to acquire a new Data Logger configuration
from the “.lx” export file retrieved from the hard disk or any other device.
c. The Frontend then stores this configuration file (one file per device).
d. During its first daily transmission, the Data Logger sends its archives to the “CS-CONFIGURATION"
before checking whether there is a new configuration waiting or not; if the new configuration indicator
is active, then Data Logger will request an update (ID card and configuration parameters).
 DL4W : Updating the Software
June 2021

Procedure
To update the options and software, Bluetooth connection to the Data Logger is necessary:

1. Wake-up and Log In

The user must perform a “wake-up on key” of the Data Logger, then log in to the device created with
SOFTOOLS from the directory (in accordance with the type of Data Logger):

Passcode: 0 to 9,999
(0 by default)

Software selection: import the new software

version of your product.

 Once the new software has been downloaded, the Data Logger resets all current and archived data.

To get the features of the new version, it is necessary to download and update the software and to
“Convert the Configuration” with SOFTOOLS.
The Data Logger’s ID card is automatically updated.
The options are updated according to the same principle: the file containing the software options you
have ordered must be imported into the Data Logger via SOFTOOLS.

03-07-DL4W-doc_Software
 Data Loggers DL4W
Nov.-22

Range

03-08-DL4W-Range
 Data Logger DL4W-S / LS10
NOV.-21

General
The Data Logger type DL4W-S / LS10 is the simplified version of the range; this Data Logger is more
particularly adapted for facilities equipped with a single meter or installations requiring only one DI.

It retransmits data at least once a day, in 2G/4G LTE-M & NB-IoT, to one or more centralization systems
(Web Server or Central Remote Management Station).

⚠ The features of this Data Logger DL4W / LS10 are described in the specific features section of this user
manual.

04-01-DL4W-LS10-doc
 Data Logger DL4W-S / LS10
Nov.-22

Description
DL4W-S / LS10 is the simplified version of the DL4W range. This Data Logger is more specifically suited to
facilities equipped with a single meter or installations requiring only one DI.
The product's specific features are as follows:

1. Hardware
The DL4W-S / LS10 case possesses the same characteristics as DL4W-S / LS42 (identical case
dimensions, built-in antenna, same IP68 protection level, same autonomy, etc.); only the "2-conductor"
connection cable for DI 1 is specific.

 This Data Logger does not allow for connection to an external antenna, no does it manage "in/out" meters
or “4-20 mA sensor” measurements.

2. Communication
• DL4W-S / LS10 communicates over Bluetooth and can communicate over 2G and 4G LTE-M & NB-IoT
with a Centralisation System (SCADA).
• Remote DL4W-S / LS10 configuration read/write is possible from the SOFTOOLS directory,
via the Web Server.

3. Information acquisition and Management

DL4W-S / LS10 can connect only one digital input:
• for managing 1 “Meter on DI”; with a configuration of 4 thresholds to check the average flow calculated
from this meter with possibility to configure 2 warning messages to be sent by SMS to a mobile phone in
the event of threshold overrun.
• or for managing a “DI”; for simple remote-signalling.
• The other DL4W-S / LS10 data are calculated or diagnostic data:

N° SCADA Central Station configuration

1 Metering 1 or DI-Signalling 1

7 Threshold 1
8 Threshold 2
9 Threshold 3
Calculated data 10 Threshold 4

15 Flow 1

19 Daily metering 1

Daily volume 1
23
Min. daily flow 1
27
Max. daily flow 1
31
Nighttime flow 1
35
Reception level
Diagnostic data 39 PC communications counter
40 Energy consumed
41 Remaining battery life
44 Metering 1 or DI-Signalling 1

 In the case where LS10 manages DI-Signalling, no data is calculated (threshold, reading, flow).

04-07-Specific_DL4W-doc_LS10
 Data Logger DL4W-S / LS10
Nov.-22

4. Data Logger autonomy

In order to limit power consumption, the Data Logger only activates its GSM modem during data
communication phases.
Two types of battery can be used to power the Data Logger; only the batteries specified by the device’s
supplier can guarantee its safety and performance.
The autonomy evaluated below takes into account the following conditions of use:
• Ambient temperature between 5°C and 25°C,
• Average GSM reception level,

Communication Battery Life Battery life

Data Logger Acquisitions and Archiving via 2G/4G with Pack 934 with Pack 933
LTE-M & NB-IoT, (Standard battery) (High-Capacity battery)

1 call
- Acquisition of 1 meter archived every 15 minutes, 5 years 10 years
per day

 To preserve the Data Logger’s battery life, it is important to limit the archiving period
and the number of daily transmissions.

04-07-Specific_DL4W-doc_LS10
 DL4W-S / LS42 Data Logger
June 2021

General
The DL4W / LS42 Data Logger is dedicated to district metering of drinking water networks and remote
meter reading.

It sends data at least once a day, via 2G/4G LTE-M & NB-IoT, to one or more centralisation systems
(Remote Control and Monitoring Web Server or SCADA Central Station).

It enables dual-flow meters to be connected (metering in both flow directions in a pipe).

⚠ The features of this DL4W / LS42 Data Logger are described in the general features section of this user manual.

03-08-DL4W-LS42-doc
 DL4W-S / LT42 Data Logger
June 2021

General

The DL4W / LT42 Data Logger is dedicated to the Remote monitoring of waste water networks (storm
overflows, etc.), Remote control and monitoring of various facilities (meters, tank levels, etc.), remote
reading in irrigation, etc.

It sends data at least once a day, via 2G/4G LTE-M & NB-IoT, to one or more centralisation systems
(Remote Control and Monitoring Web Server or SCADA Central Station).

In addition to the general features of the Data Logger, the DL4W / LT42 includes Remote control and
monitoring functions, such as:

• Archiving data status changes (signalling and thresholds),

• Archiving meters and average flows (2 archiving periods),
• Archiving AI inputs (2 archiving periods),
• Balances based on logical data.
• Overflow detection (management of one or two sensors on DI 1 or 2).
• Calculation of “Height / Flow” via conversion tables.

⚠ The features of this DL4W / LT42 Data Logger are described in the general features section of this
user manual.

03-09-DL4W-LT42-doc
 DL4W-S / LS-P Data Logger
June 2021

Description
The DL4W / LS-P Data Logger incorporates the main features of the DL4W / LS42; it makes it possible to
monitor the pressure of the drinking water network; it features 2 AIs for the acquisition of measurements
from CPR or CNP sensors.

1. Key Features
 Daily report archiving (up to 100,000 values),
 Diagnostics (reception level test, battery capacity evaluation,
etc.),
 On-site Configuration and Operation with Bluetooth connection,
curve chart, Excel transfer, Diagnostic LEDs,
 SMS alerts (when thresholds are exceeded),
 Communication with one or two Centralisation systems
(Web Server and/or SCADA Central Station),
 Alarm viewing and acknowledgement on Android Smartphone.

Characteristics
Watertightness IP68 (for 200 days in one metre of water)
Operating temperature -20ºC to +55ºC
Power Supply One “standard” or “high-capacity” battery
Antenna type Choice of a built-in or external antenna (with four-metre cable)
Local connection Bluetooth with PC Softools
Pressure measurement One or two 10- or 20-bar CPR, or 16-bar CNP sensors
Remote Communications 4G LTE-M & NB-IoT with the SCADA Central Station and/or Web Server

2. Connecting AI Inputs
To make it easier to connect sensors, the AI input cable can be disconnected from the case

 4-20 mA measurement
(sensor powered by the device)

 All inputs are protected up to a maximum voltage of 12 Volts.

04-02-Specific_DL4W-doc_LS-P
 DL4W-LP / LS-Flow Data Logger
Nov. 2022

General
The DL4W / LS-Flow Data Logger is used in the District metering of drinking water networks, for the remote
reading of major consumers and interconnection meters.

1 Description
This Data Logger features a RS-485 link for connection to an electromagnetic flow meter.
Compatible types of flow meters (EMFM) are:
• Aquamaster 3 and 4 (ABB),
• MAG 8000 (SIEMENS),
• Waterflux 3070 Low Power (KROHNE company),
• Octave (ARAD).
In this way, the Data Logger is able to acquire very accurate index values from meters and access internal
flow meter data. The Data Logger has an AI for pressure measurement and a DI for intrusion.

1.1 Features and compatibility

Softools DL4W / LS-Flow ABB Aquamaster SIEMENS KROHNE ARAD
3 and 4 MAG 8000 Waterflux Octave
3070 Low Power

Configuration
update
via Bluetooth

Meter: In Index    
Meter: Out Index    
Meter: Net index / subtotal    
Instant flow    
Pressure  ∅  ∅
Temperature ∅ ∅  
EMFM Internal data    
Speed of the RS485 link
19,200 bps 19,200 bps 9,600 bps 9,600 bps
(8 bits, 1 even parity bit, 1 stop bit)

Slave number of the flow meter 1 1 1 1

Flow meter software ABB-3: V 01.05.01.
V 3.07 V 4.2.6x V 4.01.39
(minimum version) ABB-4: V 01.XD.02.

 The ∅ symbol signifies that the data point is not accessible or available.

1.2 Data Acquisition

The Data Logger acquires the following data in the Flow meter:
• 3 Meters,
• 1 Instant flow,
• 1 “Pressure” measurement or 1 “Temperature” measurement.
This data is updated and stored at the same rate as the meter archiving period (user-configurable period
every 1, 2, 3, 5, 6, 10, 15, 30 or 60 minutes). In the configuration, their numbers are fixed, regardless of
the number of data points used.
The Data Logger sends its data to one or two centralisation systems (SCADA Central Station and/or
Web Server), and can send SMS alerts to a mobile telephone for event notification.
The Data Logger enables data archiving and processing.

04-04-Specific_DL4W-doc_LS-Flow
 DL4W-LP / LS-Flow Data Logger
Nov. 2022

2 Configuration
 The “Flow meter type” is configured via the “EXT” extension section:

 Configuration of the EXT link:

3 Operation
3.1 “Installation” screen
In this screen, you can find the index of the three meters and the calculated average flow rates:

Data point No. 45 Ext – Status is the numerical data point that specifies the nature of the faults read in
the flow meter (battery level, pressure not working, etc.); the description of faults is described in the
Appendix. The “0” value indicates there are no faults in the flow meter. The Data Logger archives changes
in the value of this data point.

Data point No. 72 Ext – Fault in status 1 indicates the link fault with the flow meter.

3.2 “Data” screen

This screen presents the information read in the flow meter and calculated by the Data Logger.

04-04-Specific_DL4W-doc_LS-Flow
 DL4W-LP / LS-Flow Data Logger
Nov. 2022
3.3 List of Data
No. Data name No. Data name
1 Metering 1 27 Min. daily flow 1
2 Metering 2 28 Min. daily flow 2
3 Metering 3 29 Min. daily flow 3

5 AI 1 31 Max. daily flow 1

6 Pressure 32 Max. daily flow 2
33 Max. daily flow 3
7 Threshold 1
8 Threshold 2 35 Night time flow 1
9 Threshold 3 36 Night time flow 2
10 Threshold 4 37 Night time flow 3

14 DI 4 (Detection/Signalling) 39 Reception level

40 SCADA CS communication meter
15 Average flow 1 41 Energy consumption
16 Average flow 2
17 Average flow 3 44 Remaining battery life
18 Instant flow 45 Ext-Status (numerical data point specifying the indicator type
flow meter alarms (battery level, pressure not working, etc.)
19 Daily metering 1 46 Internal Temperature
20 Daily metering 2 47 Number of communications triggered per day
21 Daily metering 3 48 Reliability of communications
49 Flow meter battery level

23 Daily volume 1 72 Ext-Fault (link with the flow meter: 0 = OK, 1 = faulty)
24 Daily volume 2 73 Temperature
25 Daily volume 3 75 AI 1 – Default sensor
77 Default Inter-site communication

3.4 List of data exchanged

The table below sets out the list of data read by the Data Logger, according to the various flow meter
models.
 The ∅ symbol means that the data point is not accessible or available.

Flow meter ABB SIEMENS KROHNE ARAD

Data Aquamaster MAG 8000 Waterflux Octave
Metering 1 (in)    
Metering 2 (out)    
Metering 3 (total)   (1)  
Instant flow    
EXT Status    
Pressure  ∅  ∅
Temperature ∅ ∅  
Battery level ∅  ∅ ∅
(1) For the SIEMENS MAG 8000 flow meter, metering 3 represents the change in the value of metering 1 since the last reset.

3.5 Data units

The data units read from the flow meter are displayed by SOFTOOLS and sent to the supervision system. The Data
Logger’s own data is added to the flow meter data, i.e., AI1 (No. 5), thresholds (Nos. 7, 8, 9, 10), average flows (Nos.
15 to 18), daily average flows, and Diagnostics data.
Depending on the type of flow meter, the units of volume, flow, pressure and temperature are user-configurable or
remain fixed.
Flow meter ABB SIEMENS KROHNE ARAD
Units Aquamaster MAG 8000 Waterflux Octave
Volume   m3 m3
Flow   m³/h m³/h
Pressure  ∅ bar ∅
Temperature ∅ ∅ °C °C

04-04-Specific_DL4W-doc_LS-Flow
 DL4W-LP / LS-Flow Data Logger
Nov. 2022

3.6 Night time flow calculation

The night time flow is calculated over a user-configurable time slot with a calculation start and end time
(from 00:00 to 23:00).
The Data Logger calculates the “Night time flow” data point corresponding to this night time period, from
the difference in the indices read at the start and end of the time slot. The night time flow is calculated in
the same unit as the other flows. The unit is the unit configured in the flow meter.

3.7 Flow meter alarms

The flow meter alarms are acquired by the Data Logger and sent on to the centralisation systems.
Alarms are archived by the Data Logger once a day at the time of the daily reporting (see the list described
in section 5 - Appendix).

3.8 Detection/Signalling
The Data Logger makes it possible to monitor the status of a data point (opening/closing) or to instantly
detect an event (for example, an intrusion on a site).
The user must configure a DI that will enable the Data Logger to transmit:
 data on each change of status,
 an SMS alert on each change of status of this DI.

4 Battery life
The flow meter has a standalone power source; the type of flow meter used has no impact on the Data
Logger’s battery life.
In order to limit power consumption, the Data Logger only activates its GSM modem during
communication phases. Two types of battery can be used to power the Data Logger; only the batteries
specified by the supplier can guarantee its safety and performance.
The estimated battery life below takes into account the following conditions of use:
 Ambient temperature between 5°C and 25°C,
 Average GSM reception level.

Communication Battery Life Battery life

Data Logger Acquisitions and Archiving via 2G/4G with Pack 934 with Pack 933
LTE-M & NB-IoT (Standard battery) (High-Capacity battery)

- Acquisition of 2 meters + instant flow rate

+ Flow meter status (archived every 15 minutes).
1 call
Four years Nine years
per day
- Acquisition of one AI measurement archived every five
minutes, with a CPR, CNPR or CNPI sensor.

 To preserve the Data Logger’s battery life, it is important to limit the archiving period
and the number of daily transmissions.

04-04-Specific_DL4W-doc_LS-Flow
 DL4W-LP / LS-Flow Data Logger
Nov. 2022

5 Appendix
5.1 Alarm indicator (Status) – matching bits
“Low order” 32-bit word:

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Bit ABB SIEMENS ARAD KROHNE

number Aquamaster MAG 8000 Octave Waterflux
0 ABB internal alarm 0 Insulation error Leakage Flow meter measurement warning / error

1 ABB internal alarm 1 Coil current error Pipe Burst Battery low warning < 10% left

2 ABB internal alarm 2 Preamplifier overload Reverse Flow Pressure measurement warning / error

3 High DC voltage (any power type) Database checksum error Dry Temperature measurement warning / error

4 ABB internal alarm 4 Low power warning Critical Configuration EEPROM Error

5 High DC voltage (battery power) Flow overload warning Measurement Fail Empty pipe

6 MID (read only) switch Pulse A overload warning Tamper Communication error (Addon <-> mainboard)

7 External battery warning Pulse B overload warning Octave Battery Pressure > Maximum limit Alarm

8 Not used Consumption internal warning Units Change Pressure < Minimum limit alarm

9 Sensor comms. fault Leakage warning Watch Dog Temperature > Maximum limit alarm

10 External battery fail Empty pipe warning Service Required Temperature < Minimum limit alarm

11 Sensor not connected Low impedance warning Flow Rate Cut Off Flow direction

12 Coil not connected Flow limit warning Module battery

13 Empty pipe Reverse flow warning Water meter-Module communication error

14 Mains failure Not used

15 High DC voltage (alarm) Not used

16 High flow

17 Low flow

18 Not used

19 Not used

20 Not used

21 Not used

22 Not used

23 Not used

24 Not used

25 Not used

26 Not used

27 Not used

28 Not used

29 Not used

30 ABB internal alarm 30

31

04-04-Specific_DL4W-doc_LS-Flow
 DL4W-LP / LS-Flow Data Logger
June 2021

Installation – Connection to Flow Meters

1 SIEMENS MAG8000 Flow Meter

1.1 Connecting the Flow Meter

The connection cable is supplied by SIEMENS; it is resin-coated on the MAG8000 flow meter.
For the Data Logger, the cable has a bayonet connector.

 LS-Flow cable (ref. 644 T0020311)

1.2 Connecting an Additional Probe

Wire the probe to AI1.
For a remotely-powered probe, or when an “Instant Detection” DI is present,
it is necessary to cut the cable, then create the connections in a watertight case (T4400302)
in accordance with the diagram below:

Ref. 644

DI 4
AI 1 Instant Detection
Sensor

Watertight case

Note: communication between the Data Logger and the flow meter takes place via
D+ and D- conductors (Grey and Blue respectively).
 DL4W-LP / LS-Flow Data Logger
June 2021

2 ABB AQUAMASTER Flow Meter

Preamble:
 The ABB Aquamaster 3 flow meter must have at least firmware V 01.05.01.
 The ABB Aquamaster 4 flow meter must have at least firmware V 01.XD.02.

2.1 Connecting the Flow Meter

The cable is supplied by LACROIX Sofrel. It comprises two bayonet connectors.

 LS-Flow cable (ref. 647 T0020330)

 Connection to the AQUAMASTER Flow Meter

 DL4W-LP / LS-Flow Data Logger
June 2021

2.2 Connecting an Additional Probe

Use the Y cable (LS-Flow / Aquamaster) provided to ensure the additional probe has a watertight
connection with AI1:

“Ten-pin” moulded “Seven-pin” moulded

socket Ref. 650 connector plug

- Green/Vert AI-
- Yellow/Jaune AI+
- White/Blanc DI4
- Brown/Marron GND

 LS-Flow / Aquamaster cable (ref. 650 T0020333):

For a remotely-powered probe, or when an “Instant Detection” DI is present,

it is necessary to create the connections in a watertight case (T4400301) in accordance with the
diagram below:

Ref. 650

AI 1 DI 4
Sensor Instant Detection

Watertight case
 DL4W-LP / LS-Flow Data Logger
June 2021

3 KROHNE WATERFLUX Flow meter

3.1 Connecting the Flow Meter

The cable is supplied by LACROIX Sofrel. It comprises two bayonet connectors.

 LS-Flow cable

 One-metre cable (ref. 648 T0020331)

or
 Five-metre cable (ref. 649 T0020332)

 Connection to the Waterflux Flow Meter

 DL4W-LP / LS-Flow Data Logger
June 2021

3.2 Connecting an Additional Probe

Use the Y cable (LS-Flow / Waterflux) provided to ensure the additional probe has a watertight
connection with AI1:

“Ten-pin” moulded “Four-pin” moulded

socket Ref. 651 connector plug

- Green/Vert AI-
- Yellow/Jaune AI+
- White/Blanc DI4
- Brown/Marron GND

 LS-Flow / Waterflux cable (ref. 651 T0020334):

For a remotely-powered probe, or when an “Instant Detection” DI is present,

it is necessary to create the connections in a watertight case (T4400301) in accordance with the
diagram below:

Ref. 651

AI 1 DI 4
Sensor Instant Detection

Watertight case
 DL4W-LP / LS-Flow Data Logger
June 2021

4 ARAD OCTAVE Flow Meter

4.1 Connecting the Flow Meter

The flow meter’s RS485 connection cable should be connected to the Data Logger cable ref. 642.

 Standard LS42 cable (ref. 642 T0020303)

“Three wire” flow meter

RS485 cable
Ref. 642

 It is necessary to use a watertight connection box (described below) and fully isolate the Orange
wire of the flow meter’s RS485 cable.

4.2 Connecting an Additional Probe

Wire the probe to AI1.
For a remotely-powered probe, or when an “Instant Detection” DI is present,
it is necessary to cut the cable, then create the connections in a watertight case (T4400302)
in accordance with the diagram below:

“Three wire” flow meter

RS485 cable

Ref. 642

AI 1
Sensor
DI 4
Instant Detection

Watertight case

Note: communication between the Data Logger and the flow meter takes place via
D+ and D- conductors (Grey and Blue respectively).
 Using a Rain Gauge
June 2021

1. Description
1.1. Compatibility
A DL4W / LT42 or DL4W / LT-US Data Logger can calculate rainfall intensity based on
pulses received on the DI connected to the rain gauge.

1.2. Use Case

To calculate rainfall intensity at a precise location, a tipping bucket rain gauge is generally
used. After a given quantity of water, the bucket tips and sends a pulse by closing a contact.
These pulses make it possible to calculate rainfall intensity in two different and potentially
complementary ways in terms of processing in the supervision tool:
 Pulse recording: each pulse is time-stamped. The supervision software is then able to
reconstruct rainfall intensity development over time (as a “hyetograph”) by processing the
different historical data. This method enables the contract operator to choose different
calculation methods and periods of analysis in their supervision or data-processing tool
 Local calculation of the number of pulses received, performed by the Data Logger over a user-
configurable time period. For example, for a bucket tipping after every 0.2 mm of rain received,
a count of 10 pulses, recorded over a period of six minutes, will indicate an average rainfall
intensity of 20 mm/h during the period in question.

Rain Gauge

The Data Logger can:

 archive the rising edges of the pulses
generated by the rain gauge.
 count the pulses received from the rain
gauge and calculate rainfall intensity via the
“Flow” data point for this meter.

Watertight connection of
the “Rain Gauge” DI

04-05-Specific_DL4W-doc_Pluvio
 Using a Rain Gauge
June 2021

2. Configuration
The user must specify the type of “Rain Gauge” DI and configure:
 the weight of a pulse on the DI (one pulse per millimetre by default),
 the unit of time used to express the associated average flow (in hours by default).

For archiving the rising edges of the “Rain Gauge” DIs, simply validate the function
associated with the DI.
The unit used for a meter configured as a “Rain gauge” is the millimetre (mm) and the units
of rainfall intensity are “mm/h”, “mm/mn” and “mm/s” according to the unit of time used for
the flow.

3. Updating Data
The data associated with a “Rain gauge” DI are the meter index and the average flow.
The user may perform an index reset for the number of pulses received from the rain gauge
since the last index reset. The “average flow” contains the rainfall intensity calculated by the
Data Logger.
The values of this data are updated at the frequency of the archiving period of the meters
and average flows. The value of the meter’s index is also updated when local Bluetooth
communication is activated.

04-05-Specific_DL4W-doc_Pluvio
 Controlling a Sampler
June 2021

1. Description
1.1. Compatibility
A DL4W / LT42 or DL4W / LT-US Data Logger can control a sampler.

1.2. Use Case

In a sewerage system, samples must be taken to measure the concentration of pollutants in the effluents.
A portable, battery-powered sampler can be used to periodically store samples. For example, to
automatically trigger a sampling operation in case of overflow (in stormy weather) and analyse the waste
afterwards.
Two operating modes are possible:
 Sampler (time control): upon the appearance of a logical data point (DI or Threshold), the
user defines the sampling period (3, 5, 10, 15, 30 or 60 minutes).
For example, during an overflow, or when a high-level threshold is exceeded, to perform
sampling every 10 minutes.
 Sampler (volume control): whenever a volume of effluents has been discharged, a sample
is taken; the volume is calculated based on the predefined “AI – Flow 1” conversion table.

2. Installation - Connection
Data Logger
Black

Blue

Common/Pulse Input

Sampler

⚠ Connection of the Data Logger’s AI 2 to the Sampler must be watertight.

Use the 2PE-5C kit (see the section on “IP68 Watertight Connection”).

04-06-Specific_DL4W-doc_Preleveur
 Controlling a Sampler
June 2021

3. Configuration
3.1. Configuring the Sampler
On AI 2, the Data Logger generates a 12-V/150-ms pulse; it is necessary to configure the
Sampler to take a sample on each pulse.

3.2. Configuring the Data Logger

With SOFTOOLS, it is necessary to configure:

Sampler (time control) Sampler (volume control)

 A DI, threshold or overflow data point for sampling on  A level measurement (AI 1 or LT-US
appearance of a logical data point measurement)

 A “Height/Flow” conversion table for calculating

the volume (via the “Processing” tab)

 The AI 2 for sampler control (time control) upon  The AI 2 for sampler control (volume control) and
presence of a logical data point and definition of the the definition of the number of volume units
sampling period

3.3. Connection – Installation

The AI 2 data point shows the total number of samples taken. The user can run a “Sampler Test” by
triggering a sampling operation, which will reset this total number.

04-06-Specific_DL4W-doc_Preleveur
 DL4W-HP / LT-US Data Logger
June 2021

Description
The DL4W / LT-US Data Logger makes it possible to perform a level measurement via ultrasound
(or a flow measurement via conversion tables).

1. Overview

DL4W / LT-US: ultrasound level

measurement (0.17 to 3.00 metres)

2. Technical Characteristics
US Probe: Measurement angle 8 degrees
Watertightness IP68 (for 200 days in 2 metres of water)
Resolution 1 mm
Measurement range 170 mm – 3,000 mm
Accuracy ± 3 mm (over the entire measured range)
Dead band 170 mm
Cable length 5 m or 10 m
Operating temperature -20ºC to +50ºC
Temperature compensation Via an internal temperature probe
Dimensions 142 mm total height and Ø 80 mm
Power supply Sensor remotely powered by the connected device
Configuration/Start-up Bluetooth® with SOFTOOLS Central Station
Maximum altitude 3,000 metres
Pollution level 2
Outdoor use subject to conditions (protection from the
Inside / outside use
sun’s rays, protection from draughts, etc.)

⚠️ LT-US / Standard EN61010-1:

Sound pressure risk > 110 dB (ref. 20µPa) at less than one metre from the transducer.

2.1 LT-US data

The data sent by the Data Logger to the Centralisation Systems via LACBUS-RTU are described in the
chapter “Configuration and Diagnostics”; the data listed below are specific to LT-US:

No. Data name No. Data name

45 EXT – Status 72 EXT – Fault logical data point
digital data point specifying the fault type (0 = OK, 1 = defective)
(0 = operating correctly). The Data Logger archives
changes in the value of this data point.
73 EXT - AI
ultrasound level measurement (0.17 to 3.00 metres)

04-07-Specific_DL4W-doc_LT-US
 DL4W-HP / LT-US Data Logger
June 2021

3. Installation
3.1 Installing the transducer
 Vertical position:
Two incline adjustment screws

Four screws for mounting the wall

bracket: Ø 6mm

Two screws that make it

possible to move the
wall bracket out of the way by
placing it momentarily to the side
 Horizontal position (with deflector):
Four screws for mounting the wall
bracket: Ø 6mm
Two incline adjustment screws
parallel to the surface of the water

 To ensure the quality of the measurement, the transducer must be placed in the flow axis
above an area where the eddies are not too strong:
maximum measurement distance = 3 metres.
 After mounting the bracket in a vertical or horizontal position,
the bracket incline must be adjusted so that it is parallel to the surface of the water.
 The min. and max. heights indicated below:

Max. height. Min. height.

(7× the width)
17 cm (dead band)
Max. effluent level

Width

⚠️ The cable between the transducer and the LT-US must not be modified; it is 5 or 10 metres long.
It may be necessary to protect the cable with an outer sheath (presence of rodents, for example).

04-07-Specific_DL4W-doc_LT-US
 DL4W-HP / LT-US Data Logger
June 2021
3.2 Precise measurement of the installation height

Vertical position Horizontal position

Wall bracket: the installation height is measured Deflector, the distance is measured between the
between the bottom of the foundation and the bottom of the foundation and the bottom of the
bottom of the transducer. deflector. Add 200 mm to this distance to set the
installation height in Softools.

250mm 255 mm

80mm 90 mm
65
mm

Installation height Bracket height

Installation height
=
bracket height + 200 mm

Effluent
level

⚠️ The wall bracket and the deflector are available as an option.

4. SOFTOOLS configuration
4.1 Configuration of the Transducer and Sensors
 The “Ultrasound Measurement” type is configured via the “EXT” extension section.

 The 4-20 mA sensors (CPR, CNP) are configured via the AIs, and the CSV sensor via
the DIs.

4.2 Connection – Start up

SOFTOOLS connected via Bluetooth allows access to the “EXT” section to start up the transducer:

04-07-Specific_DL4W-doc_LT-US
 DL4W-HP / LT-US Data Logger
June 2021

4.3 Measurement calibration

The user calibrates the measurement by specifying the installation height of the transducer and
the actual level of effluent.

⚠️ The ambient temperature is an important parameter; for precise calibration, the

temperature must be that at the installation site.
Diagnostics makes it possible to check that the measurement is functioning correctly (value and
quality). If the quality is not correct (red or orange bar graph), the incline of the Ultrasound unit in
relation to the effluent level needs to be checked and adjusted.

Measurement quality:
Low Average Correct Quality

4.4 US sensor diagnostics results

SOFTOOLS allows you to run the diagnostics to get the value for data point 45:

“Ext-Status” Value Diagnostics

0 Measurement OK
1 No extension card
2 Failed communication with extension card
16 Map not initialised
17 Unknown request
18 Error in format of data exchanged
19 No data block number
32 US sensor not connected
33 US measurement not stable
34 Sampling time error
35 Incorrect US sensor supply voltage
36 Measurement acquisition timed out
37 No echo
38 Distance too short
39 KO measurement

04-07-Specific_DL4W-doc_LT-US
 DL4W-HP / LT-US Data Logger
June 2021

5. Battery life
The classic application is a “Combined sewer overflow” (with an average overflow of 20 mins/day).
In order to limit power consumption, the Data Logger only activates its GSM modem during data
communication phases. Data point no.44 makes it possible to assess the remaining battery life, in days.
Two types of battery can be used to power the Data Logger; only the batteries specified by the device’s
supplier can guarantee its safety and performance.
The estimated battery life below takes into account the following conditions of use:
 Full measuring range: 3 metres.
 Ambient temperature between 5°C and 25°C,
 Average GSM reception level (> 7)

Communication Battery life

Data Logger Acquisitions and Archiving via 2G/4G with Pack 933
LTE-M & NB-IoT (High-Capacity battery)

DL4W / LT-US: Acquisition of the measurement 1 call Nine

(with US sensor only) archived every 15 minutes per day years

Acquisition of the measurement 1 call Five

archived every 5 minutes per day years

DL4W / LT-US: Acquisition of the measurement

(with US sensor and archiving:
+ associated CSV sensor) 1 call
 Outside the overflow: per day
10 years
30-min period
 During the overflow: 1-min period

⚠️ To preserve the Data Logger’s battery life, it is important to limit the archiving period and the
number of daily transmissions.

04-07-Specific_DL4W-doc_LT-US
 Data Loggers DL4W
Nov.-22

Range

03-08-DL4W-Range
 Data Logger DL4W / LP-OpenSensor
Nov. 2022

Description
The DL4W / LP-OpenSensor Data Logger allows different types of sensors to be connected (4–20 mA, CSV,
Rain Gauge, Sampler, etc.).
It also manages sensors communicating via MODBUS; the OpenSensor function offers the possibility of
reading MODBUS registers in sensors connected via RS485, with each of these registers becoming a data point
of the Data Logger (nos. 92 to 105).

 The Data Logger thus caters for a large number of applications for the implementation
of a watertight IP68 connection with sensors and assures highly reliable measurements.
Typical example with a MODBUS sensor for Radar measurements:
- warning of overflows in lifting stations,
- detecting a threshold to control the start-up and shutdown of pumps,
- measuring the water level in combined sewer overflows and preventing overflows.

1. Technical Characteristics
2 DIs Managing signaling (manhole cover open, for example).
Instant detection (detecting an intrusion on site),
Managing a pulse meter,
Overflow detection (CSV sensor),
Use of a rain gauge.

1 AI Connecting a 4–20-mA sensor

1 EXT input Managing one or more MODBUS sensors for Radar measurement or
(MODBUS) Water Quality measurement (pH, conductivity, turbidity, chlorine, etc.).

1.1 DI inputs
The configuration of DIs is described in the “DL4W General Features” and the “Using a
Rain Gauge” chapter, respectively. For more information, refer to this documentation.

1.2 AI Input
The configuration of the AI is described in the “DL4W General Features” and the
“Controlling a Sampler” chapter, respectively. For more information, refer to this
documentation.

05-03-Specific_DL4W-doc_LP-OpenSensor
 Data Logger DL4W / LP-OpenSensor
Nov. 2022

1.3 EXT Expansion (US + MODBUS)

The “EXT” section for the DL4W / LP-OpenSensor Data Logger allows users to configure
up to eight third-party MODBUS sensors.

1.3.1 Communication with MODBUS Sensors

It is possible to connect up to eight MODBUS sensors. The parameters of the link are common
to all eight sensors: identical data rate, parity, number of data bits and number of stop bits.
When several MODBUS sensors are remotely powered by the Data Logger, the user must
take into account the following recommendations: mutually compatible power supply voltages,
both energy consumption and power draw that are compatible with the Data Logger’s
electronic characteristics.

Flow meter with

5-V remotely powered sensors
autonomous power supply

12-V remotely powered sensors

 The DL4W / LP-OpenSensor Data Logger offers remote power feed for MODBUS
sensors with 5 V and/or 12 V; refer to the specific connection diagram below.

1.3.2 Operating Precautions

⚠ To ensure the installation operates correctly, the Data Logger is

fitted with an upstream “current limiting device” (user protection).

This current limit is linked to the maximum current – including on power-up (inrush current) –
and the allowable continuous current.
5V 12 V
• Maximum peak current (100 ms) 190 mA 75 mA
• Maximum permanent current 160 mA 65 mA

Exceeding this limit results in a Data Logger reset.

05-03-Specific_DL4W-doc_LP-OpenSensor
 Data Logger DL4W / LP-OpenSensor
Nov. 2022

1.4 Connecting DIs / AIs / EXT

The DI/AI and EXT (MODBUS expansion) cable can easily be disconnected from the case to
make it easier to connect various devices. All inputs are protected up to a maximum voltage
of 12 Volts.

The Ground (GND) is connected systematically via the “Brown” or “Black” conductor.

• “Standard” meter:
DI 1: metering pulses (LF signal)

or

• “In/Out” meter:
DI 1: metering pulses (HF signal)
DI 2: water flow direction in = 0
out = 1
(1)

or
• Logical data point (signalling)

• MODBUS sensor: Remote power feed

(2)

• 4-20 mA measurement
(sensor powered by the unit)

(3)
Check that the connector for
or the connection cables is
• 4-20 mA measurement locked.
(autonomous sensor)

• MODBUS sensor: Link

 It is essential to make watertight connections for the connection of input–output cables

or expansion cables. LACROIX Sofrel offers two easy-to-install watertight connection kits:
refer to the “IP68 watertight connection” documentation.

(1) The connection to an “In–Out” meter is compatible with DL4W / LS42, and DL4W / LP-OpenSensor Data Loggers.

(2) Depending on the connection, the Data Logger can remotely power the MODBUS sensor with 5 VDC or 12 VDC.

(3) The power supply voltage of the 4–20-mA sensor is 12 VDC or 20 VDC.

05-03-Specific_DL4W-doc_LP-OpenSensor
 Data Logger DL4W / LP-OpenSensor
Nov. 2022

List of data
In any given configuration, the number of each data point is fixed, irrespective of the amounts or types of data used. This data
is sent to the Centralization System via LACBUS-RTU:
Data Point
Number Description
1 Index 1 of the meter on DI 1 or rain gauge pulse meter (on DI 1)
2 Index 2 of the meter on DI 2 or rain gauge pulse meter (on DI 2)
5 Analogue measurement on AI 1 or number of samples (if Sampler on AI 1)
7, 8, 9, 10 Threshold 1, Threshold 2, Threshold 3, Threshold 4.
11 Signaling on DI 1 or on overflow sensor 1 or rain gauge status on DI 1
12 Signaling on DI 2 or on overflow sensor 2 or rain gauge status on DI 2
15 Meter flow DI 1 (meter) or rainfall intensity on DI 1 (if Rain Gauge)
16 Meter flow DI 2 (meter) or rainfall intensity on DI 2 (if Rain Gauge)
19 Meter daily index DI 1 or daily total rainfall on DI 1 (if Rain Gauge)
20 Meter daily index DI 2 or daily total rainfall on DI 2 (if Rain Gauge)
23 Meter daily volume DI 1 or daily rainfall height (if Rain Gauge) on DI 1
24 Meter daily volume DI 2 or daily rainfall height (if Rain Gauge) on DI 2
27 Meter min. daily flow DI 1 or daily MIN rainfall intensity on DI 1 (if Rain Gauge)
28 Meter min. daily flow DI 2 or daily MIN rainfall intensity on DI 2 (if Rain Gauge)
31 Meter max. daily flow DI 1 or daily MAX rainfall intensity on DI 1 (if Rain Gauge)
32 Meter max. daily flow DI 2 or daily MAX rainfall intensity on DI 2 (if Rain Gauge)
35 Meter nighttime daily flow DI 1 or nighttime rainfall intensity on DI 1 (if Rain Gauge)
36 Meter nighttime daily flow DI 2 or nighttime rainfall intensity on DI 2 (if Rain Gauge)
39 GSM reception level
40 SCADA Central Station communications meter
41 Battery consumption / Energy consumed
42 Diagnostics on measurement of overflow sensor 1
43 Diagnostics on measurement of overflow sensor 2
44 Remaining battery life (data point not present if EPS)
46 Data Logger internal temperature
47 Number of communications triggered per day (daily transmissions, transmissions upon change of status in a logical data point, user-
controlled transmissions (exceptions). Its value is reset at the daily balance time.
48 Communications reliability (percentage of successful communications calculated once a day, at the daily balance time).
50 Overflow sensor 1 fault
51 Overflow sensor 2 fault
52 Daily number of activations DI 1 or number of overflows
53 Daily number of activations DI 2 or number of overflows
56 Daily number of activations Threshold 1
57 Daily number of activations Threshold 2
58 Daily number of activations Threshold 3
59 Daily number of activations Threshold 4
60 DI 1 daily active status time
61 DI 2 daily active status time
64 Threshold 1 daily active status time
65 Threshold 2 daily active status time
66 Threshold 3 daily active status time
67 Threshold 4 daily active status time
68 AI – Flow 1 (conversion table no. 1)
69 AI – Flow 2 (conversion table no. 2)
70 AI – Daily Volume 1 (conversion table no. 1)
71 AI – Daily Volume 2 (conversion table no. 2)
75 AI 1 – Sensor fault
77 Inter-RTU communication fault
78 Meter index on AI – Flow 1 (conversion table no. 1)
79 Meter index on AI – Flow 2 (conversion table no. 2)
80 MODBUS Sensor – Fault
84–91 1 Fault data point per MODBUS sensor nos. 1, 2, 3, 4, 5, 6, 7, 8.
92–105 1 data point per MODBUS register nos. 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14.

05-03-Specific_DL4W-doc_LP-OpenSensor
 Data Logger DL4W / LP-OpenSensor
Nov. 2022

2. EXT – MODBUS Configuration

2.1 Communications Parameters

The user defines the parameters of the RS485 link:
• Bits per second: choice of 1,200, 2,400, 4,800, 9,600 or 19,200 bps
• Parity: none, odd or even
• Stop bits: 1 or 2

2.2 Sensor Fault Management

The Data Logger detects the presence of “MODBUS sensor fault no. X” in the following cases:
• no response from the sensor in the maximum wait time configured
in the Expert Mode tab,
• Response from the sensor with error code,
• Invalid response from the MODBUS sensor.

The appearance and disappearance of the “MODBUS sensor fault (1–8)” data point are recorded
in the diagnostics log.

2.2.1 Modbus Sensor - Diagnostic Codes

The following error codes are recorded in the Data Logger log:
0 No Modbus error detected
1 Error due to expansion board fault
2 Modbus CRC error
3 Timeout error waiting for response
4 Slave number error
5 Function code error
6 Length error
7 Value error (value not usable)

05-03-Specific_DL4W-doc_LP-OpenSensor
 Data Logger DL4W / LP-OpenSensor
Nov. 2022

2.3 Sensors Tab

The user defines the MODBUS query parameters for the sensors:
• Period: every 1, 2, 3, 5, 6, 10, 15, 30 or 60 minutes.
• Wait time after power-up: the maximum heating time must be configured for each
group of sensors (among those remotely powered with 5 V and those remotely powered
with 12 V)

For each sensor, the user defines:

• a 1–8 character name,
• a unique slave number from 1 to 255,
• Remote power feed voltage: 5 V and 12 V or None
• if each change of status in the sensor fault:
o must be archived by the Data Logger,
o must trigger a communication to the centralization system.

2.3.1 OpenSensor Measurement Acquisition

The acquisition of the MODBUS registers is carried out according to the configured
archiving period. It is possible to define 2 archiving periods (a main archiving period, and a
secondary one).
The second archiving period replaces the first one according to one of the following 2
principles, as desired:
• when a logical information is in the active state (DI or Threshold input),
• during the configured daily time slot.

 See § "DL4W: Configuration - Definition of archiving".

05-03-Specific_DL4W-doc_LP-OpenSensor
 Data Logger DL4W / LP-OpenSensor
Nov. 2022

2.4 Definition of Registers

The user can configure up to 14 MODBUS registers, specifying:
• The read order from 1–14: the registers are configured taking this order into account.
• The name of the sensor that the register belongs to: selection from the list of configured sensors.
• The MODBUS address of the register.
• The MODBUS Function code:
o 3: Reading of output words,
o 4: Reading of input words.
• Format of the read value: choose from the list that appears.
• Coding of words in the frame:
o Select the order of word coding based on the list that appears.
o W1 is the most significant word.
• The name of the register (up to 8 characters).
• If the read value must be archived by the Data Logger.

 The Data Logger reads the MODBUS sensor registers optimally to avoid applying the same
heating times several times in succession (i.e., firstly the registers from 12-V sensors,
followed by those from 5-V sensors).

05-03-Specific_DL4W-doc_LP-OpenSensor
 Data Logger DL4W / LP-OpenSensor
Nov. 2022

2.1 Expert Mode

This screen allows users to enter “advanced parameters” (not mandatory): as a general rule,
the configuration of Expert Mode remains optional.

• Sensors: advanced timings settings linked to the communication with each MODBUS
sensor (for example, to optimise energy consumption or to adapt to a non-compatible
sensor with timings configured by default).
• Registers: redefinition of byte coding in a word and specification of the register value
used if there is a read fault.
o Byte B1 is the high byte and byte B2 is the low byte.

05-03-Specific_DL4W-doc_LP-OpenSensor
 Data Logger DL4W / LP-OpenSensor
Nov. 2022

3. Battery life
The classic application is a “Combined sewer overflow” (with an average overflow of 20 mins/day).
In order to limit power consumption, the Data Logger only activates its GSM modem during data
communication phases. Data point no.44 makes it possible to assess the remaining battery life, in days.
Two types of battery can be used to power the Data Logger; only the batteries specified by the device’s
supplier can guarantee its safety and performance.
The estimated battery life below takes into account the following conditions of use:
 Full measuring range: 3 metres.
 Ambient temperature between 5°C and 25°C,
 Average GSM reception level

Communication Battery life

Data Logger Acquisitions and Archiving via 2G/4G with Pack 933
LTE-M & NB-IoT (High-Capacity battery)

DL4W / LP-OpenSensor: Acquisition of the measurement 1 call

per day
Nine years
archived every 15 minutes

Acquisition of the measurement 1 call

per day
Five years
archived every 5 minutes

DL4W / LP-OpenSensor: Acquisition of the measurement

(with associated CSV sensor) and archiving:
1 call
• Outside the overflow: per day
10 years
30-min period
• During the overflow: 1-min period

⚠ To preserve the Data Logger’s battery life, it is important to limit the archiving period and the
number of daily transmissions.
The archiving period corresponds to the MODBUS communication period for the relevant
sensor.

05-03-Specific_DL4W-doc_LP-OpenSensor
 Data Logger DL4W / HP-OpenSensor
Nov. 2022

Description
The DL4W / HP-OpenSensor Data Logger allows different types of sensors to be connected (4–20 mA, CSV,
Rain Gauge, Sampler, etc.). It takes level measurements with an Ultrasound sensor to detect overflows
(or flow measurements via conversion tables).
It also manages sensors communicating via MODBUS; the OpenSensor function offers the possibility of
reading MODBUS registers in sensors connected via RS485, with each of these registers becoming a data point
of the Data Logger (nos. 92 to 105).

 The Data Logger thus caters for a large number of applications for the implementation
of a watertight IP68 connection with sensors and assures highly reliable measurements.
Typical example with a MODBUS sensor for Radar measurements:
- warning of overflows in lifting stations,
- detecting a threshold to control the start-up and shutdown of pumps,
- measuring the water level in combined sewer overflows and preventing overflows.

1. Technical Characteristics
2 DIs Managing signalling (manhole cover open, for example).
Instant detection (detecting an intrusion on site),
Managing a pulse meter,
Overflow detection (CSV sensor),
Use of a rain gauge.

1 AI Connecting a 4–20-mA sensor

1 EXT input Managing a US sensor (Ultrasound measurement)

(US + MODBUS expansion) Managing one or more MODBUS sensors for Radar measurement or
Water Quality measurement (pH, conductivity, turbidity, chlorine, etc.).

Power supply Traditionally energy self-sufficient thanks to its built-in battery, the
(by battery or EPS) DL4W / HP-OpenSensor can be offered in an EPS version to be
powered by an external source (battery, power supply block, solar panel,
microturbine, etc.).

1.1 DI inputs
The configuration of DIs is described in the “DL4W General Features” and the “Using a
Rain Gauge” chapter, respectively. For more information, refer to this documentation.

1.2 AI Input
The configuration of the AI is described in the “DL4W General Features” and the
“Controlling a Sampler” chapter, respectively. For more information, refer to this
documentation.

05-04-Specific_DL4W-doc_HP-OpenSensor
 Data Logger DL4W / HP-OpenSensor
Nov. 2022

1.3 EXT Expansion (US + MODBUS)

The “EXT” section for the DL4W / HP-OpenSensor Data Logger allows users to configure:
• the SOFREL-brand US sensor,
• up to eight third-party MODBUS sensors.

1.3.1 Communication with the US Sensor

The Data Logger allows users to perform a level measurement via ultrasound (or a flow
measurement via conversion tables):

• In a vertical position, with a wall bracket, the installation height is

measured between the bottom of the foundation and the bottom of the
transducer.

• In a horizontal position, with a deflector, the distance is measured

between the bottom of the foundation and the bottom of the deflector.

 Refer to the DL4W-HP / LT-US chapter for the description, installation and configuration
of the level or flow measurement via ultrasound.

1.3.2 Communication with MODBUS Sensors

It is possible to connect up to eight MODBUS sensors. The parameters of the link are common to all eight
sensors: identical data rate, parity, number of data bits and number of stop bits.
When several MODBUS sensors are remotely powered by the Data Logger, the user must take into account
the following recommendations: mutually compatible power supply voltages, both energy consumption and
power draw that are compatible with the Data Logger’s electronic characteristics.

The sensors on the bus are remotely powered

either with 12 V or 20 V.

Flow meter with

autonomous power supply

 The user must also take note of the types of MODBUS sensors connected on the bus; the choice of
remote power feed is user-configurable and exclusively 12 V or 20 V.

1.3.3 Operating Precautions

⚠ To ensure the installation operates correctly, the Data Logger is
fitted with an upstream “current limiting device” (user protection).
This current limit is linked to the maximum current – including on power-up (inrush current) –
and the allowable continuous current.
12 V 20 V
• Maximum peak current (100 ms) 200 mA 100 mA
• Maximum permanent current 170 mA 85 mA
Exceeding this limit results in a Data Logger reset.

05-04-Specific_DL4W-doc_HP-OpenSensor
 Data Logger DL4W / HP-OpenSensor
Nov. 2022

1.4 Connecting DIs / AIs / EXT

The DI/AI and EXT (MODBUS expansion) cable can easily be disconnected from the case to
make it easier to connect various devices. All inputs are protected up to a maximum voltage
of 12 Volts.
The Ground (GND) is connected systematically via the “Brown” or “Black” conductor.

• “Standard” meter:
DI 1: metering pulses (LF signal)

or
• Logical data point
(signalling)

(1)

• 4-20 mA measurement
(sensor powered by the unit)

(2) Check that the connector for

or the connection cables is
• 4-20 mA measurement locked.
(autonomous sensor)

• MODBUS sensor: Link

 It is essential to make watertight connections for the connection of input–output cables

or expansion cables. LACROIX Sofrel offers two easy-to-install watertight connection kits:
refer to the “IP68 watertight connection” documentation.

(1) The power supply voltage of the MODBUS sensor is user-configurable to 12 VDC or 20 VDC.

(2) The power supply voltage of the 4–20-mA sensor is user-configurable to 12 VDC or 20 VDC.

05-04-Specific_DL4W-doc_HP-OpenSensor
 Data Logger DL4W / HP-OpenSensor
Nov. 2022

List of data
In any given configuration, the number of each data point is fixed, irrespective of the amounts or types of data used. This data
is sent to the Centralisation System via LACBUS-RTU:
Data Point
Number Description
1 Index 1 of the meter on DI 1 or rain gauge pulse meter (on DI 1)
2 Index 2 of the meter on DI 2 or rain gauge pulse meter (on DI 2)
5 Analogue measurement on AI 1 or number of samples (if Sampler on AI 1)
7, 8, 9, 10 Threshold 1, Threshold 2, Threshold 3, Threshold 4.
11 Signaling on DI 1 or on overflow sensor 1 or rain gauge status on DI 1
12 Signaling on DI 2 or on overflow sensor 2 or rain gauge status on DI 2
15 Meter flow DI 1 (meter) or rainfall intensity on DI 1 (if Rain Gauge)
16 Meter flow DI 2 (meter) or rainfall intensity on DI 2 (if Rain Gauge)
19 Meter daily index DI 1 or daily total rainfall on DI 1 (if Rain Gauge)
20 Meter daily index DI 2 or daily total rainfall on DI 2 (if Rain Gauge)
23 Meter daily volume DI 1 or daily rainfall height (if Rain Gauge) on DI 1
24 Meter daily volume DI 2 or daily rainfall height (if Rain Gauge) on DI 2
27 Meter min. daily flow DI 1 or daily MIN rainfall intensity on DI 1 (if Rain Gauge)
28 Meter min. daily flow DI 2 or daily MIN rainfall intensity on DI 2 (if Rain Gauge)
31 Meter max. daily flow DI 1 or daily MAX rainfall intensity on DI 1 (if Rain Gauge)
32 Meter max. daily flow DI 2 or daily MAX rainfall intensity on DI 2 (if Rain Gauge)
35 Meter nighttime daily flow DI 1 or nighttime rainfall intensity on DI 1 (if Rain Gauge)
36 Meter nighttime daily flow DI 2 or nighttime rainfall intensity on DI 2 (if Rain Gauge)
39 GSM reception level
40 SCADA Central Station communications meter
41 Battery consumption / Energy consumed
42 Diagnostics on measurement of overflow sensor 1
43 Diagnostics on measurement of overflow sensor 2
44 Remaining battery life (data point not present if EPS)
EXT – Status :
45 US Sensor Fault - Numerical information specifying the nature of the fault (0 = correct operation).
The Data Logger archives the changes in value of this information.
46 Data Logger internal temperature
47 Number of communications triggered per day (daily transmissions, transmissions upon change of status in a logical data point, user-
controlled transmissions (exceptions). Its value is reset at the daily balance time.
48 Communications reliability (percentage of successful communications calculated once a day, at the daily balance time).
50 Overflow sensor 1 fault
51 Overflow sensor 2 fault
52 Daily number of activations DI 1 or number of overflows
53 Daily number of activations DI 2 or number of overflows
56 Daily number of activations Threshold 1
57 Daily number of activations Threshold 2
58 Daily number of activations Threshold 3
59 Daily number of activations Threshold 4
60 DI 1 daily active status time
61 DI 2 daily active status time
64 Threshold 1 daily active status time
65 Threshold 2 daily active status time
66 Threshold 3 daily active status time
67 Threshold 4 daily active status time
68 AI – Flow 1 (conversion table no. 1)
69 AI – Flow 2 (conversion table no. 2)
70 AI – Daily Volume 1 (conversion table no. 1)
71 AI – Daily Volume 2 (conversion table no. 2)
72 Ext – Fault: fault with the expansion card (for US sensor)
73 Ext – AI: Value measured via the US probe
75 AI 1 – Sensor fault
77 Inter-RTU communication fault
78 Meter index on AI – Flow 1 (conversion table no. 1)
79 Meter index on AI – Flow 2 (conversion table no. 2)
80 MODBUS Sensor – Fault
84–91 1 Fault data point per MODBUS sensor nos. 1, 2, 3, 4, 5, 6, 7, 8.
92–105 1 data point per MODBUS register nos. 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14.

05-04-Specific_DL4W-doc_HP-OpenSensor
 Data Logger DL4W / HP-OpenSensor
Nov. 2022

2. EXT – MODBUS Configuration

2.1 Communications Parameters

The user defines the parameters of the RS485 link:
• Bits per second: choice of 1,200, 2,400, 4,800, 9,600 or 19,200 bps
• Parity: none, odd or even
• Stop bits: 1 or 2

2.2 Sensor Fault Management

The Data Logger detects the presence of “MODBUS sensor fault no. X” in the following cases:
• no response from the sensor in the maximum wait time configured
in the Expert Mode tab,
• Response from the sensor with error code,
• Invalid response from the MODBUS sensor.

The appearance and disappearance of the “MODBUS sensor fault (1–8)” data point are recorded
in the diagnostics log.

2.2.1 Modbus Sensor - Diagnostic Codes

The following error codes are recorded in the Data Logger log:
0 No Modbus error detected
1 Error due to expansion board fault
2 Modbus CRC error
3 Timeout error waiting for response
4 Slave number error
5 Function code error
6 Length error
7 Value error (value not usable)

05-04-Specific_DL4W-doc_HP-OpenSensor
 Data Logger DL4W / HP-OpenSensor
Nov. 2022

2.3 Sensors Tab

The user defines the MODBUS query parameters for the sensors:
• Period: every 1, 2, 3, 5, 6, 10, 15, 30 or 60 minutes.
• Wait time after power-up: the maximum heating time must be configured across
all remotely powered sensors
• Remote power feed voltage: 12 V or 20 V
(voltage of remotely powered MODBUS sensors)

For each sensor, the user defines:

• a 1–8 character name,
• a unique slave number from 1 to 255,
• if each change of status in the sensor fault:
o must be archived by the Data Logger,
o must trigger a communication to the centralisation system.

2.3.1 OpenSensor Measurement Acquisition

The acquisition of the MODBUS registers is carried out according to the configured
archiving period. It is possible to define 2 archiving periods (a main archiving period, and a
secondary one).
The second archiving period replaces the first one according to one of the following 2
principles, as desired:
• when a logical information is in the active state (DI or Threshold input),
• during the configured daily time slot.

 See § "DL4W: Configuration - Definition of archiving".

05-04-Specific_DL4W-doc_HP-OpenSensor
 Data Logger DL4W / HP-OpenSensor
Nov. 2022

2.4 Definition of Registers

The user can configure up to 14 MODBUS registers, specifying:
• The read order from 1–14: the registers are configured taking this order into account.
• The name of the sensor that the register belongs to: selection from the list of configured sensors.
• The MODBUS address of the register.
• The MODBUS Function code:
o 3: Reading of output words,
o 4: Reading of input words.
• Format of the read value: choose from the list that appears.
• Coding of words in the frame:
o Select the order of word coding based on the list that appears.
o W1 is the most significant word.
• The name of the register (up to 8 characters).
• If the read value must be archived by the Data Logger.

05-04-Specific_DL4W-doc_HP-OpenSensor
 Data Logger DL4W / HP-OpenSensor
Nov. 2022

2.1 Expert Mode

This screen allows users to enter “advanced parameters” (not mandatory): as a general rule,
the configuration of Expert Mode remains optional.

• Sensors: advanced timings settings linked to the communication with each MODBUS
sensor (for example, to optimise energy consumption or to adapt to a non-compatible
sensor with timings configured by default).
• Registers: redefinition of byte coding in a word and specification of the register value
used if there is a read fault.
o Byte B1 is the high byte and byte B2 is the low byte.

05-04-Specific_DL4W-doc_HP-OpenSensor
 Data Logger DL4W / HP-OpenSensor
Nov. 2022

3. Battery life
The classic application is a “Combined sewer overflow” (with an average overflow of 20 mins/day).
In order to limit power consumption, the Data Logger only activates its GSM modem during data
communication phases. Data point no.44 makes it possible to assess the remaining battery life, in days.
Two types of battery can be used to power the Data Logger; only the batteries specified by the device’s
supplier can guarantee its safety and performance.
The estimated battery life below takes into account the following conditions of use:
 Full measuring range: 3 metres.
 Ambient temperature between 5°C and 25°C,
 Average GSM reception level

Communication Battery life

Data Logger Acquisitions and Archiving via 2G/4G with Pack 933
LTE-M & NB-IoT (High-Capacity battery)

DL4W / HP-OpenSensor: Acquisition of the measurement 1 call Nine

(with US sensor only) archived every 15 minutes per day years

Acquisition of the measurement 1 call Five

archived every 5 minutes per day years

DL4W / HP-OpenSensor: Acquisition of the measurement

(with US sensor and archiving:
+ associated CSV sensor) 1 call
• Outside the overflow: per day
10 years
30-min period
• During the overflow: 1-min period

⚠ To preserve the Data Logger’s battery life, it is important to limit the archiving period and the
number of daily transmissions.

05-04-Specific_DL4W-doc_HP-OpenSensor
 DL4W / HP - OpenSensor EPS
Oct.-21 External Power Supply

1 Description
DL4W / HP - OpenSensor EPS (External Power Supply) Data Loggers are designed to be connected to an
external power source (battery, solar panel, microturbine, 230 V mains power supply, etc.) instead of the
case having a built-in battery.

 With an external power supply, a Data Logger makes it possible to communicate at a

frequency of less than five minutes, either between sites with a remote terminal unit, or
when transmitting data to one or two Central Station(s).

For example, in summer, a drinking water reservoir can empty very quickly and the network’s
contract operator can be promptly alerted about this high consumption.

This solution provides operators with more consistent and accurate network control by the Data Logger
and delivers a better service to subscribers:

 Frequently communicating with the SCADA Central Station for regular monitoring of networks
(Drinking water, District metering, Monitoring of water pressure, etc.)
 Monitoring water hammer phenomena
 Powering and controlling higher powered sensors (speed sensors, height radar, physico-chemical,
pH, conductivity, chlorine, etc.)
 Equipping a site with a mains supply
 Monitoring data in real time during a maintenance operation

♦ Example of a LS42 Data Logger powered by a solar panel:

04-09-Specific_DL4W-HP-OpenSensor_EPS
 DL4W / HP - OpenSensor EPS
Oct.-21 External Power Supply

2 Installation
2.1 Connection
The case, identified by its EPS label, is fitted with a circuit board for adjusting the voltage.
Its watertight connector allows the Data Logger to be connected to an external power source
(12 or 24 V solar panels, 6, 12 or 24 V microturbine, 230 V mains supply, etc.).
♦ Power supply voltage between 5 and 30 VDC (12 V or 24 V recommended).
♦ TBTS power supply circuit (in accordance with IEC 61010-1, clauses 6.3.1 and 6.3.2)
♦ Recommended power supply: 3 W
♦ Inrush current : 3 A (1 ms)

Interior view Exterior view

Watertight connector to be screwed

VDC power supply: in

Rouge / Red
Noir / Black

Blanc / White

Not connected

If it is necessary to extend the cable, ensure an appropriate section is used (section to be

determined depending on power consumption and the distance from the source). The Data
Logger’s power supply can be backed up by the installation of an external battery.
In case of intervention on the external power supply of the Data Logger, it is recommended
to the user to configure a derogation; this to prevent loss Data Logger archives which can
then be transmitted to the Centralization System before power failure.

04-09-Specific_DL4W-HP-OpenSensor_EPS
 DL4W / HP - OpenSensor EPS
Oct.-21 External Power Supply

3 Configuration
Normal operating conditions remain unchanged compared with a battery-powered LX (acquisition of two
meters every 15 minutes, AI measurement obtained every 5 minutes).

3.1 Functional features of a “EPS” Data Logger

The differences with a battery-powered Data Logger are as follows:
 The GSM modem remains powered on during the “Diagnostics-Installation” via SOFTOOLS
 In the periodic transmission configuration, either between sites or to a centralisation
system, the periodic values permitted are: 8 hrs, 4 hrs, 2 hrs, 1 hr, 30 min, 15 min, and 5 min.
These periodic transmissions can be disabled

 Data point no. 44 “Remaining battery life” is not a feature of an “EPS” Data Logger.

3.2 Real-time control

The exceptions entered from the Softools, or Web Server interface, make it possible to trigger a cycle
of several periodic transmissions to the Centralisation System(s) (in addition to configured
transmissions) or to modify archiving periods for meters or AI inputs, for a given period of time. The
table below sets out the parameters for these exceptions, which apply to all LX Data Loggers.
To enable real-time monitoring of the measurements taken, for example, during a
maintenance operation, the user can enter the 2-minute value for the transmission period
(parameter 1), solely for an “EPS” Data Logger.

 When the time period for this exception has elapsed, the Data Logger resumes normal
operation, defined in its configuration settings.

Parameters modifiable via exceptions

Web Server values

Function
Parameter Authorised values
no.

Transmission period to the Centralisation System 1 2, 5, 15, 30, 60 or 240 min

Periodic transmissions (∗)
Periodic transmissions cycle length 2 60, 240, 480, or 1,440 min
0 to stop current cycle

Meter and flow archiving period 3 1, 2, 3, 5 or 10 min

Length of application of this 24, 48, 72, etc. Up to 720 hours (∗)
meter and flow archiving period 4 0 to stop current cycle
Archiving
1, 2, 3, 5 or 10 min
AI archiving period (analogue measurements) 5

24, 48, 72, etc. Up to 720 hours (∗)

Length of application of this AI archiving period 6 0 to stop current cycle
1 denotes recipient Central Station no.1
(Central Station or Web Server),
Choice of Centralisation System (1, 2, or 3)
Centralisation system for Data Logger’s periodic transmissions. 7 2 denotes recipient Central Station no.2
3 denotes all configured Centralisation
Systems
Electrovalve command: 0, 1, or 3.
- 1 to lock the electrovalve on track 1
LS-V electrovalve 51
- 3 to lock the electrovalve on track 3
- 0 to unlock (return to configured operating mode)

(∗) Please note: The "Softools” and “Web Server” interfaces do not use the same values for measurements.

04-09-Specific_DL4W-HP-OpenSensor_EPS
 DL4W / HP - OpenSensor EPS
Oct.-21 External Power Supply

4 Specific operating features

4.1 Power outage

In the event of a power outage (mains failure, voltage drop, etc.), the product stops working.
Once the power supply has returned to the Data Logger:
 All the data is lost (current statuses and archived values)
 Al current processing is stopped
 The system “date and time” is restored to its factory settings

4.2 Setting the time and archiving

Once connected to power, data archiving functions are disabled by the Data Logger until the time
has been set.
Synchronising the Data Logger’s time is performed using a local connection with SOFTOOLS, or
when communicating with the supervision system.

04-09-Specific_DL4W-HP-OpenSensor_EPS