Reporting Issues - PLEASE READ
Posted: Wed 07 Jan 2015 8:59 am
A number of posts are reporting issues without giving any supporting material, or without having done any investigation into the problem. If it's a problem with a web site, give a link. If it's a problem with the display of data, is the engine actually getting any data - look in the data logs. Often problems are caused by firewalls or over-zealous anti-virus software - check this.
Re-read the instructions. Look at the list of FAQs and known issues.
If you have an issue with the user interface, use the F12 developer console in your browser. The interface uses http calls and websockets to get its data (websockets are used for 'live' data), so look at both, and look at the javascript console - problems are often obvious. 'Fiddler' is a useful free tool that I use myself as an alternative - http://www.telerik.com/fiddler - it can show you the communication between the browser and the server as an alternative to the browser developer console.
You can also use the developer console and/or Fiddler to find problems with your web site - it will show missing files and javascript errors etc.
If you are reporting an issue with the graphs or gauges, or any other aspect of the display, please make it clear whether you are referring to the user interface or the web pages, or both.
You can turn on extra logging ("debug logging") to the MXdiags files by adding "Logging=1" to the [Station] section of Cumulus.ini. It would be a good idea to turn this on while you are beta testing, so please do so.
You can also turn on data logging, by adding "DataLogging=1" to the [Station] section of Cumulus.ini. This may generate a lot of output, though, so you should probably only turn this on if you are trying to track down a problem with reading data from the station.
You can turn on ftp logging by adding "FTPlogging=1" to the [FTP site] section of Cumulus.ini. Normal and realtime ftp are logged to the same file, ftplog.txt.
You can turn the logging on or off temporarily (i.e. for the current run only, changes do not get affect Cumulus.ini) using the station settings in the user interface.
Any changes to Cumulus.ini should be done with Cumulus stopped.
Thanks.
Re-read the instructions. Look at the list of FAQs and known issues.
If you have an issue with the user interface, use the F12 developer console in your browser. The interface uses http calls and websockets to get its data (websockets are used for 'live' data), so look at both, and look at the javascript console - problems are often obvious. 'Fiddler' is a useful free tool that I use myself as an alternative - http://www.telerik.com/fiddler - it can show you the communication between the browser and the server as an alternative to the browser developer console.
You can also use the developer console and/or Fiddler to find problems with your web site - it will show missing files and javascript errors etc.
If you are reporting an issue with the graphs or gauges, or any other aspect of the display, please make it clear whether you are referring to the user interface or the web pages, or both.
You can turn on extra logging ("debug logging") to the MXdiags files by adding "Logging=1" to the [Station] section of Cumulus.ini. It would be a good idea to turn this on while you are beta testing, so please do so.
You can also turn on data logging, by adding "DataLogging=1" to the [Station] section of Cumulus.ini. This may generate a lot of output, though, so you should probably only turn this on if you are trying to track down a problem with reading data from the station.
You can turn on ftp logging by adding "FTPlogging=1" to the [FTP site] section of Cumulus.ini. Normal and realtime ftp are logged to the same file, ftplog.txt.
You can turn the logging on or off temporarily (i.e. for the current run only, changes do not get affect Cumulus.ini) using the station settings in the user interface.
Any changes to Cumulus.ini should be done with Cumulus stopped.
Thanks.