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

pulseIn/pulseOut accuracy #6

Closed
LeventErkok opened this issue Mar 1, 2013 · 1 comment
Closed

pulseIn/pulseOut accuracy #6

LeventErkok opened this issue Mar 1, 2013 · 1 comment

Comments

@LeventErkok
Copy link
Owner

The implementation of pulseIn and pulseOut is inherently inaccurate.

The issue exists for both functions, as the Firmata communication overhead inherently adds inaccuracy to measurements. However, I've found that pulseOut is relatively OK for practical uses. However, pulseIn is unlikely to be useful for any sort of fine measurement (as would be required for distance sensing sensors, for instance), due to the extreme accuracy needed for such an application.

There's a proposal out there to add a pulseIn function to Firmata: rwaldron/johnny-five#18

We should track the status there and start using it once it gets merged to mainline Firmata. (If ever.)

@LeventErkok
Copy link
Owner Author

Resolved by using the custom implementation.

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