Jump to content

Nicolinux

Expert
  • Posts

    3,003
  • Joined

  • Last visited

  • Days Won

    12

Posts posted by Nicolinux

  1. Hi,

     

    this is definitely not normal. Looking at the first picture from your last post, the second print core (on the right) has some material build up. Coudl it be that the materil is oozing from that core during the print?

    Also, which print cores are loaded? Just open the front lid on the print head and note down the print core markings (should be AA 0.4 or BB 0.4).

    It would also help if you could find out what kind of filament it is. Maybe there is a sticker on the spool at the back of the printer.

    If it is PLA, then in Cura select the correct material and switch to the recommended settings (see screenshot).

    Screen Shot 2018-08-29 at 22.51.38.png

  2. Hi and welcome to the forums.

     

    It looks like your model has a few errors. You can try to repair it with something like netFabb free or Meshlab.

    Other than that, it may be that some features on the model are too thin for the nozzle size to be printed correctly. Check out the "print thin walls" option in Cura.

    Screen Shot 2018-08-29 at 16.51.40.png

  3. Hi @FlorisM,

     

    sorry that nobody answered your questions. You did nothing wrong - I guess not many people knew what to do in this case since stuff that works only sometimes is hard to debug and there are no definite guides for this case.

     

    For the sake of helping others with the same problem, would you be willing to share your solution to this problem?

  4. I have printed with several PLA colors from Eumakers and I don't find prints to be brittle. Rather they feel like regular PLA prints.

    Only thing keeping me from ordering there are the crazy high shipping costs. I had hoped to finally find a replacement for Faberdashery... ?

  5. Hi,

     

    the cura.log file you have attached - is this from the 3.4.1 version when it crashed in layer view? If not, I would close all cura applications, empty the cura.log file for 3.4.1, start it again and reproduce the crash, and then attach the new cura.log here again. If there are other .log files like stderr - please attach them too.

  6. Hi,

     

    I don't understand your post. Are you ranting about the actual situation with your Makerbot and are you already disappointed by the S5 even before working with it? I think nobody here can guarantee a completely hassle free printing experience since 3d printing itself is a very complex process and with the endless combination of model geometry and filament properties you are bound to hit some edge cases - if you look for them.

     

    I have experienced the S5 as a stable 3d printer which builds upon the UM architecture and delivers very good prints with little friction. Since you are an experienced 3d printing user (even if your experience seemed to have been pretty painful with your old printer), I would assume that you already know what to expect of a 3d printer and to know about the limitations of that tech.

  7. Hi,

     

    sadly I am not familiar with your printer, but I assume that the test file that came with the printer is a .gcode fille. If that's the case, you could track down how it was produced (which software, which settings) and start from there. Maybe even looking inside the .gcode file would give you a hint since most slicers add a comment at the top (comments start with semicolon) denoting the software name and version.

  8. Hi,

     

    ich erinnere mich auch daran und ich habe auch damals die devs angemeckert dass solche halben Lösungen besser kommuniziert werden sollten.

    Anscheinend ist es aktuell so dass das Laufwerk X: automatisch gewählt wird da davon ausgegangen wird dass dieser Laufwerksbuchstabe nicht oft vorkommt.

    Quote

    Next release we'll be trying a different partial solution: Change the drive letter of the build server to X:, because that letter isn't used very often...

     

    @Mavic Wie ist der Stand aktuell bei dir? Kommt diese Fehlermeldung noch? Wenn ja und wenn du weiterhin nur Cura 3.4.1 installiert hast und sonst alle anderen Cura Versionen entfernt wurden, dann hänge bitte die neue "cura.log" hier an.

×
×
  • Create New...