Jump to content

GregValiant

Expert
  • Posts

    4,913
  • Joined

  • Last visited

  • Days Won

    188

Everything posted by GregValiant

  1. You don't need a post processor for that. You could hand code a short gcode script and print it. M140 S60 G4 S7200 ; "S" is in seconds so that would be a 2 hr dwell M140 S0 If your mainboard has an output for a second fan you could get fancy and spend more money on another 24v fan and add a M106 S255 P1 line in there. The bed and fan would turn on, wait for however long, and then shut off.
  2. I refuse to rise to the bait. Those moves are on the order of 0.08mm. There are longer ones as seen in the preview, but those short ones stick out like a sore thumb (sort of like your image there).
  3. The "Flow Rate" is what is entered into the setting boxes of the material section in Cura. It is not cumulative but rather an over-ride. If you have the default flow of a material set to 98% and you enter 100% into the Material Settings flow boxes, the flow will be 100%. If you right click on a setting box in the material settings you can select "Use value from Material". You have to look closely. If a setting has been over-ridden then the font of the setting changes to "regular". If the setting is still linked to (in this case) the material then the font of the setting will be "italic" and the "circle arrow" should be there. If you install AHoeben's "Material Settings" plugin from the Marketplace you can add additional settings in "Manage Material / Print Settings". "...no special setting for shrinkage of annealed parts..." So, how are you annealing the prints? I ask because this has come up before and I've written a post-processor to do a timed cool-down of the bed and/or build volume. It will even move the print head out of the way so you can put a cover over the print (deluxe!). I haven't posted it so it's just sitting here. If you think it is something you could use I'll post it.
  4. Alright, I do see a problem with the script. If the user does NOT enable "Accel Control" in Cura, then a user can enter numbers in the script that could increase the accel limit without a corresponding M204 line in the gcode setting the Accel. I'll add a block to keep the script from running if Accel Control is not enabled. I hadn't thought of that. With "Accel Control Enabled" then any changes to the XY Accel Limits in M201 that increase the Accel numbers are over-ridden by the M204 lines that Cura inserts. That will insure that Accel can only be lowered. There is no such thing as "Fool Proof". If a user wants to do something foolish, they are going to figure out how to do it. See pull request #18235
  5. At the end of the very first infill line (gcode line 5257), there is this little dance... G1 F4500 X113.839 Y105.925 E653.28732 >>> long extrusion G1 X113.799 Y105.855 E653.28866 G1 X113.839 Y105.925 E653.29 G1 X113.799 Y105.855 E653.29135 G1 X113.839 Y105.925 E653.29269 G1 X113.799 Y105.855 E653.29403 It's shuffling back and forth between two points and extruding every time. That really doesn't look right. It almost looks like it gets stuck in "Infill Wipe" before moving on. The same sort of thing happens at line 5318. It's a stutter-step. G1 F4500 X86.16 Y84.516 E658.30881 G1 X113.84 Y84.516 E658.76913 G1 X111.802 Y84.516 E658.80302 G1 X111.803 Y84.516 G1 X113.84 Y84.516 E658.8369 G1 X111.803 Y84.516 E658.87077 G1 X113.84 Y84.516 E658.90465 G1 X113.751 Y84.516 E658.90613 Some of the movements are very short. Almost as if it's a Maximum Resolution thing. Since it occurs in the infill, I don't know if that applies.
  6. The white marks indicate the Z-seam. You can turn them off in the Line Type dropdown when you are in Preview mode.
  7. This is one of your images. One problem is that you are under-extruding by 15% or more. The extrusions have gaps between them. Two other things affect that "gap around holes" problem. One is filament shrinkage and the other is printing "Outer walls first". Both of those reasons are made worse by under-extrusion. You can see that in some of the holes the :outer wall" filament isn't staying where it was put. It isn't sticking and instead is following the nozzle in a straight line rather than making the inside diameter of the hole. The first thing to do is to fix the under-extrusion. You might have to "calibrate the E-steps" of the printer, or increase the flow settings in Cura. In the "Wall" setting section of Cura is "Wall Order". You will probably want that set to "Inside to Outside".
  8. It was in 5.4 or 5.5 that a lot of materials disappeared for the Creality printers. Even regular PLA and PETG were excluded. I don't know who thought that was a good idea, but it didn't work out at all.
  9. Within your base printer definition file is a section called "exclude materials". You can open it in a text editor and delete the lines of the materials you don't want excluded. You might have to open and save the file in Administrator Mode. Go to "C:\Program Files\UltiMaker Cura 5.6.0\share\cura\resources\definitions" and open "Creality_base.def.json". The lines look like this: "exclude materials": ..... "generic_pva", "generic_tough_pla", "imade3d_petg_green", Be careful with the punctuation. Each line must end with a comma. The last line in a section must be without a comma.
  10. Functionally there is no difference between changing the E-steps and adjusting the Flow %. The end result is the same in both methods. 100% of 140 steps = 1mm of filament 144% of 97 steps = 1mm of filament I understand your desire to "do it right". As far as workarounds go, adjusting the flow isn't too bad at all. Getting good prints is what it's all about and if a flow adjustment allows you to do that, then it's all good.
  11. All those settings in Cura (steps/mm, Max Speeds, Accel, etc.) are only for reference and isn't actually used anywhere. Cura isn't capable of asking the printer what the actual settings are and then parsing/showing the response. It looks to me like re-compiling the X3G writer is the only thing you can do (and even then you have to cross your fingers and hope it works). It's odd (and unfortunate) that the "M92" line didn't work. Did you try the "M221 S140" line in your startup gcode? If the printer understands it then that would allow you to leave the Cura settings at 100%. Setting the "global flow" that way would be a little neater.
  12. A little more light reading HERE. Ghostkeeper did leave some how-to instructions. The plugin needs to have the lines altered for the E-steps and then it has to be re-compiled in "CMake".
  13. It's a post-processor. That means it works on the gcode after the model has been sliced and the Cura Engine is finished. All it does is adjust the acceleration of the Y (and/or X) downwards for tall prints. Your comments about "overheating" and "high forces" don't make any sense to me. Everything that post processor does can be done by the user to start a print. The post simply allows a user to lower the accel so that violent starts and stops of the Y table don't cause the printer to throw a tall, top heavy print on the floor. Ultimaker users are blocked as we know they aren't bed-slingers so the script would have no value to them. For other fixed bed printers although it won't help, it can't hurt.
  14. The "Wall Ordering" setting is in the Wall section. You can try "outside to inside". There seems to be a couple of problems. Have you tried using an adhesion promoter? Is the bed nice and clean and wiped down with Isopropyl Alcohol? If you increase the "Initial Layer Flow" by 5% you will get more squish. Enabling Z-hops can either fix the problem, or make it worse (if "not sticking" is the issue). What is your Initial Layer Print Speed? A slow first layer would seem to be a good idea. There are a lot of hearts with tips missing. Something might be going on with the retraction settings.
  15. So much for my idea. That M92 line was always in the StartUp and you just changed the E value? 140/100 is 140%. If you were to set all the "Material Flow" settings in Cura to 140% it would have the same effect as altering the E-steps by the same amount. Clumsy for sure, but it's a possible workaround. It may also be possible to get the same effect by using M221 if your printer will understand it. If you were to slice that cube and then go into the gcode and add M221 lines every 10 layers or so, you could start at M221 S130 and work your way up (or down) and every 10 layers the Flow Rate would change. It would be a way to dial it in IF (a big if) it works.
  16. You might be able to adjust the E-steps by adding a line to your startup gcode in Cura. The RepRap wiki has question marks in regards to Makerbot firmware so this might not work on the Replicator. It's worth a shot though. M92 E140 for a single extruder M92 E140:140 for a dual extruder If it works for one print then you might be able to make it the default by using: M92 E140 ; set the E-steps M500 ; Save the setting in the printer If that works then you can remove the lines from your startup.
  17. It's a post-processor so you'd have to add it from the list. That's what it does though. If you stick this into the "scripts" folder in your "Configuration Folder" it will be available with the other post-processing scripts. (and yes, it will be in 5.7) LimitXYAccelJerk.zip If you have any problems or suggestions regarding it, now would be a good time to let me know.
  18. The Anycubic site has a section HERE and it looks like they have a "how to" download for Cura profiles and setting up the printer in Cura. If you are just practicing before the printer shows up you can install the Kobra Max. It's probably pretty close. When your printer shows up then you can use those Anycubic downloads.
  19. This is the first line in that Gcode file: ;FLAVOR:UltiGCode Which I believe is UltiMaker specific. This is from your printer definition file: "machine_gcode_flavor": { "default_value": "RepRap (Marlin/Sprinter)" } that indicates you have the wrong Gcode flavor in the Machine Settings. Unless you are absolutely positive that your machine is running Ultigcode you should change the setting to "Marlin". There is a Cura bug that affects some dual extruder printers if the Tool Numbers are called out in the StartUp gcode. You can try simplifying your startup and just allow Cura to handle the heating of the extruders and the bed. I believe the bug has been addressed and should be fixed in 5.7. If you use this as the StartUp Gcode it will eliminate the {initial_extruder_nr} which has the bug (it's always "0" regardless of which extruder starts a print): ;---StartUp Gcode G21 ;metric values G90 ;absolute positioning M220 S100 ;reset the feed rate to 100% M221 S100 ; reset the flow rate to 100% M107 ;start with the fan off G28 ; Auto-Home all axes G1 Z2.0 F400 ;move the platform down 2mm M117 BIBO printing... ;---End of StartUp If you use that then the start of a gcode file will look like this (using Marlin as the gcode flavor): T0 M140 S60 M105 M190 S60 M104 S200 M104 T1 S175 M105 M109 S200 M105 M109 T1 S175 M82 ;absolute extrusion mode ;---StartUp Gcode G21 ;metric values G90 ;absolute positioning M220 S100 ;reset the feed rate to 100% M221 S100 ; reset the flow rate to 100% M107 ;start with the fan off G28 ; Auto-Home all axes G1 Z2.0 F400 ;move the platform down 2mm G92 E0 M117 BIBO printing... ;---End of StartUp G92 E0 G1 F1500 E-6.5 ;LAYER_COUNT:158 ;LAYER:0
  20. You can alternate G4 "dwell" and M300 "beep" in the gcode and get several beeps before a pause. Personally I'd find it pretty annoying. The "S" parameter of a G4 command is in seconds. The "P" parameter of the M300 beep command is in milliseconds. G4 S60 M300 P1000 G4 S60 M300 P1000 etc. That would beep for 1 second every minute. Those lines would cause the actual pause to move back by 2 minutes. There isn't any way out of a G4 so if you happened to be standing right there you would have to wait for the entire string of beeps to end before the pause actually occurred. "Annoying" might not be strong enough of a word.
  21. In Marlin M84 and M18 are the same. I used M84 in the script. When the pause happens, the printer locks up. That's true if you use "M0" which is "unconditional stop". You can't do a loop to keep beeping because the printer will not accept any commands when it is in that state. "M25" is "pause SD print". That works on some firmware but not on others. If it does work, it usually calls a subroutine in the firmware and you are stuck with that. You might be able to send commands when it is paused. Probably firmware specific again. Gcode is linear so you can't do a "loop until". You need a separate device or a piece of software running that is monitoring the USB port. You could use M118 to start a routine in the computer. I use an M118 to inform my print server that the print has finished so it can unlock the movement controls. I have an Ender 3 Pro about 4 years old running Marlin 1.1.8. Default "Stepper disarm time" is 2 minutes and the printer will accept up to 4 hours (M84 or M18 S14400). If the steppers disarm during a print you are generally in trouble. It's possible to home the XY then move the print head to an opening on the build plate and then home the Z. The problem is that the endstop switches (in my experience) aren't very repeatable. The Z being off might mean a slightly under or over extruded layer. If the XY are off it means a layer shift of up to 1/2mm. It's noticeable for sure. This has a pause to insert 4 nuts, 6 pauses for color changes, and a final pause to insert a 3/16" x 9" steel rod to try to control warpage in the Florida sun (that seems to have worked). There are a left and a right, 8 hours each, and I had to stay home and babysit all day for each one. (the stars are glued into pockets).
  22. That's an easy one to check. It would have to be awfully loose, and then it didn't happen again. The chances of it skipping that many teeth and then not doing it again are pretty low. Did the power happen to go out? Even a quick glitch could cause a stepper to lose position and then it just restarted where it thought it was.
  23. Search the gcode for ";MESH:". There are two types: ;MESH:NONMESH are combing moves at the end of a layer and ;MESH:My Model.stl Will indicate the model. The first occurrence of this will be at the end of a skirt/brim or at the end of any Support or Support-Interface. If there is no support or interface on a layer then the line will appear just after the layer line and ";TYPE:" line. ;TIME_ELAPSED:135.897187 ;LAYER:4 ;TYPE:WALL-INNER ;MESH:My Model.stl G1 F2703.4 X114.281 Y30.008 E510.47956 Your snippet is too short. At that point it's printing "skirt" which is not part of the model.
  24. I'm sure that isn't the way it was in the gcode. It looks more like something got stuck (bed wiring, bowden tube), or the bed hit something. Was the brim still affixed to the bed?
  25. 5.6.0 can be a lot slower and I have no idea why. There are supposed to be improvements in 5.7. There was a bug report on Github regarding a largish model that wouldn't slice. I checked it and there were no errors in the model. I set Cura to slice it. After a few minutes I walked away to do something else, and I forgot about the computer. The next day I was away from home. When I finally got back to Cura, slicing had completed. I checked the log file and slicing took 38 HOURS. (The "print time" was 18 hrs.)
×
×
  • Create New...