Jump to content
Ultimaker Community of 3D Printing Experts


  • Content Count

  • Joined

  • Last visited

Everything posted by 24c

  1. I do something similar with my start code, but my bed temperature heat up takes the longest time, start the head heating at the same time too, but I don't M190 until after all the levelling, and then park & wait at a wait point. I also use the Cura standby temperature setting to partially heat up the nozzle, before going to the higher print temperature at the wait point, as too much heat here can damage the LokBuild on probing with my printhead nozzle. Cuts my preheat time and start to print time down too, so win win for me. ?
  2. Thanks for the reply, do you see any mileage in having a GCode post processing settings variable tied to a printer definition or variant? I'm thinking that you could show or disable certain post processing scripts, or call plug ins as required to suit a printer.
  3. Hi, Is it possible to define a post processing script in a printer definition. I have a head that needs to have the gcode post processed, and I'm wondering if this could be automated elsewhere rather than be chosen in the Post Processing Scripts dialog/menu bar.
  4. @ghostkeeper totally agree about the summary box I drew, but I sort of did think along the S3D lines when I initially posted, and then realised it was duplicating what the script types summary above was doing, especially if you added all the other options not just search and replace. The "relatable name" was the afterthought, and would be more useful if you are using the same script several times, so you could keep track of things. Maybe that white box summary area should be retitled, conditional post processing scripts Thanks for the update, as everything in Cura 3.2 is slicing a
  5. @ahoeben is this the pull request? https://github.com/Ultimaker/Cura/pull/3229 If so, is it possible further down the line, assuming these are saved and applied on a per printer preference, which seems sensible to me, that there might be plans to view these in some sort of dialog box? Possibly like this? or maybe thinking afterwards each instance of say "Search and Replace" could be given a more useful name in this example below... @ghostkeeper a bit like this, so the user could track the scripts easier. Just an idea.
  6. Very good @ahoeben and @ghostkeeper that's one less thing to do... potentially. Thanks for the feedback.
  7. @AbeFM This is what the Simplify3D interface is like, and you can cut & paste as well as save.
  8. Ok, this is working OK, in that the Cura Gcode is being moulded into pseudo gcode the firmware in the printer can accept. Another specific question... finding how Cura would handle the Simplify {IF TOOL0REPLACE "x" 'with_value y"} in its post processing routine, as I need to swap extruder E values for something else only while a certain tool is selected. I could do it with an external Python script, not me personally, as this is beyond me at the moment, but I'd like to keep it all together in one place if I could. Any pointers or areas to look at to improve my knowledge please?
  9. I have to agree, and I wasn't expecting this at all, as Simplify3D saves them in its FFF file, and that is linked to the profile so to speak. Oh well, worst case I suppose I can phone a friend and collate my search and replace into some generic post processing script, that will manipulate the Cura file output and move it elsewhere. Shame, as I've got Cura working with my QuickFill equipped Robox, and using both nozzles at will in different combinations, and controlling the needle valves at the nozzles too.
  10. Has there been any update on this position? I was slightly surprised that I had to enter my post processing scripts again, when I thought they might be saved with the profile.
  11. My more specific question, I have moved away from using the extruder start & end gcode to open & close** the needle valves, but I'm stumped at the moment on how I might assign a custom initial layer height like you can in Simplify3D for each extruder. G1 X121.821 Y83.637 G1 F1200 E-0.22 G1 B0 M82 ;absolute extrusion mode ; G1 B0 ; close needle valve at extruder end gcode M83 ;relative extrusion mode T1 M82 ;absolute extrusion mode ; T1 ; active extruder start code ; G1 B1 ; open needle valve at extruder start gcode M83 ;relative extrusion mode M109 S205 M104 T0 S190 G0 F3600 X121
  12. @ahoeben & @mattgriffin. I'm sorry for the non-specific stuff, I'm just trying to get my head around this, but thank you both for your directions. I'm not a code bunny, so I expect some more daft questions will happen later. In the past I have compared slicer generated gcode in other slicers and vs the gcode the firmware in these printers accept, so I am just trying to grasp the Cura "syntax" & its generated gcode, and by comparison plus experimenting with settings I should mimic part of what I need. To give you a more specific idea, my Dual Material printer expects to see
  13. Sorry about this question, but I'm struggling to get my head around writing a new set of resources, aka definition, variants, extruders and materials. Well not the last one to be fair. I have a dual extruder printer, and three different head combinations, so I thought you create a definition first, and add some metadata tags, as well as some overrides common to all, then add specific overrides in the variants folder, with all the nozzle variations in the extruder section, but I'm wading in the sticky stuff now. I can get one version to work by just user the Printer custom fdmprint
  14. Not sure whether this has been asked before, but up until today, I hadn't got USB Printing working with my Robox printers since dabbling with later versions of Cura aka 2.4 onwards, so I never noticed this. As I already have a start code with an "Abort Print" end code, and I realise your Pause and Abort Print buttons are called within the USBPrinterOutputDevice.py script, but it would be a pretty useful feature, if these could be customisable ( a bit like Matter Control, Simplify 3D or even Slic3r for example), and that way other print functions could be called from this area too,
  • Create New...