.NET Components for Mobility

No supported Bluetooth protocol stack found

Last post 09-09-2010 3:35 AM by isabel fernandez. 22 replies.
Page 1 of 2 (23 items) 1 2 Next >
Sort Posts: Previous Next
  • 09-08-2010 2:54 AM

    No supported Bluetooth protocol stack found

    Hi,

    I am not able to initialize a Bluetooth adapter with Widcom stack. When I debug the project I get the following error ""No supported Bluetooth protocol stack found". So I guess it looks for the Windows stack.

    I read through some posts and I followed some of the advices.I already have copied the InTheHand.Net.Personal.dll and the 32feetWidcomm.dll in the same folder where the .exe is.  There it fails where I declare a BluetoothClient object (bt2 = new BluetoothClient; where BluetoothClient is a InTheHand.Net.Sockets.BluetoothClient). I don't know if there is any WidcomBluetooth client or if I should use another type of object. Is there any other way to initialize it, since I think that nowardays you alreday support Widcom stack.

    Thank you in advance.

    Regards,

    Isabel Fernandez.

  • 09-08-2010 7:32 AM In reply to

    Re: No supported Bluetooth protocol stack found

    There's lots of discussion of the requirements for Widcomm on Win32 in the user guide and the widcomm doc in the release, have a read through them.

    Do two things for me.  Firstly put the Test32feetWidcommWin32.exe file in the same folder as your app (and where the 32feetWidcomm.dll file is), run it, what does it report?  Do you perhaps need to install the VisualC++ libraries.  See the widcomm doc for more info.

    Secondly use the .exe.config file include in the release copy it to the app's folder, rename it to match the exe and run your app under the debugger.  Do you see any related output in the output Window?  (or if its a console app on the console, or configure a TraceListener http://msdn.microsoft.com/en-us/library/sk36c28t.aspx).

  • 09-09-2010 3:35 AM In reply to

    Re: No supported Bluetooth protocol stack found

      v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} 1024x768 Normal 0 false 21 false false false CA X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Tabla normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

    Hi,

    Thanks a lot for your quick answer.

    I followed the instructions you gave me.

    >Do two things for me.  Firstly put the Test32feetWidcommWin32.exe file in the same folder as your app (and where >the 32feetWidcomm.dll file is), run it, what does it report?  Do you perhaps need to install the VisualC++ >libraries.  See the widcomm doc for more info.

    After running the app I obtained the following report:

    32feet.NET using Widcomm stack dependency checker tool.
    We will attempt to load and use the 32feetWidcomm support. Did find 32feetWidcomm.dll file. :-)
    Did find 32feetWidcomm.dll DLL. :-)
    DLL found at >>C:\Users\isabel\PROJECTS\TELEREHAB\B_NET\Test_NEW\Debug\32feetWidcomm.dll<<
    Calling init function...
       Success
    Calling radio address function...
       Success, local address is 00-80-5a-40-4c-b7
    Hit Return to continue>

    Then it recognizes the radio. Big Smile

    >Secondly use the .exe.config file include in the release copy it to the app's folder, rename it to match the exe and >run your app under the debugger.  Do you see any related output in the output Window?  (or if its a console app on >the console, or configure a TraceListener http://msdn.microsoft.com/en-us/library/sk36c28t.aspx).

    I copied de app.exe.config into the folder, I renamed it and now it seems the problem is solved. Now I get a new error:Connection failed: ConnectionRefused (10061); PortLookup_NonRfcomm.” What does this error mean?

    Thanks again for your help!

    Regards,

     

     

    Isabel Fernández

     

    R+D Area

    ifernandez@cetemmsa.com

  • 09-09-2010 3:41 AM In reply to

    Re: No supported Bluetooth protocol stack found

    Hi,

    Thanks a lot for your quick answer.

    I followed the instructions you gave me.

    >Do two things for me.  Firstly put the Test32feetWidcommWin32.exe file in the same folder as your app (and where >the 32feetWidcomm.dll file is), run it, what does it report?  Do you perhaps need to install the VisualC++ >libraries.  See the widcomm doc for more info.

    After running the app I obtained the following report:
    32feet.NET using Widcomm stack dependency checker tool.
    We will attempt to load and use the 32feetWidcomm support. Did find 32feetWidcomm.dll file. :-)
    Did find 32feetWidcomm.dll DLL. :-)
    DLL found at >>C:\Users\isabel\PROJECTS\TELEREHAB\B_NET\Test_new\Debug\32feetWidcomm.dll<<
    Calling init function...
       Success
    Calling radio address function...
       Success, local address is 00-80-5a-40-c4-b7
    Hit Return to continue>

    Then it recognizes the radio. :-)

    >Secondly use the .exe.config file include in the release copy it to the app's folder, rename it to match the exe and >run your app under the debugger.  Do you see any related output in the output Window?  (or if its a console app on >the console, or configure a TraceListener http://msdn.microsoft.com/en-us/library/sk36c28t.aspx).

    I copied de app.exe.config into the folder, I renamed it and now it seems the problem is solved. Now I get a new error: “Connection failed: ConnectionRefused (10061); PortLookup_NonRfcomm.” What does this error mean?

    Thanks again for your help!

    Regards,
  • 09-09-2010 10:31 AM In reply to

    Re: No supported Bluetooth protocol stack found

    Yippee!

    On the error:

     PortLookup_NoneRfcomm:    None of the records are for an RFCOMM service.

    What service are you trying to connect to?  Maybe its one that uses L2CAP rather than RFCOMM.  Have a look at the list at http://www.alanjmcf.me.uk/comms/bluetooth/Bluetooth%20Profiles%20and%2032feet.NET.html

  • 09-09-2010 11:58 AM In reply to

    Re: No supported Bluetooth protocol stack found

     Hi again,

    So, you mean the service I am trying to connect is not available in the remote device?  I am trying to conenct the SeriaPort service and looking at the available services it is listed (from your list, it is in-box profile in Windows, so no L2CAP).

    Any clue?

    Thanks again for your help!

    Regards,

     

    Isabel.

     

     

  • 09-09-2010 5:39 PM In reply to

    Re: No supported Bluetooth protocol stack found

    Hmm, yup that should work.  Bah, problems never end... :-,(

    What's the type of the remote device?

    Can you run the SdpBrowserDesktop sample -- compile it and put it in the same folder as your app. Discover your device, select it, select SerialPort on the Client tab, and back on the SDP tab hit menu option SDP->SelectedServiceClass and copy the resulting text out of the window and paste it here.

    (Or add code like the following to a console app etc

        BluetoothAddress addr = ... ... ...
        //
        var dev = new BluetoothDeviceInfo(addr);
        var records = dev.GetServiceRecords(BluetoothService.SerialPort);
        foreach (var cur in records) {
          Console.WriteLine("*");
          ServiceRecordUtilities.Dump(Console.Out, cur);
          Console.WriteLine();
        }//for
    )

  • 09-10-2010 3:43 AM In reply to

    Re: No supported Bluetooth protocol stack found

    Good Morning Alan,

    I followed your instructions and here are the reports:

    This is the list of devices. The one I'm using is the one named Belkin and the one I want to connect to is named USER-PC:

     Discovery process started at 09/10/2010 07:23:32 UTC, 09/10/2010 09:23:32 local, and ended at 09/10/2010 07:23:42 UTC.

    * Blue_Test
    Address: 000319064243
    Remembered: False, Authenticated: False, Connected: False
    LastSeen: 09/10/2010 07:23:42, LastUsed: 01/01/0001 00:00:00
    CoD: (0x000000)
     Device:  Miscellaneous (0x00) / Miscellaneous (0x0000)
     Service: None (0x00)

    * Miquel
    Address: 000E6DC22717
    Remembered: False, Authenticated: False, Connected: False
    LastSeen: 09/10/2010 07:23:42, LastUsed: 01/01/0001 00:00:00
    CoD: (0x500204)
     Device:  Phone (0x200) / CellPhone (0x0204)
     Service: ObjectTransfer, Telephony (0x280)

    * USER-PC
    Address: 00190E063914
    Remembered: True, Authenticated: True, Connected: False
    LastSeen: 09/10/2010 07:23:42, LastUsed: 09/07/2010 06:52:58
    CoD: (0x7E010C)
     Device:  Computer (0x100) / LaptopComputer (0x010C)
     Service: Network, Rendering, Capturing, ObjectTransfer, Audio, Telephony (0x3F0)

    * CRISTINA-GONZAL
    Address: 001986003039
    Remembered: False, Authenticated: False, Connected: False
    LastSeen: 09/10/2010 07:23:42, LastUsed: 01/01/0001 00:00:00
    CoD: (0x3E0104)
     Device:  Computer (0x100) / DesktopComputer (0x0104)
     Service: Network, Rendering, Capturing, ObjectTransfer, Audio (0x1F0)

    * HTC_Touch2
    Address: 002376E94101
    Remembered: False, Authenticated: False, Connected: False
    LastSeen: 09/10/2010 07:23:42, LastUsed: 01/01/0001 00:00:00
    CoD: (0x7A020C)
     Device:  Phone (0x200) / SmartPhone (0x020C)
     Service: Network, Capturing, ObjectTransfer, Audio, Telephony (0x3D0)

    * Belkin
    Address: 00805A40C4B7
    Remembered: False, Authenticated: False, Connected: False
    LastSeen: 09/10/2010 07:23:42, LastUsed: 09/10/2010 07:15:48
    CoD: (0x3E0104)
     Device:  Computer (0x100) / DesktopComputer (0x0104)
     Service: Network, Rendering, Capturing, ObjectTransfer, Audio (0x1F0)

    * 20:D6:07:9E:87:2E
    Address: 20D6079E872E
    Remembered: False, Authenticated: False, Connected: False
    LastSeen: 09/10/2010 07:23:42, LastUsed: 01/01/0001 00:00:00
    CoD: (0x5A020C)
     Device:  Phone (0x200) / SmartPhone (0x020C)
     Service: Network, Capturing, ObjectTransfer, Telephony (0x2D0)

    And this is what you asked for:

    • Record:

    AttrId: 0x0000 -- ServiceRecordHandle
    UInt32: 0x10000

    AttrId: 0x0001 -- ServiceClassIdList
    ElementSequence
        Uuid16: 0x1101 -- SerialPort

    AttrId: 0x0004 -- ProtocolDescriptorList
    ElementSequence
        ElementSequence
            Uuid16: 0x100 -- L2CapProtocol
        ElementSequence
            Uuid16: 0x3 -- RFCommProtocol
            UInt8: 0x1
    ( ( L2Cap ), ( Rfcomm, ChannelNumber=1 ) )

    AttrId: 0x0005 -- BrowseGroupList
    ElementSequence
        Uuid16: 0x1002 -- PublicBrowseGroup

    AttrId: 0x0006 -- LanguageBaseAttributeIdList
    ElementSequence
        UInt16: 0x656E
        UInt16: 0x6A
        UInt16: 0x100

    AttrId: 0x0008 -- ServiceAvailability
    UInt8: 0xFF

    AttrId: 0x0009 -- BluetoothProfileDescriptorList
    ElementSequence
        ElementSequence
            Uuid16: 0x1101 -- SerialPort
            UInt16: 0x100

    AttrId: 0x0100 -- ServiceName
    TextString: [en] 'Puerto de serie Bluetooth'


    Elapsed (ms): Query: 1497, Parse: 0, Display: 16

    I hope it helps you to find out what the problem is.

    Thanks a lot for your help!!

    Regards,

    Isabel.

     

  • 09-10-2010 8:45 AM In reply to

    Re: No supported Bluetooth protocol stack found

    Thanks for doing that.  I presume that was run on a different PC?  One with the Microsoft stack.  So, the remote device is behaving correctly: there is a SerialPort SDP record and it lists RFCOMM port number 1.  Can you do that again on the Widcomm PC too?

    What platform is it?  Windows XP?  Widcomm version?  Its looking a bit like things have changed on the Widcomm stack and the APIs we call are returning different information.

    Does the PC with Widcomm have VisualStudio installed, can we do some debugging?  Even any chance that I can connect to it myself?

  • 09-14-2010 6:04 AM In reply to

    Re: No supported Bluetooth protocol stack found

     Hi again,

    The program was run in a laptop where I connected the Belkin adapter. The adapter I was trying to connect to (USER-PC)  was installed in a desktop pc. Both adapters are widcomm.

    I cannot run the application in the desktop pc since it is Windows 7 64 bits and it seems it is no supported. The OS in the laptop (the one I run the application) is also windows 7 but 32 bits.

    The Widcomm version is  5.5.0.3200.

    Both pc's have Visual Studio 2008 installed.

    I don't know if that can help you. Do you need me to do any other test?

    Thanks again!

    Regards,

    Isabel.

     

     

     

  • 09-14-2010 9:56 AM In reply to

    Re: No supported Bluetooth protocol stack found

    So the laptop, which has Windows 7 and a Belkin adapter.  Its possible that actually the Microsoft stack is being used there, and the Widcomm software is just providing the user-mode applications, that's the support Widcomm officially have for Windows Vista and 7.  In Device Manager what Bluetooth components do you see, e.g. "Bluetooth Devices" or "Bluetooth Radios" at the top level?
  • 09-15-2010 5:25 AM In reply to

    Re: No supported Bluetooth protocol stack found

    Normal 0 21 false false false CA X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Tabla normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin-top:0cm; mso-para-margin-right:0cm; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} Normal 0 false 21 false false false CA X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Tabla normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin-top:0cm; mso-para-margin-right:0cm; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} Hi again,

    I think you are right. I opened the  Device Manager and I found first the Widcomm stack (under Bluetooth Devices) and then Microsoft stack (Generic Bluetooth Adapter under Radios Bluetooth.

    It is normal, then, that both appear?

    Thanks again for your patience.

    Regards,

    Isabel.

  • 09-15-2010 5:48 PM In reply to

    Re: No supported Bluetooth protocol stack found

    I'll get back to this in the morning, but just to let you know, another userhas found that using a 32feetWidcomm.dll from a previous version works.  See http://inthehand.co.uk/forums/p/3768/11141.aspx#11141  I'm going to do a new release soon and will try to provide a fix in it (even it is having to provide two different versions of the native dll -- one for newer Widcomm and one for multi-stack support).

  • 09-17-2010 7:41 AM In reply to

    Re: No supported Bluetooth protocol stack found

     Hi Alan,

    I tried to use an older version of 32feetWidcomm.dll (from 32feet.NET 2.4_0616_beta) and I have no success. I tried first only changing this dll and mantaining the version of the InTheHand.Net.Personal.dll I was using (32feet.NET 2.5_0125) and I got no errors but the bluetooth device does nothing. Then I also changed the InTheHand.Net.Personal.dll using the same version of the 32feetWidcomm.dll (32feet.NET 2.4_0616_beta) and the result was the same. :-(

    Could be that the  32feetWidcomm.dll from 32feet.NET 2.4_0616_beta version does not work on Windows 7?

    Thanks again!

    Regards,

    Isabel.

  • 09-21-2010 5:21 PM In reply to

    Re: No supported Bluetooth protocol stack found

    Isabel sorry its taking so long to get this working.

    I'll try and provide some screen shots of the ways that Bluetooth support appears in Device Manager.  So that we can try and work out what stack is active on your machine.  If you want take a screenshot of Device Manager yourself with any Bluetooth node expanded.

     

    Otherwise/also what happens 32feetWidcomm DLL is NOT present?  PlatformNotSupportException?

    And when it is present what actually occurs?  Just hang waiting for BluetoothClient.Connect to complete or?

Page 1 of 2 (23 items) 1 2 Next >
Copyright © 2001-2012 In The Hand Ltd. All rights reserved. Terms of Use and Privacy Policy. OrcsWeb's Windows Cloud Server Hosting