nRF8001: using pipes immediately after re-connecting

RE: nRF8001: using pipes immediately after re-connecting

Stephan Walter — Thu, 31 Jul 2014 07:40:36 GMT

While it works with MCP, we have to make it work with the common smartphone OS's. Since there is no way to tell on the nRF8001 side if the encryption has been fully established, the only workaround I see is to delay the data transmission for 5seconds. Thanks for your help.

RE: nRF8001: using pipes immediately after re-connecting

David Edwin — Wed, 30 Jul 2014 09:55:01 GMT

The root cause of the problem is likely that encryption of the link did not finish before data was sent on the Pipe, so if your script gets connected to a device for which you have the encryption keys, you must encrypt the link as the first thing to do on the link. Please accept my answer if this has helped you.

RE: nRF8001: using pipes immediately after re-connecting

Stephan Walter — Wed, 30 Jul 2014 07:41:14 GMT

Hi, thanks for your reply.

Using MCP 3.6.0 the problem does not occur.

I was using the nRF2739 with an older version of the Python API. Changing Security Request Delay or Bond Timeout did not help. I will try to figure out the difference between how MCP and my script uses the nRF2739.

Best regards, --Stephan Walter

RE: nRF8001: using pipes immediately after re-connecting

David Edwin — Tue, 29 Jul 2014 14:11:20 GMT

Can you upgrade to the latest version of the master control panel that you use with the nRF2739 and test the behaviour again ?
Can you increase the nRF8001 configuration -> Security ->Security Request Delay to 10 seconds and the Bond time out to 600 seconds and re-test.
If the above 2 suggestions did not fix the issue. Can you give me a log of the Events that are coming from the nRF8001 on the re-connection. Ideally when a Pipe is open it is available for use.