Channel Search + Device Pairing Configuration

RE: Channel Search + Device Pairing Configuration

Petter Myhre — Wed, 22 Mar 2017 14:56:56 GMT

Thank you :) I converted your comment to an answer because I think it sums this up.

RE: Channel Search + Device Pairing Configuration

angel — Tue, 21 Mar 2017 12:59:07 GMT

Hi Petter,

I hope you enjoyed your vacations :). I read that, but I think I will leave the configuration in default, so, slower search but low power consumption.

In the end what I do is, when the remote control doesn't find the master, because it is OFF, I go to sleep. In all other cases I establish and use communication. If after some time, say, 5 mins, the PAD is completely unused, I just close the channel and wait for some activity. So far I think this may be the best solution.

Thanks for your help!

RE: Channel Search + Device Pairing Configuration

Petter Myhre — Mon, 20 Mar 2017 10:05:07 GMT

Sorry for the delayed reply. You can try to change the searching waveform value, see this for more information.

RE: Channel Search + Device Pairing Configuration

Hung Bui — Tue, 14 Mar 2017 15:42:13 GMT

@angel: Petter is away for 1 week, he will get back to you next week.

RE: Channel Search + Device Pairing Configuration

angel — Mon, 13 Mar 2017 07:03:34 GMT

Good morning,

I have tested it but, overall, the time to open the channel and send the information is noticeable, around 300 or 400 ms... Not fast enough to not notice a delay... Any other idea on how to do what I want to do without maintaining the channel open? Timeout to close the channel after some minutes should work, but I need a better solution than this...

Thanks a lot!

RE: Channel Search + Device Pairing Configuration

Petter Myhre — Fri, 10 Mar 2017 16:14:44 GMT

Yes.

Closing the channel would probably save you some power, if you still can fulfill your latency requirements or not I think you will have to test.

RE: Channel Search + Device Pairing Configuration

angel — Fri, 10 Mar 2017 10:18:14 GMT

Yes, I understand that only when you send from slave to master, EVENT_TX from slave will be triggered. But, however, if you leave open the channel, in the slave end you will always get EVENT_RX at each channel period, even if you don't send anything from master (I think it will send the previous data sent automatically).

Or you mean the case where I open the channel only when I need to send something and then close it again?

Thanks a lot Petter!

RE: Channel Search + Device Pairing Configuration

Petter Myhre — Fri, 10 Mar 2017 10:13:42 GMT

Why not? Broadcast data is only sent from the slave to the master if you ask it to. The latency will depend on the channel period. Short channel period will give low latency, but high power consumption, long channel period will give high latency, but low power consumption.

RE: Channel Search + Device Pairing Configuration

angel — Fri, 10 Mar 2017 07:07:56 GMT

Hi Petter,

What you suggest is actually my current implementation, but this way the slave, which is the one that acts as remote control, will not have the possibility of sending asynchronous data upon the press of a button.

I am though thinking of solving this issue opening the channel each time I press a button, send what I want to send and then closing it again. This way I would save quite a lot of battery. What worries me is the delay between pressing the button and sending the data, if the opening of the channel takes too long...

RE: Channel Search + Device Pairing Configuration

Petter Myhre — Thu, 09 Mar 2017 15:29:17 GMT

Can't just Node 1 by a slave? And Node 2 and 3 be masters?

RE: Channel Search + Device Pairing Configuration

endnode — Thu, 09 Mar 2017 07:15:40 GMT

And I've missed the tags, sorry;)

RE: Channel Search + Device Pairing Configuration

angel — Thu, 09 Mar 2017 07:06:03 GMT

Ups, sorry, I put that information in the tags of the post, forgot to put it in the actual post. Here it is: nRF51422, ANT protocol, S210 v5.0.0

RE: Channel Search + Device Pairing Configuration

endnode — Wed, 08 Mar 2017 19:35:50 GMT

You are speaking about channel, scanning and some asynchronous communication. How does it relate to Nordic products? Could you be more specific if your question is related to any existing chip (e.g. nRF52) and technology (BLE, ANT, other) or is it completely abstract thought process?;)