Cumulus Support

I have just completed a CumulusMX install on a RaspberryPi3 B+ with an Instromet datalogger.

I had expected issues configuring the port for the data logger however that worked perfectly first time. The issue I have is the Weather34 website is not updating. I initially started with build 3048 however I have moved to build 3049 now by deleting the old CumulusMX folder and copying the new across. I have seen some site updating however it has been sporadic so I have selected Debug logging and Data logging however nothing shows in the folder, I have enabled show hidden files as well just in case...

I know the system is working as I can see the update to current conditions taking place.

Thoughts anyone?

As an update the console shows the following (The MXdiags folder is empty) Note it shows build 3048 although it should be 3049

Doing CumulusMX autorun script...
Current culture: English (United Kingdom)
Serial: 74FECEABEB2DA94ECB5EBA0CD11A7137
Cumulus MX v.3.0.0 build 3048
Today.ini = data/today.ini
Last update=2019-04-25T17:00:00
Start reading history data...
Reading archive data from 25/04/2019 17:00:00 - please wait
Reading archive data from 25/04/2019 17:00:00 - please wait
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
25/04/2019 17:00:40
Type Ctrl-C to terminate
Normal running
System.IO.IOException: Input/output error
at System.IO.Ports.SerialPortStream.ThrowIOException () [0x00012] in <bd46d4d4f7964dfa9beea098499ab597>:0
at System.IO.Ports.SerialPortStream.DiscardInBuffer () [0x00011] in <bd46d4d4f7964dfa9beea098499ab597>:0
at System.IO.Ports.SerialPort.DiscardInBuffer () [0x00006] in <bd46d4d4f7964dfa9beea098499ab597>:0
at (wrapper remoting-invoke-with-check) System.IO.Ports.SerialPort:DiscardInBuffer ()
at CumulusMX.ImetStation.SendCommand (System.String command) [0x00006] in <94ce6159a2904f1baa55a29fe3559466>:0
at CumulusMX.ImetStation.ImetGetData () [0x0004a] in <94ce6159a2904f1baa55a29fe3559466>:0
at CumulusMX.ImetStation.Start () [0x00010] in <94ce6159a2904f1baa55a29fe3559466>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <8f2c484307284b51944a1a13a14c0266>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <8f2c484307284b51944a1a13a14c0266>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <8f2c484307284b51944a1a13a14c0266>:0
at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Press Enter to terminate

I think you need to investigate why you are picking up the b3048 executable.

Can you start it from the command line to eliminate the script please.

I had the CumulusMX folder on the desktop /home/pi/Desktop so I deleted it and downloaded the latest build, extracted it and copied it across so it is now at /home/pi/Desktop/CumulusMX

Launching the file from CL started it OK and the system did run for 5-6 minutes then stopped so I started it again from CL, it still shows build 3048 and I still see no logging to MXdiags.

pi@raspberrypi:~ $ cd ~/CumulusMX
pi@raspberrypi:~/CumulusMX $ sudo mono CumulusMX.exe
Current culture: English (United Kingdom)
Serial: 74FECEABEB2DA94ECB5EBA0CD11A7137
Cumulus MX v.3.0.0 build 3048
Today.ini = data/today.ini
Last update=2019-04-25T17:15:00
Start reading history data...
Reading archive data from 25/04/2019 17:15:00 - please wait
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
25/04/2019 20:36:25
Type Ctrl-C to terminate
Reading archive data from 25/04/2019 20:35:33 - please wait
Normal running
pi@raspberrypi:~/CumulusMX $

I have just launched it again and it is updating OK however still no logging

And you definitely have CumulusMXDist3049.zip ?

https://github.com/cumulusmx/CumulusMX/ ... st3049.zip

I just checked and I have installed from CumulusMXDist3049

I only have CuMX on the desktop of the RPi and once the application has been stopped it is easily removed. Are there any file versions within the folder I can check. It is still working this morning and still not logging. I guess the next thing is to swap back to the old box and reinstall everything from scratch on the RPi and see if that helps any.

Open the zip on your desktop machine, extract CumulusMX.exe and check the file properties/details.

Please zip up your MXDiags folder and post that.

I have downed the machine now and gone back to my old Win10 system. I will take a closer look this evening and update this thread.

Thank you for your help with this.

I could not resist checking...
The MXdiags folder is zero bytes and the file on my Win10 box shows: I will reinstall the OS and CuMX this evening and see how it goes.

OS is reinstalled along with updates, Mono and build 3049 which now looks correct. It is still failing to update the remote server however at least it is logging to MXDiags so I have zipped it up and attached it.

Could this be down to my ftp credentials?

Yes.

I have moved on a bit, I now have it updating in that the wind run is increasing, but the temperature stops at 9,3C which is odd for this time off evening. The time stamp on realtime.txt on the server is changing as well so it does look promising. I am going to give it some time now and see what happens.

Hmm, your data seems to have flat lined around 20:00

Mark, not entirely, the wind feed continued OK however temperature and pressure stopped. The odd thing is the CuMX install 'Now' tab shows the correct readings, so it is all coming OK and only partly heading out.

I have moved the dataloggger back to the old Win10 box now so hopefully the site will start reflecting the true readings.

It 'froze' on your PWS site until you swapped it this morning... So if the admin interface was still updating there was a problem with the file FTP - you need to switch on FTP logging and look it that log. I'd always switch on debug logging too when troubleshooting.