Wireless Communication Library Support Forum
Frameworks => Bluetooth Framework => Topic started by: alexey_gusev on June 11, 2009, 03:59:03 PM
-
hello Mike,
what would you recommend to workaround/fix the following scenario:
- Widcomm BT stack, embedded BT adapter (some HP laptop)
- I start device discovery by calling wclBluetoothDiscovery.Discover()
- there are too many times when it never signals back, I've tried the same with BluetoothOPPClientDemo
As far as I understand there is no way to set a timeout for discovery (except doing it manually with timers etc).
Any ideas are appreciated.
BR,
Alex
-
What is WidComm version?
The Discovery method has Timeout parameter.
-
for the version - please see attached image
for the timeout - oops, my fault :)
[attachment deleted by admin]
-
Strange thing. I'll test and try to fix.
-
btw, Timeout parameter (I assume it's in seconds?) didn't help either, it just went nowhere. Rebooting the laptop usually helps in such cases, but it'd be nice to know what's the reason :)
-
Could you somehow send me the drivers used on your laptop?
-
this is HP EliteBook 8530w, I guess drivers should be on HP site. If you know exact filenames, I can copy them and send.
this (and previous) laptop is kind of good testing piece of metal, because eg now it's trying to connect to the phone it discovered and also doesn't return. Usually it works, but...
-
Thanks for the info. I'll try to download drivers an test
-
Hi,
I downloaded the drivers from HP site but unfortunatly it does not work with my external BT dongles. I will try to simulate the problem and fix the problem but it may take some time.
I am really sorry for delay with fixing the bug.
-
no worries ;)
it would be really good to fix this issue as it is worrying a bit. usually it works, and mostly it works with BT dongles, but since it is at least second time when I see such problems with embedded BT hardware, it should be something in there
BR,
Alex
-
if I can help in any way, please let me know.
-
in addition to the previous posts, if I have my BT adapter in *bad* state (when it doesn't return results with WCL, but I can see them via Windows), wclBluetoothDiscovery.Discovery() with timeout parameter returns 0 as a return code, but again, never completes discovery within specified timeout.
What are the units for timeout value?
-
Timeout is in seconds. It hard depends on driver how the value will be processed.
-
great. is there any way I could get some logs from WCL? I'm quite keen to resolve this issue or at least get some sensible behaviour instead of just infinite discovery. I understand that it may be anything - drivers, WCL or whatever else :)
-
Unfortunatly WCL doesn't provide any logs but you might get WCL sources and debug it step by step.
-
Hello Mike,
any news about this issue? Should wclBluetoothDiscovery.Discovery(Radio,Timeout) just finish if Timeout is reached? I don't see it EVER worked :)
BR,
Alex
-
Timeout works only on stack which supports it. WidComm seems does not support such feature.
-
is it possible to terminate the discovery internally in WCL in such case? I just want to avoid adding unnecessary timers myself :)
-
It is possible by calling Terminate() method. But in this case you do not get discovered devices list. Any way, please try the attached wcl2wbt.dll. It may solve your problem. Simple, replace the old DLL with new one.
[attachment deleted by admin]