pulseIn/pulseOut accuracy #6

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

Comments

Projects
None yet
1 participant
@LeventErkok
Owner

LeventErkok commented Mar 1, 2013

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: rwldrn/johnny-five#18

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

@LeventErkok

This comment has been minimized.

Show comment Hide comment
@LeventErkok

LeventErkok Mar 3, 2013

Owner

Resolved by using the custom implementation.

Owner

LeventErkok commented Mar 3, 2013

Resolved by using the custom implementation.

@LeventErkok LeventErkok closed this Mar 3, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment