![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]() "Dan Luke" wrote in message 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? -------------------- Richard Kaplan www.flyimc.com |
#2
|
|||
|
|||
![]() "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 |
#3
|
|||
|
|||
![]() "Dan Luke" wrote in message Is that so? A WxWorx person on the phone led me to believe it is something to do with the XM system. I have certainly heard and read that if you do not use an XM receiver for 90 days then it needs to be re-activated. There is no doubt that is an "XM" issue. I have not heard of any such deactivation issue for a unit used more often than every 90 days; if that is the case, that is certainly not common to XM receivers overall. The Bluetooth situation you describe is indeed an excellent example of why a solution like the 396 is more appealing than a PDA solution. The less potential in-flight issues to diagnose the better. I love tinkering with computers but not while I am flying. -------------------- Richard Kaplan www.flyimc.com |
#4
|
|||
|
|||
![]()
In article 1121262944.2f06222670a0bc3f220fd5b432f1d014@teran ews,
"Richard Kaplan" wrote: I have not heard of any such deactivation issue for a unit used more often than every 90 days; if that is the case, that is certainly not common to XM receivers overall. Richard, It is common to the XM receivers used by WxWorx, and it is fairly well known. It doesn't matter whether you're using those receivers with a PC or PDA, or whose software you're running. I am not sure whether they've found a resolution in the newer receivers, but as I stated, I haven't had a problem with this issue. JKG |
#5
|
|||
|
|||
![]()
In article ,
"Dan Luke" wrote: 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. I haven't had any of these issues on the PDA, so it makes me wonder if the Bluetooth issues are related to WindowsXP. I know that I can't get my WindowsXP laptop to maintain a steady WiFi connection no matter what I do... it's good for a random period of time, and then it drops and resets. Have no such problem with WiFi on the iPaq or with my Apple-branded laptop. JKG |
#6
|
|||
|
|||
![]()
Jonathan Goodish wrote:
I haven't had any of these issues on the PDA, so it makes me wonder if the Bluetooth issues are related to WindowsXP. I know that I can't get my WindowsXP laptop to maintain a steady WiFi connection no matter what I do... it's good for a random period of time, and then it drops and resets. Have no such problem with WiFi on the iPaq or with my Apple-branded laptop. Its not XP, its the firmware in your device... |
#7
|
|||
|
|||
![]()
In article ,
Darrel Toepfer wrote: I haven't had any of these issues on the PDA, so it makes me wonder if the Bluetooth issues are related to WindowsXP. I know that I can't get my WindowsXP laptop to maintain a steady WiFi connection no matter what I do... it's good for a random period of time, and then it drops and resets. Have no such problem with WiFi on the iPaq or with my Apple-branded laptop. Its not XP, its the firmware in your device... Yes, I think the LInksys PC Card is the problem. JKG |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Amateur Review of the Garmin GPSMAP 296 GPS | Rhett | Piloting | 10 | March 23rd 05 01:16 AM |
Pirep: Garmin GPSMAP 296 versus 295. (very long) | Jon Woellhaf | Piloting | 12 | September 4th 04 11:55 PM |
Amateur Review of the Garmin GPSMAP 296 GPS | Rhett | Products | 10 | April 29th 04 06:57 AM |
Garmin DME arc weidnress | Dave Touretzky | Instrument Flight Rules | 5 | October 2nd 03 02:04 AM |
Garmin 90 Database Updates Discontinued | Val Christian | Piloting | 14 | August 20th 03 09:32 PM |