Cumulus stopped receiving data

[Sandro]

Hello,
I ran Cumulus today at 1pm, now (3am) I opened it from the tray and found out that what I was seeing was different than what I could see on the station, in fact Cumulus was displaying "last data read at 23:09". In the diags I found

Code: Select all

2009-12-15 22:59:00 : Writing todayfile, LastUpdateTime = 15/12/2009 22:59:00 raindaystart = 6,71999979019165
2009-12-15 23:00:00 : Writing todayfile, LastUpdateTime = 15/12/2009 23:00:00 raindaystart = 6,71999979019165
2009-12-15 23:01:00 : Writing todayfile, LastUpdateTime = 15/12/2009 23:01:00 raindaystart = 6,71999979019165
2009-12-15 23:02:00 : Writing todayfile, LastUpdateTime = 15/12/2009 23:02:00 raindaystart = 6,71999979019165
2009-12-15 23:03:00 : Writing todayfile, LastUpdateTime = 15/12/2009 23:03:00 raindaystart = 6,71999979019165
2009-12-15 23:03:45 : Invalid message: 
2009-12-15 23:03:45 : Access violation at address 06624191. Write of address 6822AB02
2009-12-15 23:04:00 : Writing todayfile, LastUpdateTime = 15/12/2009 23:04:00 raindaystart = 6,71999979019165
2009-12-15 23:05:00 : Writing todayfile, LastUpdateTime = 15/12/2009 23:05:00 raindaystart = 6,71999979019165
2009-12-15 23:06:00 : Writing todayfile, LastUpdateTime = 15/12/2009 23:06:00 raindaystart = 6,71999979019165

what happened and why? could this happen often?
I dont remember doing something that could have caused it in that time period.
The strange thing was that Cumulus continued to log the data for hours with the same last data received.
Could it be the serial-USB adapter that I'm going to delete soon? (I hope)

[steve]

That error message is a problem with the inter-thread communication which Cumulus uses; some sort of corruption has occurred internally (nothing to do with your USB adapter). It shouldn't have caused any problems, and it seems it did continue reading the data for a few minutes after that. I don't know why it stopped reading the data, unless a related problem with the thread mechanism caused the thread which reads the data to crash. I assume there's nothing unusual in the diag log after this, or you would have posted it.

[Sandro]

Yes but after the error it did not log the current data but repeatedly the last one before the error

[steve]

Yes but after the error it did not log the current data but repeatedly the last one before the error

Yes, some problem caused it stop reading the current data. I don't know what that problem was, maybe your USB adapter...

[Sandro]

Thanks