• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 50 subscribers
  • Views 805 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Can't send 4 notifications per event consistently

Cagatay Ulusoy
Intellectual 625 points

Hello,

I am sending 4 notifications (each 20 bytes) within a periodic event. The connection interval is 75 milliseconds and burst event period is 150 milliseconds. Each packet is sent via one function. I labeled the packets by adding number to the last byte so first function's packet ends with 1, and second ends with 2 and so on. I have some questions to be answered. I would be grateful if you can answer.

At the beginning of the established connection everything is well. 4 notification packets are sent within one connection event which means 4 functions are executed. 

Then it sends only 2nd and 3rd packets for a while and connection interval becomes 150 milliseconds (I know that it is still 75 but packets are sent in 150 milliseconds)

Finally only 3rd packet is sent in each connection event until the end and connection interval is still 150 milliseconds.

What is the reason behind that? Although every other parameters are constant, why cant I send 4 notifications in each connection event like at the beginning?

And why only the 3rd function's packet is sent but the others?


Regards,


  • 0
    Intellectual 625 points

    I increased the connection interval to 300 milliseconds and now I can see 4 notifications per event but I wish I could send 4 notifications when burst period is equal to the connection interval wich is 75 milliseconds.

  • 0 in reply to Cagatay Ulusoy
    Intellectual 625 points

    Another interesting case: I set the connection event 75 milliseconds and burst event period to 75 milliseconds as well. Now strange thing is going on. I can see all the 4 notifications but... this time the problem is with SN and NESN values. Normally, Master packets' SN and NESN values are the same and Slave packets' SN and NESN values are different. However, here it is as opposite. Can anyone explain this?

     

  • 0 in reply to Cagatay Ulusoy
    Guru 18645 points

    Setting burst and connection periods at the same value is somehow optimistic.

    The timers may be delayed a few milliseconds depending on the application. I would recommend you setting, for example, a burst period ten milliseconds lower than connection event to be sure.

    Think of notifications as passengers waiting for the bus. If they arrive at station at 10:15pm and the bus leaves at 10:15pm they may lose it ;)

    Bye!

  • 0 in reply to kazola
    Intellectual 625 points

    Thanks for the answer Kazola,

    When I try your suggestion, I could see only 3 notifications or less can be sent in one event.

    By the way, do you have any idea about why the SN and NESN values behaved differently on my last post?