Priddy

Unfortunately, it does not look to function on my end with the 4.11 Beta. I also didn't see anything in the logs that indicated an issue with it loading. I hope I'm missing something simple, because this is the only plugin I look forward to with each Cura release :P cura.log

If you only installed one of them, I'd go ahead and add the second one as well. They are meant to be paired together, so if only one is installed, you could potentially run into a number of issues, ranging from things like Er65s to motion controller errors. Other common causes are things such as: * Front fan being impacted by debris https://support.ultimaker.com/hc/en-us/articles/360011635039 * Partially clogged core https://support.ultimaker.com/hc/en-us/articles/360011620800 * Debris in the feeder https://support.ultimaker.com/hc/en-us/articles/360011652139-Clean-the-feeders-on-the-Ultimaker-S5 (I'd also recommend resetting the tension back to the middle notch) * Waterlogged PVA https://support.ultimaker.com/hc/en-us/articles/360012057799 * Changes to Cura profile settings (Speeds, temperatures, layer heights) If you continue to see errors after checking these, then I'd recommend opening a support ticket via: https://support.ultimaker.com/

Also recommended to grab the DxDiag logs as well, when submitting to GitHub: DirectX diagnostics (Windows only): Go to 'Start', in the search box type 'dxdiag' and hit enter. In the dxdiag dialog, click 'save all information' in the bottom right corner. https://support.ultimaker.com/hc/en-us/articles/360016538000-Saving-Ultimaker-Cura-logs

Not quite. This is the general release thread for Cura 4.9, not specifically for issues with Cura on Windows 7. You are welcome to keep discussing with others the issues you are seeing, but please be mindful that this thread is open to all Cura users, regardless of if they are using Windows, Mac, or Linux. The Cura developers recommend reporting issues on the GitHub for Cura, which allows them to get additional information from you and better help resolve issues: https://github.com/Ultimaker/Cura/issues

You're welcome! I hope that helps better narrow it down.

If you'd like, you should be able to get a recovery image for the UM3 from your local support. The process is pretty much identical to the S-Line in terms of the recovery procedure. There isn't a recovery image for the UM2+ series available. However, if you want to try a previous firmware for that model, you should be able to use an older version of Cura to update your printer since the versions are tied with the software: https://github.com/Ultimaker/Cura/tags It is worth noting, though, that the UM2+ firmware has not been updated since around early 2018 (Version 3.3). I hope that helps!

Recently Ultimaker has updated the support.ultimaker.com pages to add firmware recovery options that may help: S3 & S5 - https://support.ultimaker.com/hc/en-us/articles/360019088780-Firmware-recovery-procedure-for-the-Ultimaker-S3-and-the-Ultimaker-S5-mid-2020- UM2+ Connect: https://support.ultimaker.com/hc/en-us/articles/360017100080-Firmware-recovery-for-the-Ultimaker-2-Connect

If you unplug the flow sensor from the feeder, and disable the flow sensor under the Gear Icon-->Settings menu, does it allow you to start the print? https://ultimakernasupport.zendesk.com/hc/article_attachments/360049153871/Feeder3.JPG

Does moving the layer slider on the right hand side of the screen cause the preview to look normal again? If the issue happened because you no longer have the option to slice the file, then try going to the general preferences menu and enabling then disabling the autoslice option. That usually helps force it to let you slice manually again.

Yeah, the visual indicator on the screen will probably show it as empty. But the machine won't actively try to swap it unless the end of material gets detected by the sensor.

I believe the easiest option would be to pull a known good tag from an older spool of the same material. This would save a lot of the hassle from needing to respool anything. The tag is essentially used to help identify the material to ensure that whatever print you send over from Cura has the correct configuration. using the old NFC tag shouldn't cause any issues. While not related to this behavior, I'd also make sure that you are running 5.8.2 or newer, as it had a significant improvement on NFC registration in general.

Awesome, thank you! I can say that this is definitely the first thing I look for with each Cura update.

It may be a shot in the dark, but does setting "Support Stair Step Height" to 0mm look to help?

@ahoeben You are my hero right now and this is amazing. Thank you.

You may have some prints lined up in your Cura Connect print queue. To check this, navigate to the monitor tab in Cura and you should see an option to view your print jobs. Once the Cura Connect page opens, you should be able to click on the three dots on the print and abort/remove it from the queue. You can also do a full Cura Connect reset on the machine as well. This is found under System-->Maintenance. As a note, this will also remove your printer from its network group.

Hi, Ben, The PVA material is only compatible with the BB core. It was designed in a way to improve the result when using this material. There should have been one included with your machine.

I had the same issue on my end. Try deleting your Cura config folders from both your AppData/Local and AppData/Roaming directories. Ended up working for me. Note: Make sure you save any custom profiles you have before doing this.

Your welcome! I'm glad to hear you were able to get it working. For future reference, your machine logs can be dumped to USB via System -> Maintenance -> Diagnostics -> Dump logs to USB. This page has details on where the Cura logs will be located on your computer: https://github.com/Ultimaker/Cura#logging-issues Have a great weekend!

Sometimes the issue is due to mismatched settings between Cura and your machine. Try deleting your machine profile and adding it back in. This will be under Settings-->Printer-->Manage Printers. Once that is done you should be able to connect your machine again to confirm if the live stream is no available. If that doesn't work, try doing a Cura Connect Reset in the printer menu and/or hook it up via LAN to see if that changes anything.

Have you recently updated your firmware? It looks like one user found that updating to 4.3 resolved their connection issues with the app.

Hi Zephir, The printer will throw an error if nothing is plugged into either TEMP1 or TEMP3. If the error changes from "temp sensor" to "bed sensor" after switching the cables, then your temp sensor will need to be replaced. If you have a multimeter on hand, you can check the resistance of your temp sensor. It should read about 110Ω at room temperature.