5,838
edits
MX on Windows OS: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
→Report and data files to copy across from any previous Cumulus location
m (→How to run MX) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 21: | Line 21: | ||
All the (optional) files in the [[Reports folder]] can be copied across from a previous installation. It should not matter which release created past files, although ideally you need to ensure that the report naming and encoding described on that linked page remain the same. | All the (optional) files in the [[Reports folder]] can be copied across from a previous installation. It should not matter which release created past files, although ideally you need to ensure that the report naming and encoding described on that linked page remain the same. | ||
<br> | |||
If your previous Cumulus installation was of the legacy software, version 1.9.4, or earlier, then you need to do a lot of reading: | Whilst you should copy ALL the files in the [[data folder]], from any old installation into the new installation, there are several extra considerations: | ||
* [[Amending dayfile]] tells you about how MX is far more fussy about the content in [[dayfile.txt]] | * '''Your new MX installation will ignore any entries prior to the MX Start Date''' when it reads from [[Monthly log files]], such as [[Standard log files]], and [[Extra Sensor Files]]: | ||
* [[:Category:Ini Files|.ini files]] explains how time-stamps are formatted differently in the extreme tracking files | ** See [[Cumulus.ini#Data_Logging|'''StartDate=xxxxx''']] parameter, edit using ''Station Settings → Common Options → Advanced Options → Records Began date'' | ||
* [[Migrating from Cumulus 1 to MX]] gives some advice about differences in settings, but be aware that the way MX handles settings varies by release, and information on the linked page may be out of date | * Be aware your new installation has to use the same "locale" as the old installation, or MX will struggle as the locale affects how new lines are stored, and how MX expects old lines to have been stored the same way. | ||
* If your old installation, is on a different operating system to the Microsoft Windows for your new installation, remember that Microsoft Windows uses different line terminators to all other operating systems, although MX should cope with mixed line terminators, any third party routines reading your data files will probably not accept a line terminator change. | |||
* If your previous Cumulus installation was of the legacy software, version 1.9.4, or earlier, then you need to do a lot of reading: | |||
** [[Amending dayfile]] tells you about how MX is far more fussy about the content in [[dayfile.txt]] | |||
** [[:Category:Ini Files|.ini files]] explains how time-stamps are formatted differently in the extreme tracking files | |||
** [[Migrating from Cumulus 1 to MX]] gives some advice about differences in settings, but be aware that the way MX handles settings varies by release, and information on the linked page may be out of date | |||
==Configuration Files to copy across from any previous Cumulus installation== | ==Configuration Files to copy across from any previous Cumulus installation== | ||
| Line 249: | Line 254: | ||
| To remove the Cumulus system service: | | To remove the Cumulus system service: | ||
* Either run <code>CumulusMX.exe - uninstall</code> as an Administrator using Command window or Powershell window or Terminal window (one of these will be offered when you right click the Windows/Start symbol) and type '''exit''' to leave that window. | * Either run <code>CumulusMX.exe - uninstall</code> as an Administrator using Command window or Powershell window or Terminal window (one of these will be offered when you right click the Windows/Start symbol) and type '''exit''' to leave that window. | ||
* Or select '''Services''' from "Start", as an administrator, | * Or select '''Services''' from "Start", as an administrator, in the ''services applet'' that loads navigate to the one labelled Cumulus, and delete that. | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
! scope="row"| Stopping MX | ! scope="row"| Stopping MX | ||
| Line 267: | Line 272: | ||
As seen above, in Microsoft Windows, we leave off the file extension when we want to run one of the Cumulus executables, but we might need to add a parameter (starts with a minus symbol), and that parameter might need to be followed with a value. | As seen above, in Microsoft Windows, we leave off the file extension when we want to run one of the Cumulus executables, but we might need to add a parameter (starts with a minus symbol), and that parameter might need to be followed with a value. | ||
== -install parameter for installing as Windows Service== | == -install parameter for installing as Windows Service== | ||
Use '''CumulusMX -install''' to install MX as a service. | Use '''CumulusMX -install''' to install MX as a Windows service. | ||
By default, MX's Microsoft Windows service is installed to run under the System account. | By default, MX's Microsoft Windows service is installed to run under the System account. | ||
| Line 308: | Line 294: | ||
== -debug parameter for adding debugging == | == -debug parameter for adding debugging == | ||
This is only available for [https://cumulus.hosiene.co.uk/viewtopic.php?p=138839#p138839 release 3.4.4 - Build 3068] onwards. This switches on debug and data logging from the start-up of Cumulus MX by adding a parameter: | |||
:<code>CumulusMX -debug</code> | |||
If there is a problem, then there is a great benefit in actually increasing the level of detail in these logs; and that is done either within the settings (on recent MX releases this is on '''Program Settings''' page of admin interface - please see [[ | MX has a default level of logging that stores in the [[MXdiags_folder]] folder a log file that shows some of the interaction with the weather station and some of the output actions done as MX runs. A new log is started each time MX is restarted. | ||
If there is a problem, then there is a great benefit in actually increasing the level of detail in these logs; and that is done either within the settings (on recent MX releases this is on '''Program Settings''' page of admin interface - please see [[:Category:Diagnostics]] page for details) or the above command. | |||
== Beta builds of MX == | |||
The following two parameters are not available since MX came out of 3.0.0 beta. | |||
=== -wsport parameter for web sockets === | |||
Beta builds in MX version 3.0.0 had an optional parameter <code>CumulusMX -wsport nnnn</code> that determined which port (represented by a 4 digit number ''nnnn'') was used for '''Web Sockets'''. | |||
Note use of this parameter is now deprecated, as it has been incorporated into '''-port''' parameter described earlier. The reason is that [https://cumulus.hosiene.co.uk/viewtopic.php?f=40&t=17887&p=138815&hilit=sockets#p138815 Web Sockets in all builds since 3045] use the same port for web sockets as for the HTTP port of the [[MX_Administrative_Interface#The_API_interface|Admin Interface]]. | |||
=== -Logging parameter for debugging of data flow between station and MX=== | |||
Use '''CumulusMX -Logging=1''' (for the station to MX transfers to have increased debugging logging). | |||
Note use of this parameter is now deprecated, as it has been incorporated into '''-debug''', see above. | |||
=Access to admin interface= | =Access to admin interface= | ||
