Chapter 11. Ammonit Data Logger Meteo-32
Table of Contents
11.1. Preparing Meteo-32 for AmmonitOR
If a Meteo-32 data logger should be part of an AmmonitOR project, the Meteo-32 data
logger must have installed firmware version
1.9 or higher. Additionally the data logger has to be configured to send
emails to
<aor@ammonit.com>. To do so, start the
CALLaLOG software and connect the data logger to your computer.
![[Note]](admon/note.png) | Note |
|---|---|
CALLaLOG can be downloaded from the Ammonit website in the support section: www.ammonit.com. |
If you wish to configurate your Meteo-32 device with AmmonitOR please contact us
per email using the address <info@ammonit.com>. We will provide the needed
accounts and credentails for your CALLaLOG configuration.
11.2. ROW and ROWINFO files
ROW and ROWINFO files are sent by the Meteo-32 data logger as email attachments. ROW files include measurement data; ROWINFO files contain channel names, as well as slope and offset values.
Both files have the same base name. Date and time formats are similar to ISO-8601
YYYY_MM_DD_hhmm. ROW files have the extension
.row; ROWINFO files have the extension
.rowinfo.
11.3. Email Subject
The email subject consists of the data logger serial number and its id, e.g.,
Ammonit Data Logger C080765 (#21).
11.4. ROWINFO file format
The rowinfo file consists of two lines:
- The first line is a space separated list of active channels (
three letter codes). The order is relevant and has to be the order
of the activated channels from the
.rowfile. - The second line indicates slope and offset values for active channels as space
separated list of statements. Every statement consists of
two letter code of the channel and the postfix
_slopeor_offset, an equal sign, and the four digit value. The order is not relevant.
11.4.1. Example
2010_01_21_0000.rowinfo
1st line:
s1a s1x s1s s2a s2x s2s s3a s3x s3s d1a d1s d2a d2s h1a t1a b1a r1a s4a
s4x s4s vxa vxi2nd line:
s1_slope=0477 s1_offset=0025 s2_slope=0480 s2_offset=0024 s3_slope=0483
s3_offset=0024 d1_offset=0178 d2_offset=0176 h1_slope=0100 t1_slope=0100 t1_offset=0030
b1_slope=0060 b1_offset=0800 r1_slope=0000 s4_slope=0483 s4_offset=0025(line breaks here for readability only)
11.5. Explanations
- If more than one field in the first line refer to the same physical channel,
such as
s1aands1x, the slope and offsets are still transmitted only once in the second line. - If a channel does not have slope or offset, the respective values are not transmitted.
- The order in the first line is important, in the second line it is not.
11.6. Row file format
The first line is the header. The other lines are the data, e.g. for 10 minutes values of one day, 144 lines.
The header structure is:
- starts always with a
T - date and time in the format
MM/DD/YY hh:mm:ss - measurement and aggregation frequencies
- version string
- serial number of the data logger, e.g.,
C010203
11.6.1. Example
2010_01_21_0000.row
T 01/21/10 00:00:00 1*600 V5.0 C08076543 78 84 2 77 84 2 67 73 3 283 1
272 2 65 2898 1015 28 47 51 2 119 119 82 84 2 77 80 2 66 75 3 286 1 283 2 62 2860 983 28
43 57 3 130 129 74 83 3 77 79 3 65 70 1 273 3 285 1 64 2830 1001 26 45 48 2 123 119 68 79
2 71 82 2 60 74 3 289 2 275 2 68 2909 982 27 43 48 2 126 126 ...Here the measurement frequency is 1 second, the store frequency is 600 times the measurement frequency, i.e. 10 minutes. For one complete day, there should be one data line per 10 minutes, i.e. 144 data lines.