Comments (7)
What's more likely is that the phone app is using a very short connection-interval; and so causing the device to use its radio far too often. Trying changing the connection parameters.
Take a look at:
http://developer.mbed.org/forum/team-63-Bluetooth-Low-Energy-community/topic/5210/
[from the above reference]:
Users may also experiment with reducing the transmit power of their radio; there's an API for this. Connection intervals and connection latency are also available for modification, and play a very important role in power consumption.
from ble.
Yes, I know about that but that's not a problem in this case.
I tried to change connection parameters like this:
/* mbed Microcontroller Library
* Copyright (c) 2006-2013 ARM Limited
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
#include "mbed.h"
#include "BLEDevice.h"
#include "HeartRateService.h"
#include "BatteryService.h"
#include "DeviceInformationService.h"
#include "app_timer.h"
#define MIN_CONN_INTERVAL MSEC_TO_UNITS(379, UNIT_1_25_MS) /**< Minimum connection interval (379 ms) */
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(399, UNIT_1_25_MS) /**< Maximum connection interval (399 ms). */
#define SLAVE_LATENCY 4 /**< Slave latency. */
#define CONN_SUP_TIMEOUT MSEC_TO_UNITS(6000, UNIT_10_MS) /**< Connection supervisory timeout (6 seconds). */
BLEDevice ble;
const static char DEVICE_NAME[] = "Nordic_HRM";
static const uint16_t uuid16_list[] = {GattService::UUID_HEART_RATE_SERVICE,
GattService::UUID_BATTERY_SERVICE,
GattService::UUID_DEVICE_INFORMATION_SERVICE};
static volatile bool triggerSensorPolling = false;
void disconnectionCallback(Gap::Handle_t handle, Gap::DisconnectionReason_t reason)
{
ble.startAdvertising(); // restart advertising
}
void periodicCallback(void)
{
/* Note that the periodicCallback() executes in interrupt context, so it is safer to do
* heavy-weight sensor polling from the main thread. */
triggerSensorPolling = true;
}
int main(void)
{
Gap::ConnectionParams_t gap_conn_params;
Ticker ticker;
ticker.attach(periodicCallback, 1);
ble.init();
ble.onDisconnection(disconnectionCallback);
/* Setup primary service. */
uint8_t hrmCounter = 100;
HeartRateService hrService(ble, hrmCounter, HeartRateService::LOCATION_FINGER);
/* Setup auxiliary services. */
BatteryService battery(ble);
DeviceInformationService deviceInfo(ble, "ARM", "Model1", "SN1", "hw-rev1", "fw-rev1", "soft-rev1");
// Set desired connection parameters
gap_conn_params.minConnectionInterval = MIN_CONN_INTERVAL;
gap_conn_params.maxConnectionInterval = MAX_CONN_INTERVAL;
gap_conn_params.slaveLatency = SLAVE_LATENCY;
gap_conn_params.connectionSupervisionTimeout = CONN_SUP_TIMEOUT;
ble.setPreferredConnectionParams(&gap_conn_params);
/* Setup advertising. */
ble.accumulateAdvertisingPayload(GapAdvertisingData::BREDR_NOT_SUPPORTED | GapAdvertisingData::LE_GENERAL_DISCOVERABLE);
ble.accumulateAdvertisingPayload(GapAdvertisingData::COMPLETE_LIST_16BIT_SERVICE_IDS, (uint8_t *)uuid16_list, sizeof(uuid16_list));
ble.accumulateAdvertisingPayload(GapAdvertisingData::GENERIC_HEART_RATE_SENSOR);
ble.accumulateAdvertisingPayload(GapAdvertisingData::COMPLETE_LOCAL_NAME, (uint8_t *)DEVICE_NAME, sizeof(DEVICE_NAME));
ble.setAdvertisingType(GapAdvertisingParams::ADV_CONNECTABLE_UNDIRECTED);
ble.setAdvertisingInterval(1600); /* 1000ms; in multiples of 0.625ms. */
ble.startAdvertising();
while (true) {
if (triggerSensorPolling) {
triggerSensorPolling = false;
/* Do blocking calls or whatever is necessary for sensor polling. */
/* In our case, we simply update the dummy HRM measurement. */
hrmCounter++;
if (hrmCounter == 175) {
hrmCounter = 100;
}
hrService.updateHeartRate(hrmCounter);
} else {
ble.waitForEvent();
}
}
}
But it's still the same.
Transmit power is not the problem either.
I measured the current consumption of my device with application created using Nordic SDK and the same connection parameters and TX power and there is no such high current consumption, consumption is 5uA in low-power mode with small current spikes in connection events.
from ble.
Please try using the following API once a connection is made in order to request the central to update the settings:
BLEDevice::updateConnectionParams(Gap::Handle_t handle, const Gap::ConnectionParams_t *params)
It is ultimately up to the central/master to choose the connection parameters. Your requested settings may not be honored.
Please take notice of the following comment from ble_gap.h (under nrf-sdk/s110) and also pay attention to the constraint mentioned mentioned at the end:
/**@brief Update connection parameters.
*
* @details In the central role this will initiate a Link Layer connection parameter update procedure,
* otherwise in the peripheral role, this will send the corresponding L2CAP request and wait for
* the central to perform the procedure. In both cases, and regardless of success or failure, the application
* will be informed of the result with a @ref BLE_GAP_EVT_CONN_PARAM_UPDATE event.
*
* @note If both a connection supervision timeout and a maximum connection interval are specified, then the following constraint
* applies: (conn_sup_timeout * 8) >= (max_conn_interval * (slave_latency + 1))
...
I can see that your particular choice of sup_timeout will not be enough to support your slave latency and connection interval values.
from ble.
Please also consider using a BLE sniffer to determine the actual connection interval in effect.
I will try to do this next week for your code.
from ble.
Yes, that was a problem with connection parameters, they need to be updated when you connect to the device.
As for the choice of connection parameters, I chose them based on iOS limits:
https://developer.apple.com/hardwaredrivers/bluetoothdesignguidelines.pdf page 22 "3.6 Connection Parameters"
Thanks for your help!
from ble.
For the benefit of other users, could you please post your new connection settings and the power consumption numbers? Thanks.
from ble.
It's 4uA in low-power mode (in ble.waitForEvent() state) for advertising and connected state with current consumption spikes when device send/receive packets.
This spikes when device send/receive advertising packets it consumes 2-3 times more than when in connected state as it should be.
I have only multimeter on hands for now so I can't say any more useful values, but I'll try to make voltage amplifier for shunt and measure current consumption profile with oscilloscope next week and then check if there is any excessive current consumption compared to estimated values based on datasheet.
Here is test code with updateConnectionParams():
/* mbed Microcontroller Library
* Copyright (c) 2006-2013 ARM Limited
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
#include "mbed.h"
#include "BLEDevice.h"
#include "HeartRateService.h"
#include "BatteryService.h"
#include "DeviceInformationService.h"
#include "app_timer.h"
#define MIN_CONN_INTERVAL MSEC_TO_UNITS(379, UNIT_1_25_MS) /**< Minimum connection interval (379 ms) */
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(399, UNIT_1_25_MS) /**< Maximum connection interval (399 ms). */
#define SLAVE_LATENCY 4 /**< Slave latency. */
#define CONN_SUP_TIMEOUT MSEC_TO_UNITS(6000, UNIT_10_MS) /**< Connection supervisory timeout (6 seconds). */
BLEDevice ble;
const static char DEVICE_NAME[] = "Nordic_HRM";
static const uint16_t uuid16_list[] = {GattService::UUID_HEART_RATE_SERVICE,
GattService::UUID_BATTERY_SERVICE,
GattService::UUID_DEVICE_INFORMATION_SERVICE};
static volatile bool triggerSensorPolling = false;
void disconnectionCallback(Gap::Handle_t handle, Gap::DisconnectionReason_t reason)
{
ble.startAdvertising(); // restart advertising
}
void onConnectionCallback(Gap::Handle_t handle, const Gap::ConnectionParams_t *p_conn_param)
{
Gap::ConnectionParams_t gap_conn_params;
gap_conn_params.minConnectionInterval = MIN_CONN_INTERVAL;
gap_conn_params.maxConnectionInterval = MAX_CONN_INTERVAL;
gap_conn_params.slaveLatency = SLAVE_LATENCY;
gap_conn_params.connectionSupervisionTimeout = CONN_SUP_TIMEOUT;
ble.updateConnectionParams(handle, &gap_conn_params);
}
void periodicCallback(void)
{
/* Note that the periodicCallback() executes in interrupt context, so it is safer to do
* heavy-weight sensor polling from the main thread. */
triggerSensorPolling = true;
}
int main(void)
{
Gap::ConnectionParams_t gap_conn_params;
Ticker ticker;
ticker.attach(periodicCallback, 1);
ble.init();
ble.onDisconnection(disconnectionCallback);
ble.onConnection(onConnectionCallback);
/* Setup primary service. */
uint8_t hrmCounter = 100;
HeartRateService hrService(ble, hrmCounter, HeartRateService::LOCATION_FINGER);
/* Setup auxiliary services. */
BatteryService battery(ble);
DeviceInformationService deviceInfo(ble, "ARM", "Model1", "SN1", "hw-rev1", "fw-rev1", "soft-rev1");
// Set desired connection parameters
gap_conn_params.minConnectionInterval = MIN_CONN_INTERVAL;
gap_conn_params.maxConnectionInterval = MAX_CONN_INTERVAL;
gap_conn_params.slaveLatency = SLAVE_LATENCY;
gap_conn_params.connectionSupervisionTimeout = CONN_SUP_TIMEOUT;
ble.setPreferredConnectionParams(&gap_conn_params);
/* Setup advertising. */
ble.accumulateAdvertisingPayload(GapAdvertisingData::BREDR_NOT_SUPPORTED | GapAdvertisingData::LE_GENERAL_DISCOVERABLE);
ble.accumulateAdvertisingPayload(GapAdvertisingData::COMPLETE_LIST_16BIT_SERVICE_IDS, (uint8_t *)uuid16_list, sizeof(uuid16_list));
ble.accumulateAdvertisingPayload(GapAdvertisingData::GENERIC_HEART_RATE_SENSOR);
ble.accumulateAdvertisingPayload(GapAdvertisingData::COMPLETE_LOCAL_NAME, (uint8_t *)DEVICE_NAME, sizeof(DEVICE_NAME));
ble.setAdvertisingType(GapAdvertisingParams::ADV_CONNECTABLE_UNDIRECTED);
ble.setAdvertisingInterval(4096);//1600); /* 1000ms; in multiples of 0.625ms. */
ble.startAdvertising();
while (true) {
if (triggerSensorPolling) {
triggerSensorPolling = false;
/* Do blocking calls or whatever is necessary for sensor polling. */
/* In our case, we simply update the dummy HRM measurement. */
hrmCounter++;
if (hrmCounter == 175) {
hrmCounter = 100;
}
hrService.updateHeartRate(hrmCounter);
} else {
ble.waitForEvent();
}
}
}
from ble.
Related Issues (20)
- AdvertisementCallbackParams_t should include addressType for the peerAddr HOT 3
- GapState_t missing information? HOT 2
- GapAdvertisingData using deprecated type aliases HOT 1
- Time unit inconsistencies in GapScanningParams HOT 1
- Duplicated functionality in GapAdvertisingParams and GapScanningParams HOT 1
- BLE.h conflict with Nordic SDK ble.h HOT 5
- Using ANCS HOT 3
- Add error handling to GattClient procedures HOT 3
- Will we support BLE profiles? HOT 2
- "connection parameters update request" CALLBACK IS MISSING FROM MBED STACK HOT 12
- Possible Ticker BLE_API conflict causing problems with Nordic devices? HOT 7
- Link to documentation from README is broken
- NRF_52 Development Kit notification events don't fire on the central, when peripheral data changes HOT 24
- Linker error when using the Nordics Experimental Flash Data Storage API's. HOT 1
- NRF5: Byte order of characteristics with multi-byte data types incorrect HOT 4
- please implement missing key features HOT 1
- X-Nucleo-IDB05A1 Not Working HOT 4
- Can I control the channel the device is advertising on with this API?
- How to call BLE APIs from the board to host side using icetea?
- #include "mbed.h" where is it??? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ble.