After a lot of struggle with the sources and the documentation we were able to run the sample128 example.
Our android application is able to discover the board but we don't know how to populate app_sample128.c and app_sample128_task.c
要开始使用特性的通知。
Can anyone help us on the matter?
谢谢
Tue, 2014-07-29 20:39
#1
Sample128.
Hi Rony:
Please refer to the following document available under Software tab: UM-B-003: User Manual - Software Development Guide 1.4.pdf
谢谢，
TR_Dialog
这是我们使用的。
在第11章中，我们陷入了困境，而无需了解如何处理特征2的通知。
我们在app_sample128.c和app_sample128_task.c才能实现什么？
使用SDK提供样品128的轮廓。它是一个很好的工具，可以开始理解配置文件。
为什么应用程序不提供源头e?
谢谢
看看app_proxr.cand app_proxr_task.c. Use those to model your application code-you will only need to use certain functions, not all. If you are dealing with timed notifications, it would also help to look at the timer implementation in app_batt.c. If you are using the proximity reporter project, you will need to enable sample128 in app_proxr_proj.c, this is also where you enable the timer.
Looked at the prox and battery examples.
1. In the function that sends SAMPLE128_CREATE_DB_REQ I don't understand what I have to do with the data base.
Prox和电池都填充DB，但我不明白他们正在做什么。
2.同样的问题，用于发送Sample128_enable_req的函数。我看到电池和PROX正在准备我不明白的东西。
我认为文档缺少一个链接，并且不会解释应用程序部件和配置文件之间的连接。
I am sure someone solved the sampleq129 example. Is it possible to get the sources of app_sample128.c and app_sample128_task.c?
谢谢for the effort
Hi Rony,
There is an example in proximity reporter application in SDK 3.0.4
Please refer to spotar_status_update_req_handler() function as an example of sending a notification through a 128 bit UUID characteristic.
Actually notification transmission method is the same for 16 bit and 128 bit UUIDs. After database creation for GATT servers or database discovery for GATT clients all the procedures are the same because the handling is done through handles and not through UUIDs.
谢谢for the advice.
我使用的软件连接到设备可以分析BLE界面。
运行PROX报告器时，它可以正常运行，因为我可以看到电池通知。
But my problems are with the sample128 example.
Following your advice I made some progress. The situation is as follows:
我能够连接到设备。
I see 4 services: Generic Access, Generic Attribute, Device Information and the unrecognized (sample128)
When I select the unrecognized service and display the descriptors I see the 2 characteristics
当我尝试启用特征2的通知时，我收到错误消息：
'The attribute requires authorization before it can be read or written'
Seems that I am not enabling the notification feature of characteristic 2.
What am I doing wrong?
Hi Rony,
几件事......
First off, you may have noticed this already, both Android and iOS are lazy as far as making service discoveries. What I mean by that is that they both store the gatt database of a peripheral the first time they connect. But after that first time, you will not see new services etc. show up. The easy way to force a new discovery is to turn Bluetooth off and then back on. This will wipe out the local gatt database for your peripheral device.
Another issue (and this is probably only related to Android, is that Android has a couple of errors in the android Developer BT Smart reference application, causing all sorts of applications to suffer from the same issue.
I will send you an email with a link to the following:
a）一个不遭受上述问题的Android应用程序
b) A sample128 complete project. It adds a third characteristic, but everything else is identical
I hope this will help you out.
伟大的。this is exactly what I was looking for.
If possible can you make the 3rd characteristic more than one byte long so I see how it is done?
谢谢
罗尼
Hi Rony,
The third characteristic is 8 bytes long. It was implemented to demonstrate just that ;o)
伟大的。
Do you need my e-mail address?
谢谢
Hi Rony,
You should have received my email already. I sent it out on Thursday night PDT to your email address ".net.il". It contains links, so please check your spam folder.
I did get on Thursday an email that included your response and a link back to this forum.
I have experienced some problems lately with my regular e-mail so could you please be so kind and send to my gmail link
谢谢
我刚寄给它链接aginusing you gmail account. I hope you get it this time. After you receive it I recommend that you edit your post to remove your email. You never kbow...
I don't understand it.
不知何故，它没有到达，我甚至没有收到它的通知。
奇怪的。我再次怨恨它。如果您得到它，请告诉我，或者我会尝试找到其他方式来获取您。
Just got it.
谢谢