Getting a non-fatal error when starting CumulusMX

[stuartp]

Have just started using MX on my Raspberry Pi - I must admit I am very pleased with the outcome. I do however get a consistent error message when starting, just after it connects to the station :

System.ArgumentException: Invalid value: -60000
at System.Timers.Timer.set_Interval (Double value) [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) System.Timers.Timer:set_Interval (double)
at CumulusMX.Cumulus.StartTimers () [0x00000] in <filename unknown>:0
at . (System.Object , System.ComponentModel.RunWorkerCompletedEventArgs ) [0x00000] in <filename unknown>:0
at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted (System.ComponentModel.RunWorkerCompletedEventArgs e) [0x00000] in <filename unknown>:0
at System.ComponentModel.BackgroundWorker.<CompleteWorker>m__1 (System.Object darg) [0x00000] in <filename unknown>:0
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Press Enter to terminate

I have attached the latest diagnostic file. This does not seem to affect the actual running of the software as far as I can make out. Could it be something carried over from my XP setup in the config file?

Thanks,

Stuart

[nitrx]

Are you sure starting Cumulus with mono in the right directory

Code: Select all

sudo mono CumulusMX.exe

?

[freddie]

I have attached the latest diagnostic file

You need to enable debug logging in your Cumulus config. See https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=12991 for instructions. Without debug messages being logged in the diags file it is very difficult to perform any diagnosis.

[steve]

It seems to be trying to start a timer with a negative period (minus 60 seconds), so could well be a problem in your Cumulus.ini file.

[stuartp]

It seems to be trying to start a timer with a negative period (minus 60 seconds), so could well be a problem in your Cumulus.ini file.

I have upgraded MX to the latest release and enclose a diagnostics file with debugging turned on. In the meantime I will try starting with a new Cumulus.ini and see what I get.

Stuart

[steve]

You should be able to find the timer with the value of -60 fairly easily, either by searching Cumulus.ini or looking at the settings through the UI. It may not necessarily be an enabled timer, it's the setting of the interval which is causing the error message.

[stuartp]

You should be able to find the timer with the value of -60 fairly easily, either by searching Cumulus.ini or looking at the settings through the UI. It may not necessarily be an enabled timer, it's the setting of the interval which is causing the error message.

Hi Steve. I took the opportunity to rebuild the CumulusMX.ini file from a fresh install. All works fine now. Thanks for the hints. MX is working very well btw - I have it on my old Raspberry Pi in headless mode and it hardly stresses the processor or memory utilisation. Very impressive.

Stuart