5 hours ago, ahoeben said:There's a test build that seems to fix this issue here:
https://github.com/Ultimaker/Cura/issues/11896#issuecomment-1114661108
Hello,
I downloaded this version and tried an 3-Hours-USB-Print. No errors! Perfect!
Only one thing: In the time of about 90% to 95% of printing the Windows-USB-disconnect and connect sound was about 10 times. First I thought - "shit - crash". But nothing else happened ???? What was this? There was no other USB-Device.
Before the update the USB-prints always crashed within 1 to 5 Minutes after start. And Cura most too.
Thank you!
- 1
Recommended Posts
Top Posters In This Topic
28
26
25
12
Popular Days
Apr 27
20
Apr 26
17
May 2
16
Apr 22
15
Top Posters In This Topic
ahoeben 28 posts
nallath 26 posts
GregValiant 25 posts
Lupus52 12 posts
Popular Days
Apr 27 2022
20 posts
Apr 26 2022
17 posts
May 2 2022
16 posts
Apr 22 2022
15 posts
Popular Posts
ahoeben
@Lupus52, it is a bit like Ultimaker is having a party, and everyone is invited. Your printer manufacturer is also giving a party, but they did not want to spend money on cake. So they tell their gues
fvrmr
Hi everybody, Today we release the Ultimaker Cura 5.0 beta. After multiple special beta releases to test the Arachne Engine, the new slicing Engine is finally here. This new engine uses va
ahoeben
Fixed that for you here: https://github.com/Ultimaker/Uranium/pull/811
Posted Images
ahoeben 2,023
There's a test build that seems to fix this issue here:
https://github.com/Ultimaker/Cura/issues/11896#issuecomment-1114661108
Link to post
Share on other sites
hdelien 0
I decided to try 5.0. I have a LulzBot Mini 2 printer, so I am coming from the LultBot Edition (LE) of Cura. Obviously, using the LE version, I am spoiled by the LulzBot dedicated predefined commands and having printer preconfigured, etc.
But, I forged ahead. My first attempt, I copied the Start and End G-Code changing things that appeared to be missing. But when I hit "slice" the program crashed. Sorry, didn't capture log. I believe that I left an undefined variable in the G-Code so it was "user error."
My second attempt went more smoothly. When I proceeded to print via USB, I was impressed to watch the printer wipe the nozzle, auto-level the bed, and proceed to start printing. So the modded G-Code worked!!! But 15 minutes or so into a 4.5 hour print, Cura crashed. Log attached. I did report the bug on Github.
I don't think the error was mine this time. You can read the log, but in essence there was an error converting a python object that was a float data type to a C++ object that was integer instance. It logged several pages of this error before giving up.
For the record, my system:
OS: Windows 10 Pro V10.0.19044 Build 19044
Processor: AMD Ryzen 7 3700X 8-Core Processor, 3600 Mhz, 8 Core(s), 16 Logical Processor(s)
Installed Physical Memory (RAM): 16.0 GB
...and I'm sorry to say Graphics Card: NVIDIA GeForce GT 710
Also, for the record, This is my first 3D printer and I've had it less that 2 months. So I'm probably considered a nube. I am a programmer, so I was comfortable editing the G-code. Maybe I can up my rank to "intermediate?"
Thanks for listening.
cura.log
Link to post
Share on other sites