• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 55 subscribers
  • Views 186 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.

CC1352P: strange behavior when errors happen

Rogerio Almeida
Mastermind 26205 points
Part Number: CC1352P

From Customer

I have been testing 802.15.4 on the CC1352P launchpad - I need the higher power - and have notice that when errors start occurring, the software seems to get behind and strange behaviors start happening. I put more time between transmissions and that mitigates the issue. But it brings up the question, is this because the firmware is having trouble keeping up, the communication link to the PC is an issue, or is the PC software falling behind. The airtime is expected to be completely filled in this application. The client end will need to be able to pick out and process its messages (turnaround time is TBD) and the gateway needs handle all the inbound traffic which will be 75-90% of the available data rate.

Another quirk is the payload, TX ID or sequence numbers will have issues but it does not seem to note if this passes CRC or not. The error rate observed would seem to indicate the data printed to the screen is raw data independent of the checksum. I am using 802.15.4 with a 100 byte random payload with sequence numbers. This behavior seems to be specific to 802.15.4, the testing I have done with BLE tends to log a CRC error message at the end of the line. .

  • 0
    TI__Genius 14845 points

    Hi Rogerio, 

    Which data rate are the customer using? How often do they send packets and how large are the packets? 

    Thanks, 
    Elin 

  • 0 in reply to Elin W
    Prodigy 30 points

    The data rate is 250kbps and the payload packet size is set to 100 bytes. The rep rate is the default within the launchpad application.

  • 0 in reply to Jim Kokal
    TI__Genius 14845 points

    Hi Jim, 

    Thanks for sharing. Can you explain in more detail what you are testing, how it fails, which examples you are using and what kind of modifications you have made to the projects? If you have any sniffer logs of this issue occurring, please share these. 

    Thanks, 
    Elin 

  • 0 in reply to Elin W
    Prodigy 30 points

    Testing the receiver sensitivity outdoors by measuring the message error rate. Set the receiver to process 1000 packets and turn on. Turn the transmitter on in infinite mode. The message is a 100 byte payload with sequence numbers. Log the data to a file. No modifications to any code has been made. When the signal level is high, all the messages are received correctly. As the signal level is reduced a number of different errors begin to occur.

    Below is one of the log files. It starts at message 0000 and stops at 0904. There are errors in TXID, the sequence number (being outside the range), missing parts of the payload, and errors in the payload. None are marked as issues.

  • 0 in reply to Jim Kokal
    TI__Genius 14845 points

    Hi Jim, 

    Thanks for sharing. I have edited your post and removed the log to improve the readability of this post and the log. Please attach it as a file instead. 

    Please share a list of steps on how to modify the projects from the SDK to reproduce this issue. 

    Thanks, 
    Elin 

  • 0 in reply to Elin W
    Prodigy 30 points

    No changes were made to the SDK. Just standard parameters for 802.15.4. Use the GUI to set it to a 100 byte payload.

    This issue seems specific to 802.15.4. 

    Jim

  • 0 in reply to Jim Kokal
    TI__Genius 14845 points

    Hi Jim, 

    Which GUI are you referring to?

    Jim Kokal said:
    This issue seems specific to 802.15.4. 

    What kind of other tests have you performed to come to this conclusion?

    Thanks, 
    Elin