Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If both transmitter and receiver frequently change channels on the same sequence, #1

Open
desertkun opened this issue Nov 17, 2019 · 1 comment

Comments

@desertkun
Copy link

what stops them from reaching situation where they never actually catch each other and constantly jump on the same sequence, but with shifted index of the sequence array?

@philj404
Copy link

philj404 commented Jul 6, 2020

The interesting part is in the file RX_FHSS.c, in the first half of loop(). The boolean fhss_on keeps track of whether the receiver is synchronized with the transmitter yet.

  • The receiver does not hop by default. It listens on a channel until the transmitter sends something on it.
  • Sometimes a 2.4GHz channel might NEVER work -- for example when the receiver is right next to a busy WiFi base station. If the receiver never sees a valid packet in a certain amount of time (several cycles) it gives up on that channel and tries listening on the next channel.
  • Once it sees a valid data packet, the receiver starts hopping at the same rate and sequence as the transmitter.
  • If the receiver hasn't seen valid data "in a while" it starts searching again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants