• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 2 answers
  • Subscribers 51 subscribers
  • Views 176 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LAUNCHXL-CC2640R2: Project Zero BLE transmission at 45 ms

Moin Shaikh
Intellectual 580 points
Part Number: LAUNCHXL-CC2640R2
Other Parts Discussed in Thread: CC2640R2F

Hello, 

I have imported Project zero, and made a custom profile using the sunlightservice.

When I make a connection using the BLEScanner,, I get the following waveform.

45 msec after connection with BLEScanner established

This waveform indicates that the connection has been established and we are looking at some transaction taking place every 45 msec, between the central (CC2640R2f) and peripheral (BLEScanner).

This 45 msec transaction persists, I have even tried to follow the link below,

https://dev.ti.com/tirex/explore/node?node=A__ANtgxHq3pOxLq.bxN1FlGA__com.ti.SIMPLELINK_ACADEMY_CC2640R2SDK__7unKOT8__LATEST&placeholder=true

Now I have made the following changes,

I have set the "DEFAULT_SUNLIGHT_TIMEOUT" = 80 ms. In the "APP_MSG_PERIODIC" I create the packet and try sending it. The below waveform indicates the packets being generated. But I observe the BLE transaction taking place at 45 msec and not 80 msec.

80 msec packet

Kindly help me with eliminating the this 45 msec package transmission.

Regards,

Mohin Shaikh

  • 0
    TI__Expert 4496 points

    Hi Mohin,

    I am not sure if I understand your requirements 100 percent. And also your plots are a bit confusing. 

    Do you have a sniffer log available to check what messages are transmitted ? 

    However if you want to change transmission interval, why dont you change the connection_interval located in project_zero.c ? 

    Fullscreen
    1
    2
    3
    4
    5
    // Minimum connection interval (units of 1.25ms, 80=100ms) for parameter update request
    #define DEFAULT_DESIRED_MIN_CONN_INTERVAL 12
    // Maximum connection interval (units of 1.25ms, 800=1000ms) for parameter update request
    #define DEFAULT_DESIRED_MAX_CONN_INTERVAL 36
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Regards,

    Alex

  • 0 in reply to Alex Paul
    TI__Expert 4496 points

    Hi Mohin,

    Did you manage to solve your issue? 

    Otherwise as mentioned above, a sniffer log would help to solve your problem.

    Regards,

    Alex