Open mtwomey opened 5 months ago
Could you upload the log of the machine and Studio? We need that to target the issue.
Same here. Project doesn't seem to matter. macOS 14.1.2, BS Beta 1.8.1.57, BL X1C 1.0.7.00.00, AMS 00.00.06.40
I do have the same issue here. Beta 3 of the slicer and last firmware on the machine.
I cannot upload here the log as they are too big of a file now.
My studio logs were also huge, so I cleared them out and restarted studio and recreated the issue. It doesn't produce any logs - I think that is because I literally just open studio and select the filament and it happens. There is no project started and nothing done anywhere at all. I am getting the x1c logs for you though.
How should I send you the machine logs? They are 385mb.
Having same issue with the newest firmware and Bambu Studio Beta. debug_Tue_Dec_12_13_25_36_17784.log.zip
Can't up load machine log file, to big. (376 MB)
Okay, thank you for your log. I understand now. Will be fixed on the printer firmware.
will the custom filament be selected displayed in AMS later? or just be "?" forever.
For my part, it stays with the correct custom name and colour for 10 seconds or so and then goes back to "?". I managed to rapidly click on the "prepare" tab of the slicer and I can see the correct custom filament in the filament list of the machine. However, after 10sec on this tab or the device tab, it reverts back to ?
@DanBao-Bambu I know that it's two separate departments (software, firmware) but... can you ask the firmware department when a new firmware will be released to fix this issue?
Same here. The only chance to select a custom filament is to do so directly from the printer screen.
@man55 Weird. I couldn't even do that, until I did a firmware reset on the printer just now. Interesting... But at least now I can select a custom filament.
Yesterday I managed to add two filaments. Moreover, one was successfully added from the Studio. The second one was installed only through the printer screen, but the main thing is that the Studio was able to send it there. But today I can't do anything. I create filament, but it doesn't even appear on the printer screen.
I have no AMS but I can tell your that Custom filaments (with the factor K in their PA profile) created in latest Bambu Studio (1.8.2.56) do not appear on the screen of my X1-Carbon (latest FW 01.07.00.00) even after power cycling.
Moreover, when a Custom filament is selected in Bambu Studio in the Device tab, going back to the Preview tab to Print plate from there, Bambu Studio automatically switches again to the Device tab where the custom filament is no longer selected, only the "?" appears with no color, and the custom filament cannot be selected again manually as the print is currently processing.
Before clicking "Print plate":
After clicking "Print plate":
BTW weird enough, the K factor still remains for the default filament despite no manufacturer and no plastic type have been selected???
I can confirm this bug.
I have to confirm this bug too, @DanBao-Bambu any chance that the firmware department will create a hotfix for this an time soon? I mean, the custom filament feature introduced in 1.0.7.00.00 is simply not usable in this state. I (but i guess we all) would appreciate any further Information on this.
Same shit I got. T_T
This bug propagates even further! When the print job has been sent from BambuStudio with a Custom Filament selected from there, to the X1C where that Custom filament does not appear, the object correctly prints nonetheless (I don't know however if the correct K-factor is applied). But once the print has finished and "Print again" (from the cache) is selected from the touchscreen, the X1C now produces this error:
Notice in the screenshot how the printer does not seem to know the existence of that white PLA being selected in the upper right corner!
But as the Custom filament is not detected from the X1C I have to cancel completely and can't easily print several times the same object from the printer anymore. I have to go back to BambuStudio and print from the computer by uploading the same file again and again to the Bambu cloud. — EDIT: Not entirely true, as clicking "Yes" in the screenshot above, the error is bypassed and the print job begins. But this is quite annoying and prone to further errors.
[note:- cross posted as well to the other thread as mixed responses] |This is very strange, as I cannot replicate the fault, in full cloud only mode. I have now created multiple new custom filaments., as primary and apepar on device tab and printer Even creating a preset and then calibrating that preset (instead of the master) and then those also appear on the printer (k prorfile etc)
Studio version- Custom Filament setup
Studio - Device Tab - Test filament in Dropdown Studio - Device Tab - Calibration available and it stays there (Test TPU on external spool) - Device TAB\AMS section
And on Printer with calibrations...
Happy to try and help if I can..
I also have this problem, but for now it seems it happens when adding an existing brand. I have tried to add eSUN PETG and SUNLU PETG, both will not show on the printer. When I added an non existing brand(non existing in Bambu Studio): REAL ABS, it showed up on the printer.
edit, forgot to mention, my printer is cloud connected.
There seem to be two situations that can cause the Filament option on the printer screen to be displayed as "?". One is when connecting to a printer in the cloud, and the other is when connecting to a printer through a LAN. We are aware of the issue of "?" appearing on the printer screen when connecting to the printer in LAN mode. Another option is to see the custom Filament on the printer and select it, which will then change to "?" during cloud connected printing, right? @mtwomey @marnovo @tokamac @thesainthell @ Please confirm that if there is a "?" issue with the cloud connected printer, the printer's log is indeed required as I know it is quite large, so you can use the "Google Drive" cloud service to upload the log and share it with me for connection. This is very important to me, thank you.
@DanBao-Bambu Thanks for coming by. Here is my Log-File. Hopefully this will help to figure out the cause of this issue.
Here are some more information of my very last experience: Today I was able to assign an non existing vendor (Extrudr PLA) config to an AMS Slot (3) while an non Bambu profile (Eryone PETG CF) was also successfully loaded in an other AMS Slot (4). This situation worked until I changed the non Bambu Profile of Slot 4 to an other non existing vendor (Extrudr PETG) profile. Since then, I wasn't able to get it back working.
After conducting my own testing and communicating with the firmware department, I have confirmed the following issues: When Studio connects through the cloud, creating a new Filament and selecting it on the Device page of Studio does indeed result in a "?" after a period of time. The reason is that the printer screen has not received any update events or information about creating new materials, resulting in this situation. The current solution is to create the Filament, go to the Materials tab on the screen, click to enter the slot setting interface of AMS, and the Filament information on the screen will be obtained from the cloud again. Afterwards, Studio can be used for AMS Filament selection.
@KRiZ-R The problem you described seems different from others. When you create Filaments for eSUN and SUNLU, and enter the Filaments page of the printer screen to edit the Filaments, do you not have the Filaments you created under these two vendors? This may be because after creating a custom Filament in Studio, the cloud did not synchronize in a timely manner. You can exit the editing page and re-enter it. If it still doesn't work, make sure your "Auto sync user presets" option in Preferences is checked. If so, it may be a new bug. Can you send me your printer log and Studio log for analysis? thank you.
The current solution is to create the Filament, go to the Materials tab on the screen, click to enter the slot setting interface of AMS, and the Filament information on the screen will be obtained from the cloud again. Afterwards, Studio can be used for AMS Filament selection.
Can you make this more like a "step by step" guide? I've tried to reproduce this but without success. However, I cannot rule out the possibility that I simply did not understand your instructions.
Thanks in advance
@thesainthell I believe this is what he means but @DanBao-Bambu can jump in. Direct STEPS I will simply number, with dot points giving some TLDR explanations along the way.
1. Using STUDIO - First, create a custom filament, configure as you will etc. Do a calibration if you want etc
2. On the PRINTER - access the filament screen, then then AMS section and access a AMS Slot and select the filament you created in step 1. - Select the PA\K profile drop down if you did it in step 1. At this point, i find it best to ensure ALL slots are correctly set for the next step, if you sync in studio for example it will pull back all the currently assgined AMS slots. -MAKE SURE YOU CONFIRM IT-
To be clear - its on the printer screen here, I created a new filament called 'test 1912123' todays date with serial 'PLA Question mark' to show it its a new filament I created and that it works
3. Back on STUDIO - If you sync,resync, or select the AMS in the DEVICE TAB of STUDIO - it will show and RETAIN the filament, instead of returning a ? after a period of time (as in Step 2. you specified it in the Printer, preventing this bug \ loop).
As I cannot replicate the ? fault, I cannot test above but this makes sense to me, if there is a bug in one of the flow of information between Studio <---> Cloud <--> Printer 's AMS info .
@DanBao-Bambu - I understand now why I thought I couldnt replicate it initially. For me, once I select it in the PRINTER (AMS) screen ONCE, it doesnt reset anymore in STUDIO. I can repeatidly select and de-select in Studio, close and reopen studio and studio seems to remember it once I select it in the printer "once" - for that specific filament. Note: I do have to select the K profile each time after closing\opening studio - it remembers the filament not the profile.
However, Yes If I create a new filament, then the same process occurs "?" until I at least select it once and confirm through the PRINTER screen.
This still doesn't work. I have jut created a custom PRUSAMENT filament in Bambu Studio (with no PA profile or K value this time), selected it in Device tab then IMMEDIATELY went to the X1C (checking that the Wi-Fi connection is correctly established between the two in the Device tab): the new custom Prusament filament never shows up in the manufacturer drop down menu on the printer, no matter what I do on the printer screen or the tabs on the computer. It's getting a bit tiresome.
PRUSAMENT filament in Bambu Studio (with no PA profile or K value this time), selected it in Device tab then IMMEDIATELY went to the X1C (checking that the Wi-Fi connection is correctly established between the two in the Device tab):
@tokamac Strange, maybe a 2nd separate issue than the "?" mark thing - as I at least see the filament I created in studio immediatly on the printer, dated today and named specially for this thread - I created this custom named one.. see reponse above.
I then tested your example - Prusament (I just guessed PETG?) - sync works so I will leave to Bambu to test your logs etc One thing you can try is log out of your printer - and rebind it to you via the handy app etc. Especially if you havent done that after a printer firmware upgrade etc (who knows..might help).
Same issue here. white ? when I assigned the custom filaments to the AMS slots. Using cloud mode. Trying to assign anything from the printer screen isnt working, the custom filaments don't show up.
To make matters worse, I closed and reopened Bambu studio, and after carefully mapping all my custom filaments, they are no longer showing up in the "Custom filaments section", though they do all show up still in the filament selection dropdown, with their neatly created names made by the custom filament process?? I now can't even see them as an option to assign to an AMS slot on the Device page, nor are they selectable to try to re-add as custom filaments:
"User presets" are all here, with the new names assigned when I created the custom filaments:
"Custom filaments" all gone after restarting Bambu Studio
Despite the user presets still being in the filament dropdown menu on the left, they can no longer be used to recreate the custom filaments for some reason
Also not available to add to the AMS any more:
@OzDruiD That helped me a lot to understand the problem better.
I figured out that I have some sort of caching issue with an older, faulty custom filament that is preventing me from having success with the approach you described. During my test sessions, I created and deleted many custom filaments (with the same information "Extrudr" "PLA" "NX2 Matt") until they suddenly disappeared. As of now, I can create a custom filament with the above information " vendor", "material" and "serial", but the filament no longer appears in the Studio "Custom Filament" overview, nor in the AMS. Seems to be the same problem @ppamment is having.
After I create a new custom filament with a different vendor name "Extruder" but same other information, it works.
I can now create the custom filament and select it in the AMS as you mentioned. So I guess I was somehow successful.
*Edit: Updated wording to makes things more clear, thank @OzDruiD for pointing that out.
So Presets - and Custom Filaments are different things. "Filaments" is what is tied to AMS slots, Presets will be tied ot their parent "Filament".
I do assume you mean custom filaments created here and not 'saved' here (as this creates a PRESET)
As of now, I can create a custom filament with the above information " vendor", "material" and "serial", but the filament no longer appears in the Studio "Custom Filament" overview, nor in the AMS. Seems to be the same problem @ppamment is having.
After I create a new custom filament with a different vendor name "Extruder" but same other information, it works.
I can now create the custom filament and select it in the AMS as you mentioned. So
So yeah - seems a confirmed 2nd \ slightly different issue - imperfect "Syncing" \ "syncing that reports back a ?" and complete mess of custom filament process, causing loss of creations etc.
@KRiZ-R The problem you described seems different from others. When you create Filaments for eSUN and SUNLU, and enter the Filaments page of the printer screen to edit the Filaments, do you not have the Filaments you created under these two vendors? This may be because after creating a custom Filament in Studio, the cloud did not synchronize in a timely manner. You can exit the editing page and re-enter it. If it still doesn't work, make sure your "Auto sync user presets" option in Preferences is checked. If so, it may be a new bug. Can you send me your printer log and Studio log for analysis? thank you.
What would you like me to test? And how can I send the logs. I have noticed, that often when I create a Custom Filament, when I restart Bambu Studio, it has removed the new Custom Filament. The User preset is still there.
Other times, when I have created a Custom Filament, and restart Bambu Studio, it is still there, but the Custom Filament is not synced to the printer.
@OzDruiD Thanks for helping. Yes I got the difference between presets and custom filaments. I went through and converted all my presets into custom filaments using the "Copy current filament preset" option. The custom filaments then all disappeared after restarting the slicer, and now, despite the presets still appearing in the preset section, I am no longer able to create custom filaments from them with the "Copy current filament preset" function, as they do not appear in the dropdown any more. I do not know why. I took a look in my AppData folder and there are a load of JSON files that correspond to all the Custom filaments I created in the filaments folder:
They do not appear in the slicer though
I went through and converted all my presets into custom filaments using the "Copy current filament preset" option.
Might pay to test a "Brand new" filament, using the Copy - but choose "Generic PLA" or soemthing else. Also can open those JSON files and look for parent filamentr ID and see if that parent Filament still exists or you deleted it etc.,
Finally - Bambu will prolly want your files\logs.. so hold onto them for now.
@ppamment Check where the preset JSON file you created is. I suspect that the JSON file you created does not currently have the correct "filament_id". If possible, could you share your log and user folders with me?
I really hope to help you, but if it's just a problem, then I can only rely on my experience to determine what problem may have occurred, which is not accurate. Therefore, I hope that if you discover a problem, you can share the log folder at that time. Because a single log file may not detect the issue, it may already exist when creating custom materials, so the entire folder is required.
@ppamment Check where the preset JSON file you created is. I suspect that the JSON file you created does not currently have the correct "filament_id". If possible, could you share your log and user folders with me?
@DanBao-Bambu I did not create any JSON files. Bambu Studio created them for me. I simply was anxious that my presets might have been lost and so checked my AppData and took a backup just in case which is when I noticed all of those new "base" filament JSON files, which I assume were generated when I used the "create from current preset" functionlity to make my custom filaments. I have not manually created/edited any files in there so if the filament_id is incorrect, then Bambu Studio has set the incorrect filament_id which must be a bug.
Edit: Your intuition appears correct - every filament_id is null!
Here are the logs and my user folder.
Thanks for the help. It's appreciated - I am in the middle of printing Christmas gifts etc and at a bit of standstill now. I have to say that as a developer myself who has been responsible for many bugs in the past, I'm generally pretty understanding about these things, but it feels a little crazy to me that this bug was reported by users of the beta versions before the official release was put out, and yet the release went ahead anyway without addressing it...
@DanBao-Bambu I was able to create steps to reproduce this issue:
I walked into both issue A and issue B
Tried this twice with the same result both times
- Create new preset based on a system preset eg "Generic PLA". I savad it as "Generic PLA - Copy" the default
- Create a "Custom filament", and select "Copy current filament preset" and choose "Generic PLA - Copy" as the preset to create it from. A new entry is created in the available filaments "{manufacturer} {filament_type} {serial} @{printer name} {nozzle_size} nozzle.
- The filament "presets" list where you choose the filaments for AMS slots on the "Prepare" tab" now has a duplicate - "Generic PLA - Copy" and say "eSun PLA Basic @bambu Lab X1 Carbon 0.4 nozzle". You don't need duplicates, so delete "Generic PLA - Copy".
@ppamment i think this is the issue. In creating a custom filament, I dont do the intial preset copy bit - there is no need unless you want too. If your deleteing a filament preset that your creating the followup custom filament too, its possible then it will no longer be available after closing and opening Bambu studio - as it has become orphaned in the back end (If I understand what your saying correctly) - but this also would require you to mess up and delete the wrong thing.
In the create screen - is this where your definting eSun as per your example? resulting in
If you edit that custom filament - before deleteing anything like a duplicate, what does it show - this is what mine does.
I have followed your steps and been unable to replicate issue B, the loss of filaments, my test above "Stays" through multiple restarts of babmu studio, including deleteing the original duplicate "Generic PLA - Copy" Etc. Hopefully your logs show something. Note - yes Issue A ( ? ) is still preset and identified workarouind via Pritner screen also worked.
@OzDruiD
Yes, those are precisely the steps I took, and yes, the edit custom filament screen looked just like that when I was done. I even used the "Add preset" button on a couple of them as I had some existing presets for different diameters that I'd missed and didn;t add to the custom filament when creating it. That then led to having 2 entries, one for each nozzle diameter.
The first step I described - creating a preset based on a system filament is not something I would do going foraward to create new custom filaments. I had all my existing presets that I created pre v1.8 and I wanted to migrate over to become custom filaments in this case though. Copying all the settings by hand would have been tedious, which I assume is where there's an option to copy from a preset. I only added it into the reproducible steps to ensure it was a complete workflow from "stock" Bambu studio. You need to have a user preset for that flow to work as you cannot delete the system presets.
It's very possible the workaround for issue A would work for me, but I cannot try it now as the Custom filaments are no longer present in the slicer.
I do not know why issue B happens for me and not for youm
Confirming I have this same issue exactly as described
@ppamment Thank you for your steps and logs. We should have found an issue that prevented the custom material from being found on the printer. The reason for this issue is that when you create a custom Filament based on a user preset derived from a system preset (such as "Generic PLA Copy"), the created preset will be considered to have a basic preset ("Generic PLA"), and this issue will be fixed in the next version. The current solution is to create directly based on Filament or system presets, and then make parameter changes to the created presets. I know this can be troublesome, but I'm sorry, but it is indeed a solution. Thank you again for your steps and logs.
@OzDruiD I have reproduced this question, but I'm not sure if it's like @ppamment . Whether to delete "Generic PLA Copy" is irrelevant, creating based on "Generic PLA Copy" is necessary. After restarting Studio, Filament disappeared: Closing Studio, I deleted the preset that was created in my directory (for example: "eSUN PLA PPAM test @ Bambu Lab X1 Carbon 0.4 noise"). Start Studio and have it download the deleted preset from the cloud again. At this point, filling_ The ID will become null and it will not be displayed on the wizard page.
@DanBao-Bambu Just to clarify, I have not edited, moved, changed or deleted the json files in the directory directly. All interactions occurred via Bambu Studio. Is it not at all possible to determine and populate the filament IDs? They look like hex values that presumably relate to something, but I do not know what. Failing that, could I remove the filament_id: null and add "inherit" to an appropriate system filament or something like that?
Also, does this mean that the "Create from current preset" function in the Custom filament wizard is just not usable?
@ppamment The function is available, but if the selected preset is a user preset created based on the system preset ("Generic PLA Copy"), it will not be available. Additionally, deleting the field "filament_id" does not work.
@ppamment
I had all my existing presets that I created pre v1.8 and I wanted to migrate over to become custom filaments in this case though. Copying all the settings by hand would have been tedious
Understood - makes perfect semse, i think its a bug fixed in next version (usiong pre-existing presets etc to make customs)
@DanBao-Bambu
I have reproduced this question, but I'm not sure if it's like @ppamment . Whether to delete "Generic PLA Copy" is irrelevant, creating based on "Generic PLA Copy" is necessary. After restarting Studio, Filament disappeared: Closing Studio, I deleted the preset that was created in my directory (for example: "eSUN PLA PPAM test @ Bambu Lab X1 Carbon 0.4 noise"). Start Studio and have it download the deleted preset from the cloud again. At this point, filling_ The ID will become null and it will not be displayed on the wizard page.
Sorry I am also confused - are you asking if I have this problem? I dont.
@ppamment After carefully analyzing the log you shared, I found that when you restart, data will be pulled from the cloud and the "fillment_id" in your file will be replaced with null. However, I did not reproduce this scenario. Can you still reproduce this problem? Or is this a must see for you?
@DanBao-Bambu I do have this problem too. Unfortunately I can’t exactly say when this happened. But what I can bring into is the information that I am using Bambu Studio on two devices, one is on macos and the other is on windows. I do believe (sorry but I tested too much without any concept so I just can believe) this happend first on windows but because of the cloud sync it takes also effect on the macos machine. Maybe this brings a new perspective on this problem.
@OzDruiD
Sorry I am also confused - are you asking if I have this problem? I dont.
I am explaining to you under what circumstances this issue may arise.
Bambu Studio Version
1.8.1.57
Where is the application from?
Bambu Lab github releases
OS version
OXZ
Additional system information
No response
Printer
X1C
How to reproduce
Actual results
Filament is selected, but about 5 seconds later, it reverts to unconfigured with a ?
Expected results
Filament stays configured.
Project file & Debug log uploads
No log
Checklist of files to include