RE: Characteristic Larger Than 20 Bytes & and Updating S110

brianreinhold — Wed, 20 May 2020 20:36:24 GMT

I can understand ... I have a characteristic of 22 bytes in the nrf5840. Peers can't read it unless it is 20 bytes or less. No info in how to set up a 'blob' read. Peer has no problem reading other devices with long characteristics.

RE: Characteristic Larger Than 20 Bytes & and Updating S110

Lucas — Wed, 16 Jul 2014 21:20:14 GMT

I want to become vulgar

RE: Characteristic Larger Than 20 Bytes & and Updating S110

Lucas — Tue, 08 Jul 2014 19:50:03 GMT

I am starting to get a better picture of this problem, but will require additional information for full understanding. I was under the impression that sending a payload of ~500 bytes would help with throughput.

For more information: devzone.nordicsemi.com/.../

Our target application is iphone 5. So the max throughput is 4KB see above link.

What is the best way to achieve this data rate? Set connection interval at 30ms and have a single charactersistic that is 6*20 = 120B? Then have the GATT client (phone) issue a long read command to the GATT server (nrf51822)?

What happens if the peripheral device updates its GATT server characteristic before a read command from the GATT client comes? My assumption has always been that the old data is lost. Is the long read a solution to get more throughput out of one characteristic.