I've been developing a device using the da14580 and have been using lightblue on ios and a variety of android apps during development. I am able to scan and pair with my da14580 based design with both ios and android. One of the software developers I work with has tried to start working on a demo program that will interact with my device, but he can't even get windows 8.1 or windows mobile to connect to the da14580. Has anyone else been able to use windows as a central device? I know it's probably the least popular platform for this type of application but unfortunately it's what we have to go with for now. If anyone has any advice or insight into what the issue could be please let me know. Thanks.
Device:
嗨。窗户需要password pairing. Are you sure you are using that and not the Just Works pairing?
Thanks for your response, I am unsure, but I am going to assume I am using just works pairing. I've looked through the forum and the available documentation and haven't found much info about working with the security features. I am working with SDK 5 and used the ble_app_peripheral project as my starting point. I went in and defined CFG_APP_SECURITY but I am unsure what that actually does. Is there any documentation that goes over this? Thanks again.
Hi Dave,
The CFG_APP_SECURITY is something like the main switch to use security, by just defining this you wont have security in your project. By setting the user_default_hnd_conf member .security_request_scenario to DEF_SEC_REQ_ON_CONNECT you can sent to your host a security request (since your characteristics dont require security in order to be read). There is no documentation explaining the security configuration but you can check the Smart Tag reference design in order to have an idea about the messages exchanged when security is demanded.
Thanks MT_dialog
I already wrote about Windows and SDK5. You must enable security:Instructionsand you can't use custom profiles. If you use SDK3 you can work with disabled security and custom profiles. I have a working Windows Phone application with a custom profile and with the SDK3 works fine.
So the SDK5 is almost useless for a Windows platform and the SDK3 is little outdated. Hope they will fix this soon.
Thanks Cusko.