- Home
- Domestic appliances
- Climate control
- Temperature & humidity sensors
- Danfoss
- SonoCollect 111
- Operating instructions
7 Reading meters via pulse interface. Danfoss SonoCollect 112, SonoCollect 111
Add to My manuals103 Pages
advertisement
7 Reading meters via pulse interface
A simple way to digitize consumption is the pulse interface.
The method of digitization consists of outputting a certain number of pulses per unit of consumption. This way gives a pulse a weighting. It is therefore possible to infer the consumption value and thus the meter reading by counting the pulses. The weighting of the pulses is meter-specific and usually noted on the meter. Example: Inscription "1000 Imp/kWh" → 1 pulse = 1 Wh, so with each pulse the energy register can be increased by 1 Wh.
Generally, this pulse interface is referred to as the S0 interface. However, this designation is to be understood only as a synonym. There are essentially 3 different realizations:
S0 Type A according to EN 62053-31
S0 Type B according to EN 62053-31
Potential free contact
Physically, the types differ from each other. The real S0 interfaces according to EN 62054-31 are digital current interfaces. A pulse is represented by a current of more than 10 mA. In the idle state, the current is less than 2 mA. Type A and type B differ only in the maximum permitted voltage. Type A uses a maximum of 27
V, type B a maximum of 15 V. The specified maximum current of results in a minimum internal resistance of
1 kOhm. A minimum voltage is required depending on the implementation.
The potential-free contact is easier to implement on the encoder side (meter). This usually simply uses the transistor output of an optocoupler which is directly controlled. The internal resistance is the same as the optocoupler and no minimum voltages are required.
This device has a pulse interface which is compatible with S0 interfaces according to type A and with potential-free contact. Therefore all common meters with pulse interface can be connected.
7.1
Setup of a meter in the web front end
The setup of a meter with pulse interface is only possible manually.
First, the pulse interface must be activated. This is done in the
(see section 4.4). Three modes can be set here:
Configuration tab via the parameter S0 mode
Disabled
Absolute
Relative
The most commonly used mode is Absolute . Here, the meter value is continuously incremented by its value for each pulse. Thus, the recorded measured value should always correspond to the display of the meter.
In the Relative mode, the value is also incremented, but is reset to 0 at the end of the readout period to increment again. This can be used to record the consumption per period.
After activating and setting the mode of the pulse interface, the meter can be added in the Meter tab.
The meter is first created via the Add button or the context menu. In the dialog, the Interface must be set to S0-n (n = channel number). Further data such as manufacturer code, serial number, medium or user label are optional and can be assigned. The user may refer to Table 25 for the Medium field. This ensures a uniform display across all meters. Use the Ok button to accept the entries and the meter is created in the meter list in the Meter tab.
AQ332837053242en-010201 Classified as Business © Danfoss | 2021.03 | 53
Figure 33 Creating a pulse meter (sample data)
A meter value must now be added to the newly created meter. This is done by right-clicking on the newly added pulse meter and selecting the Add value command from the context menu. This command opens a dialogue box for entering the parameters of the meter value.
Figure 34 Creating the meter a pulse meter (sample data)
The parameters Value and Unit should be set to the values in the meter display. The unit may differ, we recommend using basic units such as Wh as opposed to the standard unit often used for energy meters kWh .
The parameter Scale indicates the pulse value. The value entered in Value is incremented by this value during a meter pulse. The calculation of the pulse value results from the indication on the meter, here are a few examples:
1000 Imp/kWh → 0.001 = 1e-3 with unit kWh or 1 = 1e+0 with unit Wh
5000 Imp/kWh → 0.0002 = 2e-4 for unit kWh or 0.2 = 2e-1 for unit Wh
200 Imp/m³ → 0.5 = 5e-1 with unit m³
AQ332837053242en-010201 Classified as Business © Danfoss | 2021.03 | 54
The parameters Value and Scale must be set to ensure correct metering, the other parameters are used for an easily readable data display. The user can refer to Table 26 and Table 27 for the fields Description and
Unit. This ensures a uniform display across all meters.
The measured value set up in this way is now updated by incrementing, depending on the number of pulses acquired, with each readout. For S0 meters, only one meter value can be assigned.
7.2
Troubleshooting the pulse interface
The meter does not increment
Check the technical specification of the pulse generator, especially its internal resistance or its current consumption in active/inactive state. The detection threshold is approx. 8-10 mA.
Check the polarity.
If errors could not be rectified, please contact your local Danfoss support.
AQ332837053242en-010201 Classified as Business © Danfoss | 2021.03 | 55
advertisement
Related manuals
advertisement
Table of contents
- 6 1 Notes and conventions
- 6 1.1 About this document
- 6 1.2 Legal basis
- 6 1.2.1 Copyright protection
- 6 1.2.2 Personnel qualification
- 6 1.2.3 Intended use
- 6 1.3 Symbols
- 6 1.4 Font conventions
- 7 1.5 Number notation
- 7 1.6 Safety guidelines
- 7 1.7 Scope
- 7 1.8 Abbreviations
- 9 2 Presentation of the device
- 9 2.1 Delivery variants
- 9 2.2 Connectors
- 10 2.3 Status LEDs
- 10 2.4 First steps
- 10 2.4.1 Power supply
- 11 2.4.2 Network configuration and first access
- 12 2.5 Specific troubleshooting SonoCollect 112
- 12 2.5.1 All LEDs remain dark, the device does not respond.
- 12 2.5.2 The Power LED flashes green.
- 12 2.6 Typical application scenarios
- 13 2.6.1 Local application without control system
- 13 2.6.2 Remote monitoring without control system
- 13 2.6.3 Remote monitoring with email dispatch
- 13 2.6.4 Remote monitoring with FTP upload
- 13 2.6.5 Remote monitoring with SFTP upload
- 14 2.6.6 Remote monitoring with TCP/HTTP transmission
- 14 2.7 Technical data
- 14 2.7.1 General properties
- 14 2.7.2 Electrical properties
- 15 2.7.3 Further characteristics
- 16 3 Netdiscover tool
- 16 3.1 Locating and accessing devices
- 17 3.2 Network configuration
- 18 3.3 Access to the web-based front end via HTTP
- 18 3.4 Access to the file system via FTP
- 20 3.5 Access to the command line via SSH
- 20 3.6 Mass management
- 22 3.7 Import of a device list
- 23 4 Web-based front end
- 23 4.1 Access via HTTPS
- 24 4.2 General tab
- 25 4.3 Meter tab
- 27 4.3.1 System meter
- 28 4.4 Configuration tab
- 30 4.5 WAN tab
- 32 4.6 Server tab
- 34 4.7 Security tab
- 34 4.8 User tab
- 36 4.9 Log tab
- 37 4.10 Service tab
- 39 4.11 Print page
- 41 4.12 Supplied manual
- 41 4.13 Front-end troubleshooting
- 41 4.13.1 Website or front end cannot be accessed
- 41 4.13.2 Login on website not possible
- 41 4.13.3 All input fields or buttons are greyed out.
- 42 4.13.4 Not all tabs are visible
- 42 4.13.5 Export of the log data of one/several meters is empty
- 42 4.13.6 The log is empty
- 43 5 Reading meters via M-Bus
- 43 5.1 Signalling on the M-Bus
- 44 5.2 Setup of the interface in the web front end
- 44 5.2.1 M-Bus mode
- 45 5.2.2 Addressing, search and search range
- 47 5.2.3 M-Bus baud rate
- 47 5.2.4 M-Bus timeouts
- 47 5.2.5 M-Bus request mode
- 47 5.2.6 M-Bus reset mode
- 48 5.2.7 M-Bus multipaging
- 48 5.3 M-Bus troubleshooting
- 48 5.3.1 Physical troubleshooting
- 49 5.3.2 M-Bus meters are not found
- 50 M-Bus meters are found, but do not show any data
- 50 5.3.3 The search takes a long time
- 50 5.3.4 Device restarts during search
- 51 6 Reading meters via wM bus
- 51 6.1 Signalling via wM bus
- 51 6.2 Troubleshooting the wM bus
- 51 6.2.1 wM-Bus meters are not found
- 52 6.2.2 wM-Bus mounters are found but show no data
- 53 7 Reading meters via pulse interface
- 53 7.1 Setup of a meter in the web front end
- 55 7.2 Troubleshooting the pulse interface
- 55 7.2.1 The meter does not increment
- 56 8 Reading meters via serial interface
- 56 8.1 Setup of the interface in the web front end
- 56 8.1.1 Serial mode
- 56 8.1.2 DLDE baud rate, data bits, stop bits and parity
- 57 8.1.3 DLDE mode
- 57 8.1.4 DLDE timeouts
- 57 8.2 Setup of the meter in the web front end
- 59 8.3 Troubleshooting the serial interface
- 59 8.3.1 Meters are not read out
- 60 9 Transmission of meter data
- 60 9.1 Instances and database
- 60 9.2 General settings
- 60 9.3 Preset data or file formats
- 60 9.3.1 XML format
- 62 9.3.2 CSV format
- 63 9.3.3 JSON format
- 64 9.3.4 User format
- 65 9.4 Data transmission via TCP
- 65 9.5 Data transmission via TLS
- 67 9.6 Sending files via FTP
- 67 9.6.1 Sending files via SFTP or FTPS
- 68 9.7 Sending e-mails via SMTP
- 68 9.7.1 Report as content of the e-mail
- 68 9.7.2 Report as attachment to an e-mail
- 68 9.7.3 SMTP with STARTLS
- 69 9.8 Data transmission via MQTT
- 69 9.8.1 Example Azure Cloud
- 70 9.8.2 Example AWS Cloud
- 71 9.9 Local file storage
- 72 9.10 Script-based report
- 72 9.11 Specific troubleshooting
- 73 10 Advanced configuration options
- 73 10.1 Linux operating system
- 73 10.1.1 User rights
- 73 10.1.2 Command line
- 73 10.1.3 Standard commands
- 74 10.2 Update
- 75 10.3 Configuration file chip.ini
- 84 10.4 Configuration file Device\_Handle.cfg
- 85 10.5 OpenVPN Client
- 85 10.5.1 Configuration of the device
- 85 10.6 Preconfiguration of the meter list
- 86 10.7 Scripting
- 86 10.7.1 XSLT parser
- 86 10.7.2 Report script
- 87 10.7.3 System meter script
- 88 10.8 Media types, measurement types and units
- 92 11 Access to meter data via Modbus TCP
- 92 11.1 General information
- 92 11.2 Function codes and addressing
- 93 11.3 Data display
- 95 11.4 Configuration via web front end
- 95 11.4.1 Modbus mode and Modbus port
- 95 11.4.2 Modbus test
- 96 11.4.3 Modbus swap
- 96 11.4.4 Modbus float only
- 97 11.4.5 Modbus multi slave
- 97 11.5 Instructions for use
- 97 11.5.1 How often is the data updated?
- 97 11.5.2 How can you detect if the meter is read or the value is current?
- 98 11.5.3 Which data type must be used?
- 98 11.5.4 What is the unit of value?
- 98 11.5.5 How many Modbus masters can call data simultaneously?
- 98 11.5.6 How can the data be automatically assigned?
- 99 11.6 Specific troubleshooting
- 99 11.6.1 Why does the value in the Modbus differ from the value on the website?
- 99 11.6.2 Why does the device/the Modbus server not respond?
- 100 12 Access to meter data via BACnet IP
- 100 12.1 General information
- 100 12.1.1 Implemented services
- 100 12.1.2 Supported BACnet Interoperability Building Blocks (Annex K)
- 100 12.2 Configuration via web front end
- 100 12.2.1 BACnet active
- 100 12.2.2 BACnet config network, BACnet IP, BACnet netmask und BACnet broadcast
- 100 12.2.3 BACnet BBMD
- 101 12.2.4 BACnet port
- 101 12.2.5 BACnet device ID, BACnet device name and BACnet location
- 101 12.2.6 Change of Value
- 101 12.2.7 Export of an EDE file
- 101 12.3 Data display
- 101 12.3.1 Meter values
- 102 12.3.2 BACnet Device object
- 103 12.4 Specific troubleshooting