Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


ahoeben last won the day on January 27

ahoeben had the most liked content!

Community Reputation

850 Excellent


About ahoeben

  • Rank
    fieldOfView on Github
  • Birthday 04/14/1975

Personal Information

  • Field of Work
    (Product) design
    R&D / Exploration
  • Country
  • 3D printer
    Ultimaker S5
    Ultimaker 2+
    Ultimaker Original
  • On The Web

Recent Profile Visitors

5,001 profile views
  1. Writing .hvs instead of .gcode is not something that can be done in a Cura profile. It can be done with a plugin, but writing plugins isn't for everybody; there's no guide or tutorial to follow for this exact usecase.
  2. The file you posted looks like a normal gcode file to me. The only thing that makes it a little special is the very first line of the file. Could you try the following: * slice a file with Cura * save it as a .gcode file * rename it to .hvs (make sure it does not become .hvs.gcode!) * open the file in a text editor (eg notepad) * as the very first line, insert the following: M911 3DP-310F * save the file and try to print it
  3. Your printer definition is incomplete; it does not have an extruder definition. Cura creates one in the background, but apparently there's something conflicting with my code when it does. I'll fix future versions of my plugin to be robust against this.
  4. What printer definition do you use for your Lulzbot Taz? It is not a printer that ships with Ultimaker Cura. The reason I ask is that while your logs pointed me to what is going wrong, it is strange that it is not going wrong for the printers that do ship with Ultimaker Cura. I'll make future versions robust against this issue, but there may be an issue with the printer definition you use. About static text: You can type any text instead of {machine_nozzle_size} or other replacement patterns.
  5. Have you tried printing at a lower temperature? Lower temperatures normally cause less stringing.
  6. @Scotty-G, could you post a link to your cura.log file (Help -> Show configuration folder, cura.log is in the folder that opens)? For your printer that supports multiple filament diameters, I would set up two different printers in Cura, one for each filament diameter. Then you can just add a different static text to your custom prefix for each printer/material diameter if you want.
  7. Please try the 4.5 beta. It has some changes in it that could fix this issue.
  8. @imcarterschmidt could you check the Cura 4.5 beta, with that plugin enabled? A third party component in that plugin has been fixed/updated by UM, which hopefully fixes these performance issues.
  9. I'm not sure if I love or hate that trick with the Cyrillic S. Probably both 😉
  10. Perhaps if you post a link to a working .hvs file, we can have a look if writing to or converting to that format can be easily supported.
  11. An updated version of Sidebar GUI (4.0.7) has been posted to the Marketplace, which adds compatibility with Cura 4.5, fixes a couple of bugs and adds a toggle to switch between perspective and orthographic projection. Subtle changes. Edit: See the shiny new web-based Marketplace: https://marketplace.ultimaker.com/app/cura/plugins/fieldofview/SidebarGUIPlugin
  12. Aww, thanks for mentioning me 😉
  13. What is happening is that the model is broken/unsuitable for 3d printing. I'm guessing the model has infinitely thin walls, ie the walls show white on one side and blue-ish on the other (in sketchup; did I guess correctly?). All walls need to have thickness to be printable, or Cura will get confused about being inside the wall or outside the wall.
  14. The model probably has a small hole or gap that is throwing off Cura. It needs to be "repaired". If the hole is small enough, perhaps the Mesh Tools plugin "Fix small holes" works. If not, you could try Meshmixer or Netfabb or another tool that comes up when you google "3d model repair".
  • 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!