没能读和写长期发展ristic value with same UUID

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
2 posts / 0 new
Last post
divyesh
Offline
Last seen:2 months 1 week ago
加入:2020-04-20 13:19
没能读和写长期发展ristic value with same UUID

Hi,

I am working on Reading and Writing Characteristics value using the same UUID. Here, I am facing some issues. Whenever I am using different UUIDs for reading and writing, at that time it is working fine. I am trying to access read and write together with the same UUID at that time fails. I am doing the following action inuser_custs1_def.cfile.

/* Long Value Characteristic Value */
[SVC1_IDX_LONG_VALUE_VAL] = {SVC1_LONG_VALUE_UUID_128, ATT_UUID_128_LEN, PERM(RD, ENABLE) | PERM(WR, ENABLE) | PERM(NTF, ENABLE) | PERM(WRITE_REQ, ENABLE),
DEF_SVC1_LONG_VALUE_CHAR_LEN, 0, NULL},

Here, in above configuration, only write characteristics value I can able to do, not read characteristics. So, I modify above syntax and add"PERM(RI, ENABLE)".

At this Point, Only read characteristics are working fine, not to write characteristics value. so, anyone can help me for this issue. I want both read and write characteristics with the same UUID.

How can I achieve both read and write characteristics with same UUID?

Thanks in Advance.

Regards,

Divyesh

Device:
PM_Dialog
Offline
Last seen:2 days 22 hours ago
工作人员
加入:2018-02-08 11:03
Hi divyesh,

Hi divyesh,

Could you please clarify what you are trying to accomplish? What do you mean with “read and write at the same time” ? The Long value characteristic has both read and write permissions. As soon as the characteristic is written, the you should be able to read the written value. The RI (Read Indicated) feature let the ATT layer know that there is no data in the database and read the data directly from the user application layer.

Thanks, PM_Dialog