Can you please clarify your question, what you mean how to access the target device ? There is no actual functionality in the example, the project is just an example that demonstrates the capabilities of the 680, there is no data transfer with the connected peripherals. The multilink demo acts as a peripheral and a central at the same time. Initially it acts like a peripheral until a connection is made from a central (your phone for example), as soon as a central (your phone, the master device) connects to it, the advertising stops and it will restart as soon as the first device (the master device) gets disconnected. When a BD address is written to the characteristic, the demo initiates a connection procedure (it acts as a central and starts scanning, when the device with the specific bd address is found it connects to it).
Hi Ken Chong,
Can you please clarify your question, what you mean how to access the target device ? There is no actual functionality in the example, the project is just an example that demonstrates the capabilities of the 680, there is no data transfer with the connected peripherals. The multilink demo acts as a peripheral and a central at the same time. Initially it acts like a peripheral until a connection is made from a central (your phone for example), as soon as a central (your phone, the master device) connects to it, the advertising stops and it will restart as soon as the first device (the master device) gets disconnected. When a BD address is written to the characteristic, the demo initiates a connection procedure (it acts as a central and starts scanning, when the device with the specific bd address is found it connects to it).
Thanks MT_dialog
Noted with thanks.