robinmdh

Ik denk dat de upload niet goed ging, je kan de upload via USB kabel nog een keer doen. In Cura kan je vanuit het drop down menu waar je printers selecteert naar het manage printers menu gaan. (dit kan ook via settings -> printer -> manage printers...) in het manage printers menu is een Update firmware optie, daar kan je naast de huidige/nieuwste versie ook een eigen versie kiezen. TIP: Soms begint het programmeren niet erg snel voor mij hielp het dan als je de printer uit en aan zetten terwijl die aan de USB kabel is aangesloten op de computer.

je kan de buildplate apart op een temperatuur zetten, het zelfde met de hotends en kijken of de printer aan blijft met zet de buildplate of 60+ deg C zet hotend 1 op 150+ degC zet hotend 2 op 150+ degC als de printer in stap 3 rebooten dan kan je dit nog is doen met bv hotend 2 eerst aan, etc Als de printer reboot voor stap 3 dan is er mogelijk iets mis met de power supply of er zit kortsluiting in de buildplate. Als je een multimeter hebt zou je de weerstand van de buildplate kunnen meten dat zou +- 3.7 Ohm moeten zijn. Anders kan je nog kijken of het me beide hotends aan goed gaat, dat zou altijd makkelijk moeten kunnen. Gebruik je misschien een 3d party hotend die meer stroom trekt?

yes, you can download a CSV file version of this data by pointing your browser to: http://192.168.178.42/api/v1/printer/diagnostics/temperature_flow/5000?csv=1 Where the ip address has to change to your own printers. and you can change the number 5000 to get more or less data points, but the buffer is not infinitely large. So if you are looking at more long term trends you might have to periodically get this and splice the files together based on the timestamps/first column.

A lot of time went into the active leveling feature, A lot, A lot. That's not an excuse but the sensor is quite noisy, the spring pre-tension is important(I recall 14 mm between the bottom of the buildplate and the bottom of the buildplate support approximately, I could be wrong though) and the buildplate warps while heating up by almost 50 micron a glass plate is also just not super flat and can be pre-bent by as much as the heating moves it, the hotends shrink and grow so need to be heated but having the heater on causes more noise on the sensor, 1 annoying diode that is so inconsistent it completely throws off the capacitance, blobs of plastic under the printcore, EM noise cause by external factors, the rods and axes are bent as well, etc. Those are all some of the things we've managed to fix over time. There is some more we haven't and then some we don't know about 😄 😭 But for the UM3 this is it. That said when validating multi-point leveling we did manage things like sheets 0.1mm thick with almost no variation if we probed every mm. The question is then on how many printers can you do that, etc. And on the UM3 only 3 points are used so it still assumes a flat surface in the end. so you really don't miss anything when you turn it off/ set it to Never if you did a decent job at manual leveling, you don't transport the printer large distances and the surrounding temperature is relatively stable... If you feel adventurous and want to enable multi-point active leveling on the UM3 that might work a tiny bit better. It takes a lot longer though. And you know you have to enable dev mode and be somewhat handy with Linux. If so, copy this 9066.json to the /var/lib/griffin/machines/9066.json on your printer. you can also changes other values by setting them in that file, you can just delete the file when done. you can have a look at /usr/share/griffin/griffin/machines/um3.json to see what properties there are in that "bed_level_probing" section. spacing controls the size of the grid for instance. NOTE: this is experimental and provided as is without any warranty, etc. though you are unlikely to brick the printer by doing this you can just remove the file if you want the feature gone. 9066.zip Ich verstehe das deutsch aber ich spreche es nicht, writing it is even worse, sorry.

give the precursor to the bowden tubes coming loose being no extrusion there are some more checks you can do. can you check if your front fan still spins while printing? if this is barely spinning or not at all you'll need to clean out the tiny bits of filament that can get stuck in there. https://support.ultimaker.com/hc/en-us/articles/360011635039-Check-for-debris-in-the-Ultimaker-S5-s-front-fan-of-the-print-head Did you ever clean the printcore when this happened? There is a princore cleaning guide in the printer findable via: ⚙️-> maintenance -> print head -> print core cleaning or alternatively have this useful guide wit visual examples of what the filament should look like though it was for the UM3 or this video for the S3 and S5 (note that you can also use PLA instead of "cleaning filament")

like @SandervG said the 700 degC is not a real temperature. But 2 things are happening here: One thing is that before the printcore switch, the printcore that is about to be switched off is intentionally set to a lower temperature (note the dotted target lines changing first). The other printcore is brought up to temperature, the exact timing and temperature varies by material and flow rate. This is a feature of Cura and can probably be tweaked there. Secondly the PID temperature controller is momentarily believing that 700degC is the current temperature and therefore it stops the heater because the set-point is lower then 700degC. The sub cause is intermittent breaks in the connection between the printcore and the printer. this can be due to the Pogo pins (cleaning those and the pads on the back of the printcore can help) or breaks in the cable* or the connector moving during printing, contact spray might help. But in the end it will occasionally happen. This was fixed by discarding the 700 degC in the S5 and S3 software in the 5.4.2 version, but I don't see any mention of that bug-fix in the recent UM3 release. So it might not have been included, I'll have to check with my colleagues. *EDIT: I found out that this specific spike ignore fix was not included in this update. we'll have to discuss internally if that would warrant an update at some point down the line. From what I see in your graphs I think this fix is not in your version (based on the downward spike in the heater output at the time of the 700 degC spike in the temperature measurement) but it is hard to tell without the ability to zoom in. The result of one 700degC spike is a cool-down of around 5 degrees which has a very minor impact, but more sustained spikes can cause a bigger visible defect in the print. The units for the heater in the graph are between 0 (off) and 255 (which would be heater full on). I hope that at-least answered some questions @Muggebadscher ?

hey @Winchester Ultimaker is just barely 10 years old so a 12 year old printcore does seem a bit far fetched indeed. Also printcores are normally limited to 350 degC. I haven't seen this before in all the time since we made the bit of code that handles this (and that bit has barely changed), while it is technically possible to overwrite those values with the right gcode commands, this shouldn't hurt anything (the data is just for diagnostics), the static(important for operation) data is kept on separate pages and should be fine. The only moment you have a problem with it is if you want to sell the printer, since it is a decent indication of usage (normally) in that case you can now refer to this post I guess. just for that one 80CDF5360000 printcore though 😛

TL;DR: yes, with dev mode enabled, a simple text file and 1 console command or winscp. it should even work for both locations with one file. A little while back we made a feature for the S5 and S3 to set the WiFi via USB, unfortunately that hasn't been ported to the UM3 but the UM3 does use the same back-end for networking: connman So that means you can create a file like explained here: https://support.ultimaker.com/hc/en-us/articles/360018123920-Network-setup-via-USB Then you'll have to enable dev mode like @Smithy said, and scp that file to root@<your.printer.ip.adderss>:/var/lib/connman/service.config To scp a file you can use the scp command on Linux, Mac or presumably on window10 via windows shell integration the command would look like: scp service.config root@192.168.178.35:/var/lib/connman/service.config where you replace the ip address with the ip address of your printer. if you don't know your printers IP you can find it by using Cura's "manage printers menu which you can find via settings -> printer -> manage printers or via the drop-down printer selection box at the top right; Then you select connect via network and select your printer name and the address is shown on the right. alternatively you can use winscp on windows which works more like a file manager. You can disable dev mode when the setting works but when you update the firmware to a new version the file will be removed and you'll have to redo the setup, but we've just had new UM3 firmware released for the first time in quite a while so not the biggest issue. Which all is basically this or this manual page The upshot is that you can list multiple wifi network configurations in that one file which should allow it to connect to both networks, I haven't tested this behavior though.

@CarloK Awesome that you're here answering questions on your time off man!

Every time the Material station boots up it tries to pull back the filament, when it appears to be moving freely(E.G the materials is not in the printer feeder or the printer feeder leaver is open) it will unload that material, This can then fail if the material is not deprimed (it is deprimed when you can see the material pulled back to above the printhead in the bowden tube and clearly not in the printcore). This must be what happens in your case because otherwise the printer won't go into the stage that can emit those errors on bootup. Do you have the feeder leaver opened up? it sounds to me like you had a previous error but did not completely resolve it, if you remove the boden tube on the printhead is the material stuck to the printcore? if it's not that it has to be something to do with the bowden tubes behind the printer or the decoupler (also behind the printer/material station) What is the meaning of the 【𝟭.𝟱𝟱 𝗺】? as far as I know there is no distance in the error message.

yes, and we did plan that story, but then the argument was made this would take too much time and suddenly writing to usb sticks that then might be too small would also not be super great, so we did make some scripts to do exactly this but you'll have to ask support about it to get them + instructions. This flow does sadden me but testing and integrating this with the update process would indeed have taken a decent chunk of time... Yes I suppose, have you ever used dd? if not please don't, if yes then you already know how. Also 6.2.0 has been released, anyone here install it yet?

1) the bed temperature: does it also show as way too hot on the temperature logging page? 2) the hotend: the most likely cause is the printhead's front fan not spinning correctly anymore this causes the hotends to heat up beyond the heat break and can be caused by very thin strands of filament ending up in the fan. The fact that your hotend melted the plastic at the top of the hotend probably means you have indeed baked you Teflon insert in the hotend (this shouldn't be heated to PLA melting temperatures!!! that damages it for sure). So like @gr5 said you should replace the hotends, but the cause is likely still there (E.G: a broken fan) so I'd advise you to replace/clean/fix the fan as well.

This update resizes one partition and shrinks the location where we store all the prints in you queue... This does not happen every update, most updates have no such effect, but due to updating the whole OS and in the process everything seems to need more space.

Nope, only with the firewall on. Firewall off actually still has the firewall but unblocks local website and API.

Hotfix 6.1.1 is on the way for the issue we've identified, pending tests and approval. In some rare cases corrupted material profile files where giving problems and a small change in python's xml.etree.ElementTree library meant this caused the application not to start up. As a workaround you can turn off Cura and "reset all printer settings" in the settings menu before upgrading, that will allow you to install the 6.1.0 without the current problem. In the mean time if you have already gotten stuck at the logo screen, please open a support ticket as @SandervG said! Use the 6.1.0 recovery image not a 5.x or older one! as mentioned a lot before 6.x can't be downgraded, this can brick your printer in a not user recoverable way.

did you try a settings -> "reset all printer settings" (used to be called "factory reset")

it could be the Z is moving past the home point, please also check the Z end switch in the center of the botom panel on the UM3(E), if anything got stuck in there it could explain this maybe. Changing the starting point can be done by using G92 command in the start of your G code first do G0 X0 Y0 then A G92 X1 Y-1 or something to undo 1 mm of bending outward. you can edit this in machine settings in cura I believe.

All networking data should be removed on a settings -> "reset all printer settings" (used to be called "factory reset") If you haven't already tried that, it might fix your problem. Otherwise version 6.1.0's new import network settings via USB might help as a workaround though this shouldn't be needed.

It should definitely change!, it could be that you BB printcore was programmed as an AA printcore... unlikely as that seems, it would explain your other problem.... does the slot show as empty when the hotend is removed? (can be done without using the load/unload/change as long as no filament is keeping it in there)

haven't seen anything like this, all I can say is check the material isn't ultimaker PVA iso generic natural PVA if that is what you sliced for, make sure you have a recent firmware version installed and make sure the nozzle is a BB core.

since I haven't worked on the UM2+connect I'm not sure but you can always browse to www.ultimaker.com/ER207 which will tell you a tiny bit more... the important part in this one is probably: "Unfortunately this error most likely means there is a faulty component in the board. If you are encountering this error, please raise a support ticket."

Thanks @bvsengineering for reporting this, I'll add the bug to the backlog and have a look. Will update when I know more! The switches are only actively used when homing... That has been the case since the UM2 and it does occasionally make printers create horrible noises like this 😞.

It seems likely you are printing or have not clicked the confirm removal button on your print. Please confirm removal and/or abort or wait for any running print to finish completely. The printer will reboot so to preserve a running print we don't allow users to enable/disable this setting during printing. Can you check if that solves the problem for you?

Perfect recovery strategy! I think @sj3fk3 might have missed that 😄 "S5 pro" is a bit ambiguous, is it a stand alone printer or with Material station attached?

I've not encountered the situation that a hot pull did not work at all, That does make me wonder if you are doing the hot pull corrctly it is very short not more than a second all the way inside the printcore.... That said I do have some guesses that might work: you can try pushing it out while it's extra hot use air pressure to push the filament out the other way while the hotend is hot. WARNING: if any hot plastic makes it past the PTFE insert and sticks to the metal there it's even more difficult to remove.... also air pressure may make things fly, take the appropriate precautions. (I've used air pressure before to get a clog out, it did work but does not clean much but the clog itself) try to dissolve the PVA with water... by pouring a smal amount into the top of the hotend, circulation would be a huge problem though, will likely take multiple attempts.... WARNING: water and electronics do not mix, be very careful!!!! get a small drill bit (preferably used manually) to drill out the filament until you can perform hot/cold pulls. WARNING, drilling is likely to damage the PTFE insert or the metal of the hotend as much as the plastic stuck in the printcore. This is all my own speculation, and I'm not someone focused on materials. Some of the methods above would obviously void any kind of warranty, etc. Good luck!