Jump to content

kmanstudios

Ambassador
 View Profile  See their activity

  • Posts

    4,052

  • Joined

  • Last visited

  • Days Won

    119

 Content Type 

Everything posted by kmanstudios

  1. kmanstudios
    Steps: The filament sensor stops printing This means it is either jammed or out of material If jammed, clear jam If out of material: go to material section of S5 commands Choose the material (not the core) It will only present change in this configuration Select change. Follow prompts. It will unload material. Material sensor is before the material feeder wheel and will be able to back out unless really ground down. After unloading material it will prompt you to put on new material and proceed when it is inserted.
  2. kmanstudios
    Basically go to the material section and choose the material and then change. then follow the prompts.
  3. kmanstudios
    yes. Filament can get ground up for a variety of reasons. One such as you mentioned is getting bound up in the spool and when the feeder tries to pull on it, it will grind a bit. Just good to do a bit of cleaning every now and then is all.
  4. kmanstudios
    But it is still "aborting" a print when it detects difference in nozzle heights. This means going back into the history, reloading, repositioning the print order and restarting the process. This is a pain to deal with, especially since this is not behaviour on the UM3 side of things.
  5. kmanstudios
    Having had to abort a print so that I can clean out the feeder, I can say that the prints are now going into the recent history. Dunno why it missed that first print, but it is starting to work now as expected.
  6. kmanstudios
    Well, the second print finally popped up. Talk about a delayed reaction. Did not do any of the above things though. Here is the basic operation I employ. 1. Slice and send to queue 2. May arrange or rearrange based on current need 3. Print 4. See print pop in up history I did not expect the print to show up until completed or aborted. Oddly enough the print was completed, but it finished in the wee hours when I was asleep. For some reason it hanged there and when I cleared the print and, for some reason, it showed as something else other than 'finished, so I aborted the final 'whatever it was doing'. Print was finished though. So, something happened there that I am not completely aware of all steps, but am keeping an eye out for the current print I am running. Will track that much better. Active Leveling is much, much faster though....
  7. kmanstudios
    If it is a generic profile, and people are printing PETG (Dunno about HIPS), then why is it not showing up as a generic? And, it says it is loaded, but nothing else, that is just odd. No disclaimer..... I only bring this up because it is a topic in another thread....The PETG, not anything else....
  8. kmanstudios
    What steps taken....updated firmware. Now, two prints finished, neither print made it to update history. Steps taken, printed objects. Looked at history. ? Basically, it ain't behaving as before.
  9. kmanstudios
    I am going to have to go with this in reference to third party printers. Maybe the producers of those machines should invest a bit themselves. THEN let us see how cheap they remain. Edit: It really is UM's responsiility towards thier user base and not the world. It is open source, so what is stopping them from putting forth a bit of effort? It is not like they have to write a slicer from scratch. Just a profile.
  10. kmanstudios
    There is new behaviour with this version. When I paused the print to clean the carbon off the PVA nozzle it released a long thread of material when resuming instead of a clean continuation as before. This is something I was able to capture this time, but it has happened before after updating to this firmware release. That is why I had the camera ready this time.
  11. kmanstudios
    And the memory leak goes back up again. Each screencap is about 1 minute apart from opening, to loading a generic 6 faced (12 triangles) box and then doing nothing more than positioning it at first. Open Memory: After Loading and positioning the box: One minute later: One minute after that: Hey! It went down: Oops, got my hopes up: And it keeps rising: And, so on and so forth: I closed it down after that. So, it is still growing in size, even though nothing is happening inside Cura. I am just going from screen capping the task manager to Photoshop. If I do not terminate Cura, it causes my machine to eventually crash. And, no other program I have does this.
  12. kmanstudios
    So, I go to the market place to see what is there. It says I have generic PETG installed: And I go look for it.... Nope, not there...maybe here.... So, what is up with that?
  13. kmanstudios
    We will see because mine crapped out in this latest firmware update. So, hopefully next time it is smooth. But, with the new update, Cura Connect wiped out my history. And, I just finished a print and it did not go into my history.
  14. kmanstudios
    Not easy when it happens the first time you see it. I too am used to it now, but it is a bit of a shellshock to see it for the first time and bringing on the fear of bricking a printer....
  15. kmanstudios
    Have one lined up and ready to go in 16 hrs and 46 minutes.
  16. kmanstudios
    Here is the printed model from the project file I posted.
  17. kmanstudios
    I do not start up and close rapidly. Am on Win 10. Do not go to the system tray until I close Cura. They do go away when mousing over, but honestly, it makes me wonder what little bits may be left over elsewhere. What do you mean? This folder is 175MB This is with both versions residing within. Lucky you. I have posted the pics as I watched it grow. So, do not know what to tell you.
  18. kmanstudios
    yes. and it greatly interferes with other programs. It has crashed my system. This version has not had time to do it, but the other one did.
  19. kmanstudios
    Nope. One is enough to keep up with. to be clear though, I do have a previous version installed, but only run one at a time.
  20. kmanstudios
    And as I went to capture one last bit of task manager before I walked away for a bit, I could actually watch the memory usage grow in real time. First opening, first file closed, first loaded file: Second loaded file (Go figure): After sitting for ten minutes: Time between screen caps: At this point I noticed I could watch it go up in real time. Cura Log: cura3.6REmemusage.zip
  21. kmanstudios
    Seems like as good a name as any other. Until you come up with a better name, I am sticking with this as it seems to be an odd issue. And, I wonder if it leaves little pieces in other places cluttering up a system. That I cannot say. Just finished slicing something and am going to let it just sit there to see if the memory leaks happen again. And, I am not using the monitor or octoprint in this. I just slice and send. I use the browser app to monitor the prints and rearrange them as need be. And the GUI in the dark mode seems to be functioning fully visually as I can discern at this early phase.
  22. kmanstudios
    As I was pointed to information by @Smithy in this thread: I am wondering how much of this issue may be caused by this and what can be done other than being 'router stoopid' like myself.
  23. kmanstudios
    I open it. I close it. It leaves bits and pieces in the tray until I mouse over it. the "Silent Crash" is the term @ahoeben used, so that is what I am calling it until I hear otherwise. Just started to really test it. Will leave it open to see about memory leaks. The brim issue has gone back to previous behaviour. But, according to what I read, I am not sure this is good as it was suggested by @bagel-orb to have a third version as what did happen in 3.5.1 was technically correct (By way of going from outstide to inside to outside and again to inside) and can serve a purpose as he noted. On the thread that I was pointed to, he suggested a third option which I find to be the most satisfying of all. But for now, I am not getting brim on the debossed lettering negative spaces I place against the buildplate.
  24. kmanstudios
    Still has silent crashes.
  25. kmanstudios
    All I know is that the settings I shared worked for me if I clean the glass properly.
×
×
  • Create New...