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

F7 Frequency/Duty Cycle not right #807

Open
ctacke opened this issue Jan 1, 2025 · 0 comments
Open

F7 Frequency/Duty Cycle not right #807

ctacke opened this issue Jan 1, 2025 · 0 comments
Assignees
Labels

Comments

@ctacke
Copy link
Contributor

ctacke commented Jan 1, 2025

Using the new 2.x frequency and duty cycle measurement features on the F7.

Instantaneous frequency measurements seem fine (tested 1Hz to 100kHz).

However, if I set input duty cycle (DC) to 50%, the API is giving me back 0.0 until about A 6Khz, at which point it shifts to giving sometimes ~0.53 and sometimes still 0.0.

The average frequencies are also incorrect. I get 0.0 until the input gets above about 2kHz. Even at that point, the reported average is ~7kHz.

There is a sample app in PR state right now:
https://github.com/WildernessLabs/Meadow.Samples/pull/57/files

And the Core bits that make the call are also currently in a PR:
https://github.com/WildernessLabs/Meadow.Core/blob/373c047469f459766c5ece003433a3e03651848d/Source/implementations/f7/Meadow.F7/Devices/F7DigitalSignalAnalyzer.cs#L68

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

No branches or pull requests

2 participants