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

Materials settings are not taken into account #872

Closed
murphy2712 opened this issue Jul 12, 2016 · 12 comments
Closed

Materials settings are not taken into account #872

murphy2712 opened this issue Jul 12, 2016 · 12 comments

Comments

@murphy2712
Copy link

murphy2712 commented Jul 12, 2016

I want to use the material profiles to set the hotend and bed temperatures (and eventually more) depending on the filament material I use.

I tried changing the values in Cura.app/.../materials/pla.cfg but when I select the material in Cura, the values don't change according to the file values.

[general]
version = 1
type = material
name = PLA

[settings]
material_print_temperature = 211
material_bed_temperature = 71

screenshot 2016-07-12 15 46 14

I also tried creating a new file for a new material (in Cura.app and tried in ~/.cura/profiles too) and while the new material shows in the Cura material list, selecting it does not update any values.

I'm using Cura 2.1.2 on OSX, with a custom Reprap profile based on fdmprinter.json.

@fieldOfView
Copy link
Collaborator

What printer do you use? For the UM2+ the materials in resources/materials are not used. Instead you have to edit the values in resources/profiles/ultimaker 2+

@murphy2712
Copy link
Author

I'm using a custom Reprap printer (SmartrapCore).
Any way to get those working on a non-UM machine?

@fieldOfView
Copy link
Collaborator

Hmm, for a normal reprap machine those materials should be at least somewhat functional.

Can you use profiles instead of materials for now? There has been an extensive overhaul of this in 2.2, but it will take us a bit longer to psuh out a 2.2 release.

@murphy2712
Copy link
Author

Yes that's what I'm doing in the meantime...

@Ghostkeeper
Copy link
Collaborator

Since this is fixed in 2.2 (as far as we know now) and we have a workaround for 2.1, I'll consider this one fixed 😉

@murphy2712
Copy link
Author

murphy2712 commented Jul 14, 2016

Is there a 2.2 beta build out there? Or should I build it myself to test?

@nallath
Copy link
Member

nallath commented Jul 15, 2016

There is no beta build out. We do have a system with nightlies, but those are not automatically published.

@Ghostkeeper
Copy link
Collaborator

@thopiekar has a public build of 2.2, but as far as I understood his is a bit old since his build environment broke a bit.

@thopiekar
Copy link
Contributor

@Ghostkeeper: Got here 2.2 build for Ubuntu here, but @murphy2712 is using OSX or is there something I overlooked?

@thopiekar
Copy link
Contributor

@murphy2712 If you are using Ubuntu then it is very simple to install my software packages with 2.2 aka built from [master].

@Ghostkeeper
Copy link
Collaborator

Ah right, just PPAs of course. Sorry.

@thopiekar
Copy link
Contributor

@Ghostkeeper No problem 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants