This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1352P: Sensor retried many times to a collector in SUB GHZ Communication

Part Number: CC1352P

Hi,

I have two CC1352R(Sensors) and CC1352P(collector) boards communicating with each others using sub GHz at 868 freq band, 50 KBPS speed with 12 dBm tx power with Nonbeacon mode.

We are using only by default channel mask(channel 0) particularly copying channel number and network details including sensors joined to the network, into external flash and retrieve back after restart in collector instead of using usual network creation) for both networks. we use SDK 3.3 and ccsV9.2. we are testing in India(Asia) and our client is in Germany(Europe). 

The following test cases are done by our customers.

1. Collector Association test with sensors. Result: Some time passed and sometimes failed. The collector does not send an Association response to the sensor 

2. Communication test between sensor and collector. Result:  Duplicates from the sensor to Collector occurs 

Sensor retrying the same message multiple times. Here only one collector and 4 sensors no other collectors or sensors are powered On. Log attached for your reference. The log is from the collector to PC using UART, Different colors denote how many times that particular sensor tried the same message. Please check Time Stamp

And we test the same scenarios which our customer tested in Germany and found all test cases are working fine in India. But Our client-facing Sensor Retry many Times.xlsthe above issues.

Can I know, What could be the possible reasons why this pairing issue and sensor retrying occurs at our customer location?

Note:

1. We are using 3.3 SDK and what if we updated our SDK to the latest SDK release can this solve the issue of no association response and no ack from a collector?

2. We are using Custom boards for collectors and Sensors. My hardware team ensured that they used hardware as per TI design for CC1352R and CC1352P

As some issues are fixed with the latest SDK

  • Hi Haricharan, 

    We always recommend updating to the latest SDK if that is possible as it contains the latest bugfixes and newest features. 

    Can you test the SW using the LaunchPad and see if you see an issue? You can also double-check your design by running the examples from the SDK and see if you have the same issue. This way, we have tested both your HW and SW separately. 

    Thanks, 
    Elin