I am able to to a service discovery of the DIS service using the DISC profile on the first connection. If the device disconnects and then reconnects, attempting to do a second service discovery fails with a GATT timeout (0x57) error. A second service discovery may not be necessary but it is certainly allowed within the BTLE specification. Why does the second service discovery fail?
I honestly don't know but could service discovery procedure change some state which doesn't return and then the device doesn't manage the request right?
比ks for your comment. I assume you mean the peer device...? If so, one never knows, of course, that could always be the case. But using the Android platform as a central I have no problem. I am wondering if there is some undocumented action taking place where the SW refuses to perform the action since it already has been done. Dialog doesn't offer much in the way of any documentation of central role activities so its hard to know what is going on.
If you mean the Dialog SW then that could very well be. I am using their template projects and it could be something inconsistent there. The templates are very peripheral-oriented and even when one sets the role to central there are peripheral-only actions that remain that break a central. I have found some but likely not all. And I haven't even begun to look in the profiles.
Hello Brian,
Indeed, this should not occur.
Can you send me a LOG from this failure?
You can test by using the BTOOL or the connection manager (http://support.dialog-semiconductor.com/connection-manager-win-installer) and read the DIS.
regards,
DIALOG TEAM.
THank you for your reply. That brings up a different issue, when I try to install the Connection Manager my anti virus software (AVG) says it is infected with the Downloader.Agent virus. I just downloaded the SW again and got the same result. Is there a known conflict with AVG? I don't dare to install it; the warnings about what Downloader,Agent does are pretty grim.
Hello Brian.
we are aware of an issue with AVG and smart snippets : please see the post below..
http://support.dialog-semiconductor.com/strange-anti-virus-warning-message
BR JE_Dialog
Smart snippets installs without a problem. Its the connection manager that has the warning. Its a different warning. It states the SW contains the Download.Agent virus.
OK Brian, i will check wth the developer and come back to you.
BR JE_Dialog
I am no longer using any client profiles but using GATT* and GAP* APIs only since they appear more robust for the central developer; so I no longer have the code in place to debug the DISC service discovery issue. Service discovery IS working at the GATT level (so far).