Carel plug-in User Manual Page 29

  • Download
  • Add to my manuals
  • Print
  • Page
    / 80
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 28
pCOWeb +030220471 – rel. 1.0 – 02.05.2007 29
5 LOGGER AND GRAPHS
pCOWeb can save the values of max 10 variables sampled at regular time intervals to non-volatile memory (“Logger” function).
For one of these variables, pCOWeb can also create a file in .bmp format containing a simple graph of the trend in the values; the graph can then be displayed on a web
page.
IMPORTANT: the logging function will not start if the date of the pCOWeb is earlier than 01-01-2006
. For the date / time settings see 8.6 on page 40.
START OR DISPLAY THE RECORDS
1. Open the Clock and Logger page (
Figure 5.a).
2. Click the “Logger” tab.
The settings are located in the bottom section of the page (
Figure 5.b below); they
becomes active just after the “Submit” confirmation.
SETTINGS AVAILABLE:
¾ Check logger status and free space available
: a window is opened that
shows the status of the logger (“Running” / “Not Running” / “Waiting
for a valid clock configuration”) and the space occupied and free in the
non-volatile memory.
¾ Time sample
: sample time, common to all
the variables.
¾ Compression (.gz)
: the data files created
are .cvs; if Compression is enabled,
compressed files in .gz format are created,
and can be opened using various
decompression tools, for example the
“Filzip” freeware,
http://www.filzip.com
(but not with the decompression tool
included by default in the Windows
operating system); this is used to save
space in the memory, as the data files are
made up of highly repetitive data, a
situation that allows significant
compression.
¾ Variable 1-10
: enable the logging of the
variables; the Short Description is included
in the file saved.
¾ Enable Variable Graph
: select the variable
used to generate the graph (Disabled: the
graph is not created - save memory
space).
¾ Low Limit / High Limit
: limits for the value
of the variable when drawing the graph.
HOW THE RECORDS ARE SAVED
Whenever the specified time interval expires, the sampled values are added to a temporary file resident in VOLATILE memory; at 00 minutes each hour, the data is
downloaded to a file (history_diskbuffer) in proprietary format in NON-VOLATILE memory (/usr/local/root/lash/http/cache).
At midnight each day this file is recopied in .cvs text format (compressed when enabled) in NON-VOLATILE memory accessible to the user, in the
“/usr/local/root/lash/http/log” directory, organised into monthly subdirectories (2007-02, 2007-03, etc...); the graph file is created (if enabled) in .bmp format in the
same memory space.
The logging mode is optimised for a minimum number of writes to non-volatile memory, so as to reduce the degradation of the memory (minimum guaranteed write
cycles: 100,000).
NOTE: in the event of power failures, this logging mode limits the maximum duration of data loss to one hour.
Nonetheless, the .cvs / .bmp files for the current day can be created manually, so as to obtain all the data saved until that moment.
In the “/usr/local/root/flash/http/log” directory, pCOWeb automatically saves the powerup-log.cvs file containing the records, with the date / time of the events: “Start
firmware” and “Stop firmware”, respectively “Power-up” and “Power-down” (the latter is only written when the Stop follows a reboot while pressing the physical button
or selecting the button on the configuration page; in this way, two consecutive “Power-up” events indicate that there was a power failure between the two events.
The .cvs files and the graphs appear as shown in
Figure 5.c on page 30.
The first line of the .cvs files lists the types of variables enabled for logging, the second line the indices and the third the descriptions attributed; these are followed by the
lines with the records.
Figure 5.a - Opening the Logger and Graph settings
Figure 5.b – Logger and graphs: configuration
Page view 28
1 2 ... 24 25 26 27 28 29 30 31 32 33 34 ... 79 80

Comments to this Manuals

No comments