Jump to content

Recommended Posts

Posted · Filament Width Sensor

Hi,

I came across this project on Thingiverse:

 

 

and wondered if it would be a good addition for the UM too. It measures the filament width on the fly and changes the flow to compensate for width fluctuations. Pretty nifty.

Not sure it if makes a big difference at all. I am printing with 2.85mm width for ages without a noticeable difference in quality. I'd go so far to say that the UltiGcode isn't all that useful at the moment since a) there can only be four filament presets (two of them can't be renamed) and b ) I guess most people are just too lazy to change filament width constantly. That is if you print with high quality filament which has stable properties....

 

  • Link to post
    Share on other sites

    Posted · Filament Width Sensor

    Hmm! curious device, it has a light shining on a 128x1 pixel array with the amount obscured by the filament indicating the width, but I'm not quite seeing how it works.

    Does that work with translucent filaments?

    Also, what happens if cross sectional area is consistent but it comes to an oval shaped section? Presumably it will increase or decrease the flow depending on its orientation.

    Does the modified Marlin also track the distance from the sensor to the nozzle and, with the filament speed, calculate when in the future to vary the feed rate to compensate for the width change?

    Personally I never change the filament width. I'd rather get good quality filament in the first place.

     

  • Link to post
    Share on other sites

    Posted · Filament Width Sensor

    Does this measure the width in 2 dimensions, or the actual circular area of the filament?

    Because if you only measure the 2D-width, you have a pretty much worthless setup -> What about filament which is not perfectly round (which it never is)?

    You can have a filament which has exactly the correct circular area of 2.85mm filament (which is Pi * r^2 =~ 3.14 * 1.425^2 =~ 6.38 mm2) but is slightly oval.

    If you take a 2D measurement of that oval filament, you might measure 2.9mm (or 2.7mm if you get the flatter side) and compensate for an inexistent error...

    Besides that: Getting exactly the correct amount of flow isn't critical for most prints. You usually don't even notice errors of about +-5% or even more.

    /edit:

    A partial solution would be to measure the 2D width from several angles and taking the average of the measured widths. But that makes the sensor very complex - it's hardly going to be worth the effort.

    Imho, what makes much more sense is to have a sensor which checks whether or not the filament is actually feeding, or just grinding on the spot. This can be done very easily (most probably it has already been done...) and gives valuable information about the print's status.

     

  • Link to post
    Share on other sites

    Posted · Filament Width Sensor

    Imho, what makes much more sense is to have a sensor which checks whether or not the filament is actually feeding, or just grinding on the spot. This can be done very easily (most probably it has already been done...) and gives valuable information about the print's status.

     

    I think this would be of more value then the width measuring device.

     

  • Link to post
    Share on other sites

    Posted · Filament Width Sensor

    As as someone mentioned, for bowden tubes, the measurements would need to be tracked for the length of the path between the sensor and the extruder.

    I think jams have ruined many more prints that changes in filament width.

    My filament width solution is to buy filament from a good supplier.

     

  • Link to post
    Share on other sites

    Posted · Filament Width Sensor

    This.

     

    Daid, if I might ask - why was UltiGcode introduced in the first place?

     

  • Link to post
    Share on other sites

    Posted · Filament Width Sensor

    Daid, if I might ask - why was UltiGcode introduced in the first place?

     

    Daid is on vacation, but i think it was because the ultimaker 2 needs less material settings in the gcode and more material settings saved on the machine itself.

    that is the main reason i think

     

  • Link to post
    Share on other sites

    Posted · Filament Width Sensor

    I believe that UltiGcode and the volumetric enhancements in Marlin were done to reduce the machine specifics in the gcode so that the gcode is "portable" to different machines and filaments. If you think about it, the volumetric versions of gcode just describe the object without respect to the machine. You can take the gcode to another machine using different size and type of filament and temperature.

    The only thing it doesn't address 100% is the movement speed as that is "baked in" to the gcode. While you can change the speed on the machine that doesn't give you complete control. You can vary the speed overall but you might want to have the first layer at one speed and the others at a faster speed which you might not be able achieve with a simple multiplier unless you actively dial in the speed.

     

  • Link to post
    Share on other sites

    Posted · Filament Width Sensor

    Well, you could still do that with the machine firmware.

     

  • Link to post
    Share on other sites

    Posted · Filament Width Sensor

    Sure you can adjust the speed at the machine. The only catch is that you change both travel and print speed with the speed setting in the Tune menu...

     

  • Link to post
    Share on other sites

    Posted · Filament Width Sensor

    That could technically also be possible in firmware :p

     

  • Link to post
    Share on other sites

    Posted · Filament Width Sensor

    Yep. On the day where the G0 and the G1 commands are treated seperately in Marlin... I guess the first taikonaut will be on Mars before that day...

     

  • Link to post
    Share on other sites

    Posted · Filament Width Sensor

    I think what they really should do is sort of abstract the speed in the gcode from the actual speed. The gcode should really contain a speed "level" or "type". The slicer would generate the type (for example, first layer extrude or first layer travel") and then the operator would set the speed appropriate for the printer and material in the firmware just like temperature and filament size.

    However, that would require more radical change than the filament size. For volumetric, the slicer just assumes a nominal filament size such that a feed of 1 represents 1 cubic mm. There is a magical filament width that produces this and I forget that value. (oh it's 1.1283791670955125738961589031215)

     

  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • UltiMaker Cura 5.9 stable released!
        Here comes Cura 5.9 and in this stable release we have lots of material and printer profiles for UltiMaker printers, including the newly released Sketch Sprint. Additionally, scarf seams have been introduced alongside even more print settings and improvements.  Check out the rest of this article to find out the details on all of that and more
          • Like
        • 5 replies
      • Introducing the UltiMaker Factor 4
        We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications
          • Heart
          • Thanks
          • Like
        • 4 replies
    ×
    ×
    • Create New...