Shadowman

Do as suggested and reset Cura Connect Then........ Can you see the camera feed within Cura on your computer? If yes then you will only be able to see the camera on your phone "only" if on the same wifi network unless you made changes to your network; this is how the application was designed.

Sadly; when I loaded Cura 3.5 all appeared to be fine however, when I went to print it was one issue after another never completing a successful print. I too went back to 3.4.1 late yesterday and “immediately” everything was fine. A total waste of time along with the associated frustration. Thank you for sharing your experience.

Can you view the camera on your computer?

Thank you for the updated information. I shared that with my distributor shared with me a week ago. Here is what I received;

No arguments from me. Impliment a ridgid beta program and encourage folks to participate; maybe even getting folks to participate with test prints along side their normal prints. But, do not release a product only to immediately be made aware of significant issues and not engage with those presenting the issues much less not make clear what is being done. Yes, all SW has bugs to varing degree and yes Microsoft continues to present them too however, if significant the update is pulled and yet Cura 3.5 is still being solicited as ready for prime time.

Your summation seems to fit and on many levels I agree. Use the printer’s FW as an example; when viewed on the printer it will indicate a stable versus being tested version giving you a choice. I suppose a similar tactic could be deployed with Cura too and “if” I opt to try the “yet to be confirmed stable” version then I am knowingly assuming the risk. Now going back to my being blunt; it is BS that I open Cura 3.4.1 and and presented a pop-up that says “better, reliable” Cura 3.5 only to find out that I was one of many that (because I trusted Ultimaker) was like flies to the light and clicked ok and installed it only to be greeted with a laundry list of obvious issues that cost me on many levels. With prints that often take days I can’t afford nor should I have to wonder if it will work. I for one would rather not be presented with cool widgets but rather a rock solid program that I can trust. Take the trust out of the equation and then everything is suspect. Will I blindly upgrade again; no chance in heck. Add to this; the fact that Ultimaker has not stopped the solicitation of Cura 3.5 stating we are sorry but it is not ready for prime time is concerning. I hope more then mere words can convey that the Ultimaker Team recognize what they did, assume responsibility, and evidence this by “fixing” the code to a level that makes clear that they care. Yes, Ultimaker is an open source environment with input and assistance from many however, Cura is the foundation as such “needs” to be dependable.The secondary programs i.e. plugins carry different weight; certainly bug free is the goal and yet these are often works in progress. Furthermore, if they fail to perform or at a level less than desirable they can be removed and the core interface; Cura remains. With Ultimaker defining themselves as the market standard and moving heavily into the business market as a company presenting Cura 3.5 as they did dumbfounds me. I might have expected this years ago when expectations were modest at best, 3D printing required never ending twisting and tweaking, and the products were not being marketed as out of the box ready. Today, this is what Ultimaker solicites; unbox it, plug it in, load filament, import and slice your project, and select start. Certainly I know very well that it is not this cut and dry and yet; When the core interface i.e. Cura is crap then sadly so is the hardware as they live and operate as a team.

The printer referenced below is an S5 Earlier I posted stating that we had successfully installed Cura 3.5 on 3 machines running Windows 10. We had no obvious issues; we could open our projects, manipulate the settings, slice, and save. However, when we went to print late yesterday we swapped the PLA color on Print Core 1 and noticed that the PVA on Print Core 2 was not seen even though it had not been touched since a print only hours before using Cura 3.4.1. It showed “no” material so I rebooted the printer and nothing changed so I unloaded the filament and reloaded it and then it was recognized. Figuring that we were ready to print we sliced the project in Cura 3.5 and sent it via network and nothing happened. Upon further investigation even though it gave the print via network option and not to USB Cura could not see the printer. This, even though the printer showed connected to the correct network when viewed on the printer’s touch screen. Ultimately resetting Cura Connect got the communication back online. These events should have been a grand warning. Then when the print process began I noticed that both Print Cores began glowing red and this remained throughout the Active Bed leveling and and maybe even into the actual print process. Regardless, when the print head went to the corner to extrude Prime Blob “nothing” extruded so I watched it and no material flowed while printing the perimeter outline; only several seconds into the print material began to flow. Now I need to make clear that we had only 30 minutes earlier; loaded both the PLA and PVA during which I always run several feet of material through the Print Cores so they were nice, clean, and flowing well. Since the print was effectively a failure I opted to watch it until it changed to PVA and again the print head went to the corner to extrude Prime Blob and “nothing” extruded so again I watched as it began to print; again many seconds into the print PVA material finally began to flow with the initial material being “brown” PVA as if it was cooked in the Print Core. I aborted the print, cleaned the build plate, and tried it again because I needed to see if an anomaly and again the Print Cores glowed red during the Active Leveling process however, a this time a very “minut” amount of material flowed during Prime Blob and this was as the build plate was lowering during the final phase; not enough material to create a small blob nor was any drug across the build plate. Then when it was time for PVA the Prime Blob was initiated and again, almost nothing flowed until the very end and again it was “brown”. It took several seconds of printing before it became clear. I have read within the Cura section of this forum that others are experiencing the same. Add to this; I went to open Cura 3.5 a few minutes ago and “nothing” happened. I tried several time and finally I rebooted the machine and tried again only to receive this message as shown in the attached picture. Needless to say; considering the investment in the printer only a few weeks ago and the fact that it is a business tool, this is beyond unacceptable. Having shared all of this; I just clicked on Cura 3.4.1 and it loaded with “no” issues, saw the printer, and appears to be ready to work. In my opinion; the Ultimaker Team “need” to take Cura 3.5 down and remove the pop-up that auto populates when you load an earlier version of Cura until the issues are resolved. The issues that I shared and as have been shared by many others are “extreme” and beyond unacceptable on any level and sadly these are not the only issues being experienced by many with Cura 3.5. Bugs are one thing and frankly expected. In my opinion; these are not bugs but rather the reflection of a product that was released without proper testing; on an extreme level. I mean not to be so blunt however, after thinking about this situation and reading all the comments “blunt” is needed. The shinning light; so to speak is the fact that while using Cura 3.4 and 3.4.1 we experienced some wonderful prints with the S5 however, “if” my out of the box experience had been associated with Cura 3.5 my feelings about the printer would not be good. I have experienced far too many crappy software releases with other 3D printers and this was a significant reason that I purchased into Ultimaker. I have “no” desire to be unknowingly a beta tester but rather I need consistency and the ability to “trust” the operation platform presented to me; period. ”Not Happy” Takes care

Bummer. You have already uninstalled and reinstalled Cura 3.5? If yes; please update this thread once you install 3.4.1 with your results. Thank you

Perfect!! Thank you

I was told next week; week of October 15th.

No.... there has to be something odd happening when loading that variable. I am far from the “go to person” however, I would; 1. Reset Cura connect try ... no change.... 2. Reinstall Cura 3.5 It not only should; but will work.

I am in the position as you. I registered for it online when the S5 arrived 4 weeks ago and I have not heard anything. In the meantime I ordered a spare glass build plate.

Agreed

We are not seeing an issue with layer view on the machines that we installed 3.5 on however, we are experiencing other issues. I wish I could help you.

Agreed and yet knowledge is power and with the caveat I answered the question. IMO; port forwarding for the camera has extremely low risk as it is not directly associated with the printers remote management UI so for all intensive purposes it is a one way street. Furthermore, I see no reason why Ultimaker does not allow password creation on the camera and the remote management UI; if for no other reason to insure that someone does not unintentionally disrupt and or change a print in progress.

I did a search and see no associated threads. 1. Is there a way to simply prime the Print Core; meaning can you simply command material to flow through them? 2. When cleaning a Print Core the process begins with a hot pull then cold pull; can you simply stop after the hot pull or do you have to continue through the cold pull too. Thank you

On a S5 We noticed something similar; both Print Cores has the red leds glowing throughout the active bed leveling and then there was no print blob and weak first PLA layer. Then when it was time for PVA it went to the corner and again no print blob and it took several several seconds into the print before anything extruded. We aborted the print and tried again and we saw a print blob the second time but it only began to extrude towards the very end when the bed lowers just before the head moves into print position. Very little material extruded and when the PVA extruded it is as brown as if cooked in the tip. Not good No such issue with Cura 3.4.1

The printer nor the application were designed to work out of your home network; this whether on your computer or phone. Read this thread;

Alright; I share the following with the caveat and understanding that "anytime" to create access to your network for outside no matter how secure you think it is one can "always" find the front door if they want to. Having shared this. We set up remote camera access expecting it be of great value however, because the camera is static and IMO oddly placed and does not move with the build plate about all you can discern is if the printer is printing. Yes it will show if there is a gross issue however, you can not see the quality of the print. With regards to the remote management; we have never used it however, I suspect that if we saw a gross print failure we could remotely abort the print. I certainly would not use it to start a print. Moving forward. There are two primary ways to access the printer. To be clear, the Ultimaker app such as the phone app will not work as it is not configurable. 1.Into Ultimaker Remote Management UI however, the camera is not visible through this UI. 2. Into and "only" into the camera; this is by far the least vulnerable situation. With this being said; yes you can VPN into your network and for many folks this their only option be cause they do not have a public IP. Google "whats my IP" if you do "not" have a public IP then your only reasonable choice is to access your printer via VPN. If you don't understand the difference Google it. The fundamental difference is whether you are being assigned an IP by your internet provider behind their firewall effectively a Private IP and your first NAT. If you have a Public and or Static IP then no VPN is required to access your printer and you assume "all" of the risk associated with opening your network door because as I said; "if" you can get in so can someone else. In any case; In my case I have static IP's however; my first layer of security is to use a DDNS provider such as "NO IP" but there are many. Effectively using this service allows you to convert your public IP to a name or whatever rather than the actual public IP address. By doing this it allows you to change at will, the primary access to your system. Here you go; The first this you need to do is MAC assignments within your router; this will effectively make the IP address of your printer static; even though the printer uses DHCP login it will check the MAC address first and since it has been assigned to an IP address it will always use this same IP address. Keep in mind that if you connect via WiFi and LAN you will have to do this twice as the MAC addresses are different for each. For all of the examples below I am going to assume that you use one or the other. The next thing you need to do within your router is port mapping and forwarding. For the camera "only" you need to port map 8080. You want to map this port because 8080 is a common port. Select a port number between 3000-9999 and map it to port 8080 and associate it with the MAC assigned IP address created above; for this example I will use external port 6000 = 8080 For the remote management UI you will need to port map 80. You want to map this port because 80 is a common port. Select a port number between 3000-9999 and map it to port 80 and associated with the MAC assigned IP address created above; for this example I will use external port 7000 = 80 Next; decide whether you are going to use a DDNS service; many are free. If yes then create an account and then decide what you want to call your external access name; akin to the name on your mailbox. For this example I will use "myultimaker". You will assign this name to your Public IP address that was found using "whats my IP" Once you have completed these steps using a DDNS service you will access your printer as follows For Camera "ONLY" Access myultimaker.ddns.net:6000/?action=stream For remote management services myultimaker.ddns.net:9095 "IF" you opt not to use a DDNS service then your access will be as follows For Camera "ONLY" Access http://(your public IP address):6000/?action=stream For the Remote Management Services UI http://(you public IP address):9095 I hope this gets you where you want to be.

Understood The fact that you took the time to read what was previously posted I willl gladly share the steps. Because of personal time constraints I am unable to do so until later in this day. I will update this thread.

Howdy Yes you can and rather than tell you how please use the search feature as I was encouraged to use when I first began participating within the forum. Then if you have additional questions I will be glad to help. The process is easy. This forum has a tremendous amount of information posted within.

Thank you for the suggestion; it’s a good idea to do so as it will mark all 3 FW updating options off the list with an outcome. Regardless, it does not change the fact that the printer when connected to the internet is unable to make you aware whether the FW is installed. To me this is odd as descrete data is being collected automatically by Ultimaker. I will share the results of the USB test.

Thank you for sharing the steps to your success. I am glad that you were able to get it to work.

We installed it on three Windows 10 machines; two desktop and I laptop and have been using it with no issues. We did not uninstall 3.4.1 but rather kept it as a fallback in case of as issue; thus far after numerous prints; no issues. As with previous versions you must allow it through the firewall as stated.

I am sorry that I was not clear. When I select “latest” FW it downloads and shows “installing firmware” and then it stays in the installing screen ... forever; LOL. I then have to turn it off and it will reboot and operate just fine. However, if I attempt the FW update again it does the same thing. I have tried this on both WiFi and LAN. In addition I have performed the returned original function and reset Cura function. For what it’s worth; when I initially brought the printer online it performed a FW update so I am beginning to wonder “if” because it appears to have the latest FW (5.0.19.20180622) that the system does not know how to deal with it. It remains my opinion that when in the FW area it should present if it’s the latest FW and if yes then offer a refresh option. As it is now to simply look at the screen there is no way of knowing whether the latest version or not. Thank you all