Jump to content

3dprntz

Member
  • Posts

    131
  • Joined

  • Last visited

Everything posted by 3dprntz

  1. How do you have the API alert you of these triggers or that there was a problem with the filament?
  2. GitHub - Ultimaker/UltimakerMarlin: This repo contains the versions of Marlin powering Ultimaker printers. In case of questions please drop us a line: support@ultimaker.com Looks like there are a couple here: G30 - Probe Z at current position and report result. G31 - Get/update capacitive sensor base level M310 - Single cap sensor read Could be one of these I suspect.
  3. The print is being done on the front-center portion of the printer. I think I'll run a test without active bed leveling and have the subsequent prints with lower first layer and see if that helps. Is there no griffin gcode for active bedleveling?
  4. I've had issues trying it out. Usually I wouldn't need to level it, as I've had the same experience in the past. However, the first print has a perfect layer, but the following are too far from the plate. I tried turning off the auto leveling to see if there would be a difference and it gives me the same issue, which points me to the point that the leveling helps the first layer. Thinking about it now, I can double check the full build plate leveling and get that as even as I can. But, I've done that already before. It would still be nice to know the auto-leveling gcode as it would be handy with projects in the future. From what I understand, its usually G29 on other printers, but can't be exact with the UM3.
  5. I've tried looking around and can't find the gcode for the automatic bed leveling. I'm compiling a gcode that would require the printer to level the bed during the print more than once to keep the first layer height consistent.
  6. Hello, I'm working with the UM3 to print some product that we supply to many of our customers. I was editing the gcode to automate the process and have it down very well to the point that I can continuously print them. The only thing I was looking about is to add auto bed leveling to the start of the next iteration. I've read up about G29 being the usual gcode for leveling the bed, but still not sure. I would run it without leveling the bed, but it either has much less of a flow on the first layer, or the first layer isn't as clean as if you were to do one by one. I figured it was the leveling, since when I set the setting for leveling to be once a week, it gave the same results.
  7. Looks good. Guess I was thinking about the Ultimaker 3 mainboard. They would need to be mapped in marlin to work and not sure how it would handle the capacitive sensor. Though modifying the pcb printhead board would work just as well. I wonder if getting a raspberry pi and installing the firmware image would work also to make it as UM3 with the features. I would like to make a larger version of the UM3, but 600 X 600 X 600. Although the Carbon fiber rods may deflect less than the steel rods. Although probably at that point it would be best just to get a mainboard with updated stepper drivers and 32 bit board.
  8. For about $150 for everything, Seems like a good deal. The parts are much cheaper than OEM. You mentioned that you ordered the UM3 printboard before and installed it on a UM2. How much were you able to transfer over and get functional? 3D printer accessories DIY suitable for UM machine upgrade generation special control driver board open source motherboard NO1548 | Taobao Agent Bhiner (www-bhiner-com.translate.goog) Probably if you grabbed this board, you would need to remap most of the pins and find a way to get the capacitive sensor to work.
  9. 3D printer accessories UM DIY suitable nozzle kit NO.9428_AS | Taobao Agent Bhiner (www-bhiner-com.translate.goog) mentions that the heat throat and pcb needs to be programmed to work in this one.
  10. Awesome! This one is the UM3 head board? 3D printer accessories DIY suitable for UM machine upgrade extruder adapter driver circuit board NO.2012 | Taobao Agent Bhiner (www-bhiner-com.translate.goog). I don't know how much you can understand, but the previous one you sent for the UM2.5 is just the board or the whole print head? Guess this one is confusing since it shows the partial head instead of the whole with all the fans. Have you worked through this agent website before?
  11. Could you provide a link? I am having a hard time finding the page. I did find this but it appears that it is off the shelves or not sold anymore. 3D Printer Accessories ul...-Taobao.com
  12. Do you know if they are igor drylin bearings and what are you option on them? Smooth?
  13. I printed them in resin to test the concept. I think I used a temp resistant ABS like resin. The lever was too sticky or had too much friction.
  14. Wouldn't be a bad idea. Has the print head part become cheaper? And does the bed leveling works with the included capacitor?
  15. Is there a 2.85 option? Or I would have to make a UM3 hotend to make that work? I still use 2.85mm filament for all my other printers currently.
  16. This is the original code: # Cura PostProcessingPlugin # Author: Pavel Radzivilovsky # Date: February 12, 2022 ## Description: !!! Use at your own risk !!! ## This plugin creates gcode that can seriously damage your printer. ## Inserts code to push the print out of the printer, and restart the print of a new object. ## Can be used to automate production process of multiple objects. Never use unattended! ## The model must be centered horizontally and placed in the front 2/3 of the build plate. ## Tested with Ultimaker 3. And seriously, use at your own risk, this can break your printer. from ..Script import Script class Bulldozer(Script😞 def __init__(self😞 super().__init__() def getSettingDataString(self😞 return """{ "name": "Bulldozer - Kick the model out of the printer", "key": "Bulldozer", "metadata": {}, "version": 2, "settings": { "delay": { "label": "Cooling delay", "description": "Cooling time before push. Recommended at least 20 minutes", "unit": "min", "type": "int", "default_value": 20 }, "parts": { "label": "Repeat", "description": "Number of builds to perform", "unit": "prints", "type": "int", "default_value": 5 }, "zheight": { "label": "Noozle height", "description": "The height of the noozle when performing the bulldozer", "unit": "mm", "type": "int", "default_value": 5 } } }""" def dozerCode(self, imodel, bedtemp😞 delay = self.getSettingValueByKey("delay") parts = self.getSettingValueByKey("parts") zheight = self.getSettingValueByKey("zheight") code = """ ;Bulldozer code start G0 F2000 Z150 G0 F2000 Y210 Z150 G0 F2000 X105 Y210 Z150\n\n""" for m in range(delay😞 for s in range(6😞 code += "G4 P10000\nM117 Cooling down, " + str(delay-m-1) + ":" + str(5-s) + "0\n" code += """M117 Behold!\n G0 F2000 X105 Y210 Z""" code +=str(zheight) code +=""" G0 F2000 X105 Y5 Z""" code +=str(zheight) code +="""; bulldozer G4 P10000\n\n""" if imodel+1 < parts : code += "M117 Printing model " + str(imodel+1+1) + "/" + str(parts) + "\nM190 S" + str(bedtemp) + "\n\n" # +1 for 1-based numbers for human user, +1 coz starting next model after this one return code def execute(self, data😞 parts = self.getSettingValueByKey("parts") index = 0 RepeatedPart = "" StartCod = 0 StopCod = 0 g280x = 110; initialBedTemperature_C = 0; for active_layer in data: modified_gcode = "" lines = active_layer.split("\n") for line in lines: if line.startswith(";BUILD_PLATE.INITIAL_TEMPERATURE:"😞 initialBedTemperature_C = int(line[-2:]) if line.startswith("G280") and not line.startswith("G280 S1"😞 line = "G0 F15000 X" + str(g280x) + " Y6 Z2\nG280 ;position moved\n" g280x += 15 if line == ";End of Gcode": line = "" for i in range(parts-1😞 line += self.dozerCode(i, initialBedTemperature_C) line += RepeatedPart line += self.dozerCode(parts-1, initialBedTemperature_C) line += ";End of Gcode \n" StopCod=1 if (StartCod==1) and (StopCod==0😞 RepeatedPart += line + "\n" if line == ";END_OF_HEADER": StartCod=1 modified_gcode += line + "\n" data[index] = modified_gcode index += 1 return data
  17. I have a script that I edited and thought it would work for the postprocessing plugin. However, when I check the g-code, it does not appear to have done anything. The older script worked before and I'm not sure if it may be too old for the newer version of Cura. I've pasted the script below: # Cura PostProcessingPlugin # Author: 3DPRNTZ # Date: January 18, 2024 ## Description: !!! Use at your own risk !!! ## This plugin creates gcode that can seriously damage your printer. ## Inserts code to push the print out of the printer, and restart the print of a new object. ## Can be used to automate production process of multiple objects. Never use unattended! ## The model must be centered horizontally and placed in the front 2/3 of the build plate. ## Tested with Ultimaker 3. And seriously, use at your own risk, this can break your printer. from ..Script import Script class Bulldozer(Script😞 def __init__(self😞 super().__init__() def getSettingDataString(self😞 return """{ "name": "Bulldozer - Kick the model out of the printer", "key": "Bulldozer", "metadata": {}, "version": 2, "settings": { "bedtemp": { "label": "Print Bed Removal Temperature", "description": "The Print Bed temperature at which you would like to have the piece removed. Suggested is 45", "unit": "°C", "type": "int", "default_value": 45 }, "parts": { "label": "Repeat", "description": "Number of builds to perform", "unit": "prints", "type": "int", "default_value": 5 }, "zheight": { "label": "Noozle height", "description": "The height of the noozle when performing the bulldozer", "unit": "mm", "type": "int", "default_value": 5 } } }""" def dozerCode(self, imodel😞 temp = self.getSettingValueByKey("bedtemp") parts = self.getSettingValueByKey("parts") zheight = self.getSettingValueByKey("zheight") code = """ ;Bulldozer code start G0 F2000 Z150 G0 F2000 Y210 Z150 G0 F2000 X105 Y210 Z150\n\n""" code += "G4 P10000\nM117 Cooling down\nM190 S" + str(temp) + "\n" #Changed to print bed temp to have the system automatically wait to bed temp rather than minutes M140 s code += """M117 Behold!\n G0 F2000 X105 Y210 Z""" code +=str(zheight) code +=""" G0 F2000 X105 Y5 Z""" code +=str(zheight) code +="""; bulldozer G4 P10000\n\n""" if imodel+1 < parts : code += "M117 Printing model " + str(imodel+1+1) + "/" + str(parts) + "\nM190 S{material_bed_temperature_layer_0}\n\n" # +1 for 1-based numbers for human user, +1 coz starting next model after this one return code def execute(self, data😞 parts = self.getSettingValueByKey("parts") index = 0 RepeatedPart = "" StartCod = 0 StopCod = 0 g280x = 110; # believe this is where the blobs are moved to the front initialBedTemperature_C = 0; for active_layer in data: modified_gcode = "" lines = active_layer.split("\n") for line in lines: if line.startswith(";BUILD_PLATE.INITIAL_TEMPERATURE:"😞 initialBedTemperature_C = int(line[-2:]) # if line.startswith("G280") and not line.startswith("G280 S1"): # believe this is where the blobs are moved to the front # line = "G0 F15000 X" + str(g280x) + " Y6 Z2\nG280 ;position moved\n" # g280x += 15 if line == ";End of Gcode": line = "" for i in range(parts-1😞 line += self.dozerCode(i, initialBedTemperature_C) line += RepeatedPart line += self.dozerCode(parts-1, initialBedTemperature_C) line += ";End of Gcode \n" StopCod=1 if (StartCod==1) and (StopCod==0😞 RepeatedPart += line + "\n" if line == ";END_OF_HEADER": StartCod=1 modified_gcode += line + "\n" data[index] = modified_gcode index += 1 return data
  18. They were some old profiles that I had before that I tuned for quite some time. Had the same 6.5mm retraction at 25mm/s. The other profiles that I tried were I think the standard profiles. Most everything came out really well except for the z seam. Its hard to even see the layer lines on the print.
  19. You should put in localized bed mesh leveling depending on the size of the object as an option
  20. I've notice this on all my prints since Cura 5.4. All my old profiles use to function without really any Z seam. Now for some reason the Z seam is super prevalent with larger gaps. Did the machine settings for UM3 and UM5 all have changes to their profiles that are making them have larger gaps at the Z-seams?
  21. Issues that I am getting with the beta are that the right-side settings toolbar is not showing the names of the individual adjustable settings in dark mode. I tested it yesterday and couldnt see the exact settings that I needed to change like Initial temp and printing temp. In addition, the z-seams for the prints have gotten worse for me and I can't "seem" to get rid of it or know how to get rid of it besides retractions and coasting settings. However, those haven't helped and it's become an issue with machines that didn't have it as an issue before.
×
×
  • Create New...