Jump to content

Daid

Ambassador
  • Posts

    4,700
  • Joined

  • Last visited

  • Days Won

    19

Everything posted by Daid

  1. It's doing infill->inner perimeter->outer->perimeter->top/bottom skin As then you go from fast to slower on the default printing profiles. Which is good for pressure changes in the nozzle. And increases the overall quality for Ultimaker prints.
  2. Normally Cura generates a log with can contain hints about errors at: C:\Users\[user]\.cura\15.01\output_log.txt But it could also be the case that you don't have any OpenGL 3D card drivers installed, which are a requirement for Cura.
  3. Most likely it's not your fault, but Cura's fault. The support code is currently a weakness in Cura, and can fail at random sometimes.
  4. You could easy do this from a post processing plugin. As this plugin will have access to the print time and material use headers that are added for the UM2 gcode.
  5. Actually, due to a bug in how the data was stored, you do lose it once after a certain upgrade. But you only have to adjust the initial level then, the bed still will be level, you just need to set the first height and the other 2 will be just right as before.
  6. Yes, just to annoy the hell out of you.
  7. Not every gluestick works. Very cheap ones don't really work. The UM2 comes with: http://www.staples.com/Staples-Washable-Glue-Sticks/product_SS992770
  8. In the forums? I https://www.google.nl/chrome/browser/desktop/ does this by default, wherever you go online.
  9. This is an pretty old change, you need to have an extra tag in the end code (added by default, but not if old settings are imported) This due to the fact that the profile data at the end of the GCode was confusing some firmwares (especially the BFB printers)
  10. https://github.com/daid/Cura Do your worst. Really, if you think it's so easy, do it. I'll see your pull request in a few days?
  11. Also make sure the Z screw is well greased. There goes a LOT of grease in the UM2 screw, much more then in the UMO. Switching to 1/16 stepping is also a good idea, but needs a small firmware modification (or some GCode fiddling)
  12. Nope. There is 12V on the board, but it's too limited in power to anything more then it does already.
  13. It will work. Forwards and backwards compatibility. So you can use older Cura versions on newer firmwares, or use older firmwares on newer Cura versions without issues.
  14. Daid

    15.02 RC2

    This can happen if your imported settings put a value "out of range", this will trigger this code: https://github.com/Ultimaker/Ultimaker2Marlin/blob/master/Marlin/UltiLCD2_menu_material.cpp#L852
  15. Note that the spaceclaim guys also claim that they where the original guys behind solidworks... (and they actually have a product, that works)
  16. Daid

    15.02 RC2

    Due to some critical problems, I want to move the 15.02 release very fast. So today or tomorrow. Right now I have an RC2 at: http://software.ultimaker.com/Cura_closed_beta/ The changes are: * Fixed problem with SD saving on Mac and Linux * Fixed problem with Cura not starting when you have "none ascii" characters in your username * Fixed UM2 retraction at the end of a print * Fixed UM2 priming after a filament change when pausing.
  17. The V2 electronics can be used in the 4 line character screen (it's done like that for the UMO+) The game won't work there. Because it requires the UM2 display (full graphical) The 1.5.7 electronics has a heated bed connection, however, you should not use it. The power supply connector and traces where not properly designed and cannot handle the amount of power needed for a heated bed. I would not recommend the 1.5.7 electronics for any new build. The V2 simply saves you a lot of trouble. Connecting a themistor to the V2 electronics is a bit more work. As the default temperature measure circuit is build for PT100. But there are analog pins available on the board that you can use for everything you want. There is ALWAYS room for a game :-) (It's hidden in the code, does not use any extra ram, and only like 2k of flash, which there is more then enough of in the UM2)
  18. V2 does software based motor power levels. V2 does not need additional cooling on stepper drivers. V2 has a safety circuit which could be used with thermo switches (currently unused in any of our printers) V2 is 24V instead of 19V. V2 uses PT100s instead of thermocouples.
  19. The glut32.dll file you copied is most likely the wrong one, causing these issues. Cura comes with a version in python/lib/OpenGL/glut32.dll You need to make sure that one is loaded instead of system one. (there should be no glut32.dll in windows/system32)
  20. This. Some older and strange firmwares don't accept the tool change commands. So for single extrusion it's better not to emit the tool change commands.
  21. Great, will roll out that version this week. Also to fix the SD problems.
  22. The drop downs have known problems on MacOS. But currently there is no way to fix this.
  23. In the "word of mouth" that is called 3mm.
  24. Unless you're having an issue with the latest release, you shouldn't be using the RCs. It's also quite a bit of work to keep release notes up to date on very RC. So that's why I collect the changes when I'm doing the final release. Note that 15.02 will be a quick bugfix release to address some issues that showed up in 15.01
  25. Firmware installs are never required. Some releases just improve some stuff (but the UMO firmware hasn't changed in a while)
×
×
  • Create New...