MAX_RT interrupt still happens even if retransmit is off

RE: MAX_RT interrupt still happens even if retransmit is off

ovrebekk — Tue, 30 Jul 2019 12:33:11 GMT

No problem, the best of luck 🙂

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Tue, 30 Jul 2019 07:30:36 GMT

OK. Thank your information. I will look at that.

RE: MAX_RT interrupt still happens even if retransmit is off

ovrebekk — Mon, 29 Jul 2019 11:55:57 GMT

Sorry for the late reply, I was on vacation for the last two weeks.

You should be able to extend the hal_nrf_write_multibyte_reg function to support the WR_NAC_TX_PLOAD, by adding another case in the switch for WR_NAC_TX_PLOAD.

If you want to have a look at my code I made it available here:
https://github.com/ovrebekk/nrf52-l01-hal-example

It is based on nAN24-12, but I have made some small changes to it, including a more generic way of handling the write_multibyte function.

Best regards
Torbjørn

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Tue, 23 Jul 2019 08:43:25 GMT

I tried to follow all of your codes. However, the same problem, the system still cannot receive any TX_DS after sending packets. After tracing the root cause, I found hal_nrf_write_multibyte_reg() does not have any codes to handle 0xB0 command (WR_NAC_TX_PLOAD). I copy hal_nrf_write_multibyte_reg() below.

I think the key problem now is my RF library (nAN24-12 version 2.1 subversion 2624) is much different from yours, so I cannot use your code directly. May I know what RF library do you use? If possible, could you also provide the link as well? we will evaluate if we will upgrade our library to your version or not if the effort is not big. If the change is big, I think we will give up this problem, because this issue MAX_RT event is just a trivial issue. In addition, you have provided a solution mentioned above to treat MAX_RT as the TX_DS case, and we have changed it in our codes.

---

void hal_nrf_write_multibyte_reg(uint8_t reg, uint8_t *pbuf, uint8_t length)
{
switch(reg)
{
case HAL_NRF_PIPE0:
case HAL_NRF_PIPE1:
case HAL_NRF_TX:
length = hal_nrf_get_address_width();
CSN_LOW();
hal_nrf_rw(WRITE_REG + RX_ADDR_P0 + reg);
break;

case HAL_NRF_TX_PLOAD:
CSN_LOW();
hal_nrf_rw(WR_TX_PLOAD);
break;
default:
break;
}

while(length--)
{
hal_nrf_rw(*pbuf++);
}

CSN_HIGH();
}

RE: MAX_RT interrupt still happens even if retransmit is off

ovrebekk — Wed, 10 Jul 2019 12:11:22 GMT

As long as the value is 0xB0 the name is irrelevant, so you can use that define, yes 🙂

Best regards
Torbjørn

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Wed, 10 Jul 2019 07:30:11 GMT

In my library, I did not find `W_TX_PAYLOAD_NOACK`, but I find `WR_NAC_TX_PLOAD` below. I think the definition of `W_TX_PAYLOAD_NOACK` is the same as`WR_NAC_TX_PLOAD`, right? Please double confirm in case any unexpected issue happens.

#define WR_NAC_TX_PLOAD 0xB0

RE: MAX_RT interrupt still happens even if retransmit is off

ovrebekk — Wed, 10 Jul 2019 06:50:45 GMT

The function looks like this:

void hal_nrf_write_tx_payload_noack(const uint8_t *tx_pload, uint8_t length)
{
hal_nrf_write_multibyte_reg(W_TX_PAYLOAD_NOACK, tx_pload, length);
}

It is identical to the normal TX function, except the command byte is 0xB0 (W_TX_PAYLOAD_NOACK) instead of 0xA0 (W_TX_PAYLOAD).

[quote user="harryAI"]Another question: I saw you call `hal_nrf_set_rx_payload_width(HAL_NRF_PIPE0, 8);`. My question is since we already enable dynamic payload `hal_nrf_enable_dynamic_payload(true);`, why do we still need to call set payload width?[/quote]

You are correct. There is no need to set the payload length when using dynamic payload length, and this line can safely be removed from the code.

[quote user="harryAI"]By the way, the data rate in my test is 250K bps (yours is HAL_NRF_2MBPS). I think this will not affect anything, but still mention this difference.[/quote]

Thanks for the information. I agree this should not make a difference in this case.

Best regards
Torbjørn

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Tue, 09 Jul 2019 07:08:00 GMT

Hi Torbjorn,

I check my code. I use `hal_nrf_write_tx_pload()` to send payload.

I want to try your codes, but I found my nRF libraries does not have `hal_nrf_write_tx_payload_noack(..)` this function. Could you paste this function to me?

Another question: I saw you call `hal_nrf_set_rx_payload_width(HAL_NRF_PIPE0, 8);`. My question is since we already enable dynamic payload `hal_nrf_enable_dynamic_payload(true);`, why do we still need to call set payload width?

By the way, the data rate in my test is 250K bps (yours is HAL_NRF_2MBPS). I think this will not affect anything, but still mention this difference.

RE: MAX_RT interrupt still happens even if retransmit is off

ovrebekk — Fri, 05 Jul 2019 10:14:45 GMT

That looks fine, I guess it's a slightly different implementation of the hal_nrf libraries.

Did you add the dynamic ACK configuration?

If yes, did it change the behavior?

If it still doesn't work, can you send me the code you use to upload packets, and a printout of your config register after you have configured the device?

Best regards
Torbjørn

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Fri, 05 Jul 2019 06:27:28 GMT

> Are you able to send me the implementation of the hal_nrf_enable_dynamic_pl() function?

Here you are.

void hal_nrf_enable_dynamic_pl(void)
{
hal_nrf_write_reg(FEATURE, (hal_nrf_read_reg(FEATURE) | 0x04));
}

void hal_nrf_disable_dynamic_pl(void)
{
hal_nrf_write_reg(FEATURE, (hal_nrf_read_reg(FEATURE) & ~0x04));
}

RE: MAX_RT interrupt still happens even if retransmit is off

ovrebekk — Thu, 04 Jul 2019 12:01:09 GMT

Are you able to send me the implementation of the hal_nrf_enable_dynamic_pl() function?

In my version of the HAL library this function needs to be provided a bool argument, allowing you to enable or disable the feature.

I realize now that I forgot to mention that you have to call hal_nrf_enable_dynamic_ack(true) also if you want to use the noack feature.

Below is my own test code to verify that this is working:

hal_nrf_set_operation_mode((config->mode == APP_RADIO_MODE_PTX) ? HAL_NRF_PTX : HAL_NRF_PRX);

hal_nrf_set_power_mode(HAL_NRF_PWR_UP);

nrf_delay_us(1500);

hal_nrf_set_crc_mode(HAL_NRF_CRC_16BIT);

hal_nrf_set_auto_retr(0, 500);

hal_nrf_close_pipe(HAL_NRF_ALL);
hal_nrf_open_pipe(HAL_NRF_PIPE0, true);

hal_nrf_set_address_width(5);

hal_nrf_setup_dynamic_payload(0x3F);
hal_nrf_enable_dynamic_payload(true);
hal_nrf_enable_dynamic_ack(true);

hal_nrf_set_datarate(HAL_NRF_2MBPS);

hal_nrf_set_rf_channel(2);

if(config->mode == APP_RADIO_MODE_PTX)
{
hal_nrf_flush_tx();
}
else
{
hal_nrf_flush_rx();
hal_nrf_set_rx_payload_width(HAL_NRF_PIPE0, 8);
}

And then I send my packets using the hal_nrf_write_tx_payload_noack(..) function, which removes the ACK requirement from the packet.

Best regards
Torbjørn

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Fri, 28 Jun 2019 08:53:23 GMT

Hi Torbjorn,

I follow your comments, but RF does not produce any TX_DS interrupt event anymore. The whole system cannot work.

I just copy my codes below (remove all comments to save space). Could you please help to check what's matter.

void radio_pl_init (uint8_t *address, hal_nrf_operation_mode_t operational_mode,
uint8_t rfChannel, hal_nrf_datarate_t airRate)
{
hal_nrf_close_pipe(HAL_NRF_ALL);
hal_nrf_open_pipe(HAL_NRF_PIPE0, true);
hal_nrf_set_crc_mode(HAL_NRF_CRC_16BIT);
hal_nrf_set_auto_retr(0, RF_RETRANS_DELAY);
hal_nrf_set_address_width(HAL_NRF_AW_5BYTES);
hal_nrf_set_address(HAL_NRF_TX, address);
hal_nrf_set_address(HAL_NRF_PIPE0, address);

//hal_nrf_enable_ack_pl(); // Try to enable ack payload

if(hal_nrf_read_reg(FEATURE) == 0x00 && (hal_nrf_read_reg(DYNPD) == 0x00))
{
hal_nrf_lock_unlock (); // Activate features
//hal_nrf_enable_ack_pl(); // Enables payload in ack
}

hal_nrf_enable_dynamic_pl();
hal_nrf_setup_dyn_pl(ALL_PIPES);

if(operational_mode == HAL_NRF_PTX)
{
hal_nrf_set_operation_mode(HAL_NRF_PTX);
}
else
{
hal_nrf_set_operation_mode(HAL_NRF_PRX);

// Disable this. Use dynamic payload, so no need to set the fixed payload length.
//hal_nrf_set_rx_pload_width((uint8_t)HAL_NRF_PIPE0, RF_PAYLOAD_LENGTH);
}

hal_nrf_set_rf_channel(rfChannel);
hal_nrf_set_power_mode(HAL_NRF_PWR_UP);
hal_nrf_set_datarate(airRate);
start_timer(RF_POWER_UP_DELAY);
wait_for_timer();

//radio_set_status (RF_IDLE);
}

RE: MAX_RT interrupt still happens even if retransmit is off

ovrebekk — Thu, 27 Jun 2019 07:35:28 GMT

That sounds good.

If you have any more problems just let me know 🙂

Best regards
Torbjørn

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Wed, 26 Jun 2019 09:13:04 GMT

Yes, I need dynamic payload length.

Therefore, my codes will call

* run hal_nrf_open_pipe(HAL_NRF_PIPE0, true),

* hal_nrf_setup_dyn_pl(ALL_PIPES)

* hal_nrf_enable_dynamic_pl().

and will NOT call (comment out)

* hal_nrf_enable_ack_pl();

Got it. thank you very much.

RE: MAX_RT interrupt still happens even if retransmit is off

ovrebekk — Wed, 26 Jun 2019 08:15:56 GMT

Do you need dynamic payload length or not?

If you don't need dynamic payload length you can just run hal_nrf_open_pipe(HAL_NRF_PIPE0, false), and make sure not to run hal_nrf_enable_ack_pl(), hal_nrf_enable_ack_pl(), hal_nrf_enable_dynamic_pl() or hal_nrf_setup_dyn_pl(ALL_PIPES).

If you need dynamic payload length the only way to achieve this is to run hal_nrf_open_pipe(HAL_NRF_PIPE0, true), hal_nrf_setup_dyn_pl(ALL_PIPES) and hal_nrf_enable_dynamic_pl().

The reason for this is that enabling the pipe with EN_AA = 0 removes the 9 bit PCF field in the payload which is used to support the dynamic payload length, ACK payload and dynamic ACK features.

In the documentation this might be referred to as either Shockburst mode (EN_AA = 0), or Enhanced Shockburst mode (EN_AA = 1).

Best regards
Torbjørn

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Tue, 25 Jun 2019 08:30:54 GMT

> If you want to disable ACK's while using the dynamic payload length feature you should enable ACK in the EN_AA register and enable the dynamic ACK feature, so that you can send packet without ACK even if EN_AA is enabled

Based on your comments, so my codes need to change as follows, right? (Please help to confirm).

hal_nrf_open_pipe(HAL_NRF_PIPE0, true); // Then open pipe0, w/autoack -> Harry: enable EN_AA Ack

// hal_nrf_enable_ack_pl(); // Try to enable ack payload -> Harry: comment out two lines of these codes

However, I have one question. Since I don't want ACK, why can I disable EN_AA as well, i.e.,

hal_nrf_open_pipe(HAL_NRF_PIPE0, false);

RE: MAX_RT interrupt still happens even if retransmit is off

ovrebekk — Mon, 24 Jun 2019 09:53:21 GMT

This might explain the problem. Using features like ACK payload, dynamic payload length or dynamic ACK are not compatible with clearing the EN_AA register (ie disabling ACK's).

Either you have to enable ACK's through the EN_AA register and use these features, or you have to disable these features completely.

If you want to disable ACK's while using the dynamic payload length feature you should enable ACK in the EN_AA register and enable the dynamic ACK feature, so that you can send packet without ACK even if EN_AA is enabled.

I did some testing on my own, and after a million packets I don't see a single MAX_RT interrupt occur, but in my testing I didn't enable ack payload and dynamic payload length.

Best regards
Torbjørn

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Mon, 24 Jun 2019 02:51:38 GMT

> How many packets did you send in that time, when you got 2 or 3 packets with MAX_RT?

When MAX_RT happens, RF is sending packet every 250ms, i.e., 4 packets every 1 second for reporting a periodically information. The period is lasting for about 1 ~ 2 hours.

> I do have one question, why the 0x1C and 0x1D registers are set?

I just adopt the sample codes of dynamic payload, and Nordic sample codes change 0x1C and 0x1D registers in `radio_pl.c`. Copy the codes as follows:

/*****************************************************************************
* Changed from esb/radio_esb.c *
* Enables: *
* - ACK payload *
* - Dynamic payload width *
* - Dynamic ACK *
*****************************************************************************/
hal_nrf_enable_ack_pl(); // Try to enable ack payload

// When the features are locked, the FEATURE and DYNPD are read out 0x00
// even after we have tried to enable ack payload. This mean that we need to
// activate the features.
if(hal_nrf_read_reg(FEATURE) == 0x00 && (hal_nrf_read_reg(DYNPD) == 0x00))
{
hal_nrf_lock_unlock (); // Activate features
hal_nrf_enable_ack_pl(); // Enables payload in ack
}

hal_nrf_enable_dynamic_pl(); // Enables dynamic payload
hal_nrf_setup_dyn_pl(ALL_PIPES); // Sets up dynamic payload on

RE: MAX_RT interrupt still happens even if retransmit is off

ovrebekk — Fri, 21 Jun 2019 12:46:49 GMT

How many packets did you send in that time, when you got 2 or 3 packets with MAX_RT?

I have put up a small test and will leave it over the weekend, to see if I can record any MAX_RT interrupts. So far I have sent over 15000 packets and I have only seen TX_DS interrupts.

I do have one question, why the 0x1C and 0x1D registers are set?
These features don't work when ACK's are disabled, and are usually set to 0 in this case.

Best regards
Torbjørn

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Thu, 20 Jun 2019 06:59:15 GMT

Here you are. The statuses are printed after RF initialization when power-on. The RF has not transmitted any data.

By the way, the reproduce rate of this issue is very low. I just saw twice or three times for a very long time. If you cannot reproduce this issue, I don't know how to distinguish (A) RF module has bug, but just has not happen or (B) the genuine RF module does not have this bug. Anyway, still prove the RF register values to you.

Nordic nRF24L01+ Register values
Reg 0x00: 0E
Reg 0x01: 00
Reg 0x02: 01
Reg 0x03: 03
Reg 0x04: 10
Reg 0x05: 4F
Reg 0x06: 27
Reg 0x07: 0E
Reg 0x08: 00
Reg 0x09: 00
Reg 0x0A: 52
Reg 0x0B: C2
Reg 0x0C: C3
Reg 0x0D: C4
Reg 0x0E: C5
Reg 0x0F: C6
Reg 0x10: 52
Reg 0x11: 00
Reg 0x12: 00
Reg 0x13: 00
Reg 0x14: 00
Reg 0x15: 00
Reg 0x16: 00
Reg 0x17: 11
Reg 0x1C: 3F
Reg 0x1D: 06

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Wed, 19 Jun 2019 13:01:01 GMT

> Can you do a readout of all the configuration registers in the nRF24L01+ and send it to me?

Could you give me your email? I can send to you via email.

RE: MAX_RT interrupt still happens even if retransmit is off

ovrebekk — Wed, 19 Jun 2019 07:48:49 GMT

Can you do a readout of all the configuration registers in the nRF24L01+ and send it to me?

Then I can try to replicate your setup, and see if I spot the same issue on my end.

You might also want to purchase some modules from a known genuine source, and see if the problem is the same.
In China we work with a distributor called Xuntong, and they are making some modules based on the nRF24L01+ that we know to be genuine:
http://freqchina.com/plus/view.php?aid=1091

Best regards
Torbjørn

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Tue, 18 Jun 2019 07:55:36 GMT

The picture is as follow. The text on the chip line by line is

"NRF O"

"24L01+"

"1621LR"

PS: The picture is already took by iPhone, but I know the picture is a little blur. If you do really need to see a clear text from the picture, I can use a better camera (if I have) to take another picture.

RE: MAX_RT interrupt still happens even if retransmit is off

ovrebekk — Mon, 17 Jun 2019 13:36:11 GMT

For some reason I can't open the product page, just the www.ai-thinker.com main page.

Are you able to send a link to the image directly, or attach the image to this case?

Also, are you able to read the full text printed on the chip?

Best regards
Torbjørn

RE: MAX_RT interrupt still happens even if retransmit is off

harryAI — Mon, 17 Jun 2019 08:43:35 GMT

> Are you using a nRF24L01+ module?

Sorry, I miss the answer of this question. Yes, the mark on the chip shows nRF24L01+.