Recent Posts

That is great idea to use remote server to collact stats. I just recomended TextBlue as a other software you can test functional and compare to your.

Thanks you, actually de app I'm developing has a few especial features. It connects to a remote server, and download the campaigns, upload usage stats and stuff like this, this way the clients can check the stats from the web, and make comparisons between diferents usb dongles on diferents locations.

By the way, thanks for the response, i'm going to change the way I'm 'reading' the codes. I'm testing now the textblue and found that the stats are pretty similar. I'm testing bluesender too, and the same thing.

So i think the last software my company used was stat-manipulated.

Have nice day!

Hi,

There is no one phone except SonyEricson which will wait more than 15-20 seconds. So that is absolutly ok that you have timeout in 15 seconds or so. Some devices may send Reject code even timeout appeared. OBEX_FORBIDDEN - usualy sent by SE/LG as user reject code (LG as phone reject even timeout). Actualy you got good result. Just may be wrong result code interpretation.

I can recomend to try our solution: http://www.btframework.com/textblue.htm it is WCL based application.

Hi,

I've done a little app with the WCL, and one of the basic features is too show the statistics. The people for whom I work, are telling me that there are a lot of rejected connections in comparison with their old software.

Then I tried the proximitySenderDemo and I'm founding a lot of weird thins. First of all, i put a timeout time of 120 seconds, and each proximitysender round, there are a lot of devices who send a 'timeout' (WCL_E_TIMEOUT) in the first 15 seconds.

Therefore another lot of devices send rejected connection in the first 15 seconds too (WCL_E_CONNECTION_REJECTED). On top of them, a few of them throws a internal driver error and others obex_forbidden and stuff like that.

What could be the reason of this? the usb drivers? the usb dongles? there are actually a lot of people looking at the movile in each second and they reject the request inmediatly?

Am I doing something wrong? do I have to put in the black list some manufacturers like IPhone and blackberry(I already put this two manufacturers MAC on the black list, so they are beeing ignored).

I will apreciatte any kind of help

Possible solution: com0com. One COM port is "connected" to WCL, second one is used by ZModem API.

Thanks for the advice,

Unfortunately Zmodem API works only for COMM port, I will try to convert the code to accept data coming from wclClient_OnData  function but it wont be easy...

Hi,

COM ports is used for wired connection. Bluetooth is wireless one. Use wclClient and its method Write to send data to device and OnData event to process received data.

Do not use COM ports for Bluetooth. It is old and bad idea.

Hi

I am trying to receive  a file from an external device using SPP interface. My project is .NET project (C#) and I am using demo version of WCL.
Basically, device wakes up sometimes and is available for a SPP connection. I managed to connect to it
using discover and connect interfaces (wclBluetoothDiscovery, wclClient). After a successful connection I  have a ZModem interface which opens connected port and gets the file. I have three cases about this scheme and none of them worked.

1. After I setup

wclClient.Transport = wcl.wclClientTransport.ctBluetooth;

I connect but there is no information that describes which COMM port is used for current connection. Even I hard coded comm port that used for current connection, obviously COMM port is already open and my ZModem interface cannot open same port.

2. After I setup

wclClient.Transport = wcl.wclClientTransport.ctSerial;

I connect but I have to hard code port number and again port is already open and I cannot open same port.

3. After I setup

wclClient.Transport = wcl.wclClientTransport.ctSerial;

I created a virtual COMM port using wclVirtualCOMPort that solved to get the port number but again port is already open and I cannot open same port.


Is there anyway that I can find out which COMM port is used for current connection? I prefer to connect to device like case #1.

Also after I connect to remote device SPP service, is it possible to keep COMM port NOT allocated by WCL? That way I can use my ZModem interface to open COMM port and get the file.

Regards,

Hi,

wclBluetoothAPIs CwclAPI::GetBluetoothAPIs();
wclTransports CwclAPI::GetTransports();

Please, refer to API demo to find out how to know transports available. Also, refer to API references documnetation available in WCL package.

I wanted to say widcomm nor toshiba , that was a mistake. Ok thanks you!

(I think in the above post doesn't says anything about copying the file to system32, but i think i have read something similar in another topic of the FAQ forum)