Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SCAN REPORT don't decode the full name #85

Open
straccio opened this issue Nov 9, 2016 · 9 comments
Open

SCAN REPORT don't decode the full name #85

straccio opened this issue Nov 9, 2016 · 9 comments

Comments

@straccio
Copy link

straccio commented Nov 9, 2016

With 1.0.7 version SCAN REPORT example don't decode the full name

#63

@zoujixing
Copy link

Can you post you code here? I will check that.

@straccio
Copy link
Author

straccio commented Nov 9, 2016

I have used the BLE_ScanReport example.

@straccio
Copy link
Author

straccio commented Nov 9, 2016

I'm not sure, but before update the bootloader i remember that the code works

@zoujixing
Copy link

zoujixing commented Nov 9, 2016

Can you post some debug info?
This example just parse advertising data, not parse scan response data.

@straccio
Copy link
Author

straccio commented Nov 9, 2016

I have attached the code
BLE_ScanReport_FULLINFO.txt
and here some print to serial

Scan Device CallBack Handle 
  The peerAddr : 91 47 53 35 38 84  
  The Rssi : -49
  params->isScanResponse: 0
  params->type: 0
  params->advertisingDataLen: 11
  params->advertisingData: 2 1 6 7 FF 4C 0 10 2 B 0  

Scan Device CallBack Handle 
  The peerAddr : 91 47 53 35 38 84  
  The Rssi : -48
  params->isScanResponse: 1
  params->type: 0
  params->advertisingDataLen: 0
  params->advertisingData:  

Scan Device CallBack Handle 
  The peerAddr : 73 DD B0 BF 9C 70  
  The Rssi : -49
  params->isScanResponse: 0
  params->type: 0
  params->advertisingDataLen: 23
  params->advertisingData: 2 1 6 13 FF 4C 0 C E 8 4D 17 CA CB 67 D8 AB 2D 3A EB BF 1D F0  

Scan Device CallBack Handle 
  The peerAddr : 73 DD B0 BF 9C 70  
  The Rssi : -48
  params->isScanResponse: 1
  params->type: 0
  params->advertisingDataLen: 0
  params->advertisingData:  

Scan Device CallBack Handle 
  The peerAddr : 91 47 53 35 38 84  
  The Rssi : -49
  params->isScanResponse: 0
  params->type: 0
  params->advertisingDataLen: 11
  params->advertisingData: 2 1 6 7 FF 4C 0 10 2 B 0  

Scan Device CallBack Handle 
  The peerAddr : 73 DD B0 BF 9C 70  
  The Rssi : -50
  params->isScanResponse: 1
  params->type: 0
  params->advertisingDataLen: 0
  params->advertisingData:  

Scan Device CallBack Handle 
  The peerAddr : 73 DD B0 BF 9C 70  
  The Rssi : -52
  params->isScanResponse: 0
  params->type: 0
  params->advertisingDataLen: 23
  params->advertisingData: 2 1 6 13 FF 4C 0 C E 8 4D 17 CA CB 67 D8 AB 2D 3A EB BF 1D F0

@zoujixing
Copy link

zoujixing commented Nov 9, 2016

Your advertisement don't contain a name type(BLE_GAP_AD_TYPE_SHORT_LOCAL_NAME: 0x08, BLE_GAP_AD_TYPE_COMPLETE_LOCAL_NAME: 0x09)

BLE_GAP_AD_TYPE_FLAGS : 2 1 6
BLE_GAP_AD_TYPE_MANUFACTURER_SPECIFIC_DATA: 13 FF 4C 0 C E 8 4D 17 CA CB 67 D8 AB 2D 3A EB BF 1D F0

@straccio
Copy link
Author

straccio commented Nov 9, 2016

I think there's a problem, from a bluetooth browser i can see other devices like a magic mouse or an iPhone with name. These devices are near (2 or 3 cm) from the blenano.
I seem that the peer address is inverted.

@straccio
Copy link
Author

straccio commented Nov 9, 2016

I can confirm that the peer address is inverted.
I'm not an expert of Bluetooth but is normal that the scanresponse have no advertisingData?

@zoujixing
Copy link

zoujixing commented Nov 9, 2016

That is device name not include in advertisement and scan response data.
Like example "BLE_SimplePeripheral", the device name is "BLE_Peripheral". When using "scan report" to scan this device, will get the local name "TXRX".

  // Add short name to advertisement
  ble.accumulateAdvertisingPayload(GapAdvertisingData::SHORTENED_LOCAL_NAME,(const uint8_t *)"TXRX", 4);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants