Unknown error when trying to connect to a device about pybluez

[GoogleCodeExporter]

This issue seems to appear only with Windows Vista. I tried it on the same 
notebook
with Linux and everything works as expected.

Original comment by [email protected] on 21 Aug 2008 at 4:27

[GoogleCodeExporter]

Hi,

I don't have a vista computer, and am unfortunately unable to be much help 
here. 
Just for reference, what version of the Widcomm stack are you using?

Original comment by [email protected] on 1 Sep 2008 at 5:08

[GoogleCodeExporter]

hi,
i want to report the same problem in a Vista notebook. Python2.5 and PyBluez 
0.15

Original comment by manuelpintaldi on 11 Oct 2008 at 12:36

[GoogleCodeExporter]

Me also having same problem. My Vista system doesnt support Pybluez or 
Lightblue. any
available solution for Vista users??

Original comment by [email protected] on 21 Dec 2008 at 8:51

[GoogleCodeExporter]

I'm also having these problems except I'm trying to write a socket server 
program and
I get this error when I call listen().  I'm using Widcomm 6.0.1.3100.

Original comment by [email protected] on 8 Jan 2009 at 2:54

[GoogleCodeExporter]

Yeah, Vista / Windows 7 support would be really great. Anybody willing to do 
this? ;)
I've looked through the source and as far as i can tell it won't be really easy
(however i haven't got a clue about the windows api)

Would be willing to test it :)

Original comment by [email protected] on 8 May 2009 at 3:26

[GoogleCodeExporter]

Hi Everyone,

I am also trying to use the PyBluez module on a Vista with the same problem 
reported 
above. Switching my code and trying on XP works sometimes (not all the time). 
If I 
connct succesfully once and terminate mycode, then I am having to power cycle 
my 
Bluetooth GPS every time I need to run my code the second time. Otherwise it 
doesn't 
work with the error mesage given as above posts. There are some problems in the 
Windows version of this module (particularly bad under Vista). Any plans to fix 
these ? 

I would be happy to help doing this but I don't know how to trace these 
problems and 
my coding skills are not too great. 


Is there any plan to 

Original comment by [email protected] on 27 Jul 2009 at 11:49

[GoogleCodeExporter]

Hi everyone! Thank you for your work with pybluez! I'm using pybluez for lego 
NXT 
(I'm a contributor for nxt_python) robots and recently I installed windows 7. 
With 
XP, everything ok, but now it does not.  My error is a result that equals 1, 
but i'm 
unable to know what "open_client" returns, because this part is compiled. Can 
anyone 
contribute the source to check if there's anything we can do about this?

 result = self._wc.open_client (port, str_to_BD_ADDR (addr), DEFAULT_MTU)
        if result != _widcomm.RFCOMM_SUCCESS:
            raise BluetoothError (_port_return_code_to_str (result))

Original comment by mestre.vieira on 29 Aug 2009 at 12:15

[GoogleCodeExporter]

I have the same problem in Vista. Has anyone found any solution?

I am using python 2.6 and pyBluez-0.16

Original comment by [email protected] on 16 Nov 2009 at 1:19

[GoogleCodeExporter]

Hello,

please look in this mailing list thread: 
http://groups.google.com/group/pybluez/browse_thread/thread/6be8eaeeee029766

I only had to compile PyBluez against the latest Version of Visual C++ and the 
Widcomm SDK. This solved all issues with Windows Vista and Windows 7 for me.

I could send you a binary package if you want. (The source code is PyBluez 
0.17, 
patched with VC++2008.patch)

Original comment by [email protected] on 16 Nov 2009 at 1:29

[GoogleCodeExporter]

Attached file PyBluez-0.17.win32-py2.6.exe
I tested this on Windows XP, Windows Vista 32bit and Windows 7 64bit, but don't 
blame 
me if it doesn't work for you.

Greetings,
Lukas

Original comment by [email protected] on 16 Nov 2009 at 1:50

Attachments:

• PyBluez-0.17.win32-py2.6.exe

[GoogleCodeExporter]

Thank you Lukas, worked perfectly. :-)

Original comment by [email protected] on 27 Nov 2009 at 1:53

[GoogleCodeExporter]

Okay, then I'll close this issue. Feel free to reopen it again if you have 
problems 
with this package. 

Original comment by [email protected] on 2 Dec 2009 at 9:35

• Changed state: Verified