cloudy

Author Topic: Getting the wmr100/wmr200 to work  (Read 34879 times)

0 Members and 2 Guests are viewing this topic.

Offline tivoklr

  • Posts: 12
  • Minturn, CO USA
    • wunderground archive
SO FRUSTRATED
« Reply #60 on: June 09, 2009, 03:57:24 PM »
I am so frustrated with WD on the mac and my OS WMR200A.

I had everything working for a few weeks. Updates to wunderground were perfect.

I updated to 10.5.7 from 10.5.6 and I believe this is when the problems started. I have reinstalled the newest current version of WD several times, each time deleting the /library/app support/wd folder, preferences and app folder, then reinstalled, run WD once, run the update preferences script, and it works for a few minutes then just stops updating. Likewise, it stops updating wunderground simultaneously.

I am at my wits end. I really don't want to reinstall osx since everything else I use this mini for is working just fine, nor do I want to dedicate the time to it to have it not be the problem...

I am at your mercy, and already have the ports for VNC open so I can access this machine from work, so if someone with knowledge wants to log in and fiddle, let me know.

Offline mfd38

  • Posts: 727
  • Massachusetts
    • Medfield, MA Weather
Re: Getting the wmr100/wmr200 to work
« Reply #61 on: June 09, 2009, 05:10:21 PM »
Hi there,

You do not need to be deleting that WD folder from that directory, you wipe out your settings each time you do and then you need to reconfigure it all.  There is a new installer for WD and it is quite simple. Check out this post  http://www.weather-watch.com/smf/index.php/topic,39805.msg325549.html#msg325549  you should be just fine.

Paul

Offline Weather Display

  • Posts: 65,573
Re: Getting the wmr100/wmr200 to work
« Reply #62 on: June 09, 2009, 07:57:38 PM »
what shows in the usb.txt file when it stops updating?
what happens when you run ./usbreader
from a terminal?
also try removing then re inserting the usb connection to the wmr200

Offline tivoklr

  • Posts: 12
  • Minturn, CO USA
    • wunderground archive
MMRRrrr
« Reply #63 on: June 10, 2009, 01:27:13 PM »
Well, now it's working, and has been for about 24 hours, so I am just going to leave it alone, unless of course there's a compelling reason to move from build 12 to build 13, since I seem to like to break things...

Offline Weather Display

  • Posts: 65,573
Re: Getting the wmr100/wmr200 to work
« Reply #64 on: June 10, 2009, 05:21:32 PM »
I recommend to upgrade
it should not break anything
just make sure to exit WD and quit the running usbreader program too (i.e use activity monitor, found under applications/utilities, or tye, killall usbreader from a terminal)

Offline tivoklr

  • Posts: 12
  • Minturn, CO USA
    • wunderground archive
Re: Getting the wmr100/wmr200 to work
« Reply #65 on: June 12, 2009, 04:37:05 AM »
Well, I installed build 14, but I didn't think to kill the usbreader task. Should I repeat the install following your directions? Things seem to be working right now.

Offline cyberdog

  • Posts: 5
Re: Getting the wmr100/wmr200 to work
« Reply #66 on: June 27, 2009, 05:55:19 PM »
Hi.  I've read all this post and the rest, and can't get the WMR100 to be recognised on my Mac.

I see the item in the readme to go and get a debug version of IOUSBFamily, but I can't. I've created an ADC account without problem, but trying to get the kernel extension for 10.5.7 which is listed as version 343.4.3 gives a permission denied notice:

You do not have access privileges to download the software you are requesting. If you believe you have received this message in error, you should confirm your access privileges directly with your Apple contact or view the downloads that are currently available to you.

Can someone explain why I need this debug version?  There is already a /System/Library/Extensions/IOUSBFamily.kext version 3.4.3 (size 3,777,771 bytes) in place.

When I plug in the WMR100, it is not recognised as a USB device within System Profiler and the Finder hangs after about 10 minutes, requiring a power cycle of the Mac.

So where can I get this kernel extension and why is the debug version better? And what happens when we upgrade to 10.5.8, will the USB support for the WMR100 just break?

I am REALLY WORRIED about messing around with the USB kernel support, as it seems to be about a miliimeter away from totally trashing the system.

(Running USBreader gives the USBWrite: USB device is not open message continuously)

Martin

Offline Weather Display

  • Posts: 65,573
Re: Getting the wmr100/wmr200 to work
« Reply #67 on: June 27, 2009, 07:16:19 PM »
try without the iousbfamily update
make sure to reboot with the wmr200 plugged in

Offline cyberdog

  • Posts: 5
Re: Getting the wmr100/wmr200 to work
« Reply #68 on: June 28, 2009, 12:36:14 PM »
Hi.

Using the OSX-supplied IOUSBFamily.kext (as I can't get the debug version suggested), the Console is showing these messages at 20 second intervals:

28/06/2009 14:23 : 03- 28 Jun 2009 kernel USBF: 3912.407 [0x6c6d600] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 3 of hub @ location: 0xfa210000)

That's why it is not visible to System Profiler as a valid USB device and why the usbreader program fails.

I can't get it working in Windows either - but I only have the console unit here, not the weather station itself.  But the local display is showing 28 deg and 38% humidity, and the Windows Weatherdisplay shows 13 deg and 60% humidity. All other values are 0.  Is it necessary for the console to be in range of the weatherstation for the USB port to work?

Has anyone actually downloaded, installed and got it working under OSx 10.5.7?  If so, how?

Martin

Offline Weather Display

  • Posts: 65,573
Re: Getting the wmr100/wmr200 to work
« Reply #69 on: June 28, 2009, 06:22:54 PM »
yes , others have WD for the Mac working with the wmr100

try repowering up the console too

Offline cyberdog

  • Posts: 5
Re: Getting the wmr100/wmr200 to work
« Reply #70 on: July 01, 2009, 07:32:29 AM »
After a lot more prodding and tinkering, i think I have a good handle on what's going on.

Firstly and most weirdly, the WMR100 does not act as a valid USB device unless it is in radio communication with the base station.  As I show above, it fails to enumerate under Linux and OSX, and Windows reports that it is an unknown device that has failed.

Under OSX, I got it working for a few minutes.  A file usb.txt was appearing and disappearing in the Wdisplay directory, corresponding with the WeatherD display updating.  After about 30 minutes, this stopped happening, the WeatherD display stopped updating, and usbreader could not be stopped.  It wouldn't respond to kill or kill -9 (Quit and Force Quit) but after a few minutes usbreader became a zombie process. 

Attempts to restart WeatherD lead to multiple usbreader programs, and within a couple of minutes Finder became unresponsive and the machine had to be powercycled.  i saw this behaviour previously.

So I can conclude that the usbreader side of Weather Display is not ready for production use, certainly not under OSX 10.5.7.

I left it running under Parallels and will see if that works for a few days.

Also, the WMR100 knocks out other devices on the same USB hub, so it is a Good Idea to have a dedicated hub for the WMR100 unless you don't mind your external disks and cameras just disappearing occasionally.

Windy mentioned to me in an email that you 'just had to go through some hoops'.  I have been through them all, except the one of using a debug version of IOUSBFamily kernel extension, as it is not available from Apple or elsewhere for 10.5.7.

Hope this helps others.

Offline Weather Display

  • Posts: 65,573
Re: Getting the wmr100/wmr200 to work
« Reply #71 on: July 01, 2009, 08:25:30 AM »
Quote
So I can conclude that the usbreader side of Weather Display is not ready for production use
but it does work for others
check your usb power settings

Offline cyberdog

  • Posts: 5
Re: Getting the wmr100/wmr200 to work
« Reply #72 on: July 01, 2009, 01:23:44 PM »
What are those?

The WMR100 is powered from a mains adapter.

Offline niko

  • syzygy
  • Global Moderator
  • Posts: 22,157
  • Crystal Ball broken! Please post the URL.
  • Northern California, U.S.A.
    • http://www.realweatherstation.com
Re: Getting the wmr100/wmr200 to work
« Reply #73 on: July 01, 2009, 02:15:08 PM »
Brian means on the computer side. It is quite common for power saving strategies to include powering down the USB interface which is incompatible with a realtime app like this.

Offline jmar

  • Posts: 1,405
  • Halifax, Canada
    • HRM Weather
Re: Getting the wmr100/wmr200 to work
« Reply #74 on: July 01, 2009, 04:27:57 PM »
Brian and Niko, you are spot on with taking this in the direction of power issues on the USB bus.

With something as popular as Belkin powered hubs, and HP printers, to more exotic gear like our stations, the number one USB issue on the Mac is/has been for many years, power management strategies and hardware states affecting the recognition of USB devices especially after sleep, deep sleep (hibernation) or even disk spin downs.

Google is peppered with these issues (773,000 hits with "leopard usb after sleep") and I believe it may play a role here now that we know there is a hub involved.

This has been an issue on Macs, love'em or not, since my Mac Lombard laptop was introduced with the first working USB port on a business laptop back in '99 I think. That's why I paid 4 k for it back then lol. (I digress though)

The scoop is that Apple handles power management different than Windows, even Windows running in Paralells and Fusion. I recall my Dell laptop sitting there in a meeting cooking the table because it was connected to my Treo, and just would not let go of the USB device. Connecting to the Lombard, older by then, I remember killing the batteries because I couldn't let it go to sleep or I would have to restart to remount the device.

On the desktops as USB got popular, it fast became the biggest issue with drivers and devices. On the Mac, miserly energy settings/capabilities were having huge impacts on all usb devices, and "failure to mount after sleep" variants were the biggest issue.

Hence, management of the Energy Control Panel is the most significant deterrent to this issue, especially for mission critical devices on the Mac, where a Windows system will hold onto the device, the Mac will not hesitate to let it go in favor of a user's energy settings. So in Energy Control panel, it is advisable to move the slider never sleep, as well as uncheck "allow disks to sleep..." as this has an impact on recognition of devices on the usb ports.

Also, on almost every mission critical device built for the Mac, you will see many references to advice of plugging that device directly into the Mac's built in USB ports. Although this is not as much of an issue until you have a problem, I do suggest all weather device owners follow that convention as even on my Keyspan, I can duplicate failed recognition when not plugged in directly to the Mac.

As an interesting sidebar, a Fusion or Paralells equipped Mac running Windows will not have the same issues connecting to these devices even on the same hardware, so it needs to be considered during setup... and of course those environments grabbing and not letting go of the USB ports on there host Macs are a very well known and documented issue, requiring very specific actions and vigilance from the user to prevent that from occurring. I have had that challenge in my Fusion environment specific to WD and my station although lately it seems better from both the above platforms running XP.

The last big issue I have seen over the years has to do with users that have changed ports/hubs/and other modes of connection from their device to the Mac, and not had them recognized/remounted for some time , or ever. It happened to me when I decided to go with wireless printing by connecting an Anycom 300 to my Mac via bluetooth way back when it was new technology, and connecting a USB printer to that (a Samsung Laser), now that was a day of challenges, but it is still in use here today, 5 years later lol... but back then, every thing crashed on me... numerous times.. until I got the hardware reset after changing ports so often in one day.  This is usually an issue at the hardware level where the nvram/pram/smu is just plain confused. In each of these cases unplugging all usb devices except for the one in question, and resetting the pram/smu/nvram (whichever applies to your Mac), takes care of this issue, and then reconnecting everything else in any order.

The above is of course assuming all permissions on the startup disk have been repaired and the disk verifies ok using Disk Utility.

Now I don't know if this is the answer to Cyberdog's issues or not, as a disclaimer lol, but I do know these techniques and issues have come into play on every device connection issue I have had on my Macs since the technology was introduced. I can say though, that I now almost never experience these issues with recognition/connection/mounting/remounting/sleeping of USB devices, once I followed these conventions.

Hope this helps
Jim
« Last Edit: July 02, 2009, 10:48:23 AM by jmar »
iMac, 2 x Mac Mini, Mac OS X 10.6.7, Indigo integration, Web - WDL, Saratoga templates, Lightbox