Characteristic Larger Than 20 Bytes & and Updating S110

[Lucas]

Hello,

I've been looking at this post devzone.nordicsemi.com/.../ in regards to characteristic lengths.

I'm still not clear on the matter. Currently I have initialized a characteristic to send 500bytes. The system is running, but when I try to look at the data using the Master Control Panel only 20 bytes are received. How would I go about getting all 500 bytes to send?

Also, when migrating from one version of S110 to another I assume that all new header files should be copied over into the include path where the project is linked too. Other than flashing s110, updating code accordingly, and replacing header files is there any additional things that need to be done?

Lucas

[Lucas]

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.