CC1352P7: Beagleplay - using coprocessor binary in 1352, configured FH, 200kbps - higher incidence of spontaneous re-joins with larger channel list.

Part Number: CC1352P7

Tool/software:

I'm testing a system using a beagle play as the collector for a sensor net. It's using a co-processor model, with the collector running in the BeaglePlay linux box. I'm noticing that when running in FH mode, with larger numbers of sensor nodes that if I set the channel list to 8 channels or so, it runs without issue. However, if I configured the default 64 channels, I get 3-10 sensor re-joins per sensor per day. Is there some reason why this would happen? It's difficult to figure out because it goes away when the channel list is reduced, making packet sniffing impractical as a means of debug.

Some pertinent info:

  • Sensors are cc1352R1 devices.
  • Network is configured for FH, 200 kbps 2GFSK.
  • Sensors firmware is based on the dmm_154sensor_remote_display_oad_app
  • Sensors are set to send a data report every 20 seconds, and poll every 90 seconds.
  • tracking interval (TRACKING_INIT_TIMEOUT_VALUE) has been set to 300 seconds.
  • The network has 9 sensors joined. Another test network with only 2 sensors does not exhibit this problem.
  • Sensors are about 10 feet from the collector, which should rule out saturation as an issue.

What I'm looking for is some ideas of things to check that might be causing this, and/or suggestions for how to narrow down the cause.

  • Hi Joshua,

    1. You can do a simple noise floor test with SmartRF studio, just listen to the background noise where you're doing this test, just to make sure there's no noise disturbing the test.
    2. Were you able to see the disconnect reason on the sensors before the re-join? It would be useful to know if there are specific channels that are prone to disconnect.
    3. Is it the same sensors each time or does it vary between all of them? If it's the same ones you can check the frequency offset on these specific devices.
    4. You say you're sing the DMM example. Are you also using BLE when this happens?

    Cheers,

    Marie H

  • Marie,

    1.) I've not done this yet, but will and report back.

    2.) I've not seen the disconnect reason. Could you provide any info on how best to capture this? I presume maybe the sync loss callback in the sensor could be instrumented?

    3.)It varies across the population of sensors.

    4.) I am using only advertising, and quite infrequently. A burst of 4 advertisements every 30 seconds. I did notice that the frequency of re-connects decreased a bit when I changed from exactly every 30 seconds to every 30.25 seconds. I did this because the sensors are sending data at 20 second intervals, and I didn't want the advertisements to beat with the data reports on every other third report cycle.

  • Marie,

    Noise measurements for the 64 channels in use. It doesn't look concerning to me, what do you think?

    If is is advisable to exclude the worst channels, do you have a recommended algorithm or method to do this? Is there an example?

    Regards,

    Josh

    Channel frequency reported rssi
    0 902.4 -101
    1 902.8 -98
    2 903.2 -102
    3 903.6 -100
    4 904 -85
    5 904.4 -102
    6 904.8 -96
    7 905.2 -102
    8 905.6 -94
    9 906 -97
    10 906.4 -101
    11 906.8 -85
    12 907.2 -100
    13 907.6 -97
    14 908 -95
    15 908.4 -102
    16 908.8 -94
    17 909.2 -102
    18 909.6 -85
    19 910 -102
    20 910.4 -100
    21 910.8 -90
    22 911.2 -104
    23 911.599999999999 -97
    24 911.999999999999 -102
    25 912.399999999999 -93
    26 912.799999999999 -97
    27 913.199999999999 -103
    28 913.599999999999 -96
    29 913.999999999999 -102
    30 914.399999999999 -94
    31 914.799999999999 -102
    32 915.199999999999 -102
    33 915.599999999999 -100
    34 915.999999999999 -100
    35 916.399999999999 -84
    36 916.799999999999 -100
    37 917.199999999999 -100
    38 917.599999999999 -90
    39 917.999999999999 -100
    40 918.399999999999 -93
    41 918.799999999999 -102
    42 919.199999999999 -97
    43 919.599999999999 -100
    44 919.999999999999 -102
    45 920.399999999999 -92
    46 920.799999999999 -104
    47 921.199999999999 -102
    48 921.599999999999 -102
    49 921.999999999999 -102
    50 922.399999999999 -101
    51 922.799999999999 -103
    52 923.199999999999 -92
    53 923.599999999999 -104
    54 923.999999999999 -95
    55 924.399999999999 -100
    56 924.799999999999 -102
    57 925.199999999999 -98
    58 925.599999999999 -103
    59 925.999999999999 -85
    60 926.399999999999 -102
    61 926.799999999999 -102
    62 927.199999999999 -92
    63 927.599999999999 -101