Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Custom G-Code not saving properly Slic3r 0.9.6-dev #843

Closed
sunatdawn opened this Issue · 9 comments

5 participants

@sunatdawn

Brand new user here. Slic3r working quite well for me, but I have found that saving config settings and exporting config settings seems to work for everything except for the custom g-code entries. Always appears to save but if you reload the config all the previous custom entries I put in are gone. Default values are always restored. I tried updating the default from within Slic3r but this just results in creation of multiple new defaults.

I'm getting around it by just manually editing the configs I'm creating which works fine. Seems like a minor bug, or I'm missing something.

Machine is Win 7, 64 bit, i3 HP Pavilion g.

@duttonw
@thecrazy
@mesheldrake
Collaborator

@sunatdawn - Can you try setting the custom gcode to something very simple, like just "G21" and see if that saves and restores properly, to see if it's something in your desired gcode that's triggering the problem? You might also post the gcode that won't save here, so we can try to reproduce this.

@sunatdawn

Thanks!

Here is the cal data I'm trying to put into the custom G-code block:

G28 ; home all axes
M92 X62.5345 ; calibrate X
M92 Y62.2502 ; calibrate Y
M92 Z2387.0719 ; calibrate Z
M92 E569 ; calibrate E

I enter those values exactly as shown. I select save print settings on that tab and select the profile I am using. If I then close Slic3r and reopen again, then load that profile, this is what I get:

G28 ; home all axes
M92 X61.4134 ; calibrate X
M92 Y62.4876 ; calibrate Y
M92 Z2387.0719 ; calibrate Z
M92 E569 ; calibrate E

These are the original default settings. I've just checked and it appears if I export to a new name then it will keep those entries correct. And of course manually editing the files is an easy fix. For me it just seems like that save print setting button isn't working consistently. I probably never would have noticed it other than the fact that I'm calibrating a new machine and the values kept getting reset when I wasn't careful.

@mesheldrake
Collaborator

Could it be a file permissions issue? I noticed that if I set my printer config file to read only, and then try to save, Slic3r doesn't complain. It would be easy to miss that the config wasn't saved, since the Printer tab display switches to the General settings after hitting OK on the save dialog.

And saving a config with a new name would get around that by creating that config file as the current user.

Just a guess. (Doesn't account for why you would be able to edit the config files in a text editor.)

@sunatdawn

I hadn't tried that, so I just double checked. There are no file restrictions shown related to the configs. Just for the heck of it I ran Slic3r in Admin mode to see if that might make a difference. It unfortunately still exhibits the same error.

@mesheldrake
Collaborator

When I save changed settings for the printer tab to the "- default -" profile, I get a new file in the ~/.Slic3r/printer named "- default -.ini" that wasn't there initially. So really it's a new profile with that name, but the "- default -" option in the profile choice drop down box already has a persistent "- default -" option. So I see two "- default -" items in that drop down. Is that what you see? One of them has true, hard-coded Slic3r defaults. The other one has the saved options from my custom profile also named "- default -".

So is that the confusion? Two profiles: "true" default and custom default, both with the same name in the drop down box?

But I think the main fix here is what you've already said works, which is to save custom configs with new unique names.

@alexrj
Owner

@sunatdawn, what version are you using? 0.9.7?

I can't reproduce any of these issues, but I'm only testing on Windows XP.

@alexrj
Owner

Tracked in #1134

@alexrj alexrj closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.