Closed ribbons closed 6 years ago
This will double the stress on the front-end as you mentioned. I remember doing tests on this since a too high speed would actually make the weighing slower and skip readings. But, since its on par with the readme I guess thats about the initial speed before the back-end change.
Thanks @aelveborn
The back end waits for 100 milliseconds between sending readings so that it doesn't overwhelm the front-end with readings and complete the weighing process too quickly. However, 100ms * 50 readings = 5 seconds which is a fair bit slower than the 3 seconds mentioned in the README.
To align the weighing speed with the user's expectations from the README, halve the wait between sending readings to 50ms so that the overall process takes 2.5s.