Hello, MT_Dialog,
We are developing a product which uses phones to communicate with DA14580. iOS software(iphone 5s - v9.3.2 and iphone 7 - v10.2.1) will be disconnected after 25s which is a fixed number. Besides, iOS can get data while DA14580, but DA14580 cann't receive data from iOS(both our software and LightBlue which helps to develop Bluetooth). iOS has set the right UUID, and the communication method of iOS has been applied successfully on other project such as CC2540.
However, Android software have not meeted this two problems yet.
Some engineers suggest us to use latest version of firmware , such as 5.0.2.1 or higher, but it will cost us lots of time to use new SDK. Could you please give us some suggestions? And it will be a nice thing if you can send iOS demo to us!
Look forward to your favourable reply.
⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
Wed, 2017-07-12 04:13
#1
The connection and communication between iOS and DA14580
Device:
Hi zopies,
在进入对话框显示最新的SDK范围h is the 5.0.4 and not the 5.0.2.1, i suppose that you are using SDK3 for your application. Additionally i am not able to understand the problems that you have on the project, as far i can understand you mention that you are not able to receive any data from the 580 to the iOS device while you can with an android device, which is a bit generic and i am not able to deduce anything by that description, but if it works with android and not with iOS then i can assume that this has to do with the iOS itself and not the SDK or the 580. Finally you should be able to find the source code of iOS and android on the support site in the following directory "Software & Tools" -> "Mobile". There you will find the Smart Tags application and the SUOTA application source code.
Thanks MT_dialog
Excuse me, it seems hard to find the right address. In the following directory "Guide" -> "Software", I just find some links to get iOS app without source code. Could you please paste the address of souce code for me (find the source code of iOS and android on the support site in the following directory "Software & Tools" -> "Mobile" )? Thanks a lot.
Hi zopies,
Please check the link below:
https://support.dialog-semiconductor.com/connectivity/product/da14580?qt...
Although i dont think that the link will help, since the location is restricted and you will have to login and it will promt you to the main page of the support site, so from the main page, choose the tab that indicates "Software & Tools" and then one of the options under this tab will indicate "Mobile" inside that tab there are all the source codes available.
Thanks MT_dialog
谢谢!在帮助下of LightBlue in iOS, we thought there may be some problems about the hardware. After modifying the length of UUID in DA14580 from16 bits to 128 bits and setting iOS without response, it is exciting to get right result that iOS and DA14580 can communicate with each other successfully. Besides, the communication can keep for a long time. The SDK of DA14580 is still 3.0.10.
Though we have sovled the two problems above, I wonder why DA14580 needs to set 128-bits UUID instead of 16-bits one. Android can both cummnication nomally under this two length setting of DA14580's UUID.
Hi zoples,
I suppose that you mean the UUID length of the services and characteristics. The SIG profiles are using 16bit UUIDs and custom profiles use 128bit UUIDs, this is defined by the Bluetooth SIG, so i suppose that what you see doesn't have to do with the 580 or the SDK but with the iOS. Perhaps for the iOS the usage of custom profiles requires 128bit UUID's and restricts access to custom profiles that operate under 16-bit UUID's, although it seems a bit unlikely, but if you see this only on iOS devices and its working on Android devices its the only logical assumption that i can do.
Thanks MT_dialog
Thank you for your help! : )