Difference Advertising Data and ScanRSP data.

RE: Difference Advertising Data and ScanRSP data.

Edvin — Wed, 20 Jun 2018 08:23:29 GMT

What are your scanning parameters, scan_interval and scan_window set to?

If you send the projects, I can see if I can figure out the reason.

BR,

Edvin

RE: Difference Advertising Data and ScanRSP data.

leejh — Wed, 20 Jun 2018 00:50:03 GMT

Thanks for your trying.

I have tested with LED. When the scanrsp == 1, LED is on and the other side, LED is off.

The result is that the LED is Blinky but the interval is very slowly.

I have configured scanning every sec. but the scan rsp data does not come out every sec.

A few tens of seconds short, and a few minutes long.

I think the problem was caused BLE.

RE: Difference Advertising Data and ScanRSP data.

Edvin — Tue, 19 Jun 2018 07:57:03 GMT

Hello,

I am still trying to figure out whether the issue is BLE related, or UART related. Do you get the event when you receive the scan response? What happens if you e.g. toggle a pin/LED when scan_rsp == 0 and toggle another when scan_rsp == 1? Does both of the pins toggle?

Would it be possible for me to recreate the issue that you are seeing? If you could send both the beacon application and the scanner, I can see if I can see the same behavior as you.

BR,

Edvin

RE: Difference Advertising Data and ScanRSP data.

leejh — Tue, 19 Jun 2018 00:19:37 GMT

Yes, I know that the ADV data and Scan Rsp data is same report.

static void ble_evt_handler(ble_evt_t const * p_ble_evt, void * p_context)
{
    ret_code_t            err_code;
    ble_gap_evt_t const * p_gap_evt = &p_ble_evt->evt.gap_evt;
    uint8_t rssi_value;
    ble_gap_addr_t peer_address;
   
   
    switch (p_ble_evt->header.evt_id)
    {
        case BLE_GAP_EVT_ADV_REPORT:
        {
            ble_gap_evt_adv_report_t const * p_adv_report = &p_gap_evt->params.adv_report;
            if(p_adv_report->scan_rsp == 1)
            {
                for(int i=0; i<31; i++)
                {
                  SEGGER_RTT_printf(0, "%02x", p_adv_report->data[i]);
                  app_uart_put(p_adv_report->data[i]);
                }
                SEGGER_RTT_WriteString(0, "\n");
            }
            
            else if(p_adv_report->scan_rsp == 0)
            {
              for(int i=0; i<31; i++)
                {
                  SEGGER_RTT_printf(0, "%02x", p_adv_report->data[i]);
                  app_uart_put(p_adv_report->data[i]);
                }
                SEGGER_RTT_WriteString(0, "\n");
            }

So, I have tested by using the Oscilloscope to confirm the TX Pin Signal of nRF52832 chip on the board(P0.06).

When the each advertising data and the scan rsp data was sent, the TX pin of the DK board has a correct signal.

However, in the beacon that i made using the nRF52832 chip, the advertising data showed a correct signal, but the scan ras data did not come out. This was also measured at the TX pin (P0.06).

There are same firmware and same enviroment in the DK board and my beacon.

If my beacon is designed in the wrong way and the signal does not come out properly, why is the ADV data coming out well and not the scan data?

Why this reason happend? I don't understand... thanks Edvin.

RE: Difference Advertising Data and ScanRSP data.

Edvin — Mon, 18 Jun 2018 13:54:29 GMT

Hello,

This sounds like an application issue. There is no reason why you should not be able to print the Scan response data.

I assume that you are trying to print the data in the BLE_GAP_EVT_ADV_REPORT event, right?

Could you include the snipped inside this event? How do you transmit the data from the advertising packets?

Do you see that event for the scan response as well?

Do you try to print something, which you can't see, or are you missing the events?

Best regards,

Edvin