G.FIT User Guide and Specification, Rev 2.0_Alpha.14
Page 91 of 117
thisisant.
com
7.5
Events (0xE0)
Each event is referenced by the related definition in the G.FIT library and the associated sub-message ID.
7.5.1
gfit_event_receive_heart_rate_ (0xB2)
Event: An event that is sent to the MCU when G.FIT receives HR data from the wireless heart rate monitor it
is currently connected to, as well as scan packets for heart rate monitors in the vicinity.
Requires Response: No
Depends on HR pairing mode: Proximity/Channel ID
Corresponding G.FIT library functions: This serial message relates to
gfit_event_receive_heart_rate_scan_packet and gfit_event_receive_heart_rate_paired_packet in the G.FIT
library.
Table 7-62. gfit_event_receive_heart_rate_ event message
Byte #
Name
Length
Description
0
Sync
1 byte
Fixed value of 10100100 or 10100101
(Refer to the
Interfacing with ANT General Purpose Chipsets and
Modules document for details.)
1
Length
1 byte
Variable
2
Message ID
1 byte
0xE0 (event)
3
Sub-Message ID
1 byte
0xB2 (gfit_event_receive_heart_rate_)
4
Flags
1 byte
Bit 0
–
0: Scan, 1: Pair
Bit 1
–
0: ANT protocol, 1: BLE protocol
Bits 2-7
–
Reserved for future use (set to 0)
5
Heart Rate
1 byte
Heart rate in bpm.
0x00 indicates invalid
6
RSSI
1 byte
RSSI in dBm
0x7F indicates invalid
7
HRM ID
6 bytes
HRM ID LSB
8
–
11
…
12
HRM ID MSB
13
BLE Friendly
Name Length
1 byte
Length of the BLE friendly name
0x00 indicates no name
If the protocol is ANT, this will be set to 0x00
14
–
N
BLE Friendly
Name
N bytes
BLE friendly name (maximum of 20 bytes).
N + 1
Checksum
1 byte
XOR of all previous bytes including the sync byte.