NRF8001 Problems

RE: NRF8001 Problems

David Edwin — Thu, 03 Sep 2015 07:50:17 GMT

I think you maybe right, I will ask the developer to examine the nRFToolbox. For attachments you need to put it in the answer.

RE: NRF8001 Problems

David Edwin — Thu, 03 Sep 2015 07:45:42 GMT

See answer below

RE: NRF8001 Problems

inder — Wed, 02 Sep 2015 20:38:35 GMT

Unfortunately, I don't have an Android device at the moment. But, I used BLE Explorer to test this (github.com/.../BLEExplorer.WP). And, I was able to send and receive data without any problems. No matter how many times I connected / disconnected. Now when I use nrfToolbox I can send data from the launchpad but cannot send data to it (previously I couldn't send data from the launchpad). And I don't get this 0x90 error anymore ! I think the problem is in the nrfToolbox app, maybe ?

I have added the UART data seen on the Serial Monitor in the original question. Dunno why I can't add attachments here ?

Thanks !

RE: NRF8001 Problems

David Edwin — Wed, 02 Sep 2015 08:00:25 GMT

For problem one: You attempt to send and you get a Pipe Error code 0x90. Looking this up in the documentation aka [Product Specification] (www.nordicsemi.com/.../nRF8001) we see that in the Appendix for ACI status codes

0x90 ACI_STATUS_ERROR_PIPE_INVALID Pipe Error Event : Transmit failed, Invalid or unavailable Pipe number or unknown pipe type

Clearly the pipe exists so this is not invalid so this may be a case of inadequate documentation.

Would it be possible to get the SPI messages you are sending and receiving printed out on the UART, the Arduino code base this by using the lib_aci_init and setting the debug parameter to true.

Can you use a different app, like BLE scanner to test this out ? You will need to subscribe to Notifications. You can also use our Master Control panel app on Android to test this.

RE: NRF8001 Problems

inder — Sun, 30 Aug 2015 07:34:24 GMT

I have found the solution to problem 2. So the old rev. C chip uses a slightly different BOND (0x10) command. For the rev. C the timeout limits are from 1 to 30 and for the rev. D the timeout limits are 1 to 180 seconds. The examples in the Arduino SDK are all for rev. D and all use a 180 second timeout value. Changing this value to 30 seconds made everything work.