You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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: https://github.com/rwldrn/johnny-five/issues/18
We should track the status there and start using it once it gets merged to mainline Firmata. (If ever.)
The text was updated successfully, but these errors were encountered: