5,838
edits
MX Administrative Interface: Difference between revisions
m
→Optional Sections
(new page; old content) |
|||
| Line 178: | Line 178: | ||
<pre>2020-04-09 10:00:01.047 MySQL: 2 rows were affected.</pre> | <pre>2020-04-09 10:00:01.047 MySQL: 2 rows were affected.</pre> | ||
===== Standard Daily Summary Table ===== | |||
* 1.''Dayfile.txt upload'' | * 1.''Dayfile.txt upload'' | ||
** This section is about uploading to a database table that contains one row for each day. | ** This section is about uploading to a database table that contains one row for each day. | ||
| Line 198: | Line 198: | ||
#At the end of the meteorological day, MX will now automatically run the SQL to add a new row with the daily summary values as mentioned at the start of this section. | #At the end of the meteorological day, MX will now automatically run the SQL to add a new row with the daily summary values as mentioned at the start of this section. | ||
===== Another daily summary table ===== | |||
*2. ''Custom upload - at rollover'' | *2. ''Custom upload - at rollover'' | ||
** In the previous option, you have no ability to vary the schema, it will update a column for Total Evaporation even if your weather station cannot calculate that. It will update columns for total hours of sunshine, highest solar radiation level, and the maximum UV in the day even if you cannot measure these. It will not record whether snow was falling or lying, or the depth of snow if you wanted to be recording those. | ** In the previous option, you have no ability to vary the schema, it will update a column for Total Evaporation even if your weather station cannot calculate that. It will update columns for total hours of sunshine, highest solar radiation level, and the maximum UV in the day even if you cannot measure these. It will not record whether snow was falling or lying, or the depth of snow if you wanted to be recording those. | ||
| Line 211: | Line 211: | ||
*3.'' | ===== Standard Monthly table ===== | ||
*3.''Standard log file upload'' | |||
**Cumulus starts a new log file for each new month, that is why this is called the monthly log. | **Cumulus starts a new log file for each new month, that is why this is called the monthly log. | ||
**This database table has one row for each line in any monthly log and therefore the same table contains all months. | **This database table has one row for each line in any monthly log and therefore the same table contains all months. | ||
| Line 237: | Line 238: | ||
==== Table created from Standard and/or Extra Sensor Log files ===== | |||
*4. ''Custom upload - minutes interval'' | *4. ''Custom upload - minutes interval'' | ||
** One way you could use this option, is to replace the monthly log file upload if you wanted to change the schema, by leaving out some columns if your weather station is not able to measure all the derivatives included in the standard schema. | ** One way you could use this option, is to replace the monthly log file upload if you wanted to change the schema, by leaving out some columns if your weather station is not able to measure all the derivatives included in the standard schema. | ||
| Line 245: | Line 247: | ||
**# A drop down for the number of minutes between runs, the default is 10, but if your weather station updates less frequently, maybe you will choose 15, 20, 30, or 60 as the interval out of the 11 available in drop down. | **# A drop down for the number of minutes between runs, the default is 10, but if your weather station updates less frequently, maybe you will choose 15, 20, 30, or 60 as the interval out of the 11 available in drop down. | ||
===== Table updated at real time interval ===== | |||
*5. ''Realtime.txt upload'' | *5. ''Realtime.txt upload'' | ||
** Cumulus MX can be set to recreate a file called [[Realtime.txt]] on a very frequent basis. The real time interval defines the time from the end of doing one real time update until the start of the next real time update. The file is recreated, in that unlike other log files, MX does not add new rows in each update, the file only ever contains a single line of values. | ** Cumulus MX can be set to recreate a file called [[Realtime.txt]] on a very frequent basis. The real time interval defines the time from the end of doing one real time update until the start of the next real time update. The file is recreated, in that unlike other log files, MX does not add new rows in each update, the file only ever contains a single line of values. | ||
| Line 265: | Line 267: | ||
# Now move down the screen and click the '''Save''' button, and wait for MX to pop up '''Settings Saved''' message. | # Now move down the screen and click the '''Save''' button, and wait for MX to pop up '''Settings Saved''' message. | ||
===== Another table unpdated at an interval measured in seconds ===== | |||
*6. ''Custom upload - seconds interval'' | *6. ''Custom upload - seconds interval'' | ||
** This feature allows you to specify your own SQL for an upload to be repeated every NN seconds. This caters for when you want something like the values in "realtime.txt" but want to specify your own schema (set of column names) or your own interval between updates (independent of what has been selected for real-time interval). Like the other custom options, this might be because you have extra sensors or do not have sensors for all items in standard log file. | ** This feature allows you to specify your own SQL for an upload to be repeated every NN seconds. This caters for when you want something like the values in "realtime.txt" but want to specify your own schema (set of column names) or your own interval between updates (independent of what has been selected for real-time interval). Like the other custom options, this might be because you have extra sensors or do not have sensors for all items in standard log file. | ||