• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 306 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.

CCS/CC1310: 4-mm*4-mm,128kb

user6500366
Prodigy 10 points
Part Number: CC1310


Tool/software: Code Composer Studio

dear companion：

  There are the following problems: small external interference, under normal circumstances: the packet on the sending side of the device presents three forms at the receiving side: 1. The packet verification error on the receiving side; 2. The packet cannot be received in some time period; 3.What is the cause of this, and does the data processing mechanism within the RF have an impact?Can you describe the mechanism for handling problems within the RF or provide a function body。

instance：

15:57:07.682 | 0d | cf 0d 00 02 03 69 2b 24 15 2a 01 4b 97  |  -87

15:57:35.689 | 0d | cf 0d 00 02 03 46 2b 25 15 2a 01 4b f7  |  -84

15:58:03.697 | 0d | cf 0d 00 02 03 52 2b 25 15 2a 01 4b f8  |  -86

16:18:07.993 | 0d | cf 0d 00 02 12 aa aa aa a8 5a 8e f0 6e  |  -87 CRC error

16:18:36.000 | 0d | cf 0d 00 02 03 95 55 55 55 42 d4 77 83  |  -86 CRC error

16:19:04.009 | 0d | cf 0d 00 02 03 52 aa aa aa a8 5a 8e f0  |  -86 CRC error

16:19:32.017 | 0d | cf 0d 00 02 03 52 25 55 55 55 50 b5 1d  |  -87 CRC error

16:20:00.023 | 0d | cf 0d 00 02 03 52 2a 95 55 55 55 42 d4  |  -85 CRC error

16:20:28.032 | 0d | cf 0d 00 02 03 69 2b 21 55 55 55 55 0b  |  -86 CRC error

16:20:56.040 | 0d | cf 0d 00 02 03 52 2b 21 14 aa aa aa aa  |  -86 CRC error

16:21:24.047 | 0d | cf 0d 00 02 03 52 2b 21 15 26 ba aa aa  |  -86 CRC error

16:21:52.055 | 0d | cf 0d 00 02 03 5d 2b 21 15 2f 95 55 55  |  -85 CRC error

16:22:20.062 | 0d | cf 0d 00 02 03 52 2b 21 15 2d 02 75 55  |  -86 CRC error

16:22:48.072 | 0d | cf 0d 00 02 03 52 2b 25 15 26 01 49 6a  |  -85 CRC error

16:23:16.079 | 0d | cf 0d 00 02 03 5d 2b 25 15 26 01 4d 95  |  -87 CRC error

16:23:44.087 | 0d | cf 0d 00 02 03 5d 2b 21 15 2d 01 4d 04  |  -86 CRC error

16:24:12.094 | 0d | cf 0d 00 02 03 52 2b 25 15 2f 01 4d 10  |  -85 CRC error

16:24:40.101 | 0d | cf 0d 00 02 03 69 2b 24 15 31 01 4d c1  |  -86

16:25:08.109 | 0d | cf 0d 00 02 03 52 2b 21 15 31 01 4d b1  |  -86

The sensor did not send a message, and the receiver received a CRC error at 12 minutes

Occasionally appear：cf 0d 00 07 03  | -103 CRC error；

  • Specialty error packs are not described

  • 0
    TI__Guru* 86741 points

    Not sure I understand your question.

    First of all, it would be useful to have info regarding how your are testing, what HW you are running, what RF settings you are using and what SW you are using.

    It seems like you are using SmartRF Studio as the receiver.

    If your receiver finds the programmed sync word, it will receive as many bytes as indicated by the length byte (if using variable packet length mode), or as indicated by the length filed in the receive command (if using fixed packet length mode). A CRC is calculated over the received payload, and if the calculated CRC does not match the received CRC bytes in the end of the packet, you have a CRC error.

    If no sync word is found, nothing is received.

    It is fully possible to receive noise that looks like preamble, even if your transmitter is not sending anything.

    CRC errors, or not receiving anything at all is either because of a bad RF design, interference on the air on the same frequency that you are trying to communicate, or that you are getting close to the sensitivity limit

    BR

    Siri