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

[4.2] Profile import fails from single to dual extruder machines or inverse #6083

Closed
Liger0 opened this issue Jul 30, 2019 · 9 comments
Closed
Labels
Status: Won't Fix/Do Not an issue, or an issue that we cannot fix or can live with. Type: Bug The code does not produce the intended behavior.

Comments

@Liger0
Copy link

Liger0 commented Jul 30, 2019

Application version
4.2

Platform
Win 10 x64

Printer
Single to dual OR dual to single extrusion machines (creality cr-10S as single extrusion, custom or creality cr-10X as dual extruder)

Reproduction steps
Create a profile on a Creality cr-10S single extrusion machines and import it on a dual extrusion machine.
OR
Create a profile on a double extrusion machine and import it on a single extrusion machine.

Actual results

The machine defined in profile D:/Profile.curaprofile (fdmprinter) doesn't match with your current machine (creality_base), could not import it.

Expected results
It should import successfully

Additional information

@Liger0 Liger0 added the Type: Bug The code does not produce the intended behavior. label Jul 30, 2019
@nallath
Copy link
Member

nallath commented Jul 31, 2019

This has never been possible (mostly because there has been little need for it. It's a bit tricky to do it, since in the +1 extruder case, you simply don't have settings for the second extruder (and might get some unexpected results if you have another material selected for that extruder than the first one)

@Liger0
Copy link
Author

Liger0 commented Jul 31, 2019

It worked correctly on previous cura releases. I could import a cr-10s profile into a custom dual extrusion and vice-versa.

@nallath
Copy link
Member

nallath commented Jul 31, 2019

I stand corrected then. I was under the impression that this simply wouldn't work. The upgrader script does seem to be able to handle it.

@Liger0
Copy link
Author

Liger0 commented Jul 31, 2019

Just to give the profiles to test directly.

Use custom dual extrusion machine (or a creality cr-X) and import my single extrusion profile crated with 4.2:

The machine defined in profile D:/Files/(4.2 CR10s) PLA 0.4mm 0.12LH.curaprofile (creality_base)
doesn't match with your current machine (fdmprinter), could not import it.

(4.2 CR10s) PLA 0.4mm 0.12LH.zip

Or

Use creality cr-10S and import my dual extrusion profile created on 4.1

The machine defined in profile D:/Files/PLA 0.4mm + PLA 0.5mm 0.16LH brass.curaprofile (fdmprinter) doesn't match with your current machine (creality_base), could not import it.

PLA 0.4mm + PVA 0.5mm 0.16LH brass.zip

@Ghostkeeper
Copy link
Collaborator

It seems we had forgotten one printer in the list for upgrading instance profiles, the CR10s. Fixed for 4.2.1.

@Ghostkeeper
Copy link
Collaborator

Ah, sorry. This ticket was not fixed. You still can't import these single-extrusion profiles into a dual extrusion printer because the base printer is not the same. We only allow that if the profile set is the same. That part is working as intended so we won't need to fix that.

What was fixed was importing into the CR10s in general.

@Ghostkeeper Ghostkeeper added the Status: Won't Fix/Do Not an issue, or an issue that we cannot fix or can live with. label Aug 1, 2019
@Liger0
Copy link
Author

Liger0 commented Aug 1, 2019

Is this again a creawsome implementation fault? Since it worked before. :(

@Liger0
Copy link
Author

Liger0 commented Aug 1, 2019

Ah, sorry. This ticket was not fixed. You still can't import these single-extrusion profiles into a dual extrusion printer because the base printer is not the same. We only allow that if the profile set is the same. That part is working as intended so we won't need to fix that.

What was fixed was importing into the CR10s in genera

I tried to import a cr10s profile into a custom single estrusion printer and it still doesn't work on 4.2.1 because of the different machine :(

Edit: on 4.2.1 the profile import doesn't work at all.
I tried to import a cr10s profile into its own machine, and even tho it says "profile successfully imported", it actually isn't imported at all!

@DuckersMcQuack
Copy link

It seems we had forgotten one printer in the list for upgrading instance profiles, the CR10s. Fixed for 4.2.1.

Nope, i use 4.2.1 now, it's not able to import a 4.0.0 gcode as profile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Won't Fix/Do Not an issue, or an issue that we cannot fix or can live with. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

4 participants