want to know how can i judge that the variation is caused in the connection interval, connection supervision timeout, slave latency once i have flashed ble_app_template code in nrf52832 s132.
want to know how can i judge that the variation is caused in the connection interval, connection supervision timeout, slave latency once i have flashed ble_app_template code in nrf52832 s132.
It is hard for me to say anything about what might be going on here, from your description alone. Is there any errors occurring when you use the 1000 ms connection interval? Does the device reset unexpectedly?
I would think that you might get buffer overflows etc when increasing the connection interval by this much, if you have not also made changes to your sensor-data buffer sizes.
Have you verified that the connection interval being used is actually 1000 ms?
Best regards,
Karl
yes i have verified this infact i also did with
#define MIN_CONN_INTERVAL MSEC_TO_UNITS(4000, UNIT_1_25_MS) /**< Minimum acceptable connection interval (0.5 seconds). */
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(4000, UNIT_1_25_MS) /**< Maximum acceptable connection interval (1 second). */
#define SLAVE_LATENCY 1 /**< Slave latency. */
#define CONN_SUP_TIMEOUT MSEC_TO_UNITS(16010, UNIT_10_MS) /**< Connection supervisory time-out
as told by you. still it is giving same issue
but with values as 7.5-100 ms it works fine
Please be specific - which issue do you refer to when you say 'same issue'?
Is it the issue you described in your previous comment, where the buttonpress does not produce the expected logs, or is it the issue you had before with being unable to set the desired connection parameters? The former sounds like an application logic issue, and the latter sounds like a configuration issue.
Could you also elaborate how you verified that the connection interval was actually 1000 and 4000 ms?
Best regards,
Karl
1). 'same issue' : is the issue i described in my previous comment, where the button press does not produce the expected logs when connection interval was 1000.
2). when i had set to 7.5-100ms the current between logs was
556.76 µA
but when connection interval was 1000ms it increased to
685.85 µA
why is the current between logs increasing?
3). i didnt get what is the overflow you meant bcz with 7.5-100ms i am able to get many logs but not with changing interval to 1000ms
Ridhi said:1). 'same issue' : is the issue i described in my previous comment, where the button press does not produce the expected logs when connection interval was 1000.
Thank you for specifying.
Ridhi said:2). when i had set to 7.5-100ms the current between logs was
556.76 µA
but when connection interval was 1000ms it increased to
685.85 µA
why is the current between logs increasing?
It is hard for me to speculate about this without seeing the current code.
However, this might be another symptom of the issue you are seeing with the missing / less-than-expected logging. I suggest that we focus on resolving this issue first, so that we potentially does not spend time debugging a symptom that may go away when we resolve the root issue.
Ridhi said:3). i didnt get what is the overflow you meant bcz with 7.5-100ms i am able to get many logs but not with changing interval to 1000ms
What I meant is that there might be an overflow in your buffers if you change the connection interval from 7.5 ms to 1000 ms unless you have taken specific actions to accommodate for the increase in time between transfers.
For example, if you have a sensor you are reading from every 15 ms, that would mean 1 buffered packet between every other connection event. If you then change to 1000 ms connection interval, you will suddenly buffer 67 packets between each connection event. If the connection interval is the only thing that you have changed, there might be issues with the buffers overflowing when you make this change.
Again, this is just speculations on my part, since I have not actually seen the code in its current state.
Please also see my other previous questions:
Karl Ylvisaker said:Could you also elaborate how you verified that the connection interval was actually 1000 and 4000 ms?
Karl Ylvisaker said:Is there any errors occurring when you use the 1000 ms connection interval? Does the device reset unexpectedly?
Best regards,
Karl