RE: gazell pros and cons (and timeslot sync threshold)

astella — Tue, 24 Mar 2020 18:22:37 GMT

Hi Kenneth, thank you. I was thinking to evaluate a custom schema having a master with no power constraints, that is always sending a token in a round robin fashion. When devices wake up because they have got data to send, they first listen for the token.I'll try to simulate something before implementing, to be sure it is applicable in my case.

Thank you for your kindness

RE: gazell pros and cons (and timeslot sync threshold)

Kenneth — Tue, 24 Mar 2020 11:08:43 GMT

Hi,

There is no short answer to your questions. The Gazell protocol is built on the ESB link layer. Using ESB you simply specify an address and frequency used by the receiver, then send the packet you want to transmit, next you will either get an tx success or max retransmit callback. You would need to build everything around this simplistic ESB api, for instance frequency hopping, synchronization, and how to handle max retransmit callback. It can be done, but at the end of the day I am not sure if it's worth the development time. Using Gazell, even with some of it's drawbacks, likely is the preferred solution, provided that Gazell can meet your overall requirements to throughput and latency.

Best regards,
Kenneth