Gazell Ack not received after data transfer

RE: Gazell Ack not received after data transfer

ovrebekk — Mon, 17 Oct 2016 08:44:18 GMT

Hi Kevin

I assume you have read the Gazell user guide? This, combined with the API reference, is all the documentation we have for the Gazell library.

For 250kbps to work properly you might have to increase the timeslot period, since the packet takes longer to send at the slower bitrate.

RE: Gazell Ack not received after data transfer

Kevin — Sun, 16 Oct 2016 23:50:21 GMT

The problem seems to be caused by setting the data rate to 250 kbit incorrectly. Once I switched the data rate back to default, the problem went away and the acks came through without a problem. I shifted my nrf_gzll_set_datarate(NRF_GZLL_DATARATE_250KBIT) call to be before nrf_gzll_init() call and that seemed to work

Since there's no documentation I can find on setting the datarate, I'm assuming that was the cause of the problem. If anyone can provide me with a link to where I could read a little more on setting gazell parameters like datarate, or just confirm whether I've diagnosed this correctly, I'd appreciate it.

Thanks.

RE: Gazell Ack not received after data transfer

Kevin — Sun, 16 Oct 2016 00:59:35 GMT

Follow up comment on this problem: Actually, the send isn't being fully received, just the first character of the send. I was originally just sending a status bit, but as I tried to send more information, I noticed that if the payload was more than 1 byte, it also wasn't being received properly by the host, so that's likely where it's breaking down.