LVxUpdater page: How to change the measurement frequency or the sensor model at the LVxUpdater page?

The LVxUpdater page in a water portal works on the basis of node numbers per sensor (mslvXXXXXX). These can be quickly found/copied via the Measurement points page.

The LVxUpdater page is mainly used to do 2 things:

1: To change the measuring frequency of a sensor. This can also and better be done via the Installation Planner page in the portal, for several sensors at the same time for a maintenance round. That page is more user-friendly. Therefore we recommend changing the measuring frequency of a sensor on that page.

2: If the sensor model needs to be changed after replacement in the field if it is a different model than the one that was installed (in the case of the standard delivery of the sensor). From/to digital 1.4 bar (4m) or digital 2 bar (10m).

How can you change the measurement/transmit frequency or sensor model of a sensor on the LVxUpdater page?:

• Go to the LVxUpdater page in the water portal
• Type the node name in the top input field
• To change 1 ; the measurement frequency of a sensor → fill in the field of the desired Analog Sample Time (how often the logger should take a pressure measurement), and the field of the desired Connection Cycle (how often the logger should connect to make).
• The Baro Sample time field can be left blank (this is possible for all fields you do NOT want to change).

The default settings for the loggers are as follows:
lv5: Analog Sample Time 60 minutes, Connection Cycle 1440 minutes
lv7/lv8 Analog Sample Time 60 minutes, Connection Cycle 240 minutes

• To change 2: the Sensor Model field, first check the option there. Then click below via the drop down menu on the option to which it must be changed.
• Then click at the bottom of Actions on Send -> this puts a message 'ready' for the logger.

The next time the logger connects, it will retrieve that message and adjust its measurement and transmission frequency. It can therefore take up to a day (or longer if there are range issues) before these messages are retrieved. If you want the logger to retrieve this faster, it must be physically reset manually.