How to operation the ATT_MTU Throughput Example?

RE: How to operation the ATT_MTU Throughput Example?

Susheel Nuguru — Tue, 03 Sep 2019 07:01:33 GMT

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.

RE: How to operation the ATT_MTU Throughput Example?

ken_k — Tue, 03 Sep 2019 06:40:55 GMT

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

RE: How to operation the ATT_MTU Throughput Example?

ken_k — Tue, 03 Sep 2019 06:35:20 GMT

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.

RE: How to operation the ATT_MTU Throughput Example?

Susheel Nuguru — Tue, 03 Sep 2019 05:02:08 GMT

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.