ESokkoEVBL

Hi, Can I make a request that the email report which get sent via email could have some extra information passed along? Currently the information is very lack luster especially in cases of errors. I personally would like what kind of errors were happening in the night when someone from night shift was troubleshooting. The only gain I get from email notifications is that I know that there were issues unknown to me. Then I just multi-select all of the emails and mark as read. For example: [Current] -> [Proposal] Printer ran into problem -> Printer ran into problem, ER58 Printer ran into problem -> Printer ran into problem, Aborted manually Printer ran into problem -> Printer ran into problem, ER63 Printer needs reconfigured -> Printer needs reconfigured, Nozzle 1 needs to be changed to AA0.8 and Material Ultimaker Tough PLA Black needs to be added Printer needs reconfigured -> Printer needs reconfigured, Material spool empty Ultimaker CPE+ etc.

I also voiced my concerns to our supplier and they just replied that some of the features are returned to management console. They personally updated and checked what features were returned. I will also update when ever I get the chance and I will reply here as well 🙂 EDIT: The features are there.

Just noticed the 8.1.2 firmware. Now just waiting until I get a free slot after we've worked through the queue.

I feel you. Had the same thing happen to me as well. Months of good valid data is now gone. Management console had great features to follow like Time-spent-in-queue, material usage, completion rate and I did follow them quite actively. I don't really understand why these features aren't on DF. I at least haven't found these features and I don't have the professional license for DF. I would love to see the same statistics as before but on-top other data such as cost of material x used material, nozzle time being hot to evaluate "nozzle life" (this can be seen manually from machine itself).

Regarding the camera functionality: In the previous firmware the response to check the camera feed was a lot better. From Cura or management console. As previously mentioned, I did not have access via DF so the camera there was always black for me. Response time to get image and see the head moving was a lot faster! A second or so the get immediately updating image feed. In the current firmware (8.1.1.0) when clicking on the camera icon, it takes 3-5 seconds to see full image. This is like downloading an image via extremely slow internet and you see chunks appearing top-bottom fashion. After the full image appears another 5-10 seconds before the image starts updating every 4 seconds or so. Although I understand the point that pretty much the only point of the camera is to see one or more of the following issues: spaghetti, shifted print, shifted build plate, no extrusion etc. It is in a way good enough for that.

Very disappointed in the latest firmware. As many have said it might just not be a possibility for some of us to run any cloud connections. At best I managed to create a connection to the printer via printer network but it has no connection to the internet. Via VPN I cannot see the video feed either. With the latest firmware we are kind of crippled. Manageable but annoyed compared what is was on the last stable 7.x.x firmware. Biggest drawbacks for our company so far has been the inability to duplicate prints, reprint, see easily the video feed, overall connection speed from computers to management console. Although we did use DF for maintenance scheduling but that's about it as we are unable to send anything via cloud (DF). Our company policies & customer agreements state very clearly that no IP can leave our servers rendering cloud systems as a big no-no. And our company ain't willing to take any agreement risks for a very miniscule part of the company actions. 3D printing isn't our primary field but it supports it but at the end its a very minor topic in the grand scheme of things. With the management console + printer IP-address operating S5 was doable. At this point I'm reconsidering getting further expansions of UM-printers as the management of the printer is nerfed. On top of it I can't create statistically sound business case to expand our printing capabilities as history is now gone. I had relatively good data for the past 12 months with usage time over 70%. Edit: I have to add something positive though. I've noticed more functionalities on the printer itself which a very welcome change. Such as showing how many prints are in queue and what has to be done to print next in a more clear fashion. Also the possibility to override the possible changes. 🙂

Hi, thanks for the help. I have tried now sending various sized prints (between a simple cube and more complex parts). The filesizes have varied a lot but highest was around 50mb .3mf file in-use. Dont know exactly the size of the .ufp file. This did not help. I then tried to re-export as STL (using NX1973) with both high-def and "normal" polygon settings. This did not help. I also tried for the heck of it the direct plugin from Cura to receive the .prt files from NX. As you've guessed did not help either. I already performed the disconnect and reconnection between my printer and DF but to no avail. Connection can be made without a hiccup. I wonder if the network type is somehow incorrect that I'm not able receive any feedback from the printer back to the internet. Maybe I could double check it with IT.

Hi, This is a page I've been staring all too long. Ports 80 and 8080 are open as I'm able to control the printer and via management console I also have camera feed. Ports 443 and 123 are open as DF is able to connect to the printer and timestamps are correct with history log. Port 5353 should be open as I'm able to connect to the printer. Although I did not "discover" the printer but instead I just connected with direct IP-address. Only port I'm unsure (don't have access to see) is the Port 32118. Does this affect my ability to send print files via cloud? Or the ability to send print files directly from Digital Factory. Could it be something to do with the web pages required to be whitelisted? To my knowledge all of the pages are accessible to me so they shouldn't be blocked. As stated, the file delivery gets stuck on "In Transit" and then fails all together. Sending from Cura over network (even over VPN) is possible and causes no issues.

Hi, As the title states, I'm unable to print via cloud. If I try to send the print file via cloud from Cura or directly start the print from DF projects, it will get stuck in "In Transit" and after a while will state "Failed Sending". I am able to send prints over network (ethernet cable to a dedicated IP-address). I can see my printer and all through Digital Factory (Well..., DF camera feed is not working). I have the latest stable firmware for the S5 (7.0.3). I can also use the management console where also the camera feed is working. Printer is in professional environment, so I've got heaps of IT-hoops and security measures. Is there a port which should be opened still? Could it be Port 32118? "When signing-in from Ultimaker Cura, the application creates its own local web server via http://localhost:32118. This is webserver handles the authentication that takes place when the user logs in from Cura. This port must not be blocked on the local computer." Regarding the port 32118, I understand that this port has to be open on the user PC? It's not referring to the printer ports here? I noticed printer has not enabled firewall. Does this have an effect to this? Something else I could check? Thanks