why indication callback not called

RE: why indication callback not called

Wojtek — Thu, 11 Feb 2016 10:55:36 GMT

I don't think this is wise way to send many indications. Do you want to have high throughput? If not, maybe call that ble_digitsole_param_update() periodically (app_timer?) OR just only after receiving HVC- that will save you some power because cpu can sleep more. If you want to have high throughput, I would go back to using notifications and just wait for TX_COMPLETE events to fill all available buffers.

RE: why indication callback not called

makouda — Thu, 11 Feb 2016 10:42:53 GMT

i used this code to bypass the problem. do you think it's wise way? can this generate any issue by putting app_sched_execute many times on the main lopp

				indication_pending = true;
				do {
					err_code = ble_digitsole_param_update(&m_digitsole, FLASH_DATA, NULL, steps_store_characteristic_value);//update data on BLE
					app_sched_execute();
				} while (indication_pending);

RE: why indication callback not called

makouda — Thu, 11 Feb 2016 10:25:29 GMT

so for my understanding :

indication_pending = true;
do {
		err_code = ble_digitsole_param_update(&m_digitsole, FLASH_DATA, NULL, steps_store_characteristic_value);//update data on BLE
	} while (indication_pending);

this code executed on the main loop would never run because ndication_pending flag is cleared on BLE_GATTS_EVT_HVC callback which cannot be run before app_sched_execute is called. but it working anyway, I can see many packet are sent to phone

RE: why indication callback not called

Wojtek — Thu, 11 Feb 2016 10:16:07 GMT

If you are using scheduler, you have to manually poll for events from it. If you are waiting in while loop, no events will be pulled from softdevice! (they are received by interrupt, but queued by scheduler - not propagated in application. You have to manually take them from there by app_sched_execute();)

RE: why indication callback not called

makouda — Thu, 11 Feb 2016 10:11:37 GMT

im using scheduler . my inidcation is blocking on the main loop. sometimes it works fine, but then I receive error 8 (0x8) : GATT CONN TIMEOUT on nrf master control log and the connection is lost

RE: why indication callback not called

Wojtek — Thu, 11 Feb 2016 10:05:58 GMT

I was wrong indeed. I am using scheduler and I automatically assume everyone is using it :)

RE: why indication callback not called

Susheel Nuguru — Thu, 11 Feb 2016 09:17:19 GMT

any chances of sending me your project? I will come back to you in couple of hours.

RE: why indication callback not called

makouda — Thu, 11 Feb 2016 09:15:51 GMT

im using nrf51822, Softdevice 8.0. SDK 10. nrf Master Control (android on samsung)

RE: why indication callback not called

Susheel Nuguru — Thu, 11 Feb 2016 09:14:23 GMT

strange, which softdevice, sdk, peer OS versions are you using, i can run a quick test after lunch to see if it has any problems!!!

RE: why indication callback not called

makouda — Thu, 11 Feb 2016 08:55:28 GMT

yes the indications are enabled from peer side. and im waiting on main loop. but the indication callback in never called

RE: why indication callback not called

Susheel Nuguru — Thu, 11 Feb 2016 08:54:19 GMT

Have those indications enabled from the peer side? Waiting in a while loop inside main is not a problem. Main is running in thread 4 priority which is the lowest, so it cannot blocks stack events.

RE: why indication callback not called

makouda — Wed, 10 Feb 2016 20:39:51 GMT

but how can the indication block indefinitely ???? I thought that after a period of time the data would be finally sent and indication callback is called ???. also BLE handlers can interrupt main loop programs???

RE: why indication callback not called

Wojtek — Wed, 10 Feb 2016 18:07:54 GMT

Ok, now i see what is the problem. You canot wait in while loop cause it is blocking the cpu (you don't pull events from the stack).

I am not sure what is the flow of your program, but You may try something like that:

if(!indication_pending)
{
	err_code = param_update(&m_param, FLASH_DATA, NULL, steps_store_characteristic_value);
	if (err_code == NRF_SUCCESS)
		indication_pending = true;
}

and call it periodically.

RE: why indication callback not called

makouda — Wed, 10 Feb 2016 17:58:12 GMT

im uisng nrf master control on mobile phone (samsung)

RE: why indication callback not called

Wojtek — Wed, 10 Feb 2016 17:41:47 GMT

what device are you using to receive the data? Mobile phone or central on S120/S130?