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.

RTOS/CC1350: Very low range for CC1350 REV B Rx

Part Number: CC1350


Tool/software: TI-RTOS

I use CC1350 REV B as keyfob 2 way on 433Mhz, with propriety protocol Manchester base. 

It is base on the examples for rfPacketRx and rfPacketTx, where on the TX use patch get from TI and on the Rx use the Transparent to PIN/FIFO and low level decoding.

I am using tirtos_cc13xx_cc26xx_2_21_00_06 with IAR 7.50

The antenna is a printed one which was use already with a simple transceiver and work fine.
On the TX I get a good results but on Rx I get a very short range (about some cm!!).

Do anybody already use the CC1350 REV B as a receiver and get a good sensitivity? If so what SDK, or special setting it use?

Thanks

Bar.

  • Is this request tied to the questions you have sent to the direct support mail address?

    > The antenna is a printed one which was use already with a simple transceiver and work fine.
    The antenna tuning change with the size of the board, casing etc. What range do you get if you use the rfPacketTx and rfPacketRx examples unmodified (50 kbps GFSK to check if the hardware is ok)
    > On the TX I get a good results but on Rx I get a very short range (about some cm!!).
    A link has a TX and a RX side. How do you know that the TX is ok and it's the RX that gives poor range?
  • TER said:
    Is this request tied to the questions you have sent to the direct support mail address?


    The antenna tuning change with the size of the board, casing etc. What range do you get if you use the rfPacketTx and rfPacketRx examples unmodified (50 kbps GFSK to check if the hardware is ok)

    I also check it conducted without the antenna and some results. poor sensativity.

    I can't use the example because I use the special case of transparent to PIN and OOK with there special parameters.

  • I'm aware that you have to use transparent OOK in your application. We have done a lot of testing with 50 kbps and therefore know the expected TX and RX performance. When customers report on poor performance using custom hardware and software it is a lot easier to help if it's known if it's the hardware or software (or both) that is the main contributor to the poor performance. To know this tests has to be done with known hardware/ known software. Also see the debug tab in the excel sheet in e2e.ti.com/.../375556

    A few cm range indicate something fundamentally wrong but from the information provided it's not possible to tell what.