Jump to content
Ultimaker Community of 3D Printing Experts

klaus_kraemer

Member
  • Content Count

    34
  • Joined

  • Last visited

Community Reputation

1 Neutral

About klaus_kraemer

  • Birthday 09/01/1962

Personal Information

  • Field of Work
    Other
  • Country
    DE
  • 3D printer
    Ultimaker 3

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. klaus_kraemer

    Moving filament during material change

    A little bit crude - always a chance of tearing off part of the filament inside the extruder. I'd rather treat machine and filament gently...💪
  2. klaus_kraemer

    Moving filament during material change

    Filament change: I just experienced a weird situation, when I wanted to change Willowflex filament (a flexible one) for normal PLA. As friction of Willowflex against the Bowden tubes is higher, Willowflex is not totally removed from the Bowden tube and the extruder. The only option UM3 firmare offers ist to confirm, the filament to remove has been removed - nothing else, silly! There has to be an option to move filament manually until the filament is really removed or at least an option to end the filament changeing procedure. That way you could use the menu to get to the point where you can move filament manually.
  3. klaus_kraemer

    Display current layer number during printing

    Thank you @drayson, but I simply wouldn't know how to use that code... The more I think about it, the more I feel that Cura Connect should provide extensive information about the current print job. Let's wait and see...
  4. klaus_kraemer

    Display current layer number during printing

    I imagine, it is the only way I can monitor print and decide when I have to control whether some special or critical part of a print works out. Its mostly about deciding whether to cancel the print or not at that point. I've spent to much time in front of the printer, waiting for certain parts to be printed - unnecessary wate of time due to lack of information. I can easily get the layer number from the layer view in Cura. Other ways of avoiding that issue would be a more detailed information via Cura connect web interface, which is simply one of the poorest I can imagine... indicating a time in Cura's layer view, predicting when a single layer will be printed before completion of the whole print. So you could always compare with the remaining time for printing on the UM's display. The solution does not necessarily have to come via the printer's display, it could also come from Cura's web interface. From another point of view: Indicating the remaining time AND e.g. 'Z 1000/1784' wouldn't be so difficult and bad...
  5. klaus_kraemer

    Display current layer number during printing

    Any clue this feature request got into the next firmware release?
  6. klaus_kraemer

    CURA download popup questionnaire

    Just saw that possibility - thanks for the hint! But anyway - the popup is annoying and unprofessional...
  7. klaus_kraemer

    Cura Connect stuck showing old print jobs

    This happens way too often to be solved with a workaround only!
  8. klaus_kraemer

    CURA download popup questionnaire

    Every time, I try to download a CURA update, a popup form starts asking me the same boring questions. I really don't like redundancy and I'm logged in. So why are you asking the same questions again and again? Until now I've answered these question to my best knowledge. For the future I'm tempted to simply click some items from the menu to get the update downloaded. Will that random and wrong data help you in any way? I don't think so - but you don't seem to be really interested in that data, otherwise you'd keep them in a dataset under my account. I am quite sure, many users simply click something to get forward and I'll join them...
  9. Quite hard to believe there shouldn't be a way to get around this behaviour. Ok there's no printer driver for UM3 as far as I know, But continually testing an IP connection should be feasible anyway...
  10. klaus_kraemer

    Cura 3.4 "Brim Only on Outside"

    ? Thanks!
  11. It's Windows 10, the "thing" is very much consistent and can be reproduced by 100%. No , it does not matter how long Cura has been running - it's simply about the order what's been started / switched on first. You start Cura before switching on the printer, Cura's only offered choice is "Save to File"... Never tried this, because I didn't connect "managing" Printers to the problem. Sure will try these days as a workaround.
  12. klaus_kraemer

    Cura connect shows wrong print job info

    Have the same issue - can confirm what you've been writing.
  13. Sometimes it's quite annoying - why does Cura only recognize an UM3 when the UM3 is already switched on before Cura got started? If you have Cura already running and switch on your UM3 afterward, Cura won't connect to the UM3. If Cura has been started before the printer has been switched on there is only one solution: close Cura, switch on your UM3 and then restart Cura. Not very convenient...
  14. klaus_kraemer

    Cura 3.4 "Brim Only on Outside"

    This setting seems buggy: Look at both screenshots - I only have changed the "Brim Only on Outside" checkbox. No other parameter has been changed. Look at the differenc in printing time between both settings! Why should an inside Brim like that take about 2 days and 6 hours, while the print with "Brim Only on Outside" set takes only 2 hours???? (And in the following screenshot additionally look at the printhead movements with the magenta print material seemingly leaving the printer for an all but endless journey...)
  15. klaus_kraemer

    Feature missing for support structure: wall thickness

    I just saw that CURA 3.4 will introduce "Support wall line count. Added setting to configure how many walls to print around supports." Found in CURA 3.4 beta changes... THANK YOU!! ?
×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!