WinPilot and Bluetooth on iPAQ 3970 anyone?

Hi,

Actually, Im trying to run WinPilot VFR but I guess the gps software will
be much the same..... and as a sometime soaring pilot I hope I'll be
excused for posting the question here.

Anyway, Winpilot refuses to "see" my socket / emtac bluetooth gps. Which
seems a little strange. My in-car Navigation software (TomTom) is just fine
and so is a product called "efis" (a less accomplished type of WinPilot).
However neither of these products will see the GPS after an attempt to run
WinPilot has been made. After a reset these products work just fine again.

Jerry at WinPilot did mention that it might be a little flakey. (He didn't
say it wouldn't work at all).

Any ideas?

Thanks,

Alan

"Al" wrote in message
...
| Anyway, Winpilot refuses to "see" my socket / emtac bluetooth gps.
Which
| seems a little strange. My in-car Navigation software (TomTom) is
just fine
| and so is a product called "efis" (a less accomplished type of
WinPilot).
| However neither of these products will see the GPS after an attempt
to run
| WinPilot has been made. After a reset these products work just fine
again.
|
| Jerry at WinPilot did mention that it might be a little flakey. (He
didn't
| say it wouldn't work at all).

Very good question. All of the new iPaqs that suit WinPilot (H5550 =
H5555, H5150 = H5155) have BlueTooth (as do the smaller H2215 and
H1940 models) so it makes sense to consider Bluetooth's use. The
Bluetooth GPS units are tiny, can be placed where they see the
satellites best (and out of our vision) and come with 12v adapters as
a rule. Their rechargable batteries last at least six hours apparently
(thinking of outlanding issues here) . . not sure if the 12v adaptor
*charges* them or not, probably does.

Very clever automotive voice guiding street navigation systems offer
an attractive adjunct to a Pocket-PC/GPS/WinPilot system. TravRoute's
Co-Pilot, and NavMan 4400 are both readily available with Bluetooth
GPS units.

But I'd be nervous about flying with something that is 'a bit flakey'.
Hopefully Jerry was referring to the model H5450 which is a bit flakey
by some accounts?

Also, the new iPaqs have Windows 2003, any news of this being readied
for WinPilot yet? (There are no current iPaq models listed on their
Compatible Hardware page . . the H39xx models are no longer available
in our part of the world).

Cheers,

Jim Kelly (waiting for my new H5550 8-) )

"Jim Kelly" wrote in message
u...
But I'd be nervous about flying with something that is 'a bit flakey'.
Hopefully Jerry was referring to the model H5450 which is a bit flakey
by some accounts?

Cheers,

Jim Kelly (waiting for my new H5550 8-) )


I'm using the H5450 with Winpilot. No flakes yet . . . but then I'm not
using the bluetooth feature. No need, as the PDA slips into a TEKK mount and
gets GPS info and 5 volt power from a 302.

What's this about a H5550? So how come I was assured, when I bought the
5450, that it was the "be all end all" and would not become obsolete in a
just a few months (g).
--
bumper
"Dare to be different . . . circle in sink."
to reply, the last half is right to left



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.501 / Virus Database: 299 - Release Date: 7/15/2003

Bumper,

HP doesn't know yet that only you can climb in sink.

Richard
www.craggyaero.com



"John Morgan" wrote in message
...

"Jim Kelly" wrote in message
u...
But I'd be nervous about flying with something that is 'a bit flakey'.
Hopefully Jerry was referring to the model H5450 which is a bit flakey
by some accounts?

Cheers,

Jim Kelly (waiting for my new H5550 8-) )


I'm using the H5450 with Winpilot. No flakes yet . . . but then I'm not
using the bluetooth feature. No need, as the PDA slips into a TEKK mount
and
gets GPS info and 5 volt power from a 302.

What's this about a H5550? So how come I was assured, when I bought the
5450, that it was the "be all end all" and would not become obsolete in a
just a few months (g).
--
bumper
"Dare to be different . . . circle in sink."
to reply, the last half is right to left



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.501 / Virus Database: 299 - Release Date: 7/15/2003

Al wrote in message .. .
Hi,

Actually, Im trying to run WinPilot VFR but I guess the gps software will
be much the same..... and as a sometime soaring pilot I hope I'll be
excused for posting the question here.

Anyway, Winpilot refuses to "see" my socket / emtac bluetooth gps. Which
seems a little strange. My in-car Navigation software (TomTom) is just fine
and so is a product called "efis" (a less accomplished type of WinPilot).
However neither of these products will see the GPS after an attempt to run
WinPilot has been made. After a reset these products work just fine again.

Jerry at WinPilot did mention that it might be a little flakey. (He didn't
say it wouldn't work at all).

Any ideas?

Thanks,

Alan

Hi Alan,
It sounds to me like this problem is caused by a COM port issue. When
you run Winpilot, it "hogs" the wireless COM prot. Try resetting the
unit and running WinPilot First.

Also, you don't need to reset the unit. Goto Settings - Memory and
click "Stop all running programs" This is 90% of what a reset does.

Kevin

Anyone who believes computer sales staff also clearly still believes in
the tooth fairy. ;-]

If it is on the shelf it is already obsolete...

John Morgan wrote:
"Jim Kelly" wrote in message
u...

But I'd be nervous about flying with something that is 'a bit flakey'.
Hopefully Jerry was referring to the model H5450 which is a bit flakey
by some accounts?

Cheers,

Jim Kelly (waiting for my new H5550 8-) )



I'm using the H5450 with Winpilot. No flakes yet . . . but then I'm not
using the bluetooth feature. No need, as the PDA slips into a TEKK mount and
gets GPS info and 5 volt power from a 302.

What's this about a H5550? So how come I was assured, when I bought the
5450, that it was the "be all end all" and would not become obsolete in a
just a few months (g).

(Kevin Christner) wrote in
om:

It sounds to me like this problem is caused by a COM port issue. When
you run Winpilot, it "hogs" the wireless COM prot. Try resetting the
unit and running WinPilot First.

Also, you don't need to reset the unit. Goto Settings - Memory and
click "Stop all running programs" This is 90% of what a reset does.

Kevin

Hi Kevin,

Even with soft resets it doesn't work more than about one time in twenty.

GPS on first.... wait for it to aquire..... Reset PDA.... Select WinPilot
VFR... Loads, loads maps, then "Waiting for GPS...".

WinPilot is set for Com 8 (same as TomTom). I've tried all of the Baud
rates up to 38400.

I'd then need to soft-reset before TomTom would work. Killing all active
programs isn't enough.

I'm not sure that I care what hoops I have to jump thru to get it to work,
so long as its consistent, but right now its not possible to take my PDA
and GPS flying.

Thanks for your input though.

Alan

"Al" wrote in message
...
(Kevin Christner) wrote in
om:

It sounds to me like this problem is caused by a COM port issue. When
you run Winpilot, it "hogs" the wireless COM prot. Try resetting the
unit and running WinPilot First.

Also, you don't need to reset the unit. Goto Settings - Memory and
click "Stop all running programs" This is 90% of what a reset does.

Kevin

Hi Kevin,

Even with soft resets it doesn't work more than about one time in twenty.

GPS on first.... wait for it to aquire..... Reset PDA.... Select WinPilot
VFR... Loads, loads maps, then "Waiting for GPS...".

WinPilot is set for Com 8 (same as TomTom). I've tried all of the Baud
rates up to 38400.

I'd then need to soft-reset before TomTom would work. Killing all active
programs isn't enough.

I'm not sure that I care what hoops I have to jump thru to get it to work,
so long as its consistent, but right now its not possible to take my PDA
and GPS flying.

Thanks for your input though.

Alan

From what I've seen so far, Bluetooth enabled devices create interesting
issues. For example, one of our 'gadget' folks in my local computer users
group gave a Bluetooth demo at the last meeting using a Bluetooth enabled
cell phone, headset, and PDA.

The cell phone and headset must be placed on the same side of the body (he
prefers left), since the signal is blocked by body mass. The signal to the
headset is also more reliable if the cell phone is oriented horizontally,
rather than vertically, at the beltline, so he bought a special case for
this. The best placement of the phone in the case, for quick and easy
access, is with the keypad toward the inside. But if inserted this way, the
magnetic clasp on the case causes the phone to shut off intermittently.
With the keypad placed outwards the phone is okay, but when he picks up the
phone and must rotate 180degs for use, which he considers an awkward
movement. Placement of the PDA in relation to the phone is similarly
important, but since he writes left-handed, it works most of the time.

Personally I find the blue flashes very annoying, like walking through
K-Mart. I was working with a Bluetooth enabled laptop the other day at a
clinic. They own twelve, are not using the Bluetooth feature, but haven't
disabled it on any of them. I can't believe the nurses enjoy that
distracting flash every few seconds at the top of the display and it must
make them really productive.

Now that a Bluetooth 'standard' has been settled upon, I'm sure I'm about to
be annoyed just about everywhere.

Frank Whiteley