How to operation the ATT_MTU Throughput Example?

[ken_k]

Hello.

I'm running the nRF5 SDK's ATT_MTU throughput example.(nRF5 SDK v15.3.0, nRF52 DK(nRF52832))

The tester is running as a central or peripheral device.

How to operation the tester is running as central device?
How to operation the tester is running as peripheral device?

Thank you.

 

[Susheel Nuguru]

The documentation for this example shows that button 3 and button 4 are used on each device to configure it as central /peripheral  (tester/responder) device. 

[ken_k]

Thank you for responce.

There is a case where the tester becomes peripheral device follow the steps below.
This operation is not certain.
1.Compile and program the application on both test boards.
2.Start a terminal emulator
3.Press Button 3 on the tester to put the application into tester mode.
4.Type run in the terminal to start the test.
5.The other board press Button 4 on the responder to put the application into responder mode

I want to know the reliable operation.

[ken_k]

If you follow the documentation, it will look like this:

[Susheel Nuguru]

I see what you mean.

In the ATT_MTU example there is no defined GAP role for each board. Both boards advertise and start scanning and we do not know which one would become a central and which one would become a peripheral until the connection is established. 

When the connected event is received, the gap roles are known from  p_gap_evt->params.connected.role. This example do not put any significant importance on which board has which role, 

Board Tester is the server sending (spamming)  notifications at max speed possible.

Board Dummy is the client receiving the notifications.