• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
didDiscoverPeripheral keys and GAP Assigned Numbers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

didDiscoverPeripheral keys and GAP Assigned Numbers


  • Subject: didDiscoverPeripheral keys and GAP Assigned Numbers
  • From: karel <email@hidden>
  • Date: Thu, 09 Aug 2012 18:20:56 +0900

On scanning for my device advertising with ADtypes
0x01 «Flags»
0x07 «Complete List of 128-bit Service Class UUIDs»
0x17 or 0x18 «Public Target Address» or «Random Target Address»

I get the NSDictionary results below which show only entries for AD entry of ADtype=0x07
I guess I'm am using iOS V5.something so the « XX Target Address» features may not be defined and thus don't pop up in the AdvData in the callback, but in any case, is there a header file I could modify or some parser filter list to which I could add the required 0x17 / 0x18 ?

http://developer.apple.com/library/ios/#documentation/CoreBluetooth/Reference/CBCentralManagerDelegate_Protocol/translated_content/CBCentralManagerDelegate.html
mentions the  "advertisementData" contains CBAdvertisementData* keys (kCBAdvDataServiceUUIDs, kCBAdvDataLocalName etc), but I can't find any documentation on any of this.

Help!!

#didDiscoverPeripheral
#2012-08-09 17:21:03.771 TandDTest1[8669:707] key: kCBAdvDataServiceUUIDs, value: (
#                                                                                  "Unknown (<d0d0d0d0 00000000 00000000 deadf154>)"
#                                                                                  )
#didDiscoverPeripheral
#2012-08-09 17:21:03.774 TandDTest1[8669:707] key: kCBAdvDataServiceUUIDs, value: (
#                                                                                  "Unknown (<d0d0d0d0 00000000 00000000 deadf154>)"
#                                                                                  )


The following is from a Scan response
#2012-08-09 17:21:03.775 TandDTest1[8669:707] key: kCBAdvDataLocalName, value: SimpleBLEPeripheral
#2012-08-09 17:21:03.777 TandDTest1[8669:707] key: kCBAdvDataTxPowerLevel, value: 0


Regards
Karel
 _______________________________________________
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

  • Follow-Ups:
    • Re: didDiscoverPeripheral keys and GAP Assigned Numbers
      • From: Pierre Bouchet <email@hidden>
  • Prev by Date: Re: Read/Write Blob
  • Next by Date: Re: didDiscoverPeripheral keys and GAP Assigned Numbers
  • Previous by thread: Re: Read/Write Blob
  • Next by thread: Re: didDiscoverPeripheral keys and GAP Assigned Numbers
  • Index(es):
    • Date
    • Thread