Skip to content

Commit 35b4def

Browse files
authored
Update bleservo.rst
1 parent bdea294 commit 35b4def

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/tutorials/ble/bleservo.rst

+2-2
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ GATT in this application contains only one custom service, which contains two ch
1919
Both characteristics contain information about PWM pulse width, however one of them stores this information in the form of servo's tilt angle [degrees] and the other one in pulse duration [microseconds].
2020
This allows the user to control servo in two ways, either with angle or with PWM pulse duration.
2121

22-
Notifications are used to update user's information on both values if one of them has changed. The other corresponding value is calculated before sending a notification, what will be described below, in section PWM Configuration.
22+
Notifications are used to update user's information on both values if one of them has changed. The other corresponding value is calculated before sending a notification. This calculations will be described below, in section PWM Configuration.
2323

2424
.. code:: c
2525
@@ -108,7 +108,7 @@ Notifications are used to update user's information on both values if one of the
108108
[...]
109109
110110
111-
Write callbacks of each characteristic call angle or pulse duration setter function. Both files ``gatt_svr.c`` and ``main.c`` need the access to this variables and thanks to this solution, the extern keyword wasn't used in the application. In addition, the boundary conditions of the updated value are checked in this functions and in the end, PWM fracture update event is put to the queue. ``was_angle_passed`` variable is used to keep track on which of the variables has been passed and changed.
111+
Write callbacks of each characteristic call angle or pulse duration setter function. Both files ``gatt_svr.c`` and ``main.c`` need the access to this variables and thanks to this solution, the extern keyword wasn't used in the application. In addition, the boundary conditions of the updated value are checked in this functions and in the end, PWM fracture update event is put to the queue. ``was_angle_passed`` variable is used to keep track of whether the user passed angle or pulse duration value.
112112

113113
.. code:: c
114114

0 commit comments

Comments
 (0)