DivingDuck
-
Posts
524 -
Joined
-
Last visited
-
Days Won
8
Content Type
Forums
Events
3D Prints
Posts posted by DivingDuck
-
-
Evtl. kannst du ja auch mal bei Gelegenheit deine Firmware Version überprüfen.
-
6 hours ago, zerspaner_gerd said:
Bei dein Beispiel code mit Z20 könnte es sehr gefährlich werden wenn das Modell höher ist als Z20,
Ich denke, er hat nur vergessen den G91 von darüber mit in den Code zu übernehmen.
-
G1 F4200 X-20 Y220Auf Position X-20Y220 absolut fahren.
G90 ;absolute mode G1 X-20 Y220 F4200 ; park printhead at x-20y220
-
Kannst du bitte mal das Cura Projekt abspeichern und den daraus erzeugten G-code in einer Zip-Datei hier ablegen?
Es ist nahezu unmöglich das, was du gemacht, gedacht gemacht zu haben oder nicht gemacht hast, nachzuvollziehen. Der ganze Thread zeichnet sich hauptsächlich dadurch aus, dass man immer nur vermuten kann, was gerade passiert.
Dies ist nicht böse gemeint, trägt aber ungemein dazu bei zu verstehen, warum was passiert:
- Im Cura Projekt kann man nachvollziehen, was Cura an Einstellungen über was auch immer benutzten Einstellungsmöglichkeiten in Cura selbst oder den benutzen Plugins macht. (z.B. das Thema start und Ende g-Code)
- Im G-Code kann man sehen, was genau an den Drucker gesendet wird.
(Ebenfalls wäre es sinnvoll zu wissen, ob du z.B. Octoprint benutzt, da man damit u.U. ebenfalls den "fertigen G-Code noch manipulieren kann ohne dass es einem vielleicht auf dem ersten Blick auffällt.)
Nun zu deinen zuvor angehängten G-code als Auszug (Zeilen 3309 bis 3350) :
;TIME_ELAPSED:110.960593 ;TYPE:CUSTOM ;added code by post processing ;script: ChangeFilamenti3Mega.py ;current layer: 2 M83 ; switch to relative E values for any needed retraction G1 F1500 E-15 G1 F300 Z1.8 ; move up a millimeter to get out of the way G1 F4200 X-20 Y20 G1 F300 Z15 ; too close to bed--move to at least 15mm M104 S195 ; standby temperature M300 S1318 P240 M300 S0 P120 M300 S1396 P120 M300 S1567 P120 M300 S0 P120 M300 S2093 P720 M300 S0 P180 G4 S60 ; Wait for Pause G1 F1500 E15 M300 S3000 P900 M300 S0 P300 M300 S1318 P240 M300 S0 P120 M300 S1396 P120 M300 S1567 P120 M300 S0 P120 M300 S2093 P720 M300 S0 P180 M109 S213 ; resume temperature G1 F4500 E-8 G1 F300 Z1.8 G1 F4200 X8 Y8 G1 F4500 E8 G1 F300 Z0.8 ; move back down to resume height G1 F9000 M82 ; switch back to absolute E values G92 E117.9794 ;LAYER:2 M204 S1000 M205 X8 Y8 ;TYPE:SKIRTZeile 3317:
G1 F4200 X-20 Y20
Zeile 3324:
G4 S60 ; Wait for Pause
Zeile 3341:
G1 F4200 X8 Y8
Dein G4 scheint nicht das zu machen was du möchtest, oder? BTW, bist du sicher, dass G4 der richtige Weg für einen Filamentwechsel ist? Ich würde hier eher einen anderen Gcode für einen 3D-Drucher unter Marlin erwarten (M600). Ich kenne mich jedoch nicht mit deinem Drucker aus, das sollte jemand, der den Drucker hat und besser kennt, beantworten können.
-
Glad to hear that you was able to install and run Octoprint on your Z83 Tiny PC.
-
Zeige nochmals deine jetzt aktuellen Ende-Gcode in der Druckereinstellung.
-
Quote
M205/M204 ist von Cura generiert, das sind die Befehle für der Ruck/Beschleunigungs Einstellung!
Jep. Es machte für mich jedoch nur wenig Sinn da die Jerk-Änderung nach dem Ende vom Druck aufgerufen wird.
-
Quote
So, please allow me to restate what you said to improve my understanding. The tiny PC copy of Octoprint connects to the LAN, and the 3D printer via USB.
Yes.
QuoteSo, that would also mean that I would have Octoprint running on my laptop (where the slicer is).
No, you use your laptop for slicing and connecting to the running instance at your mini-pc via LAN and web browser.
It is a bit tricky to set this up but it is possible to do if you don't want to use a Raspberry Pi (what I would suggest to do as this is how it works best. Try to find a used model 3).
Maybe a good point to look at for some ideas:
https://community.octoprint.org/t/setting-up-octoprint-on-windows/383
https://www.youtube.com/watch?v=10IZ1zE2GwwEdit:
I forgot one link that is also mentioned from the community: https://github.com/jneilliii/OctoPrint-WindowsInstaller
-
There are at least two ways to run Octoprint. One as a (Server-) program on a PC like in your little PC that is connected to the Printer via USB or LAN. The other way is to run Octoprint with a raspberry pi and connect this device to the printer via USB or LAN.
-
Mit Cura 5.7 bekomme ich Fehler beim Öffnen der .3mf datei, die dann zu einem Absturz in der Cura Engine führen...
Mit Cura 5.6 kann ich nach einem anfänglichen Slicing-Fehler das Projekt korrekt slicen, sehe jedoch die von dir gezeigten Fehler leider nicht. Versuche es mal probeweise mit einem anderen Slicer und öffne beim Cura Support eine Fehlermeldung.
-
Du hast dich wohl mit den G-Codes ein wenig vertan...
;TIME_ELAPSED:493.475547 G1 F2400 E566.62624 M140 S0 M204 S4000 M205 X20 Y20 M107 G91 ;RelativMode G1 Z3 E-2 ;Fast-Einzug und anheben G90 ;AbsoluteMode G28 X0 F2400 ;ganz nach links G91 ;RelativMode G1 E-35 F100 ;Slow-Einzug G90 ;AbsoluteMode M104 S0 ;Hotend auf Null M140 S0 ;Bed auf Null G1 X-10 Y220 F2400 ;Bed nach vorne fahren M84 ;Motoren abschalten M82 ;absolute extrusion mode M104 S0M205 X20 Y20 ? https://reprap.org/wiki/G-code#M205:_Firmware_dependent
Du meintest wohl G1 oder G0
G1 X20 Y20 um auf Position X20Y20 zu positionieren, da du noch im absoluten Koordinatensystem befindest.
Edit:
Und wenig später Referenzierst du die X-Achse...
G28 X0 F2400 ;ganz nach links
Und dann noch ein wenig später fährst du die X-Achse in den negativen Bereich (und wahrscheinlich in den Endstopp) im absoluten Koordinatensystem...
G1 X-10 Y220 F2400 ;Bed nach vorne fahren
War das so angedacht?
-
11 hours ago, GregValiant said:
I've been burned too many times by the words "Never" and "Always".
I too, but I never had problems with Fusion360 and .stl export the last maybe 8 years The model I'm talking about was sliced / printed around 100 times since I create it. Sliced with different versions of Cura, different slicers and Fusion360 itself. The model is very basic with two holes and one of them include a hex nut profile on one side. I have big hope that it is watertight 😇
I don't know where the problem come from and I hadn't the time for digging deeper. My best guess is something changed in the beta as the older Cura versions do slice fine. Maybe the beta have a problem with project files of different printer profiles, but trying to proof this gave me a "some times working , sometimes not" experience. There is an indication from Cure itself that it has a problem with a setting but was not able to tell what setting prevent slicing. I saw this behavior sometimes with 2 other models as well. Running Cura w/o plugins didn't help either.
Today I changed accidentally the build plate adhesion from none to skirt and the model surprisingly slices again. It wasn't that specific setting. It doesn't matter what setting I choose, changing any setting makes Cura able to slice the model - well, up to until CuraEngine crashes again. It looks like Cura loses at some point some setting information (only a guess) and after changing a setting it is able to access all needed parameters again.
At this point I am not able to do more. It is now up to the development team to investigate further.
Regarding effort of the Cura team, I recognize this as well. The development team try to work down the issue backlog and I'm happy for this.
This is a beta and I expect to see some problems as this is the nature of a beta test. I'm fine with this. It is, why I spend some of my time with testing the beta and reporting my findings (without being upset).
-
Thanks @ahoeben. I forgot to turn off this plugin in my test.
Unfortunately after turning off MeshTools I still have the error with settings that prevent slicing. Looking in the log it shows - well, the most important information is missed.
Infill.log 2024-03-22 09:16:59,488 - INFO - [MainThread] CuraEngineBackend.CuraEngineBackend.slice [348]: Starting to slice... 2024-03-22 09:16:59,489 - DEBUG - [MainThread] CuraEngineBackend.CuraEngineBackend.slice [368]: Going to slice build plate [0]! 2024-03-22 09:17:00,391 - WARNING - [MainThread] CuraEngineBackend.CuraEngineBackend._onStartSliceCompleted [499]: Unable to slice with the current settings. The following settings have errors:I made yesterday evening an additional observation. The bracket I show in my last post concerns me a bit, so I thought give it a try once more and send it directly from Fusion360 to Cura. It slices while sending it as 3mf file, but sending it as stl cause the slicing error again. wired. The next test was to export the model as 3mf and stl file to the desktop and then add them to Cura. both time it fails again.
Now I have all kind of scenarios for one part.
- Using an old project version as 3mf is crashing the Cura Engine.
- Using an old stl will not slice because of an unknown, possible wrong setting
- Exporting the model in Fusion 360 as 3mf and let it open in Cura slices the model
- Exporting the model in Fusion 360 as stl and let it open in Cura do not slice because of an unknown, possible wrong setting
- Exporting the model in Fusion 360 as stl and 3mf file to desktop and then put them via drag n drop into Cura do not slice because of an unknown, possible wrong setting for each file
- Changing the printer profile to an other printer while the not slicing model is on the build plate causes Cura Engine first to slice and then to crash and calling the debugger.
The part itself is a simple part that is solid, so no chance to have a not watertight model at all.
So fare my observations for this build.
-
I did some tests beginning the week and was often annoyed about "not watertight" models. They are since years as I print them quite often in the past (most of them was CAD models from Fusion360).
Then I thought us one of the most printed models: The 3DBenchy. Guess, what happen...
Shouldn't at least the 3DBenchy slice w/o errors? Regarding errors, pls. see the the error description shown in the picture, it's speechless as well 😉
I had also some crashes during slicing that was reported automatically, so they should be available.
Cura then is in a slicing loop that you can only break with closing Cura. The part itself is ok.
Two or three plugins wasn't working, but that was expected (I did report them to the plugin owner).
Looking forward for the next release. 🙂
I attached the log file. Please let me know if anything else is needed.
-
You can setup Windows opening a specific program / app associated with an file extension. This is a standard behavior Windows do since so long time that I even not remember since when. 🙂
Simply right-click with your mouse any .stl file in the windows explorer and then choose -->"open with" and select the app you like. Choose -->"More apps" / -->"Look for another app on this PC" in case it isn't listed. It will become a default behavior if you activate -->"always use this app to open ... files" check box.
Beside of that I as well do not recommend it as you will limit you to a specific app. Most of us do not use only one version of Cura. I for example use 5 different slicers and this sometimes in different versions. Another for me important point is that it takes quite a time to open Cura and every time you click a wrong file you need to wait until Cura is ready to do its magic...
In addition I would suggest using a thumbnail program for viewing .stl thumbnails in windows explorer. My choice is Papas Best since it was available first time. It is a lightweight application, fast and, more important, it is w/o any kind of bloatware or calling home stuff. There are two programs, one is the thumbnail app and the other is a lightweight viewer that is incredible fast. It becomes very handy for quick look of 3D .stl files. Use this as default app for stl files and you can view such files comfortable within your explorer before you drag and drop it to a slicer of your choice for printing.
-
Lol, Handauflegen aus der Ferne funktioniert also noch... 😄
Kleiner Tip: Wenn mal was nicht richtig in Cura funktioniert, drehe alle Änderungen zurück auf Anfang. Ich habe in den unzähligen Jahren mit Cura die Erfahrung gemacht, dass man mit dem Standard Profil bei einem neuen Projekt meist den besten Start hinlegt und dann nur die Einstellungen verändert, die das aktuelle Projekt betreffen. Das spart einem meist viel Zeit, Verdruss und Filament.
-
This isn't a setting that you can change within Cura. You need to start your research on the fdmprinter profile in the definitions profile and then you can check how the Ultimaker profiles use it. That's the normal way to explore the varius setting variables. Some of those are hardware related to Ultimaker printers only as they need a firmware understanding those variables.
Beside of this there is a plugin called Printer Settings from fieldOfView where you can edit a lot of printer settings as the one you are looking for.
Use this plugin wise as it is easy to destroy configurations if you don't know what you are doing. A backup of your configuration folder as first action should be obvious.
It is maybe also a good advice to install the plugin Settings Guide from Ghostkeeper. It provides you with a lot of useful knowledge that you won't find in any Ultimaker documentation. Sadly it is not longer at state at the latest versions as there is no one who want to take over the project at Ultimaker. It's a pity but so is life in the real world.
Both plugins can be found at Marketplace.
-
It is maybe worth to check your log file.
Usually you should not get this kind of errors. Last time I remember those errors, it was in combination with a material definition file where the definition chain that was somehow broken in a Cura config file set. It took me a while to identify and solve the problem. The log file in the end pointed me to the right place to look at.
Regarding different versions of config files. You should always go in versions upwards as this will (mostly) take care that your profiles will update correctly when you install and run a newer Cura version. The other way around asks for problems as here is no "downgrading" procedure in Cura. Copy the lastest working configuration set (or all versions, if you want to install older Cura versions later) to the new computer and rename/delete the actual 5.6 set. Cura should then transform the latest version found in the config folder to the actual version when you start a newer Cura version.
-
For Cura Engine plugins is only less information available. There was a little introduction when Cura 5.5 was introduce and there is a little bit available when you look at Github.
https://github.com/Ultimaker/Cura/discussions/15629
https://github.com/orgs/Ultimaker/repositories?q=curaEngin_plugin
-
Rein aus Interesse, verrätst du uns auch warum es bei dir am Anfang nicht funktioniert hatte?
-
There is one in addition for future development:
Printing one at a time should not be restricted to the use of one extruder in printer definition. I had forgot about this already and it is still irritating me - because when I forgot to switch the printer profile I search all the time the not longer visible setting for printing one at a time.
-
1
-
-
Yea, I hope for both. And in addition I would like having the possibility to tell Cura a specific order of print and/or rearrange the models if needed. How was that with giving a little finger...? So many ways things to manipulate. 🙂
-
1
-
-
47 minutes ago, a7abw said:
Thanks DD, but that file has a .1 after cura.log.1 Not sure if this can cause some issues.
Guess you tried to zip the log file and somehow the file extension was overwritten with .1
16 minutes ago, a7abw said:However, none of my previously saved profiles are there - is it possible to retrieve them from the cura.test folder?
Yes, you can copy the profiles from your renamed folder. and look if Cura will start. If Cura wont start after copying the files you can delete them again and add a new printer profile as you did that the first time using Cura.
Up to this point we now already that Cura will start again if you remove the old configuration folder. This is already progress. +1
When you try to copy the old configuration please do not copy the plugin folder. This way you can check if the problem came from an older plugin version.
-
1
-
-
Make a backup of all the %APPDATA%\cura\x.x\ folders and then delete all of the x.x folders. This sometimes helps to get Cura to the point initializing itself w/o trying to integrate former configuration files. Maybe it help you too. You can then try later adding the old configurations back from your backup and check where the problem came from.
Regarding not able to attach the log file. Make a zip file from the log file and attach the zip. This should work.
syntax for {nozzle_disallowed_areas}?
in UltiMaker Cura
Posted
Maybe as additional explanation to @Slashee_the_Cow,
The definition of disallowed areas starts from the center of the bed as origin and is defined by an polygon with x/y coordinates of 4 point's: [[x,y],[x,y],[x,y],[x,y]].
There are two types of disallowed areas available: nozzle_disallowed_areas and machine_disallowed_areas.