Jump to content

sj3fk3

Team UltiMaker
  • Posts

    82
  • Joined

  • Last visited

Posts posted by sj3fk3

  1. On 6/10/2021 at 3:24 PM, Chaphasilor said:

    Hi, not sure if this was introduced with this release, but I noticed an annoying bug:

    When loading a new material, at the end you need to confirm material extrusion. Previously, if you didn't confirm extrusion, the printer would auto-confirm after a minute or so and stop extruding.  
    However, last week I forgot to confirm and ended up wasting a ton of material, today it almost happened again 😅

    It would be nice if you could re-introduce/fix that feature!  
    I do understand that auto-confirmation might not be super-reliable either (what if something went wrong and no material extruded?), but you could always show a small dialog after extrusion was auto-confirmed to let the user know they should make sure everything is loaded correctly before printing 🙂

     

    We are going to look into it!

    • Like 1
  2. On 6/8/2021 at 11:24 AM, UlrichC-DE said:

    I have now had a chance to test the print break with the 6.4.
    It worked fine with Ultimaker filament. With other filament it is still noticeable.

    Many greetings

     

    That is correct, with 6.4 we have a new "deprime" procedure for all Ultimaker Material Profiles. That ensures a nice tip shape at the end of the filament. In 6.5 (coming out in a couple of weeks) we will also roll out the same behaviour for all the generic material profiles.

  3. On 5/25/2021 at 2:00 PM, Skaegget said:

    I don't know. I use the wired connection from now on.

    I still have some disconnections though. I have my printer connected both via LAN and Cloud. Could that be a problem?

    The cloud-version of the printer is quicker and more reliable with updates after material- and core changes.

     

    When you say disconnects you mean you don't see the printer online in Cura or when you go to the Digital Factory page? In that case there is a fix on the way for that issue! \o/

  4. On 5/21/2021 at 1:34 AM, platzbr said:

    With some small experimentation, I have noticed that my 8GB USB Drives (FAT32) seem to work fine with the S5, but larger 256GB flash drives (exFAT or NTFS) do not get recognized. 

     

    Is this a hardware or firmware limitation? Possible future compatibility update?

     

    (We are not allowed to use externally supplied USB drives or ethernet communications)

     

    I don't think the size is the limit, but the file system is. The printers are Linux based and Linux does not really have very good support for NTFS. FAT32 can be as big as 8TB? So why not just try big partitions with FAT32?

    • Like 1
  5. 56 minutes ago, glx said:

    Cura somehow has another versioning-system, it asked me to update my S5 to firmware version 6.2.1 (it had already v6.3 installed) 🤔. The Printer itself showed the correct v6.4 and installed it.

     

    Yes, we are working on that.. Cura can be stubborn now and then 😉

  6. On 4/29/2021 at 6:13 PM, gr5 said:

    For other people reading this thread - understand that normally you can upgrade the firmware from the display - this unbricking is only for people with an S5, S3, or UM3 that is "bricked" in that the display touch screen is useless.

     

    Also important to notice: Sometimes you get a stuck screen, but the printer is not actually "bricked" a reboot (or two) sometimes also works. If you have tried rebooting and that did not help, it's time for different measures. If you have developer mode set to on, it's always good to see whether or not you can still log into the printer (not for the fainthearted). If rebooting doesn't fix it, contact support.

    • Like 1
  7. On 5/12/2021 at 9:44 PM, UlrichC-DE said:

    With Ultimaker Filament it actually behaves differently.

    The firmware does not make a clean deprime with the 6.3, but it is at least slightly better than with the 6.2.ums5-no-deprime.thumb.jpg.6d1b0eaf26448cf5f27721814b81a36c.jpg

     

    The deprime has been much improved in 6.4 (The Ultimaker material profiles only for now). Please give it a try, you should see much beter results. Next big release (6.5) will also have the same improvements for generic material profiles.

  8. On 4/29/2021 at 7:44 AM, eddieparker said:

     

    Thanks sj3fk3.  So it looks like my machine gets hung if I leave the material station plugged in when an error happens.  I currently work around it by unplugging the material station, then plugging that power cord into the ultimaker, letting it error there, unplugging then plugging in the material station again and it starts working.  

     

    If it happens again I'll get logs to you folks.  It's definitely not ideal.  I'm thinking of getting a power strip inbetween the material station and the wall so it's easier to do this manoeuvre with at least.

     

    When you say "error" can you be more specific? What kind of error? Maybe even take a quick photo of the screen (while you are at it, also take a photo of the printhead that shows where the filament is).

     

    I think there are better ways to get out of the situation, but we really need a little bit more information to help guide you out of it.  

  9. 6 hours ago, eddieparker said:

    I've since flashed it and it seemed to be working -- although I just came back to this post to ask about the SD card extension as it *just* happened again where the material got stuck, I got an ER65 or whatever, and then on powercycling it it just never came back to life.  I'm trying my darndest to avoid flipping the titanic beast over, so if you could get back to me with the product to buy to flash it so I only have to flip it one more time, that'd be great: I'd like to avoid more chances of breaking the hardware by trying to fix it!

     

    I honestly don't think you need to do a complete restore then this happens. Have you tried to reboot the printer (again)? It could be that you maybe need to do it again. One other (maybe more safe) option is to enable the developer mode. Because maybe it's only the screen that is stuck and not the whole system. In that case you could log-in to the printer and just type reboot.

     

    Also, we would really like to have your log files as there is clearly something going on there. Could you contact support and coordinate with them to give us the logfiles?

     

    p.s.

    ER65 is a flowsensor warning. One should be able to continue from it. Are you sure it wasn't a break fail wizard? And if so, did you actually go through with the wizard? I've made the mistake once of ignoring it and then you do end up in a mess.

  10. On 4/8/2021 at 6:52 PM, mjhangge said:

    I'm willing to try anything to help fix this problem. Since you're not experiencing it there at UM, I would humbly suggest working through a few users like the ones who are sending you the problems. If you tell me what to try, I can video my attempt or document it in any way that might help - and I'm sure others would be willing to do the same.

     

    Can you tell us a little bit about the wifi setup? If you want just send me a pvt message on the forum. I would be specifically be interested in: Is it: 2.4Ghz / 5Ghz ? Does it use the same SSID? What kind of security? (WEP/WPA/WPA2), what is the brand of WiFi access points (or router)?

     

    Also, you could try to setup wifi via USB this way: https://support.ultimaker.com/hc/en-us/articles/360018123920-Network-setup-via-USB- 

  11. On 4/14/2021 at 10:24 PM, Zara23555 said:

    Ive tried downloading the Ultimaker S5 (2018 - early 2020) firmware version 6.2.0 as well as 6.3.0, but the website isnt actually downloading. Can anyone assist? Thank you

     

    Looks like there is a issue with the site and Chrome browsers. If you right click on the link and choice "Save as" it does work (or if you have it, use Firefox, Safari, maybe even Edge) 😉

  12. 5 hours ago, eddieparker said:

    Thanks.  Unfortunately I've lost the logs since I flashed the firmware since.  It did one successfuly print after I flashed it, then it gave me an error code as some filament got wrapped around the Z axis threaded rod, I removed it but it didn't quit complaining so I power cycled it, and then it bricked again. 😞

     

    I'm just finishing flashing it again.  

     

    Unrelated note: are there any micro SD card extensions I can use with the Ultimaker S5?  Having to tear apart the station to turn it upside to flash it is a bit scary given how big of a unit it is - I'd rather if I could have the micro SD more accessible, especially if flashing is going to be more common. 😞

     

    Ah, yes I think some of our debug setups have these extensions on the SD card. However it is far from normal to have to use them. When you say "bricked" what exactly do you mean? Because a black display or a stuck boot (with the Ultimaker logo) does not mean it is bricked perse. Also it might be a good idea to turn on dev-mode and ssh. That way you can get "into" the machine if you think something is fishy and you might be able to type something like "reboot" and have the system restart itself.

     

    I'll ask one of the engineers to comment on what the use to extend the SD reader as I haven't done it myself.  

  13. 15 hours ago, bkeung said:

    I have a persistent ER86 Error after this firmware update. I have the S5 pro bundle.

     

    There are no changes made with regard to the Air Manager or ER86. I suggest you contact support as the air manager fan may be faulty. ER86 is triggered if the fan can not reach the desired speed (with a fault margin of about 70%). So if you see a ER86, that means the fan is really not spinning at the right speed. (You might not be able to see this with the naked eye).

     

  14. 11 hours ago, eddieparker said:

    Support told me I had to reset the ultimaker so I did that.  Now it's just blinking lights for the last hour but not booting up. 😞

     

    Any tips or tricks to get out of this?  I'd like to restart my print if so.

     

    I am afraid the existing print is lost. I also think it's a good idea to contact support again and send them the logfiles. We need to investigate what's going on here. 

×
×
  • Create New...