So to get around problem (1), I thought I would only load the WCL api when bluetooth functionality was first used, rather that loading the API on application start. Problem 2: Delay loading the API not working Calling CwclAPI.GetBluetoothAPIs() returns 'baToshiba' as the only entry. Sometimes the application will start up on boot, and the bluetooth will function correctly without needed to restart the application.ĬwclAPI.Load() is returning success. I think this is to do with application loading order on device start up.Īdditionally, the issue does not happen every time. This kind of defeats the point of being able to load on start up! However, on Toshiba based devices, clicking 'discover' will cause an error to show: No Bluetooth API was found.ĥ) Only restarting the application will allow the chat application to function correctly. Make sure it starts normally, and that devices can be discovered when 'discover' is clicked.Ģ) Create a link to the chat client in shell:startup (you can type 'shell:startup' in Windows explorer to access the start up folder).Ĥ) When you log in to Windows, the chat application will automatically load. Use the "paid" version of the c++ DLL, so that no pop-ups appear on load / unload of the application. This is the device that is causing us problems.ġ) Get the Bluetooth chat client demo and build it (we built using the 2012 solution / dll). We have one device (the Panasonic Toughpad FZ-G1) that uses the Toshiba Bluetooth stack. The majority of devices we have are Microsoft stack based - and we have had no problems with these devices. Both the problems described below happen with 6.13.4.0 and with a slightly older 6.13.1.0
Toshiba bluetooth stack stpped working software#
We are using WCL to perform bluetooth communications for our software on Windows 7/8 machines.
0 kommentar(er)
