KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
I'm trying to implement an Android application to receive data from a medical device but I can't get through the discovery process and get the phone and the device paired or connected to each other. Describing the medical device: The device is using Service Discovery Protocol (SDP) and Serial Port Profile (SPP). It starts an inquiry procedure to discover (up to 10) surrounding access points with matched COD Filter and Service Name. Then it sequentially establishes a connection (using Page Procedure) with the access point by checking the PIN. Once the PIN is matched, the data is uploaded. Upon uploading data the device waits for an acknowledge. The decice is the master and initiates the communication. I have no control of the medical device. All I can do is to start it and await the procedure described above (after a measurement). The Android application: I've started out from the Bluetooth Chat Example on the developer pages. So far I've replaced the UUID with the 00001101-0000-1000-8000-00805f9b34fb to use SPP and set the Service Name to the appropriate name. I can confirm this seems correct through inspection of the service from a computer. Since the medical device is the one that inquirys and initiates the communication my service is using a BluetoothServerSocket and the accept() method to start listening for it. In the developer pages I've read that UUID must match between the applications trying to communicate. Since I can't set any UUID for the medical device I'm wondering if this is going to be a problem or if it is enough that the medical device is using the SP Profile? If the Service Name and UUID are correct and the medical device would actually try to connect to my Bluetooth service which is listening for
Tags (comma-separated)
Save Edits
Cancel