MIN_CONN_INTERVAL

RE: MIN_CONN_INTERVAL

sh4k3jkeee — Tue, 23 Sep 2025 11:36:35 GMT

The actual subject is how to represent the required interval enterprisesalesco using the macros given by Nordic in their examples to keep the integrity and compatibility of the code

RE: MIN_CONN_INTERVAL

Tydehodge — Wed, 06 Aug 2025 14:49:26 GMT

fascinating how such a small unit shift like 1.25 ms can impact connection intervals so precisely. reminds me of MapQuest where every turn matters. just like tweaking those values, choosing the right route or resolution can be the difference between a smooth experience and unexpected detours. great insight

RE: MIN_CONN_INTERVAL

Anthony Sanchez — Sat, 11 Jan 2025 05:21:55 GMT

Tabchilli’s sauerkraut seems like a fantastic side for grilled dishes. Has anyone tried it with Middle Eastern kebabs or shawarma?https://tabchilli.com/

RE: MIN_CONN_INTERVAL

Dustin Rhoades — Tue, 10 Dec 2024 13:17:45 GMT

To set the connection interval to 7.5 ms, use the value 6 for MIN_CONN_INTERVAL, as scary teacher 3D BLE intervals are in 1.25 ms units. Ensure your maximum interval (MAX_CONN_INTERVAL) is also correctly configured relative to your requirements.

RE: MIN_CONN_INTERVAL

curlinggeologist — Thu, 07 Sep 2023 07:58:51 GMT

Im using SDK 15 ble pheripheral and central uart example on my custom nrf52832 board.

I would like to know how to set MIN_CONN_INTERVAL and MAX_CONN_INTERVAL for connection when im sending 20bytes

in frame every 8ms using timer for 60 seconds continously. How to calculate it? dinosaur game

RE: MIN_CONN_INTERVAL

victorpatrick — Wed, 19 Jul 2023 09:57:39 GMT

Please note that the actual connection interval used may not exactly match the desired value, as it also depends on the capabilities of the Bluetooth radio and the negotiated parameters during the connection setup process. However, setting the minimum connection interval as shown above should ensure that the connection interval is close to 7.5 ms. Bitlife

RE: MIN_CONN_INTERVAL

pretzelrhetorical — Tue, 18 Jul 2023 13:47:42 GMT

The MIN_CONN_INTERVAL macro typically supports integer values only, as you mentioned. However, some Bluetooth modules may support more precise connection intervals. You can refer to the documentation for your specific module or consult with the manufacturer to determine if more precise connection intervals are possible.

dumb ways to die

RE: MIN_CONN_INTERVAL

xonoy18882 — Tue, 11 Jul 2023 14:33:03 GMT

[deleted]

RE: MIN_CONN_INTERVAL

davidlorker — Wed, 23 Nov 2022 04:49:48 GMT

Thank you for giving this insightful knowledge. Your webpage is very good. It's amazing how much information there on your website.

snake io

RE: MIN_CONN_INTERVAL

Baruch — Mon, 20 Aug 2018 14:22:00 GMT

I have. It seems to be fine but yet it is not obvious and compiler/preprocessor dependant which is wrong especially for example.

RE: MIN_CONN_INTERVAL

Bartek — Mon, 20 Aug 2018 14:09:47 GMT

Why do you think it only supports integer?

It works fine for me as long as time can be converted to units that are encoded as integer. Give a try passing 7.5 to macro and see that it will work.

RE: MIN_CONN_INTERVAL

Baruch — Mon, 20 Aug 2018 13:58:17 GMT

I'd prefer to have a macro which indeed takes everything. I do agree that 1.25 isn't going to change then using units of ms in the given macro doesn't make much sense and that is the whole reason for my complaint.

RE: MIN_CONN_INTERVAL

howard n2wx — Mon, 20 Aug 2018 13:35:18 GMT

I think it's a good catch because the 1.25mS unit defined in the spec is not likely to change. OTOH there is the issue of the units being obscured by the preproc macro. Would you prefer to pass a floating (or fixed point) interval to a wrapper?

RE: MIN_CONN_INTERVAL

Baruch — Mon, 20 Aug 2018 01:47:55 GMT

Howard, why do you think it is a good catch? I'm not following.

RE: MIN_CONN_INTERVAL

howard n2wx — Mon, 13 Aug 2018 13:13:23 GMT

Interesting. I suppose it's unlikely the units will change then, absent a core spec update. Good catch.

RE: MIN_CONN_INTERVAL

Baruch — Mon, 13 Aug 2018 12:53:50 GMT

Thank you, but this is well-known information. The actual subject is how to represent the required interval using the macros given by Nordic in their examples to keep the integrity and compatibility of the code. It isn't the question of a value but about proper representation.

RE: MIN_CONN_INTERVAL

Kenneth — Mon, 13 Aug 2018 12:24:10 GMT

The format here follow the BT core spec:

RE: MIN_CONN_INTERVAL

howard n2wx — Fri, 10 Aug 2018 19:25:12 GMT

The units could change in the next release. I agree with you.

EDIT Units unlikely to change though, per Kenneth below

RE: MIN_CONN_INTERVAL

Baruch — Fri, 10 Aug 2018 19:15:16 GMT

main.c

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(20, UNIT_1_25_MS) /**< Minimum acceptable connection interval (20 ms), Connection interval uses 1.25 ms units. */

app_util.h

/**@brief Macro for converting milliseconds to ticks.
*
* @param[in] TIME Number of milliseconds to convert.
* @param[in] RESOLUTION Unit to be converted to in [us/ticks].
*/
#define MSEC_TO_UNITS(TIME, RESOLUTION) (((TIME) * 1000) / (RESOLUTION))

enum
{
UNIT_0_625_MS = 625, /**< Number of microseconds in 0.625 milliseconds. */
UNIT_1_25_MS = 1250, /**< Number of microseconds in 1.25 milliseconds. */
UNIT_10_MS = 10000 /**< Number of microseconds in 10 milliseconds. */
};

So, even though that value 6 does work substituting breaks the integrity of the code. That is the major reason for my question.

RE: MIN_CONN_INTERVAL

howard n2wx — Fri, 10 Aug 2018 18:43:27 GMT

Hi Baruch,

Fortunately MIN_CONN_INTERVAL is specified in 1.25ms units, at least for SDK15, and the integer 6 will yield the desired 7.5ms. See ble_gap.h

Best Regards, Howard