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

gazell more device question

SDK 9.0 nRF51 PCA10028 I want use nRF51 gazell function one host multi device. Reference example code "gzp_dynamic_pairing",host and device can auto pairing . But in host example code I can't find any function to get device "ID" or "address" information,only can chang PIPE to send and receive. So, host how to differentiate receive data from which device?

Parents
  • @Paul: There should be only one slave on one pipe when talking with the host. So you should manage the slave by the pipe. If you want to transmit data back to slave, you should use the ACK payload and send it to the correspondent pipe.

  • @paul: I'm sorry that I misunderstood you were asking about gazel link layer. On gazel pairing we don't really support multiple encrypted link. So only one pipe is used for encrypted data. You can use other pipe but as normal gazel link layer.

    It would not be very straight forward to modify the library to support multiple pairing pipes, mainly because gazell was not made for such application. It was initially made for HID application where usually only the keyboard need to be paired.

    I would suggest you to implementing your own encryption solution on top of the gazel link layer library or the enhanced shockburst library.

Reply
  • @paul: I'm sorry that I misunderstood you were asking about gazel link layer. On gazel pairing we don't really support multiple encrypted link. So only one pipe is used for encrypted data. You can use other pipe but as normal gazel link layer.

    It would not be very straight forward to modify the library to support multiple pairing pipes, mainly because gazell was not made for such application. It was initially made for HID application where usually only the keyboard need to be paired.

    I would suggest you to implementing your own encryption solution on top of the gazel link layer library or the enhanced shockburst library.

Children
No Data
Related