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

Requires fuzzy timing #1

Open
mrnebbi opened this issue Jun 9, 2021 · 1 comment
Open

Requires fuzzy timing #1

mrnebbi opened this issue Jun 9, 2021 · 1 comment

Comments

@mrnebbi
Copy link
Owner

mrnebbi commented Jun 9, 2021

The system can currently decode Morse Code messages provided they are flashes by an app, or it can decode letters like "S" easily as they are easier to flash in the correct sequence with the correct timing. However, it seems to be struggling where human messages are being presented, likely due to the differences in timings between off states.

A more fuzzy timing system would work better, with a longer delay before trying to read the message and looser definitions of what a short of long are.

@mrnebbi
Copy link
Owner Author

mrnebbi commented Jun 9, 2021

5 WPM

baseline set to 85
0 0 246 245 247
0 0 726 726 726
0 0 244 245 242
SOS

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

1 participant