It is possible also that the g-code for the startup is uploaded to the BambuLab servers when we edit them. I am not sure that they have to be uploaded with every job: do you know for sure ?
Otherwise maybe insert a light turn-off instructions at the startup g-code to eliminate the direct orders from BambuLab, then turn it on, then off at the end.
Saltwater: Thanks. We knew that already. You can turn off the light manually on the BambuLab P1S screen , right under the Feeding submenu. Or in the desktop app, or the iPhone app. But we are trying to turn it off automatically at the end of a print, as many sends their prints overnight.
I dont think this will work but Iâm happy to be proven wrong. I made the same enquiries with their support team about whether there was a g-code or other mechanism to turn off the light given that it is automatically turned on at the start of print.
This was the response from their support team âYou can turn the light off via the app and the slicer, which are controls for the main display. You cannot turn it off with G code, and you cannot use a third-party assistant. The light is powered from the A-P board, and it is not possible to turn it off automatically after a print has finished (no control on the board other than On/Off with no remote option).â.
I believe the gcode would be an option for the X1C but not the P1 series. Also they did confirm that the M960 gcode is for the logo light on the X1C and not for the chamber light.
I hope you prove everyone wrong though. I would really love this feature.Such a shame this wasnât available at launch.
as we both expected, you are correct.
the âm960 gcodeâ does not turn the housing light on and off.
this is not a fix.
the frustrating part is that when I got my bambu printer the LIGHT DID NOT AUTOMATICALLY TURN ON!!! they changed something.
Iâm now about 98% positive that it is the Bambu Cloud that does it. When you send a Print job from the desktop app or phone app, it goes to the bambu cloud, I believe they have changed it so that prior to or during downloading the Gcode they run the same command as if you were in the bambu app and turned the light on or off.
the reason they canât turn it back off again is because after downloading the gcode, the bambu cloud does not actively monitor every single printer to see that the print job finished to shut the light back off. and I get it that makes sense. it wouldnât be practical to monitor every printer runningâŚ
here would be a great idea. go find out who made a change to turn on the light via bambu cloud, and change it back.
I appologize, I used the wrong terminology, and it is important to use the correct wording.
I believe it is the Bambu Network Plugin, that got updated and changed, combined with Bambuâs server. this is what is turning the light on automatically.
so there is really nothing we can do except ask Bambu to turn it back off, or give us some kind of OPTION to not have it enabled.
What exactly is the problem with the light being on or off? Youâve mentioned many send their prints overnight, so does it keeep someone awake? I think it may be nice to see if the printer is printing, or not, but is the light essential?
Is this area specific?
If I turn my light on my P1S off, it stays off until I turn it on, regardless of printing or not printing, or starting a new print. Same for my A1 mini
What I have noticed recently is the display ony P1S used to come out of dim mode when a print started down loading. Doesnât seem to do this anymore.
I donât see why the light has to stay ON, it just shows poor design/engineering. few have their printers on a boat, where energy is tight, and we are trying to minimize any watt here and there. But even then, you maybe right, the light does not consume much, and who cares if it dies faster because it stays ON, because the bambu engineers could not tell us what G-code could turn this light OFF.
Mine use to until the update that I originally posted about. since then, every time I start a print it comes on and stays on until I MANUALLY turn it offâŚ
If you look through the gcode, you will find statements such as â M1002 gcode_claim_action : 0â the claim_action allows the gcode to directly act on the firmware (the light can be controlled by the mqtt stream). You could use a text editor to write some test gcode just more or less trying various values to turn the light on/off. Iâm not sure if later releases of firmware have effected it. I run in Lan mode.
Is there any solution to the light staying on after the print has finished? Or a Gcode to enable us to manually add it to a print job yet?
no.
here is what I believe they changed.
the Bambu CLOUD has always been able to turn the light on and off.
by bambu cloud I mean when you send the file to bambu to print. it is utilizing the same code that the phone app uses to turn the light on and off.
so at some point, bambu changed the code in the cloud to turn the light on when it starts downloading the file to print. Like I have said before, it turns the light on before the file is even done downloading.
here is the senario
The problem in essence, is that there is no âgcodeâ that is turning the light on. it is the bambu cloud servers using the same function as the bambu app. because the servers disconnect from the printer after the download, there is no way to turn the light back off after the print finishes.
so bambu has to decide, do we turn the light ON when we send the print file, or do we leave it off. they canât do both because it is not controlled by gcode, and the servers are no longer connected or aware of the printer after the file downloads and it starts to print.
Thanks for that clear description of whatâs going on.
So the best way for this to get fixed is for Bambu @BambuLab to update the firmware so that a Gcode does switch the light on/off so that we can all control the light remotely. Including the printer owner.
When will that happen? How do we reinforce to Bambu that this is whatâs needed.
Iâm new to Bambu printers and shocked to find thereâs no auto light modes for printer and AMS. This is nearly a year old, is this planned obsolescence? Even if you donât care about the environment or electricity costs, electronics have a lifespan, so wastefully burning them out seems counter productive.
yeah, I think weâre all wanting this and also surprised this wasnât a configurable option somewhere in software. Either way, it doesnât look like this is going to be something addressed in this generation of their printers. All feedback today, research and my own engagement with support has always come back with this not being achievable. Iâll look at other opportunities in the future when I add some additional lighting to the unit.
The AMS maybe, but there is no way it is not possible for the interior light. You can literally turn it off via the app. If they are claiming no auto mode without a new printer purchase that is marketing BS. Iâll just have to use a smart plug.
is it possible. absolutley. but what I suspect is it is not possible in the G code!
it is only possible via the bambu SERVER. if you use the app on your phone to turn the light on and off it is a signal from the bambu server sending the machine a signal to turn the light on and off. Not the Gcode.
the problem is they only really have two choices. do like they originally did. and go back into the server software and turn OFF the line of code that is now turning on the light.
what they really canât do with any practicality is turn the light on when a print starts then turn it off when itâs done.
this would require the server to have to stay connected to the printer throughout the print to see that the print has finished, then turn off the light something that probably isnât even possible in the print code.
the âfixâ is to just NOT turn the light on automatically when the server sends a print job to the printer.
that is what is happening right now. in the bambu handy app or the Bambu studio. the .stl is uploaded to bambu servers. it then sends the .stl to your printer.
as we can see, before the print is even fully downloaded (this is the gcode) the light is TURNED ON. then the gcode finishes downloading and the printer disconnects from bambu servers and proceeds to print.
THIS, is what they changed. They changed the code on THEIR servers to automatically turn the light ON any time you print something. this was not the original way it worked. but they changed it.
@slickschoppers the printer is 100% cloud connected! So if for any reason the servers are switched off we all have paperweights. Thatâs like buying a car and it can only start if it connects to the manufacturers cloud.
P1S - Most recent firmware update of just a few days ago.
And still they canât have the light turn off when the job is done; just like the X1C.
Wow - canât manage to carry over the behavior/code from one machine to another after all this time.
As a software developer for the 25 years I feel qualified in saying:
Thatâs pathetic.
Because it is not the printer software itâs self turning the light on. It is the APP, or bambu server that is turning it on.
that is why they canât âturn it offâ when itâs done.
This is what is turning on the light. I have tracked it down. I donât know the exact code on their server or option they have enabled, but what they have done is, every time their servers send a print job the server turns the light on. basically just like we would from the app. since the server does not monitor the job, it canât turn the light off.
are there ways they âcouldâ do it? yea. there are.
but the most straight forward âfixâ is to not turn the light on automatically at all !!!
the printer never use to automatically turn the light on, so a programmer somewhere changed the code on the bambu servers to do this.
Again⌠it is NOT gcode that is turning the light on and off. it is the bambu server.