https://devzone.nordicsemi.com/f/nordic-q-a/17661/gazell-transmit-failure-nrf51-sdk10I have a bit of a strange problem. I am designing a signal Gazell signal repeater. It listens in host mode then sets itself as a device to pass the data along. However if the data being passed to the transmit fifo does not change it does not transmiten-USTelligent Community 13Fri, 11 Nov 2016 12:16:40 GMThttps://devzone.nordicsemi.com/thread/67931?ContentTypeID=1Fri, 11 Nov 2016 12:16:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4d7c8943-21df-4286-97c3-99c4a2eee7f1Elliott Makin<p>Thank you - this explains what I have encountered.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/67930?ContentTypeID=1Fri, 11 Nov 2016 11:58:53 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8fd2488b-9ff9-4b1f-a3cb-854a2a78c5a6Hung Bui<p>@Elliott: I guess that you re-initialize the repeater every time you switch the role ? Doing that the first packet the device send will look the same to the host on the other side and it can be discarded as re-transmission package since the CRC and the 2 bit PID are the same (check out the Enhanced Shockburst Userguide). PID is increased after every successful packet, but in this case you reinitialize every time you send a package, so it will be 00 on all packets.</p> <p>The easiest solution is to add one more byte to the payload to work as a counter for example, so that the payload is different every time you transmit.</p><div style="clear:both;"></div>