No weight reported NaN #1
Comments
|
Using latest Octoprint 1.3.9 |
|
Can you post your octoprint.log? |
|
Also, by any chance did you hit "calibrate" with a 0 in the "known weight" field? If so, try hitting calibrate again with any other value in the known weight field and see if it produces a real number. |
|
Thanks for responding. Will try that. What else is required/or needs to be
installed to run the plugin? I think I maybe missing something. The upper
most field can not be edited hovering with the mouse above it shows a red
circle with line through it. When I hit calibrate it shows NaN. Played
around with different input but NaN is the return. Known weight is 1300gr
for full spool.
…On Mon, Sep 10, 2018 at 11:35 PM Victor Noordhoek ***@***.***> wrote:
Also, by any chance did you hit "calibrate" with a 0 in the "known weight"
field? If so, try hitting calibrate again with any other value in the known
weight field and see if it produces a real number.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ao7F31W_ofJVtdpqTrgOMw5EQthK8DZtks5uZy-egaJpZM4WWm3O>
.
|
|
The plugin has no requirements other than RPI.Gpio, which should be installed automatically when you install the plugin. Can you post your octoprint.log as well as a screenshot of the plugin settings you are using? |
|
Will do tomorrow night
…On Fri, Sep 21, 2018 at 9:19 PM Victor Noordhoek ***@***.***> wrote:
The plugins has no requirements other than RPI.Gpio, which should be
installed automatically when you install the plugin.
Can you post your octoprint.log as well as a screenshot of the plugin
settings you are using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ao7F3zOU2uP_ouSJ29JE-YVdIRCtjXczks5udZAzgaJpZM4WWm3O>
.
|
|
[image: scale.JPG]
On Fri, Sep 21, 2018 at 9:37 PM Empiricus Dremomys <[email protected]>
wrote:
… Will do tomorrow night
On Fri, Sep 21, 2018 at 9:19 PM Victor Noordhoek ***@***.***>
wrote:
> The plugins has no requirements other than RPI.Gpio, which should be
> installed automatically when you install the plugin.
>
> Can you post your octoprint.log as well as a screenshot of the plugin
> settings you are using?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#1 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/Ao7F3zOU2uP_ouSJ29JE-YVdIRCtjXczks5udZAzgaJpZM4WWm3O>
> .
>
|
|
I'm having the same issue. I tared it with the scale empty, then I used an empty spool with a listed weight of 319 to calibrate, got "NaN". The OctoPrint log seems to be spammed by this plugin every 6 milliseconds (?, 23:46:56,400 ... 406 ... 412 ... etc) with "octoprint.plugins.filament_scale - INFO - 20". Sometimes the "Filament Remaining" display switches from "NaNg" to "Infinityg" for a second, then back to "NaNg". Edit: I think the constant INFO -20 from the plugin is overwhelming the server. Twice now it's crashed since I installed the plugin and connected the scale. |
|
Thanks for letting me know that it is not just me or the hardware I got.
Yes something is wrong here. For the first time in three years Octoprint
was crashing on me during prints with the plugin installed. Removed it and
hope that the issue can be resolved.
…On Sun, Sep 23, 2018 at 1:55 AM AbuMaia ***@***.***> wrote:
I'm having the same issue. I tared it with the scale empty, then I used an
empty spool with a listed weight of 319 to calibrate, got "NaN". The
OctoPrint log seems to be spammed by this plugin every 6 milliseconds (?,
23:46:56,400 ... 406 ... 412 ... etc) with
"octoprint.plugins.filament_scale - INFO - 20".
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ao7F38BK7DtGwnFUsdYRIOFXNaaDAuWUks5udyJagaJpZM4WWm3O>
.
|
|
I haven't yet solved the problem, but I found a bug while searching through tho code for whatever was throwing that "INFO - 20" message repeatedly in the log. In the Readme, it says, "This plugin assumed you connected the data pin to GPIO20, and the clock pin to GPIO21." However, in init.py, under the default settings section, it has I swapped my two wires around, but it didn't help. |
|
The INFO - 20 is a debug message I forgot to remove before committing. The good news is while I'm still not able to reproduce the NaN display, I am able to reproduce the crashes. Something is making octoprint segfault, which is confusing to me as I was not aware python was capable of segfaulting. Working on it. Once I get the crashes figured out I'll upload a version with some diagnostic code so we can figure out what's causing the NaN issue. Thank you for your help and patience. |
|
I've found another problem, though fixing it didn't solve this issue either. I noticed different websites talking about wiring up the hx711 have different instructions. Some say the white wire goes to A+ and green goes to A-, others say white goes to A- and green to A+. So I went to the vendor where I bought the load cell, and their info says green A+ white A-. I unsoldered and swapped the two wires around, but still no change here. |
|
Yeah, there are multiple kinds of hx711 boards/load cells out there and not all of them are wired the same. Try the latest version. I've fixed the crashing, and I've also added some feedback if the sensor isn't connected correctly. If you are still getting a NaN, it will log some diagnostic data to the console - let me know what, if anything, you see there. |
|
Thanks a bunch. Will try the new version. What data rate is expected from
the board?
I tried one that has
- On-chip active low noise PGA with selectable gain of 32, 64 and 128
- Selectable 10SPS or 80SPS output data rate
I guess the output rate is critical here. Unfortunately the documentation
that comes with these is poor to none.
…On Mon, Sep 24, 2018 at 12:45 AM Victor Noordhoek ***@***.***> wrote:
Yeah, there are multiple kinds of hx711 boards/load cells out there and
not all of them are wired the same.
Try the latest version. I've fixed the crashing, and I've also added some
feedback if the sensor isn't connected correctly. If you are still getting
a NaN, it will log some diagnostic data to the console - let me know what,
if anything, you see there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ao7F3wabR7FcgCbgy1ew0AqaPBiK-Mklks5ueGNWgaJpZM4WWm3O>
.
|
|
I think my load cell is faulty. Following some diagnostic instructions I found, in which you measure the resistance between each 6 pairs of wires. The resistance values you get should all be nearly equal, with one pair showing higher resistance. I got 3 different readings, and the highest resistance pair was not the red-black pair as it should be if they're the E+ and E-. |
|
That is why I got a second one. But same thing.
…On Tue, Sep 25, 2018 at 2:09 AM AbuMaia ***@***.***> wrote:
I think my load cell is faulty. Following some diagnostic instructions I
found, in which you measure the resistance between each 6 pairs of wires.
The resistance values you get should all be nearly equal, with one pair
showing higher resistance. I got 3 different readings, and the highest
resistance pair was not the red-black pair as it should be if they're the
E+ and E-.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ao7F3_fqE5Bcu3eyKctZYG_LPijrekCQks5ueciWgaJpZM4WWm3O>
.
|
|
I guess I really do have to get a new load cell. I soldered everything back together again, installed the updated plugin, and plugged the scale back into the pi. The Filament Scale just says "Calibration Error", and the settings page says the sensor isn't plugged in. |
|
Yeah, if the settings page says the sensor isn't plugged in that means it's reading a full run of zeroes from the HX711. If you send me a photo of your wiring I can double-check it. |
|
Emparus, as far as I can tell that refers to the sample rate and should work either way. The way the interface works is that there's a data line and a clock line. Each time the pi sends a pulse on the clock line, the HX711 sends a bit on the data line. So it's not like serial where you have to match baud rates or anything. This is the datasheet I'm basing off of: https://www.mouser.com/ds/2/813/hx711_english-1022875.pdf |
|
Thanks for the explanation. Can you share specifically which board and
weight bar you used? I have tried two different boards and had two sensor
bars. No luck
…On Sat, Sep 29, 2018 at 8:44 PM Victor Noordhoek ***@***.***> wrote:
Emparus, as far as I can tell that refers to the sample rate and should
work either way. The way the interface works is that there's a data line
and a clock line. Each time the pi sends a pulse on the clock line, the
HX711 sends a bit on the data line. So it's not like serial where you have
to match baud rates or anything.
This is the datasheet I'm basing off of:
https://www.mouser.com/ds/2/813/hx711_english-1022875.pdf
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ao7F3-IsILfvOkf1HZ3GjKFMNWqC-E1tks5ugBPxgaJpZM4WWm3O>
.
|
|
This is the one I bought: https://www.ebay.com/itm/5KG-Scale-Load-Cell-Weight-Weighing-Sensor-HX711-Weighing-Sensor-AD-Module/112631226433 AbuMaia, nothing looks wrong with your wiring to me. I do see you have other stuff plugged into your GPIO ports as well; do you have other plugins using GPIO peripherals? If you do, maybe they're interfering. You could try turning off those plugins, restarting your pi, and seeing if it works. |
|
Progress. Received my new load cell and hx711 board, soldered it all up and plugged it in. The plugin now says "-infinity g" and "Filament Remaining: 0g". Now I just have to re-print the filament holder base I broke while trying to take the old load cell out (used superglue to strengthen a bad print area, it stuck to the load cell). Yep, I have other things plugged into the GPIO. I have a bank of relays which I use to remotely switch power to the printer and lights, and a filament runout sensor. Emparus: I just received this one: https://www.amazon.com/gp/product/B078JX3KJN and it seems to be working. I need to rebuild the filament holder in order to calibrate it to see if it really does work, but the plugin isn't complaining about it not being there. |
|
Ok, I got the filament holder rebuilt, and everything plugged in, and it seems to be working. It is outputting a weight. Whether it's the right weight is another matter. I calibrated it with an empty spool, but the plugin is reporting a weight of filament double that of what Filament Manager calculates should be remaining based on usage. Perhaps I should get a kitchen scale so I can calibrate the load cell with better numbers and have a more accurate comparison. |
|
The accuracy of your "known weight" is important - if you're only estimating the weight, all the readings will be way off. If you don't have an accurate scale I recommend finding a consumer good with a weight printed on it, like a bag of rice or a can of soda (12oz can of soda is what I used, it weighs 395mg). Or something like a smartphone whose weight you can look up online. |
|
Thanks for all the help. I think a got two bad load cells. Tried 4 boards
with these cells. including two that came with the cells and are the same
you had. The new plugin detects that something is connected ( sensor not
connected if I unplug plus). But then it reports Callibration error. If I
go to the plugin it says no filament sensor detected check the pins, which
are all connected correctly. I guess bad luck.
…On Sat, Sep 8, 2018 at 5:05 PM Victor Noordhoek ***@***.***> wrote:
Can you post your octoprint.log?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ao7F3_6oiDg0KbBzDRIm2mL-926yLqT9ks5uZDErgaJpZM4WWm3O>
.
|
|
If you're getting a calibration error that's progress! It means we're getting some data from the load cell at least. When it gets a calibration error it should be putting some debug info in the console, can you post that in here? |
|
Dug around the cupboards, found a bag of farina that said "397g". Used it to calibrate. Filament Manager says there should be 288g remaining. Filament Scale is now reporting 299g. Though that is still using the 319g empty spool weight I had been using to calibrate before. |
|
Perhaps these load cells weren't intended for continuous use. Yesterday I said it was reporting 299g. I then did a print that used 30g of filament. Today it's reporting 924g, and is not stable. It jumps around to other readings, or "calibration error" occasionally. In the time it took me to type all of this it's now saying 604g. It may be accurate enough soon after taring and calibrating, but leave it sit for a bit under load, it becomes quite unreliable. |
|
Will do. Waiting for a new cell from your eBay source. I already designed a
nice rotating filament holder that integrates the load cell.
https://www.thingiverse.com/thing:3054853
…On Mon, Oct 8, 2018 at 2:00 PM Victor Noordhoek ***@***.***> wrote:
If you're getting a calibration error that's progress! It means we're
getting some data from the load cell at least. When it gets a calibration
error it should be putting some debug info in the console, can you post
that in here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ao7F39rUET3UCmUq8FmzrMkljuSlRmBRks5ui5KngaJpZM4WWm3O>
.
|
|
Now it's cycling every 5 seconds - 5 seconds displaying weight, 5 seconds error message, back and forth. Head is starting to bleed from scratching so hard... |
|
Commenting to let you know I haven't abandoned this project, I will look at your comments over the weekend and see if I can help. |
|
Thank you MOST kindly good sir! |
|
Sorry to have been such a pain sir |
|
No worries. Can you post a picture of your wiring setup? Also the output in your browser console (hit F12) |
|
|
|
|
|
Yellow wire is data connected to GPIO20, Purple is Clock, connected to GPIO 21 as instructed |
|
Power for the HX711 is tapped into the 5v pin, ground to the adjoining ground pin |
|
Octoprint server is Pi III B+ from EzPi |
|
I have noticed that the HX711 is very susceptible to loose connections. Personally I soldered my wires directly to the HX711 rather than use connectors. Please try this and let me know if the same thing still happens. |
|
No luck - never leaves sensor not connected error |
|
additionally, all of this testing is being done without the printer running any jobs, so there is no vibration present in the system |
|
I just tried every combination of the HX711 boards I have with every sensor I have. The ONLY one that even attempts to work is the one in the picture and logs I posted. It's almost sounding like a clock issue of some kind? |
|
Ordered another load cell and HX711 board from different manufacturers. We'll see. I've checked my wiring and connections 6 ways from Sunday. None of this makes sense... |
|
Any other ideas sir? |
|
OK - grabbing at straws here. The actual measured voltage out of the 5v pin on the pi is 5.12v - could that be too high and it's blowing the HX711 circuit board? Should I be powering this off of the 3.3v pin instead? |
|
Which, BTW, now it never comes alive, always stays at Sensor Not Connected Error |
|
The HX711 has a range of 2.6 ~ 5.5V so it should be fine at 5.12v. You could probably try 3.3v as well if you wanted but I don't think it would make a difference. The "sensor not connected" error happens when we get no signal at all from the board. One possibility I can think of is that some other plugin or program on your PI is interfering. Try disabling all other octoprint plugins. Do you have anything else using GPIO? There's nothing unusual in your console log, but can you upload your octoprint.log as well so I can have a look? (please use pastebin this time) |
|
I have the latest octoprint.log for you. My most humble apologies for the etiquette breach last time, However, I can't seem to post it to pastebin. I created an account, and pasted it in, but it exceeded the allowable limits for a free account, and it says there are no Pro accounts available for purchase which would allow it., so, I copied it to the public folder in my Onedrive. You can access it here: https://1drv.ms/u/s!Ah04pUrIwGvItUw3tDNUZ6WuJxXw |
|
Victor –
Any progress on this sir? I have reached out to TH3D about the possibility of their EzPi blocking it somehow, but can’t seem to get them to respond. Please help???
* Doug Brown
From: Victor Noordhoek <[email protected]>
Sent: Tuesday, July 16, 2019 10:38 PM
To: dieki-n/Octoprint-Filament-Scale <[email protected]>
Cc: wapiti59 <[email protected]>; Comment <[email protected]>
Subject: Re: [dieki-n/Octoprint-Filament-Scale] No weight reported NaN (#1)
The HX711 has a range of 2.6 ~ 5.5V so it should be fine at 5.12v. You could probably try 3.3v as well if you wanted but I don't think it would make a difference.
The "sensor not connected" error happens when we get no signal at all from the board.
One possibility I can think of is that some other plugin or program on your PI is interfering. Try disabling all other octoprint plugins. Do you have anything else using GPIO? There's nothing unusual in your console log, but can you upload your octoprint.log as well so I can have a look? (please use pastebin this time)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AIN4EC22VTFZRSW2XI44243P72O2XA5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2DADVA#issuecomment-512098772> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AIN4EC4XUJQFFPQKMDNZTFLP72O2XANCNFSM4FS2NXHA> . <https://github.com/notifications/beacon/AIN4ECYB3RN33WS6GXIWWQ3P72O2XA5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2DADVA.gif>
|
|
Victor – I have been poking around some more and wonder if any of this makes any difference, and if so, how do I change it. I installed Cayenne so I could get a view into the GPIO pin assignments, thinking that EzPi may have done something funky with them (they still have not responded to my request for support). When I connect to my Pi, and look at the GPIO table, I find that GPIO pin 20 (set for in) and 21 (set for out) have no assignment, GPIO 2 is SDA, GPIO3 is SCL, GPIO 4 is DATA and GPIO 11 is SCLK. Does that make any difference and if so, how do I change it?
* Doug
From: Victor Noordhoek <[email protected]>
Sent: Tuesday, July 16, 2019 10:38 PM
To: dieki-n/Octoprint-Filament-Scale <[email protected]>
Cc: wapiti59 <[email protected]>; Comment <[email protected]>
Subject: Re: [dieki-n/Octoprint-Filament-Scale] No weight reported NaN (#1)
The HX711 has a range of 2.6 ~ 5.5V so it should be fine at 5.12v. You could probably try 3.3v as well if you wanted but I don't think it would make a difference.
The "sensor not connected" error happens when we get no signal at all from the board.
One possibility I can think of is that some other plugin or program on your PI is interfering. Try disabling all other octoprint plugins. Do you have anything else using GPIO? There's nothing unusual in your console log, but can you upload your octoprint.log as well so I can have a look? (please use pastebin this time)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AIN4EC22VTFZRSW2XI44243P72O2XA5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2DADVA#issuecomment-512098772> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AIN4EC4XUJQFFPQKMDNZTFLP72O2XANCNFSM4FS2NXHA> . <https://github.com/notifications/beacon/AIN4ECYB3RN33WS6GXIWWQ3P72O2XA5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2DADVA.gif>
|
|
Those designations refer to if you're using the Raspberry Pi's built-in hardware I2C or SPI. We're not using those (the HX711 uses a simpler 2-wire communication protocol), so it has no effect. I've updated the plugin to hopefully be a little more forgiving about imperfect timing, please update and give it a try. |
|
Wow – FINALLY! It took 7 HX711 boards an sensors, but it is FINALLY working. The weight tends to fluctuate slightly from time to time, and on rare occasion it still goes sensor not connected, but it’s working. Thank you Victor.
From: Victor Noordhoek <[email protected]>
Sent: Monday, July 29, 2019 9:04 AM
To: dieki-n/Octoprint-Filament-Scale <[email protected]>
Cc: wapiti59 <[email protected]>; Comment <[email protected]>
Subject: Re: [dieki-n/Octoprint-Filament-Scale] No weight reported NaN (#1)
Those designations refer to if you're using the Raspberry Pi's built-in hardware I2C or SPI. We're not using those (the HX711 uses a simpler 2-wire communication protocol), so it has no effect.
I've updated the plugin to hopefully be a little more forgiving about imperfect timing, please update and give it a try.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AIN4ECZN4KQQ2TB3F5J46G3QB4BG3A5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3A76YQ#issuecomment-516030306> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AIN4EC72QS6MNJXHE4UYNZ3QB4BG3ANCNFSM4FS2NXHA> . <https://github.com/notifications/beacon/AIN4EC7QPVG73RMRE5B56CLQB4BG3A5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3A76YQ.gif>
|
|
One thing I have noticed though…
I just started a print, and the weight measurements are all over the map, including an occasional sensor not connected error. The HX711 is hard-wired to the sensor, and the connections from the HX711 out to the Pi also soldered on, however, I used sockets to connect it to the Pi as before. Guess while it’s in operation it’s just going to be erratic, because I am not too keen on soldering the wires on the pins of the Pi
From: Victor Noordhoek <[email protected]>
Sent: Monday, July 29, 2019 9:04 AM
To: dieki-n/Octoprint-Filament-Scale <[email protected]>
Cc: wapiti59 <[email protected]>; Comment <[email protected]>
Subject: Re: [dieki-n/Octoprint-Filament-Scale] No weight reported NaN (#1)
Those designations refer to if you're using the Raspberry Pi's built-in hardware I2C or SPI. We're not using those (the HX711 uses a simpler 2-wire communication protocol), so it has no effect.
I've updated the plugin to hopefully be a little more forgiving about imperfect timing, please update and give it a try.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AIN4ECZN4KQQ2TB3F5J46G3QB4BG3A5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3A76YQ#issuecomment-516030306> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AIN4EC72QS6MNJXHE4UYNZ3QB4BG3ANCNFSM4FS2NXHA> . <https://github.com/notifications/beacon/AIN4EC7QPVG73RMRE5B56CLQB4BG3A5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3A76YQ.gif>
|
|
That's great it works now! Was it the update that made it work or a different HX711 chip? You may want to try different kinds of connectors on the ends of the wires connecting to the pi - you may be able to get a better connection. There will be some variability during a print because the extruder pulls on the filament, applying force to the scale. |
|
Don’t know which it was, but have a feeling it was the chip. Tried it with the update before getting the other chips and it still didn’t work. Will try to find some different connectors for the Pi and see if that makes it more reliable, but your comment about the extruder pulling on the filament makes sense.
From: Victor Noordhoek <[email protected]>
Sent: Wednesday, July 31, 2019 3:38 PM
To: dieki-n/Octoprint-Filament-Scale <[email protected]>
Cc: wapiti59 <[email protected]>; Comment <[email protected]>
Subject: Re: [dieki-n/Octoprint-Filament-Scale] No weight reported NaN (#1)
That's great it works now! Was it the update that made it work or a different HX711 chip?
You may want to try different kinds of connectors on the ends of the wires connecting to the pi - you may be able to get a better connection.
There will be some variability during a print because the extruder pulls on the filament, applying force to the scale.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AIN4EC5L6RBC4SE5EAY4AHTQCIA43A5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3IUNZY#issuecomment-517031655> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AIN4EC37GGDIUHRYTDYZ6WTQCIA43ANCNFSM4FS2NXHA> . <https://github.com/notifications/beacon/AIN4EC6DSEWN5TXKX6UONMTQCIA43A5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3IUNZY.gif>
|
|
[email protected] has shared a OneDrive file with you. To view it, click the link below.
filament length calculator.xlsx <https://1drv.ms/x/s!Ah04pUrIwGvIvwqNYsFe1zelc9S_>
Victor – Forgive me, I hope I’m not spamming the thread here, my apologies if I do. Your scale is working great now, but I have a suggestion for a tweak. Many of the 3d slicers out there (I use Simplify3D) compute the length of filament a model will consume, which takes some mathematical gyrations to convert the weight your scale gives of the remaining filament to available length. In the attached Excel spreadsheet file, I have entered the calculations to convert that weight based on the three most common materials (PLA, ABS, PETG). In it, I have created drop downs to select the three materials, another to select the three common filament diameters (1,75, 2.85, 3.0). Once those options are entered, you simply enter the weight of the material showing yon your scale and it gives you the length of remaining material. Is there a way to incorporate this formula set into your plug in so that it gives weight, and takes that value and gives you a remaining length?
Again, sorry if I spammed you.
* Doug Brown
From: Victor Noordhoek <[email protected]>
Sent: Wednesday, July 31, 2019 3:38 PM
To: dieki-n/Octoprint-Filament-Scale <[email protected]>
Cc: wapiti59 <[email protected]>; Comment <[email protected]>
Subject: Re: [dieki-n/Octoprint-Filament-Scale] No weight reported NaN (#1)
That's great it works now! Was it the update that made it work or a different HX711 chip?
You may want to try different kinds of connectors on the ends of the wires connecting to the pi - you may be able to get a better connection.
There will be some variability during a print because the extruder pulls on the filament, applying force to the scale.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AIN4EC5L6RBC4SE5EAY4AHTQCIA43A5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3IUNZY#issuecomment-517031655> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AIN4EC37GGDIUHRYTDYZ6WTQCIA43ANCNFSM4FS2NXHA> . <https://github.com/notifications/beacon/AIN4EC6DSEWN5TXKX6UONMTQCIA43A5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3IUNZY.gif>
|
|
Victor –
I can’t remember if I sent this to you or not, but I send it to you for your filament weight scale Octoprint plug project in as a possible useful addition. It is an Excel spreadsheet in which you input two values: The filament you are printing with and the weight the scale shows is remaining on the spool. I then uses If, Then, Else statements to automatically set the input the density value (using an average value for several different manufacturers). Once you input the filament weight into the other scale, it automatically estimates the length of filament remaining on the spool. My thought is that you might use this spreadsheet to program in a second line in your plug in that allows for the input of the material being printed, then takes the weight value from the scale and plugs that into the formula and gives the user an estimated length of filament remaining on the spool.
I don’t know what code you used for the plugin, and honestly I’m not much of a coder anymore, but I would be glad to alpha and beta test this for you if you like.
* Doug Brown
From: Victor Noordhoek <[email protected]>
Sent: Wednesday, July 31, 2019 3:38 PM
To: dieki-n/Octoprint-Filament-Scale <[email protected]>
Cc: wapiti59 <[email protected]>; Comment <[email protected]>
Subject: Re: [dieki-n/Octoprint-Filament-Scale] No weight reported NaN (#1)
That's great it works now! Was it the update that made it work or a different HX711 chip?
You may want to try different kinds of connectors on the ends of the wires connecting to the pi - you may be able to get a better connection.
There will be some variability during a print because the extruder pulls on the filament, applying force to the scale.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AIN4EC5L6RBC4SE5EAY4AHTQCIA43A5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3IUNZY#issuecomment-517031655> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AIN4EC37GGDIUHRYTDYZ6WTQCIA43ANCNFSM4FS2NXHA> . <https://github.com/notifications/beacon/AIN4EC6DSEWN5TXKX6UONMTQCIA43A5CNFSM4FS2NXHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3IUNZY.gif>
|
This plugin doesn't work for me. Tried two scale setups with the green board. Under current reading NaN is reported and nothing can be calibrated.
The text was updated successfully, but these errors were encountered: