I believe the answer to my issue may be the use of the Wiced Smart SDK (I’m just getting started with it) and the Cypress community would be the people that could answer my questions. But they can’t now since you moved my post. Also Anaren tells me to address my support needs to the Cypress community, so I did. Now I’m being sent back.
Do you think that the SDK can allow me to write the code to allow one Central server to talk to multiple Peripheral clients? The Atmo programmer doesn’t seem to allow this type of program/app programming.
I just need a code snippet, tutorial, YouTube, or links to these to get me moving forward. I’ve got two BLE modules and an Android phone on which I’d like to pair/connect with and display one data value coming from each.
I’d appreciate it if you could help with this.
BTW, who/where is “airlinepilot_MD”? Sounds like an Angel Flight medical pilot. My brother flew these types of missions, for free.
image001.jpg 564 bytes
2 of 2 people found this helpful
The old Multi-sensor temperature application that you have mentioned does not use BLE. Atmosphere allows to rapidly develop your firmware on the A20737 module and the mobile app, however the mobile app is not able to support multiple connections simultaneously.
You will either need to use the BLE module as a central [Hello Client Hello Sensor demo app will be a good place to start] or if you need to have an android app, you will have to write the app using native code which will allow you to connect mulitple devices simulatanoeusly.
Hope this helps.
1 of 1 people found this helpful
You may check out the hello_client app for reference on how things are done, although it may not be applicable if you are developing an Android app. I will point out a few functions/callbacks here:
1) To enable a device to emulate a Client role:
blecm_ConMuxInit(HELLO_CLIENT_MAX_SLAVES); //this allows the central to connect up to 4 (default) peripherals
blecen_Create(); //this creates the Central/Client role
2) To receive notification when controller receives advertisement from the peripheral
// register to process peripheral advertisements, notifications and indications
// You may then go on to define what you want to do in the callback (hello_client_advertisement_report).