Attachments (0)
Nordic Case Info
  • Case ID: 115083
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Timer and Multirole for PCA20006

Tobias Hofbaur

Hello, I have implemented the code below for my project based on switching central and peripheral role in S130. The code works fine on the Devkit PCA10028 but on porting it to PCA20006 I noticed some bugs in the final steps.

  • Without line 195 and 271 to 310 everything seems to work well on the Beacon, the LED is toggling in the right frequency. However after some time the frequency seems to roughly double. I cannot solidly quantify this observation.
  • Adding the above lines, the beacon does not switch on any LED at all. Only in debug mode the LEDs are switched on and the timer handler is entered. It seems there is a problem with my timer interrupt handling, but I dont know what.
  • I Am unsure if this code will be capable of handling 120 interacting nodes (well, mostly only up to 20 should be in close proximity)

Does anybody have an idea what could be my problem when porting to PCA20006? I am also grateful for any ideas to improve the code.

edit1: attached file instead of code: Corrected line numbers to reflect recent changes, as I corrected functionality. edit2: For completness I attached to whole (ecplise) project folder. Putting it into /central_and_peripheral/experimental/ should work. The makefile is currently set for PCA20006.

edit2: attached updated code

edit3: final code

Parents
  • 0

    Thank you for testing the code. The red LED/LED3 (indicating the status) should be on 1 sec, off 1 sec, etc. The DK works well for me, but the Beacon seemed to blink faster after some time. The blue LED/LED2 should signal any incoming ad from a tag with status I. The counter should show the seconds since power up (actually the number of times my main loop was called.) I planned to increase the adv_interval to 1000ms, the scan window to 100ms and the scan interval to 200ms to lower the collision rate. In connected mode, only 8 partners would work? But I did not plan to use that anyway. (Maybe in an upgrade to record the network, but then only one connection to a central)

Reply
  • 0

    Thank you for testing the code. The red LED/LED3 (indicating the status) should be on 1 sec, off 1 sec, etc. The DK works well for me, but the Beacon seemed to blink faster after some time. The blue LED/LED2 should signal any incoming ad from a tag with status I. The counter should show the seconds since power up (actually the number of times my main loop was called.) I planned to increase the adv_interval to 1000ms, the scan window to 100ms and the scan interval to 200ms to lower the collision rate. In connected mode, only 8 partners would work? But I did not plan to use that anyway. (Maybe in an upgrade to record the network, but then only one connection to a central)

Children
No Data
Terms of service