Daniel Robertson
Daniel Robertson
https://github.com/endail/hx711/blob/de87c5b54282c7e86e214a7ec04d64beda106735/src/HX711.cpp#L257-L265 The waitReady method should busy-wait for a predefined maximum amount of time. If the amount of time is exceeded, a `TimeoutException` should be thrown. The try-catch in setConfig can...
Reading from an unconnected GPIO could lead to the process hanging (or another other unpredictable result). It may be of some use to have a method of the HX711 class...
Currently, the clock pin is pulsed with two GPIO write calls through the lg library: https://github.com/endail/hx711/blob/master/src/HX711.cpp#L88 https://github.com/endail/hx711/blob/master/src/HX711.cpp#L97 Both call [lgGpioWrite](http://abyz.me.uk/lg/lgpio.html#lgGpioWrite) through the [`Utility` class](https://github.com/endail/hx711/blob/master/src/Utility.cpp#L78). But lg also has a [lgTxPulse](http://abyz.me.uk/lg/lgpio.html#lgTxPulse)...
Considerations: - A _HX711Collection_ class? - While the current code for interfacing a single HX711 pulses the clock pin then reads the data pin, a collection of HX711s may not...
https://github.com/endail/hx711/blob/b1cb63a55b52b76e48a75648901d8954bd67a2f0/README.md?plain=1#L139 eg. https://www.ebay.com/sch/i.html?_nkw=hx711 Note: - (typically) green board, as opposed to Sparkfun's red board - not all HX711 pins are broken-out on the generic board compared to the Sparkfun version...
https://github.com/endail/hx711-pico-c/blob/43296dfa8dc8c9a6a2560b9a7985540f07af181b/src/hx711_multi_awaiter.pio#L138 False here means the data pins are input pins. https://www.raspberrypi.com/documentation/pico-sdk/hardware.html#group_hardware_pio_1gaf5c965ef1ca21684630c8be2cf3e52e7