Data Not Being Recieved by APRS/CWOP, PWS & WOW

[acatalano]

I have CumulusMX running on an RPi 2B. I have spent the last week refining the setup so that I can upload Vantage Vue/USB Datalogger supplied station data and still photos to the Weather Underground site reliably. I am using the Raspistill command to take the picture with the RPi camera, and WPUT to FTP the data within CRON. Just two lines does it all. Its taken a bit of fiddling to get it to work reproducibly. I have been moving the Vantage Vue back & forth from my Win7 machine to the RPi to test the setup. Most of the time up until this past Sunday all the sites were being serviced by Cumulus 1.X on the Win 7 machine. Satisfied that everything was OK with the RPi, I opened the two Cumulus files containing the station and internet settings (BTW I much prefer the setup page in the "old" Cumulus to the MX version) and copied everything over. After a day of waiting and the Weather Underground site behaving I checked on the PWS and APRS/CWOP & WOW (UK) site. No data had been uploaded. My typing is not the best, so I figured I had some typos so I went back over all of it, this time using the station and internet menus within Cumulus MX instead of using the text editor, Nano on the RPi. So far still no data upload. Any ideas what I am messing up? Is it possible there is some conflict with the various processes going on simultaneously (photo, ftp & CumulusMX) on the RPi? CumulusMX seems to be running just fine with CRON timing the pictures and uploads.

[steve]

BTW I much prefer the setup page in the "old" Cumulus to the MX version

It's inevitable that I'm not going to please everyone all of the time, but I'm surprised by that. The MX internet settings page is, to me, far cleaner than the Cumulus 1 settings screen, and everything is much easier to find. It's also going to be much easier to extend and include more settings. But anyway...

Could you paste the relevant settings from the Cumulus.ini file here, please? Don't forget to mask the passwords.

If you turn on debug logging (in the options section on the station settings screen) then attempted updates to the various services should get logged to the MX diags file, along with any errors returned.

[BigOkie]

BTW I much prefer the setup page in the "old" Cumulus to the MX version

It's inevitable that I'm not going to please everyone all of the time, but I'm surprised by that. The MX internet settings page is, to me, far cleaner than the Cumulus 1 settings screen, and everything is much easier to find. It's also going to be much easier to extend and include more settings. But anyway...

Could you paste the relevant settings from the Cumulus.ini file here, please? Don't forget to mask the passwords.

If you turn on debug logging (in the options section on the station settings screen) then attempted updates to the various services should get logged to the MX diags file, along with any errors returned.

I agree. I love the minimalist feel to this version. A command line window running (hopefully at some point this could have the option to run as a service but I see the need for this) and it's easy on resources. Dashboard via the web, so not only can you see the interface from home, but literally from any location with internet access, as long as you open the correct ports.

And after I returned from a 1.5 year hiatus from Cumulus I was happy to see that all the data files were interchangeable. Made the switch back pretty easy. The hard part was migrating all my data from the interim period into Cumulus. Wasn't the fault of Cumulus, either.

[water01]

but literally from any location with internet access, as long as you open the correct ports.

Not a very safe thing to do as this will allow access to Cumulus computer by anyone using a port scanner as there is no password protection on the interface and they could cause untold harm!!

[BigOkie]

but literally from any location with internet access, as long as you open the correct ports.

Not a very safe thing to do as this will allow access to Cumulus computer by anyone using a port scanner as there is no password protection on the interface and they could cause untold harm!!

I'm a network engineer..I know what I'm doing. I restrict access by port on my machine to specific IPs when on the external. I have a range of mobile ips I use, as well as some from work. Believe me, I'm more careful than most.

[acatalano]

Steve
Many thanks for your help. I've uploaded the Cumulus.ini file scrubbed of passwords and the latest MX Diag.txt file. I looked thru both again but the MXDiags file is tough to interpret intuitively.

[steve]

It appears not to be performing regular tasks (it looks like it isn't logging entries to the log file either). I'm not sure why this is, but it is usually because it thinks your station isn't working properly. It's updating WU because you have rapid fire selected. From your WU page, it looks like you have an issue with your pressure reading, it is far too low - it looks like you haven't set your altitude in the console, so you are getting your local pressure rather than corrected to sea level. However, you are getting a pressure reading, so that doesn't really explain why it isn't performing regular tasks.

Could you have a look at the monthly log files to see when it last logged an entry - if at all?

Could you also please check whether Cumulus is updating the wxnow.txt file in its 'home' directory once a minute?

[acatalano]

Steve
I have no wxnow.txt file in the /home directory. Did a "find" and it does not appear to exist. I of course saved by Cumulus 1.X program and file and moved over to the Pi on Sunday the 12th. That's when the problem started. The July 15 data files appears to end at that time. I checked the console and the altitude is correctly set to 6660 feet. I'm pretty sure I moved that data over to the RPi Cumulus config file but I'll check again. (I am using the Weather Envoy with USB datalogger with Cumulus whether on the RPi or Win7 box).

I wonder if I should reboot the whole shebang?

[acatalano]

I hope this isn't a duplicate post. I put a message together and I'm afraid I exited before posting so here goes...

Rebooting the RPi seems to have solved the problem (mostly). When I started CumulusMX after the reboot it gave the message "last update July 12 2015" (changed to US notation)which is when the problem began. The July 15 data file promptly filled up with data filling the missing interval from 7/12/15 to today 7/16/15.

Cumulus had been throwing messages periodically but I did not interpret them as error messages; I believe they where IP addresses which made no sense (maybe 127.0.0.8?)

Data now is appearing on the other websites. HOWEVER the pressure is still wrong! I checked the altitude on the Console which was correctly set, but the data is being logged by the Weather Envoy. The altitude (6660 feet) is correctly listed in the station setting of CumulusMX. Not sure what's going on. The Weather Underground site is still wrong.

[acatalano]

More info...

Cumulus is throwing two messages:
"Connected from 127.0.0.1:33087"
"Disconnected from 127.0.0.1:33087"

Otherwise OK. Also the pressure on the Cumulus gauges indicate the uncorrected pressure, even though the 6660 ft altitude is in the config file.

As an aside I'm always amazed how quickly pressure drops with altitude. 23 inches here compared to 30 at sea level. Water boils at 196F instead of 212F

[steve]

Cumulus doesn't use the altitude in its own config to correct the pressure, it lets the VP2 do it. I suspect that the envoy doesn't have your altitude configured in it, and you can't use Cumulus to set it. You will either need to use Weatherlink, or connect a terminal program and type in the command yourself - I made a post about this only yesterday, as it happens.

[acatalano]

Sorry to post so many messages..
I called Davis and they say the pressure is measured and corrected within the Console and thus the data logger receives corrected info. However although the Weather Envoy measures the pressure locally it has no value of altitude so the data logger gets the actual, uncorrected pressure. This would explain why all my pressures are incorrect (well really just uncorrected). So even though I have entered the altitude in CumulusMX, do I net to set a "flag" to invoke the correction? I'm pretty certain the altitude is in the config file. BTW the console displays the corrected pressure.

[acatalano]

I understand the pressure correction issue now. Does this mean that for the RPi, I would need to disable the data upload to the various sites and process the data stream coming from CumulusMX, or intercept the data before it got to Cumulus? Neither sounds especially easy.

Might you consider adding this as a "feature" to MX?

[steve]

Sorry, I don't understand what you're suggesting. As I understand the problem, you need to set your altitude in the Envoy, so that it calculates the correct sea-level pressure.