Cumulus Support

Hello,

I downloaded and installed the Raspberry image on my Rasbpeery PI and settup to run a WMR200 Station.
But I have this error on log file:

WMR200 station not found!

My station is correctly plugge on usb port.

Do you know why please?

Thank you for your help

My guess would be that you have not correctly identified the USB port that the WMR200 to.

Go to a command (terminal) prompt and type in lsusb. Locate your WMR200 and use that port address in CumulusMX.

Thanks for your reply.
But I don't find my WMR200 in fact: But on my station, the "usb" label is displayed.

And on the init file, there are:

Type=9
Model=Oregon Scientific WMR200
ComportName=/dev/ttyUSB0

But on the log file, there are no ref to the port.

In the com port settings for CumulusMX in the station settings having selected Oregon Scientific WMr200 I would set it to /dev/ttyusb0 and then restart CumulusMX.

Thanks David,

But it's already the case.
In the Cumulus.ini :

The WMR200 does not work with a COM port, it is read directly as a USB device with a VID/PID of 0FDE/CA01.

Your lusb command is not showing that device. So the problem would appear to lie with either the WMR200, the cable, or USB hub (if you are using one).

Mine now appears to have the same problem, directly after updating to build 3282. No problems prior. It either says WMR200 station not found in the CumulusMX window or if not, never gets to "normal running" phase. I have restarted PC / CumulusMX several times. See screenshot.


Is there an archive of older CumulusMX builds I can try to go back to?

Update: It seems to be actively reading history now as the index.html webpage for the site appears to be scrolling through showing historical data.

All I did differently this time was click in the CMX window a bunch of times and after a short while this seemed to happen. I hadn't tried this interaction for the last few days (stopped working on Monday) previously. Coincidence or a real thing?

I have had CMX stop responding before at this stage between where it claims to be reading history data (it used to only take a few minutes depending on how long the PC had been turned off) and interacting / clicking the window seems to *unfreeze* it. Unfortuately I can't be present at each PC restart to do this but wondering why this actually happens?

Switch on debug logging, restart MX and post the latest MXdiags file.

There have been no material changes to the WMR200 code for a long time.