• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 366 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

LPSTK-CC1352R: Long range communication

Renan Santos Adriano
Mastermind 22380 points
Part Number: LPSTK-CC1352R
Other Parts Discussed in Thread: LAUNCHXL-CC1352R1

Hello Team,

My Customer is using LPSTK-CC1352R and they wanted to program for long range communication. Previously, they programmed the board with SDK RTOS collector program and LPSTK with the sensor but the range that I get is only a few meters. Do we have a sample program or guide for  LPSTK-CC1352R in long-range communication? 

Regrds,

Renan

  • 0
    TI__Guru**** 317180 points

    If they get a range of just a few meters either the hardware is faulty or they use a combination of SW and HW that is not ideal. If you get only a few meters it sound like the antenna is not connected or the RF switch is not selecting the correct RF path. 

    Please list the exact example you have used for both RX and TX.

    Suggested test:

    - Connect the boards using SmartRF Studio, use the 50 kbps. Set one board as Packet TX and the other as packet RX. 

    - If you get the expected range, test with the rfPacketRX/ rfPacketTX example in the SDK.

  • 0 in reply to TER
    TI__Mastermind 22380 points

    Hello TER,

    Thank you for this response.

    They have LPSTK-CC1352R sensor tag as Transmitter and CC1352R1 launchpad board ( LAUNCHXL-CC1352R1) as a receiver. They have used rfWsnNode SDK core for TX for reading analog in A3 and used rfWsnConcentrator as Rx but the range they got is only 10 meters.

    What modifications need to be done and how in node and concentrator code to achieve long rage up to 1000 meters for the same application? 

    Regards,

    Renan

  • 0 in reply to Renan Santos Adriano
    TI__Guru**** 317180 points

    Please start with the suggested tests in the previous post. 

    I would also set both boards you are using in TX (sending a CW) and check that they are actually sending on the same frequency. What you are seeing could be caused by a frequency offset between the boards. The internal load cap array could be set incorrectly with regards to what you have on your board. (see https://www.ti.com/lit/an/swra640e/swra640e.pdf for details)