How does nRF Connect interpret the RR Intervals in nRF Connect?

[mmnano]

Hello,

I was trying out sending RR intervals on the Heart Rate Measurement service and seeing what happens in nRF Connect. But, something is weird with the way the values are interpreted in the app. The flag for Energy Expended is set to 0, so there should not be any in the packet. But if bytes 2 and 3 of the hrm packet are used to send RR intervals , they are just ignored:

Whatever RR interval is in bytes 2 and 3 is straight up ignored.

Here is another example with putting RR intervals values from byte 4 onward instead of byte 2 onward:

This time, no RR Interval value is ignored!

This is the table from the spec as reference:

Could somebody explain what I am doing wrong ?

Thank you for your help.

Best regards,

[Simonr]

Hi again

After some further debugging on the Android side, we found a bug in the nRFConnect application where a rouge offset causes these two bytes not to be printed by the nRFConnect log.

Thank you for reporting this and helping us reproduce it so we could get to the bottom of it. This fix will hopefully find its way into the next update of the nRFConnect for Android scheduled early next year.

I'd also like to thank you for your persistence.

Best regards,

Simon