Specify Port for L2CAP Communication

RE: Specify Port for L2CAP Communication

Ole Morten — Fri, 02 Aug 2013 06:43:38 GMT

I'd be happy if you could accept one of the answers, to clear up the discussion. :-)

RE: Specify Port for L2CAP Communication

Guest — Thu, 01 Aug 2013 15:32:10 GMT

From what ive searched on Qt i believe you are correct. I am going to use standard GATT and android. Much thanks.

RE: Specify Port for L2CAP Communication

Bastiaan — Thu, 01 Aug 2013 15:32:10 GMT

From what ive searched on Qt i believe you are correct. I am going to use standard GATT and android. Much thanks.

RE: Specify Port for L2CAP Communication

Ole Morten — Thu, 01 Aug 2013 10:09:45 GMT

A connection in BLE doesn't really have anything to do with a service, and you can create a connection without actually using any service, just to do L2CAP transfers.

With the S110 there isn't any other way to transfer L2CAP data than what Pål says, by registering a channel with sd_ble_l2cap_cid() and then send data with sd_ble_l2cap_tx().

Unfortunately, we cannot really help you with how to read do this from the other end, through Qt's interfaces, as we don't know them. I'd recommend you to just try to first initiate a connection and only when you're successfully able to do so try to actually receive data.

To be honest, I suspect that this L2CAP API will not be usable for BLE at all. I believe your current best bet to talk to a BLE device on Linux is the C API of BlueZ directly, as stated here.

RE: Specify Port for L2CAP Communication

Nick — Thu, 04 Jul 2013 17:00:14 GMT

Sorry if this question is dumb but im still learning the intricacies of bluetooth. I thought that as a standard L2CAP used Protocol Service Multiplexers which act similar to ports. Would the client/host not need to decide upon a port before they can communicate?

Is it possible to connect to the nRF51822 without connecting through a service?

Thanks,

Nick

RE: Specify Port for L2CAP Communication

Pål Håland — Thu, 04 Jul 2013 05:57:08 GMT

There is one way that you can send data on other L2CAP CID's (as long as they are greater than BLE_L2CAP_CID_DYN_BASE) and you cannot have more than 8 custom CID Channels

uint32_t sd_ble_l2cap_cid_register(uint16_t cid)

uint32_t sd_ble_l2cap_tx ( uint16_t conn_handle,
    ble_l2cap_header_t const *const p_header,
    uint8_t const *const p_data
)

When you send something with sd_ble_l2cap_tx, then you will receive a BLE_EVT_TX_COMPLEPLETE when the packet is received by the peer, and a BLE_L2CAP_EVT_RX when you receive something on that CID from the peer.