Re: Bluetooth-dev Digest, Vol 12, Issue 21
Re: Bluetooth-dev Digest, Vol 12, Issue 21
- Subject: Re: Bluetooth-dev Digest, Vol 12, Issue 21
- From: Justin Cooper <email@hidden>
- Date: Mon, 16 Mar 2015 11:06:33 -0500
We used this bluetooth low energy packet sniffer from TI:
I was able to confirm that there was actually no BLE traffic at the time, leading me to believe that the initial "didConnectPeripheral" is false and does not correspond to BLE traffic on the radio.
For my application, we keep track of what state we are in. So, I added some code that looks like:
public func centralManager(central: CBCentralManager!, didDisconnectPeripheral peripheral: CBPeripheral!, error: NSError!) {
// Sometimes the other end drops the connection while we are in .Connected (but not yet .ConnectedPiped)
// we can do this over and over since there is a connect timeout watching.
if(.Connected == state) {
self.central.connectPeripheral(peripheral, options: nil)
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (
email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to
email@hidden _______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden