Hi all,
I'd like to change the connection interval dynamically at runtime. Most of the time, the interval is long in order to save power, when a certain characteristic is written it needs to be short so the latency of the total system (smartphone app + BLE device) is much smaller.
I already found out that the GAPC_PARAM_UPDATE_CMD command can be issued to negotiate a new connection interval with the master. This works quite well, but I still have a problem.
Hi,
I use Murata module Type ZY (DA14580) daughter board with P2ML3078 evaluation board.
I connected the evaluation board to STM32L152 discovery evaluation board.
I use SPI (from STM as master) to load the code to the device, and use USART for communication with the device.
hi dialog
1、Use our "template" project[DA14580_581_583_SDK_3.0.10.1]
2、I use P0_4 connect to T_RxD, and P0_7 connect to T_TxD
3. my I modified as following:
@fileda14580_config.h
====================================
/*UART Console Print*/
#define CFG_PRINTF
#ifdef CFG_PRINTF
#define CFG_PRINTF_UART2
#endif
====================================
I'm using the device as a server connecting to it via a PC. I am able to write to the device characteristic values that are longer than 20 bytes. The characteristic value arrives in pieces with 'param->last' being true with the last piece. That is working fine.
When the device wants to write a value into its database (with notification) I can write more than 20 bytes but the PC side only appears to receive 20 and I'm not really sure where the problem lies. Here is the device code that responds to the 'update_req_handler:
Hi.
I need to respond with ok/error to Queued Writes (Write Long Characteristic Values).
Hi, I am trying to download the tools smart snippets and connection manager but cannot find any link that works. Are the software tools already included in SDK if so then provide the instructions on how to install them.
We are using the ADC to measure P0.0, P0.2, P0.3 and the 3v battery.
For the battery we are initializing the adc to 3x attenuation and for the rest initializing without the attenuation.
Our measurements are not consistent and I am afraid that our timing is not correct.
So please tell me:
1.我应该等待adc_init之间多少时间adc_enable_channel?
2. How much time to wait between adc_enable_channel to adc_get_sample?
3. Do I have to call adc_disable?
Thanks
Not sure what to do about the following situation:
Dialog is running fine connected to the app.
当我们远离传感器和芯片RSSI changes as expected.
Suddenly it seems that the dialog disconnects and the only way we can connect again is by restarting the device.
We could send a disconnect message to the chip from the app when the RSI level is too low and tell the user to get closer, but is there a more elegant solution?
Thanks
hi dialog
I found the following a header file is not used (# include "wkupct_quadec. H"), Whether it is right.
我发现下面的一个头文件未使用(#include "wkupct_quadec.h")，确认一下。
[DA14580_581_583_SDK_3.0.10.1]
@file app_proxr.c
/*
* INCLUDE FILES
****************************************************************************************
*/
#include "rwble_config.h"
#if (BLE_APP_PRESENT)
#if (BLE_PROX_REPORTER)
Hi DA team,
Regard to your DSPS reference design, I am having a question that Does Arm processor stop when DA go to Extended sleep mode? I have already look at main function but I can not find out where you have halted the Arm processor in source code. Another question that Where does BLE timer place? Is it belong to software timer or wakeup timer? In DA datasheet, I did not see anything talk about this timer.
Thanks,
Chung Tran.
