-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPIO used #16
base: master
Are you sure you want to change the base?
GPIO used #16
Conversation
Op153 refactor
Add's workflows for release building
Update Project and Add Release workflow
Fix Views + Versioning
Release 0.2.2
Optimise Release Process
Release v0.2.3
After various gyrations I settled on this process for now.
Improve Releases
The 'Sensor Not Connected' message was both long and slightly inaccurate. Which lead to the interface jumping around whenever a string of bad readings came through. Shortened the error to 'NaN' and documented it in the README.
Long Message in UI
Reported in #10, installation failed as RPi.GPIO was missing during setup.
Open version file directly to avoid requiring runtime dependencies during setup - fixes #10
This typo causes the plugin to fail for new installations. If you have already configured it, these values are not used. Fixes #12
Fix typo in default settings
During refactoring a typo lead to default settings not being correct. Ensure our future defaults don't change without intent. Relates to #12
Defaults Test
Line 48 of init.py <self.hx = HX711(20, 21)> You should be able to edit this via an editor. I'm not very good at giving advice as to exactly how, but that's where it is in the code. |
I've changed the 3 lines in Init.py : and the plugin always give error "Error: No filament sensor detected" anything else ? Edit : |
Glad you made progress! There is a calibration process, if I recall. It's been a while since I've used mine, as I have been going through printer changes. There is a chance pins are backwards, or a connection issue exists. -Parsko |
Hi, OctoPrint/plugins.octoprint.org#864 -Parsko |
Well. Good continuation. |
My experience with the HX711 chips is dodgy. They do not provide stable reading, simply put. I use them professionally, and can get them to work because I am writing the software. But, even then, they give me sporatic readings that are simply wrong. Using them with a Raspberry Pi is worse than a proper microcontroller. It's a pseudo I2C protocol. It's I2C, but does not work with I2C libraries, in my experience. I have not tried again since I've gained much more experience with it. I also haven't read the datasheet to get the exact timing between edges and such. I'm sure there is one to get it to read reliably, perfectly. A proper way to do this, IMHO, is to have a sub micro, like a RP2040 QTPY do the reading and filtering, while also maintaining the communication with the Pi. Much cleaner and more reliable. It's on my LOOONG list of things to do in the next couple years. If it's worth anything, mine isn't hooked up right now. I would really love this integrated with the spool manager. Another item on the list.... Good luck, stay safe. |
Thank's Parsko41 |
The code base was ported from python2 on a whim, and a lot of the code reflects that. This tidies up the typing and linting a little more
Although the effort was done to create an average with outlier dection, it was never actually used. This switches the function call over
The automatic releases use commit messages to generate the release notes. This ensures the commits are correctly formmated to align with it.
Actions Checkout + Actions Python have had a bunch of improvements, time to update them.
Add MQTT Support
I want to connect my scale on GPIO 3 (DT) and GPIO 27 (SCK). How can change for use this GPIO instead of 20 and 21 ???