232
edits
Cumulus MX FAQ: Difference between revisions
m
Text replacement - "http://sandaysoft.com/forum/" to "https://cumulus.hosiene.co.uk/"
(Created page with "<big>'''Cumulus MX FAQ'''</big> *If you use non-English settings, comma decimals etc, you will experience problems on Linux/OS X with Mono version 3.2.8 (e.g. on Raspberry Pi...") |
SaratogaWX (talk | contribs) m (Text replacement - "http://sandaysoft.com/forum/" to "https://cumulus.hosiene.co.uk/") |
||
| Line 19: | Line 19: | ||
*Davis stations sometime supply 'error' values such as 255 for wind speed. Cumulus ignores these and may log some of them to the diags file, if you have debug logging turned on | *Davis stations sometime supply 'error' values such as 255 for wind speed. Cumulus ignores these and may log some of them to the diags file, if you have debug logging turned on | ||
*Serial device names on Linux are not COM0 etc as in Windows. You need to specify something like /dev/ttyUSB0 - do a dmesg at a command line prompt and look for the actual device name from your adapter. If dmesg says your cp210x converter (as on Davis stations) is attached to ttyUSB0, for example, you need to put /dev/ttyUSB0 for the serial port name in MX. You can set the serial port name in the MX user interface, but if for some reason you want to do it by editing Cumulus.ini, note that the item in MX is called ComportName (which is a string, for the full device name, e.g. COM1 or /dev/ttyUSB0) rather than 'Port' which is just an integer. If you have not run MX yet, this item will not exist, so you will need to add it (in the [Station] section). | *Serial device names on Linux are not COM0 etc as in Windows. You need to specify something like /dev/ttyUSB0 - do a dmesg at a command line prompt and look for the actual device name from your adapter. If dmesg says your cp210x converter (as on Davis stations) is attached to ttyUSB0, for example, you need to put /dev/ttyUSB0 for the serial port name in MX. You can set the serial port name in the MX user interface, but if for some reason you want to do it by editing Cumulus.ini, note that the item in MX is called ComportName (which is a string, for the full device name, e.g. COM1 or /dev/ttyUSB0) rather than 'Port' which is just an integer. If you have not run MX yet, this item will not exist, so you will need to add it (in the [Station] section). | ||
*If you are having problems after upgrading to Windows 10, see this post - | *If you are having problems after upgrading to Windows 10, see this post - https://cumulus.hosiene.co.uk/viewtopic.php?f=2&t=14148 | ||
*Mono 4.2 is known to not work with Cumulus MX with USB stations, for reasons currently unknown. Some other versions of Mono may have the same issue. 4.6.x and 4.8.x appear to have the same issue, for example, and also later versions of Mono. The main issue is an incompatibility with the USB library which MX uses. The best version to use is 3.2.8, which is the default version in many Linux distributions. If you have to use commas for decimal separators, 3.2.8 is not suitable, but 4.0.x is probably the best version for you. | *Mono 4.2 is known to not work with Cumulus MX with USB stations, for reasons currently unknown. Some other versions of Mono may have the same issue. 4.6.x and 4.8.x appear to have the same issue, for example, and also later versions of Mono. The main issue is an incompatibility with the USB library which MX uses. The best version to use is 3.2.8, which is the default version in many Linux distributions. If you have to use commas for decimal separators, 3.2.8 is not suitable, but 4.0.x is probably the best version for you. | ||
*Cumulus MX will not run on Windows IOT | *Cumulus MX will not run on Windows IOT | ||