555
edits
FAQ: Difference between revisions
→Cumulus stops at the "Downloading data" screen
m (→Directory related problems in FTP: Some changes re Cumulus 1 and MX differences) |
|||
| Line 707: | Line 707: | ||
== Cumulus stops at the "Downloading data" screen == | == Cumulus stops at the "Downloading data" screen == | ||
If you have a Fine Offset station, this is probably caused by the station's interface locking up. You should be able to get it going again by doing a reset - remove batteries and the USB cable. Recent Fine Offset models have a problem where they can lock up frequently, requiring a reset. From version 1.9.3 of Cumulus onwards, there is an option to synchronise the reading of data with the console writing the data, to avoid doing both at the same time, and this seems to avoid most lockups. The setting is "Synchronise Fine Offset reads" on the station settings screen. | If you have a Fine Offset station, this is probably caused by the station's USB interface locking up - a known problem with some Fine Offset stations. You should be able to get it going again by doing a reset - remove batteries and the USB cable. Recent Fine Offset models have a problem where they can lock up frequently, requiring a reset. From version 1.9.3 of Cumulus onwards, there is an option to synchronise the reading of data with the console writing the data, to avoid doing both at the same time, and this seems to avoid most lockups. The setting is "Synchronise Fine Offset reads" on the station settings screen. | ||
If you look in the status bar at the bottom of the Cumulus window, there may a message "Error: no response"; this would confirm that the station has locked up and needs resetting. | If you look in the status bar at the bottom of the Cumulus window, there may a message "Error: no response"; this would confirm that the station has locked up and needs resetting. | ||
If you are using the "Synchronise" setting but are still getting frequent console interface lockups, then the clocks on the console and the platform running Cumulus may be drifting too far between synchronisations. Look in the diags files for the word "drift" and see how many seconds apart the clocks are drifting. If it is more than 3 seconds, you will need to adjust the period that Cumulus allows where it doesn't read the console data. Stop Cumulus and edit Cumulus.ini. In the [Station] section, add a line: | |||
FOReadAvoidPeriod=N | |||
where N is the required setting in seconds. If you find you are getting a drift of 9 seconds, say, you might set the value to 10. | |||
== Cumulus locks up when it starts and I have to use the task manager to kill it == | == Cumulus locks up when it starts and I have to use the task manager to kill it == | ||