Comms reset not working with 10.10.1

[jcbeckman]

I have a Davis Vantage Vue station connected to a Mac Pro running 10.10.1. Once every day or two, the comms craps out on the USB connection. Before 10.10.1, Weather Cat (2.01) would do a reset and it was always successful. Since installing 10.10.1, the resets don't work anymore, and I must physically disconnect the connection and then restart WeatherCat. It's then fine until the next hang. I'm sure Apple probably changed something that broke the reset I have attached a diagnostic log from when the latest fail occurred.

[WCDev]

Yes, it is entirely OS dependent. If it stops responding, we ask the OS to unload the driver and wait. If it does unload, we then try to re-instantiate it, if that's OK, we then try to open it and if that's Ok carry on. Otherwise, all we can do is alert you.

See http://wiki.trixology.com/index.php/Electronic_Interference_Effects_on_Station_Hardware/Data_Logger/USB_Cable for general hints and tips to avoid this problem.

 

[jcbeckman]

I guess I was hoping you would be able to see some difference in how you do the reset between 10.10 and 10.10.1, since the comms reset worked every time then. I already have the updated power supply, plugged into a UPS, with the supplied USB cable with ferrite traps on it plugged directly into my Mac, so I really can't mitigate it any more.

[WCDev]

Unfortunately there isn't anything that can be done for this in WeatherCat - either the OS will release the driver or it won't - if it doesn't it's because it either thinks there's some other software also using the driver or an OS bug or the driver has crashed in such a state it cannot be unloaded. Over the years, various OS versions have broken this functionality, only to be restored in a subsequent OS release and/or Silicon Labs driver updates.

Something you could try, is going to the Tools menu in WeatherCat and select 'Configure Station Comms' - this will cause WeatherCat to forget the current connection information and quit. When you launch it again, you'll have to reconfigure the communications, picking up new connection information. I wouldn't be too hopeful this will affect it, but it might be worth a try.

[jcbeckman]

Thanks. I tried this already as well. Can you give out the the command used? I see I can run a use program on failure, perhaps trying again using sudo will get the driver to unload/reload.

[jcbeckman]

Ha - of course, just to poke me in the eye, today the comms reset worked. Go figure. I haven't done anything that I know of to change things.

[Blicj11]

Ha - of course, just to poke me in the eye, today the comms reset worked.

Steve Jobs helping out from the other side?