Jump to content

Oddities when slicing for vase mode


Bracer

Recommended Posts

Posted · Oddities when slicing for vase mode

Hi all, scratching my head on this one and was hoping others might have seen the same (and have an easy solution!)

 

Using the same settings in cura 4.0 when printing in vase mode (spiralize..) I get different results on different models but don't understand why.  The attached pics show the difference in smoothness - the first is a low polly skull and the second was a start of a vase.  The only thing I've noticed is that the ones that don't work come out as much larger file sizes and (even though cura says e.g 2 hour print time), octoprint will start and say something like 12 hours.  When printing it sounds like the printer is making loads of little steps that ultimately create the unwanted texture you can see in the second pic.  Slicer settings are not changed between the two prints (other than on this occasion I tried the 'surface mode only' setting to see if it fixed the problem but clearly didn't.  I've tried rotating the models and reslicing and turning on and off other options but I still can't figure out why one prints fine and the other doesn't.  It happens randomly with models (not just this one) so I've had to start looking at the file size before I upload otherwise I know I'll get a poor print.

 

Any ideas?

20190414_123420.jpg

20190414_123437.jpg

Spiralvase2SurfaceModeandSpiral.gcode

  • Link to post
    Share on other sites

    Posted · Oddities when slicing for vase mode

    You didn't say what printer you have, but I'm guessing a hardware problem and not a problem with the settings. Check if all your axes are ok, have no play and are slightly oiled.

     

    It's hard to see on the photo, but I don't think it's under extrusion, or do you have holes in it?

     

    What might also help is to print slower.

  • Link to post
    Share on other sites

    Posted · Oddities when slicing for vase mode

    Hi Smithy - thanks for your reply.  The printer is a CR10S-Mini running the stock firmware. I think it's unlikely to be a hardware problem as other prints all come out fine (as do many of the vase mode models I've done).  There is a huge discrepancy between file sizes on prints that come out as expected and those that don't - the second picture model is very rough to the touch, almost like it is trying to fill a space rather than create a single shell.  Typically those that print properly will be a few hundred kb in size but those that don't will be eg. 20mb which is why I suspect slicer issues over hardware (I did do some maintenance on the printer last night to be as sure as I could be about it).  It's difficult to explain, but the print head sounds like its making a lot of micro-movements in a print like in the second picture, but will move smoothly in a successful print like the first picture.  

     

     

     

     

  • Link to post
    Share on other sites

    Posted · Oddities when slicing for vase mode

    Can you try to print the same object which is not working, without vase mode? Just to see how it behaves. A few layers are enough, just to see if there is a difference. And maybe you can upload the STL here, then we can cross check it. 

     

    When you have sliced the object and check it in layer view, do you see any similar issues there?

  • Link to post
    Share on other sites

    Posted · Oddities when slicing for vase mode

    I *think* I may have found a possible reason..

    I decided to limit the toolchain as much as possible so put the gcode directly onto the sd card rather than upload via octoprint - my printer seems to be happily vasing the mode 🙂

    I'm guessing it's possible that there is either a conversion or corruption of some kind happening when it uploads remotely if it's over a certain size.  I'm using a file that I've not used before so will go back to one that didn't work previously in a couple of hours when this is done and confirm or deny..

    Layer view always looked clean when I had checked it in the past, this was one of the head scratchers that was confusing me..

  • Link to post
    Share on other sites

    Posted · Oddities when slicing for vase mode

    So after running a few tests, it does appear that octoprint is the culprit.  The same files on the sd card vs uploaded remotely have massive differences how the printer actually prints the model.  Thanks for you replies Smithy, appreciate the quick responses - figured I'd update this incase anyone else has a similar issue in the future.  Right, off to the octoprint forums!

  • Link to post
    Share on other sites

    Posted · Oddities when slicing for vase mode

    Thanks for the feedback!

    I am not really using Octoprint, just tested it some time ago, but I heard that USB cables and/or the performance of your Raspberry (or whatever you use) can make a huge difference. So, for example, a Raspi Zero will work but not always because it can be too slow sometimes. Just a hint, if you want to dive deeper in your issue.

  • Link to post
    Share on other sites

    Posted · Oddities when slicing for vase mode
    On 4/15/2019 at 3:22 AM, Bracer said:

    So after running a few tests, it does appear that octoprint is the culprit.  The same files on the sd card vs uploaded remotely have massive differences how the printer actually prints the model.  Thanks for you replies Smithy, appreciate the quick responses - figured I'd update this incase anyone else has a similar issue in the future.  Right, off to the octoprint forums!

    Did you ever figure out WHY Octoprint was corrupting it, and what it was doing?

     

    This would be really vital information. A lot of us could have such problems and not know it.

  • Link to post
    Share on other sites

    Posted · Oddities when slicing for vase mode

    Hey All,

    I had to ask around a little since I'm not familiar with using Octoprint but I believe this behavior is more likely to be related to settings in the slicer.  If the segments per second is too high there will be buffer underrun. To improve this you'll have to tweak the Maximum Resolution.

    Other causes for this behavior could be:
    A. Using a Rasperry Pi that has outdated hardware (For example a first gen RPi0w)
    B. Faulty cabeling (please keep an eye out for transparent blue ones) 

  • 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

      • Introducing Universal Cura Projects in the UltiMaker Cura 5.7 beta
        Strap in for the first Cura release of 2024! This 5.7 beta release brings new material profiles as well as cloud printing for Method series printers, and introduces a powerful new way of sharing print settings using printer-agnostic project files! Also, if you want to download the cute dinosaur card holder featured below, it was specially designed for this release and can be found on Thingiverse! 
          • Like
        • 10 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...