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

Glitch filter unexpected callback #353

Closed

Conversation

BTPankow
Copy link
Contributor

This is addresses issue #350 by waiting to initialize the glitch filter values until samples are first processed for the glitch filter. This helps to avoid problems with timing between the SYST_CLO and sample ticks when setting gfTick.

I also added a test case onto the wavechain and filter test section (but could make it a separate test too). The test usually fails when x_pigpio.py is run remotely, but rarely does when run locally. I added a command line argument to x_pigpio.py to run with a remote Pi. All other tests pass with these changes.

guymcswain pushed a commit that referenced this pull request Jun 26, 2020
The glitch filter was not cleared on GPIO and GPIO2, causing errors when
rerunning tests.
guymcswain pushed a commit that referenced this pull request Jun 27, 2020
@guymcswain
Copy link
Collaborator

This patch was merged into v77. However, I left out the test since it used two gpio pins and both different from the current assumption that only GPIO 25 must be left unused. Thanks for the contribution.

@guymcswain guymcswain closed this Jun 28, 2020
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

Successfully merging this pull request may close these issues.

2 participants