Jump to content
Ultimaker Community of 3D Printing Experts

Kin

Member
  • Content Count

    36
  • Joined

  • Last visited

Everything posted by Kin

  1. from ..Script import Script import re class share_Wipe(Script): version = "3.2" def __init__(self): super().__init__() def getSettingDataString(self): return """{ "name":"share Wipe """ + self.version + """", "key":"share_Wipe", "metadata": {}, "version": 2, "settings": { "machine_type": { "label": "Machine Type", "description": "Select which machine type you are using. CRITICAL!", "type": "enum",
  2. That sounds like a cold plug, one of the situations where I might actually recommend the high temp warmup hold. The difference is I'd go to the material print temp, wait 3 minutes, then physically hold back the heatsink cooling fan for the hot end for 1-2 minutes before pulling. This causes filament to soften above the heatbreak [because the heatsink isn't cooled anymore and warms up], and can loosen a cold plug. It's a risky move but would probably be next step. Alternatively if you've managed to get support through other channels and methods, there's no guarantee my suspicion is correct so
  3. Hi gilbert, I agree cura doesn't really place objects very well (coming from slic3r background.) I don't know exactly the functionality you saw before, i can't remember if cura would just intelligently place objects after a row fills up into a new row. It seems if it did this after each duplication to check if it needed to change rows, it might be confused when you're making 9 duplicates in a row (that is the implementation of "multiply objects" could be barebones.) But two suggestions for your immediate problem: (1) Try multiplying 5 units, then 5 units again. My point here is ask for the
  4. So OK I would like to distill this to two questions: (1) In JSONs, can I access the material temperature settings? It seems like I cannot, I can only access a global default print_material_settings (1B) If I can access material temperature settings in the machine instance, can I also access it in the extruder specific json? (1C) If I add a temperature command to my extruder start gcode, does cura see that and turn off its M109 print temperature command? I understand it might not be enabled for the extruders but I can't figure out how to confirm, it seems my tests so far suggest it is not fu
  5. You should not need to get it hot over 15 minutes and you are likely to just degrade any plastic further. The typical procedure (please correct me anyone if I'm wrong) is more like what Labern said, to heat it up so you can fuse the filament with filament in the hot end, then pull when it's somewhere between cold and hot, such that you can pull out viscous material attached to the filament you just fused into the melt chamber. This is repeated a few times. Sometimes I find it useful to insert a 0.35mm steel cable into the nozzle end to break things up, feeling it 1mm in at a time, but I have
  6. For the record I am absolutely aware there is no way to "merge" the two programs. I hope i didn't distress anyone by throwing around words like that with more specific meaning than I intended . [Distressed insofar as someone feels distressed when they hear someone talking about things so far off-base] I absolutely only meant it in the sense of a dream world concept in which all the things I like about slic3r existed in cura, and cura handled the random nifty super-tweakable settings of slic3r. I also meant it in the sense that I conceptually admire slic3r (it was my first quality slicing e
  7. I am glad to have encouraged some movement on this post, but I admit I'm out of my comfort zone for debugging this. It does look like you found a genuine issue with 2.4 install on linux, but I don't know exactly what you've found. For the record i run in windows and expect the scripts in program files>cura>plugins>postprocessingplugins>scripts, which is totally different. Hopefully someone with more knowledge (looks like already one other person has responded) will have a better sense of whether or not this should be pushed to a github issue. Although what you've found so far
  8. edited this post because I think I'm shooting too far from hip, I will try to look into pause@height but also suggest trying a couple other gcodes/files, and also a different height (not 5.0 try 5.02 or something randomly different.) just trying to troubleshoot.
  9. Hi Martin, I checked over the pause@height and I couldn't find any major issues why it would fail for your parameters and gcode. It should be starting to look at your lines after LAYER:0, and the it should find the first Z that is above the z target, so it finds Z5.07 around layer 49, and it should then insert the pause script (m83 + anything you modify the plugin with, but I think you indicate you haven't odified it.) Have you tried any of the other default scripts? Maybe the tweak@Z or something? One suggestion: can you try pausing it at a height other than 5.0mm? maybe it's an odd bug
  10. Hey sorry about it I see you're having a lot of trouble. I run a shared UM3 a little and a prusa along with my repraps. Sometimes every printer goes through the worst shit. I didn't really read the whole thread and notice you agreed brim might make sense in some cases. Hope the rest of your problems resolve. FYI in future I think heating the t-glase above 200C should be plenty to remove it from a clog. I would probably heat the end up and manually pull back, but it sounds like you've tried a few similar things like that and your issue might be more complicated than I can diagnose f
  11. I've heard but not seen that stratasys software can do something like this (their high end suite.) I don't see a lot of value over "infill thickness" (e.g, .1mm perimeters with .3mm infill.) But it is something neat enough that it would be cool if cura matched. Sometimes I wish slic3r and cura were one software package, they both have a ton of strengths and end up doing a lot of redundant work. besides the general reasons for why they are not one project, I also have no conception of why they probably physically can't be merged [presumably they have different architectures and code bases.]
  12. I suggest uploading your gcode as well, your copy of pause at height, and also let know (and confirm) what you put the pause layer height at. I suspect it's just that you are attempting to pause above a layer that the gcode gets to, as a typo or something.
  13. You seem bizarrely indignant that cura defaults to brim. Meanwhile I'll present why I think this is correct: If the part warps off the bed, the user blames the printer. Even if only 1/20 prints *need* a brim, I think keeping it simple for basic users is what cura default settings should do, so then the brim should stay on.
  14. The behavior I'm trying to do is fairly basic: Standard cura warmup for dual extrusion heats both heaters up simultaneously with a M104 command. I want to heat up one heater, then the next, ideally adding to my machine_start_gcode json something like this: M109 T1 S{material_print_temperature_1} M109 T0 S{material_print_temperature_0} My first adventure was learning by trial and error that I can't modify the machine_start_gcode in the "extruder" json because it doesn't parse for things like S{material_print_temperature}. I am not entirely sure what settings it does parse for and which it
  15. Update: So this totally went wayside during the holiday madness . I am glad to have finally sat down on it. Dahai8 you uncovered the secret. I've include below the example code you gave extended to a more complicated number of parameters. I still have had a bear with opening cura to test edits to the script, but mostly it's just me not being a cautious practiced programmer and missing punctuation. I probably rely too much on (for example) the compiler in arduino to point out such issues. I don't get so lucky with the gcode modifier script because I never see how it fails in cura (just that it
  16. I'm at work right now, but I will process this tonight after work and go through the response. Thank you!! Edit: Update, gah! Wasn't able to work on it today after work (long day) but hope to tomorrow.
  17. Hi DaHai! I agree, I think per my fledgling understanding so far, the double quotes would be necessary. However, when I add them, the script that partially works doesn't load, even if that is the only change. I have the script attached and I just reran the tests. I'm sending the double quote version, which you will see can't load, and then if you take out the \"\" then it loads, but doesn't process the if statement looking for the "A". https://dl.dropboxusercontent.com/u/3619097/Robust_Wipe.py I don't really know what fails when I add the quotes, just that it fails. Right now although I
  18. Never made it further with this. Unfortunately I think I'm stuck hard coding things into the script and then adding override settings. I wish I understood JSON a little better or had a better sense of how to debug the scripts given the issue of no error reporting. It's been a bit of a frustrating struggle. Overall still cool to have the postprocessing plugin so not to air my frustrations as an overall negative review. It's great .
  19. Interestingly, I got somewhere with "value": "6 if machine_type == A" But it is kind of faulty. That is, at least the script loads, but the box is red and unhappy. It does let you enter numbers though, but it doesn't preload 6.
  20. Hi Nallath! I really appreciate the answer and help. I think you've got me further, and I see now the mistakes you pointed out. One thing I was not totally certain was what you meant by "default_value must be a part of a setting." I am not sure if you are saying "default_value must be used, even if you have a "value"" or something else. I paired down my normal script into just the JSON header, for debugging purposes. I have added your line "value": "6 if machine_type == \"A\" else 3 if machine_type == \"B\" else 9" to a previously working JSON header (for e.g, with just 9 instead)
  21. I am going to checkout tomorrow the codeacademy on JSON, https://www.codecademy.com/courses/javascript-beginner-en-xTAfX/0/1, I'm hoping it gets my somewhere.
  22. Hello! (1) I have been having some fun with the postprocessingplugin. It's really great! My biggest challenge has been that it is *hard* to troubleshoot the scripts, because the actual file is only run by cura, and so when the script completely fails, I only see that it won't load in Cura. And for some reason Cura takes ~25 seconds to open every time I open it, so that testing has quite some cycle time. I may be approaching it in a clunky way, I'm not sure (inexperienced here.) (2) Specifically, right now I am trying to work out how to include if statements in the JSON header, to try and ma
  23. Just wondering if there's any way to keep track of what/any progress might be happening on this. Possibly should I post a new topic elsewhere advocating for this? Does anyone know if it would be a relatively easy thing to implement or what the method for implementing it might be? Thanks!
  24. In principle I believe the distance should not affect things. Have you tried reducing the speed and (perhaps more importantly) the acceleration at which you retract? However, because 6.5mm shouldn't be impossible, I wonder if the tension isn't set well for the material.
×
×
  • Create New...