![]() We can sort of track down what settings were changed from the defaults, even though it doesn't save which default profiles were selected (only the custom profile and the unsaved setting changes). The purpose of this was to be able to debug when a user has a problem with their g-code. Like, 2.1 or so? It was one of the first things that I implemented for the Cura front-end. And many of us keep a close eye on the Cura Beta and Release threads.Ĭura has been able to import profile settings from g-code for a very long time. I know that Nallath regularly keeps up with the goings on here and Msuurmond sometimes too. Do the Cura developers read these forums or are they only for end-user support?įeel free to call upon to get my attention any time I love answering such questions. I also found the Save Project option and it works fine but I would like for the Import Profile feature to function or to be removed in favor of the Save Project. This feature is broken (for me at least) but I believe that it is intended to work as implemented. Cura 3.2.1 absolutely saves profile info at the bottom of the gcode and there's an option in the Settings->Manage Profiles screen called "Import" that allows the selection of a gcode file for the purpose of importing profile info. No disrespect intended but you are incorrect. In other words if you save in cura 3.0 can you read the project in cura 3.1? I think maybe it mostly works. I'm not sure if this carries across versions of Cura (I think it mostly works). That way I can go back later and see the settings. Therefore EVERY time I create a gcode file I also save the project. It saves all the settings and also it saves the position and scaling of every part and it saves the contents of the STL files such that when you load the project all the parts are there on the bed in the same position/orientation and with the same settings as when you saved the project. This is actually in some ways better than the old feature. Instead there is a new feature called "save project". I suspect this is what you were looking for. They don't write all the settings to the gcode file and they don't read settings from a gcode file. This also allowed the great feature "import profile from gcode" which allowed one to alter all the cura settings to the settings used to make a particular gcode file.Ĭura 2.X and 3.X don't do this. Cura 15.04.6 really worked well for me and allowed convenient profile updates and I would like to move over to 3.2.1.Ĭura 15.X used to have this wonderful feature where the last line in the file contained all the settings (meant to be read by a computer, not a human). Please let me know of additional documents, settings that would help. Funny thing is that no matter what I name my machine in my Work Cura, it writes to the gcode file as "prusa_i3". I've tried changing the printer to various names on the Work side to try to match to my home printer definition and have tried modifying the printer names in the gcode file to match but that didn't work either. ![]() ![]() 08:57:51,856 - DEBUG - : Attempting to import profile C:/Users/aolshove.xxx/Downloads/Mini_DC_DC_Converter_Box.gcode This is the log entry when I make the attempt: I create a gcode at home and then download it at work and use it to update the profile for further printing tasks while away from home. My original attempt was to import settings from my home Cura into my Work Cura (setup for the same printer that I manage via OctoPrint). This happens with any and all gcode files I attempt to import the profile from. The machine defined in profile C:/Users/aolshove.xxx/Downloads/Mini_DC_DC_Converter_Box.gcode doesn't match with your current machine, could not import it. When I save a GCode file to disk and then immediately attempt to import the profile settings from that same GCode file I had just created with the currently open session of Cura 3.2.1, I get this error consistently:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |