We are trying to connect DA and NRF BT modules, without much success.
Using example code from SDK 5.0.3, Proximity Monitor Ext with windows PC as host, we have difficulties connecting to a NRF chipset based sensor, we can never establish connection. Looking at BLE sniffer logs (TI BT sniffer based on CC2540) it sends scan requests but no connection requests can be seen in the logs. We are trying using the NRF SDK which is out-of-the box, which works well to connect to with other NRF units or mobile phone applications (i.e. Lightblue). Connecting to other devices based on DA BT chip seems to be working ok though, so we know hardware is in ok condition. Doing the opposite, running the proximity reporter example from the SDK and trying to connect from NRF as a collector (monitor), we can see connection requests but connection is also not established. Same example project from NRF can connect to other sensors (not DA based). Log files from BT sniffer for above examples are available, but cannot upload here since only pdf files are allowed.
Are there any known inter-operability issues between DA and NRF BT chipsets? Any tips for workarounds or ideas how to solve these issues?
Maybe you are able to zip your log file and upload it?
Hi johan_alps,
这个问题发生在trying to run the proximity examples either as a monitor or as a reporter ? I am not aware of the implementation the NRF module has when used as peripheral or as central. Regarding the DA as central and the NRF as a peripheral, you cant see any connection requests as you said (operating over the windows tool), are you instructing the central to send a connection request via the console ? and if you are issuing the connection command, in the app_connect() function are you setting the proper parameters ? (the proximity monitor is set to work only with the public addresses if you try to connect to a random address, as far as i can see, you wont see a connection indication in the sniffer) if you issue a connection command. As far as i know there aren't any inter-operability problems with NRF chips.
Thanks MT_dialog
Hi,
> The problem occurs when trying to run the proximity examples either as a monitor or as a reporter ?
J_A: The problem occurs when running DA14581 as monitor. When used as reporter and connecting to it from similar NRF application, there are no problems.
> I am not aware of the implementation the NRF module has when used as peripheral or as central. Regarding the DA as central and the NRF as a peripheral, you cant see any connection requests as you said (operating over the windows tool), are you instructing the central to send a connection request via the console ?
J_A: Yes, I request connection via the console (windows tool), but see no connection requests in the sniffer.
> and if you are issuing the connection command, in the app_connect() function are you setting the proper parameters ? (the proximity monitor is set to work only with the public addresses if you try to connect to a random address, as far as i can see, you wont see a connection indication in the sniffer) if you issue a connection command. As far as i know there aren't any inter-operability problems with NRF chips.
J_A: I am using the default values in the app_connect() function. Regarding the addressing (public/random), good point and I will check if this is the issue or not.