• State Verified Answer
  • Locked Locked
  • Replies 9 replies
  • Subscribers 62 subscribers
  • Views 3049 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 115384
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

esb "realtime" - timeslots - nrf51 example

Martin

Hi

can ESB be considered RealTime transfer as soon as it has it's timeslot?

Outline of use-case:

  • Device advertises existenace on BLE
  • If there is data waiting for this device, it would be notified e.g. by an attr-read
  • the device turns on radio for ESB, central connects via pipe and pushes data to device.
  • disconnect, reset device

Is this mixed mode scenario possible with the SD130 ?

Thanks

  • 0

    This scenario is possible with S130. To send data to the device (notification or attr-read) you have to be connected, so you would have to connect after advertising.

    If ESB is “realtime” depends on what you call “realtime”. ESB may be the fastest way to send data as soon as you are in a timeslot or have full control over the radio.

    Update 2016.08.09: Here is a project that uses esb in timeslot: ble_app_uart - ESB_Timeslot.zip

  • 0 in reply to Ole Bauck

    Can you hint me to an example project for SDK11 which works? I was not able to make this scenario work for the last 3 days. Also because of this problem: other question

  • 0 in reply to Ole Bauck

    There is no example in the SDK. We have an example here that works with nRF52, I will update my answer with this file.

  • 0 in reply to Ole Bauck

    Hi Ole I have integrated your source into our FW. For some reason in 90% of the cases I do not get an ACK package from the receiver... Might this be because we are not using an XTAL, but only the intrenal RC? Meaning to much drift because of this?

  • 0 in reply to Ole Bauck

    I would not believe that to be the problem, but you could try with using xtal (like on a DK) and see if the problem is still there. Are you timing the sending such that the receiver is listening at the correct time (since you are asking if the LFCLK source can be the issue)?

    The problem may also be interference, try another channel or try a place where there is not that many devices communicating in the 2.4GHz band.

    Does it work without using timeslot, like the esb examples (under examples/proprietary_rf)?

Related