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.

  • Resolved

CC1352R: Is there any alternative prop commands to CMD_IEEE_RX_ACK

Intellectual 510 points

Replies: 2

Views: 63

Part Number: CC1352R

Hi TI expert,

I was wondering if there is any alternative proprietary command to the CMD_IEEE_RX_ACK?  CMD_IEEE_RX_ACK is very useful to check the ACK message timeout, but I couldn't figure out a good approach to deal with the similar situation in sub-1 mode.

Some posts suggest to use "RF_cmdPropTx.pNextOp = (RF_Op*) &RF_cmdPropRx;" but it assumes the ACK is the piggybacked (the ACK is the next received message after transit). This hypothesis is not always true in the real situations.

Could you give some suggestions on what is the practical methods to deal with the auto-ACK situation in Proprietary mode.

Thank you very much in advance,

Kind regards,

  • Guru 252120 points

    Since prop can be used to implement a wide selection of standards, prop doesn't have a 'ACK' command. 

    Hence your best option is to chain commands as shown in http://dev.ti.com/tirex/explore/node?node=AMWGQAr.6MV9a9rMY8cU-A__pTTHBmu__LATEST&search=debug 

    If you are writing your own protocol you have full control over when you send and ack and when you have to listen for one meaning that this method should give you the flexibility you need. 

     

  • In reply to TER:

    Hi Ter,

    Sorry to late response. I checked the sample (regarding auto-ack in prop mode) that uses command chain to receive 'ACK' after transmit. But it a little confuses me that the RF_cmdPropRx has to be called again after RF_cmdPropTx command executes. 

    Chapter 25.5.4 in TRM mentioned "In IEEE 802.15.4 mode, the radio CPU accepts two levels of radio operation commands. Operations can run in the background level or in the foreground level.",  the Tx command is able to run in front of Rx command, so that the Rx command can be execute only one time.

    I assume the prop does not support combinations of Foreground and Background Level Operations?  So Rx command has to be chained after Tx? Also, whenever I want to send a packet using TX command I have to abort the running Rx command first?

    Thank you very much for your support, as always!

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.