npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@ataberkylmz/hx711

v0.1.6

Published

Less CPU intensive C Driver and Node Binding for HX711 Load Cell Amplifier

Downloads

41

Readme

@ataberkylmz/hx711

This is a fork of @shroudedcode's hx711 package which is also forked from @dangrie's hx711 package.

I've modified the library in such a way that it does not use 100% of the CPU all the time. Currently the usage is about 15-20% on Raspberry Pi 3 B+. This CPU usage is also reducible if we can figure out the sensor's response time and sleep till we possibly have a valid response. Currently the default sleep time is set to 100 nanoseconds.

This version also uses Broadcom GPIO pin numbering instead of physical/board numbering.

API

This library exposes a class with Name HX711 that gives you access to all functions you need to interface.

Constructor(Number clockPin, Number dataPin)

const sensor = new HX711(clockPin, dataPin);

create a new Sensor instance. The pin Numbers should represent the WiringPi Pins the Sensor is connected to. You can have as many HX711 Chips connected as long as they all are connected to a different set of pins.

getUnits([Number times = 10])

let units = sensor.getUnits();

Read the sensor times times and calculate the average. This returns a scaled value with the offset removed.

tare([Number times = 10])

sensor.tare();

Read the sensor times times and save the average Offset via setOffset().

setOffset([Number offset = 0])

sensor.setOffset(-1000);

set or reset the offset for the sensor

getOffset()

let offset = sensor.getOffset();

get the current offset of the sensor

setScale([Number scale = 1.0])

sensor.setScale(3543.26);

set or reset the scale for the sensor

getScale()

let scale = sensor.getScale();

get the current scale of the sensor

powerDown()

sensor.powerDown();

Powers down the sensor. Sets the clock to low, then high and waits 60 microseconds Note: After a reset or power-down event, input selection is default to Channel A with a gain of 128.

powerUp()

sensor.powerUp();

Powers up the sensor. Sets the clock to low. Note: After a reset or power-down event, input selection is default to Channel A with a gain of 128.

Troubleshooting

It sometimes can happen that the HX711 chip gets in a state where it does not recover itself. This can result in an endless loop while the library waits for the chip to notify a new data set.

If you ever run in a problem where the library does not give you new values, just power cycle the sensor.

Also if you use other GPIO pins of the Raspberry Pi with relay boards, the sensor might give inaccurate values when a relay is actuated then it goes back to giving normal values.