• State Verified Answer
  • Replies 29 replies
  • Subscribers 72 subscribers
  • Views 7916 views
  • Users 0 members are here
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

    There is no point in changing the scan parameters, as passive scanning is pure RX (and as such can be done by an infinite number of devices simultaneously). Reducing the scan time would only decrease the chances of catching advertising packets (although it would of course save battery on the scanning device to scan half as much.)

    The current s130 can only have one link as peripheral, but you can have multiple links as central. This has to do with timing constraints; the central decides connection parameters so you can schedule multiple connections in central role, but the peripheral has to accept whatever schedule the central provides meaning multiple connections in peripheral role would be a scheduling nightmare with a lot of scheduling collisions.

Reply
  • 0

    There is no point in changing the scan parameters, as passive scanning is pure RX (and as such can be done by an infinite number of devices simultaneously). Reducing the scan time would only decrease the chances of catching advertising packets (although it would of course save battery on the scanning device to scan half as much.)

    The current s130 can only have one link as peripheral, but you can have multiple links as central. This has to do with timing constraints; the central decides connection parameters so you can schedule multiple connections in central role, but the peripheral has to accept whatever schedule the central provides meaning multiple connections in peripheral role would be a scheduling nightmare with a lot of scheduling collisions.

Children
No Data
Related
Terms of service