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

Review the meaning of overrun in the docs #10

Open
dotdoom opened this issue Jun 19, 2016 · 0 comments
Open

Review the meaning of overrun in the docs #10

dotdoom opened this issue Jun 19, 2016 · 0 comments
Assignees

Comments

@dotdoom
Copy link
Member

dotdoom commented Jun 19, 2016

Overrun is actually not overflow but a signal that a new value was written to the register before the previous was read (i.e. reading rate is too slow). An appropriate error/warning needs to be generated.

Additionally, to improve reading rate we should not read configuration registers while reading the output; last set config option should be cached. Might also consider simplifying the methods for acquisition, e.g. disable "number of acquisitions" in continuous mode.

@dotdoom dotdoom self-assigned this Jun 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant