Hello!
I am relatively new to BLE device programming and I apologize if my issues and difficulties are a quick and obvious response or that are on some other topic, but I have not been able to find anything in the forums that can clearly answer my doubts.
I intend to develop a system of sending and receiving beacons between devices DA14580, ie a beacon emitter according to the project available in version 3.40.6 and a receiver of beacons without reliance on external processors. For this I acquired 2 DA14580 Basic Dev Kit boards.
I can run the beacon issuer program and identify where to modify advertising data and I have a general idea of how the project works, however I was not able to upgrade the project to the new SDK 5.0.4. I wanted to do this because the organization of the files is better than in the existing version of the project, which could lead to a better organization of the changes that I intend to make to the operation of the beacon emitter. Could you give me some suggestions on how to do this or is this step unnecessary and I should use the current version of the Beacon project?
Regarding the beacon receiver, I can not figure out how to do this. I have not found any way how to program a DA14580 board to work as a receptor only. Initially my idea is to have a DA14580 card to monitor the beacons that are beeing broadcasted and to print the beacon advertising data on the UART. Can you give me some pointers on how to do this?
Thank you for your attention.
Hi Lokthar,
The beacon reference design is indeed using a quite obsolete SDK and its recommended to use the newest SDK in order to base your new project, suggestion in how to do the porting from SDK3 to SDK5 is quite difficult to give, what i can suggest is to have a look at the SDK5 examples at the barebone project which is approaching a bit the beacon functionallity (as far as the advertising string is concern). Regarding the Scanner/ Receiver, you can have a look at the DSPS reference design, on the host side, this project implements a scanner and in every advertising event it gets is reported in the .app_on_scanning_completed callback (there are quite a few forum posts that deal with this kind of configuration). Also please have a look at the RW-BLE-GAP-IS in order to check the GAPM_START_SCAN_CMD and check the available configurations of the command and also please pay attention to the role that a device should have in order to be able to execute a scan command (GAP_ROLE_OBSERVER and GAP_ROLE_CENTRAL). Regarding the printing you can place in the callback i ve mentioned a printing function in order to print the found device. Please check the below post and in general you will be able to find lots of guidance on the forum for that issue.
https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bl...
Thanks MT_dialog
Thank you for your reply and suggestions.
Gonna try and follow them and see if i'm able to implement them the way i need.