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

Message handling should be restricted according to machine state #151

Open
t0mpr1c3 opened this issue Sep 18, 2023 · 0 comments · May be fixed by #154
Open

Message handling should be restricted according to machine state #151

t0mpr1c3 opened this issue Sep 18, 2023 · 0 comments · May be fixed by #154
Assignees
@t0mpr1c3
Labels
code quality

Comments

@t0mpr1c3
Copy link
Contributor

At the moment the firmware will basically handle any message that it is sent, at any time. It should be more restrictive, reflecting the program control in the desktop software. For example, it should only respond to test instructions when in state OpState::test. This will help guard against communication errors.
@t0mpr1c3 t0mpr1c3 linked a pull request Sep 26, 2023 that will close this issue
Finite Machine states inherit from OpInterface #154
Draft
@t0mpr1c3 t0mpr1c3 self-assigned this Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@t0mpr1c3 t0mpr1c3

Labels
code quality
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Finite Machine states inherit from OpInterface t0mpr1c3/ayab-firmware
1 participant
@t0mpr1c3