Jump to content

gandy

Member
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

2 Neutral
  1. Even though the tags are not marked to contain NDEF records, the data stored in the NFC memory adhere to the standard. There are four records one of which contains the material UUID and two others storing the amount of material on the spool. The tasks of understanding the individual data structures and how to fill them in gets much easier consulting the relevant python code on the printer. This way I managed to successfully write the UUID of a 3rd-party material to the tag of an empty spool and transfer the tag to a fresh spool of said material. I also managed to create a cura plugin for this material with both the generic and the vendor specific definitions, together with a set of profiles (which now need to be refined to meet their intent). This way, Cura uploaded the fdm_material file to the printer which now fully recognizes the material. We can even use it with the material station without any obvious restrictions. However, I am still a bit uncertain as to how to tune in the material station related parameters. For starters, I used a fdm_material file of a material with similar properties, but I'd feel much more at ease if I knew the relevance of each parameter and which material properties I need to take into account. Is there any sort of documentation on this? Another question is where we could source a small number of these circular tags, right now we don't have enough empty spools to live off recycled tags.
  2. @robinmdh, thank you for the detailed information on the probing data. Actually, yesterday after ssh-ing into the machine and just before leaving work, I found the column description in the comments of the relevant python code. I'll probably extract one or two measurement curves out of curiosity, but my original question is answered. To summarize: There currently is no parameter to correct for the observed error in first layer height on the machine level. Due to some DM exchange with @nallath the issue is known and possibly being resolved in the future. Obviously, this may take some while. Currently, there is an existing workaround in form of the z-offset-plugin for Cura. Thanks again to all participants for the discussion, Cheers, Andy.
  3. @ahoeben, I guess I have understood the motivation behind the plugin and the benefit as a workaround in the case of the S5 perfectly the first time, thank you. Regarding the issue at hand, of course you can choose to not follow my line of argument, but as you say: Each its own.
  4. @robinmdh, thank you for the two links, I wished I had known about those a week ago 😀. It's good to see how much information you share on your products, nowadays this is not typical for most businesses. The first article actually confirms my assumptions on how the probing scheme works. I'll check out developer mode and the measurement data later, but do they really contain all measurements while the bed is approaching the bed up until the probing ends (like the curve of the sensor signal vs. z-position shown in the first article) or is it just the raw z-position of the trigger points for each probed x-y-position on the bed, i.e. some sort of topography map? And yes, build plate adhesion is an important issue, but that's not my point. My point is that the first layer height is wrong and the apparently broad user base of the z-offset plugin that served as a workaround shows that there is a systematic issue that users have the need to compensate for. My argument is, that this compensation at user level would not be necessary, if the compensation would already happen at the machine level. I've just learned that this is something being worked on, so for now I'm accepting the use-as-is and looking forward to a future firmware possibly taking care of a perfect initial layer height 😉
  5. @nallath, thank you for getting in touch and confirming my theory. @ahoeben, I am sure the z-offset plugin does a wonderful job and if the printer does not allow to adjust for the error in initial layer height it is indeed the only way to keep dimensional accuracy. I will definitely give it a try, thank you for your work! @tinkergnome, you're right, squeezing in the first layer is an important factor to improve bed adhesion. That's why most cura profiles default to 120% initial layer line width. Active leveling on the other hand allows the printer to correct for a non-planar printing bed surface, making certain that the distance of the nozzle to the bed surface is the same for all positions of the bed, which is necessary for homogeneous material deposition. The intended result of any kind of bed leveling, be it manual or automated, should not be a false distance, as this really messes up dimensional accuracy.
  6. @ahoeben, thank you for the suggestion. I somehow hoped for an actual settings parameter in the printer. I do not really know how active leveling is implemented in the UM S5. Surely, the capacitive sensor in the printhead is used to determine the distance of the printhead from the bed. During each probe, the nozzle not only touches the bed, but the bed is raised a little further still, so much it tilts ever so slightly, barely noticable. I've seen a few videos of other S5s and also UM3s doing the same, so I assume it's part of the probing scheme. That may imply that the firmware checks for which z-height the capacity sensor's signal starts to flatten out. That would be the position where the nozzle makes contact with the bed surface. It would be quite independent from the bed material, too (metal under glass or bare aluminium), as long as there is something the sensor can react to. But it could still leave a certain offset that needs to be corrected. Maybe someone from ultimaker could bring a little light into this, the fact that someone went to the troubles of writing a z offset plugin in the first place indicates that I'm not the only one struggling with the initial layer height. And honestly, I believe this needs to be corrected at the printer level, not the slicer.
  7. Hi @SandervG, I just sent you a DM with the logs, hoping this helps. Cheers, Andy.
  8. Our new UM S5 arrived a week ago and from day one we've got an inconsistency in the height of the initial layer. We've tried printing Strong PLA, Nylon and TPU (all from Ultimaker) and on all materials, the first layer was of a consistent 0.16 mm height instead of the 0.2 mm specified in Cura. Same happens with PVA on the second printcore. Consequently, we need to reduce the matierial flow of the first layer to 80% to not get a totally overextruded first layer. We ran the manual bed leveling several times, even with different spacers (the thickest being a PCB with riduculous 1.6 mm), all yielding the same results. Active bed leveling was activated for each print, which may explain that the manual leveling was effectively without effect. But if this is the case, there surely must be a way of calibrating the z-offset for the active bed leveling, right? Several online searches did not turn up any results, but maybe someone here in the forum can help? Any hint in the right direction is highly appreciated. Thanks, Andy. Edit: Tested and verified for the second printcore with PVA loaded.
  9. Hi @SandervG, thank you for your welcoming words. I assume the log needs to be saved before the next reboot? I just learned my colleague rebooted the printer this morning after the camera feed got lost again over the weekend. Consequently, the dmesg file only shows messages from after the reboot. Do you need all the files stored on the USB stick or only a subset? Can I attach a ZIP archive to a DM or do you have better suited ways of uploading this kind of data? Not sure if they belong in the public area. Thanks, Andy.
  10. @SandervG we installed the latest Release on our brand new S5. Alas, this version appears to be less stable than the previous one that was pre-installed on the printer. Here's what we've encountered sofar: The camera feed, both viewed through cura and the webinterface, shows occasional dropouts of part of the image, i.e. the lower quarter or half of the image flickers briefly. After several hours of operation, the camera feed stops working On some of our computers in the local network, the printer disappears from cura and can not be discovered again though "Refresh", but works fine on other computers at the same time Just now, when trying to swap out filaments (different colors of Ultimaker Tough PLA), the new filament was not recongnized, a few seconds after that, the printer threw a ER998 at me, asking for a reboot. Filament detection worked flawlessly afterwards. None of these things occured during days of operation before installing the new firmware. The material station and air manager are on backorder, anyways, so meanwhile, we may want to go back to the previous firmware. Where can we download the image? Finally: I'm new to the Ultimaker ecosystem, is this the right channel to report this? Thanks, Andy.
×
×
  • Create New...

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!