Cumulus MX Faults and Stops Every 4 to 5 Days

[davegunnell]

Cumulus MX build 3039 running on 64-bit Windows 10 Professional on an Intel Compute Stick keeps stopping every 4 to 5 days assuming its generating some sort of a fault and blowing off. Attached is the last WXDiag file where it was started on the 12th and the last entry on the 15th is

2016-08-15 10:55:41.434 Sending command LOOP 50 - pass 1

I have also attached Cumulus.ini

Cumulus.ini

20160812-105716.txt

[steve]

It looks like it's hung in the system serial or USB code. If you turn on data logging, it might be possible to say more than that, the next time it happens. It could be that I need to set an explicit timeout somewhere.

[endfm]

Hi Dave,

Do you see loss of connection on the weather monitor? Specifically outside and wind + rain totals?

cheers

/end

[davegunnell]

Do not seem to be loosing connections or anything. Will run again with data logging turned on.

[steve]

Does restarting MX get it going again, or do you have to do anything else?

[davegunnell]

Restarting Cumulus MX is enough I dont have to reboot. Attached is the latest with datalogging turned on. It looks like last entry is reading loop packets before it blows off.

I have the USB plugged into USB 3.0 hub so trying to plug into only USB 2.0 port on the Intel Compute Stick and do another run. This may be one of those USB UART Serial USB 3.0 compatibility problems.

[steve]

The last thing in the logs is it receiving data packet 37 out of 50 at 08:01:47 - how long after that did you capture the diags file? It's odd that there's nothing at all logged after that. It should have logged the fact that it wrote an entry to the data log at 08:05, if you left it that long. I can't tell whether the problem is that it didn't receive any further data from the console, or whether it just stopped working completely.

I added a timeout for the data reads in build 3041 - you could try that, to see if the problem is that the data from the console just stops, so it waits forever for data that isn't coming.

[davegunnell]

CumulusMX.exe stopped running on its own I suspect it generated a protect fault.

[steve]

The timeout is unlikely to help, then. Sounds like a hardware or driver problem.