This is not ideal! You have to close and restart radio device, it takes time and is fault prone. Microsoft - If an error occurs during a scan, it's common for the whole stack to crash out. This is where the WCL library comes in handy! So the only option is to run one dongle on one stack and the other dongle on another. NONE of the stacks support 2 dongles at the same time. It supports all the server side stuff we need, is a well supported commercial product, which works perfectly without error. It supports Widcomm, Windows, BlueSoleil and the Toshiba stack. So, the idea is to run one dongle continuously scanning (so devices appear as quickly as possible) and the other dongle reserved for transfers, and since it's not scanning, transfers are nice and quick.Īfter much testing and thought, we ended up opting for WirelessCommunicationLibrary from BT framework. If you want to send, receive and scan all at the same time, everything slows down, badly, and you are very limited in channels. A dongle can only support 7 concurrent transfers, if you are doing a scan, this drops to 6.If a dongle is doing a scan the transfer rate is massively slowed down.Time to explain exactly what we ended up doing. What was the issue with the samples? Compile-time or run-time? On MSFT stack or Widcomm? Follow-up at if you prefer. The server-side still needs a little work however and there are some things the Widcomm API simply doesn't support eg. Inquiry (device discovery) and connections all work. Hopefully it doesn't seem too "incomplete" on the client side. I've also tested it with Andy Hume's OBEX Server using his Brecham.Obex library and the concurrent receive works fine there too. To do multiple parallel connections with ObexListener I just had multiple threads calling its GetContext() method. To send the OBEX PUTs one can use its ObexWebRequest class. That's using 32feet.NET's ObexListener class and the BluetoothClient.DiscoverDevices method. I've just checked, and on XP with the Microsoft stack (using one dongle) I can concurrently be receiving two OBEX PUTs and also discovering devices. Firstly the disclaimer, I'm the maintainer of the 32feet.NET library.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |