Jump to content

berndjm

Dormant
  • Posts

    105
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by berndjm

  1. Hi Matthias,

     

    Now, it prints very good, but only two sides of the Model and i dont know why ?

    So...what did i wrong please?

    Seems like the two no-printing walls are slightly smaller than the others.

    Try "Shell thickness" a bit smaller than 1mm e.g. 0.9mm

    Or design your test object so that the 4 walls have the same thickness.

     

    In Cura, i use Cura 15.04.6, it is fully displayed.

    Even in the layer-view? I don't think so ;)

     

    An additioonal question...what is the difference between Cura 15....and Cura 2....?

    Puuuh, this would become a very long answer.

    Basicly the 2.xx is a complete rewrite of the 15.xxx software with new features, more parameters to fiddle with and a new GUI. But it's still "Beta".

    For a newbie in 3D-printing I would suggest that you stay with the 15.xxx version and make your experiences and get become able to understand how the things and parameters work together.

    Regards Bernd

  2. As far as I remember the postprocessing plugin isn't installed automaticly in the Linux-(PPA)-Version, but you should be able to install it manualy either via Synaptic - search for "cura" - there should be "cura-extra-plugin-postprocessing" or via a Terminal with

    sudo apt install cura-extra-plugin-postprocessing

  3. Don't know if it is relevant for the UM-Hardware but for some other printers, on Ubuntu it's necessary that you (the user) belong to the group "dialout" to be able to communicate via USB with the printer.

    Give this a try (in a terminal):

     

    sudo adduser $USER dialout

     

  4. Changing the infill density during a print isn't possible as far as I know.

    Printig with 100% infill the whole model is surely not the option, 'cause it's a waste of material and time.

    But perhaps you can play with the "Shell Tickness" to force printing more shell-lines so there isn't any need for an infill in the smaller part?

  5. Mmmh ...

    doing a little mathematics would make the life easier ;-)

    Assuming you have the following in your print profile:

    Layer Height: 0.1mm

    Initial Layer Height: 0.2mm

    No you want to Pause at Height at Layer No 10

    So you have 1 x 0.2 + 9 x 0.1 = 1.1 mm

    No fiddling with layer numbers and so on needed ...

  6. Cura 2.1.2-0 for Linux is neither production ready, nor beta. It's pre-alpha software.

    Wow - big words!!!

    Please tell me how I managed to work with 2.1.2 for nearly a month now on Ubuntu 16.04 using topiekars PPA ...

    Have you ever read the link I gave you above?!?

    Did you try to install the dependencies mentioned in this link:

     

    sudo apt install qml-module-qtquick-dialogs qml-module-qtquick-controls

     

    ?

    Have you ever made an update for this PPA?

  7. Think your problem is the missing orientation if you rotate the whole buildplatform and you use a self-made printer profile?

    So there is an easy solution:

    Have a look at the printer-profiles shipped with cura, there is always a kind of backplate with a lettering (the key is "platform") - this is the "back side" of the printer, so asuming your Home(0,0,0) is in the front left corner.

  8. Nozzle size is .4mm and wall is 2mm thick

    Some times I noticed that the legacy cura is a bit "bitchy" on some parts where the wall is whole-number from the nozzle size. In this cases helped me either to make the wall a tiny bit larger (e.g. 2.01mm) or "fake" the nozzle size (e.g. 0.39mm) ...

  9. In 2.1 it's possible to place the parts as close as you want. You have just to disable Settings -> Preferences -> General -> "Ensure objects are kept apart"

    cura_placement_1.thumb.png.f7c065d32cadea301cf425411c017d5a.png

    you can even do "funny" things then

    cura_placement_2.png.406acdea76190c3f91853a47d7006629.png

    although the printpath-planing isn't very "intelligent" in this case

    cura_placement_2_layer.png.6734c278275d3564e4b76a3a39bcaa35.png

    cura_placement_1.thumb.png.f7c065d32cadea301cf425411c017d5a.png

    cura_placement_2.png.406acdea76190c3f91853a47d7006629.png

    cura_placement_2_layer.png.6734c278275d3564e4b76a3a39bcaa35.png

    • Like 2
  10. Just "thinking loud" about the connection to OctoPrint:

    A nice way would be to "hook" in the save button/dropdown something like "Send to Octoprint".

    The needed data (API-Key, IP-Adress ...) could be stored in a .cfg file in /profiles - like the material profiles (than with type = octoprint). If such a file (or even more) exists there will be additional entry(s) in the "Save" dropdown.

    Would this possible or are my thoughts to utopic or to simple-minded ...

  11. Just played a bit with the TweakAtZ plugin.

    Seems that the (mis)function depends on the printerprofile and may be have something to do with the heated bed:

    If I use e.g. the Ultimaker 2+ profile all works fine and the changes in the gcode are present. If I use e.g. the RigidBot Profile there is the error and in the console on save I get:

     

    2016-05-18 10:21:29,917 - ERROR - Script raised the following exception 'bedTemp'

     

  12. Is there a documentation for the printer.json files?

    Special which parameter goes to which section and what they affect in the different places. And what effect have the "visible", "always_visible", "active_if" settings in detail?

    For example:

    in prusa_i3.json is in "machine_settings" defined:

    "material_diameter": { "default": 1.75 },

    in RigidBot.json is defined in "overrides" as:

    "material_diameter": { "default": 1.75, "visible": true },

  13. However, Cura 15.04.5 / Linux can not even process STL files STL files with a relatively moderate size of ~5 MB, ~50000 vertices, ~100000 faces (from Blender), and that sucks big time :-(

     

    Can't confirm this, just processed a part with 6,8 MB, 68446 vertices, 136879 faces without problems or noticable time consumption.

    If it didn't work for you, there must be an other reason than the file size ...

×
×
  • Create New...