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.

Sign up for GitHub

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

Jump to bottom

question: auto sweep FSM #29

Open
hartytp opened this issue Jun 23, 2022 · 0 comments
Open

question: auto sweep FSM #29

hartytp opened this issue Jun 23, 2022 · 0 comments

Comments

@hartytp
Copy link

hartytp commented Jun 23, 2022 •
edited
Loading

I'm trying to understand the logic in the autosweep FSM. As far as I can tell it's roughly:

  • collectDataState = 0 waiting for a measurement to be requested
  • collectDataState = 1 wait for the start of a sweep to come around
  • collectDataState = 2 sweep finished
  • collectDataState = 3 wait for all values for an extra 5 frequency points to come through

What's the motivation around the collectDataState = 3 state? Why 5 more points? Any pointers appreciated!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hartytp