...
Station configuration is different from implementation in the versions D2000 v3.XX. The station time parameters (polling parameters) and polling priority are are used, ; one datalogger must be divided into logical stations as follows:
- Current values - the delay at is at least 1 second, station priority 0. Current measurements of channels and digital inputs are configured at this station. This is a logical station with the lowest priority, ; the delay parameter may not be less than 1 second.
- 1m averages - the period 1 minute, the offset 5..10 seconds, station priority 1. One-minute averages of channel measurements are configured at this station. This is a logical station with a higher priority, ; the parameter offset shouldn't be less than 5 seconds - this is the time provided for the datalogger for processing values.
- 30m averages - the period 30 minute 30 minutes, the offset 5..10 seconds, station priority 2 2. Thirty-minute averages of channel measurements are configured on this station. This is a logical station with even higher priority, ; the parameter offset shouldn't be less than 5 seconds - this is the time provided for the datalogger for processing values.
- Calibrations – station with a required period for reading calibration results.
- For other than 1m and 30m averages (15m, 60m, or custom period averages), it is necessary to configure the polling parameters according to the custom average.
Note: Time The time of values acquired from communication is the time of the beginning of a given period. The division into individual stations is necessary to ensure data reading reliability in the required time and not to overload the communication, e.g., by a frequent acquisition of current values blocking the acquisition of interval averages.
...
The following station protocol parameters can be defined:
Table 3
| Keyword | Full name | Meaning | Unit | Default value |
|---|
| Retry Count | The number of repeats of a request |
repeats | in case of a communication error. | - | 2 |
| Retry Timeout | The delay between individual request repeats in case of a communication error. | ms | 1000 ms. |
| Wait First Timeout | The delay after transmitting the request before reading the response. | ms | 500 ms. |
| Wait Timeout | The delay between response readings until |
its | finalization of the response. | ms | 400 ms. |
| Max Wait Retry | The number of repeats of response readings until its finalization. | - | 8 |
| Get Stored Interval | The size of the period |
, for which the archive data from the datalogger |
are is read without interruption. The period is specified in minutes. If the value of the period is, e.g., 60 minutes, |
so all archive data from, e.g., 05:00 to 06:00 are read, then data from 06:00 to 07:00, etc. The reading of archive data from this period shouldn't take more than one minute, because otherwise some of the current data, acquired among archive readings, could be lost. | min | 10 |
|
admadmADMArchive Depth Minute | Depth of 1-minute | Get Stored Interval Di | The size of the period from which digital archive data is read from the datalogger without interruption. This interval is specified in minutes. If the value of the period is, e.g., 5 minutes, all archive data from, e.g., 03:00 to 03:05, then from 03:05 to 03:10, etc., are read. The time of reading archive data from this interval should not last longer than 1 minute, because there is a risk of losing current data, which is always obtained between archive readings.
Note: The parameter is only relevant for Protocol Variant = EDL. | min | 5 |
| Archive Depth Minute | Depth of 1-minute archives. The ESC dataloggers had a depth of 60 minutes, the new EDLs by ECM Monitory have a configurable depth (even 2 weeks). If the read data is older than the configured depth, the reading is in 30-minute intervals. If they are newer, the Get Stored Interval parameter applies. A value of 0 means unlimited depth (reading is always performed with Get Stored Interval). | min | 90 |
| Max Hist Read 1min | Limit for the depth of reading the history of 1-minute data. The original ESC 8816 dataloggers had an internal memory for one hour of data. Newer devices supporting the ESC 8816 protocol (e.g., EDL15) can store data significantly longer, and thus it is possible to read data after a communication failure in up to 14-31 days. | hour | 1 |
| Max Hist Read Others | Limit for the depth of reading the history of other data (with a period greater than 1 minute). The original ESC 8816 dataloggers had an internal memory for 30 days of data. Newer devices supporting the ESC 8816 protocol (e.g., EDL15) can store data significantly longer, so it is possible to read data after a communication failure in up to 60 days. | hour | 31*24 |
| Protocol Variant | A variant of the protocol. Existing variants are:- 0 - ESC8816 - standard protocol for datalogger ESC8816
- 1 - DLX1 - support of datalogger DLX1 (implemented in august 2015 in D2000 version 10.0.37)
- 2 - EDL - support for EDL15 datalogger (implementation in 2025 in version 25)
This variant implements message 59 (reading historical average values with Unix timestamp) and allows reading binaries (Di) with message 24 (also with Unix timestamp).
| - | 0 - ESC8816 |
A string containing the protocol parameters is defined as follows:
...
- reading of current values with flags,
- reading of 1m, 15m, 30m, and 60m averages with flags,
- reading of custom period value averages with flags,
- reading of the current states of digital inputs,
- reading of calibration results,
- reading the real-time,
- setting the real-time,
- setting mathematic mathematical constants,
- setting relay outputs.
...
For each station (physically one ESC8816 datalogger), one I/O tag containing the real-time of the corresponding station can be configured. The I/O tag is necessary for real-time synchronization computer -> of the computer time to the datalogger.
Mathematic constant I/O tag configuration
Mathematic Mathematical constants are values of the AO type (Analog Output). The measurement type is MATH. A constant number is a decimal number within the range of 0...99.
Warning: Mathematic constants can't be read, so their current value is the value last written or unknown (after D2000 system restart).
Note: D2000 D2000 supports extended mathematic constants addressing mathematical constants addressing syntax, which allows addressing mathematic constants 0mathematical constants 0-359, with mathematic constants 0mathematical constants 0-99 backward compatible with standard addressing.
...
- November 1998 - Datalogger software version 5.16
Modification – for 30m averages, both the flag "F" (layoff) and ">" (validity of average with missing measurements) can occur, ; this half-hour is always considered as invalid.
Modification - new "p" flag - layoff. The "F" flag is set in cases of occurrence of the "p" flag for backward compatibility.
- August 2000 - implementation of relay outputs writing
- February 2003 - implementation of 15m/60m/Custom period averages
...
- Ver. 1.2 – February 8th, 2000 – Update of the versions 4.07 and 4.10.
- Ver. 1.3 – August 22nd, 2000 – controlling relay outputs added.
- Ver. 1.4 - February 7th, 2003 - custom-period averages added.
- Ver. 1.5 - March 13th, 2008 - Update of protocol parameters.
- Ver. 1.6 - August 26th, 2015 - Update of protocol parameters (protocol variant for DLX1 implemented).
- Ver. 1.7 - April 30th, 2018 - Enhancement of channel addressing and mathematic constants from mathematical constants from 0-99 to 0-359.
- Ver. 1.8 - May 23, 2024 2024 - processing of flags H, J, K, L, M, N, O, P
- Ver. 1.9 - Jan 6, 2026 - Update of protocol parameters (addition of protocol variant for EDL).