Jump to content

drayson

Expert
  • Posts

    936
  • Joined

  • Last visited

Everything posted by drayson

  1. Hi Thomas, never mind - hope it is a bit time for fun even at this long days. if it´s ok for you, I´m happy to act as a crash test bunny ? Just attach it to a PM, should work finde... b.r. chris
  2. Hi! any news on the update? As I´m in a bigger design project right now, it gets a bit annoying to have the names not propperly managed... b.r. chris
  3. Quite simple... download the ShowLayer.py file and safe it into ...\Users\xxxx\AppData\Roaming\cura\3.4\scripts start cura, open an STL, go to "Extensions" => "Post Processing" => "Modify G-Code" and then use the "Add a script" button to select the "Show Layer" postprocessor When slicing something, it automatically adds M117 lines with the corresponding layer number into your script. but I guess there is a much better description/tutorial how to use postprocessors available in this forum ?
  4. There is a postprocessor available which writes Layer Numbers into the G-Code file and displays them via M117. Maybe usefull for your application / UM3 too... https://github.com/AmedeeBulle/ShowLayer/blob/master/scripts/ShowLayer.py
  5. ? @Dim3nsioneer, kannst du da was dazu sagen?
  6. Having the same issue and I have also no solution up to now... Z-hop is a first shot in addition to combing, but my impression is that combing or "stay inside a part" is also not working propperly. ?
  7. as far as I remember, with 3.4.0 it was not an issue (working a lot with SW and print currently), but unfortunately have uninstalled it recently. Anyone else to assist??
  8. hmm... strange things happens... installed the latest 3.4.1. and 0.5.5 plugin, the name of the exported files got back to "unknown" @thopiekar, could you assist? thought this issue has been already adressed... anyway - here's the issue report ?
  9. I would like to have honey comb too, but for design reasons - but that's another story... ?
  10. ... but needs an account at MakePrintable - and is not free as far as I know, but pls. correct me if I‘m wrong...
  11. Thanks for the hint, but for me "python" is a big snake willing to choke me out if I'm to close... So frankly, no idea, as I'm not a SW guy... Maybe in a future release, some kind of selection for cloud or local and a path selection could be implemented too...
  12. or just buy black ones - fit to everything - from suits to dirty feet :-()
  13. Thanks for sharing!! Just minor a suggestion: could you paste the description you put on github also directly into the plugin.json? it might be easier to find the way if also in cura's toolbox this extended info is visible ?
  14. Sorry @ataraxis, havent seen all the postst in here - got no notification... Hope everthing worked out as expected ?
  15. Is there a way to set/change the backup to a local folder - e.g. my NAS system? Don´t want to use the cloud when having something in place - just another registration/login/password to forget...
  16. ... found it after a while seaching... Question: would it be possible to make a debug plugin for printer setups? so something that checks machine definitions, extruder definitions, nozzle cfg and shows issues? PS: sorry, don't want to abuse this thread... back to testing 3.4....
  17. hmmm.... I just put them in a cloth mesh to prevent them from escaping ? Good idea nico, but I had the experience that those sock clips wear off the area theyre mounted to over the time (and usually it is nearly the same place) Regarding material: I have a roll of vulcano filament which can be heat threated that should work with thumble dryer too...
  18. Just as an Idea... I usually put some info on gcodes I'd like to save for later reuse directky in the gcode file - as notes. a bit annoying as it is time consuming, but relatively save when there is a ned for reprinting something. Maybe there could be an additional text box for "further print information" which will directly written in the generated gcode...
  19. Great news that such a check is implemented - nevertheless, it just says that "there is an issue" but is there also somewhere a hint where in the cfg/json files it need to be fixed? I made some special config for my UMOadv (UM2 dual head on UMO) and get the note that "configuration is corrupt" and a list of files, so I´m struggling a bit looking for the issue... I know, it is somewhere in the nozzle definition
  20. Nice! hope that some bug fixes for combing and brim are in ?
  21. I would suggest to make te prefix/suffix setable in the printer settings. Everyone has it´s onwn needs - from no pre/suffix to a specific numbering/lettering. If it might be possible to set it in the printers settings - maybe with a max. of 3 digits - it could be easy self-configured and everybody is more happy than with a predefined one...
  22. Would be very helpfull... Maybe using the GodMode plugin could provide a workaround?
  23. That's already there - just go into Layer view and use the sliders or just the "play" button to get a preview of the nozzle runnin' around...
  24. Yes, please consider this feature... copying stuff is very likely to fail... BIG Thumbs up also for the updates @ctbeke
×
×
  • Create New...