Jump to content

Daid

Ambassador
  • Posts

    4,700
  • Joined

  • Last visited

  • Days Won

    19

Everything posted by Daid

  1. Both the flow and the filament diameter effect the same internal "how much material do I need to push forward" value. But that hardly makes them the same things. Larger diameter lowers the "how much material do I need to push forward" value, with a power of 2. While the flow is a direct adjustment of that value.
  2. FYI, My girlfriends work just got one of these machines as a trial, just 2 days ago. Right now they are not impressed, as a support engineer took 5 hours to unclog the nozzle. As replacing the nozzle would have been 1000 euros. He used up 20% of a roll of material during this cleaning. The solvable material is NOT water solvable. It's most likely PLA with an additive, as it's dissolved in drain cleaner at 70C. Each spot on the build plate should only be used twice, and if all spots are used up, you need to replace this part. And for the price of the machine alone they can put an Ultimaker2 on every persons desk at her office. Their software is greatly limiting the possibilities. And the support engineer was down-talking Makerbot all the time. Is that the way Ultimaker should move? Because that's not the way I want to move.
  3. The Z18 is a 5th gen machine, and thus won't work with Cura.
  4. Cura has been translated to russian already, but by default this is disabled right now, as I only have languages enabled which are verified by our re-sellers You can see the translation at: https://github.com/daid/Cura/blob/SteamEngine/resources/locale/ru/LC_MESSAGES/Cura.po
  5. Depending on which makerbot, they all talk a different dialect compared to all other printers. Some effort has been made for Gen4 machines (Replicator 2 and 2X). But no idea how well it works, or what is needed for it to work. But there are some Makerbot specific targeting in Cura. However, you might need some tricks and hacks to get it to actually work. Gen5 uses a different dialect all over again. And while someone has been doing some reverse-engineering work, there is zero support for the Gen5 Makerbot machines in Cura.
  6. Yes, it's milliseconds, and you can just adjust that value, and compile&upload with the arduino environment.
  7. If you want, you can mess with all settings straight from Cura. You just have to set the "machine setting -> gcode flavor" to "reprap (Marlin/Sprinter)" and you will have access to all the retraction and temperature settings from there, overruling whatever you have set in the machine for that print.
  8. AutoTemp is something that can be done. But it needs 4 parameters: minTemp, maxTemp ©, minFlow, maxFlow (mm3/s) Now, autoTemp won't be the way to go always, but for "preset" materials like PLA, ABS, and other stuff that we're testing, I'm sure we can do it quite fine.
  9. The UM2 firmware limits to 45mm. But anything above 25mm/s you risk stripping the PLA instead of retracting it. Above 45mm/s the motor simply has no power at all to move the filament.
  10. Which version? Any special start.gcode?
  11. Setting the temperature as a function of the speed is something I'm going to work on soon. As the more we push our printers, the more this is needed to be done in a logical way.
  12. Not really. Only thing I can tell is that the glut library fails to load properly. Why and how to fix is kinda impossible for me to diagnose from a distance.
  13. You can do this without a plugin and by just adjusting the start.gcode.
  14. Note that 5 nozzle support was never tested, so it might be broken.
  15. Daid

    15.02 RC2

    The RC2 is the same as the 15.02.1 feature wise. The RC's are "release canidates" and thus are made before the actual release. Newer versions will be 15.03-RCx versions.
  16. Be sure to use 15.02, 15.01 had a bug related to this.
  17. Best way would simply be to re-install Cura. This won't wipe settings, and will allow you to bind the stl to Cura again.
  18. Yes, the work repo is private right now. (Also due to the fast changing nature of this code)
  19. In all honesty, then I also have no clue where to look. The log file is populated with all the output from my application, so something is crashing before my code runs. You might get some extra information if you start Cura from the batch file in the Cura install directory.
  20. The shell thickness is what's causing problems for you here, goto the 1.8 as Arjan suggests.
  21. Goto the expert options, in "black magic" there is "only follow mesh surface" this will most likely do what you want. This is the limited case where this option is for :-)
  22. The timeline is to have a first test version out in about 4 weeks. Note that this will lack some features compared to the current Cura. No, don't use the PU version linked earlier. We did one step back again when we hired Arjen. And the earlier test version no longer reflects what's actually being made right now.
×
×
  • Create New...