drayson

Thanks, what type of printers do you have installed? Another person also reported this: https://github.com/Ultimaker/Cura/issues/2837 Same happens at me... Workaround (del cfg) is ok for a beta test, but bug need for sure to be killed for final :-)

Great!!! btw.: I assume, the jogging is alsu usable at UMO's - isnt??

:-D Honestly, I fully agree... so pleeeeaaaassseee let the beautifull death stare alive...

Whow, great... as Dim3nsioneer mentioned, a simple code sender would be great to be also included, but for the first shot, it's great to be able to just jog the thing... :-) btw: any chance to just port existing things e.g. pronterface, universal gcode sender,...?

second this request :-)

Servus Thomas! Some time passed, but now I had a moment to give the macro also a try at SW2013... works flawless there too... :-) Just a remark: as the cura version get new releases, it might be good to just call the button "Export to Cura" and remove the versioning. But thats jsut my two cents

Servus Thomas! Some time passed, but now I had a moment to give the macro also a try at SW2013... works flawless there too... :-)

that's already work - place some pancake dought at the build plate and give it some heat... :-)

I bought the SSS for my 2012 edition UMO - the TMC2100 - directly at Watterott. http://www.watterott.com/index.php?page=product&info=4107 It was a straight forward change with only one hurdle at the second extruder. Just make sure you buy the right heat sinks :-)# I can fully recommend the SSS as my UMO got that quiet and also the zebras have been nearly gone (but I never discovered them as THAT annoying...). If it also has effect on the end-of-step-uneveness, I have no idea, but keep us updated...

ok, another year went by and there is another guy like to use the z offset... :-) So IF I set all a.m. modifications AND define a new variable EXTRUDER_OFFSET_Z in configuration.h in the area of offset definition // Offset of the extruders (uncomment if using more than one and relying on firmware to position when changing).// The offset has to be X=0, Y=0, Z=0 for the extruder 0 hotend (default extruder, T0).// For the other hotends it is their distance from the extruder 0 hotend.// #define EXTRUDER_OFFSET_X {0.0, 20.00} // (in mm) for each extruder, offset of the hotend on the X axis// #define EXTRUDER_OFFSET_Y {0.0, 5.00} // (in mm) for each extruder, offset of the hotend on the Y axis#define EXTRUDER_OFFSET_Z {0.0, 1.00} // (in mm) for each extruder, offset of the hotend on the Z axis AND put it in the correct area of marlin_main.ccp (incl. commenting out the dual stuff), // Extruder offset#if EXTRUDERS > 1//#ifndef DUAL_X_CARRIAGE// #define NUM_EXTRUDER_OFFSETS 2 // only in XY plane//#else #define NUM_EXTRUDER_OFFSETS 3 // supports offsets in XYZ plane//#endiffloat extruder_offset[NUM_EXTRUDER_OFFSETS][EXTRUDERS] = {#if defined(EXTRUDER_OFFSET_X) && defined(EXTRUDER_OFFSET_Y) && defined(EXTRUDER_OFFSET_Z) EXTRUDER_OFFSET_X, EXTRUDER_OFFSET_Y, EXTRUDER_OFFSET_Z#endif};#endif it should be possible to define the z offset during compilation and no need for M218 - isn't?? Well, I'm using a Marlin version of 2014, so it might look a bit different now. (but my UMO runs fine on it... so why change a running system) :-)

@nallath, is there a way to get our hands on it to give it a try??? (guess it´s not at your github :-) ) I have a lot of situations where I would need this feature highly - e.g. on model heli fuselages... It's super unstable. A lot of models just make it crash. :-( very sad... the cutting via netfabb or other additional software is really annoying if something has to be done in a rush... Hope some day it will be stable enough to let me do a try.

yes, if you look into the plugin browser, there is the note to install or even update it. went flawless... The days I used SW in study and office we never did something with macros - most of the stuff I learned by myself. Grüße aus Graz! :-)

Nope this should no happen. Are you using the plugin since Cura 2.7? PS: I never had the time to track the oldest version, which is able to be used, but since the first version of the plugin, which was released in the plugin browser in Cura 2.7 a lot of things have changed to increase stability. Please remove the plugin if needed from cura's config directory Yes, I use it since 2.7.... I made an update of your plugin and now it behaves normal. Open files without closing SW and also the rendering is ok. Guess the file integration is ok, the SW integration itself of course not. Saw that there should be an icon in SW, but for this it seems my version is too old. Nevertheless - THANK YOU for your efforts!

Hi! Great plugin! I use it with SW2013 (student license). One thing I noted is that SW is closed when opening a file in Cura, but I guess that's because of the old version... Further the part is in a very dark scheme. Again, thanks, now I have a reason looking for an update... :-)

@nallath, is there a way to get our hands on it to give it a try??? (guess it´s not at your github :-) ) I have a lot of situations where I would need this feature highly - e.g. on model heli fuselages...

@ultiarjan, guess it would make the things too easy for our colleagues in copyland...

@ Neotko, I understand your step really and would like to thank you for your time and efforts you spend to assist here, discuss issues, gain and share experience and bring the 3D print forward. Your words also acts like a kick to also share my thougts... I visit this place randomly, but nowadays more seldom as before. And I contribute less.. Reason is simple: the time I started here to learn was full of fruitfull discussions about how to gain knowldedge, find new solutions or sharing thougts and ideas - and of course also somtimes to place stupid questions :-) But in the meantime I feel sometimes, that a friendly "RTFM" might be the only suitable answer as the time for gaining knowledge and fruitefull discussions is mostly gone, swaped away by industrialization and "plug&play" menthality just want to "do" but not "understand". Anyway, it's maybe the wrong place to share my feelings, but as mentioned, somethimes you get a kick to do so... So @Neotko, thanks for sharing your thoughts, thanks for being a long-time mod, thanks for all the knowledge you shared and hope to keep you here as a very well experienced user :-)

Well all steppers do the error so I preferred to use it on all. I didn't noticed any change on Z level or extruder power so it's all ok. At least for now Great info - but this is olny relevant if a A4988 / DRV8825 stepper driver is in place, isn't? Or aalso for TMC2100 / TMC2130 / ...

Damn, this is from my point of view the most interesting feature... @nallath, @ghostkeeper, any idea if it will come at 3.0 final?

... also the new postprocessor for "Correction of hole sizes, cylinder diameters and curves" sounds really interesting - will give it a try later on...

Thanks!! Is there any plan to make also the postprocessors migrateable?

@nallath, short, but hopefully not too stupid questions: - Where to put my custom machine definition & extruder json files so that they will be automatically ported? - Same question for the postprocessor scripts... (up to now I ported them manually by copy/paste...) Cheers Chris :-)

Huuu... If you have a chance, change them to e.g. SilentStepSticks aka SSS aka TMC2100 or TMC2130. There are a great tutorials for the mod available here (did it on my UMO and i´t damn silent now) https://ultimaker.com/en/community/11571-step-by-step-installation-of-silentstepstick-drivers-on-umo https://ultimaker.com/en/community/17498-new-sss-driver-tmc2130 But maybe this tuts can assist in placing your drivers too...

Whow... sehr schön... ahh.. beautifull... well done!