Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to open any .stl files at all. #16249

Open
bsaddresss opened this issue Jul 22, 2023 · 28 comments · May be fixed by #19025
Open

Unable to open any .stl files at all. #16249

bsaddresss opened this issue Jul 22, 2023 · 28 comments · May be fixed by #19025
Labels
Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: Bug The code does not produce the intended behavior.

Comments

@bsaddresss
Copy link

Cura Version

5.4.0

Operating System

Mac Catalina

Printer

Cr-10S

Reproduction steps

Cura 5.4.0 beta and fresh installed 5.4.0 will not open any .stl files. I've tried at least 15 of them, and nothing ever appears on the virtual build-late. I've tried uninstalls, new installs, restarts, new .stl's from tinkercad, opening .stl's from inside cura, changing default app to Cura... all of the .stl's will still open on prusaslicer.

Actual results

No Stl will appear on the virtual print bed.

Expected results

stl should appear on print bed

Add your .zip and screenshots here ⬇️

na

@bsaddresss bsaddresss added Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior. labels Jul 22, 2023
@MariMakes
Copy link
Contributor

Hey @bsaddresss,

Welcome to the UltiMaker Cura Github 🚀
Thanks for your report 👍

Your issue sounds super frustrating 😖
It reminds me of a similar issue we received earlier this week.

Could it be that our STL reader plug-in is disabled by accident?
If you go to the marketplace, click on the gear, and scroll down until you see STL Reader, you should be able to Enable it again from there.
image

Can you let us know if that is your issue?
If that's not the case, just let us know we'll take another look. 👍

@MariMakes MariMakes added the Status: Needs Info Needs more information before action can be taken. label Jul 24, 2023
@bsaddresss
Copy link
Author

bsaddresss commented Jul 24, 2023 via email

@github-actions github-actions bot removed the Status: Needs Info Needs more information before action can be taken. label Jul 24, 2023
@dnbernier
Copy link

@bsaddresss
I have similar issue. I can get my STL's to load after I disable the USB Printing plug-in. Only downside is that printing via computer to usb will not work.

@MariMakes MariMakes added Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. and removed Status: Triage This ticket requires input from someone of the Cura team labels Aug 9, 2023
@MariMakes
Copy link
Contributor

I'll bring it up to the team to see what they can do to improve it.
Since the amounts of reports coming in on the topic is growing.

Fingers crossed 🤞

@MariMakes MariMakes pinned this issue Aug 10, 2023
@MariMakes
Copy link
Contributor

Quick update from our side 👋

This fix will probably help with with the plug-ins being disabled by accident.
Fix required plugins by nallath · Pull Request #891 · Ultimaker/Uranium
Move the required plugins list to before it's actually checked by nallath · Pull Request #16304 · Ultimaker/Cura

But they won't help with the workaround that requires you to disable the USB Printing plug-in, that still needs some more research.

@MariMakes
Copy link
Contributor

The Cura 5.5 Beta has been released 🎉 https://github.com/Ultimaker/Cura/releases/tag/5.5.0-beta.1

We are hoping it resolves some of the issues, but please let us know if that's not the case.

@darkblaze69
Copy link

This is still unsolved in 5.6.0. I wait 4 minutes fot stl to load. What it's doing?

@DJSnCa
Copy link

DJSnCa commented Mar 30, 2024

I've been experiencing the same issue on arch. running "cura --debug" doesn't seem to show anything other than attempting to read file along with attempting serial communication with a printer followed by changing baud rates

@krifpvlic
Copy link

I'm experiencing a long delay to load an STL file on Nobara linux as well. An observation: it seems to load only when USBPrinting.AutoDetectBaudJob.run finishes. Here's an excerpt of the --debug output before opening the stl. Before it's just checking all of the tty ports.

2024-04-09 23:16:20,709 - DEBUG - [JobQueueWorker [7]] USBPrinting.AutoDetectBaudJob.run [39]: Checking /dev/ttyS28 if baud rate 9600 works. Retry nr: 1. Wait timeout: 15
2024-04-09 23:16:20,709 - DEBUG - [JobQueueWorker [4]] USBPrinting.AutoDetectBaudJob.run [39]: Checking /dev/ttyS31 if baud rate 9600 works. Retry nr: 1. Wait timeout: 15
2024-04-09 23:16:20,709 - DEBUG - [JobQueueWorker [5]] USBPrinting.AutoDetectBaudJob.run [39]: Checking /dev/ttyS29 if baud rate 9600 works. Retry nr: 1. Wait timeout: 15
2024-04-09 23:16:20,709 - WARNING - [JobQueueWorker [7]] USBPrinting.AutoDetectBaudJob.run [45]: Unable to create serial connection to None with baud rate 9600
2024-04-09 23:16:20,710 - WARNING - [JobQueueWorker [4]] USBPrinting.AutoDetectBaudJob.run [45]: Unable to create serial connection to None with baud rate 9600
2024-04-09 23:16:20,710 - WARNING - [JobQueueWorker [5]] USBPrinting.AutoDetectBaudJob.run [45]: Unable to create serial connection to None with baud rate 9600
2024-04-09 23:16:35,719 - DEBUG - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [77]: Unable to find a working baudrate for None
2024-04-09 23:16:35,721 - DEBUG - [JobQueueWorker [3]] USBPrinting.AutoDetectBaudJob.run [77]: Unable to find a working baudrate for None
2024-04-09 23:16:35,721 - DEBUG - [JobQueueWorker [1]] cura.Machines.ContainerTree.run [174]: Started background loading of MachineNodes
2024-04-09 23:16:35,722 - DEBUG - [JobQueueWorker [6]] USBPrinting.AutoDetectBaudJob.run [77]: Unable to find a working baudrate for None
2024-04-09 23:16:35,722 - DEBUG - [JobQueueWorker [2]] USBPrinting.AutoDetectBaudJob.run [77]: Unable to find a working baudrate for None
2024-04-09 23:16:35,726 - DEBUG - [JobQueueWorker [0]] USBPrinting.AutoDetectBaudJob.run [77]: Unable to find a working baudrate for None
2024-04-09 23:16:35,727 - DEBUG - [JobQueueWorker [5]] USBPrinting.AutoDetectBaudJob.run [77]: Unable to find a working baudrate for None
2024-04-09 23:16:35,727 - DEBUG - [JobQueueWorker [7]] USBPrinting.AutoDetectBaudJob.run [77]: Unable to find a working baudrate for None
2024-04-09 23:16:35,727 - DEBUG - [JobQueueWorker [4]] USBPrinting.AutoDetectBaudJob.run [77]: Unable to find a working baudrate for None
2024-04-09 23:16:35,741 - DEBUG - [JobQueueWorker [3]] UM.Mesh.MeshData.calculateNormalsFromVertices [561]: Calculating normals took 0.00025010108947753906 seconds
2024-04-09 23:16:35,741 - DEBUG - [JobQueueWorker [3]] STLReader.STLReader._read [68]: Loaded a mesh with 10830 vertices
2024-04-09 23:16:35,745 - DEBUG - [JobQueueWorker [3]] UM.Mesh.MeshData.approximateConvexHull [505]: approximateConvexHull(target_count=1024) Calculating 3D convex hull took 0.0038175582885742188 seconds. 104 input vertices. 104 output vertices.
2024-04-09 23:16:35,750 - DEBUG - [JobQueueWorker [3]] UM.FileHandler.ReadFileJob.run [87]: Loading file took 0.0 seconds
2024-04-09 23:16:35,755 - DEBUG - [JobQueueWorker [3]] UM.Mesh.MeshData.approximateConvexHull [505]: approximateConvexHull(target_count=1024) Calculating 3D convex hull took 0.0045583248138427734 seconds. 104 input vertices. 104 output vertices.
2024-04-09 23:16:35,762 - DEBUG - [MainThread] UM.Operations.OperationStack.push [72]: <UM.Operations.AddSceneNodeOperation.AddSceneNodeOperation object at 0x7f4da3545810>, took 0ms
2024-04-09 23:16:35,766 - DEBUG - [MainThread] UM.Operations.OperationStack.push [72]: GroupedOp.(#=2) RotateOp.(node=<CuraSceneNode object: 'Rode Lav Mc t-shirt clip v4.stl'>,rot.=Q<0.0,0.0,0.0,w=4.0>) TranslateOp.(node=<CuraSceneNode object: 'Rode Lav Mc t-shirt clip v4.stl'>,trans.=<0.000,0.000,0.000>), took 1ms

These errors also pop up when the file is loaded but I'm not sure how related they are

QIODevice::peek (QNetworkReplyHttpImpl): device not open
"Could not convert argument 0 at"
	 "@file:///tmp/.mount_UltiMaFR894K/share/cura/resources/qml/Menus/RecentFilesMenu.qml:33"
"Could not convert argument 0 at"
	 "@file:///tmp/.mount_UltiMaFR894K/share/cura/resources/qml/Menus/RecentFilesMenu.qml:33"
"Could not convert argument 0 at"
	 "@file:///tmp/.mount_UltiMaFR894K/share/cura/resources/qml/Menus/RecentFilesMenu.qml:33"
"Could not convert argument 0 at"
	 "@file:///tmp/.mount_UltiMaFR894K/share/cura/resources/qml/Menus/RecentFilesMenu.qml:33"

@krifpvlic
Copy link

In the flatpak version of the app, I was able to edit the AutoDetectBaudJob.py file and commented out lines 55-76. This resolved the issue and might work as a temporary remediation for those who don't use the USB printing feature.

@gtollini
Copy link

gtollini commented May 4, 2024

I fixed this by disabling USB printing altogether (I've never had an USB printer to begin with).
To do that:

  • Go to the “Installed” tab of the Marketplace.
  • Scroll down to USB Printing and click "disable".
  • Restart Cura.

@gtollini gtollini linked a pull request May 6, 2024 that will close this issue
5 tasks
@gtollini
Copy link

gtollini commented May 6, 2024

I've made a PR with a fix that works for me. It would be interesting for you guys to test it on your machines and report if it works for you as well 😄. It's here.

As it turns out, it's not scanning each of our printers for USB. It's scanning each of our tty ports (in my case, 32) and trying to make a connection. It'll use a CPU core per port (in my case, 4), 15s per port, twice each. In my case, both in theory and in practice, this totaled 4 minutes between clicking "open" and the file actually opening.

For some reason unbeknownst to me, this was only enabled on Linux/MacOS. My fix was simply disabling it for everyone, and hopefully a dev with better understanding of the project can add a setting like "Auto Detect USB Printers" or something that we can toggle on or off.

@gtollini
Copy link

gtollini commented May 6, 2024

@BlondieGayMan

There's something odd there. In theory, my fix wouldn't have a difference on Windows users. All I did was switch a Platform.IsWindows() (which would be True for you) for a hardcoded True. Can you build from source from my branch and test it on your system?

It could also be an implementation failure on IsWindows(), I'll investigate it a bit.

Also, if you don't mind sharing this information, which version of Windows are you running?

@BlondieGayMan
Copy link

BlondieGayMan commented May 6, 2024

16Jan2025

I've deleted all my comments, including the response to your comment. LOL

The reason is because, now, all this is just moot. In September 2024, I removed that ugly, monster of a printer (Wanhao D9 MK2 400) from my Lab and bought 2,
Creality Ender 3 V3 Plus
printers.

At first, I thought that I'd use Cura once I figure out how to make it work with Klipper.
However, I started off with Creality Print 5 and after working through the differences, I've come to really like it.

So now, I don't use Cura at all. I did put the old printer in a back room, because I can't seem to sell it. Oh well. I thought, at some point, just for fun, I might do some mods to it to change the X/Y to the kind of rails that the Ender printers I bought, use.
Perhaps then it might work better. LOL

So that's why I just deleted all my comments in this thread.

@ronsmits
Copy link

I can confirm that this is still an issue with 5.7 on pop os, disabling the USB printing fixed it

@gtollini
Copy link

I don't have an USB printer to test this out, but I'd guess it would still take a long time to open files.
The code tests all tty ports for baud rate - independently of it connects, I think.

@kafufafu
Copy link

kafufafu commented Jun 5, 2024

Could this have had any relation with the following? #19186

@gtollini
Copy link

Could this have had any relation with the following? #19186

Yes, it's the same root cause.

@sneakythr0ws
Copy link

I have same issue. Model doesn't appear before USBPrinting.AutoDetectBaudJob finishes.
Disabling usb printing pliugin helped

@GregValiant
Copy link
Collaborator

GregValiant commented Jul 21, 2024

I keep seeing this thread at the top of the page. There may be some movement on this as it has come up in other threads.

USB Printing is enabled by default as some older UltiMaker printers require it. For everyone else, it's a non-maintained legacy feature that not many use (or should use).

The "won't load files on startup" problem seems to be a lot worse when a user has other USB devices plugged into their computer and those devices are configured as serial devices. Headphones and some other accessories are known issues as Cura keeps polling the device and sending "M105" and the device keeps sending back "What?" and that goes on and on.

I'm in favor of adding a setting to the Extensions menu that will either jump to USB Printing in the MarketPlace where the user could turn it on, or better, just be a switch that would toggle it on and off. It's installed, loaded, and enabled by default and I see no reason to have to go to a remote website to disable it or enable it. (#19373 )

@horga83
Copy link

horga83 commented Aug 5, 2024

Still broken under both X and Wayland on latest Arch and Cura 5.8.0 running under GNOME 46
USB printing disabled and Cura still unusable

@horga83
Copy link

horga83 commented Aug 5, 2024

My apologies this may have been a bad STL for those wanting to test it is this project.
https://www.thingiverse.com/thing:3842871/files
The smaller STL opens the larger one does not.

@nebomuk
Copy link

nebomuk commented Sep 16, 2024

I keep seeing this thread at the top of the page. There may be some movement on this as it has come up in other threads.

USB Printing is enabled by default as some older UltiMaker printers require it. For everyone else, it's a non-maintained legacy feature that not many use (or should use).

The "won't load files on startup" problem seems to be a lot worse when a user has other USB devices plugged into their computer and those devices are configured as serial devices. Headphones and some other accessories are known issues as Cura keeps polling the device and sending "M105" and the device keeps sending back "What?" and that goes on and on.

I'm in favor of adding a setting to the Extensions menu that will either jump to USB Printing in the MarketPlace where the user could turn it on, or better, just be a switch that would toggle it on and off. It's installed, loaded, and enabled by default and I see no reason to have to go to a remote website to disable it or enable it. (#19373 )

I can reproduce this issue exactly. Download the latest Cura.AppImage (on linux), plug in a USB headphone and it will take a few minutes to load the simplest stl files.
The cura log is full of entries regarding the USB printing plugin.
When I disable the USB printing plugin, .stl files just load just instantly.

@horga83
Copy link

horga83 commented Sep 16, 2024 via email

@GregValiant
Copy link
Collaborator

@horga83
I'm on a Windows 10 system.

There is something wonky about the larger of the models you posted. It's kind of big for most printers. This is in MS 3D Builder and Cura shows the same numbers:
image

In Cura, at a scale of 0.10% it is 22mm tall. That makes a lot more sense than 22 meters tall.
image

@GregValiant
Copy link
Collaborator

That was just the Z.
In reality (I'm not sure whose) the printer would need to be be 150m x Y100 x 30m (500ft x 325ft x 100ft). You could print a full size Boeing 747.

In regards to the orientation of that part - it's my printer and I can print however I want.
(The smaller part came in at a reasonable size so I didn't fool with it.)

@supertin
Copy link

supertin commented Jan 16, 2025

I just downloaded 5.9 on a cleanish (never had cura or anything 3D print related) install of Mint. Got this same issue of silently not loading the STL. The log was full of attempts to open non-existent serial ports over and over.
And wouldn't you know it... Disabling the USB printing plugin makes it load.

Now the problem. The SD card reader on my printer is terribly unreliable, so I have been using USB direct printing. So for me, disabling USB printing isn't going to be a real option. So I'm going to have to wedge myself into a space near enough to the printer to set up the job with the printer attached by the sounds of things. Not fun.

Also, how is this still an issue 18 months later? How many versions have passed by now with this bug present?

Edit: Turns out even with the printer connected, it still doesn't find the printer, so it still just doesn't load the model. Downloaded 4.13 because that works.

@dzek69
Copy link

dzek69 commented Jan 16, 2025

I'm on Garuda Linux right now, on version 5.9, both from AUR and AppImage I have the same issue.

Previously I was on KDE Neon and using AppImage 5.6 version it was all fine (I did not touch any default plugin settings)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

Successfully merging a pull request may close this issue.