Cumulus MX Dashboard Red blinking Data stopped

[KK7GO]

Hi,

I am new to Cumumlus MX software. Please accept my apologies if I am posting in the wrong forum. If so, please direct me to the correct forum site. Thank you.

Here is my weather station particulars:

Davis Vantage Pro 2
Raspberry Pi 4 b
Meteo-Pi Hat Data Logger

I have had the VP2 run with Weewx for awhile. The Meteo-Pi data logger has worked flawlessly. I am switching to CumulusMX due to liking the program.

The CumulusMX serial port is set to ttyS0 and the baud rate for ttyS0 is set at 19200. I also made the file changes in the /boot folder files config.txt and cmdline.txt Setting up Meteo-Pi (Part 2) - Prodata Systems Weather Systems. The VP2 baud rate is also set to 19200

When I run the cumulusmx.exe in mono terminal, I get this as a reply:


Cumulus MX v.3.15.3 build 3173
Working Dir: /home/pi/CumulusMX/

Cumulus running at: http://localhost:8998/
http://192.168.1.9:8998/

Open the admin interface by entering one of the above URLs into a web browser.

Today.ini = data/today.ini
Last update=2022-03-24T09:41:16
Connected to station
3/24/2022 11:18:57 AM
Type Ctrl-C to terminate
Downloading Archive Data
Downloading Archive Data
Normal running

However, at the bottom of Dashboard accessed via localhose:8998 on the RPi browser, the red Data Stopped light blinks.

The Meteo-Pi yellow and green led's are blinking as seen in prior use with Weewx.

In the RPi raspi-config UI I have Serial Port enabled along with IC2 enabled.

I am sure I am missing something here. I have looked at the FAQ and forum topics to locate my issue without success.

Thank you for the help.

Ron

[mcrossley]

Hi Ron, could you zip up and attach the MXdiags folder for me please?

[KK7GO]

Hi Mark,

Here you go and thank you for looking into this.

Ron

[mcrossley]

Hi Ron, basically CMX either cannot connect to the ttyS0 port at all "Error - System.IO.IOException: Resource temporarily unavailable", or when it can it does not see any data.

Are you sure nothing else is try to read the station?

[KK7GO]

Hi Mark,
The RPi is dedicated to the Davis VP2. Nothing else is connected. The Meteo-Pi Data Logger is on the RPi via a HAT. Doe the port 8998 need to be opened in my router?

Wondering if the Meteo-Pi is configured incorrectly.

I received this from Wojtet, the Meteo-Pi developer. Not sure if I ran the command line correctly. I am not all that good with Linux.


stty 19200 -F /dev/ttyS0
echo -e "SETPER 5\n" > /dev/ttyS0
echo -e "CLRLOG\n" > /dev/ttyS0

first line is setting serial port speed to the same as console
second is sending archi interval as 5
echo -e "SETPER 15\n" > /dev/ttyS0 - will be 15 minutes
"SETPER <Archive interval in minutes-decimal>"
Sets the Vantage archive interval. Valid values are (1, 5, 10, 15, 30, 60, and 120).

3rd line is to clear arch memory after period changed.

I saw the baud rate change by using

stty -F /dev/ttyS0 19200

This might be a wrong command string.


Wondering if I should start over. If so, is there a installation doc for installing via the Linux terminal?

I apologize for going down this rabbit hole. Thanks for at least looking at this problem.

Ron

[mcrossley]

I'm away today, but the clrlog is superfluous, the setper clears the log anyway.

I'll look up the commands when I get home to start an interactive session with the serial port, but do you get any responses from those commands?

[KK7GO]

Good Morning Mark,

When I run those commands, the curser goes to the next line without a BASH. No errors.

Thank you,

Ron

[KK7GO]

Hi Mark,

Well, I am very sorry to have run you down the rabbit hole. I did some more checking and went back to level 1 troubleshooting tactics. The modular connector seemed to no be seated all the way or the Meteo-Pi module was not seated properly into the Davis console. Now waiting for the ISS cluster to report to the console via wirelessly.

Again, I am sorry for not picking this up earlier.

Thanks

Ron

[mcrossley]

OK, so you have it working now, good.

It looks like you have a mismatch in the logging intervals on the station and in CMX though - a consequence of that is that station sends the entire logger contents every time CMX requests some logger data, that is slow process.

[KK7GO]

Thanks Mark,

I now have all of the logging settings the same. Is this correct?

Ron