BASIC DA14580

Quadrature Decoder as pulse counter?

Sat, 2017-06-17 17:11--Max44

Hello Dialog Support,

I have an application that needs to implement a pulse counter on an input from a sensor. I saw that the question of possibly using the quadrature decoder for this came up in the forum a while ago but it wasn't answered. Could the quadrature decoder be used to count low frequency pulses? The plan would be to poll periodically to calculate event rates reported by the sensor.

Buffered ADC samples, transmit on app request.,

Tue, 2017-04-18 01:32--ksrgopinath

Dear Support,

I am working on DA14580 Basic kit.SO far I have been working on the ble_app_perpheral project. I was able to send ADC data on request from light-blue IOS app.
We have a requirement for setting up a timer to take adc value for every 5 min and storing in a buffer of fixed length 12. The The idea is at every given point of time we will have ADC samples for last 60 min spread at 5 min interval.

DA14580蓝牙传输率能达到32kbit/s吗?

Wed, 2017-03-08 06:55--tanyong1126

我正在设计一款可穿戴式产品,贴在胸脯上测心电图数据,传感器输出数据速度为32kbit/s,如果需要DA14580蓝牙实时将这些数据上传给手机,可以来得及吗?我听说蓝牙4.0芯片速度不够高,理论上可以达到1Mbit/s,但是实际使用时达不到这个速度。如果不行的话,能推荐一款芯片吗?比如蓝牙4.2版本的芯片,da14680可以吗?

Extended Sleep Mode Debugging

Tue, 2016-04-05 00:34--joe.brackman

Hello. I'm working with a project that is a derivative of the DSPS project (the older version 3.150.2 was our starting point). We have the application working on both the Dialog Basic board and our custom target board.

For our debugging and development thus far, we've had sleep disabled (both EXT and DEEP) in da14580_config.h.

Now we would like to enable sleep in order to save power. However, when I do enable sleep (#define CFG_EXT_SLEEP), I can't see my Dialog peripheral via Light Blue (iPhone), whereas with no sleep, I see my peripheral just fine.

Debug vs Boot from EEPROM running differently

星期五,2015-05-01 05:02--JBaczuk

I've got a script that is working but only in debug mode. When I use Keil in debug mode, it works fine, but when I use SmartSnippets to burn the firmware to the EEPROM, it loads and then runs normally until a certain point in the script, it gets stuck. I think the HEX file that it loads in debug mode must be different from the HEX that is loaded to the EEPROM, but I don't know for sure. It may be optimizing out some of my code, for example, I have an arbitrary delay (just for testing). This is the while loop it gets stuck at the 3rd line:

Pages

订阅RSS -基本DA14580