nRF8001 is not being connected to Apple iPhone

[taher143]

Dear Sir,

I am working on a project to realize the nRF8001 HRM demo application using the Github code that you suggested. However, I am stuck at a point in the code and don't know what is wrong. If you can provide any suggestions at the earliest I would be really obliged.

The scenario happens to be as follows: Hello Initializing Waiting for Standby state Calling transmitReceive... event handler EVENT debug=1 length=4 event=DeviceStartedEvent Operating mode: Setup Hardware error: No error DataCreditAvailable: 2 sending setup message number 0 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 1 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 2 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 3 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 4 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 5 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 6 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 7 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 8 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 9 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 10 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 11 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 12 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 13 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 14 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 15 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 16 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 17 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 18 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 19 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 20 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 21 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 22 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 23 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 24 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 25 non-success command response event: 0x1 ready for next setup message event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction continuation status Op: Setup sending setup message number 26 non-success command response event: 0x2 setup complete event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Transaction completed Op: Setup setup is complete! event handler EVENT debug=1 length=4 event=DeviceStartedEvent Operating mode: Standby Hardware error: No error DataCreditAvailable: 2 setup is complete! device in Standby state, returning SUCCESS calling transmitCommand event handler EVENT debug=1 length=10 event=CommandResponseEvent Status: Success Op: GetDeviceAddress Address: 0xea00fbf5c054 calling transmitCommand received temperature event handler EVENT debug=1 length=5 event=CommandResponseEvent Status: Success Op: GetTemperature 26.00 C Temperature: 26.00 connecting polling event handler EVENT debug=1 length=3 event=CommandResponseEvent Status: Success Op: Connect ready to send data device not connected device not connected calling transmitCommand polling received temperature event handler EVENT debug=1 length=5 event=CommandResponseEvent Status: Success Op: GetTemperature 26.00 C polling ready to send data device not connected device not connected calling transmitCommand polling received temperature event handler EVENT debug=1 length=5 event=CommandResponseEvent Status: Success Op: GetTemperature 25.75 C polling

after this its keep polling and printing temperature. i have used same service pipes as you have suggested. the schematic is as per nordic's datasheet. i am not able to figure out where the problem is? I am at wit's end trying to find out the reason for the same. On my hardware I have used the suggested balun components in the nRF8001 datasheet for impedence matching. I have tried using an SMA antenna, a chip antenna and a PCB trace antenna but nothing seems to help.

Once again, any suggestions/recommendations to go forward will be highly appreciated.

Thanks

[jacobrosenthal]

Just to ping this so its not sitting unanswered. Neither I nor Guan are currently working with the chip atm. If I do get back to it I'll try to confirm this, but no idea when that will be. In the mean time Nordic actually released a bunch of their own arduino stuff which you might want to check out. https://devzone.nordicsemi.com/arduino

[plskeggs]

Where did you get your services.h? Did you use the nRF Studio and make your own, or are you using an example?

[jacobrosenthal]

I cant necessarily speak for Guan but I'm sure it was generated

Sent from my iPhone

On Jan 6, 2014, at 10:08 PM, Pete Skeggs [email protected] wrote:

Where did you get your services.h? Did you use the nRF Studio and make your own, or are you using an example?

— Reply to this email directly or view it on GitHubhttps://github.com/guanix/arduino-nrf8001/issues/4#issuecomment-31713850 .

[plskeggs]

I'm actually asking the original reporter of this problem, taher143. Is he using the services.h.example, services.h.redbear, or a new one?

[taher143]

Thank you very much sir Pate Skeggs and Jacob Rosenthal for replying. I am using services.h.example in my code.

TAHER KAWANTWALA Embedded Software Engineer +91-74051-37462 skpeID:taher_embedded_engineer [email protected].

On Tue, Jan 7, 2014 at 10:43 AM, Pete Skeggs [email protected]:

I'm actually asking the original reporter of this problem, taher143. Is he using the services.h.example, services.h.redbear, or a new one?

— Reply to this email directly or view it on GitHubhttps://github.com/guanix/arduino-nrf8001/issues/4#issuecomment-31714026 .

[plskeggs]

Which circuit example from the data sheet did you build? The one with DC/DC converter enabled or the other? Have you used a microscope to make sure that all the pins of the nRF8001 are well soldered and not shorted to neighboring pins? These parts are very small and I had trouble getting my solder paste mask to work well; I had to touch up the solder joints on many pins on the first few boards I built until I made a good mask.

It seems like, from your log, that the SPI signals and the 32KHz oscillator are working. But perhaps the 16MHz oscillator is not.

It's also possible that the services.h file is selecting a setting for your hardware that is not compatible.

You can use the nRFgo Studio to check the hardware settings. The settings are:

• 32KHz clock source -- external crystal, internal oscillator, or other
• 32KHz clock accuracy -- less than 20PPM, or some other range
• 16MHz clock source -- crystal source or digital source
• initial Tx power - 0dBm
• DC/DC converter -- enable/disable

Unfortunately, guanix did not upload his .xml file that he used to create the services.h.example. You would need to use nRFgoStudio with the heart_rate_sensor-redbear.xml to load into nRFgo Studio and then generate a new services.h, after correcting the hardware settings to match your hardware.

[taher143]

Hi, We have used the DC/DC converter disabled circuit.

In the past couple of hours here has bee a major update. We have been able to conect the hardware to the Master Control Panel via the PCA10000. Until yesterday we were only able to detect the board. We are currently working on changing the capacitance around the 16Mhz crystal. If you have a better suggestion please let us know.

Neel.

TAHER KAWANTWALA Embedded Software Engineer +91-74051-37462 skpeID:taher_embedded_engineer [email protected].

On Tue, Jan 7, 2014 at 12:22 PM, Pete Skeggs [email protected]:

Which circuit example from the data sheet did you build? The one with DC/DC converter enabled or the other? Have you used a microscope to make sure that all the pins of the nRF8001 are well soldered and not shorted to neighboring pins? These parts are very small and I had trouble getting my solder paste mask to work well; I had to touch up the solder joints on many pins on the first few boards I built until I made a good mask.

It seems like, from your log, that the SPI signals and the 32KHz oscillator are working. But perhaps the 16MHz oscillator is not.

It's also possible that the services.h file is selecting a setting for your hardware that is not compatible.

You can use the nRFgo Studio to check the hardware settings. The settings are:

• 32KHz clock source -- external crystal, internal oscillator, or other
• 32KHz clock accuracy -- less than 20PPM, or some other range
• 16MHz clock source -- crystal source or digital source
• initial Tx power - 0dBm
• DC/DC converter -- enable/disable

Unfortunately, guanix did not upload his .xml file that he used to create the services.h.example. You would need to use nRFgoStudio with the heart_rate_sensor-redbear.xml to load into nRFgo Studio and then generate a new services.h, after correcting the hardware settings to match your hardware.

— Reply to this email directly or view it on GitHubhttps://github.com/guanix/arduino-nrf8001/issues/4#issuecomment-31716960 .