5,838
edits
MX on Windows OS: Difference between revisions
m
→Report and data files to copy across from any previous Cumulus location
m (→How to run MX) |
|||
| (4 intermediate revisions by the same user not shown) | |||
|
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>
All the files in the [[data folder]] can also be copied across, but 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. Microsoft Windows uses different line terminators to other operating systems, although MX should cope, any third party routines reading your data files will probably not accept a line terminator change.▼
Whilst you should copy ALL the files in the [[data folder]], from any old installation into the new installation, there are several extra considerations:
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:▼
* '''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]]:
* [[Amending dayfile]] tells you about how MX is far more fussy about the content in [[dayfile.txt]]▼
** See [[Cumulus.ini#Data_Logging|'''StartDate=xxxxx''']] parameter, edit using ''Station Settings → Common Options → Advanced Options → Records Began date''
* [[:Category:Ini Files|.ini files]] explains how time-stamps are formatted differently in the extreme tracking files▼
* 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.
* [[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▼
▲
▲* 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==
#*# Select '''Modify'''
#*# You should see '''"C:\CumulusMX\CumulusMX.exe"'''
#*#* This assumes that you have installed your MX in that system partition path, adjust the '''C:''' if you have installed your MX in another partition, in above and in examples below
#*# Now you can add parameters as per [[#Optional_parameters_to_add_to_the_instruction_to_run_the_MX_engine]]
#*#* For example modify to ''' "C:\CumulusMX\CumulusMX.exe" -port 9000''' to add port
# In your MX release distribution, navigate to '''CumulusMX\MXutils\windows'''.
# Find file '''CreateCmxResumeFromStandbyTask.ps1''' for resuming MX after Microsoft Windows has gone into standby.
# The script MUST be run with Administrator
# Type <code>CreateCmxResumeFromStandbyTask</code>, and press '''Enter''', this will create a Scheduled Task.
#* The scheduled task will exist from now on, and will automatically restart the service (on resume from standby/hibernate).
* Or, use the service command line tool:- <code>sc start CumulusMX</code> 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.
Note that you may sometimes want to use one or more of the optional parameters when starting MX, as per previous row.
|-
! scope="row"| Checking MX is still running
! scope="row"| Deleting shortcut/service
| If you have set up your short-cut in the '''Startup''' folder, you need to delete that short-cut (or move it to a sub-folder), to stop MX automatically starting when you restart your computer
| To remove the Cumulus system service:
* 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;"
! scope="row"| Stopping MX
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==▼
== Beta builds of MX ==▼
Use '''CumulusMX -install''' to install MX as a Windows service.▼
The following two parameters are not available since MX came out of 3.0.0 beta.▼
By default, MX's Microsoft Windows service is installed to run under the System account.
=== -wsport parameter for web sockets ===▼
System does not have permissions for network access, that it turn means that any batch file that MX initiates as an external program will be restricted to actions that a System account can do, that excludes actions that a network access account can do.
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'''. ▼
That parameter [https://cumulus.hosiene.co.uk/viewtopic.php?f=40&t=17887&p=138815&hilit=sockets#p138815 is now deprecated as 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], see '''-port''' parameter below.▼
=== -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.▼
▲== -install parameter for installing as Windows Service==
▲Use '''CumulusMX -install''' to install MX as a service.
== -uninstall parameter for uninstalling the Windows Service==
== -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:
MX has a default level of logging that stores in the [[MXdiags_folder]] folder a log file that shows minimal details of the interaction with the weather station and of the output actions done as MX runs. A new log is started each time MX is restarted, and when a log reaches a particular size, so the log cannot keep growing.▼
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 [[MXdiags_folder]] page for details) or by adding a parameter as you start running MX:▼
:<code>CumulusMX -debug</code>
▲MX has a default level of logging that stores in
▲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 [[
▲== 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'''.
▲
▲=== -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=
| |||