Windows Mobile 6.5 Bluetooth Problem

[ssk]

I have a PDA application that has been used on many versions of Windows mobile from 5 - 6.1. A customer recently contacted us to say that the application was not working on a new Windows Mobile 6.5 smartphone.

I have just purchased a WM6.5 phone and is does not work on the one that I have purchased (HTC Touch 2). It works fine on a WM6.1 HTC Touch 3G.

The software is able to perform a 'Discover' function but it will not connect to the BT device.

Has anybody else had experience with WM6.5 and BT?

Thanks in advance.

[Jas.W]

Hi ssk, 

Windows Mobile 6.5 isn't officially supported by our Mobile Module. Whilst some features may work, we cannot guarantee that they will. 

I think the best thing here is to open it to the floor, so to speak, and if member of the community have had experience with using Windows Mobile 6.5 and the Mobile Module then please feel free to share in this thread. 

Here is a link to a list of supported Mobile devices with our Mobile Module. 

http://digital.ni.com/public.nsf/allkb/7D65D66EB07111F186256EBD005A5499

Kind Regards, 

[ssk]

Hi Jason,

Would you be able to advise when the Mobile Module will support Windows Mobile 6.5?

This is becoming a real problem for me now. Windows Mobile 6.0 (or 6.1) devices are becoming very difficult to source and customers are struggling to find smartphones that will run the software we offer to them.

It appears as if most of our application (written in LV2010), works on WM6.5 apart from the 'Bluetooth Open Connection' function.

When it gets to the Bluetooth Open Connection (see below) the function outputs an Error code 6.

Thanks

[VlaPet]

Did somebody found solution of the problem with WM6.5 and BT communication support? Every application, not only LV have same problem.It is issue of the Microsoft, because of the non possibility to open and share Vistual Com Port which was possible in the system before. The window ComPorts is free without row support for the assignment of the COM PORT NUMBER. Who will have better answer from the support of the mobile tan me from the ASUS? Ther support is no able to solve it. Thanks for sharing info to all. VlaPET

[ssk]

National Instruments are currently trying to resolve this issue.

[VlaPet]

I found It on the internet. Providers of the WM6 distributions have no explicitly done the next in the registry.

It is good to install CeRegEditor and by this fill new rows.

[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\serial]

[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\serial\Ports]
"SupportedPorts"=hex(7):43,4F,4D,30,00,43,4F,4D,31,00,43,4F,4D,32,00,43,4F,4D,33,00,43,4F,4D,34,00,43,4F,4D,35,00,43,4F,4D,36,00,43,4F,4D,37,00,43,4F,4D,38,00,43,4F,4D,39,00,00

[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\serial\Ports\Incoming]
"Port"="COM6"
"Server"=dword:00000001
"Authentication"=dword:00000001
"Encryption"=dword:00000001
"KeepDCD"=dword:00000000
"RemoteDCB"=dword:00000000

The Key <SupportedPorts> is multi_string, then instead of the HEX values you can see now above you can write stringsmultivalue

COM0

COM1

COM2

COM3

COM4

COM5

COM6

COM7

COM8

COM9

Or I can send you serial.rgu file to direct import to the mobile by sw CeRegEditor.

[Peter7777]

I was wondering if you could send me the serial.rgu file, as I am having problems entering the lines that you have shown on the site. I would greatly apreciate your help as I need a serial port on my HTC HD2 for a portable printer. 

                            Thanks, Peter