WM 5.0 + GPS

[Hilton]

Hi,

Using the OpenNETCF libraries: I connected successfully using my Dell Axim
(2003 SE). Then I upgraded the X50 to WM 5.0 and I cannot connect. The
Axim kept asking me for a passkey - after much searching on the web I
discovered that "2003" works. OK, now my Axim and my cell phone can see my
BT receiver (Dell NAVTEQ), but I cannot get anything working with C#.

Is there a problem with WM 5.0? Am I missing something? Any diagnostics
out there? I'll start digging around the code tomorrow, but any ideas why
it is now broken?

Thanks,

Hilton

 

[Graham McKechnie]

Hilton,

Have you tried the serialport class from VS2005 - my GPS stuff works with
that on WM 5 devices.

Graham

 

[Ilya Tumanov [MS]]

WM 5.0 has native GPS support. It connects to GPS receiver to expose GPS to
any number of applications via API.

That would block direct connections to GPS since port is in use.

You can either use this API or disable WM 5.0 GPS support to free up the
port.


--
Best regards,

Ilya

This posting is provided "AS IS" with no warranties, and confers no rights.

*** Want to find answers instantly? Here's how... ***

1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).

 

[Hilton]

Graham, Ilya,

Thank you for the responses. It took me about 4 hours of tweaking to get it
working, and it works great now, but I think this is going to be a nightmare
for users; i.e. setting ports etc. With Bluetooth, it would be really cool
if you could write (psuedo) code like:

IList deviceList = Bluetooth.FindDevices ();

if (no devices) - MessageBox.Show ("You have no devices");
if (one device) - use it; i.e. Bluetooth.UseDevice (deviceList [0] as
BluetoothDevice);
if (more than one device) - show listbox, get user to pick which one.

This whole archaic serial port thing seems like a messy throwback to a
protocol that essentially went out years ago. Why is it not so easy and why
does the user have to manually try ports 1, 2, 3, 4, ,...8?

Thanks,

Hilton

 

[Graham McKechnie]

Hilton,

Have you tried SerialPort.GetPortNames()?. That finds Bluetooth ports on PC
2003 devices. Haven't tried with WM5.


Graham

Graham, Ilya,

Thank you for the responses. It took me about 4 hours of tweaking to get
it working, and it works great now, but I think this is going to be a
nightmare for users; i.e. setting ports etc. With Bluetooth, it would be
really cool if you could write (psuedo) code like:

IList deviceList = Bluetooth.FindDevices ();

if (no devices) - MessageBox.Show ("You have no devices");
if (one device) - use it; i.e. Bluetooth.UseDevice (deviceList [0] as
BluetoothDevice);
if (more than one device) - show listbox, get user to pick which one.

This whole archaic serial port thing seems like a messy throwback to a
protocol that essentially went out years ago. Why is it not so easy and
why does the user have to manually try ports 1, 2, 3, 4, ,...8?

Thanks,

Hilton

WM 5.0 has native GPS support. It connects to GPS receiver to expose GPS
to any number of applications via API.

That would block direct connections to GPS since port is in use.

You can either use this API or disable WM 5.0 GPS support to free up the
port.


--
Best regards,

Ilya

This posting is provided "AS IS" with no warranties, and confers no
rights.

*** Want to find answers instantly? Here's how... ***

1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).

 

[Hilton]

Have you tried SerialPort.GetPortNames()?. That finds Bluetooth ports on
PC 2003 devices. Haven't tried with WM5.

No since I don't want to limit my users to CF 2.0. Right now I'm using the
OpenNETCF DLLs, but having to work around the code a bunch for the GPS stuff
to work as I require. I'll try put something together for the OpenNETCF
team on how to improve the GPS code *in my opinion* and email it to them.

I write the code to work on Pocket PC 2002 running pre-2.0 CF with no
Service Packs etc. It's just too complicated to force people to upgrade and
add another 2M onto their system requirements.

Thank for the pointers though.

Hilton

Graham, Ilya,

Thank you for the responses. It took me about 4 hours of tweaking to get
it working, and it works great now, but I think this is going to be a
nightmare for users; i.e. setting ports etc. With Bluetooth, it would be
really cool if you could write (psuedo) code like:

IList deviceList = Bluetooth.FindDevices ();

if (no devices) - MessageBox.Show ("You have no devices");
if (one device) - use it; i.e. Bluetooth.UseDevice (deviceList [0] as
BluetoothDevice);
if (more than one device) - show listbox, get user to pick which one.

This whole archaic serial port thing seems like a messy throwback to a
protocol that essentially went out years ago. Why is it not so easy and
why does the user have to manually try ports 1, 2, 3, 4, ,...8?

Thanks,

Hilton

WM 5.0 has native GPS support. It connects to GPS receiver to expose GPS
to any number of applications via API.

That would block direct connections to GPS since port is in use.

You can either use this API or disable WM 5.0 GPS support to free up the
port.


--
Best regards,

Ilya

This posting is provided "AS IS" with no warranties, and confers no
rights.

*** Want to find answers instantly? Here's how... ***

1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).

Hi,

Using the OpenNETCF libraries: I connected successfully using my Dell
Axim (2003 SE). Then I upgraded the X50 to WM 5.0 and I cannot
connect. The Axim kept asking me for a passkey - after much searching
on the web I discovered that "2003" works. OK, now my Axim and my cell
phone can see my BT receiver (Dell NAVTEQ), but I cannot get anything
working with C#.

Is there a problem with WM 5.0? Am I missing something? Any
diagnostics out there? I'll start digging around the code tomorrow,
but any ideas why it is now broken?

Thanks,

Hilton