NRF8001 timing event received data

[JeffreyRyan]

Hello!

I'm currently trying to lessen the current consumption of the nrf8001.

I tried to change the connection interval, slave latency, and the timeout using ChangeTimingRequest. However, the receiver buffer returned by TimingEvent is different from what the data sheet says. Here are my issues on the receiver buffer values:

1. the index 0 always contains 0x01. I thought index 0 should be the length of the buffer?

2. the data sheet says the returned value for the connection interval is MSB first, however I receive the value in little endian format (LSB then MSB).

Lastly, sometimes when I try to change the connection interval. it shows that it is successful based from the receiver buffer. However, the next event received (timing event) still shows the previous connection interval. Does this happen when the central is not capable of the requested interval?

[run_ar]

1. The first byte is always the debug byte. This should be discarded. Second byte is length on MISO.

2. Not sure about this one. I can't find any registered errors on the byte order here. Please check that you are not swapping them in any way. Could also be that you are right but we never noticed.

3. The timing will not change right away. but on an instant in the future (which instant is stated as part of the connection parameter update). You need to wait until after that instant to see that the timing has changed.

[JeffreyRyan]

Thank you for your help. It seems that the central decides whether the requested parameters will be accepted or not.

[run_ar]

yes, that is correct.