|import RPi.GPIO as GPIO|
|ret = |
|for i in range(8):|
|def __init__(self, dout, pd_sck, gain=128):|
|self.PD_SCK = pd_sck|
|self.DOUT = dout|
|self.GAIN = 0|
|self.OFFSET = 0|
|self.SCALE = 1|
|self.lastVal = 0|
|return GPIO.input(self.DOUT) == 0|
|def set_gain(self, gain):|
|if gain is 128:|
|self.GAIN = 1|
|elif gain is 64:|
|self.GAIN = 3|
|elif gain is 32:|
|self.GAIN = 2|
|while not self.is_ready():|
|dataBits = [createBoolList(), createBoolList(), createBoolList()]|
|for j in range(2, -1, -1):|
|for i in range(7, -1, -1):|
|dataBits[j][i] = GPIO.input(self.DOUT)|
|#set channel and gain factor for next reading|
|#for i in range(self.GAIN):|
|#check for all 1|
|if all(item == True for item in dataBits):|
|bits = |
|for i in range(2, -1, -1):|
|bits += dataBits[i]|
|self.lastVal = int(''.join(map(str, bits)), 2)|
|data = [0,0,0]|
|for i in range(0,3):|
|data[i] = int(''.join(map(str, dataBits[i])), 2)|
|#data ^= 0x80|
|return data << 16 | data << 8 | data|
|def read_average(self, times=3):|
|sum = 0|
|for i in range(times):|
|sum += self.read()|
|return sum / times|
|def get_value(self, times=3):|
|return self.read_average(times) - self.OFFSET|
|def get_units(self, times=3):|
|return self.get_value(times) / self.SCALE|
|def tare(self, times=15):|
|sum = self.read_average(times)|
|def set_scale(self, scale):|
|self.SCALE = scale|
|def set_offset(self, offset):|
|self.OFFSET = offset|
|hx = HX711(9, 11)|
|val = hx.get_units(3)|
|if val > 100:|
|except (KeyboardInterrupt, SystemExit):|
I, too, am puzzled by this code so comments would help immensely. For example, I do not see anywhere to specify which gpio pins the HX711 is connected. Does it connect to the SDA and SCL pins, so that this code is assuming a default configuration? If so, can I move the connection to any other pins? I'm trying to use the HX711 in parallel with a BMP180, which is connected to those two pins. Thanks!
Thanks underdoeg. I got it to work. What I would like is a better understanding of how you are controlling the gain. This was not immediately clear. Does it vary it based upon the input range and set itself. Also, I noticed the code will "zero" itself out. How do you turn this off if necessary. First I thought it had to do with Taring, but now I'm not so sure.
I'm using this for a pressure transducer that uses a wheatstone bridge strain gage. I cannot have this zeroing out everytime I run the program.
@jproehl-- They can be any pins. In his example he uses pins 9 and 11 as shown on line #115. However I added a line to the code right before line #17
That sets the Pi to recognize the BCM pins, not just the Pi board. You have to make sure you know the difference. At the terminal prompt use the command gpio readall and it will show you the layout of all the pins.
So maybe I spoke too soon. I guess I should simplify this as I cannot correlate the returned values with real voltages.
My supply voltage coming off the Pi2 is 5.2V that feeds the HX711 board.
Thus if I excite with 4.2 V, I get an actual calibration measurement across the A+ / A- terminals (with voltmeter in hand) of 3mV/V x 4.2V x 0.8 = 10.1mV as expected.
I set my SCALE to 1, and with the assumption that I properly set the gain to 128, I'm getting back a value of 16066200 on average.
Is there a better way to control the serial timing with the Pi2? Python does have some serial API's but I don't know enough whether that would apply in this situation. Has anyone else out there has been able to make this code work on a Pi that is not a weight scale. I'm almost at the point of dumping the HX711 and getting another 24 bit ADC from TI or Analog Devices that will run SPI or I2C. Wasted way to much time trying to debug this.
Thanks for any help you can provide.
Has anyone gotten this to work in Python on Raspberry Pi? My HX711 board (Sparkfun HX711 Load Cell Amp breakout) works flawlessly with Arduino, but makes a big mess on the Pi. I've tried debugging it, getting it to spit out the bit string, etc., and it doesn't make any sense... Is there a clock timing issue? Problem interpreting the 2's complement?
I made it work. I've made a few modifications on this code on the way the bits are processed after making a few tests using Python's Numpy library. The main problem was that the final int value was not being built with the bytes in the correct order. This caused that with very low differences (noise, etc) the values would jump from one extreme to another because the "less significant byte" was in the "most significant byte" position when building the 24 bit integer.
One note about the HX711 is that just after it is plugged to power it kind of needs a few minutes to "warm up". Before digging in this code por Raspberry Pi, I used an Arduino to test the HX711 using the Serial Plotter because I thought my mine might have been broken (I have 20 of these and tested 2 of them). After I plugged the Vcc, the signal just keeps growing with very little increments for about 2 or 3 minutes until it reaches a stable value. This could lead to bad "taring" or, if you're aiming for big precision, well, you know...
I've never contributed to any repository before so I'm not sure what are the steps here. Should I fork it? Should I clone? I've only worked on my own repositories before.
Basically, you clone it. After that, branch it and make a pull request to the owner. If he accepts it, he can merge it with the original code.
Thanks for the debbuging! I will be looking forward to test it on Monday, so after that I can post the results and contribute to it too.
hello, I am trying to run this code in Beaglebone Black, however I only get 0.0 all the time . I only modified the GPIO reading and writing to fit beaglebone. Is there any timing difference between RaspberryPI and beaglebone that I should consider? Thank you very much
(self.read_average(times) always gives me 8388607 )
@underdoeg - there seems to be some problems with the bit order in this code - I've updated a version at https://gist.github.com/Richard-Major/64e94338c2d08eb1221c2eca9e014362
Hi tatobari I am using your example.py and getting -8388607 repeatedly as output, always the same whether or not I put any weight on the load gauge. I notice that tibloop also got this same number (23 Jun 2016). Can anyone help me? I'm a complete novice, this is my first project with a Raspberry Pi and load gauge, learning as I go along...