Problem to connect with connectblue OBS-421

RE: Problem to connect with connectblue OBS-421

jean-marc — Sat, 12 Mar 2016 15:20:43 GMT

YES!!!! Well done, the firmware 5.3.2 made it. But that is not all, also as you said: The must be attached with the letter "r". Great stuff, thank you very much for your assistance.

RE: Problem to connect with connectblue OBS-421

hcr — Sat, 12 Mar 2016 09:57:21 GMT

Yes at&f, just to make sure the where no strange settings.

The latest firmware for obs421 is 5.3.2 so it might help to uppgrade. (support.connectblue.com).

I still suspect that it has something to do with the random address, so one other thing worth testing could be to set a public address in the nrf module to verify or falsify this. (sd_ble_gap_address_set)

RE: Problem to connect with connectblue OBS-421

jean-marc — Sat, 12 Mar 2016 07:58:20 GMT

Factory reset? Do you mean "AT&F"? I did, power ON/OFF to accept the change. Set back parameters Central, power ON/OFF. Still bad :-(

Yes AT*AGI=6,4,0 find the Nordic as well as the others. Firmware version 5.1.4 Dec.12 2013 SP_2_10 Yes I am using the nRF52 Nordic example as well as mine. The best would be me to test with your nRF52 program.

Thank you for your help

RE: Problem to connect with connectblue OBS-421

hcr — Fri, 11 Mar 2016 23:11:33 GMT

Ok, that's too bad... I have verified that I can connect from OBS421 to nRF52 here using the following steps:

Reset obs421 to factory settings
Set obs421 as ble central
Connect using the command you provide above

Does your obs421 find the nRF module if you do a scan? (AT*AGI=6,4,0 for example)

Do you know the firmware version of your obs421?

Are you running a firmware example from nordic on you nRF52 or a custom firmware?

RE: Problem to connect with connectblue OBS-421

jean-marc — Fri, 11 Mar 2016 10:10:52 GMT

Thank you Henning for the followup. I tried and it does not work. As mentioned below, on Wireshark I can see that the command never goes out from the OBS421. The command I send is AT*ADCP=r,17,0,0 (send the r final this time). I do the same with the other brands (TI or Cypress) and it works. I send a request also to U-blox but never received any answers. I appreciate yours. I could send you more material for this subject.

RE: Problem to connect with connectblue OBS-421

hcr — Thu, 10 Mar 2016 10:13:11 GMT

Hi Jean-Marc,

nRF51/52 are using random static adresses and if you don't specify this in the connect command on OBS421 it will assume a public address. This will give the result you describe, OBS421 will not be able to connect.

The solution is to append an r to the address in the connect command, e.g. 0012F3000101 -> 0012F3000101r

If this doesn't solve your problem, please post the complete connect command you are using and I can have a look.

Best regards,

Henning

u-blox (former connectBlue)

RE: Problem to connect with connectblue OBS-421

jean-marc — Wed, 02 Mar 2016 13:26:37 GMT

OK done. I opened a case. Thank you for the following.

RE: Problem to connect with connectblue OBS-421

FormerMember — Wed, 02 Mar 2016 11:40:58 GMT

Thanks for the update! We will look further into this problem. Could you open a support case with this problem in mypage from https://www.nordicsemi.com ? In the support case, please link to this thread.

RE: Problem to connect with connectblue OBS-421

jean-marc — Wed, 02 Mar 2016 10:35:54 GMT

wrote the result of the sniffer on my second message above...

RE: Problem to connect with connectblue OBS-421

jean-marc — Tue, 01 Mar 2016 11:48:40 GMT

I will. I was hoping not having to do it :-) The sniffer is not always connecting and I need lots of trial to connect successfully. I will try in a few days. Too busy now. Thank you for helping. Will let you know. Jean-Marc

RE: Problem to connect with connectblue OBS-421

FormerMember — Tue, 01 Mar 2016 11:40:27 GMT

When trying to establish a link to nRF51/52, could you use the sniffer to track what is being transmitted over the air, and then upload the sniffer log here?

RE: Problem to connect with connectblue OBS-421

jean-marc — Tue, 01 Mar 2016 10:30:43 GMT

Yes I can connect with my phone both nRF51 and nRF52.

The only one that cannot connect as central is Connectblue. But I would not point Connectblue as the faulty since it can connect with the others (So far TI and Cypress).

Using one program of mine with nRF51 (mbed) for the nRF51 and using stack S110 for the nRF52 I do not remember what stack but is is a example supplied in the SDK with HRM.

It must be some way to connect that is used by Nordic that is not used by Connectblue. Or vice-versa. Thank you very much for your help jean-marc

FOLLOWUP: Used the sniffer and as far as I understand how to use it. :-) Used TI and Nordic to compare.

The TI peripheral advertise: 13 0.414750 TexasIns_72:9c:87 broadcast LE LL 46 ADV_IND

Then send the connection request from Connectblue: 423 14.730091 Connectb_1f:01:35 TexasIns_72:9c:87 LE LL 60 CONNECT_REQ

In this case all is fine. And we can see the connection request. ...... With Nordic (note: the advertisement has only the UUID): 73 2.512886 f9:ff:00:00:00:24 broadcast LE LL 55 ADV_IND

I send the connection request but nothing happen I only see the Nordic advertisement.

... With the phone the connection request can be seen for both TI and Nordic. Following is a connect request from the phone to the Nordic: 202 6.961006 HuaweiTe_bb:00:00 f9:ff:00:00:00:24 LE LL 60 CONNECT_REQ

Something strange here. Seems that the Connectblue never send a "request connect" when it is a Nordic :-D Could it be that the UUID peripheral number range is locked for some reason?

UPDATE and resolved: The ConnectBlue OBS421 firmware upgrade 5.3.2 [00:28:06,Apr 29 2015] made it as well as adding a letter "r" at the end of the example: fec123478941r

Connect well my nRF52 with ConnectBlue OBS421.

RE: Problem to connect with connectblue OBS-421

FormerMember — Tue, 01 Mar 2016 08:53:47 GMT

Do you have tested to connected the nRF51 or nRF52 to another central, like a phone for example?

Did you remember to program both a softdevice (S110 or S130) and the application to the nRF51/52 device?