I’ve had an X1C for a while and had no trouble importing manufacturers profiles for filaments which are ones that aren’t directly support by Bambu Lab. I’ve done that by Import Configs and point to the JSON file for the filament.
Now with a H2D they all show up as “Unsupported”. I’ve tried choosing them again with the H2D chosen as my current printer but they still show up as “Unsupported”. I know it’s possible to craft a Custom Filament based off of an existing generic or other supported filament but I’d rather have it show up as the filament manufacturer intended.
How can I make this work?
1 Like
I don’t have an H2D so I can’t try this, not sure if it answers your issue or not.
There is an embedded video where someone is re-adding device, I had to go full screen to actually see details.
Edit: not sure if custom is the same as 3rd party
I saw that one. What the person suggested didn’t work for me.
ok, maybe the 3rd party vs custom, since odds are you already have the H2D when you make the custom. I’m wondering if the 3rd party issue is related to the dual nozzles? It’s been a while since I looked at them but I seem to remember the json files for h2d being different than the ones for the A, P & X series.
What version of B Studio are you using and what is the filament brand/type? I’m thinking I might try pulling the config off their site and do some testing when I get a chance.
I’m using Bambu Studio 2.2.2.56 on Windows 11 Pro.
Here is where you can find some of the filament manufacturers profiles I had success with on my X1C but don’t show up on the H2D:
Fillamentum:
scroll down until you see “Profiles for Bambu Lab”
Fiberlogy:
scroll down until you see “Profiles Bambu Lab X1C”
Seems like maybe these profiles were made for the X1C and don’t specify the H2D in the JSON file. If this is the problem, how do you edit the file to add to H2D and so you can see how it works?
1 Like
I use notepad ++ to edit (copies) of the json files. I run the slicer in a seperate test vm and make copies of all the directory so when I mess things up (and I do) usually I can just copy things back, and maybe reboot the pc. I don’t have an H2D but the slicer won’t know that for the prep part if I tell it I do.
I am helping someone move right now so it may be a couple of days before I can sit down and spend time on this (probably while I waiting for my knee to recover).
I have the same issue with some IIIDMax filament. There’s a .json file, it’s been working forever on my X1C, but the H2D lists it as unsupported.
Did we ever find a solution to this?
Haven’t tried loading a 3rd party filament via json so don’t know if anything is fixed. I ended up doing what others recommended and copied all the filament details from the X1C (did screen shots) and manually made a new user created custom for the H2D. At least it gives you a starting point maybe a little different from the generic profiles.
One thing to keep in mind is that a lot (maybe all at this point) of the 3rd party profiles are for single nozzle printers.The files for the H2D have additional entries because of the dual nozzles and it appears that if they aren’t there the printer won’t use them. If there is a generic or Bambu for that filament material, try that. If that doesn’t work or isn’t close enough then you will need to make a custom profile. I am no expert so there are probably other ways to get there.
Edit: maybe an option/setting to “emulate” a single nozzle printer and default to only the Left (my random choice) nozzle is a thought but I don’t know if adding that is even possible.
1 Like
I’ve emailed IIIDMax to see if they have one for the H2D, will update when I get a response.
1 Like
From IIIDMax regarding their PLA+ material:
You can use the Bambu Basic PLA configuration and turn down the volumetric speed a bit: 25->23
Even though if you leave it as it is, it will work fine.
Or you can use the Generic PLA High Speed and change the volumetric speed from 18 to 23.
1 Like
I have exactly the same problem with the H2S which arrived today.
I can select any of the included profiles happily but though my custom profiles, dozens of them as a resyult of extensive tuning with Orca and X1C/P1S, show in the slicer they show as “Unspported” and cannot be selected.
If I take an existing stock profile and copy all the settings from one of my custom profiles I can save it as a new profile and it becomes selectable.
That is a TON of work to do for all my custom profiles.
Surely this is not the way it’s supposed to be?
We are being scolded and taught a lesson for not buying 1st party filaments.
2 Likes
And yet I can create a new profile for one of these filaments and it’s fine. Just pre-existing ones don’t work.
Your pre-existing ones were created for a single nozzle device, and the H2S is a dual nozzle. That is the root of the issue from what I can tell. There are parameters in the dual nozzle files that do not exist in the single. When you create a new one those parameters are included.
No. The H2S is a single nozzle device. That’s what the S stands for.
Oops, yes I was thinking of the H2D, where this issue has popped up before. I’ll have to look at the files for the H2S.
Thanks
Yes. However I do now know the real root of the issue…
I don’t know if it existed in earlier versions of the slicer, but the filament profile now has a tab called “Dependencies”. I do not believe it existed before.
**** Orca Only, not BS. But profiles set in Orca as described below will be available in BS. As usual, Orca is ahead of the BS slicer ****
When I created a filament profile it would become available on my P1S and X1C machines.
If I set the printer as one of those machines, all my profiles are available under the Custom dropdown.
Choose the one I want on the H2S and edit it, go to Dependencies and choose “Set” under “Compatible Printers”.
A list of all your printers comes up and you will see any previous printers you had are ticked (this is why I think it didn’t exist before - it applied to all printers).
You can now tick all the printers you want it to apply to in my case the four H2S nozzle sizes.
Ok and save the profile.
I assume this has been introduced for a couple of reasons:
First, you can untick Carbon filaments on any 0.2mm nozzle machines (for example - could be anything that is not recommended with a particular nozzle)
Second, if you have a machine with a high flow nozzle and another without, you can make the high flow profile only visible on the machine that can handle it
(There was another reason I thought of that has slipped my mind as I type).
You might think they would have enabled profiles for all your machines by default and this issue would never have occurred but my guwess is they decided not to because that makes you deliberately choose which machines you can use carbon fibre or glass-filled filaments in; and also if your printers don’t behave in the same way with a filament you can restrict the settings to different machines.
When I had a P1P, for example, shrinkage was greater than on my X1 so if this Dependencies tab had been there, I could have two profiles for a filament, with different shrinkage set, and only allow each to be seen by the relevant printer.
In the past I created the two profiles and I named them with " - P1P" or " - X1C" at the end of the name. I would still need two profiles now but it can be made more obvious why they are different : call them " - LowShrink" and " - HighShrink" for example.
TLDR - I can simply run through the list in the filament profile editor and select H2S in the dependencies for each profile, or if I’m not bothered making CF filaments unavailable to 0.2mm nozzles, just tick the “All” box and save
Glad you seem to have figured it out. I was testing in bambu studio and managed to get my 3rd party Americam Filaments preset for P1S to show under custom for H2S after doing some tweaks but I don’t have that printer and have no idea how they would actually print.
I did compare some files and the Bambu PLA base json for X1C is about 25 lines and for the H2S its about 130. And creating and comparing customs the H2s json is still about 20 lines longer and includes a few settings for things related to “counter_coef…” and maybe a few others.