Jump to content
Ultimaker Community of 3D Printing Experts


  • Content count

  • Joined

  • Last visited

Community Reputation

13 Good

About berndjm

  • Birthday 01/01/2015


  • Country
  1. So, little sleeping and thinking about a problem sometimes helps ;-) The script gets confused in the second run (for the higher located pause) from the "G1 Z" lines inserted in the first run. Reverse the order for the Pause at height (from highest to lowest) solves this issue. A little less intuitiv, but it helps ;-)) Maybe this is just another argument for a "Pause at layers" @tinkergnome ;-))
  2. Im using Cura 3.2.1 Appimage. Just noticed, if I try to use the "Pause at height" more than once it doesn'T work correctly Above is an exerpt from the generated g-code. There should be a pause at 0.8mm and the other one at 1.6mm As you can see, the code for the second pause is inserted immediate before the code for the first pause. Additional the 2nd pause records a false current height (should be 1.6)
  3. As far as I remember the user (= you) that runs a software which should communicate with usb-ports must belong to the group "dialout" to use the ports. Give it a try, just open a terminal an type in sudo adduser xxx dialout where "xxx" is your username.
  4. Cura Brim Bug?

    I think it's not so easy to detect the "real outside" and at the same time handle cases where the currently behavior makes sense. See this simplified use-case: Here it could be helpful to have the brim also inside the object. I think to have a adjustable threshold (is this the right word?) for the outside detection would be nice ... but how to handle than the two parts close together like in your 2nd screenshot?
  5. Cura Brim Bug?

    Indeed Cura makes the brim "outside" but it didn't recognice correctly what is "inside". There are quasi "insides inside insides", tried to visualize this here: If you set the brimline-count to 1 or 2 it becomes better visible how cura thinks, for example the "O" Because there is part 1 inside part 2 there "must" be A the outline for part 2 and B the outline for part 1
  6. pause at height - whislist:

    In some cases it's unnecessary in other cases it absolutely makes sense to handle the pause via layer-numbers. For example: I often make two-colored nameplates (with one extruder). The base-plate is 0.8mm high, the letters in another color are 0.4mm. Now I know, the pause had to happen at the end of 0.8mm (the 4th layer in my case). But if you have a unknown model (let's take this for example, which could be a nice multicolor print with one extruder) it is much easier to scroll through the layer view and say: "o.k. at layer x is the first color change on layer y the next", and so on...
  7. Thank you @tinkergnome, your answer finaly lead me in the right direction, placing the script in $USER/.local/share/cura/<Cura version>/scripts was unsuccessful and also was no hint in the log file. But, a little more searching brought me to: $USER/.config/cura/3.2/scripts where I could succesfully place my script. Not that intuitive place for it, I think ...
  8. Just a, maybe silly, question: Where should I store a custom-made postprocessing script that it will be recognized by the postprocessing plugin? In 2xx versions - not using AppImages - I had the complete PostProcessingPlugin folder (including my script) in .local/share/cura/plugins which works fine. If I do the same in 3.2.1 I see the PostProcessingPlugin is loaded twice (I asume 1 time from the AppImage and the other from my local folder) but my script didn't appear in the "Add a script" Selection list.
  9. Cura won't launch in Ubuntu

    Maybe this would be helpfull: https://discourse.appimage.org/t/how-to-make-an-appimage-executable/80
  10. Just noticed, that I get a good visible Z-Seam on a spiralized object (a simple soild cylinder). Inspecting the gcode explains where the Z-Seams comes from, but why is the gcode generated this way?!? Here an excerpt from the code around one "layer-change" G1 X84.653 Y88.444 Z4.785 E89.28759G1 X85.095 Y87.794 Z4.787 E89.29991G1 X85.563 Y87.191 Z4.789 E89.31188G1 X86.065 Y86.621 Z4.791 E89.32378G1 X86.621 Y86.065 Z4.793 E89.33611G1 X87.191 Y85.563 Z4.795 E89.34802G1 X87.794 Y85.095 Z4.797 E89.35998G1 X88.444 Y84.653 Z4.8 E89.3723G0 F5400 X88.659 Y84.526G0 X88.659 Y84.526 Z4.6;TIME_ELAPSED:248.010741;LAYER:23G0 X88.444 Y84.653 Z4.8;TYPE:WALL-OUTERG1 F924.4 X89.093 Y84.27 Z4.801 E89.38412G1 X89.792 Y83.913 Z4.803 E89.39642G1 X90.484 Y83.613 Z4.805 E89.40824G1 X91.214 Y83.35 Z4.807 E89.42041G1 X91.956 Y83.135 Z4.809 E89.43252G1 X92.702 Y82.968 Z4.811 E89.4445G1 X93.464 Y82.847 Z4.813 E89.45659G1 X94.232 Y82.775 Z4.815 E89.46868G1 X95 Y82.75 Z4.817 E89.48073G1 X95.768 Y82.775 Z4.819 E89.49278 As you can see Z increases smoothly to 4.8 than makes a move back to 4.6 and to 4.8 again than continue with the smooth incresement ... the backmove is one layer-height (0.2) This behavior repeats on every "layer-change" ....
  11. Registerkarte "Fortgeschritten" gleich ganz oben "Rückzug"
  12. Adjusting Startup G.Code/PIDs in Cura

    Send it without the : and without any spaces between the parameter and the value: M301 P24.99 or M301 P24.99 I2.10 D74.21
  13. Hi Manfred, this should be possible by sending M92 together with your desired value in the startcode. Have a look at this explanation: http://reprap.org/wiki/G-code#M92:_Set_axis_steps_per_unit Regards Bernd
  14. A Star is Born

    and than? Remember in which category(s) the setting(s) in question is(are), close the profile manager, open the category(s) ... wouldn't it be nice if a "star" (or whatsoever) in the category headlines indicates "ey man here are changes" ??? 8)
  15. A Star is Born

    I think I understand what DaHai want to say ;-) Imagine this (o.k. extreme example): O.k. - there is a change (indicated by the star) ... ... but "where the hell" is this change ...

Important Information

Terms of Use Privacy Policy