core-bluetooth

问题 I have created a bluetooth peripheral manager. I am adding some services to this peripheral manager using [self.peripheralManager addService:myService]. For iOS7.0 I am getting a callback for this method - (void)peripheralManager:(CBPeripheralManager *)peripheral didAddService:(CBService *)service error:(NSError *)error But for iOS8.0 I am not getting any callback for the same method and I am not able to establish a connection. Here are the steps that I followed: Create a peripheral manager

问题 I have created a bluetooth peripheral manager. I am adding some services to this peripheral manager using [self.peripheralManager addService:myService]. For iOS7.0 I am getting a callback for this method - (void)peripheralManager:(CBPeripheralManager *)peripheral didAddService:(CBService *)service error:(NSError *)error But for iOS8.0 I am not getting any callback for the same method and I am not able to establish a connection. Here are the steps that I followed: Create a peripheral manager

问题 Is there a recommended way for CBPeripheralManager to terminate a connection. The best way I have found so far is simply not to respond to dynamic value, then the BLE stack seems to close the connection, but that seems rather crude. There must be a better way? 回答1: No, you can't forcefully close a connection in a clear way from the peripheral side. There is no API for it. You can break the connection abruptly by not responding to a request, which results in disconnection at most after 30

问题 I'm going to break down what the flow for connection is for the first time a user wants to connect to a BLE Peripheral Device. I think I may be doing something that upsets the natural flow of the CoreBluetooth Module. My app currently works with regards to connecting and sending commands to a BLE device. To connect, I first land on a page with a tableview which displays the devices available to connect to. override func viewDidLoad() { super.viewDidLoad() //self.centralManager =

问题 What is the Difference between BGAPI and BGScript ? And if we write any code for BG profile than how can we burn it in BLE 112? 回答1: The BGAPI interface defines the protocol used to talk to the module over USB or serial link. BGScript is something which runs on the module processor itself, when the USB or serial link is not used. I have the dongle, BLED112, which is the same thing as BLE112 with a USB connector on it, and the code is "burned" to it using standard USB DFU interface. The

问题 I have an iOS app that scans for BLE peripherals, of which there may be many, and allows the user to decide whether or not to connect to the device. Once connected, the user can also decide to break the connection. All of this works fine. I would also like to add an option to allow the user to change their mind and rescan for a device, but this seems to be problematic. The most obvious way to do this seems to be to stop scanning and restart it, as in: [centralManager stopScan]; CBUUID

问题 I am developing for BLE in objective-C. I define the UUID like the following code: static NSString *const LEDStateCharacteristicUUID = @"ffffffff-7777-7uj7-a111-d631d00173f4"; I want to write characteristic to BLE device by following code , it need to pass 3 parameter:1.Data 2.Characteristic 3.type CBCharacteristic *chara = ??? // how to set the characteristic via above UUID let it can pass to following function? [peripheral writeValue:data forCharacteristic:chara type

问题 Currently, iOS does not support the combination GAP Central role and ATT Server role as well as the combination GAP Peripheral role and ATT Client role. Is Apple working on this? Does someone know when it will be possible to do so ? 回答1: If you develop a non iOS peripheral, then you should be able to start acting as ATT client once the iOS central connected to you. The ATT database is shared accross applications and should be accessible this way. You can initialize it in a separate app or in

问题 I am using corebluetooh api to send data to Bluetooth device . on android its working fine but on ios its not working. I am sending data as follows public override void DiscoveredCharacteristic(CBPeripheral peripheral, CBService service, NSError error) { System.Console.WriteLine("Discovered characteristics of " + peripheral); foreach (var characteristic in service.Characteristics) { Console.WriteLine("Write Value of characteristic " + characteristic.ToString() + " is " + characteristic.Value)

问题 I set notify to a characteristic, and then write some data(It's the address to be read and read data length) to another characteristic. Delegate didUpdateValueForCharacteristic will be called, but the characteristic.value is zero (should have some value) with the correct length. I also check the delegate didWriteValueForCharacteristic. This will be called after I write the data, but in the delegate, characteristic.value is null while the characteristic.UUID is the same as I wrote. So when