nRF51-DK Connection Event Packet Length

RE: nRF51-DK Connection Event Packet Length

Stefan Birnir Sverrisson — Mon, 02 Feb 2015 08:32:24 GMT

Hi Robert

I suspect that you are only receiving one byte per connection event because the above parameters are set to only send one byte per connection event. What happens if you put

attr.max_len   = 8;

attr.init_len  = 8;

attr_md.vlen = 1;

RE: nRF51-DK Connection Event Packet Length

Robert — Fri, 30 Jan 2015 13:19:09 GMT

I am receiving the correct data. What I am asking is how do I change the events so that variable bytes can be the payload of the packet. I still receive all the correct data, but the waveform for the current shows 8 separate connection events to send 8 bytes. Is it possible to send 1 connection event with 8 byte data payload instead of requiring a new connection event with a new header and a new 1 byte payload? I want to see if there is a difference in current between a connection event header and footer with a payload of 1 byte vs a connection event header and footer with a payload of 8 bytes and so on.

RE: nRF51-DK Connection Event Packet Length

Stefan Birnir Sverrisson — Fri, 30 Jan 2015 10:38:52 GMT

Hi Robert

The radio transmits BLE packets with 1Mbps. This means that transmitting 8 payload bytes should take 8*8=64 microseconds. If you can not see any difference when sending 1 byte and when sending 8 bytes, you may want to check if you have the correct settings for your notifying characteristic. Look at this thread to see what is needed.

I think you need to look at the three following properties in the services_init function:

attr.max_len   = 1;

attr.init_len  = sizeof(multilink_peripheral_data);

attr_md.vlen = 0;

which define the maximum size for the characteristic, initial length, and if the characteristic should have variable length or not. When you have changed that, you should be able to send data larger than one byte.

When you connect with a central device (e.g. Master Control Panel) how many bytes do you see transmitted to the notify characteristic?