nRF51822 - Proprietary Protocol - Using micro_esb library - Need Help Improving TX Function

RE: nRF51822 - Proprietary Protocol - Using micro_esb library - Need Help Improving TX Function

Hung Bui — Tue, 11 Jul 2017 11:28:30 GMT

Well, it's depends on how many re-transmission you set, or if you enable re-transmission or not. You can have a look at the nRF51 radio spec to do calculation. It starts from RAMP-UP from TXRU to TXIDLE, then START and sending packet. Then the period to wait for ACK (if you enable ACK)

It's easiest that you can toggle a pin when you calling uesb_write_tx_payload, and toggle again when you receive the event.

One quesiton, which tx mode are you using ? UESB_TXMODE_AUTO or UESB_TXMODE_MANUAL*?

If you are using the default mode UESB_TXMODE_AUTO, why did you call uesb_start_tx() ? Please follow the micro esb example included on Github

RE: nRF51822 - Proprietary Protocol - Using micro_esb library - Need Help Improving TX Function

Mahonroy — Mon, 10 Jul 2017 19:03:59 GMT

Thanks for the response! You don't happen to know the time it takes for that event UESB_INT_TX_SUCCESS_MSK to occur do you?

RE: nRF51822 - Proprietary Protocol - Using micro_esb library - Need Help Improving TX Function

Hung Bui — Mon, 10 Jul 2017 11:11:03 GMT

Hi Mahonroy,

I'm sorry for late response. We are low on staff here at the moment.

I would suggest you instead of putting a delay of ms, you should wait for the event callback after the TX packet is sent. Please have a look here, at the uesb_event_handler. The event you should wait for is UESB_INT_TX_SUCCESS_MSK.

Also be noted that the micro esb is deprecated. We integrated it inside the normal ESB library in our SDK v11. We suggest you to use that library (SDK v11 and up) instead.

RE: nRF51822 - Proprietary Protocol - Using micro_esb library - Need Help Improving TX Function

Mahonroy — Fri, 07 Jul 2017 17:53:13 GMT

Hey guys, figured I would check back in on this. Can anyone offer any advice for me?