tomnagel

Live camera feed over LAN is still there, right? Press the circled round blue button to access it while in the management console.

We hear you. We are currently investigating what it means to bring back reprinting soon

Do you have more room on one side maybe? Adding strength and stiffness can also be done by the geometry. "Just" make it more bulky.

Thank you for your elaborate answer. We take your feedback seriously. Maybe we have underestimated the amount of users that use this piece of functionality. Yes, you have paid for a printer with a set of functionality. You are free to stay on the firmware version that you bought the printer with. I just don’t understand your reasoning that we’re taking things away from you. The reason we want to move away from the management console on the printer is the limited processing power on the printer. The cloud has so much more options. And the decision was made to kill most of the functionality locally on the printer, simply because keeping that working when upgrading other functionality of the printer costs resources. And resources are always scarce. Finally, reliability. We should not have removed this functionality without proper communication. That was a clear mistake. I apologize for that.

Ultimaker is very very loyal to its customers. Products are supported for a long time and keep getting software upgrades for years. You always have the option to keep using firmware 7.1.3 which is available via our support pages. (Note that downgrading from fw version 8 must be done via the firmware recovery method, which is explained on our support pages) Our cloud offerings start with a free version. If you then want extra functionality, we offer paid subscriptions. Many companies do this, this is not evil. Though I can’t look in the future, I expect this freemium model will stay. We are not stealing your printer from you. Your voice is heard though. Do you mind explaining why the local management console is important for you? Which functionality do you miss now?

I’ve had my print stuck in transit as well. In my case the solution was to turn off all ip-v6 support in my modem.

Temperature helps a lot for sure. The drawback is that for PLA (which is most used in combination with PVA) deformations start to occur from 35C onwards. So we decided against it. 3-4x speed increase at room temp is already great improvement.

The issue that we see in your logfile has nothing to do with active leveling, but may have occurred during active leveling. The log you provided span the following period: -- Logs begin at Thu 2023-02-23 09:29:35 UTC, end at Fri 2023-02-24 07:25:09 UTC. -- You say "last print was without rebooting". That print was not included in the timespan of your logging then? I have seen only 1 error in your log. I'll have a look again if you provide logs from that 2nd error please.

Thank you for providing the log file. We've studied it, and see it is an occurrence of a bug that we already identified recently. It will be patched in 8.1.1 that we intend to release within 2 weeks. Workaround is: after booting up the printer, wait 30 seconds before starting a printjob (from USB, or a XY calibration from the printer itself, because that is also a printjob)

I am biased because I work for Ultimaker, but I can say I find the PVA removal station a joy to use. It just fixes the hassle that PVA gives. It features a basket with a lid on top that makes sure the part is submerged in water (most part float), you can lock the part in the basket so that it doesn't spin with the water, and PVA removal goes 3-4 times faster than in still water. The water bucket sits on a base station, adn can easily be carried to a sink to empty and refill. It's all not rocket science, but the product really is a joy to use.

By the way, we were wondering why your existing IS and keys stopped working. The file Jos is referring to is not touched during a normal firmware upgrade. Can you maybe explain that?

Hi Walter, We're looking into this, this was unintentional. I am very sorry to hear that this breaks your workflow. In the meantime you may want to downgrade back to 7.1.3. Please note that this can only be done via the recovery procedure with an SD card, not via the UI panel on the printer. See this post for a link to the instructions. Can't promise anything now, but we intend to fix this with a patch release.

Can you explain why you would want to manually move the print head in X and Y direction?

Search for the file printer_preferences.json in that file, the XYZ offset between printcores is stored. XY is set by the user via the XY calibration procedure, the Z is measured by the printer during active leveling. The offset is stored for every pair of nozzles. I think you can easily figure it out by looking at the file, if you want help then feel free to ask

Zoek eens op BuildTak flexplate die zijn verkrijgbaar op maat gemaakt voor de S5

remote control of the print head is easy Turn on developer mode SSH into the printer, login with ultimaker/ultimaker you can then send gcodes such as sendgcode M105 or sendgcode G1 X100 Y100 Have you already figured out where to store the XY offset data?

Of course, don’t worry, that’s not what I will be asking of you. I’m very happy with this outcome though. Roughly a month ago our firmware team worked on solving an issue that is very similar to what you are describing. This issue was that when a user paused a print and then aborted, a certain variable was left in a wrong state, impacting all print job after that. This variable is now reset only after a reboot. This will be fixed in a firmware version that we hope to launch before mid Feb. I apologize for the bad experiences you had. This one was really hard to find since it took a long time before we found out how to reproduce this.

Could you please reboot the machine, and print the same printjob again? I need to know if the problem persists over a reboot

In this sequence of 6 times, did you ever reboot the machine? Did you use Cura to slice the printjob?

Super-paulie, I’m sorry to hear you have this problem. We (in R&D) hear about this from time to time, but are not able to reproduce this. You write you have this problem now 5x in a row. Can you please dump the logfiles to a usb disk and send them to me. I’ll DM my email address. Do this before rebooting the printer please. In this series of 5, did you restart the printer at any time? If not, would you try that and attempt the 6th print?

We thought about this. A bigger bucket will make it too heavy to be portable. It needs to be portable because we want users to be able to put in fresh water every now and then.

“I have an S5 so it is dual extrusion” is not true, it is perfectly possible to print single extrusion prints with the S5. Judging from the pictures you have used the same extruder for the part and for the support. Then you get these mediocre surfaces. If you find the roughness of the surfaces important, then you should use a separate support material in your second extruder. This can be breakaway material (BAM) or PVA. if you are new to plastic printing, don’t use PVA. BAM seems a good fit since you will be able to literally break aaay the support (in the sense that is not mechanically locked inside the part, it is on the outside). My most important advice: stick with the default settings in Cura. Do not start tweaking until you have made a lot of parts!

The forced Cooldown of the printbed is removed from all s-line printers in latest firmware. However, when a material station is connected, the material still needs to deprime (unload it from print core and form ideal tipshape). For PLA this happens at 60-70degC, and unfortunately that takes a long time to cool down to. This tipshape is absolutely needed for automatic unloading to the MS, and later loading it back to the printer. And yes: if your next job is with the same material, then this deprime is not needed. We may optimize this one day, but this optimization competes with many other cool stuff on the backlog.

Have a look at this support article: https://support.makerbot.com/s/article/1667417981430

Have you installed latest firmware (7.1.0)? If you can reproduce the situation again, please save the logfiles to USB disk within an hour after the error, and post the ZIP file here, I will have a look