Trixology
WeatherCat => WeatherCat General Discussion => Topic started by: cabut on August 23, 2018, 07:23:16 PM
-
Hi,
New installation of WC. Stuck on ?waiting for weather data to become ready.?
Where should I look to fix the problem?
Thanks,
Cabut
-
Dear Cabut and WeatherCat troubleshooters,
New installation of WC. Stuck on ?waiting for weather data to become ready.?
Where should I look to fix the problem?
I'm assuming this is with your new Davis Vantage Pro-2 station - correct? If I recall correctly, you bought the Davis software to get a data logger. You can use that software to help isolate the problem. See if WeatherLink can successfully connect to your station. If it can't then the problem is with your data logger. If not, it could be something else like having an outdated driver for WeatherCat to use. We have a list of troubleshooting tips including where to get the latest drivers for your Mac on this WeatherCat Wiki page:
http://wiki.trixology.com/index.php?title=Davis (http://wiki.trixology.com/index.php?title=Davis)
Let us know what you discover.
Cheers, Edouard
-
Hi Edouard,
Thanks for your reply.
WeatherLink connects with my station console.
In preparation for the WeatherLink 6.0 installation I downloaded the drivers (SiLabsUSBDriverDisk.dmg) recommended on this site.
The drivers would not let me connect to the console so I downloaded the drivers from the
Weatherlink6.0 CD which are called SLAB_USBtoUART.
Both were installed, perhaps there is a conflict.
Do you happen to know where these drivers can be found on the Mac?
Cabut
-
Easiest way to locate 'unusual' items like drivers:
1. Hold the option key down and click the black Apple icon 9extreme left-hand end of the Menu bar
2. Select the "System Information..." item.
3. Close the "Hardware" and the "Network" items in the window that opens
4. Select the "Extensions" item in the "Software" list
5. When the list appears in the larger, right-hand section of the window, scroll to the items that start with "SiLabs..." (you may have more than one)
You can now see the one that is loaded (there will be "Yes" in the cleverly named "Loaded" column). 5.0.4 is the latest, I think.
In the bottom part of the window is more info on that items than you ever want to know! However, the exact location of the item is beside another clever label called "Location:" (those Apple guys are genius', right! ;P!). The location should start with "/Library/Extensions/..." That is the main Library, not your home Library nor the System Library. ;)
-
Hi Xair,
Fabulous directions, thank you!
I found three from SiLabs, how do I know which one to keep?
See pic.
Cabut
-
If using latest WC and macOS X software, I'd suggest the newest version of the driver. It would appear to me that the two old versions you have are duplicates; same version and install dates. I actually have two SiLab drivers, but only one (the new one) shows as 'Loaded'. ???
If you want to remove (unload) an extension, you can use a couple of methods. However, make absolutely sure you have found/identified the correct file, in this case, it's the two older versions. But the first step is to make a copy of the file. You should be able to option-drag it to your Desktop. Once you have a copy, you can always return it to the correct location if you need to.
DO NOT PUT THE REMOVED EXTENSION IN THE TRASH! The Trash is NOT a storage location. :)
You can remove the file from the /Library/Extension using Terminal. Have you ever used Terminal?
-
Thanks Xair, I think I may have stumbled upon the problem.
It seems the two older versions of the SiLabs driver are in HD/System/Library/Extensions and the new version is in HD/Library/Extensions/
Where should the newer driver live?
Yes, I have installed the latest version of WC 3.01.My Late 2009 Mac mini is running El Capitan.
I have used terminal on occasion.
The first method of removal would be to duplicate the files to the desktop then trash the files in /Library/Extensions is that correct?
What is the process for removing these files using terminal?
And lastly, if the new version, 5.05 is the correct version, can I move it to HD/System/Library/Extensions without fear😊?
Thanks,
Cabut
-
First, there is another choice than removal, there is a safer, in my opinion, Terminal command called 'kextunload', which is exactly what needs to be done. :)
Check the other two drivers and let us know where they are located. If you are lucky, the latest version may already be in the correct location and all you need to do is unload the one in the /System/Library. One command instead of several other steps. ThU32:-)
So, just report the locations of the other two drivers; the second old version and the one new version. [computer]
-
Ok, here are the locations in screen grabs:
-
Thanks. Looks like the new one is in the wrong place. Let's do the corrections one at a time.
Typing in Terminal is very exacting, most mistakes provide no warnings. I will type the commands that will unload the extension old in the correct location. Then we will tackle moving the new one to the correct location.
In case you'd like to review the commands, here's a link that explains them (http://osxdaily.com/2015/06/24/load-unload-kernel-extensions-mac-os-x/).
First, be aware that I cannot actually issue the following Terminal command since I don't have any file in the /Library/Extensions/ location, on this Mac, that I can 'mess' with. Use the following at your own discretion. Even wait for confirmation from others here. ;)
Here is the Terminal command that should unload the old SiLab driver: sudo kextunload /System/Library/Extensions/SiLabsUSBDriver.kext Double-check the text in blue. The "sudo" part tells Terminal that you have temporary permissions to make changes. The rest of the text tells the System exactly what you want to do: Unload the SiLabsUSBDriver.text file located in the Extensions directory of the main Library directory.
Be aware that unloading is not the same as removing, it may not prevent the extension from reloading on the next computer startup. Using this unload command successfully should encourage you in your ability to affect the Mac. You can confirm that the extension has been unloaded by performing another "System Information..." check. Let me know what your results are. :)
-
Hi Xair,
The second link is broken...
I tried to restart in recovery mode, but since I don?t have a monitor for the Mac mini and i?m using screen sharing it it will not connect.
Perhaps I should forgo using Terminal and remove the two manually, then move the latest driver into its proper place. I have made copies of the two older drivers. They are on my desktop.
So what do you suggest from here?
Cabut
-
I think I was typing (and being distracted by family!) while you were working. It appears I also hit the 'Save' button before I had completed editing my prior post. I don't think Recovery mode will be needed, anyway.
Please re-read my post #9 for the process. And thanks for reminding me that you are using Screen Sharing! [banghead]
-
Hi Xair,
Thanks for all your help!
I looked at #9 and I did not see any instructions to remove drivers manually without Terminal.
So I made copies of the two old drivers , trashed the two,and tried to move the new driver to HD/System/System/Library/Extentions. Got a message saying basically you have to install it, moving it was not an option.
No change in launching WC. It will not load.
Right now, I am at an impasse.
Cabut
-
OK, you've got two files on the Desktop and the latest file in the wrong place. Is that correct?
I'd suggest moving the last one out of the System/Library/Extensions directory also. Then find the original download or re-download it, if needed. Then try the 'normal' install method; double-clicking the extension. The OS is what actually "loads" them, normally. At any rate, simply double-clicking the actual extension should automagically install the driver correctly. [tup]
-
Yes, I trashed the two old drivers making copies first.. The new driver works fine communicating with the Davis console, not WC.
Should I just trash the new driver as I did the other two. I assume I should empty the trash?
Cabu
-
Question 1: Exactly how did you install the latest version of the driver?
Question 2: Is WeatherLink still in use/running?
I believe you can use Terminal to remove the copy that is in /System/Library/Extensions/ But, instead of moving it to the correct location, I suggest getting a new copy and let the System install it. Download the new driver, if you don't still have the original download. The plan is to install it in the correct location so WC can use it to get the data the Console is collecting.
-
1. Double clicked on the installer
2. Weatherlink is still running
I don?t know if I can select where it?s installed but it?s a possibility😊
Thanks,
Cabut
-
I don?t know if I can select where it?s installed but it?s a possibility
I don't think you can. It's the OS that does that when you double-click or control-click the installer. The OS keeps a list of what kind of file belongs to all apps, as well as the OS itself. You should also be getting a dialog asking if you want to install the driver for your account or all users. Are you seeing that kind of dialog? Are you set up as an Administrator on the mini?
Is the downloaded file on the mini or the iMac?
Are you sure you are using the installer on the mini?
Did you restart the mini after re-installing the driver?
Have you tried Quitting WC before you install the driver?
Did the driver get installed in /Library/Extensions/ on the mini or your iMac?
-
I will check everything you listed and report back😊
Thanks,
Cabut
-
I do not get a dialog asking all users or just the admin.
I am set up as admin.
It is on the mini
Yes I am using the installer on the mini
Yes I restarted the mini
Yes I quit WC before installing the driver also quit Weatherlink.
It got installed on the mini.
Is it possible that WC 3.01 is not compatible with El Capitan?
This person is having the same problem, see post 2 on this thread:
http://athena.trixology.com/index.php?topic=2786.0
Cabut
-
Thanks for hanging in Xair.
Found the fix.
1. Uninstall WC 3.01
2. Install WC 2.44
Driver: Latest from SiLabsUSDDriver v. 5.05
Works like a charm.
Cabut
-
Is it possible that WC 3.01 is not compatible with El Capitan?
That is possible. Im using WC 3.0.1 on macOS 10.13 High Sierra. I had to update to HS when my old mini died. I think I was using EC and I know it was WC 2.4. I continued with 2.4 for a while with HS, but Stu fixed some Apple-induced graphic problems in WC 3. I now have no way to test on anything less than HS.
Sorry I could not be of any help, but glad things are now working! [cheer]
I am assuming that the SiLabs 5.05 is now installed in the /Library/Extensions/ directory on the mini?
-
Again thank you for percervering 👍.
Yes it lives in Library/Extensions, NOT System/Library/Extensions on my Mini running 10.11.6.
After about a day in a half, after trying everything, I decided to go to WC 2.44. In minutes after set up, there was, finally... joy😃!
Thanks,
Cabut
-
Again thank you for percervering 👍.
Yes it lives in Library/Extensions, NOT System/Library/Extensions on my Mini running 10.11.6.
After about a day in a half, after trying everything, I decided to go to WC 2.44. In minutes after set up, there was, finally... joy😃!
Thanks,
Cabut
I went back to 2.44 and it did not help my Comms problem.
-
Hi,
Sorry about that...
Did you remove 3.01 and any associated files first? I used an app called Clean App which removes all associated files. I believe you can download a free trial which will remove 10 apps before you have to pay. It may be a long shot, but I removed 3.01 first, using this method.
Cabut
-
There is nothing you need to remove from 3.x other than the app itself. You want to keep the rest of the files so you have all your data when running a previous version of WC.