5,838
edits
Category:Cumulus MX: Difference between revisions
m
→Almost "Ready to run": swapping between flavours not added
m (→Comparing Cumulus 1 and MX: "localhost" update) |
m (→Almost "Ready to run": swapping between flavours not added) |
||
|
netsh http add urlacl url=http://*:8998/ user=\users
to allow all users to bind to port 8998 (i.e. that used for the Cumulus interface).
# I viewed my hub (router) to see the
When I am happy to stop using MX, I type '''Control + C''' into that MX command window on my PC and MX closes.▼
One more lesson, you cannot have Cumulus 1 and Cumulus MX running at same time, accessing same weather station. If you sometimes run one flavour (say MX) and sometimes the other (Cumulus 1), you must copy all the updated log files from the just used data folder to the data folder you are about to use when you close one favour before you start the other flavour, or you must have both executables in same top level folder to force then to share the data folder. If you don't do this various derivatives (e.g. Chill Hours) will become wrong and you may have conflicting rows in dayfile.txt (because the content is generated from what that flavour saw when it was running the previous day) and generally this will be particularly evident in any weather parameter that varies a lot like wind vector.
▲When I am happy to stop using MX, I type '''Control + C''' into that MX command window and MX closes.
=== Success ===
My installation of Cumulus MX has succeeded, and as the experiment did help me find a mistake in one of my Cumulus templates where I had not defined input parameters for "Recent History", it has been useful. I am continuing to use Cumulus 1 for the moment, until I am absolutely sure MX can do everything I want. I believe it will do some tasks better, but there is a lot more to learn about how to use it.
| |||