Cumulus Support

I installed the program CumulusMX being careful to use the mono 4.0.5, as recommended by all. After launching the program, and silky parameters on 8998 Toggle Next page to reboot I get the same response that the station does not appear. I tried to change COM ports with the same result. I state that with Cumulus conesso to PC works perfectly. What could I have missed? Grzie we potra help

pi@raspberrypi:~/CumulusMX $ sudo mono CumulusMX.exe
Current culture: English (United Kingdom)
Serial: 74FECEABEB2DA94ECB5EBA0CD11A7137
Cumulus MX v.3.0.0 build 3043
Today.ini = data/today.ini
Last update=2017-02-01T23:41:03
Unable to connect to station
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Starting web socket server on port 8002
01/02/2017 23:41:04
Type Ctrl-C to terminate

What have you put for the serial port in MX? What port does 'dmesg' say your station is on (as described in the MX FAQ)?

I tried plugging the COM0 to COM6 with the same result. The CumulusMX program starts and I view to the 8998 page screen, I put all the settings, but after starting the whole no data appears, and shows me absent station. With cmando lsusb the serial cable is displayed, but no data is loaded.

What port does 'dmesg' say your station is on (as described in the MX FAQ)?

This will help to solve the problem please give an answer to the question.

igorzo wrote:I tried plugging the COM0 to COM6 with the same result. The CumulusMX program starts and I view to the 8998 page screen, I put all the settings, but after starting the whole no data appears, and shows me absent station. With cmando lsusb the serial cable is displayed, but no data is loaded.

Raspberry PI/Linux doesn't use COMX conventions for devices.

Use the already suggested, issue a dmesg command and see what it comes back with.

I'm not an expert in Linux, today I installed all again, from NOOBS to CumulusMX. After starting the CumulusMX, I went on the 8998 page for the setting. I left as a serial port COM0 indicated. But the result is always the same as the start CumulusMX does not find the station. I run the command dmesg I can indicate what should I look for. Excuse me, but I'm new in this environment.

These data of the USB port on your Raspberry conessa the VP2

pi@raspberrypi:~ $ dmesg | grep -i usb
[ 0.154880] usbcore: registered new interface driver usbfs
[ 0.154960] usbcore: registered new interface driver hub
[ 0.155054] usbcore: registered new device driver usb
[ 1.305627] usbcore: registered new interface driver smsc95xx
[ 1.706940] dwc_otg 3f980000.usb: DWC OTG Controller
[ 1.706980] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 1.707016] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[ 1.707286] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.707302] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.707315] usb usb1: Product: DWC OTG Controller
[ 1.707327] usb usb1: Manufacturer: Linux 4.4.34-v7+ dwc_otg_hcd
[ 1.707339] usb usb1: SerialNumber: 3f980000.usb
[ 1.708176] hub 1-0:1.0: USB hub found
[ 1.709190] usbcore: registered new interface driver usb-storage
[ 1.829689] usbcore: registered new interface driver usbhid
[ 1.829698] usbhid: USB HID core driver
[ 2.078762] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 2.279087] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[ 2.279106] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.279947] hub 1-1:1.0: USB hub found
[ 2.558792] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 2.659108] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[ 2.659132] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.722574] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:c2:8d:0d
[ 2.798845] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[ 3.282924] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001
[ 3.282950] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.282963] usb 1-1.2: Product: FT232R USB UART
[ 3.282976] usb 1-1.2: Manufacturer: FTDI
[ 3.282988] usb 1-1.2: SerialNumber: A9YP5ZRF
[ 3.408869] usb 1-1.4: new low-speed USB device number 5 using dwc_otg
[ 3.542857] usb 1-1.4: New USB device found, idVendor=045e, idProduct=008c
[ 3.542884] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.542897] usb 1-1.4: Product: Microsoft Wireless Optical Desktop® 1.00
[ 3.542910] usb 1-1.4: Manufacturer: Microsoft
[ 3.585719] input: Microsoft Microsoft Wireless Optical Desktop® 1.00 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0/0003:045E:008C.0001/input/input0
[ 3.586303] hid-generic 0003:045E:008C.0001: input,hidraw0: USB HID v1.11 Mouse [Microsoft Microsoft Wireless Optical Desktop® 1.00] on usb-3f980000.usb-1.4/input0
[ 5.138831] usbcore: registered new interface driver brcmfmac
[ 6.022571] usbcore: registered new interface driver usbserial
[ 6.022985] usbcore: registered new interface driver usbserial_generic
[ 6.023332] usbserial: USB Serial support registered for generic
[ 6.035816] usbcore: registered new interface driver ftdi_sio
[ 6.036202] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 6.036786] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[ 6.038339] usb 1-1.2: Detected FT232RL
[ 6.041238] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
[ 30.980305] usb 1-1.4: USB disconnect, device number 5
[35220.743829] usb 1-1.2: USB disconnect, device number 4
[35220.744210] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[35395.338187] usb 1-1.2: new full-speed USB device number 6 using dwc_otg
[35395.820763] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001
[35395.820787] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[35395.820800] usb 1-1.2: Product: FT232R USB UART
[35395.820813] usb 1-1.2: Manufacturer: FTDI
[35395.820826] usb 1-1.2: SerialNumber: A9YP5ZRF
[35395.870789] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[35395.871049] usb 1-1.2: Detected FT232RL
[35395.873251] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0

[35395.873251] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0

A Davis logger would normally say cp210x rather than FTDI. Do you have a Davis logger or a third party logger? Do you have any other USB device connected to the Pi?

You could just try /dev/ttyUSB0 for the serial port.

On USB not be connected any other device, it states that the cable that goes from VP2 to Raspberry not be original, but the Davis AnemOS Electronics. I

In that case, that must be your logger, so /dev/ttyUSB0 should work.

Now I put the name of the serial as you indicated serial port : /dev/ttyUSB0

at page 8998, on the dashboard does not appear no data, checking on now, gauges, today / yesterday and records the parameters are now shown

pi@raspberrypi:~/CumulusMX $ sudo mono CumulusMX.exe
Current culture: English (United Kingdom)
Serial: 74FECEABEB2DA94ECB5EBA0CD11A7137
Cumulus MX v.3.0.0 build 3043
Today.ini = data/today.ini
Last update=2017-02-06T21:13:51
Connected to station
21:13:52 Downloading Archive Data
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Starting web socket server on port 8002
06/02/2017 21:13:53
Type Ctrl-C to terminate

Are you saying that the dashboard page has no data, but all of the others, including now and gauges, do have data?

Thank you so much Steve


is now also appeared on the dashboard, it looks like he needs a bit of time before loading.

I'm having the same problem!
I use the davis vantage vue and raspberry pi 3 with serial to usb converter; Installed the cumulusMX and when I run it, this appears:
But the localhost page is empty, with no data. I've already wait, but no changes happened.
I want to know if there is some command to "reset" the datalogger or other command to test if the serial/usb adapter is really working.

Two things to check.

1) Is there a lot of data that Cumulus has to download as that may take some time (it does say downloading data in the log).

2) Have you pressed F5 or hit the refresh icon when you are on the start screen as it does not automatically refresh, so you may be sat there just watching the original start data.

If you have done both of these then send the mxdiags in and it can be looked at.