5,838
edits
Cumulus MX FAQ: Difference between revisions
m
→Troubleshooting - messages in MXdiags or in console/terminal output
(Starting new structure - written introduction) |
|||
| Line 12: | Line 12: | ||
= Troubleshooting - messages in MXdiags or in console/terminal output = | = Troubleshooting - messages in MXdiags or in console/terminal output = | ||
== Request for assistance == | |||
If you see any messages that are not explained below, please update this article (you may need to ask for a login) or else post on the support forum in [https://cumulus.hosiene.co.uk/viewforum.php?f=38 Cumulus Wiki Suggestions for updates and additions] sub-forum. Thank you. | If you see any messages that are not explained below, please update this article (you may need to ask for a login) or else post on the support forum in [https://cumulus.hosiene.co.uk/viewforum.php?f=38 Cumulus Wiki Suggestions for updates and additions] sub-forum. Thank you. | ||
== Questions == | |||
=== I have a message about web tags === | |||
There is an article about [[Webtags|Web tags]], I have tried to keep that up to date. That may help, the most common errors seem to be: | |||
# Using a web tag not available at the version you are using (the message in the mXDaiags should indicate which one). | |||
# Using the wrong output formatters, as the article referenced above explains, the codes to use for MX are far more complicated. | |||
# Using an input modifier that MX cannot match to data available (the message will talk about arrays). | |||
=== I have a message about pressing '''Enter''' because a problem has occurred === | |||
This could cover a lot of problems. Make sure you don't have 2 copies of MX running and are not running anything else that accesses the same weather station or the same files as MX, because this message may relate to such a conflict. | |||
Other problems that crash MX when you have just updated either MX or Mono, may relate to code added in update. For example 3.6.2 crashed in some contexts because of a new "FluentFTP.dll file", 3.6.3 reverted to the one used for 3.6.0. Other people have seen problems because of changes in how MONO worked on an update, although that was more of a problem with MX beta than later MX. | |||
= Problems with MX not accepting data when move from C1 = | |||
== Format of data files == | |||
Please see [[Category:Log Files|Log Files index page]] for more information. In general, you should have all the files (except [[log.xml]] from your C1 installation in your MX installation, and MX will be able to read them, although it may update content and thus stop C1 from recognising them. Ensure you have same culture as before (so don't change how dates/times and decimals are stored). | |||
== Ignoring earlier data == | |||
Two issues here. | |||
# MX needs to read from [[Cumulus.ini]] the earliest date to process as it ignores any content for earlier dates. (Cumulus 1 just read all the files it could find in the data folder. | |||
# When you first start running MX, it does not seem to be able to populate charts and recent history web tags for earlier times. | |||
= Unsorted stuff = | = Unsorted stuff = | ||