"Richard Kaplan" wrote:

I believe this is an XM, rather than WxWorx issue.

Yes, that is disconcerting. But how can it be an XM issue if it only
happens with certain brands of hardware?

Is that so? A WxWorx person on the phone led me to believe it is
something to do with the XM system.

I do not understand the technical issues. I'll call WxWorx again and
see if I can get more details.

BTW, re. Bluetooth issues: I just got my WxWorx receiver back from being
converted. I spent a couple hours setting the system up, including a
Holux 230 Bluetooth GPS. WxWorx kindly includes a 120v power supply
with the conversion so this can all be done at home. That was a good
thing, as it took considerable fiddling to get everything to work,
although I never had to resort to calling WxWorx.

Everything seemed to be working fine at last, but I failed to make a
critical test before I put it all in the airplane: I did not do a cold
start of the whole system. Upon starting everything up in the airplane,
I found that WxWorx could not communicate with the GPS. Nothing I tried
worked until I deleted the GPS from Bluetooth devices in the Windows
Control Panel and added it back again. Then, everything worked fine
until I cold started again, whereupon WxWorx again could not find the
GPS.

*sigh* That will be the other thing I'll be talking to WxWorx about
today.

--
Dan
C172RG at BFM