CarloK

@Kief The UM3 announces itself on the network with a protocol named mDNS / avahi / Bonjour. It's very well possible your powerline modem creates a new subnet and that this protocol isn't forwarded. It goes beyond my knowledge to dive into the details of your specific devices and configuration. What you can do, in Cura you can enter the ip address of your UM3. This often works.

@Kief Thanks for sending the log files. I see the message: "wpa_supplicant[292]: wlan0: CTRL-EVENT-BEACON-LOSS" This is new to me and I searched the internet: Often this is caused by a mismatch between sender and receiver. It can be a bug in either the printer, or in your WiFi access point. The UM3 printer is not having an update planned, and even then it's not sure it would fix this problem. So, for you, the only thing you can control is your access point. Things you can try: - Check for a firmware update in your access point - Disable ip.v6 in your access point If this doesn't work, then you'll have to change the connection from your printer to the network. Here are some suggestions: - Use a cable instead of wifi - Replace your wifi access point by another type (or add one next to the existing one, the printer is slow and 2.4GHz only so there will be old wifi routers lying around) - Place another wifi connection device next to your printer and connect this by cable to the printer. For example, a wifi router or a wifi extension device - Add a powerline modem to create an ethernet connection in the vicinity of your printer without ugly cables. Costs about €50

@wcorbit721The printer should not behave in the manner you posted here. In order to look into this we need more information from you. Could you please answer @gr5's questions here above? Without that information we can do nothing.

support.ultimaker.com is the correct method for submitting (firmware) bugs. Note that the "submit a request" button is not available on the front page, you'll have to click one page further.

@MobyDisk My gut feeling is that you experience different errors. The problem where the screen goes unresponsive after a long period of inactivity has been reported by other people as well and is a bug that we are investigating. Then, the problem with the printer freezing when moving the printer is different. Here, in the log files I see no new entries after the freeze and a very rapid printer reboot. I'd suspect an external power plug is loose or had a bad connection and interrupted the power supply when the printer was moved. Posting new logs has no extra value at the moment. Thanks for your efforts. It's now up to my colleagues to find the bug.

The 'PauseAtHeight' plugin uses the M0 command. Have you tried using that instead of the M600?

@Kief This problem sounds unfamiliar. Is it possible for you to send me the log files? From the printer menu, save the log files to USB. You can then email them to my private inbox on this forum: click my avatar picture, and then on top of the page is a 'Message' button.

Go for the R1 feeders. A new UM3 release is not planned, so you could be waiting a long time.

@Tim_Cochrane @Super_paulie Are these printers with a Material Station? And which firmware version? Stand-alone printers (no Material Station) do have the 'skip cool down' button, but for the Material Station we've to ensure the filament tip is in a good shape which requires the material to cool down.

Hoi Johannes, Sorry, ik bedoelde niet de Cura log bestanden maar die van de printer. Dit logbestand kan ik geen gedrag van de printer in vinden. Voor het pauzeren van de print op een door jou gewenste hoogte is er in Cura een post-processing plugin met de naam pause-at-height. Slice je project. Dan, onder Extensions -> post processing -> Modify G-code -> Add a script Selecteer "pause at height" En de rest wijst zich vanzelf (selecteer de 'Griffin' g-code smaak) Wat bedoel je met de vraag of het mogelijk is om de instellingen voor een print in een doc-file te bewaren? Je kan kiezen voor 'Save project', dit wordt dan opgeslagen als een *.3mf bestand. Als je dat een volgende keer opent heb je weer alle dezelfde instellingen.

Sadly, these wifi modules do sometimes break down. More info in my post: You already tried other WiFi modules. I didn't check, but be aware that the Linux version in the UM3 printer is Debian Jessie, i.e. from 2015. Look for older WiFi models. Other paths to try: - Find another WiFi usb-module with the same chip (Atheros AR9271), costs about $19. The internal Olimex board has a spare USB port, except that the connector is a different type. Try the external USB connector first for testing. - Add an external WiFi access point on the LAN cable

And here is a topic with a nice photo:

Are you referring to this article? https://support.ultimaker.com/hc/en-us/articles/360012112759

@Jankroom Er zijn verschillende mogelijke oorzaken. Snelste manier is wanneer je mij de logbestanden van je printer stuurt. Zie bericht hierboven voor hoe je dat kan doen zonder je informatie hier publiekelijk te delen.

@LoS For documentation on the mjpg-streamer service, see: https://github.com/whinesley/mjpg-streamer You'd want to change the parameters in the mjpg-streamer@.service file, but I've never tried this. Change ExecStart=/usr/bin/mjpg-streamer -i "input_uvc.so -r SVGA -d /dev/video%i" -o "output_http.so -p 808%i" the '-r' parameter is for resolution, for example: -r 320x240

@jeremymorgan Great to hear you succeeded ! Now others can use it as well. The change will indeed be reverted after a firmware update. I suggest you reach out to @Smithy, he created a nice tool for tweaking the Ultimaker printers. The support for extra camera's would be a nice addition to this tool.

You did some extensive testing, and indeed, it looks like you got it almost working. The fact you see images from your external camera means that configuration for the camera is all good, now it must be a network configuration thing. I can't spend a lot of time on this, but when I search the code for '8080', then a firewall configuration pops up which looks promising. When we disable the firewall, then port 8080 is actively enabled. I suggest to do the same for 8081 (I assume we are not really disabling the firewall, just opening up/closing more ports). Modify file /usr/share/griffin/griffin/network/firewall/nftables_firewall_off.conf At line #19 you'll find: add rule ip filter INPUT ip protocol 6 ct state new tcp dport 8080 accept Copy this line for port 8081 I hope it'll make your second camera work

Thanks for all the extensive testing you do, guys. About the 'Never' setting for Active Leveling, that was an example of very poor naming. Sorry, for that. Our native language isn't English and from this we learned that proof reading by multiple (native) English speakers is required. What we intended here was 'Use manual leveling instead of Active Leveling'. But well, given the small screen size that didn't fit and we made a poor alternative choice that could be explained in multiple ways. In 5.2.17 we fixed a few Active Leveling bugs, but from the findings here it seems like there is still a bug when you use the Never setting. One that comes to mind: The offset is stored for each print core, but when you do manual leveling, then only the mounted set of cores are updated. I'll have to check what happens with the data of the other cores. With a Factory Reset this would be fixed and might explain what @upatamby experienced. Note that the S-line of printers removed the manual leveling option. We've learned that always leveling yields better results. A good bed adhesion requires the bed to be within 0.1mm tolerance. The printer's dimensions change with temperature. A change in room temperature, sunshine, repeated (hot) prints, etc., can all be reasons for your print to fail that's why we made the Active Leveling compulsory and I recommend this for the UM3 too.

There are provisions for starting a new instance of mjpeg-streamer for every camera that's inserted: On camera plugin a udev rule is triggered (90-camera_hotplug.rules), which in turn starts a systemd service (mjpg-streamer@.service). Port numbers start at 8080 and then increase by 1 for every camera added. But, the feature for more than 1 camera was never officially supported, implemented 5 years ago on the UM3 and since then never tested. Check the log files for possible error reasons. In the dmesg file you'll see if the camera was detected and perhaps more clues. Possible reasons for failure that come to mind: in the S3 printer many of the unused device drivers were stripped, perhaps your camera isn't supported? The camera stream is started for SVGA type. Perhaps your camera starts with another type by default?

Why did you download v4.2.1? On the Wanhao website the most recent version is 4.7.1 Or, from the Ultimaker website the current version is 4.13.1

@MobyDisk When your printer is working (more-or-less), then there is no need for extra actions and you can wait for the 7.0.3 release. What I see in the log files are problems in writing the network settings, but when there is no need for change, then that's no problem. Since the bug has already been fixed for the upcoming release I don't need any extra log files.

@gr5 This is not my specialism, I double checked with our Electronics department and I mixed up. During development both NAND and eMMC have been used. Production versions of the printers use the eMMC memory and not NAND as I've said before.

@MobyDisk In your v7.0.2 logs I see a bug we fixed in the upcoming v7.0.3, but I'm not sure this is causing your problems. The bug is that on saving configuration files we try to replace the existing file, but we didn't handle a situation where the file is missing. In your logs this concerns the network settings file. I asked a colleague for when the bug was introduced, but I guess it has to do with performing a factory reset and then the settings file is removed. Is your printer booting occasionally? Would you feel comfortable with using SSH to login to the printer and execute a command?

This bug was fixed in v6.4.0, released May 2021; only applicable to S5 printers with AirManager and/or MaterialStation. The problem was that on boot it takes some time to detect the external devices, when a print job was waiting in the queue this could already start and would later block the printer.

@walkerj For quotes you have to contact the reseller in your country. At this page it shows a button for requesting a quote for the Pro Bundle, just write down in the request that you already own an S5 and want to upgrade this. For extra info on the BreakAway material: https://ultimaker.com/materials/breakaway, here also a button for finding a reseller. About the nozzles, with a BB core you can print all materials, no need to change. The AA core has a slightly different internal geometry, intended to reduce oozing but the effect is minimal. Just click away the warning when the printer complains at the start of a print job. The other way around is not allowed, you can't print PVA with an AA nozzle. This will soon lead to a clogged nozzle as filament will start to carbonate in the areas with less flow.