Jump to content

ksihota

Member
  • Posts

    23
  • Joined

  • Last visited

Everything posted by ksihota

  1. You are right on @GregValiant The minimum layer time is set to 10 secs. By decreasing the time the expected speeds can be seen in the Colour Scheme Dialog
  2. I don't use the Colour Scheme dialog much so I am not sure how the colour setup works when you combine choices. It might do some kind of averaging calculation when they overlap or something else? If I use it I generally look at individual items at a time. If you select each item individually you will see that the scale changes so I don't think using them together is a good idea as the scale may not be what you think it is. You would have to ask someone who actually uses this for the real information. Mine is all speculation. Looking at it more carefully it looks like the speeds don't match the colour legend anyways. The legend shows 60 to be orange but the walls appear to be printing at 45. Maybe this is a bug or its just how I am interpreting the information. I did a quick check but didn't see anything on Git Hub. You might want to look into this further if it is something you use?
  3. Since I don't have a Creality Ender 3-S1 Printer The printer was created when I opened as a project. I also made sure that the nozzle settings were created new (since I already had a 0.6 nozzle defined) The result was the same with the speed settings displayed as in the last post. I am also running 5.3.0 Did you unselect the Travel moves in your colour dialog?
  4. I opened it as a project and this is what I get. What version of Cura are you running?
  5. Do you have some other setting that would not allow your walls to reach speed? This is a small model on my printer showing speeds. I don't seem to have that issue. Sometimes I start fresh with default settings and just change what I know works. If you are piggybacking your slicing on old setups there may be settings that are causing issues that you would have to go back through one by one to find.
  6. You can adjust your settings so the first layers are different than the rest. Often I will make sure my first layer has lower acceleration and jerk settings than the others to ensure that the first layer goes down nicely. The first layer can also be problematic if your filament is not sticking well to the bed nicely, so slowing it down gives you a better foundation for the rest where you can then speed things up.
  7. That shouldn't have made any difference to the show configuration folder though, or was that only happening when the USB adapter was inserted in the USB of the computer?
  8. Happy Birthday🎂 You might also want to test out the jerk settings. I set some of the small items and sharp corners down to 5 or lower. those parts of the print slow down quite a bit but if its only on the first layer and you get better adhesion for those small pieces its worth it. Printing PETG on glass is sometimes really difficult to get the filament to stick to the bed rather than the nozzle. I took a look at those tungsten carbide nozzles. Their printing characteristics (conductivity and hardness) look really good. I also noted that some have low friction coatings that make it more difficult for filament to stick to it. I can't afford parts like that so I just use hardened steel for abrasive materials.
  9. I would try and figure out where the issue is actually happening in the first layer. On my prints with PETG it was when the nozzle quickly moved from point A to point B or tight corners. Because of that I was able to use the acceleration and jerk settings to slow those particular movements way down. I could adjust these specifically for the first layer as it wasn't a problem later on. It meant parts of my first layer was slower but the rest of the print could proceed as usual. If you are printing PLA, have you tried increasing the 'squish' of your first layer just a little bit more to ensure that the adhesion was good on the first layer so the filament would not lift at all? That was not possible with PETG. I might also try increasing the first layer a little more just as a test. Maybe up to 0.3?
  10. Does it appear to be a print speed issue where the filament is being pulled away from the bed before it has a chance to stick properly? Is it only on your first layer? When I have had small objects (usually with PETG) that get stuck to the nozzle and pull off the bed, I usually set my first layer jerk to a very low setting and decrease my acceleration settings for the same. This usually allows those beads of filament to bond to the bed enough that the nozzle movement does not pull them free. I only need this for the first layer as after that the filament sticks to itself and can therefore run faster.
  11. LOL I don't have printer settings in my side menu. Guess I should add that. This is the setting that sometimes gets overlooked. Not sure if it is critical but I am pretty sure I have had under extrusion issues when I forgot to change it.
  12. Thanks Cuq. I just changed the name of my existing predator.def.json file and it now displays the proper mesh. it still references the original extruder and cfg files so i am going to run this for a while to see if it works and I don't get any other errors. I'm pretty sure I put everything back to stock. I'll probably have to wait for the next upgrade to be positive it solves all the issues but it appears to be fixed for now. The funny thing is that I thought I had already done this but when I added a new printer I got a configuration error. I guess I must have made some other change at the same time as now, when I add a new printer, it works fine. Thanks for the help.
  13. Have you checked the humidity of your filament lately. A little moisture might be causing some flow inconsistencies. How about the shape your nozzle is in? Just grasping at straws here. From the photos it appears to be those edge pieces. Do you have coasting turned on or another feature that might decrease flow as it reached the end of a path or corner so that there is a limited flow as it begins a new path?
  14. Thanks for the info Cuq The predator.def.json file in my local user definition folder is the original file with my original file name. The Cura created file in the Cura install folder is the file that was submitted and has some different information including a different mesh name. Assuming that Cura is reading my local predator.def.json file, I am not clear why it is no longer using my custom mesh and texture files. They are stored in my local config folder in the meshes and images folders. Just to test if my local predator.def.json file mesh is being used I copied a version of my obj file into the Cura install meshes folder and started Cura again. It appears to still only use the mesh file named in the Cura installation predator.def.json file and not the one listed in my local config folder. I then changed the mesh name in the Cura installation predator.def.json file to match my mesh name and it works as expected. Unless I am missing something this would indicate to me that, the mesh can be stored in either the Cura meshes folder or my local meshes folder but Cura will ignore the mesh defined in my local predator.def.json file and only uses the name specified in the Cura install predator.def.json If this is the case, I can't see how I can over-ride the defined mesh file using my local predator.def.json file Unless someone can clarify this for me I guess my only option is to clear out my installation and rebuild everything from scratch or just keep changing the install definition file every time I upgrade.
  15. Thanky you. I have just installed the plugin. I agree with Cuq that some of these plugins should be enabled by default.
  16. Ensure that you have changed the extruder size in the Machine Settings and not just the line width etc. in the profile settings. I believe that is the suggestion in Cuq's response above but often people overlook this in their haste to get printing again. When you switch to a larger nozzle you may need to up your temps a bit to take into account the extra flow from your hot end (more material needs more heat to melt.) It does appear that you may be under extruding a bit.
  17. This may have nothing to do with your issue but if you are on Win you might give it a try just in case. I have noticed since Win10 that whenever I begin to see strange issues in different programs, it has always been a Windows update that needs to be completed. Before I waste my time on trouble shooting an issue anymore I always check for windows updates and ensure that the latest is installed and that I have restarted the computer at least once. Often the updates says there are no new updates but after restarting and checking again there are indeed updates that need to be completed.
  18. A few years ago before I got my first AnyCubic Predator I decided to try my hand at building a printer definition setup for use in Cura since one did not yet exist. I put it together and tested it out once I got my printer. When I knew it was working I posted the files and the instructions on how set it up inside the Cura configuration folder (it is on Thingiverse) since I was not yet prepared to submit it to Cura for inclusion in the stock download. It worked fine and upgraded properly with new versions of Cura. At one point another user asked if they could submit it to Cura and I agreed. They submitted it, but had to change the mesh obj file to a stl because my original obj file was too large. Although this did change the display slightly (no image template) it was not an issue since whenever Cura upgraded it would first read the resources printer.def.json file but after a restart or the user configuration file was touched Cura would then read the local printer.def.json file (user configuration folder) where my original obj file and png template files were referenced and they would then display properly. At one point in the upgrades (around V4) Cura set some kind of file size limit on the mesh size so mine would no longer work. At that point I rebuilt my obj mesh and shrunk the size considerably (well within limits) and my mesh displayed properly again. The latest issue I have been having, which may have started with v5 of Cura, is that the printer.def.json file in the Cura resources folder appears to be the only one that is being read. I have tried restarting Cura and changing settings in Cura in order to force the program to see my local printer.def.json file but nothing seems to work. The only way I have been able to get my mesh to work properly is to edit the Cura version of the printer.def.json file and specify the mesh obj fle instead of the current mesh stl file. At that point Cura will then look in my local configuration meshes folder and use the proper file. So obviously Cura is still reading the local configuration folder since it is able to read the local mesh obj file but it does not appear to be reading the local printer.def.json file that included the proper mesh file reference to begin with. Was there some change in Cura 5 that I need to account for, to ensure that Cura will read the local printer.def.json file, so I do not need to manually change the Cura file each time I upgrade Cura? Is there anything else I have overlooked that might be causing this issue? Thanks for any assistance anyone can provide.
  19. Get your configurations files by selecting help and open the configuration folder from the menu. You should be able to copy the most recent version folder and then when Cura upgrades to a new version it will use the previous versions data. Here is a view of my old versions: You might also be able to just replace the latest versions with an older one but I would run a test or two to ensure it works before relying on that. If you have another computer you can always test this out by installing Cura on it and then copying and pasting the old version folder in place of the new version. With each version change there are changes which may cause issues. If it does not work you can always try putting the old Cura config folder in place before upgrading to see if the new Cura update will create the new configuration from your old version. I would first install the version you are currently running and copy the existing configuration folder over to the new machine. Check if it works. If it does install the new version and see if Cura upgrades the system properly by creating a new folder bringing forward all the old data. The Cura program files etc. are totally independent of your configuration files, so if there is a problem it will be with the configuraton folder and files. If all else fails with this easy method, I believe there are export and import tools you can use. I have never had to resort to those so I am not familiar with them.
  20. Yes, that can be a problematic dialog. I know that some users don't even think about it and just select OK and have the stuff deleted. I did that myself the first time but now I just close the dialog and begin to search for the problem. Often it is due to a recent change that was made (manually editing files) and by reverting the change the error goes away. A more prominent Cancel button may help for some here but the rather limited return information does not help people who are not aware of what they might have done to cause the issue. It would be nice if other information was given such as the file name where the conflict arose etc. but that may not be possible.
  21. I have this issue as well with PETG. When printing the small circles on the first layer, the filament ends up catching on the nozzle and sticks to it better than the bed. It can then pull the small piece off and mess up the other areas. I was considering printing a solid first layer and then the circles but this means that all holes would have to be hand cleaned. Not an issue with a few mounting holes but a major issue with something like a grill cover. I figured that by now Cura would have a resolution so I started looking more carefully at the settings. I found this under Experimental, which I have not yet tested but hope will solve my problem. It looks similar to what JCD and Burtoogle were talking about. This looks like I can decrease the print speed for hole diameters under the set size. I will give it a try once my current print has completed and see if it does what I hope it will.
  22. If you delete the Cura folders under AppData Local and Roaming you essentially have a new install of Cura (unless there are damaged or missing files in your original install) You can try opening Cura after you have removed these files and see if it will open. You might try running it as Administrator. I have sometimes had a problem where it won't start from the original shortcut so I usually try running it from a variety of other shortcuts (Start Menu, taskbar or direct from installation location) In most cases it eventually starts. If you get Cura reporting that it has a configuration error and it wants to reset it for you, this will delete any settings and profiles you have already set up. It does, however, create a zipped backup of your old directory that you can access if you need to. If you think your Cura installation is a problem and you just want to start fresh (not worrying about saving old settings and profiles) I would delete the two AppData Local and Roaming folders and then uninstall Cura. This would ensure that all Cura associated files have been removed and there should be no conflicts with old files. I'm not sure of the purpose behind adjusting the Privacy Settings but if they are a problem maybe unchecking both would be better? On an additional note, rather than deleteing the two Cura folders you may want to temporarily move the Roaming one (maybe drop it on your desktop) so you don't lose any profiles you might want later. The Local one, AFAIK, is used as a cache so it doesn't really matter for this.
  23. Have you tried running it as administrator? You might have some permission problems. I have never had to run in compatibility mode.
×
×
  • Create New...