struct custs1_val_ntf_req* req = KE_MSG_ALLOC_DYN(CUSTS1_VAL_NTF_REQ,
TASK_CUSTS1,
TASK_APP,
custs1_val_ntf_req,
DEF_CUST1_NTF_CHAR_LEN);
...
ke_msg_send(req);
I assume this code will result in a Notification message (based on CUSTS1_VAL_NTF_REQ), which is an asynchronous message, without waiting for an acknowledge packet, is that right?
I want to make use of as much as possible packets per connection interval (highest throughput) and this is why i think i should use messages without acknowledgements, is that also right?
My peripheral is connected to a Samsung Galaxy S5, which supports (i am not that sure about it, but i think it is) 5 packets per connection interval, since i can see 5 peaks within one connection intervall on the oscilloscope by measuring the current drawn by the chip.
However, based on counting the packets i receive on the smartphone (checked for packet loss by counters) in a certain time interval and considering the connection interval parameter chosen by the smartphone, i calculated an average of 2,5 packets per connection interval.
As i expected it to be 5 packets per CI, this leads me to the assumption, the the sending operation invoked by my DA14583 code, are somehow acknowledged and thereby dropping the average usable packets per CI to 2.5 (half of possible packets per CI).
Can someone tell me, whether i am right with my assumption or if i indeed invoke a asynch message sending and the issue must be somewhere else?
Kind regards,
Florian