RE: Advertisement packet too long

CodyTheHun — Tue, 28 Apr 2015 09:51:58 GMT

Thanks, I changed my packet to only advertise the main service, and the rest can be discovered after connecting.

RE: Advertisement packet too long

kerem — Sun, 26 Apr 2015 21:27:48 GMT

I don't think you're supposed to broadcast all characteristics in a BLE packet nor try to fit them in. You should only broadcast what's really needed, depending on your packet type. It's probably only one UUID, maybe some major and minor values along with rssi is what you need to broadcast only, say if you're trying to broadcast an ibeacon packet. Characteristics and services are values that should be read/written after bonding to the peripheral, one at a time. (The limit was 20 bytes per write operation if I'm not wrong).

You should check your packet length by accounting for the fields, what you put in it, see Ole's answer here. Your advertising packet cannot exceed 31 bytes. There is probably something wrong at the part you're building it or you're confused about what you should advertise. Please share that snippet so we can comment on it, instead of assuming.

A BLE packet being broadcasted over the air is actually 47 bytes in total, but actual payload information you can put in it is limited by the packet's structure;

1 byte preamble
4 byte access address
2-39 bytes advertising channel PDU
2 bytes (size and type of payload)
37 bytes payload

37 = 6 bytes (mac address) + 31 bytes (data from your services, characteristics etc., not the service itself)

3 bytes CRC

In addition to checking how you build up your fields, you can also sniff your packets and see what's really in them. If one packet is not enough you can always use the scan response data for an additional 31 bytes.