gearsawe

the M104 and M140 is part end code? So those should be after the "G1 E-1 F300"

Then there are the professional systems like the Statasys. Yes they are closed sources and use proprietary material. But they are true click and print. You don't worry about warp, if the print will fail. It auto-detects the bed, senses when it is out of material and waits for you to insert more then continues. If you have extra material bays it will switch over to the full spool and continue. It senses a print head jam. Actually there was once it did not detect an extrusion jam but it was a quick pretty easy fix. The propriety filament is guaranteed to be accurate and free of variance. Also the dimensional accuracy is dead on. It prints the part in a heated chamber and after it cools and shrinks it is +/- 0.005" I bought a cheap little $350 3D printer fir myself and it has been nothing but a head ache both mechanically and software wise. It was claiming to be open source during time of development but then never did. Fortunately they finally add the ability to print external g-code files which gave us the ability to use pretty much any program to slice. I have had to come up some horrible hack to the g-code to make it so their software does not mess up the files. There are many claims on this printer from the make and I have found only about 20% of them to be true. So this is the two extremes really cheap and really expensive. But if we were to invest in another printer at work I am seriously looking at the UM. Since there is such a big community on this thing who is will to help.

Thanks missed the getValue() will use that. (corrected posting above) As for the settings I am retrieving is a printer settings such as backlash which is specific to this type of printer. I don't necessarily want to see the actual tooling path with backlash in the viewer since it will look like a mess. This will be something that is done at save. But now I am able to pull the set values into the gcode writer which makes me very happy. And will hopefully be useful for those who also own a M3D Micro.

the below should not have any URL formatting. This makes it impossible to post code! Just because there is dot between two letters does not mean it is a URL. from UM.Application import Application it should look like from UM.Application import Application

so to get the value of a setting for a printer config... in the printer config you have a category "MyCategory" and a value "MyValue" in that category from UM.Application import ApplicationMyValue = Application.getInstance().getActiveMachine().getSettingsCategory("MyCategory").getSettingByKey("MyValue").getValue() THe code above is not formatting correctly It keeps putting url tags automatically in the posting. There should be be no urls inside code brackets. GRR But still having that one problem making my own custom GCodeWriter. I have gone a head and reported the bug but still not sure if I am not setting something up right.

The above is actually from the .json file. Along with a bunch of other custom settings for the printer. I actually have a model of the printer with the print volume in the correct position. Displaying correctly. Just took a while to find where everything is stored Till then I might just have to modify the original GCodeWriter and hardcode the code to modify the gcode there. I made my own "GCodeWriterMicro" it actually shows up in the save as options but when saving it still only use the original writer. I think I am doing it right but the new system just is now supporting what I need it to do like you said. It would be great if the settings in the json file could be used by the script when saving. Would make things a whole lot better. I really don't want to see the g-code paths in the viewer since the pathing looks like a mess because of the backlash movement and offset put in place. One thing that did not make sense is in the Plugins my custom GcodeWriterMicro was showing up but I could not turn it off. The check box would always stay on no matter how much I clicked. And then it acts like it is not being used when saving. So there might be a bug there. Not sure. Don't know enough about the new system.

I am still very new to Cura. In 15.04 I made a simple post process plugin which modifies the g-code to work with a specific printer. The plugin has some parameters which could be adjusted and it would modify the gcode at save. This was pretty simple in 15.04. Now in 15.06 I am starting to understand how to add parameters to a printer configuration in the "fixes" catagory but how to pass these values to let sat a new GCodeWriter plugin is where I am completely lost. I tried to make my own "GCodeWrinerM3DMicro" but since it uses the same extension ".gcode" only the original gcode writer seem to be used. I did not want to modify the the Orignal GCodeWrite process and hard code settings into it. But make it optional for those who would like to use the software for more than one type of printer on the same system. I am not a programmer by trade so I learn as I go. Forgive my lack of terminology understanding when it comes to pointers, imports, object, mutli-dimensional arrays and so forth. So in my custom printer config if have a small snippet of code which show a value in to adjust in the fixes category. Maybe I am going about this all wrong. But how to pass these values into a custom gcode writer is where I am clueless. Any guidance would be appreciated. "micro": { "label": "Micro", "visible": true, "icon": "category_fixes", "settings": { "micro_prefs": { "label": "Use Micro Prefs", "description": "Use Micro preferences", "type": "boolean", "default": false, "visible": false }, "chop_len": { "label": "Max Line Dist", "description": "Longest a line can be before is it chopped.", "unit": "mm", "type": "float", "default": 2.5, "visible": false, "active_if": { "setting": "micro_prefs", "value": true } } } }