Jump to content
Ultimaker Community of 3D Printing Experts

ctbeke

Team Ultimaker & Admin
  • Content Count

    410
  • Joined

  • Days Won

    6

ctbeke last won the day on January 10

ctbeke had the most liked content!

Community Reputation

114 Excellent

3 Followers

Personal Information

Recent Profile Visitors

1,804 profile views
  1. Thanks for reporting, I'll relay this to the team working on this functionality.
  2. We've started an internal investigation into this. It seems like the printer is a bit too restrictive with which characters it does not allow when parsing file names, and there's also some inconsistency between Cura, Cloud and Printer regarding the validation rules. Since Cura and the Printer firmware are not released continuously, it'll take some time before any fixes end up in releases, but we're working on it for sure 🙂
  3. @Gero very helpful and thorough debugging! I'll take this issue back to the team to see if something can be done about it!
  4. For any networking/cloud related issues, please check the sub forums about Digital Factory as well. There have been several posts there with in-depth analyses and (temporary) fixes. In short, network issues are always difficult to debug because it could be a problem with the hardware, embedded software, the specific network setup (i.e. a customer had issues with DNS because in their network setup Microsoft Active Directory deviated from DNS caching standards that our printer software assumes are in place, as they should be). Usually it comes down to sending us the printer debug logs so we can
  5. Unfortunate that you can't do some tests, but no problem, I understand how IT departments can be 😛 Could you confirm with them if they happen to run Microsoft Active Directory in the network? And if Active Directory is used for domain control and DNS as well? If so, you're likely experience a known (but yet unresolved) issue where Active Directory does not fully adhere to DNS specifications that the printer expects are in place (see the long thread above about this topic). If not, we'll have to dig deeper and find another root cause of your DNS resolve error logs. Chris
  6. Hi @epakkane, I've scanned through your logs and I see the following line: socket.gaierror: [Errno -3] Temporary failure in name resolution This means the printer was not able to resolve the api.ultimaker.com DNS record. This usually happens in certain network setups where for example the DNS server on the LAN caches records for too long. Things you can try: * Reboot the printer. * Do a factory reset via the touch screen. * Check if you can resolve api.ultimaker.com manually from your own computer (in the same network), e.g. using nsloo
  7. Ah, I think we were confusing print speed (movement in xy direction) with extrusion speed (how fast the extruder motor pushes out the filament). In my posts I meant the latter.
  8. Np, it's fine to disagree on something, as long as it's civil 🙂 Anyways, Cura is open source, so if you have ideas and/or abilities to write something that could solve this (for either modifier meshes or adaptive layers), feel free to do so!
  9. The extruder motor (E values in G-code) only determines the speed component of that equation (again, this is the one with the physical delays caused by the distance between extruder motor and hot-end). The position of the extruder (X, Y, Z values in G-code) determine the (layer) height and are determined by the motors that control the X, Y and Z axes. The width is mostly caused by the nozzle diameter (with some limited control over that by how much material you push through). So although it's a single set of settings, or even a single G-code command even, the results are influenced by many dif
  10. I'm not sure, I'm only reporting on what I experienced during testing. However I can imagine that because height, width and speed are implemented by different parts of the mechanical system, these 3 never align as perfectly as you want them. For example layer height has a very direct result (just move the Z-axis up), but speed has that delay between moving the extruder motor vs the actual extrusion at the hot-end caused by the physical distance between those two components. So all combined it's just a complex system that is hard to capture in a mathematical model that can be used to 'predict'
  11. The delay is not caused by settings, it is caused by the physical process of pushing on the filament with the extruder motor, then that force actually resulting in more or less material being extruded at the hot-end. So in a perfect world with no friction inside bowden tubes etc (and many other physics laws), the settings above would work. But in practice you always have that delay and you get visual artifacts in your printed part.
  12. Theoretically yes, but in practice this is hard because there's delays between the G-code instructions and the physical act of laying down material and it cooling off (mostly caused by the distance between the extruder stepper motor and the hot-end). So you could write something to 'look ahead' and take that delay into account, but that's very hard to do as well as you'd need to model these delays and other physical properties of the printing process. Also Cura cannot really change the line width currently (although a new version of CuraEngine is being worked on that has that capab
  13. Hi! I'm not expert on the slicing engine and the physics of laying down molten plastics, but to me it seems in order to get a clean print when changing the layer height, you still want a consistent line width (otherwise you get 'banding'). To achieve this, when reducing the layer height, you want to extrude less material, so a lower flow rate. But in the current architecture of both the slicer and the printer mechanics, it is nearly impossible to change the flow in a short time frame (from one move to the next ideally), so when building adaptive layers I've tweaked around with the parameters u
  14. Note sure who is using this IRL (as it's still experimental as well), but the biggest advantage of adaptive layers over modifier meshes is that adaptive layers changes the layer height gradually, resulting is less sudden changes in the flow rate (this proved to be the biggest contributor to ugly prints whenever the layer height changes when I did the research and testing for the adaptive layers algorithms).
  15. Unfortunately such a simple statement would often not be true, because it very much depends on the topology of the model you're slicing. But if there would be a single way to capture the concept, I'd say it determines the 'hardness' or 'sensitivity' of the algorithm, similar to how Photoshop brushes can have hard or soft edges.
×
×
  • Create New...