DSPS_Central与DSPS_DEVICE（ComperipherWirectal）连接

Hi prasanth.velliyangiri,

如果您拥有第二个设备的公共BD地址，希望连接到您可以在使用App_easy_gap_start_connection_to_set（）函数的情况下，可以在不扫描的情况下启动连接过程，并设置地址，地址类型和连接间隔。如果您没有地址并且需要扫描您应该向堆栈发出扫描命令获取地址，然后使用从扫描过程中获得的地址发出相同的连接命令。

Thanks MT_dialog

Hi prasanth.velliyangiri,

The scanner scans one channel at the time and reports back the devices one by one and prints them as well in the user_on_adv_report_ind if this is what you mean, you wont get two devices on one user_on_adv_report_ind invocation.

Thanks MT_dialog

Hi prasanth.velliyangiri,

You should modify the code and after the first connection is made you should restart the scanning procedure. At the advertising indication you can decide on which device you are willing to connect to, either check the bd address or the advertising string and if it matches a predefined string you will issue a connection command.

Thanks MT_dialog

Hi prasanth.velliyangiri,

Q1: On the host side as soon as you get an advertising message the connection request is send and when the connection is established the gapc_connection_req_ind_handler() hits and the a confirmation message is sent to the the GAPC task. After that the connection callback is invoked and in that callback the connection timer is disabled, and the host starts the discovery procedure with the app_prf_enable() function (there are quite some functions invoked during the discovery procedure, when the user_sps_enable is invoked starting with the GATTC_DISC_CMD - the information about those messages can be found in the RW_BLE_GATT_IS). So while you are discovering you are allready connected and the discovery functions are being invoked in order to retrive the services of your peer device. Also the mtu exchange function is invoked. Also since the peer device is issuing an update request you should also see the gapc_param_update_req_ind_handler() executing as well.

Q2: You can restart scanning in the connection complete callback function.

Q3: You can have an array of all the available predefined addresses and loop through that array when you have an indication that you have received an advertising string.

Thanks MT_dialog

Hi prasanth.velliyangiri,

Q2: .app_on_connection = user_on_connection, your device has finished the connection with the first device and starts scanning for the second device.

Q3: I dont think that this is too much to debug, you will have to check what is the value in the parameters and check what might go wrong and the comparison fails, you can also use the memcmp() in order to compare the two bd addresses. The bdaddr_compare() doesn't do anything special, it just runs through the two arrays and checks the elements one by one. Perhaps the one of the two addresses is inversed.

Thanks MT_dialog

Hi prasanth,

The reason for this is that the DSPS when scanning, the mode that it used is GAP_GEN_DISCOVERY, when scanning is performed in that mode the procedure automatically expires and the DSPS sends a new scan command in order to restart scanning. So during the period of the scan command with the duplicate filter enabled you should not get additional advertising events from the same device, but when you restart scanning those advertising event will pop up again. You can either implement an additional buffer that will hold the devices during previous scans or you can change the GAP_GEN_DISCOVERY mode to GAP_OBSERVER_MODE. With the GAP_OBSERVER_MODE the scan never times out, so you dont have to start the scanning again by sending a new command therefore you wont get additional indications from allready reported devices but you will get all kind of advertising strings (undirected, non-connectable, limited etc).

Thanks MT_dialog