Something it wrong here.
Yes, and I think it is the lack of something between my ears!
WeatherLink is a Java application.
Most likely.
WeatherCat is a native Mac application.
Agreed.
WeatherCat doesn't do any testing.
Actually it can and especially when first run. At least the version I downloaded (2.0.2 Build 30) can and did. If you look at page 21 of the WC User Manual, you'll see the window that had the "Testing... This may take a few minutes." message. Of course, the image in the manual does not show the "Testing..." text, see below
* for more on how to get that window after the first run of WC.
After I finished outside, I woke up the mini to find it still spinning that 'pizza'. I Force Quit WC (which was shown as
not responding). I started it again and it didn't even open a window, and it reported the same crash log as before.
I finally checked (command-tab) and saw that WeatherLink was, in fact,
still running! I Quit it and re-started WC without any problem.
It has been running fine for the last hour.
Since you still have the User Manual open, look back at the next to last paragraph on page 20.
Finally, make sure you have quit any other weather software...
"
Well, there's your problem!"
Nothing wrong with WC, it was simply the Davis app interfering with communications with the Console. It may also have blocked access to any files it was creating (Permissions). The
problem was not reading the manual!
As for "testing" I can only assume that the initial 'test' was to the Console. It did not begin until I selected the new USB driver from that "Comms Port" dropdown menu. You can also get a 'comms' 'test/check' using the Tools->Station Hardware Options menu item. It will test the Transmitter Battery Status and the Console Voltage. This will be done automatically just by using that menu. There is a "Test Power System" button that "will take a while" as it runs in the background.
*Finally, the Tools->Configure Stations Comms... menu brings up the window seen on page 21. You are warned that WC will Quit and delete the current Comms info. This time, however, it did
not show any "Testing..." message.