Microtronics myDatalogNANOamr User Manual

User manual
300436
Manual for the portable device
myDatalogNANOamr
Rev. 01 valid from:
Firmware version: 03v005
Modem version: 03v005
l Server version: 38.1
l Hardware version: 1.1
l
l
Microtronics Engineering GmbH | www.microtronics.at
Hauptstrasse 7 | 3244 Ruprechtshofen | Austria
Tel +43 2756 77180 23 | Fax +43 2756 77180 33 | [email protected]
Chapter 1 Table of contents
Chapter 1 Table of contents
Manual for the portable device myDatalogNANOamr
1
Chapter 1 Table of contents
3
Chapter 2 Declaration of conformity
9
Chapter 3 Technical data
11
Chapter 4 General specifications
13
4.1 Translation
13
4.2 Copyright
13
4.3 General descriptive names
13
4.4 Safety instructions
13
4.4.1 Use of the hazard warnings
14
4.4.2 Safety and preventative measures for handling GSM/GPRS modems
14
4.4.2.1 Safety and precautionary measures for the GSM/GPRS modem installation
14
4.4.2.2 Safety measures for installing the antenna
15
4.5 Overview
16
4.6 Intended use
16
4.7 General product information
17
4.8 Device labelling
17
4.9 Installation of replacement and wear parts
18
4.10 Storage of the product
18
4.11 Obligation of the operator
18
Chapter 5 Functioning principle
21
5.1 ALOHA transmission mode
23
5.2 Selection of the GSM network
23
5.2.1 Ban list
24
Chapter 6 Storage, delivery and transport
25
6.1 Inspection of incoming deliveries
25
6.2 Scope of supply
25
6.3 Storage
25
Rev. 01
3
6.4 Transportation
25
6.5 Return
26
Chapter 7 Installation
27
7.1 Dimensions
27
7.2 Installing the myDatalogNANOamr
27
7.2.1 Wall mounting
28
7.2.2 Top-hat rail assembly
29
7.2.3 Pipe assembly
31
7.3 Safety instructions for the cabling
7.3.1 Information on preventing electrostatic discharges (ESD)
7.4 Electrical installation
7.4.1 Connecting the meters
32
32
33
7.4.1.1 Connection examples
34
7.4.1.1.1 Elster T-probe
34
7.4.1.1.2 Sensus MS8100
35
7.4.2 Connection of the GSM antenna
35
7.4.3 Optimum antenna positioning for assembly in a shaft
36
7.4.3.1 Influences on the signal quality
36
7.4.3.2 Possibilities for improving the signal quality
37
7.4.3.3 Procedure for determining the optimum position of the antenna
37
7.4.4 Technical details about the meter inputs
37
7.4.5 Technical details about the device operating time
38
Chapter 8 Initial Start-Up
41
8.1 User information
41
8.2 General principles
41
8.3 Placing the system into operation
41
8.4 Testing communication with the device
43
Chapter 9 User interfaces
9.1 User interface on the myDatalogNANOamr
9.1.1 Operating elements
4
32
45
45
45
Rev. 01
Chapter 1 Table of contents
9.1.1.1 Solenoid switch
45
9.1.1.2 Status LED
46
9.2 User interface on the myDataweb-Server
9.2.1 Site configuration
47
47
9.2.1.1 Site
47
9.2.1.2 Comments
47
9.2.1.3 Measurement channels
48
9.2.1.3.1 Basis
48
9.2.1.3.2 Config
49
9.2.1.4 Calculated channels
50
9.2.1.4.1 Basis
50
9.2.1.4.2 Calculation
51
9.2.1.4.3 Alarm
52
9.2.1.5 Internal channels
9.2.1.5.1 Basis
52
52
9.2.1.6 Alarm settings
52
9.2.1.7 Basic setting
53
9.2.1.8 FTP export settings
53
9.2.2 Device configuration
54
9.2.2.1 Comments
54
9.2.2.2 Measurement instrument
54
9.2.2.3 Device-specific settings
55
9.2.2.4 GPRS
56
Chapter 10 myDataweb server
10.1 Overview
10.1.1 Explanation of the symbols
57
57
57
10.2 "Customer" area
58
10.3 "Site" area at customer level
59
10.3.1 Reports
10.4 Recommended procedure
Rev. 01
59
60
5
10.4.1 Creating the site
60
10.4.2 Assigning a device to the customer
61
Chapter 11 WebApp
11.1 General
65
11.2 Creating a "Direct login"
65
11.2.1 iOS (iPhone)
67
11.2.2 Android 2.2
68
11.3 List of sites
11.3.1 Determining the position of the site
11.4 Site info screen
69
70
71
11.4.1 Editing a comment
71
11.4.2 Configuring the measurement channels
72
11.4.2.1 User level 1
73
11.4.2.2 User level 2
74
Chapter 12 XML interface
75
12.1 General
75
12.2 Structure of the database
75
12.2.1 Generally applicable table identifiers
6
65
76
12.2.1.1 mydatalognanoamrid
76
12.2.1.2 geraetid
83
12.2.1.3 bookingline (read only)
85
12.2.1.4 kundeid
85
12.2.2 Device-specific table identifier
87
12.2.2.1 mydatalognanoamr_data
87
12.2.2.2 mydatalognanoamr_channel
88
12.2.2.3 mydatalognanoamr_log
89
12.2.2.4 mydatalognanoamr_user1
89
12.2.2.5 mydatalognanoamr_state
91
12.2.2.6 mydatalognanoamr_aloha
91
12.2.2.7 mydatalognanoamr_pos
91
Rev. 01
Chapter 1 Table of contents
12.2.2.8 mydatalognanoamr_set
12.3 XML export
12.3.1 Configuration of a HTTP-GET command
12.3.1.1 Syntax of the xPath query
92
93
93
94
12.3.1.1.1 List of the fields in a table
94
12.3.1.1.2 List of site types
94
12.3.1.1.3 Filter conditions
94
12.3.1.1.3.1 Example:
95
12.3.1.1.4 Fields
12.3.1.1.4.1 Example
12.3.1.1.5 Data retrieval including index specifications
12.3.1.1.5.1 Example
96
96
97
97
12.3.1.2 Data record compression
99
12.3.1.3 Updating data fields
100
12.3.1.3.1 Example
12.3.2 Format of the XML result
12.3.2.1 Example:
12.4 XML import
100
101
102
102
12.4.1 Transferring data to the myDataweb server
102
12.4.2 Configuration of a HTTP-POST command
103
12.4.3 Structure of the XML file
104
12.4.3.1 Changing existing data
104
12.4.3.2 Importing data
104
Chapter 13 Maintenance
107
13.1 General maintenance
107
13.2 Replacing the battery pack
107
Chapter 14 Removal/disposal
111
Chapter 15 Troubleshooting and repair
113
15.1 General problems
113
15.2 Log entries and error codes
114
Rev. 01
7
15.2.1 Modem error
15.3 Evaluating the device log
120
15.3.1 Evaluating the device log on the myDataweb server
120
15.3.2 Evaluating the device log using myDatanetDeviceConfig
120
Chapter 16 Spare parts and accessories
8
117
121
16.1 Assembly sets
121
16.2 Antennas
121
16.3 Battery packs
121
16.4 Other accessories
121
Chapter 17 Document history
123
Chapter 18 Contact information
125
Rev. 01
Chapter 2 Declaration of conformity
Chapter 2 Declaration of conformity
Rev. 01
9
Chapter 3 Technical data
Chapter 3 Technical data
Voltage supply
Battery pack BP434RLC : 2 x Li-SOCl2 cells fully fabricated with 29Ah
Housing
Material: Luran/PC
Weight: 600g (incl. battery)
Protection class: IP68
Dimensions (WHD): 86 x 155 x 64mm (without connection cable)
Operating
temperature
-20...+60°C, 15...90%rH non-condensing
Storage
temperature
-30...+85°C
Display
LED for indicating the operating state and error codes
Operation
Solenoid switch for initiating ALOHA transmission mode
Antenna
connection
FME-M
Inputs
4 x meters
Minimum pulse length: >1ms
Additional information is provided in "Technical details about the meter inputs"
on page 37.
Data memory
Internal flash memory for up to 17.050 measurement cycles
Data type
s64 (64 Bit signed)
Data
transmission
By means of GSM/GPRS quad-band modem to the respective myDataweb server
SIM
The myDatalogNANOamr is equipped with an integrated SIM chip.
Monthly data
volume
t.b.d. at two-minute measurement cycle and 120-minute transmission cycle
Device operating With the default settings (1 channel, 200 ms reader type, 6 h transmission cycle)
time
up to 3,76 years
Additional information is provided in "Technical details about the device
operating time" on page 38.
Rev. 01
11
Chapter 4 General specifications
Chapter 4 General specifications
The information in this manual has been compiled with great care and to the best of our knowledge.
The manufacturer, however, assumes no liability for any incorrect specifications that may be
provided in this manual. The manufacturer is not responsible for direct, indirect, accidental or
consequential damages which arise from errors or omissions in this manual even if advised of the
possibility of such damages. In the interest of continuous product development, the manufacturer
reserves the right to make improvements to this manual and the products described in it at any time
and without prior notification or obligation.
Note: The specifications in this manual are valid as of the versions listed on the front page. Revised versions of this
manual, as well as software and driver updates are available in the service area of the myDataweb server.
4.1 Translation
For deliveries to countries in the European Economic Area, the manual must be translated into the
language of the respective country. If there are any discrepancies in the translated text, the original
manual (German) must be referenced or the manufacturer contacted for clarification.
4.2 Copyright
The copying and distribution of this document as well as the utilisation and communication of its
contents to others without express authorisation is prohibited. Contraventions are liable to
compensation. All rights reserved.
4.3 General descriptive names
The use of general descriptive names, trade names, trademarks and the like in this manual does not
entitle the reader to assume they may be used freely by everyone. They are often protected
registered trademarks even if not marked as such.
4.4 Safety instructions
For the connection, commissioning and operation of the myDatalogNANOamr , the following
information and higher legal regulations of the country (e.g. ÖVE), such as valid EX regulations as
well as the applicable safety and accident prevention regulations for the respective application case
must be observed.
Please read this manual completely before unpacking, setting up or operating this device. Observe
all hazard, danger and warning information. Non-observance can lead to serious injuries to the
operator and/or damage to the device.
Ensure that the safety equipment of this measurement device is not impaired. Install and use the
measuring system only in the manner and method described in this manual.
Rev. 01
13
Important note: The manufacturer's products that are designed for use outdoors include
extensive protection against penetrating moisture and dust. The operator is responsible for
protecting the joint between the product's sensor cable and the sensor against penetrating
moisture and dust in a suitable way and complying with local safety regulations.
4.4.1 Use of the hazard warnings
DANGER:
Indicates a potential or threatening hazardous situation that will result in death or serious
injuries if not avoided.
WARNING:
Indicates a potential or threatening hazardous situation that can result in death or serious
injuries if not avoided.
CAUTION:
Indicates a potential hazardous situation that can result in minor or moderate injury.
Note: Indicates a situation that does not result in any injury to persons.
Important note: Indicates a situation that can result in damages to this instrument if it is not
avoided. Information that must be particularly emphasised.
Note: Information that supplements the specifications in the main text.
4.4.2 Safety and preventative measures for handling GSM/GPRS modems
Observe the following safety and preventative measures during all phases of installation, operation,
maintenance or repair of a GSM/GPRS modem. The manufacturer shall not be held liable if the
customer disregards these preventative measures.
CAUTION:
The GSM/GPRS modem connection may not be used in hazardous environments.
No guarantee of any kind, whether implicit or explicit, is given by the manufacturer and its
suppliers for the use with high risk activities.
In addition to the following safety considerations, all directives of the country in which the device is
installed must be complied with.
Important note: No liability shall be assumed at any time and under no condition for the
connection via a GSM/GPRS modem for whose use radio signals and networks are utilized,
The GSM/GPRS modem must be switched on and be operated in an area where sufficient
signal strength is present.
4.4.2.1 Safety and precautionary measures for the GSM/GPRS modem installation
l
14
This device may only be installed by a trained technician who applies the recognised
installation practices for a radio frequency transmitter including the of external antennas.
Rev. 01
Chapter 4 General specifications
The device may not be operated in hospitals and/or near medical equipment such as heart
pacemakers or hearing aids.
l The device may not be operated in highly flammable areas such as petrol filling stations, fuel
storage sites, chemical factories and explosion sites.
l Do not operate the device in the vicinity of flammable gases, vapours or dusts.
l Do not subject the device to strong vibrations or impacts.
l The GSM/GPRS modem can cause interference if it is located near television equipment, radios
or computers.
l Do not open the GSM/GPRS modem. Any modification to the equipment is prohibited and
shall lead to loss of the operating licence.
l The use of GSM services (SMS messages/data communication/GPRS etc.) may lead to
additional costs. The user alone is responsible for any damages and costs resulting through
this.
l Do not install the device in any other manner than the one described in the operating
instructions. An improper use will invalidate the warranty.
l
4.4.2.2 Safety measures for installing the antenna
Only use antennas that are recommended or supplied by the manufacturer.
The antenna must be installed at a distance of at least 20 cm from individuals.
l The antenna must not be extended outside protected buildings and must be protected against
lightning strikes.
l The voltage supply must be switched off before replacing the antenna.
l
l
Rev. 01
15
4.5 Overview
Overview myDatalogNANOamr
1 Antenna connector
3 Sensor cable with open ends (channel 1 and
channel 2)
2 Sealed sensor cable (channel 3 and
channel 4)
4 Housing cover
4.6 Intended use
The portable measurement instrument is used to record meter readings. The device can operate
without mains power. The measured and recorded data is stored on a non-volatile memory medium.
This stored data is sent via the mobile network to a central server for further processing. The device
is equipped with an integrated SIM chip for this purpose. The maximum permissible limit values
specified in chapter "Technical data " on page 11 must be observed. The manufacturer shall not be
liable for any operational cases that deviate from these limit values and have not been approved by
the manufacturer in writing.
Note: This device is exclusively intended to be used for the purposes as described above.
Any other use or use beyond what is specified or a modification of the device shall be
deemed to be not for the intended purpose and is not permitted without the express written
consent of the manufacturer. The manufacturer shall not be held liable for any damages that
may result from such unauthorised use or modification. The operator alone bears the
associated risk.
Note: The manufacturer is not liable for data loss of any kind if the device is damaged and
data is not able to be stored correctly.
16
Rev. 01
Chapter 4 General specifications
Note: The integrated SIM chip provides a mobile communications connection to a variety of
international service providers. In order to be able to utilise all functions of the device, you
must ensure that the device is located in the service area of one of these service providers.
You can find a list of all supported countries and associated service providers under
www.microtronics.at/footprint. A Managed Service contract with Microtronics Engineering
GmbH is required for use of the mobile data transmission (see
www.microtronics.at/managedservice). This includes the provisioning of the mobile
communications connection via the network of the service provider included in the abovementioned list.
4.7 General product information
The device is a compact, portable device for recording and transferring meter pulses. The energy
supply is provided via an integrated, replaceable battery pack, that facilitates a device operating
time of up to 3,76 years (see "Technical details about the device operating time" on page 38) using
the default configuration (1 channel, 200 ms reader type, 6 h transmission cycle). 4 inputs are
available to which a meter contact can be connected without an additional energy supply (see
"Technical details about the meter inputs" on page 37). The internal "Battery" and "GSM level"
measurement values (see "Internal channels" on page 52) are also determined. All of the generated
measurement data is temporarily saved on an internal data memory and is then wirelessly
transferred to a central location at a freely selected interval. The device is also configured via this
connection. The device is equipped with an integrated SIM chip.
4.8 Device labelling
The specifications in this user manual apply exclusively to the myDatalogNANOamr device type. The
type plate is located on the top of the device and includes the following specifications:
Type designation
l Serial number
l Environmental conditions during operation
l Hardware revision
l CE marking
l Protection class
l
The correct specification of the type designation and serial number is important for all queries and
spare part orders. Only then can we process requests promptly and properly.
Type plate myDatalogNANOamr
Rev. 01
17
Note: These operating instructions are part of the device and must be available to the user at
all times. The safety instructions included therein must be observed.
DANGER:
It is strictly prohibited to disable the safety equipment or modify its mode of operation.
4.9 Installation of replacement and wear parts
Please be advised that replacement and accessory parts that have not been supplied by the
manufacturer have also not been inspected or approved by it. Installing or using such products and
similar can constructively modify the specified properties of the device in a negative way. The
manufacturer shall not be liable for any damages that arise from the use of non-original parts and
non-original accessory parts.
4.10 Storage of the product
To store the myDatalogNANOamr , activate the transport lock, by setting the "Operation mode" in
the input screen of the myDataweb server to configure the device (see "Device-specific settings" on
page 55) to "OFF". Then activate ALOHA transmission mode (see "ALOHA transmission mode" on
page 23) via the solenoid contact so that the amended configuration is transferred to the
myDatalogNANOamr . During this process, all of the data that has not yet been transferred to the
myDataweb server is transferred. The cables and antenna can be removed as soon as the GPRS
connection has been deactivated - indicated by the status LED going out (see "Status LED" on page
46). Store the myDatalogNANOamr in its original packaging. The battery pack remains in the device.
The myDatalogNANOamr is placed in energy-saving mode by activating the transport lock. However,
it may still occur that the battery pack is fully discharged if the device is stored for very long periods.
Although the configuration and the most recently determined data are definitely maintained. The
transport lock is deactivated again by re-initiating ALOHA transmission mode (see "ALOHA
transmission mode" on page 23) and the myDatalogNANOamr resumes operation according to the
configuration.
4.11 Obligation of the operator
WARNING:
In the EEA (European Economic Area), the national implementation of the framework
directive (89/391/EEC) as well as the associated specific directives and from these in
particular, the directive (89/655/EEC) about the minimum safety and health requirements for
use of work equipment by workers at work, each in their respective version are to be
complied with.
The operator must obtain the local operating licence and the associated documents.
18
Rev. 01
Chapter 4 General specifications
In addition, the operator must comply with the local legal requirements for
the safety of the personnel (accident prevention measures)
the safety of the equipment (protective equipment and maintenance)
l the product disposal (waste disposal law)
l the material disposal (waste disposal law)
l the cleaning (cleaning agents and disposal)
l and the environmental protection amendments.
l
l
Before commissioning, the operator must ensure that the installation and commissioning –
provided these were performed by the operator himself – are in compliance with the local
regulations.
Rev. 01
19
Chapter 5 Functioning principle
Chapter 5 Functioning principle
In the graphic below, all of the components that are part of the myDatanet are illustrated in grey. All
of the other components must be supplied/produced by the customer.
Functional principle of recording meter readings
1
Meter with pulse output (switch contact)
2 myDatalogNANOamr with integrated managed service SIM chip including data transmission
3 Client who access the WebApp via a smartphone
4 myDataweb server to which the data is transferred
5 Client that accesses the interface of the myDataweb server via the web browser
6 Customer-specific server that provides clients with their own interface. The customer-specific
server obtains the data via the XML interface of the myDataweb server (see "XML interface" on
page 75).
7 Client, on which a PC program is running, that obtains its data via the XML interface of the
myDataweb server (see "XML interface" on page 75)
8 Client that accesses the interface of the customer-specific server via the web browser.
Rev. 01
21
Functions and components provided by myDatanet :
l
myDatalogNANOamr
The myDatalogNANOamr is a compact portable device for connecting the meters (IN1-4) to the
myDataweb server (GPRS).
l
Managed Service:
Managed Service is the basis for operating your devices and provides you with a wide range of
services. Managed Service includes updates for device firmware and server software, mobile
data transmission on a global scale and free support. One contact person for the entire
solution.
l
myDataweb server:
Database for saving the measurement data and configurations. Data is either accessed via the
XML interface of the server (see "XML interface" on page 75) or web interface of the server.
The WebApp (see "WebApp " on page 65) has a web interface that is optimised for the
displays of smartphones making it accessible via these devices. However, this is only
displayed if a Level 1 or 2 user has logged in. Users with a higher access level always access
the standard web interface even via a smartphone.
Functions and components provided by the customer:
l
Meter with pulse output:
Meter that includes a switch contact that is compatible with the specifications listed in the
chapter "Technical details about the meter inputs" (see "Technical details about the meter
inputs" on page 37)
l
Customer-specific server with web interface for the clients (optional):
It is therefore possible to create an individual web interface for the clients. Using this method,
the data is read out of the myDataweb server via the XML interface (see "XML interface" on
page 75) by the customer-specific server.
22
Rev. 01
Chapter 5 Functioning principle
5.1 ALOHA transmission mode
ALOHA transmission mode is a special connection mode whereby the myDatalogNANOamr
establishes a connection to the myDataweb server for a period of time configured via the "Basic
settings" configuration section (see "Aloha/wakeup duration" in chapter "Basic setting" on page
53).
ALOHA transmission mode is initiated directly on the device by means of a solenoid switch (see
"Solenoid switch" on page 45). The GSM network is re-selected during this process. This means that
a list of all of the GSM networks in the receiving range of the device is created from which the first
GSM network is then selected that is not on the "Ban list" (see "Ban list" on page 24) and that is
part of one of the service providers supported by the integrated SIM chip (see
www.microtronics.at/footprint).
A speech bubble in the measurement instrument list (see "myDatanet Server Manual" 805002) with
the title "Aloha" indicates that a device is in ALOHA transmission mode.
Clicking on the speech bubble with the "Aloha" title opens the ALOHA data window (see
"myDatanet Server Manual" 805002). It comprises the internal "GSM level" and "battery"
measurement values, as well as the measurement values of the 4 meter inputs. The measurement
values for the last thirty minutes are always shown in the ALOHA data window, which means that
data from a previous ALOHA transmission may be included. The ALOHA data is generated every
three seconds independently of the normal measurement values and is thus not saved with the
standard measurement data.
If a measurement dataset is recorded during ALOHA transmission mode, it is immediately transferred
to the myDataweb server and saved in the standard measurement data.
5.2 Selection of the GSM network
The GSM network to which the device should register must be selected, as the myDatalogNANOamr
is equipped with a SIM chip that provides a mobile connection via a variety of international service
providers (see www.microtronics.at/footprint ). This is completed automatically by the device. During
this process it is taken into consideration if a connection to a certain GSM network is possible but
the use of this GSM network repeatedly causes transmission errors. Such a GSM network is added to
a ban list and is ignored during the next login attempt.
The following conditions ensure that the myDatalogNANOamr logs itself into a GSM network:
l
l
PowerOn
Initiation of ALOHA transmission mode (see "ALOHA transmission mode" on page 23)
Rev. 01
23
l
Expiry of the transmission cycle if the "Interval" connection type was selected (see "Basic
setting" on page 53)
1. The myDatalogNANOamr checks whether any errors occurred during the last login attempt.
No errors:
The myDatalogNANOamr logs into the same GSM network that was also used last time.
Error:
Continue with the next step
Note: A transmission error is not the same as an error that occurs when logging into
the GSM network. It is possible for the login to the GSM network to work correctly but
that a transmission error still occurs.
The following steps are only completed if an error was detected during step 1:
2. The device searches for GSM networks within its receiving range and creates a list of available
GSM networks.
3. A search of the list of available GSM networks is completed and the first GSM network is
selected that is not on the "ban list" and is assigned to one of the service providers
supported by the integrated SIM chip (see www.microtronics.at/footprint).
Note: An explanation detailing the conditions when a GSM network is added to the "ban list" is provided in
"Ban list" on page 24.
5.2.1 Ban list
The ban list provides space for 5 entries and is not saved in a volatile memory. This means that it is
also available following a PowerOn.
If a "BEARER GPRS FAILED" error occurs (see "Modem error" on page 117), an internal counter is
increased by 2 . If the transmission was completed without errors, i.e. all of the data was transferred,
this internal counter is reduced by 1 . The current GSM network is added to the ban list if the internal
counter reaches the value 6 .
The ban list is deleted if no GSM network can be selected from the list of available GSM networks in
the receiving range taking the ban list into consideration. Another search for GSM networks in the
coverage area is completed once the ban list is deleted and the network selection is completed with
the ban list that is now empty (see item 3 in the chapter"Selection of the GSM network" on page
23).
24
Rev. 01
Chapter 6 Storage, delivery and transport
Chapter 6 Storage, delivery and transport
6.1 Inspection of incoming deliveries
Please check the shipment immediately after receiving for completeness and intactness. Immediately report any discovered transport damages to the delivering carrier. Also notify the manufacturer in writing about this without delay. Report any incompleteness in the delivery to the
responsible representative or directly to the company headquarters of the manufacturer within 2
weeks (see "Contact information" on page 125).
Note: Any claims received thereafter will not be acknowledged!
6.2 Scope of supply
The standard scope of supply of the myDatalogNANOamr (206.271) includes:
myDatalogNANOamr
l Antenna 900 FME (206.801)
1)
l BP434RLC (206.725)
l
1) The battery pack (BP434RLC ) was already inserted in the myDatalogNANOamr during production.
Additional accessories such as internal expansions, assembly sets, antennas, accu or battery pack,
sensors, power supply, charging devices, etc., depending on the order. Please check these against
the delivery slip.
6.3 Storage
The following storage conditions must be observed:
myDatalogNANOamr
Storage temperature
-30...+85°C
Humidity
15...90%rH
Note: The battery pack remains in the myDatalogNANOamr during storage.
Store the measurement technology so that it is protected against corrosive and organic solvent
vapours, radioactive emissions and strong electromagnetic radiation.
6.4 Transportation
The myDatalogNANOamr is designed for rough industrial applications. Nevertheless, it should not
be subjected to heavy shocks, bumps, impacts or vibrations. The original packaging must always be
used for transport.
Rev. 01
25
6.5 Return
Every return must be accompanied by a fully field-out return form. This return form is available in
the service area of the myDataweb-Server. An RMA number is mandatory for any returns and can be
obtained from the Support & Service Centre (see "Contact information" on page 125). The return
shipment of the myDatalogNANOamr must occur in the original packaging and with freight and insurance paid to Microtronics Engineering GmbH (see "Contact information" on page 125). Insufficiently
cleared return shipments will otherwise not be accepted!
26
Rev. 01
Chapter 7 Installation
Chapter 7 Installation
Important note: To prevent any damage to the device, the work described in this section of
the instructions must only be performed by qualified personnel.
7.1 Dimensions
Dimensions: Width and height
Dimensions: Depth
7.2 Installing the myDatalogNANOamr
Important note:
Ensure the installation is completed properly.
Comply with the existing legal and/or operational directives.
l Improper handling can cause injuries and/or damage to the devices.
l
l
Rev. 01
27
The installation site must be selected according to specific criteria. The following conditions must be
avoided in any case:
Direct sunlight
l Objects that radiate intense heat (maximum ambient temperature: -20...+60°C)
l Objects with a strong electromagnetic field (frequency converter or similar)
l Corrosive chemicals or gases
l Mechanical impacts
l Direct installation on foot or road ways
l Vibrations
l Radioactive emissions
l
Note: Approx. 15 cm of space should be left beneath the device for the cable connections. Further information
about the installation dimensions can be found in the relevant sub-chapter.
7.2.1 Wall mounting
For wall mounting the optional "Universal bracket for housing myDatanet 86x126 (206.640)"
equipment is required.
Step 1 of the wall mounting
28
Step 2 of the wall mounting
Rev. 01
Chapter 7 Installation
1 myDatalogNANOamr
3 Assembly loop (included in the delivery scope
of 206.640)
2 Delta PT M3.5x8 Torx 15 (included in the
delivery scope of 206.640)
4 Raised head tapping screw 3.5x32 (included
in the delivery scope of 206.640)
1. First attach the assembly loop (3) using the screws (2) included in the "Universal bracket for
housing myDatanet 86x126 (206.640)" equipment set to the myDatalogNANOamr (see "Step 1
of the wall mounting" on page 28).
2. Drilling the holes for mounting:
If you want to use the tapping screws (4) included in the equipment set to secure the
assembly loop (3) to the wall, drill four 6-mm holes in the wall using the drill template as a
guide in accordance with the dimensions in the diagram "Step 2 of the wall mounting" on
page 28.
If you want to use your own fastening screws you can use the drill guide provided in the
equipment set to determine the position of the holes. The diameters are then determined
by the screws that are being used and any wall plugs that may be required.
3. Securing the myDatalogNANOamr to the wall:
If you want to use the tapping screws (4) included in the equipment set, first of all insert
the supplied wall plugs into each of the four drill holes before screwing the
myDatalogNANOamr with the attached assembly loop (3) to the wall (see "Step 2 of the
wall mounting" on page 28).
If you are using your own screws, you must also insert the wall plugs into the holes before
mounting the myDatalogNANOamr with the attached assembly loop (3) to the wall (see
"Step 2 of the wall mounting" on page 28).
7.2.2 Top-hat rail assembly
The optional "DIN rail mounting set for myDatanet housing 86x126 (206.634)" equipment is
required for the top-hat rail assembly.
Rev. 01
29
Step 1 of the top-hat rail assembly
Step 2 of the top-hat rail assembly
1 myDatalogNANOamr
3 Assembly loop (included in the scope of
delivery of 206.634)
2 Delta PT M3.5x8 Torx 15 (included in the
scope of delivery of 206.634)
1. First attach the assembly loop (3) using the screws (2) included in the "DIN rail mounting set
for myDatanet housing 86x126 (206.634)" equipment set to the myDatalogNANOamr (see
"Step 1 of the top-hat rail assembly " on page 30).
2. Place the assembly loop (3) onto the top edge of the top-hat rail. When turned slightly around
the horizontal axis of the myDatalogNANOamr with the assembly loop (3) attached, the
30
Rev. 01
Chapter 7 Installation
assembly loop (3) engages on the top-hat rail (see "Step 2 of the top-hat rail assembly" on
page 30).
7.2.3 Pipe assembly
The optional "Pipe mounting kit for myDatanet housing 86x126 (206.660)" equipment is required
for the pipe assembly.
Step 1 of the pipe assembly
Step 2 of the pipe assembly
1 myDatalogNANOamr
3 Assembly loop (included in the scope of
delivery of 206.660)
2 Delta PT M3.5x8 Torx 15 (included in the
scope of delivery of 206.660)
4 Cable binder (included in the scope of
delivery of 206.660)
Rev. 01
31
1. First attach the assembly loop (3) using the screws (2) included in the "Pipe mounting kit for
myDatanet housing 86x126 (206.660)" equipment set to the myDatalogNANOamr (see "Step 1
of the pipe assembly " on page 31).
2. Position the myDatalogNANOamr with the attached assembly loop (3) on the pipe and use the
supplied cable binders (4) to secure the myDatalogNANOamr (see "Step 2 of the pipe
assembly" on page 31).
7.3 Safety instructions for the cabling
When connections are made to the myDatalogNANOamr , the following warnings and information
must be observed, in addition to the warnings and information found in the individual chapters on
the installation. Further safety information is included in "Safety instructions" on page 13.
7.3.1 Information on preventing electrostatic discharges (ESD)
Important note: Maintenance procedures that do not require the device to be connected to
the power supply should only be performed once the device has been disconnected from the
mains power supply to minimise hazards and ESD risks.
The sensitive electronic components inside the device can be damaged by static electricity, which
can impair the device performance or even cause the device to fail. The manufacturer recommends
the following steps to prevent any damage to the device caused by electrostatic discharges:
Discharge any static electricity present on your body before handling the electronic
components of the device (such as circuit boards and components attached thereto). To do
this, you can touch a grounded metallic surface such as the housing frame of a device or a
metal pipe.
l Avoid any unnecessary movements to prevent the build-up of static charges.
l Use antistatic containers or packaging to transport components that are sensitive to static.
l Wear an antistatic wristband that is grounded via a cable to discharge your body and keep it
free of static electricity.
l Only touch components that are sensitive to electric charges in an antistatic working area. If
possible, use antistatic mats and work pads.
l
7.4 Electrical installation
Important note: Only qualified personnel should undertake the installation described in this
chapter of the operating instructions to avoid any damage to the device.
32
Rev. 01
Chapter 7 Installation
7.4.1 Connecting the meters
Important note:
All cabling work must be performed in the de-energised state.
Ensure installation is completed correctly.
l Comply with the existing legal and/or operational directives.
l Improper handling can cause injuries and/or damage to the instruments!
l Run all data cables so that they do not pose a trip hazard and ensure that cables do not have
any sharp bends.
l The myDatalogNANOamr must not be operated in the field with the lid open.
l
l
Connection of the sensors and power supply
1 Antenna connector
3 Sensor cable with open ends (channel 1 and
2)
Cable length: 3m
Cable length: 1m
2 Sealed sensor cable (channel 3 and 4)
Cable length: 0,12m
Sensor cable with open ends
Channel
Colour
Channel 1
Red
Channel 2
Rev. 01
Function
IN1
Blue
GND
Green
IN2
Yellow
GND
33
Sealed sensor cable
Channel
Colour
Channel 3
Orange
Channel 4
Function
IN3
Brown
GND
Pink
IN4
Black
GND
1. Connect your meters with pulse output to the inputs. If you also require channels 3 and 4, cut
through the sealed sensor cable (2) in front of the sealing cap and strip the wires of the cable
in accordance with your requirements.
Important note: Use suitable means to protect the joint between the sensor cable and
meter or connection cable of the meter against the penetration of moisture and dust.
Please note that the myDatalogNANOamr is only protected against damage to the
external cable sheath relating to the penetration of moisture. If the cable sheath of the
wires is also damaged or the joint is not sealed suitably, protection against the
penetration of moisture can no longer be guaranteed.
2. Connect the antenna (see "Connection of the GSM antenna" on page 35).
3. Initiate ALOHA transmission mode (see "ALOHA transmission mode" on page 23). The status
LED should then start to flicker (see "Status LED" on page 46), indicating that a connection is
being established.
Note: If the myDatalogNANOamr is still in transport mode, the transport lock is deactivated by the initiation
of ALOHA transmission mode and the device starts to operate in accordance with the configuration.
The following step is not mandatory.
4. Check whether the connection to the myDataweb has worked correctly (see "Testing
communication with the device" on page 43).
7.4.1.1 Connection examples
7.4.1.1.1 Elster T-probe
Type
TL1
Elster T-probe
Function
Colour of the cable
Pulse
Yellow
Channel
1
Black
TL2
Pulse
Red
Blue
34
1
myDatalogNANOamr
Function
Colour of the cable
IN1
Red
GND
Blue
IN1
Red
GND
Blue
Rev. 01
Chapter 7 Installation
7.4.1.1.2 Sensus MS8100
Type
A1/B1
Sensus MS8100
myDatalogNANOamr
Function
Colour of the cable Channel Function Colour of the cable
Balanced pulses
White
1
IN1
Red
Brown
Not used
---
---
--A2/B2 1)
Forward pulse
White
1
Brown
Backward pulse
Yellow
2
Brown
A3/B32)
Forward/backward pulse
White
1
Brown
Flow direction
Yellow
---
Brown
A4/B43)
Balanced pulses
White
1
Brown
Error, when open
Yellow
---
Brown
GND
Blue
---
---
---
---
IN1
Red
GND
Blue
IN2
Green
GND
Yellow
IN1
Red
GND
Blue
---
---
---
---
IN1
Red
GND
Blue
---
---
---
---
1) If backward pulses are expected, a "Calculated channel" (see "Calculated channels" on page 50) must be used to
subtract the backward pulses from the forward pulses.
2) The myDatalogNANOamr cannot evaluate type A3/B3 direction signal. This connection example can be used if no
backward pulses are expected.
3) The myDatalogNANOamr cannot evaluate type A4/B4 tamper/error signal.
7.4.2 Connection of the GSM antenna
Important note: To ensure the correct functionality, only use antennas that are supplied by
the manufacturer.
The standard antenna is directly attached to the antenna cable (see "Overview" on page 16) of the
myDatalogNANOamr . In the event of a low radio signal strength, you can use the Flat antenna Smart
Disc FME-F (206.814).
If the length of the 3m antenna cable of the myDatalogNANOamr is not long enough, you can use a
5m Extension cable for Antenna 900 FME (206.805).
Rev. 01
35
1. If you need an antenna extension, connect this to the antenna first.
2. Connect the antenna extension or antenna directly to the antenna cable of the
myDatalogNANOamr (see "Overview" on page 16).
Important note: Do not apply too much force when tightening the antenna. Do not use
any tools to tighten the antenna or antenna extension; only tighten it manually.
The following step is not mandatory.
3. Check whether the connection to the myDataweb has worked correctly (see "Testing
communication with the device" on page 43).
7.4.3 Optimum antenna positioning for assembly in a shaft
7.4.3.1 Influences on the signal quality
Signal losses compared to the reference measurement
Steel cover
up to -30dBm
Concrete cover
approx. -10dBm
Environmental influences
up to -15dBm
Installation height of the antenna
approx. -5dBm/depth of 15 cm
Vertical/horizontal alignment
approx. -10dBm
Horizontal alignment
up to -15dBm
Centre/edge of the shaft
approx. -10dBm
Other influences
Transmission power of the network operator
Note: Practical example:
36
GSM level
-67dBm
Position
Reference measurement outside the shaft
-103 dBm
Measurement at a depth of 1.20 m
-95dBm
Vertically on the edge of the shaft at a depth of approx. 15 cm
-83dBm
Centre of the shaft, horizontal on the steel fitting
-89dBm
Antenna turned by 90°
-78dBm
Centre of the shaft, vertical
-75dBm
Plastic pipe used instead of steel fitting
Rev. 01
Chapter 7 Installation
7.4.3.2 Possibilities for improving the signal quality
Drill a duct for the antenna into the concrete ring on the shaft to bypass the steel cover
Insert the antenna extension in an existing ventilation or supply pipe
l Use special types of antennas (please note: The use of antennas that are not approved by the
manufacturer with devices that are Ex approved will render this approval invalid)
l
l
7.4.3.3 Procedure for determining the optimum position of the antenna
1. Install the myDatalogNANOamr as described in chapter "Installing the myDatalogNANOamr "
on page 27. During this process, also observe the notes regarding the influences on the signal
quality (see "Influences on the signal quality" on page 36).
Note: Have a Extension cable for Antenna 900 FME (206.805) at your disposal just in case.
2. Initiate ALOHA transmission mode (see "ALOHA transmission mode" on page 23).
3. Wait until it is indicated in the list of measurement instruments that the device is in ALOHA
transmission mode. This is indicated by a speech bubble with the "Aloha" inscription.
4. Check the internal "GSM level" measurement value in the incoming data in the ALOHA data
window of the myDataweb server, which can be accessed by clicking on the speech bubble
with the "Aloha" inscription (see "myDatanet Server Manual" 805002). Change the position
of the antenna to obtain the best possible signal quality.
Note: A security stock of 15dBm is highly recommended.
Note: Additional explanation about evaluating the "GSM level":
"GSM level"
>-64dBm
-64 to -73dBm
-74 to -83dBm
-84 to -93dBm
-94 to -107dBm
<= -108dBm
7.4.4 Technical details about the meter inputs
4 inputs are available to which a meter contact can be connected without an additional energy
supply. To save energy, the output voltage Uout is applied to the internal resistor Ri at a sample
Rev. 01
37
interval dependent on the selected "Reader type" (see "Config" on page 49) for a sample time that
is also dependent on the selected "Reader type". The sample interval is 15,6ms for all "Reader
types" for which the signal detection is greater or equal to 64ms. For all of the other "Reader types",
the sample interval is 1ms. This means that as soon as one of the inputs requires the use of the
short sample interval, the short sample interval is used for all of the inputs. This increases the
energy requirement and reduces the device operating time.
The effects of the sample interval on the operating time of the device are detailed in the chapter
"Technical details about the device operating time" (see "Technical details about the device
operating time" on page 38).
The same sample time is used for all of the inputs. This means that the input that requires the
longest sample time specifies the sample time. The effects on the operating time of the device are
insignificant.
Schematic diagram of a meter input
Uout max
3,3V
Iout max
1,5mA
Ri
2k2
Rload max
640
Cload max
10nF
The following conditions must be observed for the pulses to be detected correctly:
Low
< 0,75V
High
> 2,3V
Pulse length
>1ms
7.4.5 Technical details about the device operating time
The following calculations apply to fully charged batteries and 15 minute record intervals.
38
Rev. 01
Chapter 7 Installation
Note: It must be noted that if the transport lock is activated, the myDatalogNANOamr uses a
certain, albeit low, amount of energy even during storage. This means that if a device has
already been stored for a prolonged period that the operating times in the following table
might not be able to achieved anymore.
Configuration
Device operating time
1 channel active
4 ms reader type
6 h transmission cycle
up to 3 years
2 channel active
4 ms reader type
6 h transmission cycle
up to 2,83 years
1 channel active
100 ms reader type
6 h transmission cycle
up to 3,76 years
2 channel active
100 ms reader type
6 h transmission cycle
up to 3,75 years
1 channel active
4 ms reader type
12 h transmission cycle
up to 4,64 years
2 channel active
4 ms reader type
12 h transmission cycle
up to 4,28 years
1 channel active
100 ms reader type
12 h transmission cycle
up to 6,87 years
2 channel active
100 ms reader type
12 h transmission cycle
up to 6,81 years
Important note: Any deviation of the configuration from the values in the table affect the
operating time of the device.
Rev. 01
39
Chapter 8 Initial Start-Up
Chapter 8 Initial Start-Up
8.1 User information
Before you connect the myDatalogNANOamr and place it into operation, you must observe and
comply with the following user information!
This manual contains all information that is required for using the device.
Is intended for technically qualified personnel who have the relevant knowledge and experience in
the area of measurement technology.
Read this manual carefully and completely in order to ensure the proper functioning of the myDatalogNANOamr .
Please contact our technical department if anything is unclear or if you encounter difficulties with
regard to installation, connection or configuration (see "Contact information" on page 125).
If necessary, please also refer to the manuals of the accessory parts when commissioning the complete system. These manuals are included in the scope of delivery of the accessory parts.
8.2 General principles
The entire measurement system may only be placed into operation after completion and inspection
of the installation. Study the manual thoroughly before placing into operation to prevent faulty or
incorrect configuration.
Utilise the manual to familiarise yourself with the operation of the myDatalogNANOamr and the
input screens of the myDataweb-Server before you begin with the configuration.
8.3 Placing the system into operation
Note: It is recommended that the myDatalogNANOamr is first placed into operation in the office before mounting
the device permanently at the place of use. During this process, you should set a site for the later operation on the
myDataweb server (see "myDatanet Server Manual" 805002) and determine a site configuration (see "Site configuration" on page 47). Take the opportunity to get to know the functions of the device in a stable environment.
You can also use suitable test signals to simulate the sensors to establish the optimum configuration of the myDatalogNANOamr prior to its actual first use. This reduces the amount of time required for on-site installation to a minimum.
The following work should be completed at the office before you go to the future location of the
device:
1. If necessary, create a customer on the myDataweb server (see "myDatanet Server Manual"
805002).
Rev. 01
41
2. Within the selected customer, create a site for the operation on the myDataweb server (see
"myDatanet Server Manual" 805002).
3. Configure the created site according to your requirements (see "Site configuration" on page
47).
4. Initiate ALOHA transmission mode (see "ALOHA transmission mode" on page 23). The status
LED should then start to flicker (see "Status LED" on page 46), indicating that a connection is
being established.
Note: If the myDatalogNANOamr is still in transport mode, the transport lock is deactivated by the initiation
of ALOHA transmission mode and the device starts to operate in accordance with the configuration.
5. Move the myDatalogNANOamr from the pool to the selected customer (see "Assigning a
device to the customer" on page 61).
6. Link the myDatalogNANOamr with the created site (see "Site" on page 47).
7. Activate the ALOHA transmission mode (see "ALOHA transmission mode" on page 23) again
so that the site configuration is transferred to the myDatalogNANOamr .
Note: You can also skip this step, as ALOHA transmission mode must also be initiated during the installation on site, which transfers the configuration to the myDatalogNANOamr at the same time.
The following work is completed at the location of the device:
8. Complete all of the steps detailed in the chapter "Connecting the meters" on page 33.
Important note: The last work steps of the chapter "Connecting the meters" on page
33 include the initiation of ALOHA transmission mode. If you intend to install the myDatalogNANOamr in a shaft, the device including the antenna should still be outside the
shaft when ALOHA transmission mode is initiated.
9. Use the WebApp (see "Configuring the measurement channels" on page 72) to adjust the
basic settings of the measurement channels as well as the meter readings to the meter connected to the relevant measurement channel. The myDatalogNANOamr must be in ALOHA
transmission mode for this purpose.
10. If you intend to install the myDatalogNANOamr in a shaft, you must check that the device can
also establish a GPRS connection in the final installation position when the shaft lid is closed
before you leave the place of use. Proceed as follows during this process:
1. Place the device and the antenna in the final installation position (with the shaft lid
open).
2. Initiate ALOHA transmission mode.
3. Close the shaft lid.
4. Wait until it is indicated in the list of sites of the WebApp (see "List of sites" on page 69)
that the myDatalogNANOamr is in ALOHA transmission mode. This is indicated by a
green background colour.
5. Click on the site assigned to the device and check the GSM signal strength displayed in
the upper right corner.
42
Rev. 01
Chapter 8 Initial Start-Up
Note: Information on improving the reception quality is provided in chapter "Optimum antenna positioning for assembly in a shaft" on page 36.
8.4 Testing communication with the device
1. Create a site for the operation on the myDataweb server (see "myDatanet Server Manual"
805002).
2. Configure the created site according to your requirements (see "Site configuration" on page
47).
3. Link the myDatalogNANOamr with the created site (see "Site" on page 47).
4. Initiate the ALOHA transmission mode (see "ALOHA transmission mode" on page 23) so that
the configuration of the site is transferred to the myDatalogNANOamr .
5. Wait until it is indicated in the list of measurement instruments that the device is in ALOHA
transmission mode. This is indicated by a speech bubble with the "Aloha" inscription.
The following steps are only required if you simultaneously want to test the measurement value
acquisition and data transmission.
6. Stop the ALOHA transmission mode by clicking the cross in the speech bubble with the
"Aloha" inscription or wait for the duration of the ALOHA transmission mode. This period can
be set in the basic settings (see "Basic setting" on page 53) of the site configuration. The
default setting is 10 minutes.
7. Then wire up the sensors (see "Connecting the meters" on page 33) and restart the ALOHA
transmission mode.
8. Check the incoming data in the ALOHA data window of the myDataweb server, which can be
accessed by clicking on the speech bubble with the "Aloha" inscription (see "myDatanet
Server Manual" 805002). Particular attention must be paid to the internal"GSM level" measurement value.
Rev. 01
43
Note: Additional explanation about evaluating the "GSM level":
"GSM level"
>-64dBm
-64 to -73dBm
-74 to -83dBm
-84 to -93dBm
-94 to -107dBm
<= -108dBm
44
Rev. 01
Chapter 9 User interfaces
Chapter 9 User interfaces
The configuration of the myDatalogNANOamr is carried out via the web interface on the myDataweb
server (see "User interface on the myDataweb-Server" on page 47), which your responsible sales
partner will provide to you.
9.1 User interface on the myDatalogNANOamr
9.1.1 Operating elements
The operating elements of the myDatalogNANOamr can still be operated when the housing is
closed.
Operating elements
1 Solenoid switch
2 Status LED
9.1.1.1 Solenoid switch
The MDN Magnet (206.803), that is available as an accessory, is required to operate the solenoid
switch. The solenoid switch can be used to initiate the ALOHA transmission mode or to instruct the
myDatalogNANOamr to immediately issue the error/status code.
Operation by the
Device response
user
Press briefly
Status LED illuminates
(approx. one
second)
Operation after releasing the solenoid
switch
Error/status code is issued (see "Status
LED" on page 46)
Press and hold for Status LED flashes three times and
five seconds
then remains on
ALOHA transmission mode
Rev. 01
45
9.1.1.2 Status LED
The status LED is used both to display the error/status codes and to indicate the current operating
state. If the ALOHA transmission mode was activated or the power supply was provided (PowerOn),
the status LED shows the current operating state for ten minutes. During these ten minutes, the
error/status codes are transmitted every three seconds.
Error/status codes
Flashing
Description
code
0x
Transport lock (GPRS OFF, measurement
OFF)
Solution/cause
If the ALOHA transmission mode is
initiated by the solenoid switch, the
myDatalogNANOamr switches back into
"RUN" mode (GPRS ON, measurement
ON).
1x
Last connection OK
---
2x
Last transmission faulty
Try again later
4x
Standby (GPRS ON, measurement OFF)
see "transport lock"
6x
Offline (GPRS OFF, measurement ON)
see "transport lock"
7x
Network block/no matching provider
l
8x
No GSM network
l
Improve position of the antenna
l Check whether the device is located
in the coverage area of a service
provider that is supported by the
integrated SIM chip
(www.microtronics.at/footprint)
l
10x
No GPRS connection
11x
No myDataweb server accessible
12x
Faulty SIM chip
Operating states
Status LED
Flickering Establishing connection
Try again later
Improve position of the antenna
Improve position of the antenna
Check whether port 51241 is enabled
on the myDataweb server
l Try again later
l
Contact support
Description
Lights up
GPRS connection established or solenoid switchactuated
Off
Normal measuring operation according to configuration until the next transmission
46
Rev. 01
Chapter 9 User interfaces
9.2 User interface on the myDataweb-Server
9.2.1 Site configuration
Note: Several of the configuration fields in the following sub chapters may possibly be hidden depending on the
respective user level. In this case, please contact the myDataweb-Server administrator.
Click on the name of the site in the list of sites to get to the input screen for configuring the site (see
"myDatanet Server Manual" 805002).
9.2.1.1 Site
Customer
Specifies to which customer the site is assigned.
icon
Assign site to another customer
Name
Site designation (not relevant for the device or data assignment)[2-50 characters]
Instrument S/N
Serial number of the device that is linked to the site (device assignment!)
9.2.1.2 Comments
Comments
Free comment field (is also displayed below the device type in the site list)
Rev. 01
47
9.2.1.3 Measurement channels
9.2.1.3.1 Basis
Title 1-4
Freely selectable channel title for the meter inputs
Mode
Basic settings for the measurement channel
Off
Measurement channel deactivated
Cnt.Inf Infinite counter
Impulse Metered measurand of a pulse in the "Imp. unit"
Imp.unit String that the WebApp displays as the measuring unit when specifying the
pulse value (see "Configuring the measurement channels" on page 72)
Impulse Factor with which the metered measurand of a pulse is multiplied to convert
scale
the "Imp. unit" to the "Unit" that is used by all of the display elements of
the server (see "Additional information on configuring a meter input:" on
page 48)
Max
Defines the upper scale end of the pointer instruments
Unit
String, which is used as the measurement unit by all of the server display
elements The WebApp also uses this string to display the meter readings.
Decimal Number of decimal places that are used by all of the server display elements
places
Note:
Additional information on configuring a meter input:
Assumption: The meter provides one pulse per 5l. The meter reading should be displayed in [m ] on the
myDataweb server interface
48
Required configuration
Parameter
Impulse
5
Imp.unit
l
Impulse scale
0.001
Unit
m
Value
Rev. 01
Chapter 9 User interfaces
9.2.1.3.2 Config
Reader type
Selection of the reader type
Elster Grey Snapfit (4 ms)
Elster Black Snapfit (4 ms)
Elster T. PROBE (4 ms)
Elster LRP (4 ms)
Elster reader
Minimum signal length for the signal detection: 4 ms
sample interval: 1ms
sample time: 30µs
Elster Q4000 (4 ms)
Elster HRP (4 ms)
Elster ODO7 (4 ms)
Elster HELIX 4000 (4 ms)
Elster PR7 (4 ms)
Elster PR6 (4 ms)
Elster reader
Minimum signal length for the signal detection: 4 ms
sample interval: 1ms
sample time: 40µs
Itron CYBLE K1000 (64 ms)
Itron reader
Itron EMES UNIT (64 ms)
Minimum signal length for the signal detection: 64 ms
sample interval: 15,6ms
sample time: 30µs
Sensus HRI (15 ms)
Sensus reader
Sensus HRI-Mei (15 ms)
Minimum signal length for the signal detection: 15 ms
sample interval: 1ms
sample time: 30µs
Sensus OD01 (4 ms)
Sensus reader
Sensus RD01 (4 ms)
Minimum signal length for the signal detection: 4 ms
sample interval: 1ms
sample time: 30µs
Arad BASIC (4 ms)
Arad reader
Arad 40/50 (4 ms)
Minimum signal length for the signal detection: 4 ms
sample interval: 1ms
sample time: 30µs
Rev. 01
49
Aquamaster (8 ms)
Aquamaster reader
Minimum signal length for the signal detection: 8 ms
sample interval: 1ms
sample time: 30µs
slow (200 ms)
Universal setting for long pulses:
Minimum signal length for the signal detection: 200 ms
sample interval: 15,6ms
sample time: 30µs
medium (64 ms)
Universal setting for medium pulses:
Minimum signal length for the signal detection: 64 ms
sample interval: 15,6ms
sample time: 30µs
fast (4 ms)
Universal setting for short pulses:
Minimum signal length for the signal detection: 4 ms
sample interval: 1ms
sample time: 30µs
fast plus (4 ms)
Universal setting for short pulses and high load resistances:
Minimum signal length for the signal detection: 4 ms
sample interval: 1ms
sample time: 40µs
Colour of the cable
Specifies the colours of the pair of wires for the meter input
9.2.1.4 Calculated channels
Note: The values of the calculated channels are calculated directly for the data output (display on myDataweb
server or download from myDataweb server). They are not saved in the server database.
9.2.1.4.1 Basis
Title 1-5
Freely selectable channel title for the calculated channels [0-16 characters]
50
Rev. 01
Chapter 9 User interfaces
Mode
Possible calculation modes for the calculated channels
Off
---
Calculated channel deactivated
Table
Min
Defines the lower scale end of the pointer instruments
Max
Defines the upper scale end of the pointer instruments
Unit
String, which is used as the measurement unit by all of the server
display elements
Decimal
places
Number of decimal places that are used by all of the server display
elements
Invert
Inverts the input signal
Digital
+, -, x, / Min
Defines the lower scale end of the pointer instruments
Max
Defines the upper scale end of the pointer instruments
Unit
String, which is used as the measurement unit by all of the server
display elements
Decimal
places
Number of decimal places that are used by all of the server display
elements
Shifts element down
Shifts element up
9.2.1.4.2 Calculation
Off
---
Calculated channel deactivated
Table
Source
Selection of the channel from which the input data is used
Opens the screen for entering the values table (between the table rows is
interpolated linearly, values outside of the defined table are extrapolated
linearly.)
Digital
+, -, x, /
Source
Selection of the channel from which the input data is used
High level
Signal recognition level
Source
Selection of the channel from which the input data is used
+, -, x, /
Source
Rev. 01
Selection of the channel from which the input data is used
51
9.2.1.4.3 Alarm
Note: The alarm levels for calculated channels can only be evaluated once the device has transmitted the
measurement data to the myDataweb server.
Alarm low
An alarm is initiated if the measurement value drops to or below this value.
Alarm high
An alarm is initiated if the measurement value meets or exceeds this value.
Hyst %
Hysteresis for all-clear (e.g. hyst = 5%, alarm or warning at 100 -> all-clear at 95)
9.2.1.5 Internal channels
9.2.1.5.1 Basis
Battery title
Freely selectable channel title for the battery voltage
Unit
String, which is used as the measurement unit by all of the server
display elements
GSM level title Freely selectable channel title for the GSM level
Unit
String, which is used as the measurement unit by all of the server
display elements
9.2.1.6 Alarm settings
Acknowledgement Standard
The global server setting is used to determine whether to
acknowledge alarms automatically or manually (see "myDatanet
Server Manual" 805002).
automatic
Alarms are acknowledged automatically as soon as all of the
messages have been sent. If SMS that have a tariff with a delivery
confirmation function have also been sent, acknowledgement is
provided after delivery confirmation.
Manual
Alarms must be acknowledged by the user.
Offline alarm
Alarm in the event that the device does not respond for longer than the set
transmission cycles
Transfer volumes Standard
52
The configuration for the transfer volume alarm is adopted from
the global server setting (see "myDatanet Server Manual"
805002).
Off
The transfer volume alarm is deactivated.
Individual
The level at which the transfer volume alarm should be triggered
can be entered in the adjacent field in KB.
Rev. 01
Chapter 9 User interfaces
9.2.1.7 Basic setting
Connection type
Interval
The device registers in the transmission cycle.
Aloha/Wakeup duration Aloha/Wakeup duration connection
Transmission cycle
Time between transmissions
Transmission time
Time at which the device establishes a connection to the server regardless
of the transmission cycle. However, this additional transmission is only
completed if a transmission has not already been completed 5 minutes
before this time or if a transmission will not be completed 10 minutes
after this time.
If an additional transmission has been initiated, the internal meter of the
device, that determines the time of the transmission, is reset. This means
that the next transmission is completed exactly after the time specified via
the "transmission cycle" parameter.
Record interval
Time between measurement data recordings
Time zone
Regional settings (not relevant for raw measurement data as this is stored
in the UTC)
Daylight saving time
Configuration for automatic time adjustment
Standard
The configuration for the time adjustment is adopted
by the global server setting (see "myDatanet Server
Manual" 805002).
Off
Automatic time adjustment deactivated
USA
Predefined setting for the American area
EU
Predefined setting for the European area
Position cycle
Position update interval
Default report
Selection of the report that is loaded by clicking on the device link in the
maps
Switch contact mode
Off
The default graphic is loaded.
"Name of a
report"
The selected report is loaded.
Operation that is triggered when the solenoid switch is activated, is
currently not modifiable
9.2.1.8 FTP export settings
Note: This configuration section is only visible if the "FTP Agent Extended" licence for the myDataweb-Server has
been enabled.
Rev. 01
53
FTP export
profile
off
FTP export deactivated
"Name of an
FTP export
profile"
List with the FTP export profiles that were created on the Server
(for creating an FTP export profile, see "myDatanet Server
Manual" 805002).
Settings of the
selected profile
shows an overview of the most important parameters of the selected FTP export
profile
FTP directory
makes overwriting the standard directory of the selected FTP export profile
possible [0-100 characters]
9.2.2 Device configuration
Note: Several of the configuration fields in the following sub chapters may possibly be hidden depending on the
respective user level. In this case, please contact the myDataweb-Server administrator.
You can reach the input screen for configuring the device by clicking on the serial number in the site
list (see "myDatanet Server Manual" 805002) or by clicking on the device name in the device name
list (see "myDatanet Server Manual" 805002).
9.2.2.1 Comments
Comments
Empty comment field (is also displayed below the site name in the measurement instrument
list)
9.2.2.2 Measurement instrument
Customer
Name of the customer to whom the measurement instrument is assigned
IMSI
IMSI of the used SIM chip or SIM card
Serial number Serial number of the instrument
Instrument
class
The instrument class of the site and instrument must match for an instrument to be
able to be connected to a site.
Telephone
number
Telephone number of the SIM card. The control SMS messages (e.g. wakeup) are
sent to this number. Format: +43555837465
Instrument
flags
Additional information on the instrument class (for internal use)
Firmware
version
Current software version installed on the measurement controller
Modem
version
Current software version installed on the modem controller
OS version
OS version of the modem
54
Rev. 01
Chapter 9 User interfaces
Last
connection
In each case, the last time stamp of the affected operation
Last wakeup
Last
disconnection
Last
transmission
error
Last Aloha
connection
Firmware
update
Off
Firmware update is deactivated
On
As soon as a new version of the selected firmware type is
available, this is installed immediately.
Even if tag is missing
Firmware is also transmitted to the device if the device has
not transmitted the current firmware version to the server.
(NOT RECOMMENDED!)
Allow downgrade
Facilitates the installation of an older firmware version than
the one on the device. (NOT RECOMMENDED!)
Once
Performs a single firmware update. If no new firmware is
available or the firmware was installed successfully, the
firmware update is automatically switched to "OFF".
Firmware type Released
Only firmware versions that have successfully undergone
internal and field testing are installed (this practically
eliminates malfunctions).
Release candidate
Only firmware versions that have successfully undergone
internal testing are installed (malfunctions cannot be
excluded).
Beta release
Even firmware versions that have not successfully
undergone all of the internal tests are installed
(malfunctions may occur).
9.2.2.3 Device-specific settings
Operating
type
Rev. 01
HOLD
Measurement: OFF, transmission: ON
RUN
Measurement: ON, transmission: ON
OFF
Measurement: OFF, transmission: OFF
OFFLINE
Measurement: ON, transmission: OFF
Aloha
Reserved for internal use
55
9.2.2.4 GPRS
SIM tariff
Selected SIM tariff
56
Rev. 01
Chapter 10 myDataweb server
Chapter 10 myDataweb server
Note: All of the screenshots show version 38.1 of the myDataweb server using the standard colour scheme. Newer
versions may include minor changes to the appearance of the server.
10.1 Overview
Overview of the myDataweb server
1 Tabs to switch between the individual server
areas
5 Logout the active user
2 Freely selectable logo
6 Call up the help menu
3 User group to which the user that is currently 7 Switches to the "Data exports" area to
logged in is assigned
configure the data export. This tab is only
visible if at least the licence for one export
variant is available.
4 Opens the screen to input the global settings 8 Opens the input screen to upload a XML file.
for the server
This tab is only visible if the licence for the
XML import is available.
10.1.1 Explanation of the symbols
Adds a new entry to the current list (reports, sites, users, etc.).
Deletes the adjacent element (reports, sites, users, etc.) from the list.
Calls up the input screen to edit the adjacent element (reports, sites, users, etc.).
Rev. 01
57
10.2 "Customer" area
Overview of the "Customer" area
1
Current "Overview map" on which the sites can be placed
2 Adds a new customer
3 Opens the input screen for configuring the customer
4 Deletes the customer
5 Comment that can be entered in the configuration of the customer
6 If a default report was defined, the default report is accessed by clicking on the name of the
customer. Otherwise the "Sites" area at customer level is opened by clicking on the name of
the customer (see ""Site" area at customer level" on page 59 or "Reports" on page 59).
7 Customer's address that can be entered via the input screen for configuring the customer
8 Symbol via which an image file can be loaded on to the server as an "Overview map"
To remove the "Map" again, open the upload dialogue again and click on "Submit" without
selecting an image file beforehand.
58
Rev. 01
Chapter 10 myDataweb server
10.3 "Site" area at customer level
Overview of the "Sites" area at customer level
1 Symbol via which an image file can be loaded on to the server as a "Map"
To remove the "Map" again, open the upload dialogue again and click on "Submit" without
selecting an image file beforehand.
2 Current "Map" on which the sites can be placed
3 Symbol that represents a site on the "Map"
4 List of reports (see "Reports" on page 59)
5 List of sites (see "Site" on page 47)
10.3.1 Reports
The reports provide a variety of options to display graphs of the data on the web interface of the
myDataweb server or to download the data from the myDataweb server. Detailed instructions on
creating and handling the reports is provided in myDatanet Server Manual (805002).
Rev. 01
59
10.4 Recommended procedure
10.4.1 Creating the site
Note: Some of the fields mentioned in the following chapters may be hidden depending on the respective user
level. In this case, please contact the administrator of the myDataweb server.
Detailed instructions on creating a new site are included in myDatanet Server Manual (805002).
1. Log in via the web interface on the myDataweb server. You will receive the web address from
your responsible sales partner.
Login form of the myDataweb server
2. Click on the "Customer" menu item of the myDataweb server to call up the list of available
customers. Select an existing customer or create a new customer.
Selecting the customer
1 Menu item to call up the list of customers
3 List of available customers
2 Creating a new customer
3. Click on the "Sites" menu item of the myDataweb server to call up the list of available sites.
Create a new "myDatalogNANOamr " type site.
60
Rev. 01
Chapter 10 myDataweb server
Creating the site
1 Menu item to call up the list of sites
3 Selection of the type of site
2 Creating a new site
4. Link the site with the myDatalogNANOamr by selecting the serial number. If the serial number
of your device is not included in the list, you must first of all assign the device to the customer
(see "Assigning a device to the customer" on page 61) or the device is already assigned to a
different site. More detailed information on this is provided in myDatanet Server Manual
(805002).
Linking the device and site
1 Device assignment
2 List of devices that have not yet been
linked with a site
10.4.2 Assigning a device to the customer
Note: Some of the fields mentioned in the following chapters may be hidden depending on the respective user
level. In this case, please contact the administrator of the myDataweb server.
Detailed instructions on shifting the devices are provided in myDatanet Server Manual (805002).
Rev. 01
61
1. Log in via the web interface on the myDataweb server. You will receive the web address from
your responsible sales partner.
Login form of the myDataweb server
2. Click on the "Pool and Aloha" menu item of the myDataweb server to access the list of
devices that are in ALOHA transmission mode.
Assigning a device to the customer
1 Menu item to call up the list of devices that 4 Opens the dialogue to select the customer
are in ALOHA transmission mode
to whom the device should be assigned
2 List of devices in ALOHA transmission
mode
5 Selection of the customer to whom the
device should be assigned
3 Filter for the list of measurement
instruments
6 List of measurement instruments
3. Initiate ALOHA transmission mode on the device. Instructions for this are provided in "ALOHA
transmission mode" on page 23.
62
Rev. 01
Chapter 10 myDataweb server
4. Use the filter to find the required device in the list of measurement instruments. Click on the
symbol to open the dialogue to select the customer (see "Assigning a device to the customer"
on page 62) and assign the device to the selected customer.
Rev. 01
63
Chapter 11 WebApp
11.1 General
The WebApp is not a native application that you have to install on your smartphone, it is instead an
optimised web interface of the myDataweb server for the displays of these devices. You therefore
only have to access the web interface of the myDataweb server via the browser of the smartphone.
However, this optimised interface is only displayed if a Level 1 or 2 user has logged in. Users with a
higher access level always access the standard web interface and the full functional scope even via
a smartphone.
11.2 Creating a "Direct login"
It is possible to create a favourites link on the smartphone that uses the "Direct login" function of
the myDataweb server. Such a direct link includes the "Direct login character string" that clearly
identifies the user on the myDataweb server and thus means that the login dialogue can be skipped
and direct access to the list of sites is granted. A "Direct login" link can only be created if the "Direct
login" function has been activated for the relevant user (see "myDatanet Server Manual" 805002)
and requires the login process to be completed once via the login dialogue. The "Direct login"
function is activated for all users as standard.
Important note: Do not give your "Direct login" link to anyone else otherwise they would be
granted access to your account on the myDataweb server.
The following two chapters describe how to create a "Direct login" for iOS (iPhone) and Android. For
other mobile operating systems, please refer to your smartphone's operating instructions.
For both systems, first of all enter the web address of the myDataweb server. You will receive the
address from your responsible sales partner. This will take you to the login dialogue.
Rev. 01
65
Login dialogue (iPhone)
After you have entered your login details, you can access the list of sites
Note: The "Direct login" link can only be created from the list of sites.
66
Rev. 01
11.2.1 iOS (iPhone)
Select the
List of sites (iOS)
symbol to open the submenu.
Submenu for creating a link
Use the "Add to home screen" button to add a "Direct login" link as a symbol on your "Home
screen" or use the "Add bookmark" button to bookmark your "Direct login" link.
Rev. 01
67
11.2.2 Android 2.2
Select the submenu button to access the browser's basic menu and then select the
symbol to expand the menu.
List of sites (Android)
Submenu for creating a link
Use the "Add shortcut to home" button to add a "Direct login" link as a symbol on your "Home
screen".
68
Rev. 01
11.3 List of sites
You will have access to the list of sites once you have logged in via the login dialogue.
List of sites sorted according to distance
List of sites sorted according to title
1 Text input field to filter the list of sites
5 Distance and direction to the site
2 Indicates that the list of sites is sorted
6 Title of the measurement channels
according to distance. Clicking will change the
sorting according to site titles.
3 Title of the site
7 Position data is not available for the site
4 Serial number of the device linked to the site 8 Indicates that the list of sites is sorted
according to titles of the sites. Clicking will
change the sorting according to distance.
Sites for which the assigned device is in ALOHA transmission mode (see "ALOHA transmission
mode" on page 23) are indicated by a green background colour. A blue background indicates that
the device linked to the site currently has not established an active connection to the myDataweb
server.
Rev. 01
69
List of sites: devices in ALOHA transmission mode
1 Device offline
2 Device in ALOHA transmission mode
11.3.1 Determining the position of the site
The position of the site must be determined to indicate the distance to the site in the list of sites. If
you are at the site, you can use the GPS receiver of your smartphone to assign your current position
to the site via the WebApp . To do this, click on the distance value (position data is already
available) or on the symbol that indicates that there is no position data available yet.
List of sites
Assigning the position
1 Distance value (position data is already
available)
2 No position data available yet
70
Rev. 01
11.4 Site info screen
The site info screen is accessed by clicking on the site in the list of sites (see "List of sites" on page
69). In this case, the background colour will indicate the connection status (green for ALOHA
transmission mode, blue for offline) of the device connected to the site.
Site info screen (ALOHA transmission mode active)
1 Back to the list of sites
5 Time stamp of the last measurement value
2 Title of the site
6 Last measurement value (meter reading) 1)
3 GSM signal strength
7 Colours of the pair of wires for the
measurement channel
4 Title of the measurement channels
8 Comment on the site
1) The measurement channel is deactivated if no meter reading is displayed. It cannot be activated via the WebApp but can
only be activated via the standard web interface (see "Measurement channels" on page 48).
11.4.1 Editing a comment
Clicking on the comment (see "Site info screen" on page 71) opens the screen to enter the
description of the site.
Rev. 01
71
Editing the comment
1 Back to the site info screen without saving
3 Input field for a comment about the site
2 Title of the site
4 Save change and go back to the site info
screen
11.4.2 Configuring the measurement channels
To configure the measurement channel, click on the relevant entry in the info screen of the site (see
"Site info screen" on page 71). In this case, the background colour will also indicate the connection
status (green for ALOHA transmission mode, blue for offline) of the device connected to the site.
Changes cannot be made in offline mode. Which of the input fields can be edited in ALOHA
transmission mode is dependent on the authorisation level of the user who is logged in.
Screen for configuring a measurement channel (offline)
1 Back to the site info screen
72
7 String that is used as the measuring unit for
the meter readings 2)
Rev. 01
2 Title of the site
8 Selection of the reader type (see "Config" on
page 49) 3)
3 Title of the measurement channel
9 Unit in which the metered measurand of a
pulse has to be entered 2)
4 Time stamp of the last measurement value
10 Metered measurand of a pulse in the "Imp.
unit"3)
5 Last measurement value (meter reading) 1)
11 Input field to change the title of the
measurement channel3)
6 Colours of the pair of wires for the
measurement channel
1) The measurement channel is deactivated if no meter reading is displayed. It cannot be activated via the WebApp but can
only be activated via the standard web interface (see "Measurement channels" on page 48).
2) Can only be edited via the standard web interface (see "Measurement channels" on page 48)
3) The input fields can only be edited when the myDatalogNANOamr is in ALOHA transmission mode.
11.4.2.1 User level 1
Users of authorisation level 1 can only edit the pulse value and meter reading.
Screen for configuring a measurement channel (ALOHA, level 1)
Rev. 01
73
1 Input field to change the meter reading (can
only be edited when the measurement
channel is activated)
3 Button for accepting the configuration
changes
2 Metered measurand of a pulse in the "Imp.
unit"
11.4.2.2 User level 2
Users of authorization level 2 can edit the reader type and title of the measurement channel in
addition to the pulse value and the meter reading.
Screen for configuring a measurement channel (ALOHA, level 2)
1 Input field to change the meter reading (can
only be edited when the measurement
channel is activated)
4 Input field to change the title of the
measurement channel
2 Selection of the reader type (see "Config" on 5 Button for accepting the configuration
page 49)
changes
3 Metered measurand of a pulse in the "Imp.
unit"
74
Rev. 01
Chapter 12 XML interface
Chapter 12 XML interface
Important note: The relevant licences are required on the myDataweb server to use the XML
interface. If the licence is not available for the XML export, the following message is
displayed for every request: "-ERR: XML agent is not active on this server!".
Likewise, if the licence is missing for the XML import, the following message is returned for
each import attempt: "-ERR: XML upload is not active on this server!". In this case,
contact your responsible sales partner.
12.1 General
The XML interface is provided to export data from and import data to the myDataweb server.
However, this is not just limited to the pure measurement data but includes all of the data provided
by the myDataweb server (e.g. measurement data, configurations, log entries, alarm lists, etc.). It is
therefore possible for the customer to completely dispense with the interface of the myDataweb
server and to create his own user interface. A specially developed PC program or web interface can,
for example, be used for this purpose.
12.2 Structure of the database
Structure of the database
Rev. 01
75
Generally applicable table identifiers
Identifier
mydatalognanoamrid
Site configuration
Description
(see "mydatalognanoamrid" on page 76)
geraetid
Devices
(see "geraetid" on page 83)
bookingline
Connection list
(see "bookingline (read only)" on page 85)
kundeid
Customers
(see "kundeid" on page 85)
Device-specific table identifier
Identifier
Allocation
mydatalognanoamr_data
Site
Measurement data
mydatalognanoamr_channel Site
Configuration of the meter inputs
Description
(see "mydatalognanoamr_channel" on page 88)
mydatalognanoamr_log
Device
Device log
(see "mydatalognanoamr_aloha" on page 91)
mydatalognanoamr_user1
Site
User config 1
(see "mydatalognanoamr_user1" on page 89)
mydatalognanoamr_state
Device
Device status
(see "mydatalognanoamr_state" on page 91)
mydatalognanoamr_aloha
Device
Aloha data
(see "mydatalognanoamr_aloha" on page 91)
mydatalognanoamr_pos
Device
Position and network information
(see "mydatalognanoamr_pos" on page 91')
mydatalognanoamr_set
Site
Provided to set the meter readings to the required
value
(see "mydatalognanoamr_set" on page 92)
12.2.1 Generally applicable table identifiers
12.2.1.1 mydatalognanoamrid
This table includes all of the site-specific configurations.
76
Rev. 01
Chapter 12 XML interface
name
Site designation (not relevant for the device or data assignment)[2-50 characters]
timezone
Regional settings (not relevant for raw measurement data as this is stored in the UTC)
Value
99.00
Explanation
The regional setting for the site is adopted from the global server setting.
-12.00
UTC -12 hours
:
:
+14.00
UTC +14 hours (Kiritimati)
summertime
Configuration for automatic time adjustment
Value
*DEFAULT*
Explanation
The configuration for the time adjustment is adopted by the
global server setting
*OFF*
Automatic time adjustment deactivated
USA;99CC96152B000000
Predefined setting for the American area
EU;99CC95A627080884
Predefined setting for the European area
alert_mode
Setting for acknowledging the alarms
Value
0
Explanation
The global server setting is used to determine whether to acknowledge alarms
automatically or manually
1
Alarms are acknowledged automatically as soon as all of the messages have
been sent. If SMS that have a tariff with a delivery confirmation function have
also been sent, acknowledgement is provided after delivery confirmation.
2
Alarms must be acknowledged by the user.
Rev. 01
77
transfer_alerts
Alarm in the event that the device does not respond for longer than the set transmission cycles
Value
Explanation
0
No alarm settings
1
standard (>2x transmission cycles)
2
immediately (>1x transmission cycle)
3
medium (>5x transmission cycles)
4
long (>10x transmission cycles)
5
extra long (>20x transmission cycles)
max_transfer_volume
Settings for the transfer volume alarm
Value
-1
Explanation
The configuration for the transfer volume alarm is adopted from the global server
setting
0
The transfer volume alarm is deactivated.
>0
Threshold at which the transfer volume alarm should be triggered [KB]
max_transfer_volume_kb
This is a "Ghost" field, the content of which always corresponds to that of the "max_transfer_
volume" field.
comment
Free comment field (is also displayed below the device type in the site list)
loc_site_lat
Specification of the geographical latitude where the site is located [°]
loc_site_long
Specification of the geographical longitude where the site is located [°]
loc_alarm_rad_mode
A radius can be defined for a site. Depending on the settings for this parameter, an alarm is
triggered if the device leaves this radius.
Value
Explanation
0
Radius monitoring deactivated (no alarm)
>0
78
Specification of the alarm radius [km]. An alarm is triggered if the device leaves the
radius.
Rev. 01
Chapter 12 XML interface
loc_alarm_rad
This is a "Ghost" field, the content of which always corresponds to that of the "loc_alarm_rad_
mode" field.
view
Selection of the report that is loaded by clicking on the device link in the maps
Value
*OFF*
Explanation
The default graphic is loaded.
"viewid"
The selected report is loaded.To obtain the "viewid", open the required report
(see ""Site" area at customer level" on page 59) and take the ID from the
address line of the browser (e.g.....&viewid=A1A5AD6CD299EF96&....).
test_alarm
A test message is sent to all recipients ("parallel" alarm call plan type) and/or the first recipient
("serial" alarm call plan type) as soon as this page is saved. The check box is subsequently
reset automatically.
scale_units1 - scale_units4
String that the WebApp displays as the measuring unit when specifying the pulse value (see
"Configuring the measurement channels" on page 72) [0-16 characters]
scale_factor1 - scale_factor4
Factor with which the metered measurand of a pulse is multiplied to convert the "Imp. unit" to
the "Unit" that is used by all of the display elements of the server (see "Additional information
on configuring a meter input:" on page 48)
Value
6
Explanation
1000000
5
100000
4
10000
3
1000
2
100
1
10
0
1
-1
0.1
-2
0.01
-3
0.001
-4
0.0001
-5
0.00001
-6
0.000001
Rev. 01
79
wire_color1 - wire_color4
Specifies the colours of the pair of wires for the meter input(read only)
80
Rev. 01
Chapter 12 XML interface
reader_type1 - reader_type4
Selection of the reader type
Important note: This parameter only specifies the selection for the display on the
myDataweb server. To function correctly, the minimum signal length for the signal
detection (time specification provided in brackets in the following table) in the
"mydatalognanoamr_channel" table and the sample time in the "mydatalognanoamr_
user1" table must also be set. Both of these operations are completed automatically
when configuring the reader type (see "Config" on page 49) via the web interface of
the myDataweb server.
The sample time that must be used for the relevant reader type is specified in the
chapter "Config" on page 49. As the same sample time is used for all meter inputs, the
longest of the required sample times must be entered in the "mydatalognanoamr_
user1" table.
Value
Explanation
0
slow (200 ms)
1
medium (64 ms)
2
fast (4 ms)
3
fast plus (4 ms)
10
Elster Grey Snapfit (4 ms)
11
Elster Black Snapfit (4 ms)
12
Elster T. PROBE (4 ms)
13
Elster LRP (4 ms)
14
Elster Q4000 (4 ms)
15
Elster HRP (4 ms)
16
Elster ODO7 (4 ms)
17
Elster HELIX 4000 (4 ms)
18
Elster PR6 (4 ms)
19
Elster PR7 (4 ms)
20
Itron CYBLE K1000 (64 ms)
21
Itron EMES UNIT (64 ms)
22
Sensus HRI (15 ms)
23
Sensus HRI-Mei (15 ms)
24
Sensus OD01 (4 ms)
25
Sensus RD01 (4 ms)
26
Arad BASIC (4 ms)
27
Arad 40/50 (4 ms)
28
Aquamaster (8 ms)
Rev. 01
81
ftpexportprofile
Selection of the FTP export profile
Value
Explanation
0
FTP export deactivated
"id"
To obtain the "id", open the configuration of the required FTP export profile (see
myDatanet Server Manual805002) and take the ID from the address line of the
browser (e.g.....&id=A0B66D1CF7ED87DD&....).
ftpexportdir
makes overwriting the standard directory of the selected FTP export profile possible [0-100
characters]
mappincaption
Specifies whether the title of the site should be displayed in the "Map"
mapovpincaption
Specifies whether the title of the site should be displayed in the "Overview map"
The following parameters apply to the "Meter inputs" (see "Measurement channels" on page 48)
title1 - title4
Freely selectable channel title for the meter inputs
units1 - units4
String, which is used as the measurement unit by all of the server display elements
max_max1 - max_max4
Defines the upper scale end of the pointer instruments
decpl1 - decpl4
Number of decimal places that are used by all of the server display elements
Value
Explanation
-1
Standard
0
No decimal places
:
:
6
6 decimal places
The following parameters apply to the "Internal channels" (see "Internal channels" on page 52)
title6
Freely selectable channel title for the GSM level
units6
GSM field strength: String, which is used as the measurement unit by all of the server display
elements
82
Rev. 01
Chapter 12 XML interface
title7
Freely selectable channel title for the battery voltage
units7
Battery voltage: String, which is used as the measurement unit by all of the server display
elements
The following parameters apply to the "Calculated channels" (see "Calculated channels" on page
50)
title60 - title64
Freely selectable channel title for the calculated channels [0-16 characters]
units60 - units64
String, which is used as the measurement unit by all of the server display elements
min60 - min64
Defines the lower scale end of the pointer instruments
max60 - max64
Defines the upper scale end of the pointer instruments
decpl60 - decpl64
Number of decimal places that are used by all of the server display elements
Value
Explanation
-1
Standard
0
No decimal places
:
:
6
6 decimal places
alarm_low60 - alarm_low64
An alarm is initiated if the measurement value drops to or below this value.
alarm_high60 - alarm_high64
An alarm is initiated if the measurement value meets or exceeds this value.
hysterese60 - hysterese64
Hysteresis for all-clear (e.g. hyst = 5%, alarm or warning at 100 -> all-clear at 95)
12.2.1.2 geraetid
This table includes general information and configurations that are the same for all devices of the
myDatanet range.
kunde
Unique data record number of the customer to whom the device is assigned (read only)
devsn
Serial number of the instrument
Rev. 01
83
devclass
Device class The instrument class of the site and instrument must match for an instrument to
be able to be connected to a site.
telno
Telephone number of the SIM card. The control SMS messages (e.g. wakeup) are sent to this
number. Format: +43555837465[0-20 characters]
devflags
Additional information on the instrument class (for internal use) (read only)
swversion
Current software version installed on the measurement controller (read only)
modemversion
Current software version installed on the modem controller(read only)
osversion
OS version of the modem(read only)
lastcon
Time stamp of the last connection (read only)
lastwakeup
Time stamp of the last wakeup (read only)
lastdisc
Time stamp of the last disconnection (read only)
lasterr
Time stamp of the last transmission error (read only)
lastaloha
Time stamp of the last Aloha connection (read only)
fw_update
Settings for the firmware update
Value
0
84
Explanation
Off: Firmware update is deactivated
1
On: As soon as a new version of the selected firmware type is available, this is
installed immediately.
2
Even if tag is missing: Firmware is also transmitted to the device if the device has
not transmitted the current firmware version to the server. (NOT RECOMMENDED!)
3
Allow downgrade: Facilitates the installation of an older firmware version than
the one on the device. (NOT RECOMMENDED!)
4
Once: Performs a single firmware update. If no new firmware is available or the
firmware was installed successfully, the firmware update is automatically
switched to "OFF".
Rev. 01
Chapter 12 XML interface
fw_release_type
Settings for the firmware type
Value
0
Explanation
Released: Only firmware versions that have successfully undergone internal and
field testing are installed (this practically eliminates malfunctions).
1
Release candidate: Only firmware versions that have successfully undergone
internal testing are installed (malfunctions cannot be excluded).
2
Beta release: Even firmware versions that have not successfully undergone all of
the internal tests are installed (malfunctions may occur).
12.2.1.3 bookingline (read only)
This table includes information about the connections between the devices and the myDataweb
server
kunde
Unique data record number of the customer to whom the device is assigned
geraet
Unique data record number of the device to which the connection list is assigned
text
Duration of the connection
context
Title of the site with which the device is linked or error that occurred during the connection
source
Serial number and IP address
cmh_quantity
Amount of received data in bytes (device to the server)
cmh_quantity2
Amount of sent data in bytes (server to the device)
cmh_code
Indicates whether the device has established a connection to the myDataweb server
(41=closed, 942=connected)
Important note: Table entries with different codes to the ones mentioned above
include information that is only intended for internal use and that should be filtered
out by the customer.
12.2.1.4 kundeid
This table includes information and configurations for the customers created on the myDataweb
server.
name
The freely selectable name of customer is a mandatory field [2-50 characters].
Address of the customer:
Rev. 01
85
strasse
Street [0-50 characters]
plzort
Postcode and town [0-50 characters]
comment
Comment on the customer. This is displayed in the customer overview below the name.
erp_code
The ERP code is designed to simplify and speed up the charging process. All costs that are, for
example, incurred through SMS or calls are charged directly to this ERP code.
Value
*
ERP code
Explanation
The ERP code is adopted from the global server settings.
One of the ERP codes that was created via the global server settings (see
myDatanet Server Manual805002)
Important note: If an invalid code is specified, the ERP code is set to the
global server settings the next time you edit the customer via the web
interface of the myDataweb server.
sms_enabled
This includes the option to generally deactivate SMS for the customer.
Value
-1
Explanation
The setting is adopted from the global server settings
0
Off
1
On
call_enabled
This includes the option to generally deactivate calls for the customer.
Value
86
-1
Explanation
The setting is adopted from the global server settings
0
Off
1
On
Rev. 01
Chapter 12 XML interface
acknowledge_mode
Customer's settings to acknowledge the alarms
Important note: This setting can be overwritten for every measurement instrument via
the alarm settings (see "Alarm settings" on page 52).
Value
0
Explanation
The global server setting is used to determine whether to acknowledge alarms
automatically or manually
1
Alarms are acknowledged automatically as soon as all of the messages have
been sent. If SMS that have a tariff with a delivery confirmation function have
also been sent, acknowledgement is provided after delivery confirmation.
2
Alarms must be acknowledged by the user.
alert_schedule_mode
Settings for the procedure to inform about alarms that have to be acknowledged by the user
Value
0
1
Explanation
The setting is adopted from the global server settings
Inform about every alarm per site: In this case, the alarm schedule is activated
every time an alarm is triggered. Even if the alarm schedule has already been
executed and the alarm has not yet been acknowledged, the alarm schedule is
executed again if a new alarm is triggered on the site.
Important note: This can incur high costs.
2
Inform about the first unacknowledged alarm per site: Messages for new alarms
that have been triggered will only be sent once the alarm has been
acknowledged.
12.2.2 Device-specific table identifier
12.2.2.1 mydatalognanoamr_data
This table includes the measurement data of the myDatalogNANOamr (see "Measurement channels"
on page 48, "Internal channels" on page 52 and "Calculated channels" on page 50).
context
Unique data record number of the site (read only)
ch1 - ch4
Meter readings
Rev. 01
87
calc60 - calc64
Measurement values of the calculated channels.
Important note: However, these measurement values are not saved in the database but
are recalculated during each access (display or download) based on the specifications
entered via the "Calculated channels" configuration section (see "Calculated channels"
on page 50).
gsm_level
GSM field strength [dBm]
voltage
Battery voltage [V]
battery
Battery voltage [%] (calculated based on the battery voltage in Volt)
12.2.2.2 mydatalognanoamr_channel
This table includes the configuration of the meter inputs (see "Measurement channels" on page 48)
that is transferred to the myDatalogNANOamr .
context
Unique data record number of the site (read only)
mode1 - mode4
Basic settings for the measurement channel
Value
Explanation
0
Measurement channel deactivated
12
Infinite counter
mode1_raw - mode4_raw
This is a "Ghost" field, the content of which always corresponds to that of the "mode1" "mode1" field.
88
Rev. 01
Chapter 12 XML interface
scale1 - scale4
Metered measurand of a pulse in the "unit" that is used by all of the server display elements
Important note: Please note that this value is divided by the "Impulse scale" parameter
(see "Measurement channels" on page 48) for the display/input ("Impulse" parameter)
on the web interface of the myDataweb server (see "Measurement channels" on page
48) or the WebApp ("Configuring the measurement channels" on page 72).
Note: Assumption: The meter provides one pulse per 5l. The pulse quality should be displayed in [l] , while
the meter reading is displayed in [m ] on the myDataweb server interface.
Required configuration
Parameter (web interface)
Impulse
5
Imp.unit
l
Impulse scale
0.001
Unit
m
Value
Parameter (mydatalognanoamr_channel) Value
scale1
0.005000
filter_time1d - filter_time4d
Minimum signal length for signal detection [ms]
12.2.2.3 mydatalognanoamr_log
This table includes the log entries and error codes (see "Log entries and error codes " on page 114)
of the device.
log
Log entry
par
Parameter for the log entry
12.2.2.4 mydatalognanoamr_user1
This table includes the remaining configuration that is specific to the myDatalogNANOamr device
class and is not included in the "mydatalognanoamr_channel" table (see "mydatalognanoamr_
channel" on page 88). The configurations from the "mydatalognanoamr_user1" table are
transferred to the myDatalogNANOamr .
The device-specific configuration from the "mydatalognanoamr_channel" and
"mydatalognanoamr_user1" tables are supplemented with the configuration from the "deviceid"
(see "geraetid" on page 83) table that is the same for all of the myDatanet devices.
Rev. 01
89
context
Unique data record number of the site (read only)
measure_mode
Operating type
Value
0
HOLD
Explanation
Measurement: OFF, transmission: ON
1
RUN
Measurement: ON, transmission: ON
2
OFF
Measurement: OFF, transmission: OFF
3
OFFLINE
Measurement: ON, transmission: OFF
4
Reserved for internal use
record_interval
Time between measurements (00:00 same as record interval) [1...1090min]
transfer_interval
Time between transmissions [00:10...168:00 hh:mm]
pos_cycle
Position update interval [00:00...168:00 hh:mm]
tx_mode
Connection type (read only)
Value
0
Explanation
The device registers in the transmission cycle.
alive_time
Aloha/Wakeup duration connection[00:60...90:00 mm:ss]
switch_mode
Operation that is triggered when the solenoid switch is activated, (read only)
Value
1
Explanation
Initiation of ALOHA transmission mode
tx_time
Time at which the device establishes a connection to the server regardless of the transmission
cycle. However, this additional transmission is only completed if a transmission has not
already been completed 5 minutes before this time or if a transmission will not be completed
10 minutes after this time.[hh:mm]
sample_time
Sample time for which the output voltage Uout is activated during the sample interval to
determine the levels at the meter inputs (see "Technical details about the meter inputs" on
page 37) [30...1000µs].
90
Rev. 01
Chapter 12 XML interface
12.2.2.5 mydatalognanoamr_state
This table contains the device status at the time of the last transmission.
Note: As, depending on the system, the GSM field strength and battery voltage are measured
more frequently than the recording is completed, the values included in this table do not
always correspond exactly to the last entry in the "mydatalognanoamr_data" table.
gsm_level
GSM field strength [dBm]
voltage
Battery voltage [V]
instrument_state
Error/status code of the device (see "Status LED" on page 46)
sim_id
IMSI of the SIM chip
sim_apn
APN that was used for the last connection
net_mcc
MCC (mobile country code) of the network that was used for the last connection
net_mnc
MNC (mobile network code) of the network that was used for the last connection
imei
IMEI of the modem
sim_icc_id
ICC ID of the SIM chip
12.2.2.6 mydatalognanoamr_aloha
This table includes the ALOHA data that is generated every three seconds independently of the
normal measurement values and is thus not saved with the standard measurement data (see
"ALOHA transmission mode" on page 23).
gsm_level
GSM field strength [dBm]
voltage
Battery voltage [V]
ch1 - ch4
Meter readings
12.2.2.7 mydatalognanoamr_pos
This table includes the position and network information. The interval during which the data is
generated can be set via the "pos_interval" field in the "mydatalognanoamr_user1" table (see
"mydatalognanoamr_user1" on page 89) or via the web interface in the "Basic settings"
configuration section (see "Position cycle" in chapter "Basic setting" on page 53).
Rev. 01
91
gps_lat
Determined geographical latitude where the device is located [°]
gps_long
Determined geographical longitude where the device is located [°]
gps_elev
Determined height above sea level [m]
gps_quality
Specifies the quality of the determined position data. The position for devices without a GPS
receiver is calculated based on the information from the GSM cells in the receiving range.
Value
0, 1
Explanation
Position could not be determined.
10
Only the country in which the device is located could be determined.
20, 30
The position has been limited to a larger area within a country.
>=100
Position could be calculated from the information of the GSM cells in the
receiving range
>31,000
Position determined by the GPS receiver1)
1) The myDatalogNANOamr does not include a GPS receiver.
Information about the five GSM cells in the receiving range that were used to determine the position
gsm_mcc_0 - gsm_mcc_4
MCC (mobile country code) of the GSM cell
gsm_rssi_0 - gsm_rssi_4
Received GSM field strength [dBm] for the GSM cell
gsm_mnc_0 - gsm_mnc_4
MNC (mobile network code) of the GSM cell
gsm_ta_0 - gsm_ta_4
TA (timing advance) of the GSM cell
gsm_lac_0 - gsm_lac_4
LAC (location area code) of the GSM cell
gsm_cellid_0 - gsm_cellid_4
Cell ID of the GSM cell
12.2.2.8 mydatalognanoamr_set
This table is provided to set the meter readings to the required value.
92
Rev. 01
Chapter 12 XML interface
context
Unique data record number of the site (read only)
ch1_set - ch4_set
Provided to set the meter reading of measurement channel x to a certain value. This field is
reset by the myDataweb server once the value has been adopted.
Important note: Please note that this setting affects the meter readings within the
device. This means that the meter reading will only be reset and the content of the field
will only be deleted during the next connection of the myDatalogNANOamr with the
myDataweb server. It is therefore advisable to only reset the counters when the
myDatalogNANOamr is online (is in ALOHA transmission mode).
12.3 XML export
12.3.1 Configuration of a HTTP-GET command
A request is executed by means of a HTTP-GET command that corresponds to simply entering the
command in the address line of a standard internet browser. The command line (URL) is assembled
as follows and provides an XML document as a result:
https://{IP address}:{Port}/{XPath Query}?{login}{settings}{update}
Parameter
{IP-Address}
Explanation
Address of the server on which the xPath module operates (myDataweb server)
{Port}
Port on which the xPath server operates. The standard setting is 8080.
{xPath Query}
xPath of the required XML table (e.g. "Structure of the database" on page 75).
A description of the syntax is provided in "Syntax of the xPath query" on page
94.
{login}
User name and password of a user account created on the myDataweb server
to authenticate the request (e.g. user=u1&password=p1 ).
{settings}
OPTIONAL
Settings relating to the output format of the request. There is only one
possible parameter. It deactivates the display of the field attributes:
attributes=off
Settings relating to the output of the data. There is only one possible
parameter. It specifies the data compression period: period=... (see "Data
record compression" on page 99)
{update}
OPTIONAL
Update of data fields in the query result (e.g. &$field01=33) (see "Updating
data fields" on page 100)
Rev. 01
93
12.3.1.1 Syntax of the xPath query
12.3.1.1.1 List of the fields in a table
A list of the fields within a table is read out via an @ before the table identifier.
https://server-URL:8080/@geraetid?user=u1&password=p1
Example above provides a list of the fields in the "Device" table (geraetid):
<Result>
<Field title="Customer">customer</Field>
<Field title="Serial number">devsn</Field>
<Field title="Device class">devclass</Field>
<Field title="Telephone number">telnr</Field>
<Field title="Device flags">devflags</Field>
<Field title="Firmware version">swversion</Field>
<Field title="Modem version">modemversion</Field>
<Field title="OS version">osversion</Field>
<Field title="Last connection" units="<%data locals.time_code%> 
<%data locals.offset_record.lastcon%>">lastcon</Field>
<Field title="Last wakeup" units="<%data locals.time_code%> 
<%data locals.offset_record.lastwakeup%>">lastwakeup</Field>
<Field title="Last disconnection" units="<%data locals.time_code%> 
<%data locals.offset_record.lastdisc%>">lastdisc</Field>
<Field title="Last transmission error" units="<%data locals.time_code%> 
<%data locals.offset_record.lasterr%>">lasterr</Field>
<Field title="Last Aloha connection" units="<%data locals.time_code%> 
<%data locals.offset_record.lastaloha%>">lastaloha</Field>
<Field title="Firmware update">fw_update</Field>
<Field title="Firmware type">fw_release_type</Field>
</Result>
A list of possible table identifiers is provided in "Structure of the database" on page 75.
12.3.1.1.2 List of site types
You can access a list of all the types of sites that are supported by the myDataweb server by
specifying the xPath query SiteTypes:
https://server-URL:8080/SiteTypes?user=u1&password=p1
Result:
<Result>
:
<SiteType class="6000" title="myDatalogNanoAMR"> FFFF6000 </SiteType>
:
</Result>
12.3.1.1.3 Filter conditions
The filter condition is always within square brackets [] and comprises expressions that can be
linked by keywords such as and and or. The expressions can be prioritised by using round brackets
94
Rev. 01
Chapter 12 XML interface
() . Only and links are permissible at the highest level. A filter expression comprises a field name,
an operator and a constant. All of the fields in the table can be used.
Note: Upper and lower case are taken into consideration for the name of the site. The
condition must not be specified with an inverted comma ’ when a filter is applied to id or
ref.
The following attributes are available in addition to the fields from the table:
Attribute
Explanation
id
Unique data record number
stamp
Time stamp of the data record (only operator >= and <= are permitted)
ref
Unique data record number of the reference data record
The following operators are supported: =, <>, >, <, >=, <=
The following types can be used as constants:
Data type
Integer
Explanation
Whole numbers
Float
Floating point numbers
Strings
Text indicated by single inverted commas '
Date
Time stamp within single inverted commas '
Formats (comma, date format, etc.) are adopted from the user or server settings.
12.3.1.1.3.1 Example:
The configuration of all sites of the type myDatalogNANOamr is displayed if no filter conditions are
provided.
https://server-URL:8080/mydatalognanoamrid?user=u1&password=p1
Rev. 01
95
Result:
<Result>
<mydatalognanoamrid id="A1526911CF9CCAA0" stamp="8.2.2013 11:48:16">
<tag>FFFF6000</tag>
:
<name title="Name"> site1 </name>
:
</mydatalognanoamrid>
<mydatalognanoamrid id="A1617F03900A44F3" stamp="8.2.2013 11:54:52" >
<tag>FFFF6000</tag>
:
<name title="Name"> site2 </name>
:
</mydatalognanoamrid>
</Result >
The filter must be set up as follows if only the configuration for the "Site1" site has to be returned:
https://server-URL:8080/mydatalognanoamrid[name='Site1']?user=u1&password=p1
Result:
<Result>
<mydatalognanoamrid id="A1526911CF9CCAA0" stamp="8.2.2013 11:48:16">
<tag>FFFF6000</tag>
:
<name title="Name"> site1 </name>
:
</mydatalognanoamrid>
</Result >
12.3.1.1.4 Fields
If more than one field is read out, the list of fields must be placed in round brackets () and
separated by a | or blank space. If none of the fields are specified, all of the available fields are
issued if this is permitted by the user's authorisation level.
Note: The special tag field can be requested in every table and it returns the tag from the requested table (e.g.
FFFF0005 for the geraetid table identifier).
12.3.1.1.4.1 Example
The following example provides the names of all sites of the type myDatalogNANOamr
https://server-URL:8080/mydatalognanoamrid/(name)?user=u1&password=p1
96
Rev. 01
Chapter 12 XML interface
Result:
<Result>
<mydatalognanoamrid id="A1526911CF9CCAA0" stamp="8.2.2013 11:48:16">
<name title="Name">Site1</name>
</mydatalognanoamrid>
<mydatalognanoamrid id="A1617F03900A44F3" stamp="8.2.2013 11:54:52">
<name title="Name">Site2</name>
</mydatalognanoamrid>
</Result>
12.3.1.1.5 Data retrieval including index specifications
Only the following index specifications are supported:
Index
[0]
Explanation
First data record (with the oldest time stamp)
[last()-1]
Last data record (with the latest time stamp)
Other index specifications, such as [5] or [last()-2] are invalid.
12.3.1.1.5.1 Example
The following example provides the first data record of a myDatalogNANOamr type site that is called
"Site1".
https://server-URL:8080/mydatalognanoamrid[name='Site1']/mydatalognanoamr_data[0]
?user=u1&password=p1
Result:
<Result>
<measurement_values id="F10001C000000000" stamp="9.4.2013 09:30:00">
<tag>00006000</tag>
<context title="Site">A19D60AC2883F9B3</context>
<flags title="Flags">0000000000000000</flags>
<ch1 title="Meter number 1" units="m³">0.0000</ch1>
<ch2 title="Meter number 2" units="m³"/>
<ch3 title="Meter number 3" units="m³"/>
<ch4 title="Meter number 4" units="m³"/>
<ch5 title="Channel 5" units="m³"/>
<calc60 title="Flow rate 1" units="%" calc="1"/>
<calc61 title="Flow rate 2" units="%" calc="1"/>
<calc62 title="Flow rate 3" units="%" calc="1"/>
<calc63 title="Flow rate 4" units="%" calc="1"/>
<calc64 title="Calculation channel 5" units="%" calc="1"/>
<gsm_level title="GSM level" units="dBm">-57</gsm_level>
<voltage title="Battery" units="V">3.51</voltage>
<battery title="Battery [%]" units="%">31</battery>
</measurement_values>
</Result>
Explanation:
Rev. 01
97
mydatalognanoamrid
Specifies that the data of a myDatalogNANOamr type site should be queried
[name='Site1']
Specifies that the name of the site, that has to be queried, is "Site1".
mydatalognanoamr_data
Specifies that the data from the measurement data table should be queried.
[0]
Specifies that the first data record (with the oldest time stamp) should be queried.
The following example supplies the last data record of a myDatalogNANOamr type site that is
connected to the device with serial number "010146AF251D0BA9".
https://server-URL:8080/geraetid[devsn='010146AF251D0BA9']/
mydatalognanoamrid/mydatalognanoamr_data[last()-1]?user=u1&password=p1
Result:
<Result>
<measurement_values id="F10001C0000009F0" stamp="11.4.2013 09:25:00">
<tag>00006000</tag>
<context title="Site">A19D60AC2883F9B3</context>
<flags title="Flags">0000000000000000</flags>
<ch1 title="Meter number 1" units="m³">0,0050</ch1>
<ch2 title="Meter number 2" units="m³"/>
<ch3 title="Meter number 3" units="m³"/>
<ch4 title="Meter number 4" units="m³"/>
<ch5 title="Channel 5" units="m³"/>
<calc60 title="Flow rate 1" units="%" calc="1"/>
<calc61 title="Flow rate 2" units="%" calc="1"/>
<calc62 title="Flow rate 3" units="%" calc="1"/>
<calc63 title="Flow rate 4" units="%" calc="1"/>
<calc64 title="Calculation channel 5" units="%" calc="1"/>
<gsm_level title="GSM level" units="dBm">-63</gsm_level>
<voltage title="Battery" units="V">3,56</voltage>
<battery title="Battery [%]" units="%">36</battery>
</measurement_values>
</Result>
Explanation:
geraetid
Specifies that the entry point for the request is the device table
[devsn='010146AF251D0BA9']
Specifies that the serial number for the device, for which the date has to be queried, is
"010146AF251D0BA9".
mydatalognanoamrid
Specifies that the data of a myDatalogNANOamr type site should be queried.
mydatalognanoamr_data
Specifies that the data from the "Measurement data" table should be queried.
98
Rev. 01
Chapter 12 XML interface
[last()-1]
Specifies that the last data record (with the latest time stamp) should be queried.
12.3.1.2 Data record compression
Data record compression can be activated via the optional period=... setting. This means that all
of the data records within the specified period are compressed with the per field adjustable
calculation method.
The calculation method must be specified in brackets after each field in the field list (see "Fields"
on page 96) of the xPath query:
https://{IP-Adresse}:{Port}/{xPath Query Table Selection}/
(ch0(method=1)|ch0(method=2)|ch0(method=16;sum_mode=4))?{login}&period=15
The example above provides three different results for the values of channel 0 compressed over
15 min.:
ch0(method=1): Minimum within the compression period
l ch0(method=2): Maximum within the compression period
l ch0(method=16;sum_mode=4): Daily total over the compression period
l
Based on: The value of channel 0 increases by one per minute.
<Result>
<record stamp="2013-01-25 11:30:00">
<ch0_min>0.0</ch0_min>
<ch0_max>14.0</ch0_max>
<ch0_sum>105.0</ch0_sum>
</record>
<record stamp="2013-01-25 11:45:00">
<ch0_min>15.0</ch0_min>
<ch0_max>29.0</ch0_max>
<ch0_sum>330.0</ch0_sum>
</record><record stamp="2013-01-25 12:00:00">
<ch0_min>30.0</ch0_min>
<ch0_max>44.0</ch0_max>
<ch0_sum>555.0</ch0_sum>
</record>
</Result>
period=...
Period in minutes to which it should be compressed:
Example:
60
hourly data
1440
daily data
10080
weekly data
44640
monthly data
133920 quarterly data
Rev. 01
99
method=…
The compression methods can be specified per channel:
1
Minimum within the compression period
2
Maximum within the compression period
4
Average over the compression period
8
Median over the compression period
16
Total over the compression period
Several methods can be used simultaneously. Individual values must be added up for this
purpose. That means that (ch0(method=1) | ch0(method=2)) is equivalent to
(ch0(method=3)).
If the compression method "Total" (16) is activated, the summation method sum_mode=…
must be specified in addition to the method=… compression method.
sum_mode=…
1
1/sec (e.g. One channel is recorded in m3/s; the total period equals m3.)
2
1/min (e.g. One channel is recorded in m3/min; the total period equals m3.)
3
1/h (e.g. One channel is recorded in m3/h; the total period equals m3.)
5
1/day (e.g. One channel is recorded in m3/day; the total period equals m3.)
4
Total of a day counter (counting channel is reset once per day)
6
Total of an interval counter (counting channel is reset after each recording)
12.3.1.3 Updating data fields
A HTTP-GET command can also be used to update the fields of a data record. For this purpose, the
HTTP-GET command must be extended by the relevant field assignment starting with a dollar sign $
. Any number of fields can be overwritten at once.
Note: The user must have the relevant rights to modify the data (see tbd).
12.3.1.3.1 Example
The following example sets the "Firmware update" to "ON" and the "Firmware type" to "Release
candidate" for all of the devices that are compatible with the myDatalogNANOamr type site.
https://server-URL:8080/geraetid[devclass=6000]?user=u1&password=p1
&$fw_update=1&$fw_release_type=1
Result:
<Result>
<updated>2</updated>
</Result>
Explanation:
100
Rev. 01
Chapter 12 XML interface
geraetid
Specifies that the entry point for the request is the device table.
[devclass=6000]
Specifies that the action should apply to all of the devices that are compatible with the
myDatalogNANOamr type site.
$fw_update=1
Specifies that the "Firmware update" should be set to "On".
$fw_release_type=1
Specifies that the "Firmware type" should be set to "Release candidate".
The following example sets the "Firmware Update" to "Off" for the device with serial number
"010146AF251D0BA9".
https://server-URL:8080/geraetid[devsn='010146AF251D0BA9']
?user=u1&password=p1&$fw_update=0
Result:
<Result>
<updated>1</updated>
</Result>
Explanation:
geraetid
Specifies that the entry point for the request is the device table.
[devsn='010146AF251D0BA9']
Specifies that the action should apply to the device with serial number "010146AF251D0BA9".
$fw_update=0
Specifies that the "Firmware update" should be set to "Off".
12.3.2 Format of the XML result
The result is an XML document for which the root element is <Result>. At least one child element is
issued with the title of the table for each data record.
The data records generally have the following attributes:
Attribute
Explanation
id
Unique number of the data record
stamp
Time stamp of the data record
Rev. 01
101
The data fields have the following attributes:
Attribute
title
Explanation
Title of the data field (for measurement data this is dependent on the site settings)
units
Units of the data field for measurement data (dependent on the site settings)
calc
OPTIONAL
Is only displayed if it is a channel that has been calculated by the sever
12.3.2.1 Example:
<?xml version="1.0"?>
<Result>
<deviceid id="A15D6246F7AEBFAA" stamp="13.2.2013 09:10:05">
<tag>FFFF0005</tag>
<customer title="Customer">A1519985809987EC</customer>
<devsn title="Serial number">010146AF251D04C3</devsn>
<devclass title="Device class">6000</devclass>
<telnr title="Telephone number">+436764006643</telnr>
<devflags title="Device flags">0007</devflags>
<swversion title="Firmware version">0300</swversion>
<modemversion title="Modem version">0300</modemversion>
<osversion title="OS version">07.0430</osversion>
:
:
</geraetid>
<geraetid id="A1526911CF1A42CC" stamp="13.2.2013 09:33:54" >
:
:
</geraetid>
</Result>
12.4 XML import
The XML import is designed to import the data generated or changed via the user interface, created
by the customer, back into the myDataweb server.
Only existing measurement data and settings can be changed or new measurement data can
be added. No historical measurement data can be added.
l It must be ensured that the stamp of the data records is always created in ascending order.
Errors can occur if this is not the case.
l If any settings are changed, it must be ensured that the stamp is set to the current date/time.
Otherwise the data are not synchronised with the device.
l When creating measurement data, the id="0" and <tag>00006000</tag> (60 representing the
device class) must always be specified.
l <tag>0</tag> must always be specified during the deleting process. Historical data (e.g.
measurement data) cannot be deleted.
l
12.4.1 Transferring data to the myDataweb server
A HTTP post command can be used to transfer a XML file to be imported by the myDataweb server.
102
Rev. 01
Chapter 12 XML interface
A HTTP POST command can, for example, be executed with the freely available "Wget" command
line tool (http://www.gnu.org/software/wget/).
12.4.2 Configuration of a HTTP-POST command
Important note: The transmission of XML files to the server is completed via the HTTP server
(standard port 80) and not the xPath server (standard port 8080).
The HTTP-POST command is made up of the following:
http://{IP-Adresse}[:{Port}]/send.xml?directlogin={login}
The XML file must be transferred with this POST command. The configuration of these is described
in the chapter "Structure of the XML file" on page 104.
Parameter
{IP-Address}
Explanation
Address of the server to which the data should be transferred (myDataweb
server)
{Port}
Port on which the HTTP server is running. Standard value is 80.
{login}
The direct login parameter clearly identifies the user on the server. Each
relevant user can only request his own parameter. For this purpose, the user
must open the input screen for editing his user data (see "myDatanet Server
Manual" 805002) in the "User" area of the myDataweb server. The "Direct
login character string" (1) is in the lower third of this area.
Rev. 01
103
12.4.3 Structure of the XML file
12.4.3.1 Changing existing data
If an existing data record has to be changed, the unique identification number of the data record
that is going be changed must be specified as the id attribute (e.g. id ="F000002200000282" ). The
XML file must only include those elements that should be changed. All of the elements that are not
included are not changed. The attributes (title , units , calc , etc.) are not relevant for the data
import and can be omitted.
Note: Formats (comma, date format, etc.) are adopted from the user or server settings.
<?xml version="1.0"?>
<Result>
<mydatalognanoamr_data id="F000002200000282" >
<ch1>0.0000</ch1>
</mydatalognanoamr_data>
</Result>
mydatalognanoamr_data
Not relevant for the data import. However, it is recommended to use the relevant table
identifier.
id
Unique identification number of the data record that is going to be modified
ch1
Value to which the meter reading of channel 1 should be changed
12.4.3.2 Importing data
The id="0" attribute must be specified if a new data record is going be created. The time stamp for
the data record can be determined using the stamp attribute. It must be ensured that the time
stamp of the data is always in ascending order. The stamp attribute can also be omitted. In this
case, the current time is used as the time stamp for the data record. The default values of the
myDataweb server are used for all of the elements that are not specified in the XML file when
creating a new data record. The tag element is a mandatory field and specifies the table in which
the data record is saved. The link between the data record and the site (if the data record is saved in
one of the tables assigned to the site) or the device (if the data record is saved in one of the tables
assigned to the device) is specified via the context element. This relates to the unique data record
identification number (id) of the site or device. The attributes (title , units , calc , etc.) are not
relevant for the data import and can be omitted.
Note: Formats (comma, date format, etc.) are adopted from the user or server settings.
104
Rev. 01
Chapter 12 XML interface
Site to which the data record should be linked:
<Result>
<mydatalognanoamrid id="A1526911CF9CCAA0"
<tag> FFFF6000 </tag>
<name title="Name"> Site1 </name>
:
:
</mydatalognanoamrid>
</Result>
stamp="13.2.2013 10:00:54" >
XML file:
<?xml version="1.0"?>
<Result>
<mydatalognanoamr_data id="0" stamp="16.1.2013 09:00">
<ch1>0.0000</ch1>
<tag>00006000</tag>
<context>A1526911CF9CCAA0</context>
</mydatalognanoamr_data>
</Result>
mydatalognanoamr_data
Not relevant for the data import. However, it is recommended to use the relevant table
identifier.
id
must always be specified when importing data. A new data record with an
automatically generated ID is created.
id="0"
stamp
OPTIONAL
Time stamp that should be used for the data record. It must be ensured that the time stamp of
the data is always in ascending order. If the attribute is omitted, the current time is used as the
time stamp for the data record.
ch1
The actual measurement data (in this case only the meter reading of channel 1) that should be
imported.
tag
Specifies the table in which the data record is saved
context
Specifies with which site or with which device the data record is to be linked (see "Site with
which the data record should be linked")
Rev. 01
105
Chapter 13 Maintenance
Chapter 13 Maintenance
Important note: The work described in this section of these instructions may only be performed by qualified personnel to prevent damage to the instrument.
Before maintenance, cleaning and/or repair work, the device must absolutely be deenergised
(zero potential).
13.1 General maintenance
Regularly check the myDatalogNANOamr for mechanical damage.
Check all of the connections for leaks or corrosion on a regular basis.
l Check all of the cables for mechanical damage at regular intervals.
l Clean the myDatalogNANOamr with a soft, moist cloth. Use a mild cleaning agent, if necessary.
l
l
13.2 Replacing the battery pack
Important note: When replacing the battery pack under adverse weather conditions or site
locations where water can enter from above, find a suitable dry location for replacing the battery pack. If this is not possible, protect the opened device against penetrating moisture
using suitable means.
Rev. 01
107
Replacing the battery pack
1 Housing cover
3 Battery pack BP434RLC (206.725)
2 Supply connector
4 Retaining bracket for the battery pack
1. Ensure that all of the relevant data was transferred to the myDataweb server. If necessary initiate the ALOHA transmission mode using the magnetic contact (see "ALOHA transmission
mode" on page 23) and then check again that all of the relevant data has been transferred.
2. Remove the four screws that secure the housing cover and open the myDatalogNANOamr .
3. Disconnect the connector of the battery pack from the device's supply connector.
Important note: Avoid excessive force and pull the connector of the battery pack as
straight as possible from the supply connector.
108
Rev. 01
Chapter 13 Maintenance
4. Rotate the battery pack to the left (see "Removing the battery pack - step 1" on page 109) so
that it slips out of the retaining bracket on the opposite side to the connection cable. You can
then simply remove it in an upwards direction (see "Removing the battery pack - step 2" on
page 109).
Note: Ensure that the battery pack is disposed of in line with environmental requirements. Used battery packs can be returned to the manufacturer or handed in at suitable collection points.
Removing the battery pack - step 1
Rev. 01
Removing the battery pack - step 2
109
5. Complete the steps in reverse order to insert the new battery pack. During this process, ensure
that the connection cable of the negative pin of the battery pack (black cable) is between the
battery pack and retaining bracket.
6. Reconnect the connector of the battery pack to the supply connector of the device. Just like
when the connection was disconnected, avoid applying excessive force and insert the connector of the battery pack as straight as possible into the supply connector.
Important note: Observe the polarity of the battery pack connector.
The following step is not mandatory.
7. Check whether the connection to the myDataweb functions correctly (see "Testing communication with the device" on page 43).
8. Close the housing cover. The best option is to tighten the four screws crosswise (torque
0,5Nm) so that the housing cover is positioned evenly.
Important note: Ensure that the seals are clean and intact before closing the housing
cover. Remove any impurities and/or dirt. The manufacturer shall not be liable for any
damage to the device caused by leaky or faulty seals.
9. Check that the housing cover is positioned correctly on all sides and that no foreign materials
have been trapped between the housing and housing cover.
Important note: The manufacturer is not liable for any damage that is caused by housing covers that are not closed correctly.
110
Rev. 01
Chapter 14 Removal/disposal
Chapter 14 Removal/disposal
Dispose of the device in accordance with the locally valid environmental regulations for electronic
products.
Rechargeable batteries and/or battery packs may not remain in the myDatalogNANOamr after discharging. Ensure that the used rechargeable batteries and/or battery packs are disposed of in an
environmentally proper way.
Rev. 01
111
Chapter 15 Troubleshooting and repair
Chapter 15 Troubleshooting and repair
15.1 General problems
Problem
Device does not
respond (status
LED always off)
Communication
problems
Not all or no data
is available on the
server
Data at the meter
input is not
plausible.
Alarm message
was not sent
although the
alarm was
signalled.
Rev. 01
Cause/solution
The capacity of the battery pack is depleted. Instructions on replacing the
battery pack are provided in the chapter "Replacing the battery pack" on page
107. A list of possible replacement battery packs is included in the chapter
"Battery packs" on page 121.
Evaluate the status LED blink code (see "Status LED" on page 46).
l Load the device log from the myDataweb server and use
myDatanetDeviceConfig for the evaluation (see "Evaluating the device
log" on page 120).
l The capacity of the battery pack is virtually depleted.
l
The connection was interrupted during transmission, which is indicated
by a time-out entry in the connection list (see "myDatanet Server
Manual" 805002). Solution: Initiate a ALOHA transmission or wait for the
next cyclical transfer.
l The assignment of the device and site is not correct (see "Site" on page
47).
l
Check the cable connections (see "Connecting the meters" on page 33)
Check whether the meter input configuration matches the meter output
signal (see "Measurement channels" on page 48).
l Check whether the correct "Reader type" has been selected for the meter
that you are using. (see "Config" on page 49).
l Check whether the output signal from the meter that you are using is
compatible with the electrical characteristics of the meter inputs (see
"Technical details about the meter inputs" on page 37).
l
l
Check the settings of the alarm schedule (see "myDatanet Server
Manual" 805002).
l Check the address data of the alarm schedule (see "myDatanet Server
Manual" 805002).
l
113
15.2 Log entries and error codes
Log entry
Code
Plain text
1020 ERROR SOD
Parameter
Code
Plain text
## ---
Description
Internal system error
There may be a hardware problem if this
error is included in the device log several
times with the same parameter code.
Contact the manufacturer in this case (see
"Contact information" on page 125).
1200 MODEM ERROR
Modem error (see "Modem error" on page
117)
1212 ERROR MODEM
IRREGULAR OFF
##
---
Indicates a faulty connection. The parameter
indicates how many consecutive
connections have not worked.
1252 MODEM TO CON
##
---
Timeout while a connection is being
established. The parameter includes a
counter that indicates how many
consecutive connection attempts have not
worked.
1281 ZLIB
STREAMPROCESS
ERR
##
---
Internal error
Contact the manufacturer if the device log
includes the error several times (see
"Contact information" on page 125).
1282 ZLIB STREAMFINISH ##
ERR
---
1440 DECAY MEM ERR
---
114
---
Internal error
Contact the manufacturer if the device log
includes the error several times (see
"Contact information" on page 125).
Reserved for extensions
Rev. 01
Chapter 15 Troubleshooting and repair
Log entry
Code
Plain text
1600 STATE
Parameter
Code
Plain text
1
OK
Last connection OK
(1/2) (1/2)
2
TRANSMISSION
ERROR
Last transmission faulty
MEASUREMENT
ERROR
Last measurement faulty
3
Description
Try again later
Check the configuration
l Check the connection between the
device and the sensor
l
4
HOLD
Standby (GPRS ON, measurement OFF)
If the ALOHA transmission mode is initiated,
the myDatalogNANOamr switches back into
"RUN" mode (GPRS ON, measurement ON).
5
TRANSPORT
Transport lock (GPRS OFF, measurement
OFF)
see "Standby"
6
OFFLINE
Offline (GPRS OFF, measurement ON)
see "Standby"
7
NO NET (NET LOCK) Netlock/no matching provider
Try to improve the position of the
antenna.
l Check whether the device is in the
coverage area
(www.microtronics.at/footprint).
l
8
NO NET
No GSM network
Improve the position of the antenna
l Try again later
l
10
GPRS ERROR
No GPRS connection
Try to improve the position of the antenna.
Rev. 01
115
Log entry
Code
Plain text
1600 STATE
Parameter
Code
Plain text
11
IP ERROR
(1/2) (1/2)
Description
No myDataweb server available
Check whether port 51241 is enabled
on the myDataweb server.
l Try again later
l
12
SIM CARD ERROR
Faulty SIM chip
Contact support.
2000 MODULE ERR
Reserved for extensions
3000
Reserved for extensions
3099
116
Rev. 01
Chapter 15 Troubleshooting and repair
15.2.1 Modem error
Log entry
Code
Plain text
GPRS error (1/2)
Parameter
Plain text
Code
1200 BEARER LINE BUSY
-993 ---
Description
Line busy
Try again later
BEARER NO
ANSWER
-992 ---
No answer
l
l
BEARER NO
CARRIER
-991 ---
No carrier
l
l
BEARER GPRS
FAILED
-988 ---
Try again later
Check whether the device is in the
coverage area
(www.microtronics.at/footprint).
Try again later
Check whether the device is in the
coverage area
(www.microtronics.at/footprint).
GPRS setup failure
Try to improve the position of the
antenna
l Check whether the device is in the
coverage area
(www.microtronics.at/footprint).
l
BEARER PPP LCP
FAILED
-987 ---
BEARER PPP AUTH
FAILED
-986 ---
BEARER PPP IPCP
FAILED
-985 ---
BEARER PPP LINK
FAILED
-984 ---
BEARER PPP TERM
REQ
-983 ---
Rev. 01
Error when negotiating the LCP
Internal error
Error occurred during PPP authentication
Internal error
Error when negotiating the IPCP
Internal error
PPP receiver does not react to echo request
Internal error
PPP session terminated by the receiver.
Internal error
117
Log entry
Code
Plain text
GPRS error (2/2)
BEARER CALL
REFUSED
Code
Parameter
Plain text
-982 ---
Description
Incoming call refused
Try again later
BEARER UNKNOWN -981 ---
Try again later
Error when establishing the GPRS connection
1200 BEARER BAD HDL
-980 ---
Invalid handling
Internal error
BEARER BAD STATE -979 ---
The carrier was not stopped.
Internal error
BEARER DEV
-978 ---
Error occurred during link layer initialisation
Internal error
BEARER GPRS
START UNKNOWN
-977 ---
Internal error
Error when disconnecting the GPRS connection
1200 BEARER GPRS STOP -976 --BAD HDL
BEARER GPRS STOP -975 --UNKNOWN
1200 NETLOCK FAILURE
-970 ---
Invalid handling
Internal error
Internal error
Error when selecting the network
l
118
Check whether the device is in the
coverage area
(www.microtronics.at/footprint).
Rev. 01
Chapter 15 Troubleshooting and repair
Log entry
Code
Plain text
1200 BAND SEL FAILED
Parameter
Code
Plain text
-969 ---
Description
A network could not be found on the
GSM900/1800 or on the GSM85071900
band.
Try to improve the position of the
antenna.
l Check whether the device is in the
coverage area
(www.microtronics.at/footprint).
l
TCP channel error (1/2)
1200 CHANNEL ABORTED -965 ---
An attempt is being made to write to/read a
TCP client that is no longer available.
Try again later
CHANNEL CSTATE
-964 ---
The channel is not in the "WIP_CSTATE_
READY" state.
Try again later
CHANNEL NOT
SUPPORTED
-963 ---
CHANNEL OUT OF
RANGE
-962 ---
The option is not supported by the channel.
Try again later
The optional value is outside the permissible
range.
Try again later
CHANNEL MEMORY -961 ---
Internal error
CHANNEL INTERNAL -960 ---
Internal error
CHANNEL INVALID
Invalid option or parameter
-959 ---
Internal error
TCP DNS FAILURE
-958 ---
The name could not be resolved in an IP
address.
Internal error
CHANNEL
RESOURCES
-957 ---
CHANNEL PORT IN
USE
-956 ---
Rev. 01
There are no further TCP buffers available.
Try again later
TCP server port is already being used.
Try again later
119
Log entry
Code
Plain text
TCP channel error (2/2)
Code
Parameter
Plain text
1200 CHANNEL REFUSED -955 ---
Description
The TCP connection has been refused by the
server.
Try again later
CHANNEL HOST
UNREACHABLE
-954 ---
No route to the host.
Try again later
CHANNEL NETWORK -953 --UNREACHABLE
No network available
CHANNEL PIPE
BROKEN
TCP connection interrupted
-952 ---
Try again later
Try again later
CHANNEL TIMEOUT -951 ---
Timeout (DNS request, TCP connection, ping
response, etc.)
Try again later
CHANNEL
UNKNOWN
-950 ---
Internal error
15.3 Evaluating the device log
15.3.1 Evaluating the device log on the myDataweb server
The last 300 log entries on the myDataweb server can be called up via the button shown below that
is located in the measurement device list. As the log entries are sent to the server in the
transmission cycle in the same way as the measurement data, only the log entries up to the last
server connection are available.
The manual for the server ("myDatanet Server Manual" 805002) includes a detailed description of
the evaluation of the device log on the myDatawebserver.
15.3.2 Evaluating the device log using myDatanetDeviceConfig
A detailed description regarding the evaluation of the device log using myDatanetDeviceConfig is
included in the myDatanetDeviceConfig user manual ("myDatanetDeviceConfig Manual" 805004).
120
Rev. 01
Chapter 16 Spare parts and accessories
Chapter 16 Spare parts and accessories
16.1 Assembly sets
Description
Universal bracket for housing myDatanet 86x126
Quantity
Order number
1
206.640
DIN rail mounting set for myDatanet housing 86x126
1
206.634
Pipe mounting kit for myDatanet housing 86x126
1
206.660
16.2 Antennas
Description
Antenna 900 FME
Quantity
Order number
1
206.801
Flat antenna Smart Disc FME-F
1
206.814
Extension cable for Antenna 900 FME
1
206.805
Flat Antenna Smart Disc US FME-F
1
206.817
Antenna 1800 FME
1
206.809
antenna adapter FME-F to SMA-F
1
206.822
flat antenna Smart Disc Plus FME-F
1
206.824
antenna extension SMA-F to FME-F
1
206.825
Flat whip antenna with adapter SMA-FME
1
206.830
Portable Antenne Multi Band
1
206.826
16.3 Battery packs
Description
BP434RLC (Li-SOCl2; 29Ah; -55...+85°C operating temperature)
Quantity
Order number
1
206.725
16.4 Other accessories
Description
myDatanet Tool Pen
Quantity
Order number
1
206.646
MDN Magnet
1
Rev. 01
206.803
121
Chapter 17 Document history
Chapter 17 Document history
Rev.
Date
01 26.04.2013 First version
Rev. 01
Changes
123
Chapter 18 Contact information
Chapter 18 Contact information
Support & Service:
Microtronics Engineering GmbH
Hauptstrasse 7
3244 Ruprechtshofen
Austria, Europe
Tel. +43 (0)2756 7718023
[email protected]
www.microtronics.at
Microtronics Engineering GmbH
(Headquarter)
Hauptstrasse 7
3244 Ruprechtshofen
Austria, Europe
Tel. +43 (0)2756 77180
Fax. +43 (0)2756 7718033
[email protected]
www.microtronics.at
Rev. 01
Microtronics Engineering GmbH
Windthorststrasse 5
63179 Obertshausen
Germany, Europe
[email protected]
www.microtronics.de
125