• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 193 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC1310: Unable to use CC1352R as collector and communicate with CC1310 as sensor.

Owen Brown
Prodigy 140 points
Part Number: CC1310
Other Parts Discussed in Thread: CC1352R

The CC1352R and CC1310 use different TI examples & SDKs.

I can flash the CC1352R as a collector using collector_CC1352R1_LAUNCHXL_tirtos_ccs_syscfg (SDK version: simplelink_cc13x2_26x2_sdk_3_40_00_02). This works and can connect to other CC1352R sensors.

I can flash the CC1310 as a collector using sensor_CC1310_LAUNCHXL_tirtos_ccs (SDK simplelink_cc13x0_sdk_3_20_00_23). This works and can connect to other CC1310 sensors.

This issue is with a CC1362R collector and a CC1310 sensor. They do connect but then I get !Responding messages on collector terminal port and don't see sensor updates and rarely updates LED status on sensor.

  • 0
    TI__Mastermind 25810 points

    Hey Owen,

    I was not able to reproduce the symptoms described above. What mode/PHY rate are you using? Are you running the examples on LaunchPads?

    I connected two launchpads running out of the box software with no changes with the SDK's listed above. I see the sensor connect and send updates as usual. Is your setup different?

  • 0 in reply to Ammar N
    Prodigy 140 points

    I have the issue using APIMAC_GENERIC_US_LRM_915_PHY_129 on both collector and sensor.

    It does work with APIMAC_STD_US_915_PHY_1.

  • 0 in reply to Owen Brown
    TI__Mastermind 25810 points

    Hey Owen,

    Thanks for the clarification. I pulled up a sniffer and saw the sensor was not sending data.

    The reason for what you're seeing is because the newer firmware has changed the polling/reporting intervals. The sensor reporting interval is ~5min, when the collector is expecting data every 3 seconds. After modifying the polling/reporting intervals in the sensor's config.h file to match the collector, I saw no issue.