[FIXED] V5 Will Not Import FFF Printer Profile From V4

[wirlybird]

V5 wouldn't import a profile for one of my printers using the migration wizard.
I then tried to export the FFF from V4 and then import into V5 but I get a message "failed to import profile".

What is the issue?

[S3D-Jason]

Can you send the profile to our support team?
https://www.simplify3d.com/contact-us/

I bet they could give you some exact suggestions on the cause. I think the only 2 other times I saw others users on the forum report this problem it was due to something like an <extruder> or <temperatureController> tag in the auto-configure sections of the XML that was seemingly referencing a non-existent extruder/temperature controller. For example, the top of the file only defines a single extruder with the name "primary extruder", but then the auto-configure sections at the bottom of the XML said something like <extruder name="Extruder 2"> even thought there is no extruder with that name.

Another cause I saw recently was someone that has the <printExtruders> tag using a value that wasn't defined anywhere else in the file (the value for that tag should always match one of the <autoConfigureExtruders> sections).

[wirlybird]

I will send it.
This is a dual extruder printer. It is a QIDI X-Pro.

I have three profiles for it, and none will import.

[Instrumentation]

I think the only 2 other times I saw others users on the forum report this problem it was due to something like an <extruder> or <temperatureController> tag in the auto-configure sections of the XML that was seemingly referencing a non-existent extruder/temperature controller. For example, the top of the file only defines a single extruder with the name "primary extruder", but then the auto-configure sections at the bottom of the XML said something like <extruder name="Extruder 2"> even thought there is no extruder with that name.

Jason and Co.,

I also have an issue where a group of v4 printer profiles will not import.

Please consider the lack of robust error handling in the import as a serious bug, especially if something as common as removing an extruder in v4 can abort the v5 import process. V4 was perfectly happy to let you delete an extruder on a multi-extruder machine and ignore the orphaned reference to an extruder in the auto-configure menu. The attached .fff files illustrate this.

I loaded a dual-head profile into v4 and v5 and deleted an extruder in the same way in both. I exported both new profiles and compared them. The way that v5 handles that in the XML seems much more elegant, but it's a serious issue if v5 can't import the default behavior of v4.

I was looking forward to using the new profile management tools in v5 to help fix my profiles; now I'm not looking forward to editing a bunch of XML to clean up after v4.

[S3D-Jason]

Version 5.0.1 was just released with improved migration capabilities for handling a wider variety of V4 profiles. The profiles in this thread all import correctly for me now using this latest version. Thank you for submitting the files and helping us identify the issue!