Jump to content

MobyDisk

Member
  • Posts

    30
  • Joined

  • Last visited

Personal Information

  • 3D printer
    Ultimaker S3

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

MobyDisk's Achievements

4

Reputation

  1. Happened again after an overnight build, firmware version: 8.3.1.0. The printer is on and the web UI reports the print as finished. I assume it thinks it is at the "confirm removal" screen. Have you considered a button on the remote UI to reinitialize the screen? So when this happens, we could press that button and report if the screen comes back. UPDATE: After I power cycled it, it indeed displayed the "Confirm Removal" screen but the lights were *on* which is odd since I have them set to off.
  2. Another occurrence after a few months-long hiatus from printing. A print finished <5 minutes ago. I remove the print from the platform, then noticed the UI was at the "Ultimaker S3" logo screen, as displaying during bootup. It suspect that I turned it on, queued the print, and never even looked at the printer until after the print was done.
  3. I want to know why we all have such different experiences. Could someone post a 3MF file and we can all test print the exact same model with the same PLA and the same PVA, and post videos of the print? When I purchased my printer I straight-away bought a spool of polymaker PVA because I had heard bad things about the Ultimaker PVA absorbing humidity. But since I have had almost no problems, I haven't even opened the polymaker. So far I have only printed with PLA in the winter. I wonder what the relative humidity is in our various places? I don't see how heating filament to 55C and sitting it somewhere will help if the relative humidity in the room is 80%.
  4. Another occurrence. Overnight print, had a feed error, fixed that this morning, came home ~10.5 hours later to a finished print and a black screen. Is there continuing value in me posting logs?
  5. @gr5 Happened again, *while I was watching* 1. Cura: "Print from network" 2. Walk over to printer, open door, loosen clips, remove platform 3. Printer homes the build plate and starts pre-heating 4. Grab my 3DLac, walk into the next room, spray 5. Return to the printer, place build plate 6. As I was pushing the glass build plate onto the metal platform, the printer slid backward about an inch, and *the screen went black*. 7. I aborted the print remotely, then confirmed that the touch screen would not respond to my touches. 8. Power cycled the printer, exported logs via the touch-screen UI. 9. Restarted print This is definitely not the first time that I have removed the build plate and applied 3DLac or glue just as a print started. Is that a problem? I just make sure I finish quickly since I know the first step is to warm the platform before it runs the auto-leveling. It is also not the first time that applying pressure to the glass to slide it under the rear clips has caused the printer to slide back a bit. I don't think I was pushing too hard as the printer is easy for me to move around on the table. I regularly move/rotate the printer this when loading/unloading filament as well. The printer has been on for at least 24 hours, and did a couple of 3 - 4 hour prints yesterday. I wish I had recorded the whole thing. The screen blanking absolutely corresponded with the instant that the printer slid backward. ultimakersystem-0030d6283580.7.0.2.boot-1.log.zip
  6. @gr5 - Sorry for the belated reply - I am fairy certain that I have never changed cores while the printer is off. It did not occur to me that this would be possible until I read your post. It has been almost 30 days since I was last on here and I have had no further incidents of either type. Although I have not attempted any >12 hour prints since that time. I will continue to post logs should it happen again.
  7. @gr5 @CarloK In both cases I rebooted and it is working just fine. @CarloK I am quite comfortable with SSH and embedded systems. FYI: I have not done a factory reset. Could I have improperly power-cycled the printer at some point? Do my logs from Jan 30th show the problem? If not, then the missing file was introduced between then and now. I am not having any networking problems with the printer. If this SSH session will help you do a root cause analysis, I'm open to it. But so far, the problem is rare enough that I can wait for 7.0.3 and continue monitoring in the mean time. Would you like me to power cycle the S3 and post some more logs of bad and good boot ups? I could do it a few times and see if it is consistently an every-other-time kind of thing, or if it is random. P.S. I am on US eastern time.
  8. Happened again at bootup. I don't see any errors in the log that seem relevant. Frozen screen at bootup 2022-03-08 - exported after reboot - 2022-03-08 ultimakersystem-0030d6283580.7.0.2.boot-3.log.zip Frozen screen at bootup 2022-03-08 - logs obtained via api before reboot.zip
  9. When supports are set to "Touching Buildplate" Cura may make supports that are unprintable and that don't even touch the model. I attached a picture of Cura's supports for the Makerbot Knight by wes. The support I circled in red does not support anything, and is too thin to actually print. So it will slowly form a ball of support material that sticks to random places on the model. I suppose for now I either need to avoid this option, or to manually sanity check the supports and use the support blocker to eliminate them.
  10. I just powered-on my Ultimaker S3 and the touch-screen is frozen at the "Ultimaker S3" logo. The touch-screen is non-responsive. However, the web site is working and Cura connected to the printer and the "Print over network" button is available. This looks like the same symptom, but it happened at power-on instead of after sitting idle for a long time. I can't get logs via the touch-screen without rebooting so I'll do them using the web via the API like I did before. P.S. I clicked the button to send my print job. The web UI is waiting for me to switch materials, but the touch-screen UI did not change. ultimaker frozen log.zip
  11. @CarloK Happened again. I must reboot in order to access the Diagnostic menu and export the logs. Will the logs get reset upon reboot? Just in case, I also attached a JSON export captured from before I rebooted. I will open a ticket and I guess I will post the ticket number in this thread so that others can track it and add to it? Or are the tickets private? 2022-Feb-08 2021 MobyMaker logs from before rebooting.zip 2022-Feb-08 2021 MobyMaker logs.zip Also, I was able to confirm that the touch screen did not respond while it was black. I clicked where "Confirm Removal" should be and the printer did not stop pulsing the lights and did not re-home the motors like it normally would. I also think the backlight was off because it was totally black. Your LCD panel is dang good, but I am pretty sure I can tell a powered-down display from a black screen.
  12. @SandervG Why does Cura not ask me to enter the DNS name of the printer, instead of the IP address? The name is fixed, but the IP changes. It makes much more sense for me to enter "ultimakersystem-00306d238850" which works forever, rather than "192.168.1.75" on Monday and "192.168.1.67" on Tuesday and "192.168.1.56" on Wednesday...
  13. @CarloK Thanks, I will use that option next time. The print finished successfully and a reboot fixed the problem. If it happens again, I will post to this thread and open a support ticket. Is there anything else I can do if it happens again that might be helpful? One idea I thought of is to try and touch the screen on the left side to see if the touch sensor is working. I believe it writes log messages when you switch to a different tab.
  14. @Dim3nsioneer Thanks for the info. Is there any documentation on this? I did finally have the sensor alert me when I was printing too fast with a 3rd-party filament. So I now can confirm that it does work. And that the printer can recover.👍
  15. @JTMD Any links for those? I only get the official ones.
×
×
  • Create New...