PolluCom® F

Operation Instructions
Communication Interface And Data Logger
PolluCom® F Communication
Content

1. Optical interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Wireless M-Bus (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Wireless M-Bus Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3. Wireless M-Bus communication modes T1 and C1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3.1. Mode T1 uni-directional acc. to OMS; EN 13757-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3.2. Mode C1 uni-directional acc. to OMS; EN 13757-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4. Wireless M-Bus telegram package type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4.1. Long telegram package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4.2. Short telegram package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4.3. Very short telegram package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.5. Wireless M-Bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.6. Impact of wireless M-Bus configuration on lifetime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Info Code and Status Byte of the M-Bus Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1. Info code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2. Status Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4. Wired M-Bus (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.2. M-Bus technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.3. Data reading via wired M-Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
4.3.1. Telegram package "One" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
4.3.2. Telegram package "One Plus" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3.3. Telegram package "All" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3.4. Telegram package "User" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.4. M-Bus communication baud rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.5. M-Bus communication with 2 pulse inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5. Data Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1. Data Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.2. Event Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.3. Error Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
6. Pulse output for remote reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7. Further useful PolluCom® F documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Page 2
 PolluCom® F Communication
This manual focuses on the communication part of PolluCom® F. Further information on PolluCom® F can also be
found in the main PolluCom® F manual, which is available for download at www.sensus.com.
The manual for the MiniCom 3 software can also be downloaded from our website.

1. Optical interface
All PolluCom® F meters are equipped with a standard optical interface designed according to IEC 870-5. The
communication baud rate is selectable between 300 and 9600 Bd. Higher baud rates (Maximum 9600 Bd) are de-
signed for fast reading of the integrated data logger of PolluCom® F. Automatic baud rate detection is between 300
and 2400 Bd.

Parameters can be changed via an optical data coupler (Sensus order no. 184023 for USB port), using Sensus service
software MiniCom 3 starting from version 3.6.0.120. The meter also can be read out via Sensus' readout system Sen-
susREAD starting from version 1.0.2.3. The interface activates by pressing the button of the PolluCom® F. If neither a
valid telegram is received after 5 minutes nor the button pressed, the interface switches off again to save energy. If a
valid telegram is received within this period, the interface is enabled for one hour.

2. Wireless M-Bus (optional)

2.1 General information
If the meter has the wireless M-Bus option, the meter can communicate wirelessly with a stationary collection unit or
a mobile handheld collection unit (e.g. SIRT from Sensus) using the 868 MHz unlicensed radio frequency. In this case
the meter has an integrated antenna. The meter is certified according to the European Open Metering System Spe-
cification (Issue 4.0.2) to ensure the best interoperability with all other OMS compatible reading systems. The radio
data are secured by a 128 bit key.
The radio function will be activated by one of the following steps:
- by pressing the button of the PolluCom® F for 5 seconds for the initial activation
- with the MiniCom 3 software (direct activation or setting activation date)
- Automatically after 100 litres volume
After successful activation the radio symbol will appear on the LC display.

2.2 Wireless M-Bus Technical data

Standard: Open Metering System Specification (Issue 4.0.2); EN 13757-4
Selectable modes: T1/C1 (default : T1, 900 sec transmission interval, long telegram)
Available telegram types:
- Long telegram
- Short telegram
- Very short telegram
Encryption: AES Advanced Encryption Standard, key length: 128 bits
Radio frequency: 868.95 MHz acc. EN13757-4
Transmission power: max. 25 mW (13.9 dBm)
Transmission range: Free field ≥ 400 m

Page 3
PolluCom® F Communication
Power supply: Two lithium batteries type AA
Transmission interval:
- Stationary data reading 15 minutes for T1 mode with long telegram as default
- Mobile data reading 16 seconds for C1 mode with very short telegram as option
- User defined data reading according to telegram type selected from 16 to 14.400 seconds (4 hours)
The factory setting of the clock in the meter is standard Central European Time (GMT +1). There is no automatic
change to summer time.

2.3 Wireless M-Bus communication Modes T1 and C1

2.3.1 Mode T1 uni-directional according to OMS; EN 13757-4
T mode is the Frequent Transmit mode and metering devices periodically send data to collectors which are in the
range. The interval between transmissions is configurable and may range between several seconds to several minu-
tes. This mode can be used either for walk-by/drive-by data collection or for stationary networks.

2.3.2 Mode C1 uni-directional according to OMS; EN 13757-4

This mode is the C (compact) mode. It is similar to the T mode but is more efficient and enables a shorter transmission
time with the same data. This particular mode is useful for walk-by/drive-by data collection.

2.4 Wireless M-Bus telegram package type

2.4.1 Long telegram package
The long telegram package is the longest selectable telegram. The transmission interval default for the long tele-
gram package is set to 900 seconds (15 minutes), and can be set between 30 to 14.400 seconds (4 hours). The long
telegram package is available in both the T1 and C1 mode.

Heat Meter Cooling Meter Heat/Cooling Meter

Current Data Current Data Current Data
Current Date And Time Current Date And Time Current Date And Time
Working Days Counter Working Days Counter Working Days Counter
Heat Energy Cooling Energy Heat Energy
Tariff Energy / Malus Energy ** Tariff Energy / Malus Energy **
Bonus Energy ** Bonus Energy ** Cooling Energy **
Volume Volume Volume
Power Power Power
Flow-Rate Flow-Rate Flow-Rate
Temperature in Warm Pipe Temperature in Warm Pipe Temperature in Warm Pipe
Temperature in Cold Pipe Temperature in Cold Pipe Temperature in Cold Pipe
Pulse-Input 1 ** Pulse-Input 1 ** Pulse-Input 1 **
Pulse-Input 2 ** Pulse-Input 2 ** Pulse-Input 2 **
Info Code Info Code Info Code
Error Hours Error Hours Error Hours

Page 4
 PolluCom® F Communication
Target data (for each item: of last Target data (for each item: of last Target data (for each item: of last
month or last year) month or last year) month or last year)
Target Date Target Date Target Date
Heat Energy Cooling Energy Heat Energy
Tariff Energy / Malus Energy ** Tariff Energy / Malus Energy **
Bonus Energy ** Bonus Energy ** Cooling Energy
Volume Volume Volume
Max. Temperature Warm Pipe * Max. Temperature Warm Pipe * Max. Temperature Warm Pipe *
Max. Temperature Cold Pipe * Max. Temperature Cold Pipe * Max. Temperature Cold Pipe *
Max. Flow Rate * Max. Flow Rate * Max. Flow Rate *
Pulse-Input 1 ** Pulse-Input 1 ** Pulse-Input 1 **
Pulse-Input 2 ** Pulse-Input 2 ** Pulse-Input 2 **

* max value is always the max value of the period ending at the target date (monthly or yearly)
** data points only available if the appropriate option is activated

2.4.2 Short telegram package

The short telegram package transmits the necessary information. The transmission interval for the short telegram
package can be set between 16 and 14.400 seconds (4 hours). The short telegram package is available in both T1
and C1 mode.

Heat Meter Cooling Meter Heat/Cooling Meter

Current Data Current Data Current Data
Current Date and Time Current Date and Time Current Date and Time
Working Days Register Working Days Register Working Days Register
Heat Energy Heat Energy Heat Energy
Cooling Energy
Volume Volume
Power Power
Info Code Info Code Info Code
Target Data Target Data Target Data
Target Date Target Date Target Date
Heat Energy Last Month Or Last Year Cooling Energy Last Month Or Last Heat Energy Last Month Or Last Year
Year
Cooling Energy Last Month Or Last
Year

2.4.3 Very short telegram package

The very short telegram package transmits the basic information of current energy consumption and flow. The send
interval for very short telegram package is set as default 16 seconds and can be selected between 16 to 14.400
seconds (4 hours). The very short telegram package is available in both T1 and C1 mode.

Page 5
PolluCom® F Communication

Heat Meter Cooling Meter Heat/Cooling Meter

Current data Current data Current data
Heat Energy Cooling Energy Heat Energy
Heat Energy Last Month or Last Year Cooling Energy Last Month or Last Cooling Energy
Year

2.5 Wireless M-Bus configuration

The Sensus service software MiniCom 3 is used for configuring or changing the settings of the PolluCom® F para-
meters via optical interface.

I Screenshot of MiniCom 3 configuration overview of PolluCom® F, licensed version I

Users can switch the wireless M-Bus communication on or off with MiniCom 3.

I Screenshot of MiniCom 3 for switching on or switching off wireless M-Bus I

Page 6
 PolluCom® F Communication
Users can also schedule a date for switching the wireless M-Bus radio communication on or off.

I Screenshot of MiniCom 3 for activating wireless M-Bus with planned date I

Users can select the different telegram package types and communication modes in the MiniCom 3 software. They
can also set the different timings for data transmission for wireless M-Bus based on the internal clock of PolluCom® F.

I Screenshot of MiniCom 3 for selecting the wireless M-Bus mode I

For detailed information on the Sensus MiniCom 3 software, please refer to the MiniCom 3 manual or the online help.

2.6 Impact of wireless M-Bus configuration on lifetime

The configuration of transmission modes, telegram types and transmission intervals has a significant impact on the
battery lifetime. Please see the following table for the battery lifetime* at some typical configurations:

Mode T1 Mode C1
Long telegram with 15 minutes interval 13 years 13 years
Short telegram with 3 minutes interval 12 years 12 years

Page 7
PolluCom® F Communication
Short telegram with 32 sec. interval 8 years 8 years
Very short telegram with 16 sec. interval 7 years 8 years
Long telegram with 16 sec. interval 3 years 4 years
The duration of the use of PolluCom® F is governed by national guidelines and may not correspond to the battery
life of the device.

* Approx. 0.5 years (1.5 years for wM-Bus devices) before the battery will be empty and a “low battery” warning
appears on the display.

3. Info Code and Status Byte of the M-Bus Header

3.1. Info Code
PolluCom® F is equipped with an automatic self-checking function. In case an error occurs, the display shows a
four-digit info code with 16 bits in the format "Err XYZW". This information also will be included in the optical, M-Bus
and wireless M-Bus transmission depending on the optional modules and configuration. The info code can be de-
coded as following:

X: maintaining a check on the temperature sensors

Y: maintaining a check on the integrator electronics and communication

Z: error statistics

W: error in measurement electronics

Error examples:
Code Decoding
Err 2010 One or both temperature sensors is/are short-circuited
Err 4010 Return pipe temperature sensor broken/defect
Err 8010 Supply pipe temperature sensor broken/defect
Err 0022 Error in impeller scanning
Err 0200 Battery lifetime less than 6 months
Err 0044 Maximum flow rate exceeded
Err 0048 Ambient temperature too high
For more detailed information on info codes, please contact your local Sensus office.

3.2. Status Byte

Status byte is a one-byte (8 bits) value for indicating the current meter status. No matter which telegram type of M-Bus
or wireless M-Bus is selected, the status byte always will be transmitted in the header of the telegram.

The status byte contains 8 bits information of meter status, which is less than the detailed info code information, but
it is compact and can be used as a first indication on errors or failure situations.

Page 8
 PolluCom® F Communication
The following table shows the related information at each bit of the status byte:
Status bit Meaning Description
0-1 Application status
0 0 No error
0 1 Application busy Not used
1 0 Random application error Bit mask in info code: 0xEF0F
1 1 Unusual status/alarm Bit mask in info code: 0x0004
Overload operation (current flow rate)
2 Low battery Bit mask in info code: 0x0200
Power supply
3 Permanent error Bit mask in info code: 0xE803
Error at temperature measurement;
Error at flow measurement;
Emergency operation mode;
Inlet /outlet temperature sensor is short-wired;
Outlet temperature sensor not connected / sensor broken;
Inlet temperature sensor not connected / sensor breakage
4 Temporary error Bit mask in info code: 0x0004
Overload operation (at current flow)
5 At least one time out of specification Bit mask in info code: 0x0040
Overload operation; ambient temperature > 65 °C
6 Temperature sensor error (sensor Error bit mask in info code: 0xE000
broken, sensor short-wired) Inlet or outlet temperature sensor is short-wired;
Inlet or outlet temperature sensor not connected / sensor
broken
7 Negative temperature difference Error bit mask in info code: 0x1000, but also with a hybrid
meter

4. Wired M-Bus (optional)

4.1 General information
If the meter has the wired M-Bus option, it has a built in M-Bus communication module and can communicate via two
wire cables with M-Bus protocol according to EN 13757-3. The built-in M-Bus interface is galvanically isolated. It is
recommended to use telephone cable J-Y(ST)Y 2x2x0.8mm².

4.2 M-Bus technical data

Primary address: 0 (factory setting); 1 - 250 (configurable)

Secondary address = meter ID (factory setting)

Baud rate: 2400 Bd (factory setting). Automatic baud rate detection is between 300 Bd and 2400 Bd; manually se-
lectable up to 38400 Bd.

Connection polarity: None

Number of possible read-outs: no credits necessary, unlimited

Note: Higher baud rates (>9600*) are designed for fast reading of the integrated data logger of PolluCom® F and
are only available with appropriate M-Bus Master hardware. In case of a multi-slave network and with a longer cable,
higher baud rates may not be reached.

Page 9
PolluCom® F Communication
4.3 Data reading via wired M-Bus
Users can readout the PolluCom® F meter data by using their own M-Bus Master device.
PolluCom® F has four different selectable telegram package types: "One", "One Plus", "All", "User". To choose or
configure the different telegram packages, use Sensus service software MiniCom 3 starting from version 3.6.0.116.

4.3.1 Telegram package "One"

In telegram package "One" current consumption and meter information will be transferred:
Heat/cooling energy, volume, flow, power, inlet temperature, outlet temperature, temperature difference, fabrication
number, customer specific location number.

4.3.2 Telegram package "One Plus"

In addition to Telegram package "One" there will be more meter data transferred in package "One Plus":
Heat/cooling energy, volume, flow, power, inlet temperature, outlet temperature, temperature difference, tariff ener-
gy, cooling energy, identification number of pulse input counter 1, pulse input counter 1, identification number of
pulse input counter 2, pulse input counter 2, fabrication number, customer specific location number.

4.3.3 Telegram package "All"

If this package type is selected, 19 telegrams will be transferred to the M-Bus master.

First telegram package current values:

Heat/cooling energy, volume, flow, power, inlet temperature, outlet temperature, temperature difference, fabrication
number, customer specific location number.

Second telegram package tariff values and error time:

Averaging interval, current date/time, threshold value for tariff, tariff energy, threshold value for inlet temperature for
cooling energy, threshold temperature difference for cooling energy, cooling energy, error hours, and error power
supply hours.

Third telegram package target date value:

Target date, energy at target date, volume at target date, tariff energy at target date, cooling energy at target date,
max. absolute power with time stamp, max. absolute flow with time stamp, max. absolute inlet temperature with time
stamp, max. absolute outlet temperature with time stamp.

16 x telegram packages with monthly values:

Date of data logging with the following data: energy, volume, tariff energy, cooling energy, error hours in month,
error hours of power supply in month, max. power in month with time stamp, max. flow in month with time stamp.

Note: with telegram package “All” all information will be transferred to the M-Bus master. Due to the amount of data
it takes about 17 seconds for the read-out at 2400 baud with MiniCom 3.

Page 10
 PolluCom® F Communication
4.3.4 Telegram package "User"
This telegram package enables the users to define their own telegram according to their needs.
• First part of the telegram is the fixed part, which contains the current meter information and values: Heat/cooling
energy, volume, flow, power, inlet temperature, outlet temperature, temperature difference, fabrication number,
customer specific location number.
• Second part is the free configurable part in which users can choose their own values. Up to 30 values and 234
bytes can be selected for the free configurable part.

An example of a "User" telegram would be:

• First part fixed part: Heat/cooling energy, volume, flow, power, inlet temperature, outlet temperature,
temperature difference, fabrication number, customer specific location number
• Second part freely configurable: info code, date of last saved month, heat energy last month, cooling e n e r g y
last month, heat energy month before last month, cooling energy month before last month, heat
energy last 4 months, cooling energy last 4 months.

The MiniCom 3 software from Sensus must be used to set the user telegram configuration. The command "Set User
Telegram" has to be selected to configure, see the following screenshot:

I Screenshot of MiniCom 3 for selecting the Set User Telegram, licensed version I

In this pop-up window, users can add or remove the values, and set the sequence of data transfer. Please pay atten-
tion to the maximum allowed size of the "User" telegram. By pressing the Ok button, the selected values will be saved
for the "User" telegram.

Page 11
PolluCom® F Communication

I Screenshot of MiniCom 3 for setting the user telegram I

For details on the MiniCom 3 software please refer to the MiniCom 3 manual and the online help.

4.4 M-Bus communication baud rate

The baud rate is set separately for the optical interface and M-Bus. For example, you can set the optical interface to
9600 Bd and at the same time have the baud rate for M-Bus at 19200 Bd.
PolluCom® F can support the baud rate from 300 up to 38400. Automatic detection of the baud rate will be from 300
to 2400. If the high baud rate (> 2400) is selected at the M-Bus
Master side, the PolluCom® F has to be set manually to match the
Master baud rate. Use the Sensus service software MiniCom 3 to
configure the baud rate of PolluCom® F.

I Screenshot of MiniCom 3 for setting baud rate I

Page 12
 PolluCom® F Communication
4.5 M-Bus communication with 2 pulse inputs
If PolluCom® F is ordered with this option, additional to the M-Bus communication, two external consumption meters
(possible medium types: volume, energy, other) with passive remote read-out contact can be connected (reed switch
or open collector) to PolluCom® F. This option has two connection cables (1 cable with two wires, 1 cable with four
wires). The two-wire cable (white and brown wire) is already placed at a suitable place in the M-Bus communication.
Polarity can be disregarded.

Connect the four-wire cable as follows:

White = external meter 1 / positive pole
Brown = external meter 1 / negative pole
Green = external meter 2 / positive pole
Yellow = external meter 2 / negative pole

Technical data contact pulse inputs:

Required closing time: > 125 ms
Input frequency: <3 Hz
Terminal voltage: 3 V
Both contact inputs pre-set in the factory to:
- Input 1: cold water meter, pulse value 10 litres, initial meter reading 0.00 m³
- Input 2: warm water meter, pulse value 10 litres, initial meter reading: 0.00 m³

Use the MiniCom 3 software to change the pulse input setting. Choose the "set pulse input params" in the software
and select the type of meter you want to collect:

Page 13
PolluCom® F Communication

Note: depending on the meter type for the 2 contact inputs you choose, the pulse value also will be changed
accordingly. E.g. for an electricity meter, the unit will be changed to Wh (watt hour) per pulse.

5. Data Logger
All PolluCom® F products are equipped with an integrated data logger. The data logger stores consumption values
and current values. The logger has the possibility to record values of the last 1200 hours, 120 days and 120 months.
The data logger can be read-out via optical interface or M-Bus by means of the service software MiniCom 3. As part
of the integrated data logger, the device also stores up to 500 events and 500 changes of error situations.

I Screenshot of MiniCom 3 for setting and reading of data logger I

Page 14
 PolluCom® F Communication
5.1 Data logger
Users can choose an hourly, daily or monthly log. The maximum readout for the hourly log is the last 1200 hours,
for the daily log it is the last 120 days, and for the monthly log the last 120 months. In the data logger, the following
information of the PolluCom® F meter will be logged:

Header
• Date and time of data record
Meter status
• Error code
• Error hours
Accumulated current values
• Heat or cooling energy
• Volume
• Tariff consumption 1 or Malus (depending on meter type)
• Tariff consumption cooling or Bonus (depending on meter type)
• Consumption pulse input 1
• Consumption pulse input 2
Average values
• Average temperature in inlet pipe
• Average temperature in outlet pipe
Maximum or minimum values
• Maximum flow with date and time
• Maximum power with date and time
• Maximum temperature in inlet pipe with date and time
• Minimum temperature in inlet pipe with date and time
• Maximum temperature in outlet pipe with date and time
• Minimum temperature in outlet pipe with date and time

5.2 Event logger

By reading the event logger, the user can see the last 500 events or changes that occurred at PolluCom® F. The num-
ber of events can be set by MiniCom 3. The events will be registered with the time stamp and have an event ID and
description of the event. The event data (which value has been set) also will be shown in the event logger.

Page 15
PolluCom® F Communication

I Example of reading last 2 events with MiniCom 3 I

The sample picture above shows that we set MiniCom 3 to read the event logger with baud rate 2400 and read the
last two events (start 0, stop 1).

The first event (event 0) shows that the primary address has been changed: the changed value is 1. The second event
(event 1) shows that the system date and time was changed to “25.10.2018 15:26 ”.

5.3 Error logger

By reading the error logger, the user can see the maximum last 500 errors that occurred at PolluCom® F. The events
will be registered with the time stamp and will have an error ID.

The example shows that we have read the last 2 errors (start 0 stop 1) at baud rate 2400 with MiniCom 3, but no error

Page 16
 PolluCom® F Communication
occurred. The only error ID is 0x0000. In case an error occurred, e.g. temperature sensor broken or battery low, the
user will see different error IDs accordingly. The user can consult Sensus on details about the error code.

6. Pulse output for remote reading

With the pulse output option the meter will provide the consumption pulses of energy or volume depending on the
configuration. Connect the two-wire cable to a suitable pulse receiving system or to a contact input of a building
control system. The pulse outputs are potential free and polarity of both wires can be disregarded.

Technical Data
Consumption pulses
Pulse value: 1 kWh or m³
Closing time: 125 ms
Bounce time: none
Max. Voltage: 28 V DC or AC
Max. Current: 0.1 A

Configuration of the pulse output can be done via the Sensus MiniCom 3 software. You can send the meter energy
or volume of meter to the pulse reading systems. The following screenshot shows how to set the parameters using
the MiniCom 3 software:

Page 17
PolluCom® F Communication
7. Further useful PolluCom® F documents

Sensus GmbH Ludwigshafen

Industriestr. 16, 67063 Ludwigshafen
T: +49 (0) 621 6904-1113 F: +49 (0) 621 6904-1409
Email: info.int@xyleminc.com
www.sensus.com

MH 1410 INT • Version 0002, July 2020 • Subject to changes without prior notice.

Page 18