I'm evaluating WCL Developer edition for our application, but we need to make sure it can do what we need before purchasing. I'm having trouble running your demo BluetoothClientDemo application with our bluetooth device. Basically, we need an API that can communicate with our Leica DISTO device via bluetooth. The sample application discovers the device and the service just fine. However, the connection fails. I'm trying to use the SerialPortServiceClass_UUID for WclClient.Service, but it always returns an error code 44. In fact, I've tried to assign the UUID of the discovered service, but that doesn't work either. Basically, the DISTO device communicates over a Bluetooth connection using serial communication. When I run the SerialClientDemo, and test using the "Bluetooth Serial Port" it works just fine. However, we're trying to get away from having the user deal with COM ports. Instead we would like to have our application simply discover the device and work with it. Can you tell me if WCL is supposed to work this way? What are we doing wrong? Thanks.
