This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Problem to connect with connectblue OBS-421

Using OBS-421 from Connectblue as Central. Using simple AT command to connect and get data. Can connect successfully with Cypress BLE as well as the TI sensortag and get data from them. I cannot connect with nRF51, nRF52 at all. Cannot trace any error yet trying to debug by the serial port.

Unfortunately did not investigate with any sniffer or else. Just want to know if there is a known problem with the way nRFx connection and the way Connectblue handle this.

BTW: Try the central with nRF52 and failed so far. Another topic for later. :-)

Thank you for some help. I would like to use nRFx products in this configuration. jean-marc

Parents
  • 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)

Reply
  • 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)

Children
  • 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.

  • 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?

    • 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

  • 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)

  • 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.

Related