Getting the wmr100/wmr200 to work

[Weather Display]

first, see the topic on setting the permissions (and of course you have run the install.sh from a terminal window (see the readme.txt included with the WD install), and also make sure you have at least version 10.37h build 03
next, make sure you have downloaded and installed the IOUSBdriver update for your Mac OSX version
http://developer.apple.com/hardwaredrivers/download/usbdebug.html

and then restart the PC

then try running WD (double click the WeatheD icon)

there should then be a usb.txt file created (and then read and deleted by WD)

if not, try running the usbreader program from a terminal window (find the terminal program under applications, utilities, then type cd /../ then hit enter, then type cd applications then hit enter, then type cd wdisplay then hit enter, then type ./usbreader then hit enter)
if an access violation error,then restart OSX then try running the usbreader from a terminal program or run WD,again

also note that sometimes the wmr100 console needs resetting

also note that I still need to add in support for the history missed data from the wmr200 (now that I have that working correct in the windows version) (i.e you will need to wait for that data to all come through before the live data starts)

[berthouz]

Brian,
I've tried these instructions (including those in your permissions posting).
This is what I get when I type ./usbreader

10-5-image-rn-3:wdisplay lb203$ ./usbreader
An unhandled exception occurred at $00000000 :
EAccessViolation : Access violation
  $00000000

I've rebooted the Mac, unplugged the USB cable after it had restarted, waited a minute, replugged and started WD and I still get nothing. I have also reset the console (with the USB cable plugged in). usbreader still shows the above.
Any hint? Thanks, -luc

[Weather Display]

I have had that error myself, but that is fixed by rebooting OSX
(try that but then do not unplug the usb cable)

the USB on a mac is not easy stuff (not my fault, a problem with the OS grabbing the USB device exlusively)

[berthouz]

Hi Brian,
It worked after shutting down and restarting with the cable plugged in.
Very pleased about that... Thanks for the help! -luc

[paragoat]

Great post Windy.  I am now sucessful in downloading data from my WMR200! Everything is working great!  Just need to tweak the offsets. 

Thanks, John

[Weather Display]

thats good news, 2 of you up and running
I will work on getting the missed history data working too now

[Francis]

I've tried all of the above suggestions and I think the WMR100 is now working with WeatherD.  I set the permissions correctly, ran install.sh, installed iousbfamily, and installed wdlibraryinstall.  My WMR100 was still not recognized.  Then I read the posts in this forum and tried the following: I plugged the USB cable from the WMR100 directly into my laptop (NOT into my USB hub) and did a cold reboot (shut down the computer and then power up).  A restart did not work.  The WMR100 is  now sending data to WeatherD!

[Francis]

WeatherD doesn't show the same current temperature on the WMR100.  It seems to lag behind approximately 10 minutes.  Can anyone explain why?

[Weather Display]

its possible that the temperature data is coming through jumbled with other data (i.e not on its own data line)

[Francis]

OK, now that I have the WMR100 capturing data on my Mac, how do I make the window of WeatherD larger?  I can barely read the legends on the graphs.  Is there a way to make the window larger?  I cannot find it. 

[Weather Display]

no,sorry
but you can change alot of the font sizes

[Brightwood93]

This was my 6th attempt at getting my WMR100A running.  I posted in the past and had no real luck with getting any communication going.

I have:
Set Permissions
Installed libraries
ReBooted system and powered off
Reset my wmr100a
connected directly to my iMac
installed via terminal
installed usb driver from mac

The program runs, the usb data file is created and then deleted on opening of program.

What communications port should be set in the settings, I only show the bluetooth devices.

[Weather Display]

did you download and install the needed IOUsbfamily driver update?
then reboot the Mac
also though the wmr100 has a hardware fault, where it stops sending data, and needs to be reset sometimes
also try runnning the separate usbreader in a terminal window to see what messages are displayed there

it does work, but takes a bit of kicking (all apples fault because of the way the OS grabs a HID device!!)

[NorCal Dan]

Along with what Brian said I will add some insight and hope it helps...

After you install the IOUsbfamily drivers and before you reboot your computer, remove power and batteries from the wmr100 console. Then shutdown/power off the iMac.  After a minute or so turn the iMac back on and allow it to boot up.  Then reapply power and reinstall batteries in the wmr100 console.  Do not run WD for 15 minutes.  That's how long it takes the wmr100 console to set itself up.  (I discovered this 15 minute delay because I was setting an altitude on the console and noticed the barometer did not "adjust" to the corrected reading for 15 minutes).  After 15 minutes you can launch WD and it should start grabbing data. 

If WD does not begin grabbing data there are a couple things you can try.

1. In WD under the view menu is a button to view the ftplog.  Click it and it will open the log viewer window.  Click the close button and it will then open 2 more windows, one is for mySql (it says something about mySql is all I remember), and the other window shows some columns and had a start button.  Try clicking the start button and usually that will get the data flowing. 

2. If #1 fails, then I usually open a terminal window and see how many usbreader programs are running by doing a ps -eaf |grep -i usb.  There should be only 1 usbreader running.  If there is more than one I usually kill them all, then try #1 again.

If all this fails to get it working I start back at the top and reboot, remove power, etc.

The only other things I did on my system was grant 777 permissions to the usbreader program, the wdisplay install directory and sub directories.  Be sure the datafiles directory is 777 as well as any other directories that WD needs to write data into.

Like Brian says, the Mac USB stuff is a pain to get going...but I have found that the above steps work.  Please let us know how you get along...

[Brightwood93]

Along with what Brian said I will add some insight and hope it helps...

After you install the IOUsbfamily drivers and before you reboot your computer, remove power and batteries from the wmr100 console. Then shutdown/power off the iMac.

Thanks for all the suggestions.

I have installed the ISOUSBfamily as above. Tried this, no data.

1. In WD under the view menu is a button to view the ftplog.  Click it and it will open the log viewer window.  Click the close button and it will then open 2 more windows, one is for mySql (it says something about mySql is all I remember), and the other window shows some columns and had a start button.  Try clicking the start button and usually that will get the data flowing. 

The window that mentions MySQL has the start button. Nothing happened when that was clicked.

2. If #1 fails, then I usually open a terminal window and see how many usbreader programs are running by doing a ps -eaf |grep -i usb.  There should be only 1 usbreader running.  If there is more than one I usually kill them all, then try #1 again.

Launching usbreader separately in Terminal gives an access violation. GREP shows one running process if WD is running.

If all this fails to get it working I start back at the top and reboot, remove power, etc.

Done. No change.

The only other things I did on my system was grant 777 permissions to the usbreader program, the wdisplay install directory and sub directories.  Be sure the datafiles directory is 777 as well as any other directories that WD needs to write data into.

Done. No dice.

When WD is launched it throws a ton of messages to Console, along the lines of this (only a small portion copied). Any clues here?

6/16/08 7:29:18 PM [0x0-0x36036].WeatherD[903] TCarbonWidgetSet.GetClipBo
6/16/08 7:29:18 PM [0x0-0x36036].WeatherD[903] x Error - invalid DC  = 0!
6/16/08 7:29:18 PM [0x0-0x36036].WeatherD[903] TCarbonWidgetSet.StretchMaskBlt Error - invalid source device context TCarbonControlContext, expected TCarbonBitmapContext!
6/16/08 7:29:18 PM [0x0-0x36036].WeatherD[903] TCarbonWidgetSet.GetClipBox Error - invalid DC  = 0!
6/16/08 7:29:18 PM [0x0-0x36036].WeatherD[903] TCarbonWidgetSet.StretchMaskBlt Error - invalid sour
6/16/08 7:29:18 PM [0x0-0x36036].WeatherD[903] ce device context TCarbonControlContext, expected TCarbonBitmapContext!
6/16/08 7:29:18 PM [0x0-0x36036].WeatherD[903] FindCarbonFontID Error: ATSUFindFontFromName  failed with result -8796
6/16/08 7:29:18 PM [0x0-0x36036].WeatherD[903] FindCarbonFontID Error: ATSUFindFontFromName  failed with result -8796
6/16/08 7:29:18 PM [0x0-0x36036].WeatherD[903] FindCarbonFontID Error: ATSUFindFontFromNa
6/16/08 7:29:18 PM [0x0-0x36036].WeatherD[903] An unhandled exception occurred at $00000000 :
6/16/08 7:29:18 PM [0x0-0x36036].WeatherD[903] EAccessViolation : Access violation
6/16/08 7:29:18 PM [0x0-0x36036].WeatherD[903]   $00000000
6/16/08 7:29:36 PM [0x0-0x36036].WeatherD[903] me  failed with result -8796
6/16/08 7:29:36 PM [0x0-0x36036].WeatherD[903] FindCarbonFontID Error: ATSUFindFontFromName  failed with result -8796
6/16/08 7:29:36 PM [0x0-0x36036].WeatherD[903] FindCarbonFontID Error: ATSUFindFontFromName  failed with result -8796
6/16/08 7:29:36 PM [0x0-0x36036].WeatherD[903] CarbonWindow_ActivateProc MainForm:TMainForm
6/16/08 7:29:36 PM [0x0-0x36036].WeatherD[903] CarbonWindow_ActivateProc MainForm:TMain
6/16/08 7:29:36 PM [0x0-0x36036].WeatherD[903] Form
6/16/08 7:29:36 PM [0x0-0x36036].WeatherD[903] TCarbonWidgetSet.GetClipBox Error - invalid DC  = 0!
6/16/08 7:29:36 PM [0x0-0x36036].WeatherD[903] TCarbonWidgetSet.StretchMaskBlt Error - invalid source device context TCarbonControlContext, expected TCarbonBitmapContext!